Re: [debian...@casulana.debian.org: testingcds 3sidamd64 (amd64 dvd) has failed; log included]
Hello, On mar., 09 août 2022, Raphael Hertzog wrote: > Ah, sure, that seems quite likely. I did not have the issue in my > tests, but I tested with a partial mirror as created by simple-cdd so I > quite likely did not hit the problematic recursive dependency. > > Can you point me to the debian-cd configuration that I shall use to reproduce > the issue? So the issue was not trivial to reproduce. FWIW, it's only reproducible in bullseye, for some reason buster was coping fine with it. But I got it reproduced and the problem was due to packages which have strong "Recommends" like libapreq2-dev which has "Recommends: libapreq2-doc (= 2.13-7+b3)" which is not satisfiable. It would never stop its recursion because the version found was not good for it. So in the end I have a new patch in the hertzog/bug601203 branch. I'm doing some further tests but it seems to solve the issue: https://salsa.debian.org/images-team/debian-cd/-/commit/ca9ac8deac5c1436f4b311a22a34a56f236dfe05 But as I investigated I found more things to fix, like quite some dead code: https://salsa.debian.org/images-team/debian-cd/-/commit/e77ade6033445571092e8663ad94a24c7e882b03 I'm going to push this soon but I would love if someone else could do a test run and ensure it doesn't break anything else. I have created a merge request to make it easier to review the code if anyone wants to do it: https://salsa.debian.org/images-team/debian-cd/-/merge_requests/26 Cheers, -- Raphaël Hertzog ◈ Offensive Security ◈ Kali Linux Developer
Re: [debian...@casulana.debian.org: testingcds 3sidamd64 (amd64 dvd) has failed; log included]
Hi Steve, On lun., 08 août 2022, Steve McIntyre wrote: > This weekly DVD run just tooke ~15h to run compared to the normal ~30m > or so. Checking the stuff in the log here, I'm thinking that this > "Deep recursion on subroutine" message is very likely due to your > changes in commit cc4e1fa450a074ef1428bf678a57cdf8b0d0f0e5. Could you > take a look please? Ah, sure, that seems quite likely. I did not have the issue in my tests, but I tested with a partial mirror as created by simple-cdd so I quite likely did not hit the problematic recursive dependency. Can you point me to the debian-cd configuration that I shall use to reproduce the issue? Cheers, -- Raphaël Hertzog ◈ Offensive Security ◈ Kali Linux Developer
Bug#601203: Released fix in git
Control: tags -1 + pending Hello, I fixed this issue in git now: https://salsa.debian.org/images-team/debian-cd/-/commit/8513b237afbdb59a4a59d1bc707d37f0aa9138f7 This was on top of a first cleanup where I turned $add_rec and $add_sug into global variables: https://salsa.debian.org/images-team/debian-cd/-/commit/c9489cd926f9b09b1359c17cc651a7a664e537a7 I think it would be great if we could make a new debian-cd upload as we have some important fixes in git by now. Steve, do you want to review my latest changes and do an upload? Let me know if you need help for the upload. Cheers, -- Raphaël Hertzog ◈ Offensive Security ◈ Kali Linux Developer
Re: Time to drop win32-loader ?
Hello, On Tue, 19 Jul 2022, Didier 'OdyX' Raboud wrote: > I haven't checked (as I don't have access to Windows machines...), but I'm > quite confident that the Windows Bootloader fiddling is quite unlikely to > work > on modern (Secure Boot ?) machines. I think I had read some report that it was indeed not working... it was in the context of Kali but there are no specific changes that might justify that the breakage would be specific to Kali. It's also one part of the ISO that still contains Debian references by default and where it's not trivial to replace it (it's embedded in the executable IIRC). > That brings two sides of the question: > * should it still be shipped on amd64 netinsts, CD's, other images? > * should it still be offered on the mirrors ? > on https://deb.debian.org/debian/tools/win32-loader/stable/ > (where it lands via dak's byhand handling upon uploads; but is manually > moved by ftp-master on migrations and release days) I think it was a cool feature (even though I never used it myself) but if we don't have the manpower to maintain it properly, we'd better ditch it. Also with EFI, the setup screens tend to be more graphical and more user friendly, and the benefit of the "Boot from Windows" feature is more limited IMO. Cheers, -- ⢀⣴⠾⠻⢶⣦⠀ Raphaël Hertzog ⣾⠁⢠⠒⠀⣿⡁ ⢿⡄⠘⠷⠚⠋The Debian Handbook: https://debian-handbook.info/get/ ⠈⠳⣄ Debian Long Term Support: https://deb.li/LTS signature.asc Description: PGP signature
Bug#993141: simple-cdd: default.downloads is missing packages used by debian-installer
Package: simple-cdd Version: 0.6.8 Severity: important User: de...@kali.org Usertags: origin-kali X-Debbugs-Cc: raph...@offensive-security.com, debian-cd@lists.debian.org While diagnosing a failure to boot an encryted install, I discovered that simple-cdd was not properly adding cryptsetup-initramfs and I fixed that directly: https://salsa.debian.org/debian/simple-cdd/-/commit/eb0d1d8960e22dd1c087b15a505b1503d76088a3 FWIW, I fixed a similar issue in debian-cd: https://salsa.debian.org/images-team/debian-cd/-/commit/8d2bd4aa2e29fedbf9e224e6ce56bb6feae2b36a However when I analyzed debian-cd's sort_deps.amd64.log I noticed that the mirror generated by simple-cdd is lacking other packages that debian-cd tries to include for the benefits of debian-installer with multiple lines like those: WARNING: 'cryptsetup-initramfs' does not appear to be available ... (ignored) Among the missing packages I believe you might want to add those: - pcmciautils - discover - dosfstools - btrfs-progs - open-iscsi - multipath-tools-boot - wireless-tools - ppp - pppoeconf - pptp-linux - wpasupplicant - rdnssd - installation-report - alsa-utils - brltty - espeakup - grub-efi-amd64-signed - shim-signed The following are also reported as missing but they no longer exist in unstable so they are not really relevant: - btrfs-tools - ufsutils - zfsutils - loop-aes-utils - apt-transport-https - linux-image-2.6-amd64 Those might be candidates to be dropped from debian-cd's listings? (cc to debian-cd@lists.debian.org) -- System Information: Debian Release: 11.0 APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'oldoldstable'), (500, 'unstable'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-8-amd64 (SMP w/16 CPU threads) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages simple-cdd depends on: ii dctrl-tools 2.24-3+b1 ii debian-cd 3.1.35 ii lsb-release 11.1.0 ii python3 3.9.2-3 ii python3-simple-cdd 0.6.8 ii reprepro5.3.0-1.2 ii rsync 3.2.3-4 ii wget1.21-1+b1 Versions of packages simple-cdd recommends: ii dose-distcheck 6.0.1-2 Versions of packages simple-cdd suggests: ii qemu-system-x86 [qemu-kvm] 1:5.2+dfsg-11 -- no debconf information -- Raphaël Hertzog
Re: Porting the standard image from live-wrapper to live-build
Hi Roland, thanks for your efforts! I would very much welcome if you could submit gradually your live-build changes to the official repository so that you don't have to keep a big fork. On Wed, 11 Nov 2020, Roland Clobus wrote: > live-wrapper: > * ISO volume ID contains '10.6.0' > ** AP: live build mentions 'buster', which contains less details You can tweak this with "lb_config --iso-volume 'Debian 10.6.0'" for example. > * Makes a beep on boot > ** AP: Should this be added to live build as well? Likely, yes. It's meant to help visually impaired users. > * The grub configuration contains 'SAYS ...' > ** AP: Should this be added to live build as well? I don't know what you are referring to. > * The grub and isolinux menus contain all available languages > ** AP: It would be nice to reproduce this in live build Is this a feature to pre-select the language from the boot menu? I'm +0. Not opposed to it but I also don't see it as a big win. > * The boot splash screen uses the Debian theme > ** AP: live build shows a helmet and the versions of the live packages. > We need the Debian-themed splash screen, combined with the version numbers Definitely! > live-build: > * /EFI/boot contains a 32-bit EFI image on the amd64 iso. > ** AP: Is this needed/correct? Pass, I don't know. > * xorriso complains about issues with Joliet (symlinks not supported, > volid too long) > ** AP: Do we need support for Joliet? Untested: does Windows XP/7/10 > support RockRidge sufficiently well? And is it needed? This warning is common and can be safely ignored AFAIK. You get it with any debian-cd generated image too. > * The packages lists are available both uncompressed and as gzip file > ** AP: Isn't just one variant suffient? live-wrapper only has the > uncompressed file Likely yes, but it doesn't hurt much. > My comments to the command line options to lb config (as shown below): > * --security false > ** AP: Shouldn't this be true per default for Debian Stable? > * --updates false > ** AP: Shouldn't this be true per default for Debian Stable? I'm not sure what you mean by "true per default for Debian Stable". There's no such concept of default value by release for some options... > * --loadlin false > ** Is this still tested? (I don't have a computer which can run 16-bit > executables at the moment) I don't think that anyone needs to set this option, yes. Cheers, -- ⢀⣴⠾⠻⢶⣦⠀ Raphaël Hertzog ⣾⠁⢠⠒⠀⣿⡁ ⢿⡄⠘⠷⠚⠋The Debian Handbook: https://debian-handbook.info/get/ ⠈⠳⣄ Debian Long Term Support: https://deb.li/LTS signature.asc Description: PGP signature
Re: Debian images on Microsoft Azure cloud
Hi, On Thu, 12 Nov 2015, Bastian Blank wrote: > On Wed, Nov 11, 2015 at 02:53:36PM +, Steve McIntyre wrote: > > My only concern is that I'd be happier if the builds were created and > > hosted on Debian project machines, like our existing official > > builds. I've been discussing that with other people for other types of > > build. How awkward/difficult would that be? > > The first problem is the DMUP; yes, Microsoft pays us to do that work. This one is a red herring. I'm paid to work on LTS updates. Others are paid to work on Debian packages for the benefit of Canonical, etc. > Also we can't share the access keys for the different Azure clouds. If Microsoft is willing to trust Debian as a supported platform, maybe they can be convinced to trust the Debian administrators and the respective teams in charge of the building the images? And in the worst case, you don't have to share the keys. You let debian.org build the images and then you download them, check them and upload them to Azure clouds from a credativ server. > Appart from that, it needs > - Jenkins or some other job scheduler, Is cron enough? > - CPU: several, > - RAM: several GB (each image have over 1.5GiB of used space, and it > needs to fit into memory at least once), > - disk: a lot of SSD, > - bandwidth: the images are uploaded daily and > - root. Those should be all solvable if you get in touch with the debian-cd/DSA team. Cheers, -- Raphaël Hertzog ◈ Debian Developer Support Debian LTS: http://www.freexian.com/services/debian-lts.html Learn to master Debian: http://debian-handbook.info/get/
Re: Bug#774811: debian-installer: debian-testing-powerpc-netinst.iso 2015-01-05 08:58 278M doesn't boot
Hi, Since this problem is powerpc specific, I'm putting debian-powe...@lists.debian.org in copy and since it concerns the bootability of an ISO image, I also add debian-cd@lists.debian.org. On Wed, 07 Jan 2015, intervenant0 wrote: I have downloaded debian-testing-powerpc-netinst.iso 2015-01-05 and I have burned a CD-R disk with the previous named iso. Then, I put the CD on my PowerMac G4 Gigabit Ethernet and hold on the keyboard key named Option for booting on it. The CD doesn't appear on boot screen. I make this twice, first with a CD-R from imation, then with a CD-R from maxell, same results. Then I have checked my CD-DVD drive by booting on my previous install CD : debian-7.4.0-powerpc-netinst.iso and I succeed to boot. [ in another mail ] Dear Maintainer, I have continued and tried an other iso : debian-jessie-DI-b2-powerpc-netinst.iso [...] Then, I put the CD on my PowerMac G4 Gigabit Ethernet and hold on the keyboard key named Option for booting on it. The CD doesn't appear on boot, so I have chose Linux logo and clicked on it. So then, I have seen displayed : First Stage Debian GNU/Linux Bootstrap Press l for GNU/Linux, x for MacOSX, c for CDROM Stage 1 Boot: End of display I have typed c and then the screen display following what was already displayed : Booting CDROM... DEFAULT CATCH!, code=fff6 at%SRR0: End of display Does anyone have any idea why jessie ISO images would not be bootable on an old G4 ? Regards, -- Raphaël Hertzog ◈ Debian Developer Support Debian LTS: http://www.freexian.com/services/debian-lts.html Learn to master Debian: http://debian-handbook.info/get/ -- To UNSUBSCRIBE, email to debian-cd-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150121112111.ga1...@home.ouaza.com
Re: Debian installer and CD BoF: my views for jessie
Hi, On Tue, 26 Aug 2014, Cyril Brulebois wrote: I might be misremembering of course but I think d-i on linux archs has been working more or less during the whole release cycle. (The parted I can confirm this as I imported d-i snapshots from git into Kali to cope with new upstream kernels that we imported too. Sometimes subsequent fix to kernel udebs were required but apart from that, it's been working well for us. Cheers, -- Raphaël Hertzog ◈ Debian Developer Discover the Debian Administrator's Handbook: → http://debian-handbook.info/get/ -- To UNSUBSCRIBE, email to debian-cd-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140827092640.gf23...@x230-buxy.home.ouaza.com
Re: Help with debian-cd's UEFI boot on a Debian derivative
On Wed, 09 Jul 2014, Raphael Hertzog wrote: We use the Debian grub package unchanged. What changed here is that we have rebuilt debian-installer images which picked those supplementary modules. So looking further into d-i changes related to this, I found this: http://anonscm.debian.org/gitweb/?p=d-i/debian-installer.git;a=commitdiff;h=81109010691ee0fc9357bd10be8fe116b9bb9f84 And the debian-installer images we generated thus have this change too. Is it possible that this change works with grub 2.0 but not 1.99 of wheezy? /me feels that I'm getting closer to the root of the problem Cheers, -- Raphaël Hertzog ◈ Debian Developer Discover the Debian Administrator's Handbook: → http://debian-handbook.info/get/ -- To UNSUBSCRIBE, email to debian-cd-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140709102250.gb27...@x230-buxy.home.ouaza.com
Re: Help with debian-cd's UEFI boot on a Debian derivative
On Wed, 09 Jul 2014, Steve McIntyre wrote: On Wed, Jul 09, 2014 at 12:22:50PM +0200, Raphael Hertzog wrote: So looking further into d-i changes related to this, I found this: http://anonscm.debian.org/gitweb/?p=d-i/debian-installer.git;a=commitdiff;h=81109010691ee0fc9357bd10be8fe116b9bb9f84 And the debian-installer images we generated thus have this change too. Is it possible that this change works with grub 2.0 but not 1.99 of wheezy? Ooh, maybe. It's *possible*, I'm not sure tbh. For Wheezy CD builds we still use the Wheezy branch of debian-cd, so I've not tested that combo. So I rebuilt d-i images with this commit reverted and then rebuilt my ISO image with the new d-i images, and the problem is gone. Thanks for your help! I double checked that the current Debian weekly build boots fine, in other word this change works well with grub 2, but not with grub 1.99. Cheers, -- Raphaël Hertzog ◈ Debian Developer Discover the Debian Administrator's Handbook: → http://debian-handbook.info/get/ -- To UNSUBSCRIBE, email to debian-cd-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140709165036.ga6...@x230-buxy.home.ouaza.com
Help with debian-cd's UEFI boot on a Debian derivative
Hello, I'm trying to use debian-cd to build an image for a Debian derivative (aka Kali Linux). I'm using this version of debian-cd: http://http.kali.org/pool/main/d/debian-cd/debian-cd_3.1.15kali1_all.deb It's plain debian-cd 3.1.15 with just a few supplementary symlinks kali pointing to wheezy in tasks/, data/ and tools/boot/. Now I'm trying to generate images with those changes to CONF.sh: # Name of the distribution for the image filename (Defaults to 'debian') -# export CDNAME=debian +export CDNAME=kali # Building wheezy cd set ... -export CODENAME=wheezy +export CODENAME=kali [...] -export MIRROR=/srv/mirror/debian +export MIRROR=/ext/mirror/kali [...] -# export NONFREE=1 +export NONFREE=1 [...] -# export FORCE_FIRMWARE=1 +export FORCE_FIRMWARE=1 [...] -export DISKTYPE=CD +export DISKTYPE=NETINST [...] -#export MAXCDS=1 +export MAXCDS=1 [...] -#export OMIT_MANUAL=1 +export OMIT_MANUAL=1 [...] -#export OMIT_DOC_TOOLS=1 +export OMIT_DOC_TOOLS=1 And I build the image with make official_images. The build seems to work fine but the resulting image doesn't boot with UEFI. I get a grub screen but whenever I select an entry, grub tells me: error: unknown command `linux'. error: unknown command `initrd'. Press any key to continue... Yet the file structure seems exactly the same than for an official Debian ISO image. And building an official Debian images in the same environment yields a fully working ISO image. So I'm wondering what I can have missed. Do you have an idea of what could be wrong ? Note that Kali rebuilds debian-installer images with newer snapshots of d-i because we track newer kernels as well. But we have the same grub packages. Here's the possibly relevant changes in the diff comparing the file listing of both images: --- debian-7.0-amd64-NETINST-1.filelist 2014-07-08 16:19:24.206922498 +0200 +++ kali-7.0-amd64-NETINST-1.filelist 2014-07-08 16:19:47.834925117 +0200 @@ -41,6 +41,7 @@ /mnt/boot/grub/x86_64-efi/efi_uga.mod /mnt/boot/grub/x86_64-efi/elf.mod /mnt/boot/grub/x86_64-efi/ext2.mod +/mnt/boot/grub/x86_64-efi/extcmd.mod /mnt/boot/grub/x86_64-efi/fat.mod /mnt/boot/grub/x86_64-efi/fixvideo.mod /mnt/boot/grub/x86_64-efi/font.mod @@ -105,6 +106,7 @@ /mnt/boot/grub/x86_64-efi/msdospart.mod /mnt/boot/grub/x86_64-efi/multiboot2.mod /mnt/boot/grub/x86_64-efi/multiboot.mod +/mnt/boot/grub/x86_64-efi/normal.mod /mnt/boot/grub/x86_64-efi/ntfscomp.mod /mnt/boot/grub/x86_64-efi/ntfs.mod /mnt/boot/grub/x86_64-efi/ohci.mod @@ -183,68 +185,32 @@ [...] @@ -281,10 +248,8 @@ /mnt/install.amd /mnt/install.amd/gtk /mnt/install.amd/gtk/initrd.gz -/mnt/install.amd/gtk/install.bat /mnt/install.amd/gtk/vmlinuz /mnt/install.amd/initrd.gz -/mnt/install.amd/install.bat /mnt/install.amd/vmlinuz /mnt/isolinux /mnt/isolinux/adgtk.cfg [...] The first is due to debian-installer generating different debian-cd_info.tar.gz and the latter is because the Kali mirror lacks the tools directory. Comparing debian-cd_info.tar.gz I see changes to the syslinux config files, addition of grub/x86_64-efi/normal.mod grub/x86_64-efi/extcmd.mod, as well as a different checksum to grub/efi.img (but the content seems identical except for the filesystem Volume Serial Number). I don't know what to try out next. Any suggestion of further possible investigation is welcome. Thank you! -- Raphaël Hertzog ◈ Debian Developer Discover the Debian Administrator's Handbook: → http://debian-handbook.info/get/ -- To UNSUBSCRIBE, email to debian-cd-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140708151344.gc3...@x230-buxy.home.ouaza.com
Bug#703431: Annoying GPG error message
Hi, On Fri, 19 Apr 2013, Robert Spencer wrote: This still requires that the keyring be installed on the system whereas we're already extracting it from the binary package in debian-cd. I'm sorry, I didn't misunderstand you. I made a bad assumption. I hope the attached patch file is satisfactory. Yes, it's mostly OK. I committed it. +# Keyring (defaults): +#ARCHIVE_KEYRING_PACKAGE=debian-archive-keyring +# The path to the keyring file relative to $TDIR/archive-keyring/ +#ARCHIVE_KEYRING_FILE=usr/share/keyrings/debian-archive-keyring.gpg + # By default we use debootstrap --no-check-gpg to find out the minimal set # of packages because there's no reason to not trust the local mirror. But # you can be paranoid and then you need to indicate the keyring to use to # validate the mirror. -#export DEBOOTSTRAP_OPTS=--keyring /usr/share/keyrings/debian-archive-keyring.gpg +#export DEBOOTSTRAP_OPTS=--keyring $TDIR/archive-keyring/$ARCHIVE_KEYRING_FILE This hardcodes TDIR and ARCHIVE_KEYRING_FILE in a second parameter and makes it impossible to do stuff like this (assuming that you have uncommented DEBOOTSTRAP_OPTS): $ . CONF.sh $ export TDIR=/tmp/debian-cd But I guess it's not a big deal. At least it documents the value that you're expected to set if you want to use it. Thanks again! -- Raphaël Hertzog ◈ Debian Developer Get the Debian Administrator's Handbook: → http://debian-handbook.info/get/ -- To UNSUBSCRIBE, email to debian-cd-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130419130419.ga13...@x230-buxy.home.ouaza.com
Bug#703431: Annoying GPG error message
On Tue, 16 Apr 2013, Robert Spencer wrote: And have debian-cd extract the file and pass it around to APT and debootstrap. And then DEBOOTSTRAP_OPTS would default to --no-check-gpg and we would just unset it to activate the GPG check at the debootstrap level. Can you implement this ? Patch file attached. Again it's for debian-cd 3.1.12. Thanks, but there's a small misunderstanding left here: # By default we use debootstrap --no-check-gpg to find out the minimal set # of packages because there's no reason to not trust the local mirror. But # you can be paranoid and then you need to indicate the keyring to use to # validate the mirror. -#export DEBOOTSTRAP_OPTS=--keyring /usr/share/keyrings/debian-archive-keyring.gpg +#export DEBOOTSTRAP_OPTS=--keyring $ARCHIVE_KEYRING_FILE This still requires that the keyring be installed on the system whereas we're already extracting it from the binary package in debian-cd. So I was suggesting to always pass the --keyring option to debootstrap but letting it point to the extracted keyring instead of the system-wide one. And then CONF.sh would only contain something like this: # By default we use debootstrap --no-check-gpg to find out the minimal set # of packages because there's no reason to not trust the local mirror. But # you can be paranoid and then you need to set DEBOOTSTRAP_OPTS to an # empty value and indicate the keyring to use with ARCHIVE_KEYRING_PACKAGE # and ARCHIVE_KEYRING_FILE. #export DEBOOTSTRAP_OPTS=--no-check-gpg Cheers, -- Raphaël Hertzog ◈ Debian Developer Get the Debian Administrator's Handbook: → http://debian-handbook.info/get/ -- To UNSUBSCRIBE, email to debian-cd-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130418121543.ga30...@x230-buxy.home.ouaza.com
Bug#703431: Annoying GPG error message
Hi, On Tue, 19 Mar 2013, Steve McIntyre wrote: On Tue, Mar 19, 2013 at 04:41:08PM +0200, Robert Spencer wrote: There's a long standing error that I've seen even in on-line official Debian CD build logs. W: GPG error: file: squeeze Release: No keyring installed in /home/idms/tmp/apt/squeeze-amd64/apt/trusted.gpg.d/. Attached please find a patch file that fixes the error. Cool, looks good. I've applied this in svn straight away, and it'll make it into the next upload shortly. Robert, would it be possible to add some parameters to use something else than debian-archive-keyring ? debian-cd ought to be usable to build CD images of Debian derivatives and they don't reuse debian-archive-keyring, instead they provide their own keyring package. Thanks in advance! -- Raphaël Hertzog ◈ Debian Developer Get the Debian Administrator's Handbook: → http://debian-handbook.info/get/ -- To UNSUBSCRIBE, email to debian-cd-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130328074232.gd28...@x230-buxy.home.ouaza.com
Re: Debian's new mirror
[ English speaking readers: he's seeking instructions to become a debian-cd mirror, I'm answering here ] Bonjour, pour votre information cette liste est anglophone. Merci d'utiliser l'anglais pour tout message adressé à debian-cd@lists.debian.org On Wed, 08 Jun 2011, deb...@freegnu.net wrote: Je souhaite vous apporter un miroir supplémentaire. J'ai donc comme domaine debian.freegnu.net Comment dois-je récupérer les cd's pour les mettre sur mon mirror? Suivez les instructions de cette page: http://www.debian.org/CD/mirroring/ Cordialement, -- Raphaël Hertzog ◈ Debian Developer Follow my Debian News ▶ http://RaphaelHertzog.com (English) ▶ http://RaphaelHertzog.fr (Français) -- To UNSUBSCRIBE, email to debian-cd-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110609122740.ge12...@rivendell.home.ouaza.com
Re: MBF alert: packages with very long source / .deb filenames
On Fri, 25 Mar 2011, Steve McIntyre wrote: On Fri, Mar 25, 2011 at 12:28:54PM -0400, Joey Hess wrote: Steve McIntyre wrote: There are uses I've heard about, including (apparently quite common) using CDs and DVDs to seed a mirror on a Windows server. If I had to chose between that working, and not needing to worry about filename lengths, I'd choose the latter. We already have arbitrary limits on filename length (~200 bytes or so on RockRidge), even before this. I'm just proposing to lower them for a common use case. Do we really care about supporting *very* long names here? I think so. The package with long names tend to follow a naming policy that sort of imposes the long name... so if we put a too-short limit then we're asking them to make an exception in the naming policy. One approach then would be to omit joliet filenames for the few long packages. This would not even impact your use case above much, since any mirror seeded from files from CDs needs a further sync step. I'd be much happier to not have to special case yet another thing in the CD scripts. That way potentially leads to unforeseen bugs in the future, for very little gain. What happens if you try to put too-long filenames on the CD with Joliet enabled? Does it fail to build? Are there options to rename the files automatically? If it means we have some unexpected filenames for long filenames on Windows, it's not a big deal IMO. Cheers, -- Raphaël Hertzog ◈ Debian Developer Follow my Debian News ▶ http://RaphaelHertzog.com (English) ▶ http://RaphaelHertzog.fr (Français) -- To UNSUBSCRIBE, email to debian-cd-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110326075614.ga29...@rivendell.home.ouaza.com
Re: New artwork for Squeeze CDs
Hi, On Sun, 06 Feb 2011, Ulrich Hansen wrote: I have updated my artwork for Debian CDs. I hope you like it. See: http://ulrich-hansen.de/debian/index.htm It would be great if someone could update the link on the http://www.debian.org/CD/artwork/ page. Done. Just committed to CVS should appear online in a few hours. $ cvs commit ulrich-hansen.de-*.png index.wml /cvs/webwml/webwml/english/CD/artwork/ulrich-hansen.de-squeeze-cd.png,v -- ulrich-hansen.de-squeeze-cd.png initial revision: 1.1 /cvs/webwml/webwml/english/CD/artwork/ulrich-hansen.de-squeeze-dvd.png,v -- ulrich-hansen.de-squeeze-dvd.png initial revision: 1.1 /cvs/webwml/webwml/english/CD/artwork/index.wml,v -- index.wml new revision: 1.40; previous revision: 1.39 Cheers, -- Raphaël Hertzog ◈ Debian Developer Follow my Debian News ▶ http://RaphaelHertzog.com (English) ▶ http://RaphaelHertzog.fr (Français) -- To UNSUBSCRIBE, email to debian-cd-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110312180737.ga3...@rivendell.home.ouaza.com
Re: New artwork for Squeeze CDs
Hello Ulrich, On Sun, 06 Feb 2011, Ulrich Hansen wrote: Congratulations to the Squeeze release!! Thanks! I have updated my artwork for Debian CDs. I hope you like it. Yes, it really looks great! Can you make the sources available so that we can tweak the text and so on? See: http://ulrich-hansen.de/debian/index.htm It would be great if someone could update the link on the http://www.debian.org/CD/artwork/ page. Copying debian-...@lists.debian.org for this. This page needs some clean up, the first link no longer works. :-( I plan to complete the artwork for a greater choice of Debian CDs/DVDs in the next days. I also will transfer the old artwork to refer to Squeeze instead of Lenny. Looking forward for them, feel free to tell us when you put more stuff online. Cheers, -- Raphaël Hertzog ◈ Debian Developer Follow my Debian News ▶ http://RaphaelHertzog.com (English) ▶ http://RaphaelHertzog.fr (Français) -- To UNSUBSCRIBE, email to debian-cd-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110207204457.ga17...@rivendell.home.ouaza.com
Bug#598196: debian-cd: more patches for documentation
On Wed, 29 Sep 2010, Petter Reinholdtsen wrote:
[Karl Goetz]
It was so that both options 'behave the same'. Specifically, both
settings about pulling in dependencies have the same default which
is then overriden by the config file (in the same way). Looking at
the diff again, it looks like i changed recommends instead of
suggests - oops.
It was meant to be
+my $nosuggests = $ENV{'NOSUGGESTS'} || 0;
-my $nosuggests = $ENV{'NOSUGGESTS'} || 1;
hope that explains :)
I believe the build should handle recommends and suggests differently,
as apt will install recommends by defaults but not suggests. Because
of this, I believe it is important for debian-cd to include recommends
on the CD and DVD by default, to make sure installs from the net and
from CD/DVD behave more the same (ie will install the same packages).
+1 from me, I don't undertand/agree with the reasoning of the change and
would prefer that we kept the same good default.
Cheers,
--
Raphaël Hertzog ◈ Debian Developer ◈ [Flattr=20693]
Follow my Debian News ▶ http://RaphaelHertzog.com (English)
▶ http://RaphaelHertzog.fr (Français)
--
To UNSUBSCRIBE, email to debian-cd-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20101007130428.gc10...@rivendell.home.ouaza.com
Re: New cdbuilder server improves Debian infrastructure
On Thu, 01 Apr 2010, Frans Pop wrote: [1] I saw your request to add me to a group, but that's all I know. I tried 'ssh cdimage.debian.org', but that does not work. Try ssh cdbuilder.debian.org, I can log there. Cheers, -- Raphaël Hertzog Like what I do? Sponsor me: http://ouaza.com/wp/2010/01/05/5-years-of-freexian/ My Debian goals: http://ouaza.com/wp/2010/01/09/debian-related-goals-for-2010/ -- To UNSUBSCRIBE, email to debian-cd-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100401062355.gb5...@rivendell
Re: Bug#542241: simple-cdd: Deal better with non-official codenames
On Wed, 16 Sep 2009, Frans Pop wrote: It seems a bit strange to me to have a derived distribution as CD release that's not backed up by it's own archive, and thus mirrors. I'd say that if you want to use different codenames, you should start by creating an archive that has those codenames. We have that. If you have such an archive, it also seems trivial to me to create the needed configuration files (if you like as symlinks to files/dirs for Debian codenames) needed for Debian CD. (I'd recommend using git-svn and creating a branch for the derived distribution.) Well, I don't want to have to maintain a debian-cd fork, I generate images with simple-cdd which in turn uses debian-cd. My feature request is to have simple-cdd create symlinks in the temporary debian-cd directory that it already uses so that the tools/boot/$CODENAME/ scripts that are called actually exist even when $CODENAME is not an official Debian codename. Now, the alternative is to not create the symlinks and have a way to tell debian-cd “well CODENAME is foo, but for boot-enabling scripts, please use those of lenny”. So, IMO debian-cd already has all the functionality needed to support derived distributions using different codenames. Or am I missing something? Yes it has (if you consider normal to have to duplicate the codename specific directories inside it to match your own codename). I think it's a reasonable assumption but still wanted to ask for more opinion. Cheers, -- Raphaël Hertzog -- To UNSUBSCRIBE, email to debian-cd-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Bug#542241: simple-cdd: Deal better with non-official codenames
On Mon, 14 Sep 2009, Vagrant Cascadian wrote: On Tue, Aug 18, 2009 at 05:52:03PM +0200, Raphaël Hertzog wrote: Currently the CODENAME given is used both to select the distribution to download from the mirror and the distribution to create in the local mirror. Given that debian-cd will only do its job properly if the CODENAME is a well known one, we are forced to use official debian codenames even when we are in fact building a derivative distribution. It would be nice if simple-cdd could be somewhat more intelligent in that regard. I suggest to check that debian-cd/data/$CODENAME, debian-cd/tools/$CODENAME and debian-cd/tools/boot/$CODENAME exists and if not to create them as symlinks pointing to $debian_cd_rules_like_dist (you can find a better name maybe, it's meant to be a new variable that selects the Debian distribution whose rules we want to re-use when building the CD). if that's really all it would take, it probably wouldn't be too hard to implement in simple-cdd. though i would rather see something like this implemented in debian-cd directly, unless there's a compelling reason not to. Well, as a debian-cd co-maintainer, I thought about this too, but I didn't like the idea very much. It would mean 2 supplementary variables that should be used instead of $CODENAME or $DI_CODENAME in various places and that should default to $CODENAME $DI_CODENAME. Ccing debian-cd@lists.debian.org to get the input of Steve (and maybe Frans) but for now I think that simple-cdd is a good place to implement this. I consider the fact that we can put supplementary directories in those places as a relatively official interface of debian-cd. Cheers, -- Raphaël Hertzog -- To UNSUBSCRIBE, email to debian-cd-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#518145: Missing dependencies on official Lenny installation CDs
severity 518145 normal thanks On Wed, 04 Mar 2009, Frans Pop wrote: On Wednesday 04 March 2009, Julian Andres Klode wrote: The package gnome depends on gnome-app-install. gnome is located on CD1, gnome-app-install on CD2. This is more a feature than a bug. I.e, it's just a consequence of how packages are added to images and does not cause any problems during installation. This is definitely not a feature. This is a regression compared to what list2cd used to do. While it might not have a big practical impact, it is a real bug in the application logic. Cheers, -- Raphaël Hertzog Contribuez à Debian et gagnez un cahier de l'admin Debian Lenny : http://www.ouaza.com/wp/2009/03/02/contribuer-a-debian-gagner-un-livre/ -- To UNSUBSCRIBE, email to debian-cd-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#497270: debian-cd: includes embedded copies of bootloaders
On Sun, 31 Aug 2008, Daniel Baumann wrote: Aurelien Jarno wrote: Bug#496869 is a release blocker. We don't want to produce d-i images that do not work on some machines. agreed, but that's not the point. to fulfil the license /for that specific version/ of syslinux embedded in debian-cd, you need to include the sources of /that specific version/ of syslinux. Would it be enough to put the sources of that specific version of syslinux somewhere on cdimage.debian.org and document that ? Once that this is done, we can reduce the severity of this bug to wishlist. I somewhat agree that we should extract what we need from the syslinux package itself but it's not something that is very practical to implement and IIRC we had quite some history with syslinux being broken in a few cases that justified to keep control over what syslinux version we were using. Sledge, what do you think ? Cheers, -- Raphaël Hertzog Le best-seller français mis à jour pour Debian Etch : http://www.ouaza.com/livre/admin-debian/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: debian.fr outdated (was: hyperlink down)
On Sat, 03 Nov 2007, Simon Paillard wrote: On Sat, Nov 03, 2007 at 07:18:26PM +0100, Richard Atterer wrote: On Sat, Nov 03, 2007 at 06:44:07PM +0100, Baptiste COLLARD wrote: I'm french and links on this web site are dead : http://debian.fr/CD/netinst/ The master page http://www.debian.org/CD/netinst/index.fr.html is up to date. It seems that the debian.fr mirror is out of date. Looks like it is not a simple mirror of the HTML data, as it uses some redirect.php link for the download links. Who runs debian.fr? debian.fr is *NOT* an official mirror, and is operated by someone not affiliated to Debian. Many others issues on debian.fr (like /doc/ in error) have already been reported. I've sent an email to the contact of the domain debian.fr, without any result. IIRC debian.fr is not a web-mirror, it's a simple frame redirecting to www.fr.debian.org Cheers, -- Raphaël Hertzog Premier livre français sur Debian GNU/Linux : http://www.ouaza.com/livre/admin-debian/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Excluding packages
On Sat, 02 Jun 2007, Joey Schulze wrote: Is there a commandline option like --exclude-from file that will exclude all packages mentioned in file and packages depending on them from the build process? If not, would it be possible to develop such an option eventually? We always had the possibility to exclude packages from generated CD. It may result in the exclusion of other packages that depend on the excluded package however. Check out the README in the SVN and the CONF.sh file. Options are defined as environement variables in debian-cd. Cheers, -- Raphaël Hertzog Premier livre français sur Debian GNU/Linux : http://www.ouaza.com/livre/admin-debian/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re:
On Wed, 09 May 2007, Brian Morris wrote: boy you are one mean bureaucratic honcho. where do you get off talking down to people like that ? [...] (you are not courteous in your reply. Isn't there some possible alternative ?) Sorry to have to state it, but Frans has just stated some facts and explained the situation. He hasn't done anything bad. Your answer however is very impolite. :-( it loooks to me like testing is there. I think you are in error about that, or else there is some dispute. There's no http://ftp.fr.debian.org/debian/dists/testing/main/binary-m68k/ The m68k architecture is not currently in testing. That's a fact. additionally there is unstable, and there is etch-m68k on the mirrors in the pool directories. Right. we should have cd-images for all of those. no, we should We should... however we're volunteers and you're welcome to help if you're not happy with the current situation. additionally it should be no secret if I wanted to make my own templates. There's no secrets. Check out the debian-cd package, it contains everything needed to build yourself updated CD images. it seems to me you are blocking the possibility of reinstatement of the port by not providing the means to create images. That's wrong. We're not blocking anything. m68k has many other problems to solve before CD images are a real problem. That said, maybe that Steve can build weely images based on sid for m68k. Cheers, -- Raphaël Hertzog Premier livre français sur Debian GNU/Linux : http://www.ouaza.com/livre/admin-debian/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: too many CD ISOs
Hi, On Tue, 17 Apr 2007, Frans Pop wrote: On Tuesday 17 April 2007 19:42, Michael Loftis wrote: It's becoming prohibitively expensive for mirrors to maintain a debian mirror because of the huge amount of storage required by all of the CD/DVD images. This has been brought up before by mirror maintainers. IMH(umble)O Jigdo should be pushed much much harder since it can generate the entire CD or DVD set for a given arch off a normal repo pool, and those have to be kept around anyway. That is an idea. Maybe only publish the lower .iso's (exactly how many would need to be determined) but keep all jigdo's around. CD vendors can probably be expected to be able to generate iso's using jigdo. While I sympathize with the idea, please keep in mind that some big mirrors prefer that users download images via ISO than via jigdo. So the most popular images should really be available as ISO. Reason: it's much more effective for them when users download an ISO than when they use jigdo. For example the ftp.fr.debian.org admin explained me that they were limited by the disk seek and not by the bandwith used by the users. Cheers, -- Raphaël Hertzog Premier livre français sur Debian GNU/Linux : http://www.ouaza.com/livre/admin-debian/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#413506: strange error from make_disc_trees.pl
Hello, On Tue, 06 Mar 2007, Steffen Joeris wrote: Hi mates The original bug seems to be fixed, thanks a lot. However now I get another error, I attached the build log for that one. The problem seems to be in add_packages this time with the call of -gzclose(); You have many strange messages in your build. Please provide the CONF.sh that you're using because it looks like it's borked: patching file tasks/exclude-etch ./build.sh: line 1: ARCHES: command not found This is the first error that should not happen. And you have many reference of bad shell script in the log: ./build.sh: line 1: ARCHES: command not found Using CONF from /home/builder/src/debian-edu/src/build/CD-administrator/CONF-etch-test.sh /bin/sh: line 1: [: too many arguments Cleaning the build directory /bin/sh: line 1: [: too many arguments Please fix your CONF.sh / CONF-etch-test.sh and try again. That file changed a lot with debian-cd 3.0. Use of uninitialized value in string eq at /home/builder/src/debian-edu/src/build/CD-administrator/debian-cd/tools/make_disc_trees.pl line 371. This means that your CONF.sh doesn't provide DISKTYPE. Use of uninitialized value in scalar assignment at /home/builder/src/debian-edu/src/build/CD-administrator/debian-cd/tools/make_disc_trees.pl line 392. Use of uninitialized value in scalar assignment at /home/builder/src/debian-edu/src/build/CD-administrator/debian-cd/tools/make_disc_trees.pl line 393. Use of uninitialized value in subtraction (-) at /home/builder/src/debian-edu/src/build/CD-administrator/debian-cd/tools/make_disc_trees.pl line 397. Use of uninitialized value in concatenation (.) or string at /home/builder/src/debian-edu/src/build/CD-administrator/debian-cd/tools/make_disc_trees.pl line 108. Use of uninitialized value in string eq at /home/builder/src/debian-edu/src/build/CD-administrator/debian-cd/tools/make_disc_trees.pl line 371, INLIST line 1. This is consequences from the previous error. cp: cannot stat `cdrom/2.6/einitrd.gz': No such file or directory Strange... is that debian-edu specific ? Please investigate a bit yourself as what I see here is not a debian-cd problem but a problem of your configuration. Cheers, -- Raphaël Hertzog Premier livre français sur Debian GNU/Linux : http://www.ouaza.com/livre/admin-debian/
Bug#413506: strange error from make_disc_trees.pl
tag 413506 + patch pending
severity 413506 serious
thanks
On Tue, 06 Mar 2007, Steffen Joeris wrote:
Placing packages into image 1
Nested quantifiers in regex; marked by -- HERE in m/^g++ -- HERE $/
at
/home/builder/src/debian-edu/src/build/CD-administrator/debian-cd/tools/make_disc_trees.pl
line 246.
make: *** [image-trees] Error 9
I am not quite sure what is going mad there and it is probably too late
for me to do debugging, sorry.
Please try this patch (or svn update your debian-cd tree) and confirm me
that it fixes your problem.
I already committed it to debian-cd's svn.
I leave the severity at RC level because we need to make sure that
debian-cd 3.0.1 (unreleased) gets into etch, it has many fixes used for
generating the real official Debian CDs and we want this into etch.
I'll leave the upload up to Steve.
Regards,
--
Raphaël Hertzog
Premier livre français sur Debian GNU/Linux :
http://www.ouaza.com/livre/admin-debian/
Index: tools/make_disc_trees.pl
===
--- tools/make_disc_trees.pl (révision 1372)
+++ tools/make_disc_trees.pl (copie de travail)
@@ -159,7 +159,7 @@
foreach my $reinclude_pkg (@excluded_package_list) {
my ($arch, $pkgname) = split /:/, $reinclude_pkg;
foreach my $entry (@unexclude_packages) {
-if (($pkgname =~ /^$entry$/m)) {
+if (($pkgname =~ /^\Q$entry\E$/m)) {
print LOG Re-including $reinclude_pkg due to match on \\^$entry\$\\n;
$guess_size = int($hfs_mult * add_packages($cddir, $reinclude_pkg));
$size += $guess_size;
@@ -243,7 +243,7 @@
my $should_exclude = 0;
foreach my $entry (@exclude_packages) {
- if (($pkgname =~ /^$entry$/m)) {
+ if (($pkgname =~ /^\Q$entry\E$/m)) {
print LOG Excluding $pkg due to match on \\^$entry\$\\n;
$should_exclude++;
}
@@ -254,7 +254,7 @@
# exclude the package at the same time. If so, complain and
# bail out
foreach my $entry (@unexclude_packages) {
-if (($pkgname =~ /^$entry$/m)) {
+if (($pkgname =~ /^\Q$entry\E$/m)) {
print LOG But ALSO asked to unexclude $pkg due to match on \\^$entry\$\\n;
print LOG Make your mind up! Bailing out...\n;
die Incompatible exclude/unexclude entries for $pkg...\n;
Bug#413510: get_diskusage.pl is missing
Hi,
On Tue, 06 Mar 2007, Steffen Joeris wrote:
I am a bit surprised of why the get_diskusage.pl script was dropped? Maybe I
am missing something, in this case sorry for the noise, but I could not find
any information about it in the changelog or in the svn log.
I attached the script again and a small patch which I applied for the new
debian-cd version, can you maybe consider readding it or is it obsolete?
No idea for this, I'll let Steve answer.
-$ENV{TDIR}/$ENV{CODENAME}-$ENV{ARCH}/log.list2cds);
+$ENV{TDIR}/$ENV{CODENAME}-$ENV{ARCHES}/log.list2cds);
I doubt that this patch would work with debian-cd 3.0.
$ARCHES is a space separated list of arch and the file log.list2cds is now
in $TDIR/$CODENAME/ IIRC.
Cheers,
--
Raphaël Hertzog
Premier livre français sur Debian GNU/Linux :
http://www.ouaza.com/livre/admin-debian/
Re: [PATCH 6/6] Before resolve dependencies, add all packages listed on the task
On Thu, 08 Feb 2007, Otavio Salvador wrote: Steve McIntyre [EMAIL PROTECTED] writes: On Tue, Feb 06, 2007 at 08:45:37AM -0200, Otavio Salvador wrote: From: Otavio Salvador [EMAIL PROTECTED] Signed-off-by: Otavio Salvador [EMAIL PROTECTED] Hmmm. I'm not convinced by this one, either. It's a major decision to change dependency ordering, and we expect dependency resolution to work. What's the point of including packages in a task before all the dependencies? Current code do not check the prefered packages of task before adding a dependency so, for example: You're right this is a problem. But your approach doesn't look as the good solution to that problem... you should keep the full task on the side (ie a separate variable and not directly include it) and when you encounter an OR depends, then check if one the components can be taken from the task instead of arbitrarily. Otherwise I fear you loose the fact that CD1 can be used independantly of CD2, and so on... Cheers, -- Raphaël Hertzog Premier livre français sur Debian GNU/Linux : http://www.ouaza.com/livre/admin-debian/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#283137: Problem when booting from second CD
Le dimanche 28 novembre 2004 à 22:48 +0100, Santiago Garcia Mantinan a écrit : Proably because there are no udebs at all, let alone kernel udebs, on the second CD. So I'm reassigning this to debian-cd; if the second full CD is intended to be bootable, it needs to have the d-i udebs on it. :-??? Does this seem reasonable? I mean, isn't it more reasonable to inform the user of this problem and ask him to change the cd and introduce the one with the udebs on it rather than having the udebs on each bootable cd? I agree with you. Responding to Joey Hess : What's the point of booting from the second CD? Will it use syslinux instead of isolinux for old systems that cannot handle isolinux? Yes, that was the idea of the other bootable images... keep syslinux for machines were isolinux is failing. I'm against copying udebs on all CD, so if d-i doesn't support the suggestion above we'll just remove the possibility to boot on other CD than the first. Cheers, -- Raphaël Hertzog Premier livre français sur Debian GNU/Linux : http://www.ouaza.com/livre/admin-debian/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Calculation of cd sizes implemented and tested, should I commit?
Quoting Santiago Garcia Mantinan: Hi! It is two weeks since we started using at gluck the code I made to try to estimate the sizes of the cd parts that debian-cd was not controling, it seems to be working ok, so I was wondering if I should commit it :-? Of course ! Please go for it. Cheers, -- Raphaël Hertzog -+- http://www.ouaza.com Formation Linux et logiciel libre : http://www.logidee.com Earn money with free software: http://www.geniustrader.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: debian-cd upload needed soon
Quoting Steve McIntyre: If we want to get a vaguely useable version of debian-cd into sarge for the release, we need to do it soon. I'm about to checkin the couple of tiny changes that I have locally on normal debian-cd. If anybody else has stuff to go in, do it ASAP please. I'm planning to do a medium-urgency upload tomorrow unless I hear otherwise... Thanks for taking care of that, Steve ! Just don't forget to tag when you do the final commit. Cheers, -- Raphaël Hertzog -+- http://www.ouaza.com Formation Linux et logiciel libre : http://www.logidee.com Earn money with free software: http://www.geniustrader.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: JTE 1.3 debian-cd test branch
Quoting Steve McIntyre: I'd like to create a branch in debian-cd CVS to check this lot in so other people can test this out - comments? I see no problem with that, but maybe it would be even better if you could make the debian-cd code generic ? if mkisofs --support-jigdo; then ... else ... fi Isn't something like that possible ? Cheers, -- Raphaël Hertzog -+- http://www.ouaza.com Formation Linux et logiciel libre : http://www.logidee.com Earn money with free software: http://www.geniustrader.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Debian_sarge task missing debian-installer+kernel?
Quoting Santiago Garcia Mantinan: that after seing this he had found that debian-installer+kernel was not included in the Debian_sarge task. I believe that debian-installer+kernel should be part of Debian_sarge, unless there can be a problem if any package part of debian-installer+kernel is already in Debian_sarge, I have included debian-installer+kernel from Debian_sarge at gluck, for testing purposes, but I'd like to know opinions on this from other people, is this wrong? I think you're right to include it. Sarge is meant to be released with debian-installer so we need to make sure that we have everything related to it. Cheers, -- Raphaël Hertzog -+- http://www.ouaza.com Formation Linux et logiciel libre : http://www.logidee.com Earn money with free software: http://www.geniustrader.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: TRANS.TBL on CDs
Quoting Steve McIntyre: Guys, We're still putting TRANS.TBL files in every directory on the CDs. Surely by now we can just lose them? They're going to be wasting space on all the images (especially important on netinst and business card), and I'd bet that we're not bothered about supporting people renaming files by hand on DOS machines any more...? Agreed. Feel free to commit a fix. Cheers, -- Raphaël Hertzog -+- http://www.ouaza.com Formation Linux et logiciel libre : http://www.logidee.com Earn money with free software: http://www.geniustrader.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: debian-cd broken?
Quoting Jan Kesten: I had problems building sarge cd images from my local mirror yesterday and today. I didn't change anything and used the latest cvs version of debian-cd. Can you show the CONF.sh file that you're using ? It looks like there's a problem with your EXCLUDE variable ... in the target $(BDIR)/rawlist-exclude the test doesn't fail and the perl command is launched without a parameter when it needs one and so stays blocked waiting on standard input : if [ -n ]; then \ perl -npe 's/[EMAIL PROTECTED]@/i386/g' | \ cpp -nostdinc -nostdinc++ -P -undef -D ARCH=i386 -D ARCH_i386 \ -U i386 -U i386 -U linux -U unix \ -DFORCENONUSONCD1=0 \ -I /mirror2/debian-cd/tasks -I /mirror2/tmp/sarge-i386 - - /mirror2/tmp/sarge-i386/rawlist-exclude; \ fi make: *** Deleting file `/mirror2/tmp/sarge-i386/rawlist-exclude' make: *** [/mirror2/tmp/sarge-i386/rawlist-exclude] Interrupt otavio is responsible for that change, maybe he can sort it out ? :) I bet that we could replace -n with -e and have a better test. Or we should at least add quotes around $(EXCLUDE) in the test itself. Cheers, -- Raphaël Hertzog -+- http://www.ouaza.com Formation Linux et logiciel libre : http://www.logidee.com Earn money with free software: http://www.geniustrader.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Dirty workaround for size reduction in the netinst cds
Quoting Santiago Garcia Mantinan: The problem was how to translate this into debian-cd code, and I did so at gluck by hinting the list, I mean that I added a couple of good hints at the beginning of the list so that the problematic dependencies that were throwing a lot of unwanted stuff in the cds get covered with this hints and thus we avoid that extra stuff. I know this is a dirty thing, thats why I have commited the stuff for having the 2.6 in the images but not this part of the code, which only aims size reduction on the netinst cd, and I'm posting it here asking for comments on it and if I should commit it or not. Please commit it because otherwise nobody else will be able to generate nice netinst CDs but you're right, it's an ugly fix. That's why you have to comment it better so that we don't forget about this hack and so that we have a chance to make a better fix when someone has the time needed. Include a pointer to the mail archives of this discussion in the comment... Cheers, -- Raphaël Hertzog -+- http://www.ouaza.com Formation Linux et logiciel libre : http://www.logidee.com Earn money with free software: http://www.geniustrader.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Syncing my stuff at gluck with cvs, or asking for sugestions.
Quoting Santiago Garcia Mantinan: We have new sparc configs, same files we used to have at data/sparc/ I have placed these files at data/sarge/sparc to avoid breaking woody and other older distros, but I don't know what to do with the old dir, is it ok to leave it like it is now? I'd say yes. Go ahead. Cheers, -- Raphaël Hertzog -+- http://www.ouaza.com Formation Linux et logiciel libre : http://www.logidee.com Earn money with free software: http://www.geniustrader.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#242337: module-init-tools-udeb breaks 2.4.x debian-installer, MUST be optional priority
Quoting Joey Hess: module-init-tools-udeb is listed in the d-i netinst ISO image as Priority: standard, despite being listed in the official Packages file from ftp.debian.org as Priority: extra. This breaks the debian installer, thus the severity of this bug report. debian-cd uses the override files when they are available ... $ ls /scratch/mirror/debian/indices/*debian-installer* /scratch/mirror/debian/indices/override.sid.main.debian-installer.gz But we only have an override file for sid. Thus when we generate sarge images, we have wrong priorities. If this fix to debian-cd cannot be done immediatly, please tell me. I know that we have some other udebs that have their priority currently overrided, and if debian-cd is not going to be fixed, I will need to make a practice of checking over all such udebs for problems. I don't think that anything needs to be fixed in debian-cd, you'd better correct everything on ftpmaster's side. Cheers, -- Raphaël Hertzog -+- http://www.ouaza.com Formation Linux et logiciel libre : http://www.logidee.com Earn money with free software: http://www.geniustrader.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Contents-i386.gz files
Quoting Steve McIntyre: About 1/5th of the sarge businesscard image, and a fair bit of the netinst iso are taken up by the Contents-i386.gz files. I propose that these be dropped from these smaller images. As I understand it, the That makes obvious sense, yes. Agreed. Comitted something that should do it. I've also thought that it might be worthwhile to remove the debian-keyring.tar.gz file (also 7 mb) from these images. However, I do not really know how that file is intended to be used. I'm not sure myself. Maybe things like debsig-verify will use the keyring files in there to validate the signatures of the packages. Even so, on a small image I'd agree that's a lot of space to be taking up. IIRC, that file has never been integrated explicititely. It's just that we include everything from the doc directory on the mirror. So we can safely remove it. I committed changes to remove that file (on all kind of CD). Cheers, -- Raphaël Hertzog -+- http://www.ouaza.com Formation Linux et logiciel libre : http://www.logidee.com Earn money with free software: http://www.geniustrader.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: release 2.2.17
Quoting Joey Hess: Maybe it would be good to release debian-cd 2.2.17 soon? It has many changes for d-i and sarge is getting close to a release. Done. Cheers, -- Raphaël Hertzog -+- http://www.ouaza.com Formation Linux et logiciel libre : http://www.logidee.com Earn money with free software: http://www.geniustrader.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: release 2.2.17
Quoting Joey Hess: Maybe it would be good to release debian-cd 2.2.17 soon? It has many changes for d-i and sarge is getting close to a release. Done. Cheers, -- Raphaël Hertzog -+- http://www.ouaza.com Formation Linux et logiciel libre : http://www.logidee.com Earn money with free software: http://www.geniustrader.org
Re: Not usefull kernel images take all first Debian sarge CD :(
Quoting Adam Majer: I agree. This is crazzy. But how the heck do you get this? kernel-image-2.4.22-xfs - ~22 Mb kernel-image-2.4.22-i386 - ~78 Mb [...] So even if you had 8 kernels, that would be 80M. To occupy most of the disk, I think you'll need more than 25 kernels.. We have many kernels, here's the list that I excluded yesterday evening: kernel-image-2.6.0-test11-1-386 kernel-image-2.6.0-test9-1-386 kernel-image-2.4.20-3-386 kernel-image-2.4.20-3-586tsc kernel-image-2.4.20-3-686 kernel-image-2.4.20-3-686-smp kernel-image-2.4.20-3-k6 kernel-image-2.4.20-3-k7 kernel-image-2.4.20-3-k7-smp kernel-image-2.4.21-5-386 kernel-image-2.4.21-5-586tsc kernel-image-2.4.21-5-686 kernel-image-2.4.21-5-686-smp kernel-image-2.4.21-5-k6 kernel-image-2.4.21-5-k7 kernel-image-2.4.21-5-k7-smp kernel-image-2.4.22-1-386 kernel-image-2.4.22-1-586tsc kernel-image-2.4.22-1-686 kernel-image-2.4.22-1-686-smp kernel-image-2.4.22-1-k6 kernel-image-2.4.22-1-k7 kernel-image-2.4.22-1-k7-smp kernel-image-2.4.23-1-386 kernel-image-2.4.23-1-586tsc kernel-image-2.4.23-1-686 kernel-image-2.4.23-1-686-smp kernel-image-2.4.23-1-k6 kernel-image-2.4.23-1-k7 kernel-image-2.4.23-1-k7-smp That makes ~30 kernels. I kept 2.4.24* and 2.6.0-1*. Anyway, the number of kernel on the CDs should be reduced anyway. We should only have the i386 version and let people build their own variants if they choose to (or DL from mirrors). No, IIRC debian-installer installs the good one depending on /proc/cpu. So we'd better keep all the variants on the first CD. But we should definitely stick to one version of the kernel. Cheers, -- Raphaël Hertzog -+- http://www.ouaza.com Formation Linux et logiciel libre : http://www.logidee.com Earn money with free software: http://www.geniustrader.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Not usefull kernel images take all first Debian sarge CD :(
[ removing debian-devel which is not really necessary but added debian-boot ] Quoting Goswin von Brederlow: Test and pre kernels could be kept in sid exclusively. They could, but for the moment they aren't and I have to live up with that. :) For non i386 the list of kernels differs widely between archs. Yes I address the problem only for i386. But I bet the problem is less serious for other arches because they don't have so frequent uploads of kernels, aren't they ? The first CD should have only one version, the one used in D-I, but as many flavours as possible without overcrowding. All other versions could be on later CDs. People might want a 2.2.x kernel or need a 2.6.0 kernel for their hardware. debian-installer doesn't use 2.4.24 yet, does that mean that I broke d-i by excluding the other kernels from the CDs ? Is that's true, couldn't d-i be a bit more clueful and install the latest kernel-image-2.4.x package that it finds ? Cheers, -- Raphaël Hertzog -+- http://www.ouaza.com Formation Linux et logiciel libre : http://www.logidee.com Earn money with free software: http://www.geniustrader.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Not usefull kernel images take all first Debian sarge CD :(
Hi, Quoting AKL. Mantas Kriauciunas: week I'm downloading first 3 CD's at work and upgrading my work and home Linux system's. And I noticed, that there are fewer and fewer usefull packages in first Debian CD's :( My patience is running out with latest version of Official debian sarge CD's - now various kernel images uses about 480 MB in first Sarge CD and about 100 Mb in second CD. Because of this there are only 155 MB of other packages in first CD :( Right, I noticed that yesterday evening as well. It has been a long time since I last generated a few images myself... This I just corrected that by adding the corresponding kernel images to the tasks/exclude-sarge file. I only kept 2.4.24-1 and 2.6.0-1 (2.6.1 doesn't seem to be in testing yet). Please understand that the process of selecting which packages goes on which CD can't be 100% automatic thus humans have to show how things are going and give appropriate overrides/hints to debian-cd. Because of the kernel images CD image 1 had only 340 packages instead of about 1000... BTW, I also suggest to use NORECOMMENDS=1 because otherwise you get too many packages included just because of a Recommends on a virtual package (this includes all the packages that provide the given virtual package). There's no need to file a bug against debian-cd, the shortcoming is well known, but sending mails like the one you did does help when you notice that an override would be welcome. Manty, can you update debian-cd on gluck so that images are better ? Cheers, -- Raphaël Hertzog -+- http://www.ouaza.com Formation Linux et logiciel libre : http://www.logidee.com Earn money with free software: http://www.geniustrader.org
Re: Not usefull kernel images take all first Debian sarge CD :(
Quoting Adam Majer: I agree. This is crazzy. But how the heck do you get this? kernel-image-2.4.22-xfs - ~22 Mb kernel-image-2.4.22-i386 - ~78 Mb [...] So even if you had 8 kernels, that would be 80M. To occupy most of the disk, I think you'll need more than 25 kernels.. We have many kernels, here's the list that I excluded yesterday evening: kernel-image-2.6.0-test11-1-386 kernel-image-2.6.0-test9-1-386 kernel-image-2.4.20-3-386 kernel-image-2.4.20-3-586tsc kernel-image-2.4.20-3-686 kernel-image-2.4.20-3-686-smp kernel-image-2.4.20-3-k6 kernel-image-2.4.20-3-k7 kernel-image-2.4.20-3-k7-smp kernel-image-2.4.21-5-386 kernel-image-2.4.21-5-586tsc kernel-image-2.4.21-5-686 kernel-image-2.4.21-5-686-smp kernel-image-2.4.21-5-k6 kernel-image-2.4.21-5-k7 kernel-image-2.4.21-5-k7-smp kernel-image-2.4.22-1-386 kernel-image-2.4.22-1-586tsc kernel-image-2.4.22-1-686 kernel-image-2.4.22-1-686-smp kernel-image-2.4.22-1-k6 kernel-image-2.4.22-1-k7 kernel-image-2.4.22-1-k7-smp kernel-image-2.4.23-1-386 kernel-image-2.4.23-1-586tsc kernel-image-2.4.23-1-686 kernel-image-2.4.23-1-686-smp kernel-image-2.4.23-1-k6 kernel-image-2.4.23-1-k7 kernel-image-2.4.23-1-k7-smp That makes ~30 kernels. I kept 2.4.24* and 2.6.0-1*. Anyway, the number of kernel on the CDs should be reduced anyway. We should only have the i386 version and let people build their own variants if they choose to (or DL from mirrors). No, IIRC debian-installer installs the good one depending on /proc/cpu. So we'd better keep all the variants on the first CD. But we should definitely stick to one version of the kernel. Cheers, -- Raphaël Hertzog -+- http://www.ouaza.com Formation Linux et logiciel libre : http://www.logidee.com Earn money with free software: http://www.geniustrader.org
Re: Not usefull kernel images take all first Debian sarge CD :(
[ removing debian-devel which is not really necessary but added debian-boot ] Quoting Goswin von Brederlow: Test and pre kernels could be kept in sid exclusively. They could, but for the moment they aren't and I have to live up with that. :) For non i386 the list of kernels differs widely between archs. Yes I address the problem only for i386. But I bet the problem is less serious for other arches because they don't have so frequent uploads of kernels, aren't they ? The first CD should have only one version, the one used in D-I, but as many flavours as possible without overcrowding. All other versions could be on later CDs. People might want a 2.2.x kernel or need a 2.6.0 kernel for their hardware. debian-installer doesn't use 2.4.24 yet, does that mean that I broke d-i by excluding the other kernels from the CDs ? Is that's true, couldn't d-i be a bit more clueful and install the latest kernel-image-2.4.x package that it finds ? Cheers, -- Raphaël Hertzog -+- http://www.ouaza.com Formation Linux et logiciel libre : http://www.logidee.com Earn money with free software: http://www.geniustrader.org
Subversion repository
Hello everyone, I just created a subversion repository on svn.debian.org for debian-cd. It will be used for the planned rewrite of debian-cd. It's mainly empty for now (it only contains the design.txt file). $ svn co svn+ssh://svn.debian.org/svn/debian-cd/debian-cd/trunk debian-cd If you want write access to this repository, you need to ask me so that I add you to the debian-cd project on alioth.debian.org. This subversion repository can also be used to host other related projects if needed (I'm thinking to jigdo for example). Regards, -- Raphaël Hertzog -+- http://www.ouaza.com Formation Linux et logiciel libre : http://www.logidee.com Earn money with free software: http://www.geniustrader.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Subversion repository
Hello everyone, I just created a subversion repository on svn.debian.org for debian-cd. It will be used for the planned rewrite of debian-cd. It's mainly empty for now (it only contains the design.txt file). $ svn co svn+ssh://svn.debian.org/svn/debian-cd/debian-cd/trunk debian-cd If you want write access to this repository, you need to ask me so that I add you to the debian-cd project on alioth.debian.org. This subversion repository can also be used to host other related projects if needed (I'm thinking to jigdo for example). Regards, -- Raphaël Hertzog -+- http://www.ouaza.com Formation Linux et logiciel libre : http://www.logidee.com Earn money with free software: http://www.geniustrader.org
Re: Status of the cd building (NEW: bootable cd images for hppa)
Le Sat, Jan 17, 2004 at 05:22:06PM +0100, Santiago Garcia Mantinan écrivait: Well, aside all that, I'm thinking in how could I reschedule the full cd set and dvd set builds, as now it takes really long to build and I cannot build all cds in the same day like we used to do. So I'm wondering... should I spread the build throughout the week? or would it be better for gluck if I could build the most each day and have the machine building cds all day long during 3 or 4 days? Do not generate full CD set, nobody is downloading them isn't it ? Generate daily netinst businesscard CD for all arches. Full CD and DVD can be done once a week. And even for that I'm sure we could do only the 3 first CD. Just my 2¢, feel free to decide whatever please you better. Cheers, -- Raphaël Hertzog -+- http://www.ouaza.com Formation Linux et logiciel libre : http://www.logidee.com Earn money with free software: http://www.geniustrader.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Status of the cd building (NEW: bootable cd images for hppa)
Le Sat, Jan 17, 2004 at 05:22:06PM +0100, Santiago Garcia Mantinan écrivait: Well, aside all that, I'm thinking in how could I reschedule the full cd set and dvd set builds, as now it takes really long to build and I cannot build all cds in the same day like we used to do. So I'm wondering... should I spread the build throughout the week? or would it be better for gluck if I could build the most each day and have the machine building cds all day long during 3 or 4 days? Do not generate full CD set, nobody is downloading them isn't it ? Generate daily netinst businesscard CD for all arches. Full CD and DVD can be done once a week. And even for that I'm sure we could do only the 3 first CD. Just my 2¢, feel free to decide whatever please you better. Cheers, -- Raphaël Hertzog -+- http://www.ouaza.com Formation Linux et logiciel libre : http://www.logidee.com Earn money with free software: http://www.geniustrader.org
[licquia@progeny.com: Progeny picax: Replacement for debian-cd]
Hello, FYI, this has been posted to -devel and -boot. It concerns a possible replacement of debian-cd. I haven't yet looked at it. Feel free to try it out and make a review on this list, I'd be interested in user feedback and I'm sure Jeff would be interested in it as well. Cheers, -- Raphaël Hertzog -+- http://www.ouaza.com Formation Linux et logiciel libre : http://www.logidee.com Earn money with free software: http://www.geniustrader.org ---BeginMessage--- It's been brought to my attention that there's some dissatisfaction with debian-cd within Debian, that some reengineering may need to happen, and that such reengineering may not be able to happen soon. Given that, I thought it would be good to alert Debian to the presence of an alternative. Progeny has had some struggles with debian-cd also. When we started work on Anaconda for Debian, we decided against using debian-cd for it, and begun work on an alternative. The result is called picax (for Progeny Install Creator and Archive eXtractor; if you think the name is horrid, you didn't hear some of the other suggestions). We've been using it to make our Anaconda CDs, and it's worked well for us so far. Picax is written in Python. At its most basic level, it splits apt repositories into parts, either by number of parts or maximum part size. It can write installers to the parts via a modular extension mechanism; the mechanism works to the extent that we have placed all anaconda-specific logic in anaconda and kept it out of picax. It can create source media four ways: separate (completely separate source and binary parts, just like debian-cd), immediate (the last binary media is also the first source media), mixed (each of the media contains all the source for each binary on it), or none. Package ordering is handled via order files, debootstrap, and/or asking the installer for important packages; it is also apt-aware. As far as I can tell, it should be architecture-independent, and even cross-architecture, although this has not been tested. Picax is still very new, and I expect that there will be problems should Debian decide to switch to it. But I expect these problems should be easy to solve. In particular, I've created aptable media for three different Debian-based distributions, and working Anaconda install media for two of those, including sarge. To make picax useful for Debian, a debian-installer module would need to be written. Writing an installer module for picax shouldn't be too difficult; it amounts to a Python module with a particular API, which picax calls at the appropriate times. You can see a working example in anaconda; see http://platform.progeny.com/anaconda for details. I haven't uploaded it yet because it lacked the source features until very recently, but I will be uploading it very soon now that those are done and tested. In the meantime, you can get picax from Progeny's Subversion server: svn checkout svn://svn.progeny.com/anaconda/picax/trunk The package architecture is mature, so you should be able to build packages from the above in the usual way. In none of this do I wish to impugn the good name of Raphael Hertzog or of his creation, which has served Debian well thus far. Nor do I wish to impose my preferred solution upon Debian. It may be that fixing debian-cd is the best course of action for Debian to take. But I think picax could be a very useful replacement, and I wanted to ensure it was considered. Whatever Debian decides, picax fills an important niche at Progeny, and will continue to be useful there. Picax development is discussed on the [EMAIL PROTECTED] list (see platform.progeny.com for more details), so please CC followup discussion there, at least. Suggestions and concerns are welcome. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] ---End Message---
Design of new debian-cd
Hello everybody, I took a few notes yesterday everning about how I would see the build of an image with a rewrite of debian-cd ... it's in the text file attached. Comments are welcome (as well as patch if you feel the need to extend what I wrote) ! Cheers, -- Raphaël Hertzog -+- http://www.ouaza.com Formation Linux et logiciel libre : http://www.logidee.com Earn money with free software: http://www.geniustrader.org DESIGN OF A NEW DEBIAN-CD Process of building a set of ISO 1. Setup a build directory This temp tree will be self-hosting. It will contain everything related to that CD set and its build for one arch : - the configuration selected (having it only in environment variables is not good, it causes confusion and is a risk of having an old config conflict with the new one currently used if all variables are not reset) - the list of packages to include (still generated from profile like it is now) - temporary tree(s) where we drop everything that needs to be put on the image - resulting ISO images or jigdo files - temporary tree for apt - cache file for things downloaded from the net ? - scripts used to generate 2. Configure the parameters of the build - Select a media type This will induce a default media size and will have consequences on other scripts concerning how much data can be included on the image. - Select a package profile (i.e. an actual task) - Select a debian-installer profile - Select a build profile This could copy all the required scripts in the build directory. (maybe the media type info could be integrated into the build profile, in any case build profiles would vary with releases ...) - Customize any other standard configuration item (cf CONF.sh) - Add additionnal sources of package (used to be local packages) 3. Setup an APT sub-directory to be able to download packages and to make calculations with the information contained in apt-cache dumpavailable Loop until packages are available ( 4. Add fixed content to the CD #1 (documentation, tools, boot files, ...). 5. Create the list of packages that goes for CD #1 (with an accurate calculation since we already have all the content of the image except md5sum.txt and the Packages files, and size of both of them can be easily estimated). 6. Generate Packages.gz file for CD #1 (ideally without having to add the packages into the temp tree). ) And then : 7a. Either add packages and generate .iso 7b. Or directly generate jigdo files.
Design of new debian-cd
Hello everybody, I took a few notes yesterday everning about how I would see the build of an image with a rewrite of debian-cd ... it's in the text file attached. Comments are welcome (as well as patch if you feel the need to extend what I wrote) ! Cheers, -- Raphaël Hertzog -+- http://www.ouaza.com Formation Linux et logiciel libre : http://www.logidee.com Earn money with free software: http://www.geniustrader.org DESIGN OF A NEW DEBIAN-CD Process of building a set of ISO 1. Setup a build directory This temp tree will be self-hosting. It will contain everything related to that CD set and its build for one arch : - the configuration selected (having it only in environment variables is not good, it causes confusion and is a risk of having an old config conflict with the new one currently used if all variables are not reset) - the list of packages to include (still generated from profile like it is now) - temporary tree(s) where we drop everything that needs to be put on the image - resulting ISO images or jigdo files - temporary tree for apt - cache file for things downloaded from the net ? - scripts used to generate 2. Configure the parameters of the build - Select a media type This will induce a default media size and will have consequences on other scripts concerning how much data can be included on the image. - Select a package profile (i.e. an actual task) - Select a debian-installer profile - Select a build profile This could copy all the required scripts in the build directory. (maybe the media type info could be integrated into the build profile, in any case build profiles would vary with releases ...) - Customize any other standard configuration item (cf CONF.sh) - Add additionnal sources of package (used to be local packages) 3. Setup an APT sub-directory to be able to download packages and to make calculations with the information contained in apt-cache dumpavailable Loop until packages are available ( 4. Add fixed content to the CD #1 (documentation, tools, boot files, ...). 5. Create the list of packages that goes for CD #1 (with an accurate calculation since we already have all the content of the image except md5sum.txt and the Packages files, and size of both of them can be easily estimated). 6. Generate Packages.gz file for CD #1 (ideally without having to add the packages into the temp tree). ) And then : 7a. Either add packages and generate .iso 7b. Or directly generate jigdo files.
Future of debian-cd
Hello everyone, many of you already noticed that debian-cd is a bit complicated. And it tends to get worse since we keep doing small modifications everywhere without a global logic. Thus I think that debian-cd needs to be partially rewritten. Here are the main critics that I have : - complicated shell code in Makefile is ugly, it was supposed to not need to be modified, and in fact many parts of the Makefile were modified for various purposes - you can't reasonnably build potato cd with current debian-cd because of those infrastructural change to a CD (inclusion of udeb for example) which were not expected at the time of my initial rewrite of debian-cd. I still managed to keep most of the compatibility but at the cost of more code complexity. - we have too many imbricated options which do not make sense to many of us, it's time to see if we shouldn't get rid of some of them (or at least hide them somewhere deeper than CONF.sh) - the official support of businesscard cd/netinst cd/dvd is not good, most people are not able to build such CD with debian-cd because they don't know how the magic combination of parameters. - it's too much of black magick to know the good size parameters to give In a new design, I would like to have : - a MEDIA_TYPE input variable that would tell me : 1 - businesscard CD 2 - netinst CD 3 - usual CD 4 - DVD The size would be taken from a default value (if not overriden). - a system of profile that would describe how to build a particular kind of ISO - a system of profile for debian-installer, so that we can easily customize the udebs used by the debian installer The new design should still reuse most of the existing code, not everything needs to be thrown. In fact I think that most should be kept but cleaned from the cruft and reorganized in a different way. Now, I'd like to hear from you : - what are your (constructive) critics against debian-cd ? - what design ideas do you have for a possible rewrite ? - what do you think of what i've written above ? - how do you think we should proceed ? should I start from a completely new repository and import only what I want to keep ? should we work in a branch of the actual repository ? BTW, as you may have noticed I have less less time for debian-cd, and I'd like to have some help in the long term to help me maintain it. With a (partial) rewrite, it would be the perfect time for someone to step up and get familiar with the code ... Cheers, -- Raphaël Hertzog -+- http://www.ouaza.com Formation Linux et logiciel libre : http://www.logidee.com Earn money with free software: http://www.geniustrader.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Future of debian-cd
[ I cced [EMAIL PROTECTED] in my initial mail in order to have a paragraph about debian-cd in DWN next week - no need to continue CCing them even if my Mail-Followup-To included them ] Le Wed, Jan 07, 2004 at 03:59:52PM +0100, Richard Atterer écrivait: I think the idea of using a Makefile at all wasn't that good in retrospect. In some aspects it was interesting, I liked to be able to avoid redoing stuff which were already done when I corrected something by hand. But that's it. Maybe it would be nicer to use run-parts: A top-level script executes everything in a stages directory in alphabetical order. The individual stages could then have further directories of their own where substage-scripts for that stage of the process are stored. This would get rid of all that hook ugliness... There could be different top-level stages directories for the different CD flavours, with symlinks to scripts which are identical between any two of them. This has the advantage that you can fork code any time; instead of linking from the sarge version to the woody version, just make a copy of the script, then make changes/hacks which are woody-only. Each top-level stages dir could also come with configuration files preconfigured for that particular CD flavour. Well, something like that... I don't know if the above would work. :) It's exactly something like that that I had in mind when I spoke of profile in my initial mail. And I have the same problem than you, it looks like nice but I didn't took the time to see it it fits as well as I hope. Cheers, -- Raphaël Hertzog -+- http://www.ouaza.com Formation Linux et logiciel libre : http://www.logidee.com Earn money with free software: http://www.geniustrader.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Future of debian-cd
Hello everyone, many of you already noticed that debian-cd is a bit complicated. And it tends to get worse since we keep doing small modifications everywhere without a global logic. Thus I think that debian-cd needs to be partially rewritten. Here are the main critics that I have : - complicated shell code in Makefile is ugly, it was supposed to not need to be modified, and in fact many parts of the Makefile were modified for various purposes - you can't reasonnably build potato cd with current debian-cd because of those infrastructural change to a CD (inclusion of udeb for example) which were not expected at the time of my initial rewrite of debian-cd. I still managed to keep most of the compatibility but at the cost of more code complexity. - we have too many imbricated options which do not make sense to many of us, it's time to see if we shouldn't get rid of some of them (or at least hide them somewhere deeper than CONF.sh) - the official support of businesscard cd/netinst cd/dvd is not good, most people are not able to build such CD with debian-cd because they don't know how the magic combination of parameters. - it's too much of black magick to know the good size parameters to give In a new design, I would like to have : - a MEDIA_TYPE input variable that would tell me : 1 - businesscard CD 2 - netinst CD 3 - usual CD 4 - DVD The size would be taken from a default value (if not overriden). - a system of profile that would describe how to build a particular kind of ISO - a system of profile for debian-installer, so that we can easily customize the udebs used by the debian installer The new design should still reuse most of the existing code, not everything needs to be thrown. In fact I think that most should be kept but cleaned from the cruft and reorganized in a different way. Now, I'd like to hear from you : - what are your (constructive) critics against debian-cd ? - what design ideas do you have for a possible rewrite ? - what do you think of what i've written above ? - how do you think we should proceed ? should I start from a completely new repository and import only what I want to keep ? should we work in a branch of the actual repository ? BTW, as you may have noticed I have less less time for debian-cd, and I'd like to have some help in the long term to help me maintain it. With a (partial) rewrite, it would be the perfect time for someone to step up and get familiar with the code ... Cheers, -- Raphaël Hertzog -+- http://www.ouaza.com Formation Linux et logiciel libre : http://www.logidee.com Earn money with free software: http://www.geniustrader.org
Re: Future of debian-cd
[ I cced [EMAIL PROTECTED] in my initial mail in order to have a paragraph about debian-cd in DWN next week - no need to continue CCing them even if my Mail-Followup-To included them ] Le Wed, Jan 07, 2004 at 03:59:52PM +0100, Richard Atterer écrivait: I think the idea of using a Makefile at all wasn't that good in retrospect. In some aspects it was interesting, I liked to be able to avoid redoing stuff which were already done when I corrected something by hand. But that's it. Maybe it would be nicer to use run-parts: A top-level script executes everything in a stages directory in alphabetical order. The individual stages could then have further directories of their own where substage-scripts for that stage of the process are stored. This would get rid of all that hook ugliness... There could be different top-level stages directories for the different CD flavours, with symlinks to scripts which are identical between any two of them. This has the advantage that you can fork code any time; instead of linking from the sarge version to the woody version, just make a copy of the script, then make changes/hacks which are woody-only. Each top-level stages dir could also come with configuration files preconfigured for that particular CD flavour. Well, something like that... I don't know if the above would work. :) It's exactly something like that that I had in mind when I spoke of profile in my initial mail. And I have the same problem than you, it looks like nice but I didn't took the time to see it it fits as well as I hope. Cheers, -- Raphaël Hertzog -+- http://www.ouaza.com Formation Linux et logiciel libre : http://www.logidee.com Earn money with free software: http://www.geniustrader.org
Re: Debian cd from apt repository
Le Thu, Dec 25, 2003 at 04:50:36PM +0300, Sergey Smirnov écrivait: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Then I burn cd with pool and dists directories. And after # apt-cdrom add no new packages added. What I'm doing wrong? You're assuming that a CD is only a package repository. Tip: check the content of an official CD... you'll see things like the .disk directory. Cheers, -- Raphaël Hertzog -+- http://www.ouaza.com Formation Linux et logiciel libre : http://www.logidee.com Earn money with free software: http://www.geniustrader.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Debian cd from apt repository
Le Thu, Dec 25, 2003 at 04:50:36PM +0300, Sergey Smirnov écrivait: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Then I burn cd with pool and dists directories. And after # apt-cdrom add no new packages added. What I'm doing wrong? You're assuming that a CD is only a package repository. Tip: check the content of an official CD... you'll see things like the .disk directory. Cheers, -- Raphaël Hertzog -+- http://www.ouaza.com Formation Linux et logiciel libre : http://www.logidee.com Earn money with free software: http://www.geniustrader.org
debian-cd CVS back online
Hello everyone, the debian-cd CVS repository is back online (after a check of its integrity). Please commit any change that you postponed until now. Cheers, -- Raphaël Hertzog -+- http://www.ouaza.com Formation Linux et logiciel libre : http://www.logidee.com Earn money with free software: http://www.geniustrader.org
Re: Usage of isolinux on the beta CDs
Le Wed, Nov 19, 2003 at 09:00:12PM +0100, Santiago Garcia Mantinan écrivait: We can build two netinst sets for now if you want, but I'd rather build test images with the last version of isolinux in debug mode before making a decision on all this, anybody objects on building this kind of images and asking the people that wrote the bugs to test them so that we can get feedback on this? Go ahead ! Cheers, -- Raphaël Hertzog -+- http://www.ouaza.com Formation Linux et logiciel libre : http://www.logidee.com Earn money with free software: http://www.geniustrader.org
Re: Usage of isolinux on the beta CDs
Le Wed, Nov 19, 2003 at 09:00:12PM +0100, Santiago Garcia Mantinan écrivait: We can build two netinst sets for now if you want, but I'd rather build test images with the last version of isolinux in debug mode before making a decision on all this, anybody objects on building this kind of images and asking the people that wrote the bugs to test them so that we can get feedback on this? Go ahead ! Cheers, -- Raphaël Hertzog -+- http://www.ouaza.com Formation Linux et logiciel libre : http://www.logidee.com Earn money with free software: http://www.geniustrader.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Usage of isolinux on the beta CDs
Le Thu, Nov 13, 2003 at 04:29:25PM -0500, Joey Hess écrivait: I have just tried it and it works, even though the setup for syslinux should be changed a bit to include the help screens and all that, this should be done in debian-installer, as it is d-i who makes that image. There are several advantages to having the syslinux help be part of d-i, including letting us reuse the same material for syslinux help on the boot floppy. What would be a good way for us to distribute the help texts so debian-cd could use them on the d-i cdroms? We don't need syslinux help files AFAIK. Syslinux is integrated into the boot image that you provide us. Maybe we could put isolinux on the *second* CD, with eventually an initrd that supports SCSI cdroms. That sounds fine with me if it is ok to drop the net initrd from the booting options of the cds. Well, I don't know what else to say, in the full cd set we really can have different booting methods, one on each cd, the important thing is to decide what do we put on the netinst/bussinesscard cds and also how do we order the methods in the full cd set. I think that the main problem from the d-i team's perspective is that all the daily cds and the cds for beta 1 use isolinux. So when users come to us who cannot boot from isolinux, we have no alternative except boot floppies or the monthly full cd builds. Any approach that provides at least one netinst cd without isolinux on it would be a help to this situation. Why did we use isolinux ? Because we wanted that most people could install Debian with the first CD ... and to cover all users we had to have several kernels, one generic and one more SCSI oriented (called compact at that time). If you tell me we support all users with a single kernel/initrd then fine ... I'll remove isolinux but if you tell me that we have to keep several kernels/initrd then I want to have those several kernel/initrd on the same netinst cd and I'll keep isolinux. We did tests last year before going on with isolinux and it was supported by most of the hardware. The few failures were on old hardware where they could fall back to another CD from the full CD set. But if you really need a netinst CD without isolinux, it's of course doable. Cheers, -- Raphaël Hertzog -+- http://www.ouaza.com Formation Linux et logiciel libre : http://www.logidee.com Earn money with free software: http://www.geniustrader.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Usage of isolinux on the beta CDs
Le Thu, Nov 13, 2003 at 04:29:25PM -0500, Joey Hess écrivait: I have just tried it and it works, even though the setup for syslinux should be changed a bit to include the help screens and all that, this should be done in debian-installer, as it is d-i who makes that image. There are several advantages to having the syslinux help be part of d-i, including letting us reuse the same material for syslinux help on the boot floppy. What would be a good way for us to distribute the help texts so debian-cd could use them on the d-i cdroms? We don't need syslinux help files AFAIK. Syslinux is integrated into the boot image that you provide us. Maybe we could put isolinux on the *second* CD, with eventually an initrd that supports SCSI cdroms. That sounds fine with me if it is ok to drop the net initrd from the booting options of the cds. Well, I don't know what else to say, in the full cd set we really can have different booting methods, one on each cd, the important thing is to decide what do we put on the netinst/bussinesscard cds and also how do we order the methods in the full cd set. I think that the main problem from the d-i team's perspective is that all the daily cds and the cds for beta 1 use isolinux. So when users come to us who cannot boot from isolinux, we have no alternative except boot floppies or the monthly full cd builds. Any approach that provides at least one netinst cd without isolinux on it would be a help to this situation. Why did we use isolinux ? Because we wanted that most people could install Debian with the first CD ... and to cover all users we had to have several kernels, one generic and one more SCSI oriented (called compact at that time). If you tell me we support all users with a single kernel/initrd then fine ... I'll remove isolinux but if you tell me that we have to keep several kernels/initrd then I want to have those several kernel/initrd on the same netinst cd and I'll keep isolinux. We did tests last year before going on with isolinux and it was supported by most of the hardware. The few failures were on old hardware where they could fall back to another CD from the full CD set. But if you really need a netinst CD without isolinux, it's of course doable. Cheers, -- Raphaël Hertzog -+- http://www.ouaza.com Formation Linux et logiciel libre : http://www.logidee.com Earn money with free software: http://www.geniustrader.org
Re: prerequisites for debian-installer image upload
Le Tue, Oct 28, 2003 at 07:24:26PM -0500, Joey Hess écrivait: debian-cd: What kinds of images do you use/need from the debian-installer tree for building CDs on the various architectures? There is both an initrd image, and a CD boot floppy image, and I do not want to waste space in the archive with both if they are not both needed on a given architecture. We need : - kernel + initrd for isolinux (for multiple choice at boot time) for the first CD - kernel + initrd for starting the installation via LoadLin on Windows - boot images (2.88MB mainly) for making the CD 2 above bootable (the good old way which should still work if isolinux fails) That's for i386. I can't tell for non-i386 arches but I bet that most archs need only boot images. Last week I disabled shipping the initrd image, and this apparently broke CD builds on i386. It looks like the CD for i386 includes both the CD floppy and a cdrom.gz that looks like a renamed version of our CD initrd. Surely these are not both necessary? Yes they are. One is needed to boot with isolinux on CD1 and the other to make another CD bootable (usual ElTorito thing). The CD also currently contains the d-i floppy-initrd.gz (in install/), and I do not understand how this can possibly be of use, but my removal of that initrd from the debian-installer daily builds also seemed to break the CD builds. The actual script downloads floppy-image.img and floppy-initrd.gz ... it copies the initrd but never use it anywhere. So we should probably remove any reference to those files in our scripts since they are not used. as opposed to against the daily builds. And all the filenames of the various images d-i produces are due for an overhaul that will break your build scripts. Just a heads up for now on that.SQ Santiago (aka manty), would you like to take care of that ? I'm quite busy lately and I certainly won't be respoosive enough in the days to come ... Cheers, -- Raphaël Hertzog -+- http://www.ouaza.com Formation Linux et logiciel libre : http://www.logidee.com Earn money with free software: http://www.geniustrader.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: prerequisites for debian-installer image upload
Le Tue, Oct 28, 2003 at 07:24:26PM -0500, Joey Hess écrivait: debian-cd: What kinds of images do you use/need from the debian-installer tree for building CDs on the various architectures? There is both an initrd image, and a CD boot floppy image, and I do not want to waste space in the archive with both if they are not both needed on a given architecture. We need : - kernel + initrd for isolinux (for multiple choice at boot time) for the first CD - kernel + initrd for starting the installation via LoadLin on Windows - boot images (2.88MB mainly) for making the CD 2 above bootable (the good old way which should still work if isolinux fails) That's for i386. I can't tell for non-i386 arches but I bet that most archs need only boot images. Last week I disabled shipping the initrd image, and this apparently broke CD builds on i386. It looks like the CD for i386 includes both the CD floppy and a cdrom.gz that looks like a renamed version of our CD initrd. Surely these are not both necessary? Yes they are. One is needed to boot with isolinux on CD1 and the other to make another CD bootable (usual ElTorito thing). The CD also currently contains the d-i floppy-initrd.gz (in install/), and I do not understand how this can possibly be of use, but my removal of that initrd from the debian-installer daily builds also seemed to break the CD builds. The actual script downloads floppy-image.img and floppy-initrd.gz ... it copies the initrd but never use it anywhere. So we should probably remove any reference to those files in our scripts since they are not used. as opposed to against the daily builds. And all the filenames of the various images d-i produces are due for an overhaul that will break your build scripts. Just a heads up for now on that.SQ Santiago (aka manty), would you like to take care of that ? I'm quite busy lately and I certainly won't be respoosive enough in the days to come ... Cheers, -- Raphaël Hertzog -+- http://www.ouaza.com Formation Linux et logiciel libre : http://www.logidee.com Earn money with free software: http://www.geniustrader.org
[joeyh@debian.org: Bug#215469: don't include unnecessary udebs on the cd]
Hello, I just got this bug. It looks like we aren't smart enough about the selection of udebs to include on the CD ... The initial idea was to include them all so that all install scenario can happen but it looks like there are udebs which are useless since they are simple file repositories for d-i. And the list is getting so big, that it doesn't make sense to include everything for netinst business card CD. I think we need to update the script that generates the task files which lists udebs. Santiago ? The first step is probably just to have exclusion list/pattern used by tools/generate_di_list and/or tools/generate_di+k_list ... Cheers, -- Raphaël Hertzog -+- http://www.ouaza.com Formation Linux et logiciel libre : http://www.logidee.com Earn money with free software: http://www.geniustrader.org ---BeginMessage--- Package: debian-cd Severity: normal The businesscard and netinst cd images at http://gluck.debian.org/cdimage/testing/netinst/i386/ are bigger than they need to be. partly because they include such useless things as this: ./pool/main/k/kernel-image-2.4.20-1-i386-udeb/kernel-image-2.4.20-1-386-udeb_2.4.20-8_i386.udeb This contains only a kernel, in a form users cannot use, and that the installer will only waste a lot of memory loading into its initrd after it has already booted. ./pool/main/b/busybox-cvs/busybox-cvs-udeb_20030926-1_i386.udeb ./pool/main/b/busybox/busybox-udeb_0.60.5-2_i386.udeb All d-i images already come with the appropriate busybox udeb installed on the image. ./pool/main/c/cdrom-detect/cdrom-detect_0.31_all.udeb ./pool/main/c/cdrom-retriever/cdrom-retriever_0.08_all.udeb If the installer can find these on the CD, it does not need them. ./pool/main/c/cdebconf/cdebconf-gtk-udeb_0.46_i386.udeb ./pool/main/c/cdebconf/cdebconf-newt-udeb_0.46_i386.udeb ./pool/main/c/cdebconf/cdebconf-priority_0.46_i386.udeb ./pool/main/c/cdebconf/cdebconf-slang-udeb_0.46_i386.udeb ./pool/main/c/cdebconf/cdebconf-text-udeb_0.46_i386.udeb ./pool/main/c/cdebconf/cdebconf-udeb_0.46_i386.udeb These are probably useless, d-i boot images include at least one cdebconf frontend. Etc. I'm sure you could save a *lot* of space by working with the d-i team to whittle down the udebs on the cd images to a set that is appropriate for the purpose of the CD. As it is these images are getting too big to be useful. -- System Information: Debian Release: testing/unstable Architecture: i386 Kernel: Linux dragon 2.4.22 #1 Sun Oct 12 15:11:10 EDT 2003 i686 Locale: LANG=C, LC_CTYPE=C -- see shy jo signature.asc Description: Digital signature ---End Message---
[joeyh@debian.org: Bug#215469: don't include unnecessary udebs on the cd]
Hello, I just got this bug. It looks like we aren't smart enough about the selection of udebs to include on the CD ... The initial idea was to include them all so that all install scenario can happen but it looks like there are udebs which are useless since they are simple file repositories for d-i. And the list is getting so big, that it doesn't make sense to include everything for netinst business card CD. I think we need to update the script that generates the task files which lists udebs. Santiago ? The first step is probably just to have exclusion list/pattern used by tools/generate_di_list and/or tools/generate_di+k_list ... Cheers, -- Raphaël Hertzog -+- http://www.ouaza.com Formation Linux et logiciel libre : http://www.logidee.com Earn money with free software: http://www.geniustrader.org ---BeginMessage--- Package: debian-cd Severity: normal The businesscard and netinst cd images at http://gluck.debian.org/cdimage/testing/netinst/i386/ are bigger than they need to be. partly because they include such useless things as this: ./pool/main/k/kernel-image-2.4.20-1-i386-udeb/kernel-image-2.4.20-1-386-udeb_2.4.20-8_i386.udeb This contains only a kernel, in a form users cannot use, and that the installer will only waste a lot of memory loading into its initrd after it has already booted. ./pool/main/b/busybox-cvs/busybox-cvs-udeb_20030926-1_i386.udeb ./pool/main/b/busybox/busybox-udeb_0.60.5-2_i386.udeb All d-i images already come with the appropriate busybox udeb installed on the image. ./pool/main/c/cdrom-detect/cdrom-detect_0.31_all.udeb ./pool/main/c/cdrom-retriever/cdrom-retriever_0.08_all.udeb If the installer can find these on the CD, it does not need them. ./pool/main/c/cdebconf/cdebconf-gtk-udeb_0.46_i386.udeb ./pool/main/c/cdebconf/cdebconf-newt-udeb_0.46_i386.udeb ./pool/main/c/cdebconf/cdebconf-priority_0.46_i386.udeb ./pool/main/c/cdebconf/cdebconf-slang-udeb_0.46_i386.udeb ./pool/main/c/cdebconf/cdebconf-text-udeb_0.46_i386.udeb ./pool/main/c/cdebconf/cdebconf-udeb_0.46_i386.udeb These are probably useless, d-i boot images include at least one cdebconf frontend. Etc. I'm sure you could save a *lot* of space by working with the d-i team to whittle down the udebs on the cd images to a set that is appropriate for the purpose of the CD. As it is these images are getting too big to be useful. -- System Information: Debian Release: testing/unstable Architecture: i386 Kernel: Linux dragon 2.4.22 #1 Sun Oct 12 15:11:10 EDT 2003 i686 Locale: LANG=C, LC_CTYPE=C -- see shy jo signature.asc Description: Digital signature ---End Message---
[toff1@cox.net: Bug#214867: debian-cd: Current powerpc netinst image for debian-installer is not hfs]
PowerPC porters ? Can you look at this bug and respond ? Cheers, -- Raphaël Hertzog -+- http://www.ouaza.com Formation Linux et logiciel libre : http://www.logidee.com Earn money with free software: http://www.geniustrader.org ---BeginMessage--- Package: debian-cd Version: current Severity: normal File: debian-cd The current netinst iso build at gluck.debian.org for powerpc (on 10/7/2003) is not an hfs volume. When I downloaded it last week, I think it was. The CD needs hfs in order to be bootable on powermacs. -- System Information: Debian Release: 3.0 Architecture: powerpc Kernel: Linux ip68-107-137-100.tc.ph.cox.net 2.4.22-powerpc #1 Sat Oct 4 08:20:43 CEST 2003 ppc Locale: LANG=C, LC_CTYPE=C ---End Message---
[toff1@cox.net: Bug#214867: debian-cd: Current powerpc netinst image for debian-installer is not hfs]
PowerPC porters ? Can you look at this bug and respond ? Cheers, -- Raphaël Hertzog -+- http://www.ouaza.com Formation Linux et logiciel libre : http://www.logidee.com Earn money with free software: http://www.geniustrader.org ---BeginMessage--- Package: debian-cd Version: current Severity: normal File: debian-cd The current netinst iso build at gluck.debian.org for powerpc (on 10/7/2003) is not an hfs volume. When I downloaded it last week, I think it was. The CD needs hfs in order to be bootable on powermacs. -- System Information: Debian Release: 3.0 Architecture: powerpc Kernel: Linux ip68-107-137-100.tc.ph.cox.net 2.4.22-powerpc #1 Sat Oct 4 08:20:43 CEST 2003 ppc Locale: LANG=C, LC_CTYPE=C ---End Message---
Re: changes I'd like to commit and discuss
Le Sun, Oct 05, 2003 at 05:49:54PM +0200, Santiago Garcia Mantinan écrivait: $CODENAME, I really think that moving the yaboot dir is the best we can do, anyway, either this solutions should mean changes in potato and woody powerpc boot scripts. Yes, use separate directories. The boot script we have now for sarge and which is still missing some little things, currently downloads this yaboot related files from tsauter's page at people.debian.org, but I really think we should place them in debian-cd, like it was done before. Agreed. As long as the files do not changes too often ... For the rest, I'm ok. Feel free to commit your work. Cheers, -- Raphaël Hertzog -+- http://www.ouaza.com Formation Linux et logiciel libre : http://www.logidee.com Earn money with free software: http://www.geniustrader.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: changes I'd like to commit and discuss
Le Sun, Oct 05, 2003 at 05:49:54PM +0200, Santiago Garcia Mantinan écrivait: $CODENAME, I really think that moving the yaboot dir is the best we can do, anyway, either this solutions should mean changes in potato and woody powerpc boot scripts. Yes, use separate directories. The boot script we have now for sarge and which is still missing some little things, currently downloads this yaboot related files from tsauter's page at people.debian.org, but I really think we should place them in debian-cd, like it was done before. Agreed. As long as the files do not changes too often ... For the rest, I'm ok. Feel free to commit your work. Cheers, -- Raphaël Hertzog -+- http://www.ouaza.com Formation Linux et logiciel libre : http://www.logidee.com Earn money with free software: http://www.geniustrader.org
Re: new sarge cd images and some questions
Le Tue, Sep 09, 2003 at 12:11:41AM +0200, Santiago Garcia Mantinan écrivait: Petter asked me what is zlib1g doing there, if it isn't supposed to be pulled when needed, and I don't remember why it was put there to know if it can be removed, anyone? No idea ... The removal of the cdrom144 option, as it no longer exists. Made the required changes to build using sjogren's debian-installer repository instead of tfheen's broken one. If all this seems fine I'll commit them and upgrade the udeb list as well. Comments? Everything looks fine, go commit ! Cheers, -- Raphaël Hertzog -+- http://www.ouaza.com Formation Linux et logiciel libre : http://www.logidee.com Earn money with free software: http://www.geniustrader.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: debian-cd questions [Was: Re: Debian-cd 2.2.16 uploaded, any co-maintainers ?]
Le Fri, Aug 22, 2003 at 03:12:50AM +0200, Goswin von Brederlow écrivait: I need different kernel images (building them atm), different ramdisks (those debix will build via debix-imager), and the normal ramdisk or a full live filesystem as loopback file on the CD. I hope I can use debian-cd to create the actual CDs and make them bootabel. I would hate to do the bootloader stuff for alpha, mips, all over again. Sure, beware however that not all arch are able to provide a choice for the kernel to use at boot time ... Is there some documentation about intelligent hooks in the cvs? Not really, the only doc available is what's in README (and README.devel). It's rather terse about the hooks but well UTSL. :-) By the way, does debian-cd need root to build the ramdisk or is that provided as image by boot-floppies/D-I? Can't rememer. Provided by d-i. I always tried to avoid root requirement. It may be that sparc building needs root right (in order loop-munt a file and edit it IIRC). Cheers, -- Raphaël Hertzog -+- http://www.ouaza.com Formation Linux et logiciel libre : http://www.logidee.com Earn money with free software: http://www.geniustrader.org
Re: Debian-cd 2.2.16 uploaded, any co-maintainers ?
Le Thu, Aug 21, 2003 at 09:21:11AM +0200, [EMAIL PROTECTED] écrivait: What exactly are the tasks of a co-maintainer and how much time will this consume ? The tasks of the comaintainer are the same as the tasks of the maintainer. Fixing bugs in debian-cd and adapt it to follow the evolution of Debian (examples of changes have been: inclusion of signed Packages files, inclusion of udeb, ...). Hmm, so maintaining debian-cd will require in-depth knowledge about debian-boot for all 16 (17) architectures ? No, it requires you to take contact with the people who know and work with them. It requires you to prod people who can do the work ... Cheers, -- Raphaël Hertzog -+- http://www.ouaza.com Formation Linux et logiciel libre : http://www.logidee.com Earn money with free software: http://www.geniustrader.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#206501: cdrom: sarge-i386-netinst.iso does not contain all 2.4 kernel net modules
reassign 206501 installation thanks Le Thu, Aug 21, 2003 at 02:16:20PM +1000, Ian Maclaine-cross écrivait: have Debian installed or reinstalled. The eepro100 module of kernel version 2.4.19+ works very well as a driver but is apparently not included in Official Debian installation media. The sarge-i386-netinst.iso image of the 20th August 2003 tells you to go and get the module elsewhere. This is very inconvenient and no instructions are given about which package or disk the eepro100.o file must be taken from. Debian-cd can't do anything about that. Please check with the debian-boot team. Cheers, -- Raphaël Hertzog -+- http://www.ouaza.com Formation Linux et logiciel libre : http://www.logidee.com Earn money with free software: http://www.geniustrader.org
Re: Debian-cd 2.2.16 uploaded, any co-maintainers ?
Le Thu, Aug 21, 2003 at 09:21:11AM +0200, [EMAIL PROTECTED] écrivait: What exactly are the tasks of a co-maintainer and how much time will this consume ? The tasks of the comaintainer are the same as the tasks of the maintainer. Fixing bugs in debian-cd and adapt it to follow the evolution of Debian (examples of changes have been: inclusion of signed Packages files, inclusion of udeb, ...). Hmm, so maintaining debian-cd will require in-depth knowledge about debian-boot for all 16 (17) architectures ? No, it requires you to take contact with the people who know and work with them. It requires you to prod people who can do the work ... Cheers, -- Raphaël Hertzog -+- http://www.ouaza.com Formation Linux et logiciel libre : http://www.logidee.com Earn money with free software: http://www.geniustrader.org
Re: Debian-cd 2.2.16 uploaded, any co-maintainers ?
Le Thu, Aug 21, 2003 at 12:05:16PM +0200, Goswin von Brederlow écrivait: The package is not in a bad shape (there's only one wishlist bug open) but from time to time it requires immediate attention to adapt it to a new set of files provided by the debian-boot team for example... Is there any debian-installer support yet? Sure there is ! How do you think we build the d-i test images ? Did you notice me developing and packaging debix and as a sub package debix-imager. Debix-imager handles the part of boot-floppy and ramdisk creation that needs root. I intend to do build D-I CDs with debix as one option which might mean forking debian-cd or copying the support for it from debian-cd. What about depending on it and using it ? debian-cd is modular enough to be able to do whatever you need provided that you write some intelligent hooks ... doing work on different archs and from debian-boot. Or even more likely pestering debian-arch so someone volunteres to test and fix problems that arise. Exactly. Cheers, -- Raphaël Hertzog -+- http://www.ouaza.com Formation Linux et logiciel libre : http://www.logidee.com Earn money with free software: http://www.geniustrader.org
Debian-cd 2.2.16 uploaded, any co-maintainers ?
Hello everyone, I finally uploaded debian-cd 2.2.16 to unstable. But I've been way too long in doing that and that reminds me that I really should find some co-maintainers in order to avoid such delays in the future. So, are there any volunteers ? The package is not in a bad shape (there's only one wishlist bug open) but from time to time it requires immediate attention to adapt it to a new set of files provided by the debian-boot team for example... Cheers, -- Raphaël Hertzog -+- http://www.ouaza.com Formation Linux et logiciel libre : http://www.logidee.com Earn money with free software: http://www.geniustrader.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Official testing images served as text/plain
Le Sun, Aug 17, 2003 at 01:38:15PM +0100, Brian Campbell écrivait: The official testing network install images on gluck.debian.org linked to from http://www.debian.org/CD/netinst/ are being served as text/plain. It would be better if it were something less likely to be mangled by browsers, although I can't find anything more appropriate than application/octet-stream. Ok, I modified the apache config file on gluck. The server just needs to be restarted/reloaded. This will automatically happen one day (when the logs are rotated) ... just wait a bit more. :) Cheers, -- Raphaël Hertzog -+- http://www.ouaza.com Formation Linux et logiciel libre : http://www.logidee.com Earn money with free software: http://www.geniustrader.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Debian-cd 2.2.16 uploaded, any co-maintainers ?
Hello everyone, I finally uploaded debian-cd 2.2.16 to unstable. But I've been way too long in doing that and that reminds me that I really should find some co-maintainers in order to avoid such delays in the future. So, are there any volunteers ? The package is not in a bad shape (there's only one wishlist bug open) but from time to time it requires immediate attention to adapt it to a new set of files provided by the debian-boot team for example... Cheers, -- Raphaël Hertzog -+- http://www.ouaza.com Formation Linux et logiciel libre : http://www.logidee.com Earn money with free software: http://www.geniustrader.org
Re: Official testing images served as text/plain
Le Sun, Aug 17, 2003 at 01:38:15PM +0100, Brian Campbell écrivait: The official testing network install images on gluck.debian.org linked to from http://www.debian.org/CD/netinst/ are being served as text/plain. It would be better if it were something less likely to be mangled by browsers, although I can't find anything more appropriate than application/octet-stream. Ok, I modified the apache config file on gluck. The server just needs to be restarted/reloaded. This will automatically happen one day (when the logs are rotated) ... just wait a bit more. :) Cheers, -- Raphaël Hertzog -+- http://www.ouaza.com Formation Linux et logiciel libre : http://www.logidee.com Earn money with free software: http://www.geniustrader.org
Re: contents of the first sarge CD image
Le Thu, Jul 24, 2003 at 12:31:43AM +0200, Santiago Garcia Mantinan écrivait: BTW, I was wondering if we should also use SECURED=1 or not :-? Well, it doesn't seem necessary to me until apt has real support for checking the signatures. It also takes more space than needed. So leave it out for the moment. Cheers, -- Raphaël Hertzog -+- http://www.ouaza.com Formation Linux et logiciel libre : http://www.logidee.com Earn money with free software: http://www.geniustrader.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: contents of the first sarge CD image
Le Thu, Jul 24, 2003 at 12:31:43AM +0200, Santiago Garcia Mantinan écrivait: BTW, I was wondering if we should also use SECURED=1 or not :-? Well, it doesn't seem necessary to me until apt has real support for checking the signatures. It also takes more space than needed. So leave it out for the moment. Cheers, -- Raphaël Hertzog -+- http://www.ouaza.com Formation Linux et logiciel libre : http://www.logidee.com Earn money with free software: http://www.geniustrader.org
Re: contents of the first sarge CD image
Le Wed, Jul 23, 2003 at 10:40:42AM +0200, Josip Rodin écrivait: So atlas2* gets in because it's in some scientific task package, is that what you're saying? yes. And aterm, powershell, original-awk...? None of those are nearly as popular as those three things I mentioned (standard popcon disclaimers apply), and yet they all got onto the first CD. And judging by what you are saying, some of those things are simply buggy. The exclude file tries to kill off a lot of the aspell-* packages and fails: It doesn't fail, it's probably just not used by the scripts run on gluck... Santiago could you please use exclude-sarge and unexclude-CD2-sarge in the build on gluck ? Also there are some real gems on the first CD: I'd be glad if you could make a real proposition (ie a patch) of what to remove from CD1 and put on CD2, etc. (and yes, I realize that _some_ of the above is in tasks, but still) Anyway tasks don't fit together on the same CD, that's why we created two task file ... one for the important ones and the other ones for the less important one. Of course what this does mean is that the popularity contest has no influence on CD1 but just on CD2/3-8 ... Anne Bezemer used to do that kind of work in the past, and there's a kind of gap to fill there ... so if someone is willing to volunteer... Cheers, -- Raphaël Hertzog -+- http://www.ouaza.com Formation Linux et logiciel libre : http://www.logidee.com Earn money with free software: http://www.geniustrader.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: contents of the first sarge CD image
Le Tue, Jul 22, 2003 at 11:30:07PM +0200, Josip Rodin écrivait: Hi, I burned a sarge-i386-1.iso the other day using Jigdo from gluck. Who/what decides what packages go onto it? It's a complex algorithm. :) Basically, just check tasks/Debian_sarge as a starting point. We try to include on the first CD all packages listed in a Task (tasks/task-essential-sarge, tasks/task-full-sarge), all packages required by debootstrap (tasks/base-sarge), and generally speaking the most common packages (as defined by the popularity contest, tasks/popularity-contest-sarge). On the other hand we have an exclude mechanism because some packages get included for other reasons (standard priority for example) and we don't want them on the first CD (tasks/exclude-sarge) but they may be reintegrated somewhere else (tasks/unexclude-CD2-sarge). Those two features need some specific environment variables set at build time and thus those files may have been not used to build the sarge image available ... We also have a custom must-have list: tasks/forcd1 Cheers, -- Raphaël Hertzog -+- http://www.ouaza.com Formation Linux et logiciel libre : http://www.logidee.com Earn money with free software: http://www.geniustrader.org
Re: please change debian-cd/data/sarge/f3.txt
Le Mon, Jul 14, 2003 at 10:54:29AM +0100, Alastair McKinstry écrivait: Please change reference to 'net' to 'netboot', as it has been renamed. Please commit that change yourself, you appear to know what you're speaking about. :-) Cheers, -- Raphaël Hertzog -+- http://www.ouaza.com Formation Linux et logiciel libre : http://www.logidee.com Earn money with free software: http://www.geniustrader.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: please change debian-cd/data/sarge/f3.txt
Le Mon, Jul 14, 2003 at 10:54:29AM +0100, Alastair McKinstry écrivait: Please change reference to 'net' to 'netboot', as it has been renamed. Please commit that change yourself, you appear to know what you're speaking about. :-) Cheers, -- Raphaël Hertzog -+- http://www.ouaza.com Formation Linux et logiciel libre : http://www.logidee.com Earn money with free software: http://www.geniustrader.org
Input about #185238
Hello, in bug #185238 I have been requested to add an autorun.inf file to debian-cd so that the documentation is opened by default when you insert a debian-cd on your Windows PC. Unfortunately it's not that easy, it requires including an external program to make it work on all Windows. Is that worth it ? Also I'd like to know what happens if I put a cd with the start index.html stuff in Windows NT/2K, does it silently fail or does it show an error ? In the same manner I might propose to start the install/boot.bat script (start of install with loadlin) with a second option that is visible with a rigt click on the CD. This is good if install/boot.bat is frequently used and is considered a good way to start the install process. Unfortunately I never used this script (i'm used to boot right on the CD) and as such I don't know if this would be a good idea. Thank you in advance for your feedback ! Cheers, http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=185238 -- Raphaël Hertzog -+- http://www.ouaza.com Formation Linux et logiciel libre : http://www.logidee.com
Re: stuff that needs to be on cd #1
Le Fri, Apr 18, 2003 at 07:28:19PM -0400, Joey Hess écrivait: Thank you. Another one is libtext-iconv-perl which is now important and installed by debootstrap. It's used by debconf i18n. Hum... the packages installed by debootstrap have a dedicated task file which I update from to time with a simple script. I did it right now but libtext-iconv-perl didn't appear as it's only listed for sid in debootstrap. Someone should remind to update that task file once libtext-iconv-perl is listed for sarge too. Cheers, -- Raphaël Hertzog -+- http://www.ouaza.com Formation Linux et logiciel libre : http://www.logidee.com
Re: stuff that needs to be on cd #1
Le Fri, Apr 18, 2003 at 01:19:39PM -0400, Joey Hess écrivait: Please make sure that the following stuff is on cd #1, if at all possible: popularity-contest Added. discover read-edid mdetect Those three already were in the first CD. Cheers, -- Raphaël Hertzog -+- http://www.ouaza.com Formation Linux et logiciel libre : http://www.logidee.com
Re: your mail
[ I'm redirecting him where appropriate ... ] J'aimerai d'abord vous informer que la liste debian-cd@lists.debian.org est dédiée au développement du logiciel de création des CDs Debian et c'est une liste anglophone. Votre message n'y est donc pas à sa place. Vous devriez vous tourner vers debian-user-french@lists.debian.org plutôt. Le Wed, Apr 09, 2003 at 03:41:08PM +0200, bernard.klein écrivait: Puis je installer Debian sur un ATHLON 2000? Oui. Contient il GTK? Oui. S'installe t il seul? Non, il faut mettre le CD dans le lecteur, booter dessus et répondre aux questions. Cordialement, -- Raphaël Hertzog -+- http://www.ouaza.com Formation Linux et logiciel libre : http://www.logidee.com
Re: Making netinst CDs Not Suck
Le Fri, Apr 04, 2003 at 09:24:15PM +0200, Martin Sjögren écrivait: The cvs version of anna now supports calling the retriever with a 'config' argument, and tries to load a list of udebs to automatically install from /var/cache/anna/autoinst. Now we need: How does that interact together ? calling the retriever with the config argument is expected to do what ? fill in /var/cache/anna/autoinst ? - decide a /cdrom/.disk/ file. anna_autoinst? And what would contain this file ? a list of udebs ? a name of an install scenario ? - add stuff to debian-cd for creating reasonable files for the netinst CDs. That's easy if you tell me what to put in the files ;-) - file bugs on ftp.d.o to have the priority of the udebs changed to optional so they aren't pulled in all the time. Sounds reasonable? What did I forget? Looks like ok for me. Cheers, -- Raphaël Hertzog -+- http://www.ouaza.com Formation Linux et logiciel libre : http://www.logidee.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: 3.0r1 DVD/netinst images
Le Tue, Jan 28, 2003 at 09:55:31AM +, Steve McIntyre écrivait: Why did it crash ? Because there was not enough disk space or because there are problems with some packages or debian-cd ? Neither - open was having hardware problems and being relatively unstable. Steve, an update for the DVD image ? Many people have requested them since your last mail ... I'm surprised you have problems. I'm using an unpatched debian-cd on open right now. It's created the i386 and source jigdos fine and is on to arm now. The alpha DVD build failed because isomarkboot isn't (yet) large file clean. If you created the DVD images, can you make them available ? :) Cheers, -- Raphaël Hertzog -+- http://www.ouaza.com Formation Linux et logiciel libre : http://www.logidee.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: 3.0r1 DVD/netinst images
Le Tue, Jan 28, 2003 at 09:55:31AM +, Steve McIntyre écrivait: Why did it crash ? Because there was not enough disk space or because there are problems with some packages or debian-cd ? Neither - open was having hardware problems and being relatively unstable. Steve, an update for the DVD image ? Many people have requested them since your last mail ... I'm surprised you have problems. I'm using an unpatched debian-cd on open right now. It's created the i386 and source jigdos fine and is on to arm now. The alpha DVD build failed because isomarkboot isn't (yet) large file clean. If you created the DVD images, can you make them available ? :) Cheers, -- Raphaël Hertzog -+- http://www.ouaza.com Formation Linux et logiciel libre : http://www.logidee.com
