Hi,
I just wrote a new script:
https://magenta.jak-linux.org/ubuntu-archive/distcheck/noble.armhf/removal-candidates.py
This is some basic apt shenanigans to walk the (build) dependencies and
then check which packages have no reverse depends and list them. It does
this iteratively, so it removes all leaf packages, and then it finds
more packages, so hence you get iterative levels.
Like britney, we do not include dependencies solely used as testsuite
triggers.
We have 3 reports
https://magenta.jak-linux.org/ubuntu-archive/distcheck/noble.armhf/removal-candidates.txt
Contains all `:armhf` leaf binaries
We should not be removing them all, because there may be no newer
version in proposed.
https://magenta.jak-linux.org/ubuntu-archive/distcheck/noble.armhf/removal-candidates.with-proposed.txt
Contains all `:armhf? leaf binaries with newer source package in
proposed (regardless of whether it built them yet)
We can remove them all, but they may not be blocking migration as
they might have a newer build in proposed.
https://magenta.jak-linux.org/ubuntu-archive/distcheck/noble.armhf/removal-candidates.with-proposed-missing.txt
Contains all `:armhf? leaf binaries that are missing in proposed
despite a newer source package being there (so the leaf subject of
missing build on armhf in update_excuses).
This will be the most useful one: These are actually blocking
migration so we should remove them.
They all conveniently include a remove-package command to run in the
last line and are updated hourly.
I suggest ubuntu-archive just looks at this at :20 past the hour
and executes the command in the final file listed above.
--
debian developer - deb.li/jak | jak-linux.org - free software dev
ubuntu core developer i speak de, en
--
ubuntu-devel mailing list
ubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
