Removal suggestion

2004-07-18 Thread Pierre Machard
Hi, I suggest that we remove libflux0 from testing. No maintainer upload since 2001, RC bug related to old libtool, and it seems that a new software is available on fluxlib.org. This software seems deprecated. QA : it seems that the maintainer is MIA. Maybe we should orphaned this package. Ch

Re: Standards for QA uploads?

2004-07-18 Thread Matthew Palmer
On Fri, Jul 16, 2004 at 03:42:59PM +0200, Pierre Machard wrote: > Don't forget to set maintainer to "Debian QA Packages <[EMAIL PROTECTED]>" D'oh! I even thought about putting that in before I started writing. Thanks for reminding me. > > * After you make your upload, subscribe to the package's

QA Upload best practices, 2nd draft

2004-07-18 Thread Matthew Palmer
I've incorporated the excellent suggestions from Pierre Machard, Andreas Metzler, and Frank Lichtenheld, to produce this new draft. Further comments appreciated. -8<- QA UPLOAD BEST PRACTICES When making an upload on a package maintained by the QA team, it is important to keep some basi

Re: QA Upload best practices, 2nd draft

2004-07-18 Thread Martin Michlmayr
* Matthew Palmer <[EMAIL PROTECTED]> [2004-07-18 19:59]: > what's going on. Setting the owner of the bug to you (not the submitter!) "Setting the owner of the bug (not the submitter!) to you" makes it clearer that you're not setting the submitter as owner. > * In most aspects of preparing a QA u

Re: Removal suggestion

2004-07-18 Thread Martin Michlmayr
* Pierre Machard <[EMAIL PROTECTED]> [2004-07-18 11:55]: > QA : it seems that the maintainer is MIA. Maybe we should orphaned > this package. I've contacted him, thanks. -- Martin Michlmayr [EMAIL PROTECTED]

Re: Mozart Debian package

2004-07-18 Thread Pierre Machard
Hi, On Sat, Jul 17, 2004 at 08:19:09PM +0200, Kevin Glynn wrote: > > > > Yes, I am very interested. I am on vacation until the 28th July, we > (the Mozart developers) have just made a mozart 1.3.1 release. My > intention was to package that when I got back and then look for a > mentor. > > We

Re: QA Upload best practices, 2nd draft

2004-07-18 Thread Rene Engelhard
Hi, Matthew Palmer wrote: > * It's also important to ensure that the maintainer address is set correctly. > The address has changed in the past, and some packages haven't had their > maintainer address changed since it's orphaning (even after several QA > uploads!), so ensure that the maintainer

Re: QA Upload best practices, 2nd draft

2004-07-18 Thread Martin Michlmayr
* Rene Engelhard <[EMAIL PROTECTED]> [2004-07-18 15:41]: > > uploads!), so ensure that the maintainer of the package is set to "Debian QA > > Packages <[EMAIL PROTECTED]>". > > Shouldn't it be Debian QA Group <[EMAIL PROTECTED]>? Yes. -- Martin Michlmayr [EMAIL PROTECTED]

Re: QA Upload best practices, 2nd draft

2004-07-18 Thread Matthew Palmer
On Sun, Jul 18, 2004 at 02:06:22PM +0100, Martin Michlmayr wrote: > * Matthew Palmer <[EMAIL PROTECTED]> [2004-07-18 19:59]: > > what's going on. Setting the owner of the bug to you (not the submitter!) > > "Setting the owner of the bug (not the submitter!) to you" makes it > clearer that you're

Re: QA Upload best practices, 2nd draft

2004-07-18 Thread Matthew Palmer
On Sun, Jul 18, 2004 at 03:41:26PM +0200, Rene Engelhard wrote: > Hi, > > Matthew Palmer wrote: > > * It's also important to ensure that the maintainer address is set > > correctly. > > The address has changed in the past, and some packages haven't had their > > maintainer address changed since

Re: QA Upload best practices, 2nd draft

2004-07-18 Thread Joey Hess
Matthew Palmer wrote: > Would you encourage people to rewrite the packaging method used (eg convert > from dh_ to cdbs) in a QA upload? I'm thinking that, apart from fixing > hideous bletcherisms of past maintainers (such as making upstream-available > packages Debian-native) we would want to avoi