[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: DM application for Adam Cécile (Le_Vert)



On 04/02/08 at 22:43 +0100, Aurélien GÉRÔME wrote:
> On Mon, Feb 04, 2008 at 04:02:16PM +0100, Lucas Nussbaum wrote:
> > Regarding the example of #443702 (fuse-source's NMU), there are many
> > examples of DDs not replying positively to NMUs, so it doesn't seem fair
> > to reject DM/DD based on this. A recent example is #459193, where
> > Aurélien Gérôme (currently waiting for DAM approval) didn't answered
> > very welcomly to an NMU I sponsored. Are there other examples of
> > socially-incorrect behaviour from Adam?
> 
> Sorry, but I fail to see the relation between my behaviour in #459193
> and Adam's in #443702. I do not mind receiving a NMUdiff in a bug
> report and I certainly like the idea. However, I was upset to find
> the so-said NMUdiff in a DELAYED queue 20 minutes later, without
> giving me time to anwser.

The bug was reported 16 days earlier, and you didn't comment on it, nor mark it
pending. The part of the patch that fixed the bug was:
@@ -38,7 +37,7 @@
 		HELPDIR=$(TARGET)/usr/share/dancer-services \
 		WHOAMI=root
 
-	touch $(TARGET)/var/lib/dancer-services/{glines,jupes}.conf
+	touch $(TARGET)/var/lib/dancer-services/glines.conf $(TARGET)/var/lib/dancer-services/jupes.conf
 	touch $(TARGET)/etc/dancer-services/logon.news
 
 	# Lintian overrides...

You probably agree that it was not rocket science. I think that it was safe to
assume that fixing that bug was not on the top of your TODO list, or you would
probably have figured the fix yourself.

> I learnt during the NM process that NMUers are supposed to contact
> the maintainer before rushing forward. This is at least what I did
> in #451417, #450446, and #434150.

This is a recommended practice, not a mandatory one. And in practice,
when processing a lot of NMUs, it is much easier to:
1. contact the maintainer through the BTS
2. immediately upload to DELAYED/n
3. if the maintainer answers, cancel/delay some more the upload
Than to:
1. contact the maintainer through the BTS
2. wait an "appropriate" amount of time
3. upload without going through DELAYED

The result is exactly the same, and, FWIW, during all the NMUs I sponsored to
fix dash build failures, you were the only one to complain.
-- 
| Lucas Nussbaum
| lucas@lucas-nussbaum.net   http://www.lucas-nussbaum.net/ |
| jabber: lucas@nussbaum.fr             GPG: 1024D/023B3F4F |

Attachment: signature.asc
Description: Digital signature


Reply to: