Re: unexpected NMUs || buildd queue
Bartosz Fenski aka fEnIo <fenio@o2.pl> writes:
> On Sat, Jul 17, 2004 at 04:22:58PM +0200, Goswin von Brederlow wrote:
>> >> Then uploads are treated as NMUs, and we start going around in circles
>> >> (it was this issue that started this thread).
>> >
>> > <shrug> That's just people whinging. Far more important that you know
>> > what happened to your upload (and Maintainer is right, not
>> > Changed-By). It's also the actual meaning of the fields - one person
>> > changed it, and another is responsible for it.
>>
>> Getting your packages NMUed doesn't look good in the NM
>> process. The DAM is looking at that but I don't know if he is
>> (always) looking close enough to notice it was a sponsoring.
>
> Really? So this could delay my application.
Delay hardly. Just sway the DAM one way or another if you are right in
on the edge of accept/reject. It could be the drop that makes the
barrel spill.
> I don't know when there will be new release of my packages so this could
> take even several weeks/months, and right now there are NMUes and they
> don't look good.
>
> Considering your opinion I really wonder if I should close it by hand.
>
> I finnished my application on February, so I'm waiting five months now, and
> I'll do anything to avoid next delays.
>
> Is it really so wrong to close it by sending mail xxx-done@b.d.o with the
> explanation that it was mistake?
You should definatly close any bugs that are only taged fixed because
the upload was an NMU.
Having open bugs can also sway the DAM one way or another. If you
fixed them close them.
> regards
> fEnIo
MfG
Goswin
Reply to: