Source: piuparts Severity: important 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... ;).
In this case, a number of hours have been wasted hunting for a seemingly-unreproducible bug, that was in fact perfectly reproducible, but just wrongly characterized. So: * we surely need a better test procedure for package ugrades => what's wrong with just "apt-get install $PACKAGE/sid" ? * we do need a test procedure that would reproducibly find this kind of bugs What I'm thinking of is something like a tool that would start with a large installation of packages from testing, and which would test-upgrade each one of those packages separately. Similarly, triggers could be tested from a similar setup (both for testing and sid). (and probably a ton of other tests like that) -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.13-1-amd64 (SMP w/4 CPU cores) Locale: LANG=C, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org