Hi, On Mon, Apr 27, 2015 at 08:49:52PM +0100, Joe Mullally wrote: > http://ci.debian.net and autopkgtest are awesome. > > Has anyone thought of writing something like apt-listbugs that checks > package upgrades/new installs against the CI data recently? > > Seems like an obvious and easy win towards getting a safely upgradable > "rolling release" debian version based on CI that has been discussed > before.
That is interesting, although the original idea was to do that checking on the archive side i.e. preventing packages that fail their CI (or that make reverse dependencies fail theirs) from migrating to testing. Such a client-side tool would however be useful anyway, at least for people running unstable. apt-listbugs has some logic to pin buggy packages if the users says so, and to remove the pinning when the corresponding bugs get fixed; it would be nice to not duplicate that. I'm CC:ing apt-listbugs maintainer(s?) for input. > An extra problem dimension here currently is determining whether a > package failure is due to a new change in the package itself or a new > change in a dependency. debci already does this; a package won't be blamed for another package failure if the failing package itself was also updated. The test suite for this is at http://sources.debian.net/src/debci/0.12/test/test_blame.sh/ If you can think of other test cases please let me know (or better report bugs against debci). -- Antonio Terceiro <terce...@debian.org>
signature.asc
Description: Digital signature
