Re: sarge3 kernel build r3
dann frazier wrote: On Tue, Jun 06, 2006 at 01:32:42PM -0600, dann frazier wrote: On Tue, Jun 06, 2006 at 09:23:45PM +0200, Frans Pop wrote: The more arches are built by the same person, the easier coordination is. So your offer is very welcome. Note that you'll need to check out the kernel udeb package sources from the *sarge branch* of the d-i SVN repo for the different arches as ABI numbers have to be updated there. yes, np. I'll try to have these done by this weekend. Here's the current status... DSA is pending for the security update; jmm thought he'd be able to et those released tonight. I haven't reconfirmed this with him today. There have been some interruptions (klecker running out of disk space and strange NEW processing for some packages), which micht delay this a few days further. Cheers, Moritz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: sarge3 kernel build r3
On Mon, Jun 12, 2006 at 06:50:36PM -0600, dann frazier wrote: The exceptions are: * linux-kernel-di-powerpc appears to require a 2.4 build host - I've poked around looking for help here, but no volunteers yet. Still need help with this one... * linux-kernel-di-m68k-* - I've just e-mailed pokes to a couple m68k folks Done (thanks Stephen!) * linux-kernel-di-mips* - I've poked a few mips folks; one responded saying that he could probably get a build done tomorrow night. Done (thanks tbm/Sledge!) -- dann frazier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: sarge3 kernel build r3
On Tue, Jun 13, 2006 at 03:41:42PM -0600, dann frazier wrote: On Mon, Jun 12, 2006 at 06:50:36PM -0600, dann frazier wrote: The exceptions are: * linux-kernel-di-powerpc appears to require a 2.4 build host - I've poked around looking for help here, but no volunteers yet. Still need help with this one... Sledge saw this did a build for us, so now all builds are complete and available at: people.debian.org:~dannf/3.1r3-lkdi-rebuilds Let me know if/when I should upload them. -- dann frazier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: sarge3 kernel build r3
On Tue, Jun 06, 2006 at 01:32:42PM -0600, dann frazier wrote: On Tue, Jun 06, 2006 at 09:23:45PM +0200, Frans Pop wrote: The more arches are built by the same person, the easier coordination is. So your offer is very welcome. Note that you'll need to check out the kernel udeb package sources from the *sarge branch* of the d-i SVN repo for the different arches as ABI numbers have to be updated there. yes, np. I'll try to have these done by this weekend. Here's the current status... DSA is pending for the security update; jmm thought he'd be able to et those released tonight. I haven't reconfirmed this with him today. lkdi builds for most archs are complete, and at: people.debian.org:~dannf/3.1r3-lkdi-rebuilds The exceptions are: * linux-kernel-di-powerpc appears to require a 2.4 build host - I've poked around looking for help here, but no volunteers yet. * linux-kernel-di-m68k-* - I've just e-mailed pokes to a couple m68k folks * linux-kernel-di-mips* - I've poked a few mips folks; one responded saying that he could probably get a build done tomorrow night. The only interesting bit about these rebuilds is that the jfs-modules udeb has been dropped from ia64. jfs is completely broken on ia64, and I dropped the module build before sarge's release. This probably requires a pkglist tweak in d-i. -- dann frazier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: sarge3 kernel build r3
Karl Schmidt [EMAIL PROTECTED] writes: For people wanting to install Sarge on AMD64 I recommend using the mini.iso found here: http://amd64.debian.net/debian-installer/daily/netboot/ I did a sarge jfs on RAID with home on jfs/raid1/lvm with only minor problems with this iso. There should be a mention of this iso on the main installer page for the time being. The main page http://www.us.debian.org/devel/debian-installer/ links to there under the If you'd like something newer section: * other images (netboot, usb stick, floppy, tape, etc) [alpha] [amd64] [arm] [hppa] [i386] [ia64] [m68k] [mips] [mipsel] [powerpc] [s390] [sparc] MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: sarge3 kernel build r3
(Also replying to other mails about Sarge support in Etch installer) On Wednesday 07 June 2006 20:42, Goswin von Brederlow wrote: Frans Pop [EMAIL PROTECTED] writes: I ment that when you select sarge in choose-mirror in expert mode you get the inofficial list and if you choose etch/etch+1/sid you get the official one. Ah, OK. The Etch installer currently has extremely basic support for Sarge installations which has only really been tested for i386. The real downside of using the Etch installer for Sarge is that, although a current kernel will be used for the installation, it will still install 2.6.8 for the target system (it does not use any backports). This means that there is a relatively high chance that the user will experience problems on the reboot into the target system. I'm currently unsure if the udeb that adds Sarge support for the Etch installer will make it into the final release of d-i for Etch. The main reasons are: - increasing differences between the Sarge 2.6.8 and current kernels; - questionable usability of systems installed this way; - Sarge support may be incompatible with changes needed to realize persistent device naming for harddrives. If it does make it, there will be disclaimers shown to the user after mirror selection to the effect that there is only limited support and not to come complaining if there are problems on reboot. To finally answer your question: I don't think we will offer the unofficial AMD64 mirrors in the Etch installer in this case, if only because the mirror selection happens _before_ the suite/codename is selected. Cheers, FJP pgp3KEfKaHthS.pgp Description: PGP signature
Re: sarge3 kernel build r3
Frans Pop [EMAIL PROTECTED] writes: (Also replying to other mails about Sarge support in Etch installer) On Wednesday 07 June 2006 20:42, Goswin von Brederlow wrote: Frans Pop [EMAIL PROTECTED] writes: I ment that when you select sarge in choose-mirror in expert mode you get the inofficial list and if you choose etch/etch+1/sid you get the official one. Ah, OK. The Etch installer currently has extremely basic support for Sarge installations which has only really been tested for i386. The real downside of using the Etch installer for Sarge is that, although a current kernel will be used for the installation, it will still install 2.6.8 for the target system (it does not use any backports). This means that there is a relatively high chance that the user will experience problems on the reboot into the target system. Basicaly 100% since the user would/should have used the sarge installer if possible. But adding backports to the sources.list and installing a newer kernel is easily explained in a HowTo and done by the user on the fly. I don't think that this is a real show stopper. One could think about adding backports to sources.list automatically though if the testing installer is used to install stable. I'm currently unsure if the udeb that adds Sarge support for the Etch installer will make it into the final release of d-i for Etch. The main reasons are: - increasing differences between the Sarge 2.6.8 and current kernels; That is a reason for. - questionable usability of systems installed this way; Hmm, what is questionable? A stable system with a fresher kernel is totaly usable. A lot, if not the majority, of users do this. - Sarge support may be incompatible with changes needed to realize persistent device naming for harddrives. What changes are those? Is Debian finaly going to use LABEL= or UUID= in the generated fstab? Isn't that also just limited to kernel, udev and fstab? udev is also available on backports so there should be no big problem there. If it does make it, there will be disclaimers shown to the user after mirror selection to the effect that there is only limited support and not to come complaining if there are problems on reboot. Isn't it enough that you already need expert mode? To finally answer your question: I don't think we will offer the unofficial AMD64 mirrors in the Etch installer in this case, if only because the mirror selection happens _before_ the suite/codename is selected. That is a problem indeed. Cheers, FJP MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: sarge3 kernel build r3
On Thu, Jun 08, 2006 at 01:33:57PM +0200, Goswin von Brederlow wrote: Frans Pop [EMAIL PROTECTED] writes: What changes are those? Is Debian finaly going to use LABEL= or UUID= in the generated fstab? I hope not; /dev/disk/by-* names seem a lot less kludgy to me. -- dann frazier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: sarge3 kernel build r3
On Thursday 08 June 2006 13:33, Goswin von Brederlow wrote: - increasing differences between the Sarge 2.6.8 and current kernels; That is a reason for. Only if we _would_ include some backports repository that is known to have a current backported kernel and all other packages needed with that kernel, but without random backports of other packages. And we would need some guarantees about the maintenance of and procedures for changes in such a repository (compare volatile.d.n). If we don't include such a repository, we're only offering an installation that is known not to work on the reboot. And currently we don't. If it does make it, there will be disclaimers shown to the user after mirror selection to the effect that there is only limited support and not to come complaining if there are problems on reboot. Isn't it enough that you already need expert mode? IMO not. Especially if we would add a backported repo by default as we'd have to make clear that the upgrade path of such a system to the next stable release is not guaranteed. Too many regular users choose expert mode (and you don't even need expert mode; deconf/priority=medium will offer Sarge as well). pgpH6PurOB7QA.pgp Description: PGP signature
Re: sarge3 kernel build r3
Frans Pop [EMAIL PROTECTED] writes: On Thursday 08 June 2006 13:33, Goswin von Brederlow wrote: - increasing differences between the Sarge 2.6.8 and current kernels; That is a reason for. Only if we _would_ include some backports repository that is known to have a current backported kernel and all other packages needed with that kernel, but without random backports of other packages. And we would need some guarantees about the maintenance of and procedures for changes in such a repository (compare volatile.d.n). If we don't include such a repository, we're only offering an installation that is known not to work on the reboot. And currently we don't. Worst case you have to add testing to sources.list and get the kernel from there. With the right pining or default release that still leaves you nearly completly stable. I also think we can trust backports.org to continue its great service of backporting. Lay out some groundrules that need to be met to support testing-sarge installs and I'm sure something can be worked out from there. MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: sarge3 kernel build r3
For people wanting to install Sarge on AMD64 I recommend using the mini.iso found here: http://amd64.debian.net/debian-installer/daily/netboot/ I did a sarge jfs on RAID with home on jfs/raid1/lvm with only minor problems with this iso. There should be a mention of this iso on the main installer page for the time being. Karl Schmidt EMail [EMAIL PROTECTED] Transtronics, Inc. WEB http://xtronics.com 3209 West 9th StreetPh (785) 841-3089 Lawrence, KS 66049 FAX (785) 841-0434 Time wounds all heels -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: sarge3 kernel build r3
On Tue, Jun 06, 2006 at 09:23:45PM +0200, Frans Pop wrote: The more arches are built by the same person, the easier coordination is. So your offer is very welcome. Note that you'll need to check out the kernel udeb package sources from the *sarge branch* of the d-i SVN repo for the different arches as ABI numbers have to be updated there. yes, np. I'll try to have these done by this weekend. I could do i386, sparc and S/390 myself if needed, but only next week. I'm still not sure about the status of AMD64 in this update. It would be nice if AMD64 could be brought back in line with the other arches with r3. If the kernel updates cannot be released into the main archive for AMD64, we'll have to skip that arch for d-i too. I don't think its very likely that amd64/sarge will be added to debian.org, but this is a good question for the amd64.debian.net maintainers. The next point release of sarge will have a kernel ABI change which will break net install flavors of d-i. We are preparing an updated d-i to go along with this release - does the amd64.debian.net project wish to follow suit? I have an interest (job-related) in seeing amd64.debian.net track sarge point releases, so if there is a desire but lack of resources, please let me know. -- dann frazier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: sarge3 kernel build r3
dann frazier [EMAIL PROTECTED] writes: On Tue, Jun 06, 2006 at 09:23:45PM +0200, Frans Pop wrote: The more arches are built by the same person, the easier coordination is. So your offer is very welcome. Note that you'll need to check out the kernel udeb package sources from the *sarge branch* of the d-i SVN repo for the different arches as ABI numbers have to be updated there. yes, np. I'll try to have these done by this weekend. I could do i386, sparc and S/390 myself if needed, but only next week. I'm still not sure about the status of AMD64 in this update. It would be nice if AMD64 could be brought back in line with the other arches with r3. If the kernel updates cannot be released into the main archive for AMD64, we'll have to skip that arch for d-i too. I don't think its very likely that amd64/sarge will be added to debian.org, but this is a good question for the amd64.debian.net maintainers. The next point release of sarge will have a kernel ABI change which will break net install flavors of d-i. We are preparing an updated d-i to go along with this release - does the amd64.debian.net project wish to follow suit? I have an interest (job-related) in seeing amd64.debian.net track sarge point releases, so if there is a desire but lack of resources, please let me know. Currenly we all wait for Ganneff (Joerg Jaspert) to finaly do the Sarge R2 for amd64 but aba (Andreas Barth) is close to step in as backup ftp-admin and do it himself. Hopefully with R3 we can keep up in a more timely fashion. D-I changes would be welcome and a bit of work is needed there for both sarge and etch. If possibly it would be nice to have different mirror lists for sarge and etch/sid in choose-mirror. Since you are intrested and seem to be involved in the D-I changes anyway it would be welcome if you could lead the effort for amd64 and coordinate between amd64 and D-I. For kernel changes you should best contact fs (Frederik Schueler) directly. MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: sarge3 kernel build r3
(Removed irrelevant CCs for this question) On Wednesday 07 June 2006 10:11, Goswin von Brederlow wrote: If possibly it would be nice to have different mirror lists for sarge and etch/sid in choose-mirror. This is not really a problem. choose-mirror for Sarge will remain unchanged and thus keeps using the unofficial mirrors. For the next d-i beta release for Etch we'll make sure that the exceptions for AMD64 are removed from choose-mirror so the regular mirror lists will be used for AMD64 too (in fact, these changes are already done in the udeb currently in unstable and thus in the daily built images). Cheers, FJP pgp5FWaGQ0nOF.pgp Description: PGP signature
Re: sarge3 kernel build r3
Frans Pop [EMAIL PROTECTED] writes: (Removed irrelevant CCs for this question) On Wednesday 07 June 2006 10:11, Goswin von Brederlow wrote: If possibly it would be nice to have different mirror lists for sarge and etch/sid in choose-mirror. This is not really a problem. choose-mirror for Sarge will remain unchanged and thus keeps using the unofficial mirrors. For the next d-i beta release for Etch we'll make sure that the exceptions for AMD64 are removed from choose-mirror so the regular mirror lists will be used for AMD64 too (in fact, these changes are already done in the udeb currently in unstable and thus in the daily built images). Cheers, FJP I ment that when you select sarge in choose-mirror in expert mode you get the inofficial list and if you choose etch/etch+1/sid you get the official one. Might be too much work for a transient problem though. MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: sarge3 kernel build r3
On Wed, Jun 07, 2006 at 08:42:23PM +0200, Goswin von Brederlow wrote: Frans Pop [EMAIL PROTECTED] writes: (Removed irrelevant CCs for this question) On Wednesday 07 June 2006 10:11, Goswin von Brederlow wrote: If possibly it would be nice to have different mirror lists for sarge and etch/sid in choose-mirror. This is not really a problem. choose-mirror for Sarge will remain unchanged and thus keeps using the unofficial mirrors. For the next d-i beta release for Etch we'll make sure that the exceptions for AMD64 are removed from choose-mirror so the regular mirror lists will be used for AMD64 too (in fact, these changes are already done in the udeb currently in unstable and thus in the daily built images). Cheers, FJP I ment that when you select sarge in choose-mirror in expert mode you get the inofficial list and if you choose etch/etch+1/sid you get the official one. Might be too much work for a transient problem though. I thought that installing sarge with current etch installers is broken / not supported / whatever. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: sarge3 kernel build r3
Sven Luther [EMAIL PROTECTED] writes: On Wed, Jun 07, 2006 at 08:42:23PM +0200, Goswin von Brederlow wrote: Frans Pop [EMAIL PROTECTED] writes: (Removed irrelevant CCs for this question) On Wednesday 07 June 2006 10:11, Goswin von Brederlow wrote: If possibly it would be nice to have different mirror lists for sarge and etch/sid in choose-mirror. This is not really a problem. choose-mirror for Sarge will remain unchanged and thus keeps using the unofficial mirrors. For the next d-i beta release for Etch we'll make sure that the exceptions for AMD64 are removed from choose-mirror so the regular mirror lists will be used for AMD64 too (in fact, these changes are already done in the udeb currently in unstable and thus in the daily built images). Cheers, FJP I ment that when you select sarge in choose-mirror in expert mode you get the inofficial list and if you choose etch/etch+1/sid you get the official one. Might be too much work for a transient problem though. I thought that installing sarge with current etch installers is broken / not supported / whatever. Friendly, Sven Luther It used to work and for many amd64 users nowadays it is the only way to install a stable system due to needed hardware support in 2.6.12+ kernels. I think it would be a good idea to preserv/restore that ability and to aim to support this for etch as well. If using the testing images to install stable is not possible in the future then we should seriously consider releasing images with newer kernels in point releases or having D-I on backports.org. MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: sarge3 kernel build r3
Sven Luther [EMAIL PROTECTED] writes: I ment that when you select sarge in choose-mirror in expert mode you get the inofficial list and if you choose etch/etch+1/sid you get the official one. Might be too much work for a transient problem though. I thought that installing sarge with current etch installers is broken / not supported / whatever. People readded support for it also because we have a lot of hardware support issues and in this way is easy to workaround them. -- O T A V I OS A L V A D O R - E-mail: [EMAIL PROTECTED] UIN: 5906116 GNU/Linux User: 239058 GPG ID: 49A5F855 Home Page: http://www.freedom.ind.br/otavio - Microsoft gives you Windows ... Linux gives you the whole house. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: sarge3 kernel build r3
On Thu, Jun 08, 2006 at 12:59:42AM +0200, Goswin von Brederlow wrote: If using the testing images to install stable is not possible in the future then we should seriously consider releasing images with newer kernels in point releases or having D-I on backports.org. This is being considered was discussed a lot at debconf. See the debian-kernel archives from around that time for some discussion. -- dann frazier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: sarge3 kernel build r3
On Tuesday 06 June 2006 21:32, dann frazier wrote: I don't think its very likely that amd64/sarge will be added to debian.org, I did not mean to imply that of course. but this is a good question for the amd64.debian.net maintainers. The main reason we need to know is that the d-i source needs to be updated for the ABI change and so we need to know if this update should happen for AMD64 as well as for the other arches *before* we _upload_ it. Also, from a CD building point of view amd64 is the same as other arches, even if its packages reside on a different mirror. CDs for amd64 are normally built at the same time as other arches and it would be nice if they could follow the same timeline as the main archive. If need be, the _build_ of the new installer images and the build of CDs for AMD64 could be delayed, but preferably not. pgphnsLvVfH58.pgp Description: PGP signature
