Re: release status

Joey Hess wrote: John Summerfield wrote: I set out to find whether the new manual provides that kind of information, or pointer to where it may be found. In the course of my search I have discovered: a) http://d-i.alioth.debian.org/manual/en.arm/apas03.html contains links to a.1 The Multi D

Re: release status

On Mon, Aug 09, 2004 at 01:52:24AM +0200, Christian Leimer wrote: > Sven Luther wrote: > > > On Sat, Aug 07, 2004 at 10:18:09PM +0200, Christian Leimer wrote: > >> Sven Luther wrote: > >> > >> > On Sat, Aug 07, 2004 at 05:02:31PM +0200, Holger Levsen wrote: > >> >> Hi, > >> >> > >> >> > Well, i

Re: release status

Joey Hess wrote: John Summerfield wrote: I set out to find whether the new manual provides that kind of information, or pointer to where it may be found. In the course of my search I have discovered: a) http://d-i.alioth.debian.org/manual/en.arm/apas03.html contains links to a.1 The Multi D

Re: release status

Sven Luther wrote: > On Sat, Aug 07, 2004 at 10:18:09PM +0200, Christian Leimer wrote: >> Sven Luther wrote: >> >> > On Sat, Aug 07, 2004 at 05:02:31PM +0200, Holger Levsen wrote: >> >> Hi, >> >> >> >> > Well, i have no idea what you are trying to do, but my guess is that >> >> > you are not loo

Re: release status

John Summerfield wrote: > I set out to find whether the new manual provides that kind of > information, or pointer to where it may be found. In the course of my > search I have discovered: > a) http://d-i.alioth.debian.org/manual/en.arm/apas03.html contains links > to > a.1 The Multi Disk HOWT

Re: release status

Joey Hess wrote: Joey Hess wrote: I guess anyone not on my home network would prefer this url: A partcular concern I have is the reason for so many

Re: release status

On Sat, Aug 07, 2004 at 10:18:09PM +0200, Christian Leimer wrote: > Sven Luther wrote: > > > On Sat, Aug 07, 2004 at 05:02:31PM +0200, Holger Levsen wrote: > >> Hi, > >> > >> > Well, i have no idea what you are trying to do, but my guess is that > >> > you are not looking in the right place. The

Re: release status

Joey Hess wrote: > I guess anyone not on my home network would prefer this url: -- see shy jo signature.asc Description: Digital signature

Re: release status

I've released d-i rc1. Great job! Also, some may find this worth reading: Would someone who was active while I wasn't working on d-i like to fill in the gap? -- see shy jo signature.asc Description: Digital signature

Re: release status

Sven Luther wrote: > On Sat, Aug 07, 2004 at 05:02:31PM +0200, Holger Levsen wrote: >> Hi, >> >> > Well, i have no idea what you are trying to do, but my guess is that >> > you are not looking in the right place. The miboot 2.4 floppies are at >> > : >> > >> > http://people.debian.org/~luther/d

Re: release status

On Sat, Aug 07, 2004 at 05:02:31PM +0200, Holger Levsen wrote: > Hi, > > > Well, i have no idea what you are trying to do, but my guess is that you > > are not looking in the right place. The miboot 2.4 floppies are at : > > > > http://people.debian.org/~luther/d-i/images/daily/powerpc-small/flo

Re: release status (checklist)

Holger Levsen wrote: > 1. is it true, that if 32mb ram installs work, 48mb will always work, too ? No. The system only enters lowmem mode at a given cutoff point, so we have to test the lowest supported amount of memory, as well as making sure that the cutoff point is at a place where there is eno

Re: release status (checklist)

Hi, On Tuesday 03 August 2004 16:43, Joey Hess wrote: > > > The test > > > checklist in installer/doc/checklist is still missing many entries and > > > the more complete it is the better I'd feel about calling this release > > > rc1 instead of beta5. > > If you'll send me a pointer (URL?) to the t

Re: release status

Hi, > Well, i have no idea what you are trying to do, but my guess is that you > are not looking in the right place. The miboot 2.4 floppies are at : > > http://people.debian.org/~luther/d-i/images/daily/powerpc-small/floppy/ hmm the boot.img from 2004-08-06, 21:24 (still) doesn't boot and

Re: release status

Yet another update: We seem to be on schedule for a release tomorrow. All images are built except for full CDs (building for next 24+ hours). To do prerelease testing, use the 20040801 images from the archive, and the 20040806 arge_d-i CDs. Official release will be after dinstall tomorrow. -- se

Re: release status

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tuesday 03 August 2004 05:55, Joey Hess wrote: > At this point the only delay is waiting for the autobuilders, which > are overloaded from all the other uploads surrounding the sarge > release, to catch up and build the d-i images. In the past 24 ho

Re: release status

Hi, At 6 Aug 04 04:23:48 GMT, Joey Hess wrote: > Kenshi Muto wrote: > > Well, what's current status of d-i release...? We delay some days. > > From [1], arm and mipsel seem need to build. Is this a show stopper? > > We got the last of the initrd builds today, it's just waiting on the > ftp-master

Re: release status

Kenshi Muto wrote: > Well, what's current status of d-i release...? We delay some days. > From [1], arm and mipsel seem need to build. Is this a show stopper? We got the last of the initrd builds today, it's just waiting on the ftp-master to move them into place, and then the CD builds. -- see s

Re: release status

At 3 Aug 04 03:55:21 GMT, Joey Hess wrote: > At this point the only delay is waiting for the autobuilders, which are > overloaded from all the other uploads surrounding the sarge release, to > catch up and build the d-i images. In the past 24 hours, we've gotten > builds for hppa, ia64, s390, and s

Re: release status

On Thu, Aug 05, 2004 at 12:07:21AM +0200, Christian Leimer wrote: > >> Since the most oldworld use scsi to boot it is very important that this > >> works. > >> > >> Maybe 2.4 should be the standard for oldworld macs since I have a lot of > >> problems getting a 2.6 kernel to work with quik. > > >

Re: release status

>> Since the most oldworld use scsi to boot it is very important that this >> works. >> >> Maybe 2.4 should be the standard for oldworld macs since I have a lot of >> problems getting a 2.6 kernel to work with quik. > > 2.4 is the default for the miboot oldworld floppies, which are the default >

Re: release status

On Wed, Aug 04, 2004 at 01:48:32PM +0200, Christian Leimer wrote: > Joey Hess wrote: > > > Rick Thomas wrote: > >> Bug#261460: Non-DHCP network config step of d-i is broken If you > >> choose to manually configure the network (don't use DHCP) the > >> installer keeps coming back to the "configure

Re: release status

Joey Hess wrote: > Rick Thomas wrote: >> Bug#261460: Non-DHCP network config step of d-i is broken If you >> choose to manually configure the network (don't use DHCP) the >> installer keeps coming back to the "configure network" step, and if >> you force it to move forward, after the reboot, the n

Re: release status

Joey Hess wrote: > At this point the only delay is waiting for the autobuilders, which are > overloaded from all the other uploads surrounding the sarge release, to > catch up and build the d-i images. In the past 24 hours, we've gotten > builds for hppa, ia64, s390, and sparc, plus a manual build

Re: release status OldWorld PowerPC "mesh" scsi

On Tue, 2004-08-03 at 10:51, Joey Hess wrote: > Rick Thomas wrote: > > Bug#261460: Non-DHCP network config step of d-i is broken If you > > choose to manually configure the network (don't use DHCP) the > > installer keeps coming back to the "configure network" step, and if > > you force it to move

Re: release status

Rick Thomas wrote: > Bug#261460: Non-DHCP network config step of d-i is broken If you > choose to manually configure the network (don't use DHCP) the > installer keeps coming back to the "configure network" step, and if > you force it to move forward, after the reboot, the network is not > configur

Re: release status (checklist)

Rick Thomas wrote: > > Joey Hess wrote: > > > The test > > checklist in installer/doc/checklist is still missing many entries and > > the more complete it is the better I'd feel about calling this release > > rc1 instead of beta5. > > If you'll send me a pointer (URL?) to the test checklist, I'l

Re: release status (checklist)

Joey Hess wrote: > The test > checklist in installer/doc/checklist is still missing many entries and > the more complete it is the better I'd feel about calling this release > rc1 instead of beta5. If you'll send me a pointer (URL?) to the test checklist, I'll try to make sure that it gets as d

Re: release status

OOOps... I accidentally hit "send" when I meant to hit "save"... Here's the complete message as I intended it to be! Rick Joey Hess wrote: > > At this point the only delay is waiting for the autobuilders, which are > overloaded from all the other uploads surrounding the sarge release, to > catc

Re: release status

Joey Hess wrote: > > At this point the only delay is waiting for the autobuilders, which are > overloaded from all the other uploads surrounding the sarge release, to > catch up and build the d-i images. In the past 24 hours, we've gotten > builds for hppa, ia64, s390, and sparc, plus a manual b

Re: release status update

On Thu, Jul 29, 2004 at 03:11:11PM -0400, Joey Hess wrote: > I've submitted what I hope will be the final debian-installer build to the > autobuilders, but it seems that recent dependency breakage in newt will > cause some of the builds to fail. I hope I can ask the autobuilders to > retry, but thi

discover on powerbook [was: Re: release status update]

Il dom, 2004-04-25 alle 00:13, Petter Reinholdtsen ha scritto: > [Giuseppe Sacco] > > A second problem I understand only now is that the powerpc discover > > we have in testing now is broken: every time I switch on my laptop > > (powerbook g4, 15", 867Mhz) it hangs when discover run and probe for >

Re: release status update

Giuseppe Sacco wrote: > I would like to have powerpc release only after having > kernel-image-2.4.25-powerpc-* version 2.4.25-8 in testing > because of #245012. If I'm expanding yuor wildcard correctly, they seem to go in tonight/tomorrow. Anyway, you have several days to get them in, but this doe

Re: release status update

[Giuseppe Sacco] > A second problem I understand only now is that the powerpc discover > we have in testing now is broken: every time I switch on my laptop > (powerbook g4, 15", 867Mhz) it hangs when discover run and probe for > parallel port devices. This means that I have to press the keyboard >

Re: release status update

Il gio, 2004-04-22 alle 18:55, Joey Hess ha scritto: [...] > - powerpc: need list of working subarches (oldworld?) I would like to have powerpc release only after having kernel-image-2.4.25-powerpc-* version 2.4.25-8 in testing because of #245012. A second problem I understand only now is

Re: release status update

On Sat, Apr 24, 2004 at 12:16:44PM -0500, elijah wright wrote: > > > - both the de4x5 and the tulip drivers fail to work with many > > > DECChip-based ethernet cards in the 2.4.2x series alpha kernels; > > > bug #228654. > > Both of these sound like reasonable candidates for errata if they're

Re: release status update

On Sat, Apr 24, 2004 at 12:54:18PM -0400, Joey Hess wrote: > Steve Langasek wrote: > > - qlogicisp driver doesn't work right with many (most?) SCSI cards; > > bug #238593 et al. > > - both the de4x5 and the tulip drivers fail to work with many > > DECChip-based ethernet cards in the 2.4.2x seri

Re: release status update

> > - both the de4x5 and the tulip drivers fail to work with many > > DECChip-based ethernet cards in the 2.4.2x series alpha kernels; > > bug #228654. > Both of these sound like reasonable candidates for errata if they're not > fixed, and not release blockers. Do you want them in the errata

Re: release status update

Steve Langasek wrote: > - qlogicisp driver doesn't work right with many (most?) SCSI cards; > bug #238593 et al. > - both the de4x5 and the tulip drivers fail to work with many > DECChip-based ethernet cards in the 2.4.2x series alpha kernels; > bug #228654. Both of these sound like reasonab

Re: release status update

On Thu, Apr 22, 2004 at 12:55:06PM -0400, Joey Hess wrote: > - alpha: still SCSI cd problems? > Please let me know of any other issues or corrections. Other major issues on alpha, both apparently kernel related: - qlogicisp driver doesn't work right with many (most?) SCSI cards; bug #

Re: release status update

On Thu, Apr 22, 2004 at 12:55:06PM -0400, Joey Hess wrote: > I'm trying to track status of various architectures at the top of TODO, > here is what I have so far. > - ia64: There is a devpts/sysvinit/glibc file conflict of some > sort that breaks debootstrap. Need a bug #.

Re: release status update

* Joey Hess <[EMAIL PROTECTED]> [2004-04-22 22:15]: > Argh, not again. libdebian-installer 0.22 went into the archive today > with some fixes for subarch handling, in particular #243692. Was that > version on your image? I tried it with 0.22 now and still see the same... it's quite strange. Just f

Re: release status update

* Thiemo Seufer <[EMAIL PROTECTED]> [2004-04-23 16:32]: > Does archdetect show the correct output for netwinder? Yes. -- Martin Michlmayr [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: release status update

Martin Michlmayr wrote: > * tbm <[EMAIL PROTECTED]> [2004-04-23 01:43]: > > > - arm: ? > > > > arm/netwinder most definitely works. It worked recently and there is > > It works; the only problem I had was that the wrong kernel was > installed. For some reason, debian-installer/kernel/su

Re: release status update

* tbm <[EMAIL PROTECTED]> [2004-04-23 01:43]: > > - arm: ? > > arm/netwinder most definitely works. It worked recently and there is It works; the only problem I had was that the wrong kernel was installed. For some reason, debian-installer/kernel/subarchitecture was not set. Unfortunat

Re: release status update

* Joey Hess <[EMAIL PROTECTED]> [2004-04-22 22:15]: > > was loaded since it has a different sub-architecture (however, iirc, > > delo-installer is also loaded on Cobalt, so I assume sub-arch handling > > is broken). > > Argh, not again. libdebian-installer 0.22 went into the archive today > with s

Re: release status update

Martin Michlmayr wrote: > I just did a successful installation on a DECstation 5000/133 via the > serial console. Everything worked fine, apart from one thing: both > colo-installer and delo-installer got loaded, and colo-installer was > executed instead of delo-installer. I have no idea why colo

Re: release status update

* Joey Hess <[EMAIL PROTECTED]> [2004-04-22 12:55]: > I'm trying to track status of various architectures at the top of TODO, > here is what I have so far. > > - arm: ? arm/netwinder most definitely works. It worked recently and there is afaict nothing that broke it in the meantime. arm

Re: release status update

* Joey Hess <[EMAIL PROTECTED]> [2004-04-22 12:55]: > - mipsel: looks good I just did a successful installation on a DECstation 5000/133 via the serial console. Everything worked fine, apart from one thing: both colo-installer and delo-installer got loaded, and colo-installer was executed

Re: release status update

On Thu, Apr 22, 2004 at 12:55:06PM -0400, Joey Hess wrote: > - m68k: need list of working subarches mac and amiga are fully supported. I hope to have support for the rest in the next couple of weeks or so, but if they aren't ready for release, so be it. -- Stephen R. Marenka If lif

Re: release status

On Sun, Mar 14, 2004 at 03:00:55PM -0500, Joey Hess wrote: > Assuming we release tomorrow, the deadline is now past for changes to > udebs that go in the initrds. All translations are uploaded. The string > freeze is over. Please limit changes to important fixes. If there are > any final fixes to b

Re: release status

Il mar, 2004-03-16 alle 10:05, Sven Luther ha scritto: > On Sun, Mar 14, 2004 at 11:26:31PM +0100, Giuseppe Sacco wrote: > > Il dom, 2004-03-14 alle 21:00, Joey Hess ha scritto: > > [...] > > > powerpc: autobuilding. kdb-chooser, airport wifi (#237894) > > > > What is the problem with au

Re: release status

On Sun, Mar 14, 2004 at 11:26:31PM +0100, Giuseppe Sacco wrote: > Il dom, 2004-03-14 alle 21:00, Joey Hess ha scritto: > [...] > > powerpc: autobuilding. kdb-chooser, airport wifi (#237894) > > What is the problem with autobuilding? I don't know if that port still > uses the kernel I com

Re: release status

Quoting Nikolai Prokoschenko ([EMAIL PROTECTED]): > Forget it, I should have looked before I asked... :( When it comes to me, don't expect me online very often on IRCI still get connection problems for getting what I consider a good IRC client (gaim) connected though a SSH tunnel when I'm at

Re: release status

On Mon, Mar 15, 2004 at 11:13:39PM +0100, Geert Stappers wrote: > On Mon, Mar 15, 2004 at 07:14:44PM +0100, Bastian Blank wrote: > > On Mon, Mar 15, 2004 at 07:09:42PM +0100, Petter Reinholdtsen wrote: > > > [Bastian Blank] > > > > Both are marked as installed in w-b. > > > I'm not sure what that m

Re: release status

On Mon, Mar 15, 2004 at 07:14:44PM +0100, Bastian Blank wrote: > On Mon, Mar 15, 2004 at 07:09:42PM +0100, Petter Reinholdtsen wrote: > > [Bastian Blank] > > > Both are marked as installed in w-b. > > I'm not sure what that means. Does that give us anything we can use > > to find out where the bin

Re: release status

On Mon, Mar 15, 2004 at 08:50:55PM +0100, Nikolai Prokoschenko wrote: > > file you mentioned me yesterday on IRC, > It's good you mentioned it. Which IRC channel do you use? Forget it, I should have looked before I asked... :( -- Nikolai Prokoschenko [EMAIL PROTECTED] / Jabber: [EMAIL PROTECTE

Re: release status

On Mon, Mar 15, 2004 at 09:27:00AM +0100, Christian Perrier wrote: > file you mentioned me yesterday on IRC, It's good you mentioned it. Which IRC channel do you use? -- Nikolai Prokoschenko [EMAIL PROTECTED] / Jabber: [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a

Re: release status

On Mon, Mar 15, 2004 at 07:09:42PM +0100, Petter Reinholdtsen wrote: > [Bastian Blank] > > Both are marked as installed in w-b. > I'm not sure what that means. Does that give us anything we can use > to find out where the binaries are? It means that w-b saw it in the parsed Packages file. Bastia

Re: release status

[Bastian Blank] > Both are marked as installed in w-b. I'm not sure what that means. Does that give us anything we can use to find out where the binaries are? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: release status

Quoting Joey Hess ([EMAIL PROTECTED]): > Christian Perrier wrote: > > Quoting Joey Hess ([EMAIL PROTECTED]): > > > Assuming we release tomorrow, the deadline is now past for changes to > > > > I couldn't find the release annoucement file you mentioned me > > yesterday on IRC, and I lost my logs fo

Re: release status

Petter Reinholdtsen wrote: > If we release the CDs tomorrow, please note that a missing s390 upload > blocks packages tasksel and shadow from entering testing. A full disk > on the m68k autobuilder block package dpkg from entering testing. > Missing i386 binary packages block pcmcia-cs from enteri

Re: release status

Christian Perrier wrote: > Quoting Joey Hess ([EMAIL PROTECTED]): > > Assuming we release tomorrow, the deadline is now past for changes to > > I couldn't find the release annoucement file you mentioned me > yesterday on IRC, and I lost my logs for checkingI remember you > mentioning some file

Re: release status

On Mon, Mar 15, 2004 at 07:13:19AM +0100, Petter Reinholdtsen wrote: > If we release the CDs tomorrow, please note that a missing s390 upload > blocks packages tasksel and shadow from entering testing. Both are marked as installed in w-b. Bastian -- No one may kill a man. Not for any purpose.

Re: release status

Quoting Joey Hess ([EMAIL PROTECTED]): > Assuming we release tomorrow, the deadline is now past for changes to I couldn't find the release annoucement file you mentioned me yesterday on IRC, and I lost my logs for checkingI remember you mentioning some file in doc/. Where is it ? -- To UNS

Re: release status

[Joey Hess] > Assuming we release tomorrow, the deadline is now past for changes > to udebs that go in the initrds. If we release the CDs tomorrow, please note that a missing s390 upload blocks packages tasksel and shadow from entering testing. A full disk on the m68k autobuilder block package dp

Re: release status

Giuseppe Sacco wrote: > Il dom, 2004-03-14 alle 21:00, Joey Hess ha scritto: > [...] > > powerpc: autobuilding. kdb-chooser, airport wifi (#237894) > > What is the problem with autobuilding? Nothing. That means it is autobuilding. -- see shy jo signature.asc Description: Digital sig

Re: release status

Il dom, 2004-03-14 alle 21:00, Joey Hess ha scritto: [...] > powerpc: autobuilding. kdb-chooser, airport wifi (#237894) What is the problem with autobuilding? I don't know if that port still uses the kernel I compile, but I had some problem lately and I manage to put it up again two days

Re: release status

Nathan Poznick wrote: > Out of curiosity, was anything figured out on bug #232415? Not that I know of except that for some reason the dev files are missing for cciss drives (whatever those are). Sounds like it's a bug in debootstrap or makedev. -- see shy jo signature.asc Description: Digital

Re: release status

Thus spake Joey Hess: > Assuming we release tomorrow, the deadline is now past for changes to > udebs that go in the initrds. All translations are uploaded. The string > freeze is over. Please limit changes to important fixes. If there are > any final fixes to build/, add them soon; I upload the fi

Re: release status

On Thu, Mar 11, 2004 at 11:56:07PM +, Martin Michlmayr wrote: > * Andrew Pollock <[EMAIL PROTECTED]> [2004-03-07 13:38]: > > > I've uploaded a package with your patch. > > > > I tested the daily build for 20040305, which included lvmcfg 0.17, and it > > now works properly, lvm10 is installed o

Re: release status

* Andrew Pollock <[EMAIL PROTECTED]> [2004-03-07 13:38]: > > I've uploaded a package with your patch. > > I tested the daily build for 20040305, which included lvmcfg 0.17, and it > now works properly, lvm10 is installed on a system that uses LVM. And that works for you? The LVM is created is ve

Re: release status update (grub notes)

> - lowmem package must enter archive > - Check archive for udebs that need to be built on various arches; >make sure everything is up-to-date. Also, make sure that eg, >appropriate kernel debs have entered the archive on each >architecture. one thing I noticed with a recent daily bu

Re: release status update

Sven Luther wrote: > chrp, chrp-rs6k and prep will be working this time around, i think > everything is there, but i need to fiddle the build system for it still > to build the initrd images, but i do this already by hand, and > everything is in place for it. This would use the powerpc netboot > in

Re: release status update

On Mon, Mar 08, 2004 at 10:29:28PM -0500, Joey Hess wrote: [...] > The string freeze has not quite started, since a few strings were > changed today. Hopefully we've seen the last of that I also just rewrote most of the strings for the cdebconf text frontend. They should certainly be reviewed by a

Re: release status update

On Mon, Mar 08, 2004 at 10:29:28PM -0500, Joey Hess wrote: > > 3. at least one successful installation report per boot method > > I have not had time to track installation reports. Could someone take > a pass through the list of recent reports and post a summary to the list > please? My vague imp

Re: Re: release status

Joey Hess wrote: > Thomas Poindessous wrote: > > On Fri, Mar 05, 2004 at 05:34:09PM -0900, Joey Hess wrote: > > > Thomas Poindessous wrote: > > > > demo must be disabled in config/sparc.cfg. I took the right to do it in > > > > CVS. > > > > > > Hmm, that must make the debian-installer-demo packag

Re: Re: release status

Peter Karbaliotis wrote: > Joey Hess wrote: > > Thomas Poindessous wrote: > > > >>On Fri, Mar 05, 2004 at 05:34:09PM -0900, Joey Hess wrote: > >> > >>>Thomas Poindessous wrote: > >>> > demo must be disabled in config/sparc.cfg. I took the right to do it in > CVS. > >>> > >>>Hmm, that must

Re: release status

On Thu, Mar 04, 2004 at 07:12:59PM -0500, Joey Hess wrote: > > I've uploaded a package with your patch. I tested the daily build for 20040305, which included lvmcfg 0.17, and it now works properly, lvm10 is installed on a system that uses LVM. Thanks. Andrew signature.asc Description: Digital

Re: release status

Peter Karbaliotis wrote: > Please see Bug #236364 for my sparc installation report (just made > yesterday). Looks like you're close.. -- see shy jo signature.asc Description: Digital signature

Re: release status

Joey Hess wrote: Thomas Poindessous wrote: On Fri, Mar 05, 2004 at 05:34:09PM -0900, Joey Hess wrote: Thomas Poindessous wrote: demo must be disabled in config/sparc.cfg. I took the right to do it in CVS. Hmm, that must make the debian-installer-demo package rather useless. yes, I didn't realize

Re: release status

Thomas Poindessous wrote: > On Fri, Mar 05, 2004 at 05:34:09PM -0900, Joey Hess wrote: > > Thomas Poindessous wrote: > > > demo must be disabled in config/sparc.cfg. I took the right to do it in > > > CVS. > > > > Hmm, that must make the debian-installer-demo package rather useless. > > yes, I di

Re: release status

On Fri, Mar 05, 2004 at 05:34:09PM -0900, Joey Hess wrote: > Thomas Poindessous wrote: > > demo must be disabled in config/sparc.cfg. I took the right to do it in > > CVS. > > Hmm, that must make the debian-installer-demo package rather useless. yes, I didn't realize that, sorry :( > What's the

Re: release status

Thomas Poindessous wrote: > since I didn't hear any reports about this, I did a check with pbuilder > and a sid environment. > > debian-installer package for sparc will build, but with these changes : > > demo must be disabled in config/sparc.cfg. I took the right to do it in > CVS. Hmm, that mu

Re: release status

On Mon, Feb 23, 2004 at 06:05:25PM -0800, Jeff Bailey wrote: > On Mon, Feb 23, 2004 at 08:39:23PM -0500, Joey Hess wrote: > > > - Make sure the debian-installer package builds for your arch in a > >clean chroot, and let me know so I can add your architecture to the > >control file. Curren

Re: release status

Andrew Pollock wrote: > I'd love to test it, I really would. It's not for want of trying, but I've > been unable to build a new CD in the same vein as the beta 1 CD, with the > new lvmcfg udeb package on it. I ended up taking the existing beta 1 CD, > copying to a directory, plopping the new udeb i

Re: release status

On Thu, Mar 04, 2004 at 11:17:21AM -0500, Joey Hess wrote: > Andrew Pollock wrote: > > Can #229328 be addressed? I've submitted a patch. It would greatly improve > > LVM support in the installation process, as it's rather broken at present. > > I had been reluctant to commit that since I don't kno

Re: release status

Andrew Pollock wrote: > Can #229328 be addressed? I've submitted a patch. It would greatly improve > LVM support in the installation process, as it's rather broken at present. I had been reluctant to commit that since I don't know enough about lvm to test it. -set -- `vgdisplay -v | grep 'NOT act

Re: release status

On Wed, Mar 03, 2004 at 04:36:16PM -0500, Joey Hess wrote: > We're still on track for release on the 15th. Here's a schedule up to > then: > > March 3rd No changes to libraries past this point. > March 6th Final code changes for i386 enter the archive. > (except n

Re: release status

Joey Hess wrote: > The last upload of the debian-installer package failed to build on > powerpc and mips. > > powerpc: > > > http://buildd.debian.org/fetch.php?&pkg=debian-installer&ver=20040227&arch=powerpc&stamp=1078039810&file=log&as=raw > > The following packages have unmet dependencie

Re: release status

On Mon, Mar 01, 2004 at 01:52:26PM -0500, Joey Hess wrote: > Stephen R Marenka wrote: > > On Mon, Feb 23, 2004 at 08:39:23PM -0500, Joey Hess wrote: > > I now have m68k daily builds at > > . They are now > > being built right off the archiv

Re: release status

Stephen R Marenka wrote: > On Mon, Feb 23, 2004 at 08:39:23PM -0500, Joey Hess wrote: > > > A few things that porters need to do soon, if you have a port that > > mostly works. Consider these mandatory for release: > > > > - Get daily builds working. > > Currently working: alpha, i386, ia64,

Re: release status

The last upload of the debian-installer package failed to build on powerpc and mips. powerpc: http://buildd.debian.org/fetch.php?&pkg=debian-installer&ver=20040227&arch=powerpc&stamp=1078039810&file=log&as=raw The following packages have unmet dependencies: di-utils-shell: Depends: lib

Re: release status

On Mon, Feb 23, 2004 at 08:39:23PM -0500, Joey Hess wrote: > A few things that porters need to do soon, if you have a port that > mostly works. Consider these mandatory for release: > > - Get daily builds working. > Currently working: alpha, i386, ia64, m68k, sparc I now have m68k daily b

Re: To partman or not to partman (was Re: release status)

On Sun, Feb 29, 2004 at 01:19:35PM +, Martin Michlmayr wrote: > * Sven Luther <[EMAIL PROTECTED]> [2004-02-29 14:25]: > > > Based on what I know of partman and with newbie installation in mind, > > > I would definitely say "go fo partman as default on i386 and as an > > > option on other archs

Re: To partman or not to partman (was Re: release status)

Quoting Sven Luther ([EMAIL PROTECTED]): > > Read the sentence again. He says he considers it the default for i386 > > and maybe powerpc. > > Ok, then, sounds nice for me. Yes, this is what I intended to write. The idea is : the two archs were the "newbie" ratio may be high are i386 and powerpc

Re: To partman or not to partman (was Re: release status)

* Sven Luther <[EMAIL PROTECTED]> [2004-02-29 14:25]: > > Based on what I know of partman and with newbie installation in mind, > > I would definitely say "go fo partman as default on i386 and as an > > option on other archs (except powerpc if it works OK for them?)". > > Why do you say except pow

Re: To partman or not to partman (was Re: release status)

On Sun, Feb 29, 2004 at 08:11:42AM +0100, Christian Perrier wrote: > Quoting Joey Hess ([EMAIL PROTECTED]): > > > What say you gentlemen? > > Based on what I know of partman and with newbie installation in mind, > I would definitely say "go fo partman as default on i386 and as an > option on othe

Re: release status

On Mon, Feb 23, 2004 at 08:39:23PM -0500, Joey Hess wrote: [...] > There is not a lot of time in 3 weeks for a protracted string freeze, > so I would like to know whter one seems necessary at all, and whether > a very short one, such as a 2 day string freeze, would be enough to at > least get the t

Re: release status --> l10n status

> Some action for "awaking" translators may be needed (no offense > intended here). > > Spanish Good news : Spanish is again on its way towards 100%. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

  1   2   >