Version rtla build deps wrt libtraceevent, libtracefs

Hans van Kranenburgrequested to merge
knorrie/linux:for-kernel-team-sid-rtla into sid

See commit for details. The change explicitly sets minimal required build dependency versioning for libtraceevent and libtracefs. This is helpful to have in any case.

The next question is what to do about bullseye-backports.

20:34 < Knorrie> Hi! I'm trying to build 5.19.11 on Bullseye, and it fails because of the libtraceevent version: 
                 https://paste.debian.net/plainh/9a4416fc Do you have any suggestion already about what to do about that? 
                 (since I guess you guys'll run into the same thing later anyway?)
20:44 < Knorrie> Ah, fe4d0d5dde ("rtla/Makefile: Properly handle dependencies")
22:19 < Knorrie> currently building with self-made bullseye-backports of libtraceevent 1.6.3-1 to see what happens
[...]
23:05 < bwh> Knorrie: I should really update bullseye-backports. Let me know if you decide to backport libtraceevent so I can 
             decide whether to keep rtla enabled

My other comments:

  • I can confirm that libtraceevent and libtracefs are trivial to backport for Bullseye (it just builds (tm)).
  • I can confirm that using the result, the linux package builds fine on Bullseye.
  • I'm not a RT Linux user, and I don't easily have an environment to actually test all of this, but I can just help to check that stuff builds, at least.
  • In my build result the resulting actual package dependencies for rtla (set as result of ${shlibs:Depends}) show up as: libtraceevent1 (>= 5.4), libtracefs1 (>= 1.3.0). I didn't figure out yet why and how these are set to those versions, but I guess we want to have them reflect the newer versions as well to make it actually work, make it more explicit and save time for users who otherwise might run into wild obscure problems (if they will also be available in backports).
  • If you want, I can assist with the process of asking the package maintainer of both libraries (via the BTS) to push backports of both of them to bullseye-backports, so that we can do the backports kernel with rtla enabled. Since I'm not an actual user of the software right now, I'd like to leave the actual decision to either backport them, or, not do it and disable rtla in the backports package to you.

Thanks, Knorrie

Merge request reports