Bug#522909: linux-image-2.6.29-1-amd64: Package cannot be configured due to invalid mkinitrd options)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dear maximilian, On Tue, Apr 07, 2009 at 06:46:15PM +0200, maximilian attems wrote: >won't comment any further on your personal opinons. [further comments on my opinions snipped] I have commented on your personal opinions presented as fact. Have a nice day. - Jonas - -- * Jonas Smedegaard - idealist og Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAknbrTAACgkQn7DbMsAkQLi2FACgnB8moZrIPhEe5K5XqesWN4C/ Yp0An1Cw1BCG7bnmf3TnvTM2va696mu4 =o6VV -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#522909: closed by maximilian attems (Re: Bug#522909: linux-image-2.6.29-1-amd64: Package cannot be configured due to invalid mkinitrd options)
dear jonas, On Tue, Apr 07, 2009 at 05:53:05PM +0200, Jonas Smedegaard wrote: > On Tue, Apr 07, 2009 at 05:28:03PM +0200, Frank Blendinger wrote: > >Hi. > > > >On Tue 2009-04-07 12:15, Debian Bug Tracking System > > proclaimed: > >> > On Tue 2009-04-07 13:31, maximilian attems proclaimed: > >> > > On Tue, Apr 07, 2009 at 01:27:45PM +0200, Frank Blendinger wrote: > >> > > > ramdisk=mkinitrd.yaird mkinitramfs > >> > > > >> > > well that is wrong, easiest way is to just scratch that last line. > >> > > >> > Indeed. It works fine without that line. > >> > >> this line was added in a special debian installer beta for Etch. > >> it was quickly repaired to not been added. > >> the trouble is that /etc/kernel-img.conf is not owned by any package > >> so we are not allowed to modify it. > >> > >> As aboves failure never slipped in a real realease > >> it is a bit unfortunate for the users of that specific debian installer > >> release. > > > >Ah, then it is clear where it came from - I installed the system in > >question with an RC of the Lenny installer. > > Hmm. I disagree that it was "repaired". Instead it was at some point > changed to favor initramfs-tools over yaird - while still supporting > both. > > If, as Max wrote, debian-installer was changed shortly after some beta > for Etch, it seems odd to me that you experience this issue in a RC for > Lenny: Etch was released some years before Lenny. won't comment any further on your personal opinons. fact is that yaird never was default for any linux-2.6 testing image and aboves line was completly false due to the usage of mkinitramfs instead of update-initramfs (maybe mkinitramfs-kpkg for lenny). anyway this story is closed and i will refrain to repeat myself or post any followup even if your allegations get even stranger. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#522909: closed by maximilian attems (Re: Bug#522909: linux-image-2.6.29-1-amd64: Package cannot be configured due to invalid mkinitrd options)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, Apr 07, 2009 at 05:28:03PM +0200, Frank Blendinger wrote: >Hi. > >On Tue 2009-04-07 12:15, Debian Bug Tracking System > proclaimed: >> > On Tue 2009-04-07 13:31, maximilian attems proclaimed: >> > > On Tue, Apr 07, 2009 at 01:27:45PM +0200, Frank Blendinger wrote: >> > > > ramdisk=mkinitrd.yaird mkinitramfs >> > > >> > > well that is wrong, easiest way is to just scratch that last line. >> > >> > Indeed. It works fine without that line. >> >> this line was added in a special debian installer beta for Etch. >> it was quickly repaired to not been added. >> the trouble is that /etc/kernel-img.conf is not owned by any package >> so we are not allowed to modify it. >> >> As aboves failure never slipped in a real realease >> it is a bit unfortunate for the users of that specific debian installer >> release. > >Ah, then it is clear where it came from - I installed the system in >question with an RC of the Lenny installer. Hmm. I disagree that it was "repaired". Instead it was at some point changed to favor initramfs-tools over yaird - while still supporting both. If, as Max wrote, debian-installer was changed shortly after some beta for Etch, it seems odd to me that you experience this issue in a RC for Lenny: Etch was released some years before Lenny. - Jonas - -- * Jonas Smedegaard - idealist og Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAknbduAACgkQn7DbMsAkQLhmeQCdEGuHnzmT8GqxmDfWgovO2uf0 IOAAniEeCEujRQ5/MQYqmrBdT22v5bPG =MyBx -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#522909: closed by maximilian attems (Re: Bug#522909: linux-image-2.6.29-1-amd64: Package cannot be configured due to invalid mkinitrd options)
Hi. On Tue 2009-04-07 12:15, Debian Bug Tracking System proclaimed: > > On Tue 2009-04-07 13:31, maximilian attems proclaimed: > > > On Tue, Apr 07, 2009 at 01:27:45PM +0200, Frank Blendinger wrote: > > > > ramdisk=mkinitrd.yaird mkinitramfs > > > > > > well that is wrong, easiest way is to just scratch that last line. > > > > Indeed. It works fine without that line. > > this line was added in a special debian installer beta for Etch. > it was quickly repaired to not been added. > the trouble is that /etc/kernel-img.conf is not owned by any package > so we are not allowed to modify it. > > As aboves failure never slipped in a real realease > it is a bit unfortunate for the users of that specific debian installer > release. Ah, then it is clear where it came from - I installed the system in question with an RC of the Lenny installer. Greetings, Frank -- Frank Blendinger | fb(at)intoxicatedmind.net | GPG: 0x0BF2FE7A Fingerprint: BB64 F2B8 DFD8 BF90 0F2E 892B 72CF 7A41 0BF2 FE7A signature.asc Description: Digital signature
Bug#522909: linux-image-2.6.29-1-amd64: Package cannot be configured due to invalid mkinitrd options
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, Apr 07, 2009 at 01:54:05PM +0200, Frank Blendinger wrote: >Hi. > >On Tue 2009-04-07 13:31, maximilian attems proclaimed: >> On Tue, Apr 07, 2009 at 01:27:45PM +0200, Frank Blendinger wrote: >> > > post the output of >> > > cat /etc/kernel-img.conf >> > >> > # Kernel image management overrides >> > # See kernel-img.conf(5) for details >> > do_symlinks = yes >> > relative_links = yes >> > do_bootloader = no >> > do_bootfloppy = no >> > do_initrd = yes >> > link_in_boot = no >> > ramdisk=mkinitrd.yaird mkinitramfs >> >> well that is wrong, easiest way is to just scratch that last line. > >Indeed. It works fine without that line. What Max suggests above is to stop favoring yaird, and instead use the default one (initramfs-tools). If you have no interest in using a specific ramdisk tool, then I agree that you can *avoid* this bug by not explicitly using a ramdisk generator that triggers the bug. Above config file of yours is not "wrong", however. ...or more precisely it is not wrong to have "yaird" in that line - it might be wrong to use "mkinitramfs" (use "mkinitramfs-kpkg" instead) but that is a different issue which does not relate to the currently discussed bug. >> longer explanation >> * yaird doesn't fully implement update-initramfs compat syntax >> so can no longer install any linux image since 2.6.28 >> #518315 If you read that bugreport you will notice the lack of response from the kernel team on the questions raised there. >> (beside beeing not recommended, not distributed in Lenny, buggy >>in many ways, not developed anymore and thus deprecated) The package maintainer of initramfs-tools (Max) do not recommend the use of the alternative ramdisk tool yaird. Yaird is bugy in *different* ways than initramfs-tools. Yaird is still developed. Please do not spread FUD! >> * mkinitramfs was never the direct wrapper to call >> previously in lenny you could have had mkinitramfs-kpkg >> in aboves line. >> now you want update-initramfs that is the upper layer >> and the recommended command to generat an initramfs >> since at least etch. > >Thanks for the explanation. Would you recommend purging yaird >completely then? I maintain yaird, and I do not recommend purging it. I depend on it for server installations that need a different degree of reliability than the default ramdisk generator, initramfs-tools, can provide. I am not the only user of yaird. Max obviously has a different opinion, as indicated by his filing http://bugs.debian.org/457177 blocking it from being released with Lenny. >After all, I am wondering how the line ended up in kernel-img.conf at >all. I never touched it myself (etckeeper helps my unreliable brain >here), so it has to be generated by some package, but I could not find >which one it is. Do you happen to know that? Should a bug against that >package be filed? Again, it is not a bug to have that line. Debian-installer at some point favored yaird over initramfs-tools. Hope that helps, - Jonas - -- * Jonas Smedegaard - idealist og Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAknbUvEACgkQn7DbMsAkQLhVWACfWZB91ZwP3rHGbIZ41eD3QpuF sIoAnRHixJkNqyiTynSbwSMArdOUpdyZ =DV9B -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#522909: linux-image-2.6.29-1-amd64: Package cannot be configured due to invalid mkinitrd options
Hi. On Tue 2009-04-07 13:31, maximilian attems proclaimed: > On Tue, Apr 07, 2009 at 01:27:45PM +0200, Frank Blendinger wrote: > > > post the output of > > > cat /etc/kernel-img.conf > > > > # Kernel image management overrides > > # See kernel-img.conf(5) for details > > do_symlinks = yes > > relative_links = yes > > do_bootloader = no > > do_bootfloppy = no > > do_initrd = yes > > link_in_boot = no > > ramdisk=mkinitrd.yaird mkinitramfs > > well that is wrong, easiest way is to just scratch that last line. Indeed. It works fine without that line. > longer explanation > * yaird doesn't fully implement update-initramfs compat syntax > so can no longer install any linux image since 2.6.28 > #518315 > (beside beeing not recommended, not distributed in Lenny, buggy >in many ways, not developed anymore and thus deprecated) > > * mkinitramfs was never the direct wrapper to call > previously in lenny you could have had mkinitramfs-kpkg > in aboves line. > now you want update-initramfs that is the upper layer > and the recommended command to generat an initramfs > since at least etch. Thanks for the explanation. Would you recommend purging yaird completely then? After all, I am wondering how the line ended up in kernel-img.conf at all. I never touched it myself (etckeeper helps my unreliable brain here), so it has to be generated by some package, but I could not find which one it is. Do you happen to know that? Should a bug against that package be filed? Greetings, Frank -- Frank Blendinger | fb(at)intoxicatedmind.net | GPG: 0x0BF2FE7A Fingerprint: BB64 F2B8 DFD8 BF90 0F2E 892B 72CF 7A41 0BF2 FE7A signature.asc Description: Digital signature
Bug#522909: linux-image-2.6.29-1-amd64: Package cannot be configured due to invalid mkinitrd options
On Tue, Apr 07, 2009 at 01:27:45PM +0200, Frank Blendinger wrote: > > post the output of > > cat /etc/kernel-img.conf > > # Kernel image management overrides > # See kernel-img.conf(5) for details > do_symlinks = yes > relative_links = yes > do_bootloader = no > do_bootfloppy = no > do_initrd = yes > link_in_boot = no > ramdisk=mkinitrd.yaird mkinitramfs well that is wrong, easiest way is to just scratch that last line. longer explanation * yaird doesn't fully implement update-initramfs compat syntax so can no longer install any linux image since 2.6.28 #518315 (beside beeing not recommended, not distributed in Lenny, buggy in many ways, not developed anymore and thus deprecated) * mkinitramfs was never the direct wrapper to call previously in lenny you could have had mkinitramfs-kpkg in aboves line. now you want update-initramfs that is the upper layer and the recommended command to generat an initramfs since at least etch. kind regards -- maks -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#522909: linux-image-2.6.29-1-amd64: Package cannot be configured due to invalid mkinitrd options
On Tue, Apr 07, 2009 at 12:49:55PM +0200, Frank Blendinger wrote: > Package: linux-image-2.6.29-1-amd64 > Version: 2.6.29-2 > Severity: important > > Installation of the packages fails with the following output: > > Reading package lists... Done > Building dependency tree > Reading state information... Done > Reading extended state information > Initializing package states... Done > Reading task descriptions... Done > The following partially installed packages will be configured: > linux-image-2.6.29-1-amd64 > 0 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded. > Need to get 0B of archives. After unpacking 0B will be used. > Writing extended state information... Done > Setting up linux-image-2.6.29-1-amd64 (2.6.29-2) ... > Running depmod. > Running mkinitrd.yaird. > Other valid candidates: mkinitrd.yaird mkinitramfs > mkinitrd.yaird: invalid option -- 't' > Terminating... > mkinitrd.yaird failed to create initrd image. > Running mkinitramfs. > Other valid candidates: mkinitrd.yaird mkinitramfs > /usr/sbin/mkinitramfs: invalid option -- 'c' > /usr/sbin/mkinitramfs: invalid option -- 't' > Terminating... > mkinitramfs failed to create initrd image. > Failed to create initrd image. > dpkg: error processing linux-image-2.6.29-1-amd64 (--configure): > subprocess post-installation script returned error exit status 2 > Errors were encountered while processing: > linux-image-2.6.29-1-amd64 > 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.29-1-amd64 (2.6.29-2) ... > Running depmod. > Running mkinitrd.yaird. > Other valid candidates: mkinitrd.yaird mkinitramfs > mkinitrd.yaird: invalid option -- 't' > Terminating... > mkinitrd.yaird failed to create initrd image. > Running mkinitramfs. > Other valid candidates: mkinitrd.yaird mkinitramfs > /usr/sbin/mkinitramfs: invalid option -- 'c' > /usr/sbin/mkinitramfs: invalid option -- 't' > Terminating... > mkinitramfs failed to create initrd image. > Failed to create initrd image. > dpkg: error processing linux-image-2.6.29-1-amd64 (--configure): > subprocess post-installation script returned error exit status 2 > Errors were encountered while processing: > linux-image-2.6.29-1-amd64 > Reading package lists... Done > Building dependency tree > Reading state information... Done > Reading extended state information > Initializing package states... Done > Reading task descriptions... Done post the output of cat /etc/kernel-img.conf -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#522909: linux-image-2.6.29-1-amd64: Package cannot be configured due to invalid mkinitrd options
Hi. On Tue 2009-04-07 13:19, maximilian attems proclaimed: > On Tue, Apr 07, 2009 at 12:49:55PM +0200, Frank Blendinger wrote: > > Package: linux-image-2.6.29-1-amd64 > > Version: 2.6.29-2 > > Severity: important > > > > Installation of the packages fails with the following output: > > [...] > > post the output of > cat /etc/kernel-img.conf # Kernel image management overrides # See kernel-img.conf(5) for details do_symlinks = yes relative_links = yes do_bootloader = no do_bootfloppy = no do_initrd = yes link_in_boot = no ramdisk=mkinitrd.yaird mkinitramfs Greetings, Frank -- Frank Blendinger | fb(at)intoxicatedmind.net | GPG: 0x0BF2FE7A Fingerprint: BB64 F2B8 DFD8 BF90 0F2E 892B 72CF 7A41 0BF2 FE7A signature.asc Description: Digital signature
Bug#522909: linux-image-2.6.29-1-amd64: Package cannot be configured due to invalid mkinitrd options
Package: linux-image-2.6.29-1-amd64 Version: 2.6.29-2 Severity: important Installation of the packages fails with the following output: Reading package lists... Done Building dependency tree Reading state information... Done Reading extended state information Initializing package states... Done Reading task descriptions... Done The following partially installed packages will be configured: linux-image-2.6.29-1-amd64 0 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 0B of archives. After unpacking 0B will be used. Writing extended state information... Done Setting up linux-image-2.6.29-1-amd64 (2.6.29-2) ... Running depmod. Running mkinitrd.yaird. Other valid candidates: mkinitrd.yaird mkinitramfs mkinitrd.yaird: invalid option -- 't' Terminating... mkinitrd.yaird failed to create initrd image. Running mkinitramfs. Other valid candidates: mkinitrd.yaird mkinitramfs /usr/sbin/mkinitramfs: invalid option -- 'c' /usr/sbin/mkinitramfs: invalid option -- 't' Terminating... mkinitramfs failed to create initrd image. Failed to create initrd image. dpkg: error processing linux-image-2.6.29-1-amd64 (--configure): subprocess post-installation script returned error exit status 2 Errors were encountered while processing: linux-image-2.6.29-1-amd64 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.29-1-amd64 (2.6.29-2) ... Running depmod. Running mkinitrd.yaird. Other valid candidates: mkinitrd.yaird mkinitramfs mkinitrd.yaird: invalid option -- 't' Terminating... mkinitrd.yaird failed to create initrd image. Running mkinitramfs. Other valid candidates: mkinitrd.yaird mkinitramfs /usr/sbin/mkinitramfs: invalid option -- 'c' /usr/sbin/mkinitramfs: invalid option -- 't' Terminating... mkinitramfs failed to create initrd image. Failed to create initrd image. dpkg: error processing linux-image-2.6.29-1-amd64 (--configure): subprocess post-installation script returned error exit status 2 Errors were encountered while processing: linux-image-2.6.29-1-amd64 Reading package lists... Done Building dependency tree Reading state information... Done Reading extended state information Initializing package states... Done Reading task descriptions... Done -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.28 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages linux-image-2.6.29-1-amd64 depends on: ii debconf [debconf-2.0] 1.5.26 Debian configuration management sy ii initramfs-tools [linux-initra 0.93.2 tools for generating an initramfs ii module-init-tools 3.7-pre9-1 tools for managing Linux kernel mo ii yaird [linux-initramfs-tool] 0.0.13-5 Yet Another mkInitRD linux-image-2.6.29-1-amd64 recommends no packages. Versions of packages linux-image-2.6.29-1-amd64 suggests: ii grub 0.97-53GRand Unified Bootloader (Legacy v pn linux-doc-2.6.29 (no description available) -- Frank Blendinger | fb(at)intoxicatedmind.net | GPG: 0x0BF2FE7A Fingerprint: BB64 F2B8 DFD8 BF90 0F2E 892B 72CF 7A41 0BF2 FE7A signature.asc Description: Digital signature
