On Sun, Aug 03, 2008 at 04:46:35AM -0700, Don Armstrong wrote:
> On Sun, 03 Aug 2008, Simon Huggins wrote:
> > It would be really neat if you could designate that a bug that is
> > assigned to another package, affects this one.
> The right way to do this is to file a bug against "this" package,
> which explains what the problem is, which is blocked by the bug
> against the "other" package.
This is incredibly clumsy though.
That means that for every bug you reassign to a library, ideally you
would:
* file another bug
* explain the problem fully in the other bug (potentially you
just clone the first bug to the other package but you would
need to add more explanation in either case)
* set the second bug to be blocked by the first bug you've
reassigned.
* manually track when the first bug goes away and close the
second bug.
> > * Update the storage
> > When a bug is closed it should be removed from the
> > per-package-it-affects index. Optionally you could notify
> > people on the [EMAIL PROTECTED] alias
> > that you had done so.
> This is the only thing that blocking bugs currently do not do. There
> is some argument that we should allow a feature to allow specific bugs
> to be automatically closed when a blocker is closed, but that's not
> something that we do currently.
You also don't get the severity of the bug on the dependent package.
I think to be honest, whilst technically you can do some of this by
being fastidious with blockers, this is a sane feature request that
would make the lives of Debian developers and other users of the BTS
easier.
Simon.
--
oOoOo - You have saved our lives. We are eternally grateful. oOoOo
oOoOo - Yeah, yeah, yeah whatever. oOoOo
oOoOo oOoOo
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
