Re: Sarge release for amd64 - Please help to fix the remaining bugs

2005-05-03 Thread Adrian Bunk
On Tue, May 03, 2005 at 07:08:50AM -0400, sean finney wrote: > On Tue, May 03, 2005 at 10:22:04AM +0200, Adrian Bunk wrote: > > BTW: The interaction between the two MySQL server packages in > > unstable/sarge at purge time is *ahem* interesting. > > They are really time bombs ready to exp

Re: Sarge release for amd64 - Please help to fix the remaining bugs

2005-05-03 Thread sean finney
On Tue, May 03, 2005 at 10:22:04AM +0200, Adrian Bunk wrote: > BTW: The interaction between the two MySQL server packages in > unstable/sarge at purge time is *ahem* interesting. > They are really time bombs ready to explode in a few days or > years. > It seems RC bugs are requ

Re: Sarge release for amd64 - Please help to fix the remaining bugs

2005-05-03 Thread Adrian Bunk
On Tue, May 03, 2005 at 12:15:43AM -0700, Steve Langasek wrote: > On Tue, May 03, 2005 at 03:54:10AM +0200, Adrian Bunk wrote: > > On Fri, Apr 29, 2005 at 09:10:10PM -0700, Steve Langasek wrote: > > > On Fri, Apr 29, 2005 at 10:52:02PM -0500, Adam M. wrote: > > > > > >Ideally, we would have agreem

Re: Sarge release for amd64 - Please help to fix the remaining bugs

2005-05-03 Thread Steve Langasek
On Tue, May 03, 2005 at 03:54:10AM +0200, Adrian Bunk wrote: > On Fri, Apr 29, 2005 at 09:10:10PM -0700, Steve Langasek wrote: > > On Fri, Apr 29, 2005 at 10:52:02PM -0500, Adam M. wrote: > > > >Ideally, we would have agreement to update all of the following packages > > > >to > > > >libmysqlclie

Re: Sarge release for amd64 - Please help to fix the remaining bugs

2005-05-02 Thread Adrian Bunk
On Fri, Apr 29, 2005 at 09:10:10PM -0700, Steve Langasek wrote: > On Fri, Apr 29, 2005 at 10:52:02PM -0500, Adam M. wrote: > > > >Ideally, we would have agreement to update all of the following packages to > > >libmysqlclient12 at the same time: > > > I would suggest that libmysqlclient14 should

Re: Sarge release for amd64 - Please help to fix the remaining bugs

2005-04-29 Thread Francesco Paolo Lovergine
On Mon, Apr 25, 2005 at 04:10:21PM -0700, Steve Langasek wrote: > Ideally, we would have agreement to update all of the following packages to > libmysqlclient12 at the same time: > > courier > cyrus-sasl2 > exim4 > linesrv > pam-mysql > postfix > proftpd ^^^ yet do

Re: Sarge release for amd64 - Please help to fix the remaining bugs

2005-04-29 Thread Steve Langasek
On Fri, Apr 29, 2005 at 10:52:02PM -0500, Adam M. wrote: > >Ideally, we would have agreement to update all of the following packages to > >libmysqlclient12 at the same time: > I would suggest that libmysqlclient14 should be used if possible. MySQL > has changed the way passwords are stored in the

Re: Sarge release for amd64 - Please help to fix the remaining bugs

2005-04-29 Thread Adam M.
Steve Langasek wrote: >Ideally, we would have agreement to update all of the following packages to >libmysqlclient12 at the same time: > > I would suggest that libmysqlclient14 should be used if possible. MySQL has changed the way passwords are stored in the database and this prevents clients f

Re: Sarge release for amd64 - Please help to fix the remaining bugs

2005-04-25 Thread Joey Hess
Goswin von Brederlow wrote: > We have daily builds and the normal upload in > > http://debian-amd64.alioth.debian.org/pure64/pool/unstable/main/amd64/d/debian-installer/debian-installer-images_20041227_amd64.tar.gz > > I guess you want that untared to > /dists/sarge/main/installer-amd64/ on the n

