Re: libstdc++ configuratrion

2005-11-14 Thread Florian Weimer
* Matthias Klose: Does it change the internal representation of std::string, or some other template instantiation provided by libstdc++? I don't see a change to the internal representation of std::string, I'm forwarding this upstream. std::string seems to be fine because the instance is

Re: petsc_2.3.0-1_i386.changes REJECTED

2005-11-14 Thread Adam C Powell IV
Greetings, Can someone please clarify what's going on here? * On November 1, I uploaded petsc-2.3.0-1_i386.changes. * On Sunday 11/6, Joerg Jaspert marked my upload rejected for now, citing number of packages and naming convention as a reason. * I gave the

Re: petsc_2.3.0-1_i386.changes REJECTED

2005-11-14 Thread Luk Claes
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Adam C Powell IV wrote: Greetings, Hi Can someone please clarify what's going on here? * On November 1, I uploaded petsc-2.3.0-1_i386.changes. * On Sunday 11/6, Joerg Jaspert marked my upload rejected for now, citing

current blockers?

2005-11-14 Thread Nathanael Nerode
So if I'm not mistaken, these are the current release blockers (based on http://lists.debian.org/debian-devel-announce/2005/10/msg4.html) There's also a fair amount of testing progression necessary of course. Have I got this about right? * releaseable binutils in unstable (necessary for

Re: [pkg-boost-devel] Re: libstdc++ configuratrion

2005-11-14 Thread Domenico Andreoli
On Mon, Nov 14, 2005 at 11:32:15AM +0100, Christophe Prud'homme wrote: can we start working on 1.33.1 ? or do you want to make some intermediary release ? i don't see any good reason to make any new upload to unstable until new gcc 4.0 upload. and even when new gcc 4.0 is uploaded, we

Re: petsc_2.3.0-1_i386.changes REJECTED

2005-11-14 Thread Adam C Powell IV
On Mon, 2005-11-14 at 18:22 +0100, Luk Claes wrote: Adam C Powell IV wrote: Greetings, Hi Can someone please clarify what's going on here? * On November 1, I uploaded petsc-2.3.0-1_i386.changes. * On Sunday 11/6, Joerg Jaspert marked my upload rejected for

Re: petsc_2.3.0-1_i386.changes REJECTED

2005-11-14 Thread Luk Claes
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Adam C Powell IV wrote: On Mon, 2005-11-14 at 18:22 +0100, Luk Claes wrote: Adam C Powell IV wrote: Greetings, Hi [...] What gives? Is this sufficient justification for rejecting a lintian-clean package? [...] I think the REJECT-FAQ [1] will

Re: petsc_2.3.0-1_i386.changes REJECTED

2005-11-14 Thread Thomas Viehmann
Adam C Powell IV wrote: As you could see in my message, I did ask Joerg again, but with no reply for a week, so nobody but Joerg knows what I did or didn't convince him of. Well, I'm not Joerg, but based on the evidence of rejects/accepts and my understanding of policy and actual practices, it

Re: current blockers?

2005-11-14 Thread Daniel Jacobowitz
On Mon, Nov 14, 2005 at 12:36:30PM -0500, Nathanael Nerode wrote: * releaseable glibc in unstable (likewise) This should be done now. There is a substantial glibc upgrade on the horizon, but I told Steve yesterday that we have no plans to do it until this one has reached testing and gotten

Re: petsc_2.3.0-1_i386.changes REJECTED

2005-11-14 Thread Joerg Jaspert
On 10473 March 1977, Adam C. Powell, IV wrote: * On Sunday 11/6, Joerg Jaspert marked my upload rejected for now, citing number of packages and naming convention as a reason. * I gave the reason for my naming convention and number of packages. * He

Re: petsc_2.3.0-1_i386.changes REJECTED

2005-11-14 Thread Adam C Powell IV
On Mon, 2005-11-14 at 21:32 +0100, Joerg Jaspert wrote: On 10473 March 1977, Adam C. Powell, IV wrote: * On Sunday 11/6, Joerg Jaspert marked my upload rejected for now, citing number of packages and naming convention as a reason. * I gave the reason for my

Re: petsc_2.3.0-1_i386.changes REJECTED

2005-11-14 Thread Adam C Powell IV
On Mon, 2005-11-14 at 20:56 +0100, Thomas Viehmann wrote: Adam C Powell IV wrote: As you could see in my message, I did ask Joerg again, but with no reply for a week, so nobody but Joerg knows what I did or didn't convince him of. Well, I'm not Joerg, but based on the evidence of

Re: library renaming due to changed libstdc++ configuration

2005-11-14 Thread Ming Hua
I have a question: On Sun, Nov 13, 2005 at 07:17:17PM +0100, Matthias Klose wrote: * Rename and Rebuild the libraries listed below. The new suffix for these packages should be in any case c2a (instead of c2). No new suffix is needed when the soname changes in a new upstream upload.

Re: library renaming due to changed libstdc++ configuration

2005-11-14 Thread Steve Langasek
On Mon, Nov 14, 2005 at 05:39:06PM -0600, Ming Hua wrote: I have a question: On Sun, Nov 13, 2005 at 07:17:17PM +0100, Matthias Klose wrote: * Rename and Rebuild the libraries listed below. The new suffix for these packages should be in any case c2a (instead of c2). No new suffix

Re: current blockers?

2005-11-14 Thread Florian Weimer
* Nathanael Nerode: * removal of non-free docs etc. from all packages IIRC, the release goal is to release without GNU FDL documentation only, not to remove all non-free documentation. At least I'm not aware of a coordinated effort in that direction. -- To UNSUBSCRIBE, email to [EMAIL

Re: petsc_2.3.0-1_i386.changes REJECTED

2005-11-14 Thread Steve Langasek
[redirecting this to -devel; discussions of ftp team NEW queue policies are off-topic for -release.] On Mon, Nov 14, 2005 at 05:13:47PM -0500, Adam C Powell IV wrote: And thats what I asked for, yes. Drop the version from -dev|-dbg|-doc, use the shlib system for the rest (which makes