If there is any architecture specific news that you'd like to have
included in the Release Notes (like new subarchs supported or dropped),
please send a proposed text to the d-doc mailing list (CC the list for
the architecture) before the end of this week.
Cheers,
Frans Pop
pgpJSfW0bTfFl.pgp
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
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
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
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
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
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
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
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
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
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
[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 0
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 de
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]
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
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
>
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
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
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
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
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
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
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
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
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
>
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
will not be part of the amd64 release of sarge.
> The packages mentioned in the table below and all their dependencies
> will not be part of the amd64 sarge release unless the listed problems
> get fixed really soon and the fixed package versions make it into sarge.
> The followi
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 sarge source packages.
The amd64
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
On Mon, Apr 04, 2005 at 05:19:41PM +0200, Martin Schulze wrote:
> Adrian Bunk wrote:
> > The milestone that included the start of the official security support
> > for sarge was only 6 days after the announcement, but is was missed by
> > more than 6 months.
> >
> > Whyever it was expected to ge
Eduard Bloch wrote:
> > Also, bear in mind that if we'd have done that, then we would still be
> > where we are right now, but would not have the debian installer ready to
> > release with sarge.
>
> Maybe. But AFAICS there are only few developers that have worked on
> both, b-f and d-i. So how wo
Adrian Bunk wrote:
> The milestone that included the start of the official security support
> for sarge was only 6 days after the announcement, but is was missed by
> more than 6 months.
>
> Whyever it was expected to get testing-security for sarge that quick, it
> should have been obvious 6 da
Hi, Steve Langasek wrote:
>>> testing-proposed-updates is _still_ missing autobuilders.
>> May I respectfully ask why that's been a problem for half a year now, IIRC?
> So if it has taken us 6 months to get the problems with testing-security
> sorted out, what do you suppose we would have done fo
Steve Langasek <[EMAIL PROTECTED]> writes:
> So if it has taken us 6 months to get the problems with testing-security
> sorted out, what do you suppose we would have done for security support if
> we had frozen and released six months ago, without first sorting out these
> problems? Gone six mont
On Wed, Mar 16, 2005 at 02:06:01AM +0100, Matthias Urlichs wrote:
> Hi, Joey Hess wrote:
> > testing-proposed-updates is _still_ missing autobuilders.
> May I respectfully ask why that's been a problem for half a year now, IIRC?
> It's not THAT difficult to set up an autobuilder. People have vol
#include
* Joey Hess [Tue, Mar 15 2005, 07:40:09PM]:
> > But considering the choice between releaseing Debian 3.1 with the new
> > installer in 2005 or releasing Debian 3.1 with boot-floppies in 2003, it
> > might have been possible finding some Debian developers hacking
> > boot-floppies to u
On Tue, Mar 15, 2005 at 07:40:09PM -0500, Joey Hess wrote:
> Adrian Bunk wrote:
> > Not after October 1st 2003 it sould have been clear that the progress
> > of the installer wasn't as good as expected. This was 2 months before
> > the announced release date.
> >
> > What would have been a secon
Hi, Joey Hess wrote:
> testing-proposed-updates is _still_ missing autobuilders.
May I respectfully ask why that's been a problem for half a year now, IIRC?
It's not THAT difficult to set up an autobuilder. People have volunteered
to work on this problem, including several who have already demon
Martin Zobel-Helas wrote:
> Also i hoped the release team and the ftp-masters would have worked on
> the current release instead of planing for the next on. Having all these
> people together sitting in one room working on the current release would
> have been much more prodcutive.
>
> Perhaps the
Adrian Bunk wrote:
> Not after October 1st 2003 it sould have been clear that the progress
> of the installer wasn't as good as expected. This was 2 months before
> the announced release date.
>
> What would have been a second plan?
> Nobody likes boot-floppies.
> But considering the choice betw
Bas Zoetekouw <[EMAIL PROTECTED]> wrote:
> I definately agree with you on this. The way this discussion is going
> atm is in the direction of finding solutions while the underlying
> problems aren't at all clear[1].
>
> [1] At least not to the developers at large.
Andreas Barth has posted a goo
Hi Pierre!
You wrote:
> btw, I think that before making very huge plans, maybe an exhaustive
> problems that have blocked the sarge release (like Adrian did) *is* the
> way to go.
I definately agree with you on this. The way this discussion is going
atm is in the direction o
On Tue, Mar 15, 2005 at 05:39:37PM +0100, Frank Lichtenheld wrote:
> So where is the lack of communication you detected?
Well, at least to me it's completely unclear why it took so long to
address the points you mentioned (t-s, d-i). There are probably very good
reasons, and people did work hard t
On Tue, Mar 15, 2005 at 04:15:38PM +0100, Martin Zobel-Helas wrote:
> On Tuesday, 15 Mar 2005, you wrote:
[...]
> Also i hoped the release team and the ftp-masters would have worked on
> the current release instead of planing for the next on. Having all these
> people together sitting in one room w
Hi Pierre,
On Tuesday, 15 Mar 2005, you wrote:
> Le Mardi 15 Mars 2005 16:15, Martin Zobel-Helas a écrit :
Full ACK on the whole mail.
Greetings
Martin
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
ore.
I agree with you, there is really communication problems (whatever the
invoked reason is, no communication is evil, period).
btw, I think that before making very huge plans, maybe an exhaustive
problems that have blocked the sarge release (like Adrian did) *is* the
way to go.
If you, d
Hi Adrian,
On Tuesday, 15 Mar 2005, you wrote:
> The timeline for another failed release date:
> - August 2nd 2004: announcement
> - August 8th 2004: "Official security support for sarge begins"
> - September 15th 2004: announced release date
>
> The milestone that included the start of the offic
Hi,
I'm a former Debian developer, and this mail contains some subjective
observations of mine regarding what lessions Debian might learn from
mistakes during the sarge release cycle.
Contents:
- Introduction
- Have a second plan - Discover problems early and react
- RC bugs - only a m
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
> >
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
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
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
ze every action as long as it doesn't fit exactly with their
> point of view.) has hidden the first topic : we nearly have a
> realease schedule and sarge release is becoming more and more reality.
Yes, but the utherly arrogant and despreciating way in how this announcement
was made didn&#
the last release team
It looks like the giant noise generated by this mail (I sometimes
wonder whether some people are in Debian just to make noise and
criticize every action as long as it doesn't fit exactly with their
point of view.) has hidden the first topic : we nearly have a
r
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
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
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
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
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
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 other bugs
against my packages. If sarge's release will h
Drew Scott Daniels <[EMAIL PROTECTED]> wrote:
> The last time I posted my unofficial release issues status I received
> several requests to change the formatting, and so I have. I plan to find a
> site to host this html document (preferably alioth), but I haven't ironed
> out the details yet. It sh
On Wed, Jul 02, 2003 at 11:20:52AM -0500, Drew Scott Daniels wrote:
> I know text is preferred by many over html, but formatting is easier for
> me in html than in text. If anyone's interested in a text only version,
> let me know.
at least use the correct mime type. This is not
application/octet-
On Wed, 2003-07-02 at 11:20, Drew Scott Daniels wrote:
> I know text is preferred by many over html, but formatting is easier for
> me in html than in text. If anyone's interested in a text only version,
> let me know.
$ lynx -dump usri.html > usri.txt
Attach/use that next time, with a reference
The last time I posted my unofficial release issues status I received
several requests to change the formatting, and so I have. I plan to find a
site to host this html document (preferably alioth), but I haven't ironed
out the details yet. It should also be strongly noted that this is an
unofficial
On Sun, Jun 15, 2003 at 11:31:27PM +0200, Stefano Zacchiroli wrote:
> On Mon, Jun 02, 2003 at 02:38:47PM -0500, Drew Scott Daniels wrote:
> > 2 ocaml status?
> > http://lists.debian.org/debian-devel/2003/debian-devel-200304/msg00986.html
> > and bug 187155. Done?
>
> Done! OCaml 3.06 has successfu
Hi,
Marcelo E. Magallon wrote:
> On Sat, Jun 14, 2003 at 09:19:19PM +0200, Christoph Hellwig wrote:
>
> > Stock OpenOffice seem to be able to embedd java applets into
> > documents. RedHat nuked this.
>
> And we can't do the same because ... ???
We have done that (as Jan wrote.)
Building n
Hi,
Drew Scott Daniels wrote:
> 2 i386 libc support? (The large thread starting with
> http://lists.debian.org/debian-devel/2003/debian-devel-200304/msg01895.html
> and going into the May archive talks about this). Do we have to wait for
> upstream to fix this? We want to stay compatible with othe
ists:
http://bjorn.haxx.se/debian/
Testing information: http://www.debian.org/devel/testing
Update excuses:
http://ftp-master.debian.org/testing/update_excuses.html.gz
Update output: http://ftp-master.debian.org/testing/update_output.txt
Archives of the mailing list for "Coordinating Debian releases"
On Sat, May 10, 2003 at 10:16:40PM -0400, Morgon Kanter wrote:
> This one time, at band camp, Marc Haber <[EMAIL PROTECTED]> wrote:
> > On Mon, 5 May 2003 17:17:20 -0500, Chris Cheney <[EMAIL PROTECTED]>
> > wrote:
> > >I have read that Linus is planning to have 2.6 released before July and
> > >ha
Your mail was a bit misleading, so a clarification will be needed:
> * The source packages should build-depend on libpng-dev or libpng12-dev,
> but those build-depending on libpng3-dev will still work.
A source package should never build-depend on libpng-dev,
especially if the source package bu
Le lun 14/04/2003 à 16:45, Drew Scott Daniels a écrit :
> 2 libpng transition? debian-devel has some discussion about this archived
> for Jan and Jul 2002.
> http://lists.debian.org/debian-devel/2002/debian-devel-200207/msg01106.html
> is quite interesting.
As the new maintainer of libpng, I can
On Mon, Apr 14, 2003 at 09:45:29AM -0500, Drew Scott Daniels wrote:
> I'd like to see a place where the status of all the various places where
> potential Sarge release issues are tracked. I feel that
> http://www.debian.org/devel/testing was missing things, and I didn't see
&
I'd like to see a place where the status of all the various places where
potential Sarge release issues are tracked. I feel that
http://www.debian.org/devel/testing was missing things, and I didn't see
anything else like this. Following the debian-devel convention, I created
something
73 matches
Mail list logo