Re: Sarge release for amd64 - Please help to fix the remaining bugs

2005-04-25 Thread Steve Langasek
On Mon, Apr 25, 2005 at 11:40:25AM -0300, Henrique de Moraes Holschuh wrote: > On Mon, 25 Apr 2005, Andreas Jochens wrote: > > Unfortunately, quite a few important packages still Build-Depend > > on libmysqlclient10-dev: > > > > cyrus-sasl2 > > cyrus-sasl2-mit > Frozen. I will gladly update them

Re: Sarge release for amd64 - Please help to fix the remaining bugs

2005-04-25 Thread Goswin von Brederlow
[EMAIL PROTECTED] (Andrew M.A. Cater) writes: > On Mon, Apr 25, 2005 at 11:32:25AM +0200, Andreas Jochens wrote: >> Debian sarge release for the amd64 architecture >> --- >> >> At the amd porters irc meeting on 2005-04-23 07:00 UTC, the amd64 porting >>

Re: Sarge release for amd64 - Please help to fix the remaining bugs

2005-04-25 Thread Goswin von Brederlow
Joey Hess <[EMAIL PROTECTED]> writes: > Andreas Jochens wrote: >> Debian sarge release for the amd64 architecture >> --- >> >> At the amd porters irc meeting on 2005-04-23 07:00 UTC, the amd64 porting >> team decided to release a version of sarge for am

Re: Sarge release for amd64 - Please help to fix the remaining bugs

2005-04-25 Thread Bernd Eckenfels
In article <[EMAIL PROTECTED]> you wrote: > Debian sarge release for the amd64 architecture Yes! Very good move. Congrats. Keep it up. Greetings Bernd -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Sarge release for amd64 - Please help to fix the remaining bugs

2005-04-25 Thread Andreas Jochens
Andrew M.A. Cater wrote: > On Mon, Apr 25, 2005 at 11:32:25AM +0200, Andreas Jochens wrote: >> Debian sarge release for the amd64 architecture >> --- >> >> At the amd porters irc meeting on 2005-04-23 07:00 UTC, the amd64 porting >> team decided to relea

Re: Sarge release for amd64 - Please help to fix the remaining bugs

2005-04-25 Thread Andreas Jochens
Hello Kurt, thank you for the clarifications. On 05-Apr-25 19:49, Kurt Roeckx wrote: > On Mon, Apr 25, 2005 at 11:32:25AM +0200, Andreas Jochens wrote: > > gnustep-base - + does not build with gcc-3.3 (needs gcc >= 3.4) > It looks like it builds fine with gcc-3.3. But if my memory is >

Re: Sarge release for amd64 - Please help to fix the remaining bugs

2005-04-25 Thread Andrew M.A. Cater
On Mon, Apr 25, 2005 at 11:32:25AM +0200, Andreas Jochens wrote: > Debian sarge release for the amd64 architecture > --- > > At the amd porters irc meeting on 2005-04-23 07:00 UTC, the amd64 porting > team decided to release a version of sarge for amd64

Re: Sarge release for amd64 - Please help to fix the remaining bugs

2005-04-25 Thread Kurt Roeckx
On Mon, Apr 25, 2005 at 07:36:36PM +0200, Adrian von Bidder wrote: > > Does that mean amd64 installer come without a mailer by default? Or will the > amd64 installer install a different mailer? The problem is that the old version of libmysqlclient-lgpl was build before we switched to an nptl onl

Re: Sarge release for amd64 - Please help to fix the remaining bugs

2005-04-25 Thread Kurt Roeckx
On Mon, Apr 25, 2005 at 11:32:25AM +0200, Andreas Jochens wrote: > > There are still a few packages in sarge which fail to build from source > on amd64. Those packages will not be part of the amd64 release of sarge. I've made a list list on saterday too which included all patched versions in the

