help needed -- fixing hard-coded dependencies on shared library packages

Julian Andres Klode julian.klode at canonical.com
Sat Mar 23 18:17:41 UTC 2024


On Sat, Mar 23, 2024 at 07:05:19PM +0100, Matthias Klose wrote:
> Hi,
> 
> according to
> https://magenta.jak-linux.org/ubuntu-archive/distcheck/noble.armhf/global-ben.rebuild-for.txt
> 
> we still have a lot of hard-coded dependencies on shared library packages.
> 
> These fixes just take some minutes, not only replacing a shared library name
> with another hard-coded name.  So when you're bored, can't sleep, or
> whatever, please fix some packages!
> 
> To check:
> 
>  - For architecture dependent package, check removing the
>    libfoo1 dependency, test build with nocheck, and look
>    if the dependency is still there. In this case, just
>    drop the hard-coded dependency.

You can also confirm this by looking at the first section of:

https://magenta.jak-linux.org/ubuntu-archive/distcheck/noble.armhf/proposed-binaries.txt

which tells you if you have a libfoo1 and libfoo1t64 in the same package
in the first section (trivial conflicts), in which case just go ahead with removing it.

You can also go solely by that report in theory, but then you might want
to look at the one that only lists regressions vs release:

https://magenta.jak-linux.org/ubuntu-archive/distcheck/noble.armhf/proposed-binaries.only-regressions.txt


-- 
debian developer - deb.li/jak | jak-linux.org - free software dev
ubuntu core developer                              i speak de, en



More information about the ubuntu-devel mailing list