Re: NEW-queue handling after extending group of ftp-master
On 10237 March 1977, Bartosz Fenski aka fEnIo wrote: Usually NEW-queue was handled by the date of first upload of some package. After tracking of debian-bugs and/or debian-wnpp mailing lists last days I can say it's not true anymore. So could someone explain what are the criterions now? There are criterions for the order? Well, ok. Lets define some: - How much money did you sent to one ftpmaster/assistant? - How much do you intent to send? - Are you a girl? - Alcohol level? - Random picking. Actually there are none, as the queue should be (soon) small enough to not need any. So we havent bothered too look for rules, just started. The reason for the random order is just me, approving old and new uploads - to get the queue smaller and not let newer uploads rot in the queue as long as some old stuff. Looking at the queue noone needs to worry about that, so please do something more useful like RC bug fixing. :) -- bye Joerg (NO hat on) Unstable means subject to rapid change rather than full of bugs, though sometimes it is both :-). pgpEL87OkNeyv.pgp Description: PGP signature
Re: NEW-queue handling after extending group of ftp-master
On Wed, Mar 23, 2005 at 11:09:17PM +0100, Joerg Jaspert wrote: Usually NEW-queue was handled by the date of first upload of some package. After tracking of debian-bugs and/or debian-wnpp mailing lists last days I can say it's not true anymore. So could someone explain what are the criterions now? There are criterions for the order? Well, ok. Lets define some: - How much money did you sent to one ftpmaster/assistant? - How much do you intent to send? - Are you a girl? - Alcohol level? - Random picking. I could apply for fourth alternatively. Or maybe fifth but with the 1/4 probability :P Actually there are none, as the queue should be (soon) small enough to not need any. So we havent bothered too look for rules, just started. The reason for the random order is just me, approving old and new uploads - to get the queue smaller and not let newer uploads rot in the queue as long as some old stuff. Ok. That's something what I wanted to hear. Great to see that NEW queue is handled at all and that I had to wait for answer so short ;) Looking at the queue noone needs to worry about that, so please do something more useful like RC bug fixing. :) Believe me I'm trying to investigate and fix #295131. Btw any ideas/help are welcome. Second RC bug for scorched3d is fixed both in upstream and on my box, but without fixing first one there's no need to upload. Once again hints for #295131 are welcome, since afaik it works on sarge, and not on sid so we've got probably some interesting bug in libglib or something relevant. regards fEnIo -- ,''`. Bartosz Fenski | mailto:[EMAIL PROTECTED] | pgp:0x13fefc40 | irc:fEnIo : :' : 32-050 Skawina - Glowackiego 3/15 - w. malopolskie - Poland `. `' phone:+48602383548 | proud Debian maintainer and user `- http://skawina.eu.org | jid:[EMAIL PROTECTED] | rlu:172001 signature.asc Description: Digital signature
Re: NEW-queue handling after extending group of ftp-master
On Wednesday 23 March 2005 05:33 pm, Bartosz Fenski aka fEnIo wrote: On Wed, Mar 23, 2005 at 11:09:17PM +0100, Joerg Jaspert wrote: Usually NEW-queue was handled by the date of first upload of some package. After tracking of debian-bugs and/or debian-wnpp mailing lists last days I can say it's not true anymore. So could someone explain what are the criterions now? There are criterions for the order? Well, ok. Lets define some: - How much money did you sent to one ftpmaster/assistant? - How much do you intent to send? - Are you a girl? - Alcohol level? - Random picking. I could apply for fourth alternatively. Or maybe fifth but with the 1/4 probability :P Actually there are none, as the queue should be (soon) small enough to not need any. So we havent bothered too look for rules, just started. The reason for the random order is just me, approving old and new uploads - to get the queue smaller and not let newer uploads rot in the queue as long as some old stuff. Ok. That's something what I wanted to hear. Great to see that NEW queue is handled at all and that I had to wait for answer so short ;) Looking at the queue noone needs to worry about that, so please do something more useful like RC bug fixing. :) Believe me I'm trying to investigate and fix #295131. Btw any ideas/help are welcome. Second RC bug for scorched3d is fixed both in upstream and on my box, but without fixing first one there's no need to upload. Once again hints for #295131 are welcome, since afaik it works on sarge, and not on sid so we've got probably some interesting bug in libglib or something relevant. regards fEnIo I have know idea if this would work, but what about using libwxgtk2.5.3 rather than libwxgtk2.4? I don't know how much porting effort if any would be involved in that, but libwxgtk2.5.3 seems to be built against libglib2.0 like scorched3d and libSDL, whereas (as the bug report says) libwxgtk2.4 is linked against libglib1.2. Josh -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
wxWidgets 2.5 [Was Re: NEW-queue handling after extending group of ftp-master]
On Wed, Mar 23, 2005 at 08:43:17PM -0500, Josh Metzler wrote: Believe me I'm trying to investigate and fix #295131. Btw any ideas/help are welcome. Second RC bug for scorched3d is fixed both in upstream and on my box, but without fixing first one there's no need to upload. Once again hints for #295131 are welcome, since afaik it works on sarge, and not on sid so we've got probably some interesting bug in libglib or something relevant. I have know idea if this would work, but what about using libwxgtk2.5.3 rather than libwxgtk2.4? I don't know how much porting effort if any would be involved in that, but libwxgtk2.5.3 seems to be built against libglib2.0 like scorched3d and libSDL, whereas (as the bug report says) libwxgtk2.4 is linked against libglib1.2. Can be done, but libwxgtk2.5 is a non-releasable mess because it results in mutual breakage with libwxgtk2.4 when the packages are co-installed; so any package that's updated to wxWidgets 2.5 is almost certainly not going to make it into sarge. -- Steve Langasek postmodern programmer signature.asc Description: Digital signature
