Il giorno mer, 23-02-2005 alle 20:21 +0100, Adrian Bunk ha scritto:
> On Wed, Feb 23, 2005 at 07:59:39PM +0100, Giuseppe Sacco wrote:
[...]
> > Hi Adrian,
> > I did send a message to Noah, yesterday, about this NMU and about those
> > bugs; then I also get some information about his status since he seem
> > MIA. I did it, even if we are in 0-day NMU time.
> 
> Noah himself sent the RFA for his package. Since he did this but didn't 
> simply orphan the package, this should at least have given you a hint 
> that he might be reachable.

This is why I sent him the email.

> > Of corse, usually all NMUs should just tag the bugs as fixed but these
> > fixes are very simple and a simple tag wouldn't probably make the
> > package migrate to testing (because of the RC bug, but I am not really
> > sure about this) moreover Noah posted an RFA last year, so probably he
> > have no much time to focus on this package, so I think he will excuse me
> > about this.
> 
> This has nothing to do with 0-day NMUs or the severity or how simple the 
> bugs are:
> By convention, only the official package maintainer or the original bug 
> submitter close bugs.
> 
> It seems you aren't aware that different from the subject you used for 
> closing the RC bug the NMU had _nothing_ to do with the RC bug. Didn't 
> you notice, that I sent the bug more than two months after the NMU?
> Why did you pretend it was fixed by the NMU?

No, you are referring to the wrong NMU. I did an NMU early today.
Please have a look at:
http://lists.debian.org/debian-devel-changes/2005/02/msg01603.html

I am not used, as policy suggest, to close bug in changelog, so I did
send an email to every bug submitter, and close all bugs.

> Try to understand why Steve removed the sarge tag from the bug and you 
> might understand why your action was wrong.

I did.

> A hint:
> As soon as wdm reaches testing the RC bug is again 100% present...

No. See above. I even recompiled and installed it in sarge.

Bye,
Giuseppe



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to