Re: Sarge release for amd64 - Please help to fix the remaining bugs

2005-04-25 Thread Andreas Jochens
Steve Langasek wrote: >> portslave- "pppd.h: No such file or directory" > > Hmm, you may want to re-check this against current versions of ppp and > portslave. I just re-checked this again and now portslave builds fine in testing, thanks. Regards Andreas Jochens -- To UNSUBSCRI

Re: Sarge release for amd64 - Please help to fix the remaining bugs

2005-04-25 Thread Adrian von Bidder
On Monday 25 April 2005 14.51, Andreas Jochens wrote: > Steve Langasek wrote: > >> libmysqlclient-lgpl - Linuxthreads test has to be switched off for > >> amd64 [...] > Unfortunately, quite a few important packages still Build-Depend > on libmysqlclient10-dev: > exim4 Does that mean amd64 inst

Re: Sarge release for amd64 - Please help to fix the remaining bugs

2005-04-25 Thread Henrique de Moraes Holschuh
On Mon, 25 Apr 2005, Andreas Jochens wrote: > Unfortunately, quite a few important packages still Build-Depend > on libmysqlclient10-dev: > > cyrus-sasl2 > cyrus-sasl2-mit Frozen. I will gladly update them if the release team tells me to go ahead and do it. -- "One disk to rule them all, One

Re: Sarge release for amd64 - Please help to fix the remaining bugs

2005-04-25 Thread Steve Greenland
On 25-Apr-05, 04:32 (CDT), Andreas Jochens <[EMAIL PROTECTED]> wrote: > Package BTS Bug Problem description > --- --- > amynth #274703+ missing '#include ' in main.cc Or possibly '#include ', depending on

Re: Sarge release for amd64 - Please help to fix the remaining bugs

2005-04-25 Thread Kevin B. McCarty
Andreas Jochens wrote: mn-fit #301509 segmentation fault on 64bit architectures FYI, this looks like it's due to some 64-bit brokenness in Cernlib (on which mn-fit depends). The same problem appears on alpha and ia64. I don't expect this to be solved for a long while, if ever; certa

Re: Sarge release for amd64 - Please help to fix the remaining bugs

2005-04-25 Thread Joey Hess
Andreas Jochens wrote: > Debian sarge release for the amd64 architecture > --- > > At the amd porters irc meeting on 2005-04-23 07:00 UTC, the amd64 porting > team decided to release a version of sarge for amd64 which is based on the > unpatched Debian

Re: Sarge release for amd64 - Please help to fix the remaining bugs

2005-04-25 Thread Andreas Jochens
Hello Steve, thank you for your quick reply to my amd64 bug list. Steve Langasek wrote: >> libmysqlclient-lgpl - Linuxthreads test has to be switched off for amd64 > > I'm not going to give this a high priority, personally; all my reasons for > adding this package in the first place have since

Re: Sarge release for amd64 - Please help to fix the remaining bugs

2005-04-25 Thread Steve Langasek
Hi Andreas, On Mon, Apr 25, 2005 at 11:32:25AM +0200, Andreas Jochens wrote: > Packages from sarge with build problems on amd64 > > There are still a few packages in sarge which fail to build from source > on amd64. Those packages will not be part

Re: Sarge release (Re: Bits (Nybbles?) from the Vancouver release team meeting)

2005-04-05 Thread Henrique de Moraes Holschuh
On Tue, 15 Mar 2005, Sven Luther wrote: > Since when are you following these issues ? and what experience do you have > with how debian works ? And did you read Anthony's post on how this worked > out. Since 1998 I think, and I experienced first hand how difficult is to get something through some

Re: Sarge release (Re: Bits (Nybbles?) from the Vancouver release team meeting)

