Bug#537827: debian-cd boot tries to extract files from syslinux instead of syslinux-common
Package: debian-cd Version: 2:3.71+dfsg-5 When packing a bootable lenny CD, debian-cd/tools/boot/lenny/boot-x86 (line 167) tries to extract isolinux.bin from package syslinux, but this file is in syslinux-common which makes the CD build fail. Correcting syslinux to syslinux-common solved the problem. -- To UNSUBSCRIBE, email to debian-cd-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#537205: KDE CD installs TWM but not KDE
forcemerge 537205 536312 thanks Quoting Steve McIntyre (st...@einval.com): I think it is the consequence of #536312. Maybe should be merged with that one? Agreed, looks very like that. Let's trust you blindly. After all, I've been crazy enough to trust you as DPL, so I have some trust in you..:) signature.asc Description: Digital signature
Bug#537841: debian-cd copies vmlinuz to /install.386 whereas isolinux is configured to fetch it in /install
Package: debian-cd Version: 3.1.1 debian-cd/tools/boot/lenny/boot-x86 states at line 59 INSTALLDIR_i386=install.386 but isolinux (dists/lenny/main/installer-i386/current/images/cdrom/debian-cd_info.tar.gz) is set up to boot the kernel from /install, so the generated CD can't boot. Replacing install.386 by install solved this issue for me. -- To UNSUBSCRIBE, email to debian-cd-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#537841: debian-cd copies vmlinuz to /install.386 whereas isolinux is configured to fetch it in /install
On Tuesday 21 July 2009, Alexis Bezverkhyy wrote: debian-cd/tools/boot/lenny/boot-x86 states at line 59 INSTALLDIR_i386=install.386 but isolinux (dists/lenny/main/installer-i386/current/images/cdrom/debian-cd_info.ta r.gz) is set up to boot the kernel from /install, so the generated CD can't boot. Replacing install.386 by install solved this issue for me. This is wrong. The script also takes care of creating the install.386 directory _and_ to change the isolinux config appropriately [1]. If it does not in your case, then the script is failing somewhere and you should trace where and why it is failing. The script normally creates working images, so the problem is with your use of it. [1] The reason it does this is to support multi-arch images containing both i386 and amd64 which each have their own install.arch directory. -- To UNSUBSCRIBE, email to debian-cd-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
