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

Andreas Beckmann debian at abeckmann.de
Fri Jan 13 10:29:48 UTC 2012

On 2012-01-13 11:03, Holger Levsen wrote:
> Maybe I don't understand what you mean but I don't see the problem here.

Let me try to rephrase my question:
How can we teach piuparts that this problem has already been bugged,
i.e. so that it moves the log from fail/ to bugged/? piuparts will look
at the wrong place ... the bug report for failing-package.

I'd like remove it from fail/ in order to save time from everybody who
wants to write bug reports for problems detected by piuparts - that
includes me and my finite cache for bug status for arbitrary packages
I'd never install myself :-)

> If a package supporting mysql and postgresql has a bug using mysql it's 
> pointless to make that bug affecting mysql. Or am I totally wrong with this 
> comparision?

Its the other way around. xsql is buggy, but the problem only shows up
in something-xsql, piuparts sees the problem in something-xsql and in
the BTS I'd probably do
  reassign 12345 xsql
  affects 12345 something-xsql src:something
so that the bug shows up for something-xsql while being assigned to xsql


More information about the Piuparts-devel mailing list