Patrick Schoenfeld <schoenfeld@in-medias-res.com> (15/10/2007): > No? The maintainer of gpredict appearently is active (he answered in > this thread..) and a DD. You might not be aware of [1,2,3]. Reading the (originally) Cc'd bugreport might help… 1. http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=10;bug=444514 2. http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=15;bug=444514 3. http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=20;bug=444514 > > year, I would recommend Cyril to ask on -devel, and -qa if he can > > orphan the package, and then propose comprehensive NMU. Lucas has been working on that (see the thread on -devel he started some days ago), and was also giving me his views when I've been preparing this series of NMUs and the previous, during the BSP in Dijon. FWIW, he is a member of -qa. > But also if he wasn't a DD there is no reason to ignore the processes > meant to be used. Before assuming that someone is appearently inactive > someone should at least try to *contact* the maintainer, regardless of > weither the maintainer is a DD or not. I'm missing that step in your > list. There's no need to be a DD to answer to a (RC) bugreport. There's no need to be a DD to answer to a mail announcing an NMU uploaded to DELAYED/*5*. I can understand one might need time to prepare an upload (I'm currently in this case for a package), but there's still no need to be a DD to react to an NMU announce and eventually oppose. One can eventually cancel the DELAYED NMU if it is indeed not wished by the maintainer and if she/he is on her/his way to fix it. > BTW. in Cyrils case I don't see how it makes sense to orphan and adopt > the package? He did an NMU and the maintainer complained that it was > to intrusive and so Cyril asked what policy he should follow. I did a mistake by not closing the appropriate bug in the changelog. You can check that by looking at [2] and at the “Source:” line. And there's still no news about the maintainer of grig, which you (Patrick) dropped from the Cc list (along with the original bugreport). -- Cyril Brulebois
Attachment:
signature.asc
Description: Digital signature