On Mon, Dec 19, 2016 at 05:24:38PM +0100, Andreas Beckmann wrote: > On 2016-12-19 17:13, Niels Thykier wrote: > > Though for some reason it appears that your testing version is passing > > the piuparts, which leads me to thinking that unstable and testing have > > different requirements. > > > > * @h01ger: can you confirm the above? > > Yes, the sid configuration is more strict than testing. > (primary difference is testing using --warn-on-leftovers-after-purge) I thought so too, but then instances/piuparts.conf.pejacevic has # default flags, only warning on leftover files flags-default = %(flags-base)s --warn-on-leftovers-after-purge flags-start-stretch = [tarball/sid] piuparts-flags = %(flags-default)s [tarball/stretch] piuparts-flags = %(flags-default)s %(flags-start-stretch)s which I understood as both having the same tests… And "anyway", considering piuparts results in sid are now considered for testing migrations, shouldnt we test sid+stretch with the same flags? (and maybe introduce a sid-strict suite?) -- cheers, Holger
Attachment:
signature.asc
Description: Digital signature