2005-03-14 Thread Sven Luther
On Mon, Mar 14, 2005 at 09:12:42PM -0300, Henrique de Moraes Holschuh wrote: > On Tue, 15 Mar 2005, Sven Luther wrote: > > Where are the minutes of the discussion, where are detailed explanation of > > the > > problems trying to be sovled ? Where is a call to alternative solution ? > > Where > >

Re: Sarge release (Re: Bits (Nybbles?) from the Vancouver release team meeting)

2005-03-14 Thread Henrique de Moraes Holschuh
On Tue, 15 Mar 2005, Sven Luther wrote: > Where are the minutes of the discussion, where are detailed explanation of the > problems trying to be sovled ? Where is a call to alternative solution ? Where > is a call for help from the arch porters for security and infrastructure > issues ? Given that

Re: Sarge release (Re: Bits (Nybbles?) from the Vancouver release team meeting)

2005-03-14 Thread Sven Luther
On Mon, Mar 14, 2005 at 07:44:03PM -0300, Henrique de Moraes Holschuh wrote: > On Mon, 14 Mar 2005, Sven Luther wrote: > > Yes, but the utherly arrogant and despreciating way in how this announcement > > Chill out. It was a RFC, and it was labelled as such. It may not be perfect, > and obviously i

Re: Sarge release (Re: Bits (Nybbles?) from the Vancouver release team meeting)

2005-03-14 Thread Henrique de Moraes Holschuh
On Mon, 14 Mar 2005, Sven Luther wrote: > Yes, but the utherly arrogant and despreciating way in how this announcement Chill out. It was a RFC, and it was labelled as such. It may not be perfect, and obviously it will see some (many?) changes yet. But it was NOT arrogant or depreciating. Some of

Re: Sarge release (Re: Bits (Nybbles?) from the Vancouver release team meeting)

2005-03-14 Thread Sven Luther
On Mon, Mar 14, 2005 at 07:23:33PM +0100, Christian Perrier wrote: > Quoting Steve Langasek ([EMAIL PROTECTED]): > > Hello all, > > > > As promised earlier on -project[0], after the release team/ftpmaster > > team meeting-of-minds last weekend, we have some news to share with the > > rest of the p

Re: sarge release

2003-11-19 Thread martin f krafft
also sprach martin f krafft <[EMAIL PROTECTED]> [2003.11.13.0800 +0100]: > I get your point, and I will tend to the RC bug as soon as somehow > possible. Right now I am swamped, and I simply wanted to get a feel > whether I am already in the crowd of those upholding the release, or > whether I am j

Re: sarge release

2003-11-13 Thread martin f krafft
also sprach Scott James Remnant <[EMAIL PROTECTED]> [2003.11.12.2312 +0100]: > I'd always understood that bugs with a severity of 'serious' or > above (also knows as Release Critical, or RC bugs) should always > be treated with the highest priority, not just when near > a release. also sprach Bria

Re: sarge release

2003-11-12 Thread Colin Watson
On Wed, Nov 12, 2003 at 10:26:57PM +0100, martin f krafft wrote: > I apologise if this is covered elsewhere, I am currently totally > swamped and can't afford too much time for Debian. > > I am going to be away from my machine(s) starting 22 Nov until the > middle of December. I currently have 1 R

Re: sarge release

2003-11-12 Thread Brian Nelson
martin f krafft <[EMAIL PROTECTED]> writes: > I apologise if this is covered elsewhere, I am currently totally > swamped and can't afford too much time for Debian. > > I am going to be away from my machine(s) starting 22 Nov until the > middle of December. I currently have 1 RC bug and several oth

Re: sarge release

2003-11-12 Thread Scott James Remnant
On Wed, 2003-11-12 at 21:26, martin f krafft wrote: > I am going to be away from my machine(s) starting 22 Nov until the > middle of December. I currently have 1 RC bug and several other bugs > against my packages. If sarge's release will happen in 2003, I will > bite the bullet and fix these bugs