Bug#341524: yaird: fails to upgrade from linux-2.4 to 2.6
On Thu, Dec 01, 2005 at 08:25:13AM +0100, Sven Luther wrote: Well, at 2.6.14 release time, initramfs-tools, and his klibc dependency, had some maturation problems, and is also regularly broken by udev, so for now, yaird, provided it works, is still the more solid solution, and at least it will fail cleanly, and give you an error message or such, while initramfs-tools may or not fail during boot time. In case this was not clear, this applied to the time 2.6.14 was released. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#341524: yaird: fails to upgrade from linux-2.4 to 2.6
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, 1 Dec 2005 08:25:13 +0100 Sven Luther [EMAIL PROTECTED] wrote: Maybe the best idea would be to have yaird as first default as now, but have the dependencies install both, which would guarantee it always works. A better approach IMHO is to recommend (not depend on) alternative ramdisk tool than the one picked as default. initramfs-tools will pull in udev which is unwanted for some, and yaird will similarly pull in perl dependencies that is unwanted for some. Sure, both can be seen as weird complaints (I have had my fights with convincing the php4 maintainer to not depend on X11 by default when sanely avoidable), but I don't think disliking udev should force one to either recompile kernels or use equivs. - Jonas - -- * Jonas Smedegaard - idealist og Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ - Enden er nær: http://www.shibumi.org/eoti.htm -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFDjtvFn7DbMsAkQLgRAtUiAJ41fFeCsOqGJL0Thd0y34hUyWVvwwCeLy7e Z/lO7oCK9c7D8OS+8wuAimQ= =xFwx -END PGP SIGNATURE-
Bug#341524: yaird: fails to upgrade from linux-2.4 to 2.6
On Thu, Dec 01, 2005 at 12:17:25PM +0100, Jonas Smedegaard wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, 1 Dec 2005 08:25:13 +0100 Sven Luther [EMAIL PROTECTED] wrote: Maybe the best idea would be to have yaird as first default as now, but have the dependencies install both, which would guarantee it always works. A better approach IMHO is to recommend (not depend on) alternative ramdisk tool than the one picked as default. Well, with tools like aptitude, there is not much of a difference. initramfs-tools will pull in udev which is unwanted for some, and yaird will similarly pull in perl dependencies that is unwanted for some. perl dependencies are hardly problematic, especially since we have perl-base, altough it would be good to make yaird depend on perl-base only, but we discussed this already. Udev might be more legitimate to not want though. Sure, both can be seen as weird complaints (I have had my fights with convincing the php4 maintainer to not depend on X11 by default when This is also a sane complaint, we divided ocaml packages between the x version and the nox stuff too. sanely avoidable), but I don't think disliking udev should force one to either recompile kernels or use equivs. Yep, that makes sense. Too bad dependencies don't allow us to do something more advanced. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#341524: yaird: fails to upgrade from linux-2.4 to 2.6
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, 1 Dec 2005 12:25:02 +0100 Sven Luther [EMAIL PROTECTED] wrote: On Thu, Dec 01, 2005 at 12:17:25PM +0100, Jonas Smedegaard wrote: On Thu, 1 Dec 2005 08:25:13 +0100 Sven Luther [EMAIL PROTECTED] wrote: Maybe the best idea would be to have yaird as first default as now, but have the dependencies install both, which would guarantee it always works. A better approach IMHO is to recommend (not depend on) alternative ramdisk tool than the one picked as default. Well, with tools like aptitude, there is not much of a difference. Yes there is: Aptitude treats recommends as they are: Recommended but acceptable to explicitly avoid. Or, as I do for some setups: explicitly avoid recommended packages *always* by passing it - --with-recommends. initramfs-tools will pull in udev which is unwanted for some, and yaird will similarly pull in perl dependencies that is unwanted for some. perl dependencies are hardly problematic, especially since we have perl-base, altough it would be good to make yaird depend on perl-base only, but we discussed this already. Udev might be more legitimate to not want though. Stop spreading FUD, please. this has been discussed before and it does not seem likely to have yaird use only perl-base without extensive changes. Sure, both can be seen as weird complaints (I have had my fights with convincing the php4 maintainer to not depend on X11 by default when This is also a sane complaint, we divided ocaml packages between the x version and the nox stuff too. Please note that I did not claim insanity. I wrote that it _can_ be seen as weird. Agreeing with me is no argument that others can see it as weird. If interested then I'd appreciate help making libgd dependent packages build-depend on the -noxpm variant development packages, but really that is irrelevant for this bugreport. sanely avoidable), but I don't think disliking udev should force one to either recompile kernels or use equivs. Yep, that makes sense. Too bad dependencies don't allow us to do something more advanced. I just porposed a possible approach: When depending on yaird then recommend initramfs-tools, and vice versa. I am aware that apt-get ignores recommends, but that is a bug with apt, and everytime people are hit by that bug we get a chance to advertise aptitude (and if such advertisement is refused with apt-get is good enough for me, well - then it's their own fault they get hurt by things like this). - Jonas - -- * Jonas Smedegaard - idealist og Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ - Enden er nær: http://www.shibumi.org/eoti.htm -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFDjwDMn7DbMsAkQLgRAnnZAJ9JPKevwJ6LklwoWJ4RPy5eUMSZnACdHMmh hCrRrAG92MmkxDLEmG6ku9c= =nzYT -END PGP SIGNATURE-
Bug#341524: yaird: fails to upgrade from linux-2.4 to 2.6
Package: yaird Version: 0.0.11-12 Severity: important Hello, I just upgraded to sid from sarge, and I'm having problems moving to the kernel 2.6. First off, let me mention that the upgrade didn't go as smoothly as planned, which was to be expected nowadays... My packages for kernel-image-2.6 were removed somehow, probably due to the new linux-image kernels. Anyways... Now that I actually try to switch to 2.6, some weird problem doesn't want to let me. I tried this: # aptitude install yaird [...] # tail -1 /etc/kernel-img.conf ramdisk = /usr/sbin/mkinitrd.yaird # : note that I also tried without the above line # aptitude install linux-image-k7 [...] The following NEW packages will be installed: linux-image-2.6-k7 linux-image-2.6.14-2-k7 linux-image-k7 [...] Selecting previously deselected package linux-image-2.6.14-2-k7. (Reading database ... 230480 files and directories currently installed.) Unpacking linux-image-2.6.14-2-k7 (from .../linux-image-2.6.14-2-k7_2.6.14-4_i386.deb) ... You are attempting to install an initrd kernel image (version 2.6.14-2-k7) while running a kernel of version 2.4.27-2-k7, but you have no suitable ramdisk generation tool installed among /usr/sbin/mkinitrd.yaird. This will break the installation, unless a suitable ramdisk generation tool is also being installed right now. Could not find . at /var/lib/dpkg/tmp.ci/preinst line 228. Selecting previously deselected package linux-image-2.6-k7. Unpacking linux-image-2.6-k7 (from .../linux-image-2.6-k7_2.6.14-4_i386.deb) ... Selecting previously deselected package linux-image-k7. Unpacking linux-image-k7 (from .../linux-image-k7_2.6.14-4_i386.deb) ... Setting up linux-image-2.6.14-2-k7 (2.6.14-4) ... Failed to find suitable ramdisk generation tool for kernel version 2.6.14-2-k7 on running kernel 2.4.27-2-k7 in /usr/sbin/mkinitrd.yaird dpkg: error processing linux-image-2.6.14-2-k7 (--configure): subprocess post-installation script returned error exit status 9 dpkg: dependency problems prevent configuration of linux-image-2.6-k7: linux-image-2.6-k7 depends on linux-image-2.6.14-2-k7; however: Package linux-image-2.6.14-2-k7 is not configured yet. dpkg: error processing linux-image-2.6-k7 (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of linux-image-k7: linux-image-k7 depends on linux-image-2.6-k7; however: Package linux-image-2.6-k7 is not configured yet. dpkg: error processing linux-image-k7 (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: linux-image-2.6.14-2-k7 linux-image-2.6-k7 linux-image-k7 E: Sub-process /usr/bin/dpkg returned an error code (1) A package failed to install. Trying to recover: Setting up linux-image-2.6.14-2-k7 (2.6.14-4) ... Failed to find suitable ramdisk generation tool for kernel version 2.6.14-2-k7 on running kernel 2.4.27-2-k7 in /usr/sbin/mkinitrd.yaird dpkg: error processing linux-image-2.6.14-2-k7 (--configure): subprocess post-installation script returned error exit status 9 dpkg: dependency problems prevent configuration of linux-image-2.6-k7: linux-image-2.6-k7 depends on linux-image-2.6.14-2-k7; however: Package linux-image-2.6.14-2-k7 is not configured yet. dpkg: error processing linux-image-2.6-k7 (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of linux-image-k7: linux-image-k7 depends on linux-image-2.6-k7; however: Package linux-image-2.6-k7 is not configured yet. dpkg: error processing linux-image-k7 (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: linux-image-2.6.14-2-k7 linux-image-2.6-k7 linux-image-k7 Seems to me that yaird doesn't support migration from 2.4 to 2.6.14. It does support anything below 2.6.13 though: # mkinitrd --supported-host-version=2.4.27-2-k7 --supported-target-version=2.6.12 echo 1 1 # mkinitrd --supported-host-version=2.4.27-2-k7 --supported-target-version=2.6.13 echo 1 # That is after adding the line to kernel-img.conf but i had the same result before. Now, I *was* able to upgrade, using the initramfs-tools package. Maybe the dependency list for linux-image should be reversed for that package, ie. put initramfs before yaird. # /usr/sbin/mkinitramfs --supported-host-version=2.4.27-2-k7 --supported-target-version=2.6.14 echo 1 1 I'm not sure I understand all the implications here, but I leave that all in your wise hands. I can help more if you tell me what to do. :) Thanks, a. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#341524: yaird: fails to upgrade from linux-2.4 to 2.6
On Thu, Dec 01, 2005 at 01:29:08AM -0500, The Anarcat wrote: Package: yaird Version: 0.0.11-12 Severity: important Hello, I just upgraded to sid from sarge, and I'm having problems moving to the kernel 2.6. First off, let me mention that the upgrade didn't go as smoothly as planned, which was to be expected nowadays... My packages for kernel-image-2.6 were removed somehow, probably due to the new linux-image kernels. Anyways... Now that I actually try to switch to 2.6, some weird problem doesn't want to let me. I tried this: Well, yaird cannot install from a 2.4 kernel, which is why you see this failure. The correct upgrade way using yaird is to first upgrade to the sarge (2.6.8) or etch (2.6.12) 2.6 kernel, and then upgrade to 2.6.14 after a reboot, using yaird, or boot the current 2.6.14 based sid-d-i netinst, once you are at the partitioning step, go to console 2, mount your root partition, chroot into it, mount /proc and /sys, and dpkg-reconfigure linux-image-2.6.14-2-k7. The other alternative is to install initramfs-tools, which knows how to install from a 2.4 kernel. I prefer using yaird myself though. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#341524: yaird: fails to upgrade from linux-2.4 to 2.6
On Thu Dec 01, 2005 at 07:58:32AM +0100, Sven Luther wrote: Well, yaird cannot install from a 2.4 kernel, which is why you see this failure. The correct upgrade way using yaird is to first upgrade to the sarge (2.6.8) or etch (2.6.12) 2.6 kernel, and then upgrade to 2.6.14 after a reboot, using yaird, or boot the current 2.6.14 based sid-d-i netinst, once you are at the partitioning step, go to console 2, mount your root partition, chroot into it, mount /proc and /sys, and dpkg-reconfigure linux-image-2.6.14-2-k7. The other alternative is to install initramfs-tools, which knows how to install from a 2.4 kernel. I prefer using yaird myself though. Is this what the upgrade path from sarge will look like for etch (assuming here that etch will go up to 2.6.14, or will that not happen at all?). In general, why not simply change the depends to have the whole thing Just Work in the general case? A. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#341524: yaird: fails to upgrade from linux-2.4 to 2.6
On Thu, Dec 01, 2005 at 02:12:20AM -0500, The Anarcat wrote: On Thu Dec 01, 2005 at 07:58:32AM +0100, Sven Luther wrote: Well, yaird cannot install from a 2.4 kernel, which is why you see this failure. The correct upgrade way using yaird is to first upgrade to the sarge (2.6.8) or etch (2.6.12) 2.6 kernel, and then upgrade to 2.6.14 after a reboot, using yaird, or boot the current 2.6.14 based sid-d-i netinst, once you are at the partitioning step, go to console 2, mount your root partition, chroot into it, mount /proc and /sys, and dpkg-reconfigure linux-image-2.6.14-2-k7. The other alternative is to install initramfs-tools, which knows how to install from a 2.4 kernel. I prefer using yaird myself though. Is this what the upgrade path from sarge will look like for etch (assuming here that etch will go up to 2.6.14, or will that not happen at all?). No, but we are still far from the sarge release (which is scheduled for december 2006, with freeze in july or so), and we probably will have to move to having initramfs-tools the first default for it. Maybe the best idea would be to have yaird as first default as now, but have the dependencies install both, which would guarantee it always works. In general, why not simply change the depends to have the whole thing Just Work in the general case? Well, at 2.6.14 release time, initramfs-tools, and his klibc dependency, had some maturation problems, and is also regularly broken by udev, so for now, yaird, provided it works, is still the more solid solution, and at least it will fail cleanly, and give you an error message or such, while initramfs-tools may or not fail during boot time. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
