Bug#532187: please mark bugs already closed by an upload in versioned view
On Thu, 12 Aug 2010, Bernhard R. Link wrote:
> * Bernhard R. Link <firstname.lastname@example.org> [090608 19:37]:
> > * Don Armstrong <email@example.com> [090607 23:23]:
> > > On Sun, 07 Jun 2009, Bernhard R. Link wrote:
> > > > When a package is uploaded to unstable and not yet built and
> > > > installed on all architectures, debugs output is quite confusing, as
> > > > all bugs are still displayed as "Outstanding".
> > >
> > > This is because they are outstanding.
> > At least the upload pending bugs are not suddenly more outstanding then
> > before the upload.
> If I understand the code correctly, then the pending tag seems to no
> longer exists after closing the bug. No idea if not removing that
> now that closed no longer means closed in another way to improve the
> situation here.
Yeah, the old closed code removed the pending tag. I'm not sure if
that's ideal, however.
> > I think such a new "Outstanding on some architectures only"
> > category would massively improve the current situation.
> I've attached an patch that might do what I think it should do. I've
> no idea how I can test debbugs and my perl is not that good, but the
> changes needed seem to be relatively trivial.
The main problem with this is that it changes the syntax of max_buggy,
which has all kinds of far-reaching effects. It seems this can be
calculated as a separate call to a different function than max_buggy,
and just populate another field that get_status returns instead of
further overloading the pending field.
In fact, I think what you may actually want to know is whether the bug
is -done or not, not whether it's even fixed in a particular version
in that archive. But I'm not totally sure about that.
All of that said, thanks for taking the impetus to write up a patch
life's not a paragraph
And death i think is no parenthesis
-- e.e. cummings "Four VII" _is 5_