On 2014-05-21 13:08, Holger Levsen wrote: > On Dienstag, 20. Mai 2014, Yann Dirson wrote: >> http://bugs.debian.org/726799 shows that, while using dist-upgrade may >> be useful and can reveal problems, it does not test *just* the package >> upgrade it claims to be testing (sounds obvious, but well... ;). > > Yes, it's obvious and I'd also argue it's obviously the right thing to do. So > in fact I'm also considering to just close your bug (as not a bug, but > design) > and/or make it wishlist and close it then. > > The usual way to upgrade the system is precisely to use "apt-get upgrade" or > "apt-get dist-upgrade" and _not_ to upgrade a single package with "apt-get > install $package/$version" - that's not a common real world use case.
IIRC piuparts even did the apt-get install way in the past - this usually failed if the upgrade involved a bigger transition that requires removal of some packages... I might consider doing "apt-get install" upgrade tests (since they operate on "valid" systems as long as no --force-* options get involved) in addition to the "normal" distupgrade tests if they can uncover problems not found by distupgrade tests - but only if they don't create false positives (or these can be filtered automatically). And I'd like to see an example first... Andreas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
