Thanks for reporting this bug.

On Tue, 2017-10-17 at 21:23 +0200, Alexander Kurtz wrote:
> Package: libbpfcc
> Version: 0.3.0-3
> Severity: serious
> Justification: Makes the package uninstallable on most architectures
> 
> Hi!
> 
> As [0] shows, libbpfcc has unsatisfiable dependencies on everything
> but
> amd64. This is because [1] is inherently wrong, "linux-headers-amd64"
> is of course only available on amd64, the other architectures have
> their own meta-packages [2]. Unfortunately there is (AFAIK) no good
> way
> to properly solve the "this package needs the current kernel headers
> installed" problem in Debian because
> 
>    1. There are no (real or virtual) "linux-{image,headers}-
>       generic" packages (like in Ubuntu [3,4]) which have the same
> name on
>       all architectures.
>    2. Even if there were such packages, there's no guarantee that
> "linux-
>       headers-generic" would point to the headers matching the
> *currently
>       running* kernel (which is what libbcc needs). In fact, with
> partial
>       upgrades, migrations from unstable to testing, upgraded-but-
> not-yet-
>       rebooted machines, etc., it is quite likely that libbpfcc will
> be
>       broken even if all its dependencies are fulfilled.
> 
> I therefore ask you to
> 
>    1. Revert [1].
>    2. Reopen [5] and put a note regarding the requirements of the
> kernel
>       headers in README.Debian and/or the package description.
>    3. Talk to the Debian Linux maintainers to find a proper solution
> to
>       this problem. It's probably not going to be easy, but these
> kinds of
>       problems really deserve to be fixed properly.
> 

Yes. My bad. I completely missed about the dependency's limitation
across architectures. I'll fix it soon.

README.Debian is the wise way to deal with it. There were similar
situation with systemtap too.

> Yes, this sucks. I have run into #877925 myself and also thought that
> this should be simply solvable with a dependency. Oh, well, at least
> you may take comfort in the fact that others [6] have also run into
> this problem... ;-)
> 
> Best regards
> 
> Alexander Kurtz
> 
> [0] https://tracker.debian.org/pkg/bpfcc
> [1] https://anonscm.debian.org/git/collab-maint/bpfcc.git/commit/?id=
> f73049e48fd98dd01d4475f88f6b490e6a1b34bb
> [2] https://packages.debian.org/source/sid/linux
> [3] https://packages.ubuntu.com/artful/linux-image-generic
> [4] https://packages.ubuntu.com/artful/linux-headers-generic
> [5] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877925
> [6] https://anonscm.debian.org/git/pkg-dkms/dkms.git/tree/debian/cont
> rol#n24
-- 
Ritesh Raj Sarraf | http://people.debian.org/~rrs
Debian - The Universal Operating System

Attachment: signature.asc
Description: This is a digitally signed message part

Reply via email to