[Piuparts-devel] rescheduling all failed/bugged/untestable

Holger Levsen holger at layer-acht.org
Fri Jan 20 13:15:55 UTC 2012


On Mittwoch, 18. Januar 2012, Andreas Beckmann wrote:
> We should probably not reschedule bugged logs from squeeze and
> lenny2squeeze - the bugged state may not be recoverable if the bugs have
> been fixed in wheezy, closed and archived

hasn't this been addressed now by the following?

On Donnerstag, 19. Januar 2012, Andreas Beckmann wrote:
> piuparts.git analyze-affects
> Andreas Beckmann (2):
>       consider bugs that 'affects' a failing package
>       treat bugs without 'found' as version '~'
> We can now do
>   # assume 987654 is our bug report in buggy-package,
>   # but the problem only shows up when testing (upgrades of)
>   # failing-package with piuparts:
>   bts affects 987654 failing-package
>   # and if failing-package is from a different source with a different
>   # version number:
>   bts found 987654 failing-package/$FAILED_VERSION
? :-)

at least this allows me to address some bugs correctly, ie in lvm2 from 

On Donnerstag, 19. Januar 2012, Andreas Beckmann wrote:
> We should also remove the "keep bugged state" part from archive-old-logs
> as this may do wrong decisions. E.g. first bug is fixed (e.g. postinst
> fixed) but new problem is revealed (purge problem) - requires a new bug
> report.


> PS: there are command_not_found_during_purge.mail and
> fails_to_purge_-_command_in_postrm_not_found.mail that seem to be the
> same, but with different wording

feel free to propose to delete one :-)


More information about the Piuparts-devel mailing list