[Piuparts-devel] [PATCH] Re: tagging piuparts-detected bugs that affect other packages

Holger Levsen holger at layer-acht.org
Mon Jan 23 09:51:52 UTC 2012

Hi Andreas,

On Donnerstag, 19. Januar 2012, Andreas Beckmann wrote:
> 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

This doesnt seem to work: I sent this mail:

To: control at bugs.debian.org
found 655715 lvm2/2.02.66-5
found 655845 slapd/2.4.25-4

but each day report_newly_bugged_packages claims:

slapd/2.4.28-1.1: Maybe the bug was filed earlier: 655845 against 
lvm2/2.02.88-2: Maybe the bug was filed earlier: 655715 against lvm2/2.02.66-5

Did I understood you wrong? I duplicated this info at 
http://piuparts.debian.org/bug_howto.html ...


More information about the Piuparts-devel mailing list