Debian Developers - Problems with closing certain bugs

This is Interesting: Free IT Magazines  
Home > Archive > Debian Developers > June 2007 > Problems with closing certain bugs





You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

Author Problems with closing certain bugs
Daniel Schepler

2007-06-29, 7:21 pm

I appear to be unable to close certain bugs lately, while others work fine.
One earlier example was #205163, which I was trying to close as it was fixed
a long time ago. Then yesterday closing #379237 and #387587 worked, but in
the same message my attempt to close #378102 was rejected. With both #205163
and #378102 I got a bounce message saying that ###-done@bugs.debian.org was
an "unknown user".

I tried sending a mail to owner@bugs.debian.org about #205163 several days
ago, which I haven't gotten any response to yet. Does anybody else have any
idea what's going on? Anybody else who's run into this? Maybe, just a
random guess, it's not working on bug numbers containing a 0?
--
Daniel Schepler


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Adam D. Barratt

2007-06-29, 7:21 pm

On Fri, 2007-06-29 at 12:58 -0400, Daniel Schepler wrote:
> I appear to be unable to close certain bugs lately, while others work fine.
> One earlier example was #205163, which I was trying to close as it was fixed
> a long time ago. Then yesterday closing #379237 and #387587 worked, but in
> the same message my attempt to close #378102 was rejected. With both #205163
> and #378102 I got a bounce message saying that ###-done@bugs.debian.org was
> an "unknown user".


#205163 and #378102 are both archived (and therefore by definition also
closed). Modifications to archived bugs aren't possible, so debbugs
won't accept mail for them.

[#205163 was closed in October 2003 so would have been archived some
time in November 2003. #378102 was closed in July 2006 whilst archiving
was disabled and finally archived on June 17th this year.]

FWIW, I'm guessing the two bug numbers may have been typos as #378102 is
a mysql security bug and #205163 a translation for gnapster whereas your
closure message refers to gcc.

Adam


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Don Armstrong

2007-06-29, 7:21 pm

On Fri, 29 Jun 2007, Daniel Schepler wrote:
> I tried sending a mail to owner@bugs.debian.org about #205163 several days
> ago, which I haven't gotten any response to yet.


AFAICT, your message has not arrived at owner@b.d.o; but in any event,
your query appears to have been correctly answered.


Don Armstrong

--
The solution to a problem changes the problem.
-- Peer's Law

http://www.donarmstrong.com http://rzlab.ucr.edu


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Daniel Schepler

2007-06-29, 7:21 pm

On Friday 29 June 2007 13:32:44 pm Adam D. Barratt wrote:
> FWIW, I'm guessing the two bug numbers may have been typos as #378102 is
> a mysql security bug and #205163 a translation for gnapster whereas your
> closure message refers to gcc.


OK, sorry for the noise. You're completely correct, I actually meant #378012
and #215063. I guess I should have checked more carefully before putting my
foot in my mouth.
--
Daniel Schepler


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2008 webservertalk.com