Your message dated Tue, 7 Apr 2009 14:10:21 +0200 with message-id <20090407121021.GU3901@baikonur.stro.at> and subject line Re: Bug#522909: linux-image-2.6.29-1-amd64: Package cannot be configured due to invalid mkinitrd options has caused the Debian Bug report #522909, regarding linux-image-2.6.29-1-amd64: Package cannot be configured due to invalid mkinitrd options to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 522909: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=522909 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: linux-image-2.6.29-1-amd64: Package cannot be configured due to invalid mkinitrd options
- From: Frank Blendinger <fb@intoxicatedmind.net>
- Date: Tue, 7 Apr 2009 12:49:55 +0200
- Message-id: <[🔎] 20090407104643.31044.98401.reportbug@macbork.congress.ccc.de>
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-53 GRand Unified Bootloader (Legacy v pn linux-doc-2.6.29 <none> (no description available) -- Frank Blendinger | fb(at)intoxicatedmind.net | GPG: 0x0BF2FE7A Fingerprint: BB64 F2B8 DFD8 BF90 0F2E 892B 72CF 7A41 0BF2 FE7AAttachment: signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
- To: 522909-done@bugs.debian.org
- Subject: Re: Bug#522909: linux-image-2.6.29-1-amd64: Package cannot be configured due to invalid mkinitrd options
- From: maximilian attems <max@stro.at>
- Date: Tue, 7 Apr 2009 14:10:21 +0200
- Message-id: <20090407121021.GU3901@baikonur.stro.at>
- In-reply-to: <[🔎] 20090407115405.GS4047@intoxicatedmind.net>
- References: <[🔎] 20090407104643.31044.98401.reportbug@macbork.congress.ccc.de> <[🔎] 20090407111905.GR3901@baikonur.stro.at> <[🔎] 20090407112745.GR4047@intoxicatedmind.net> <[🔎] 20090407113143.GS3901@baikonur.stro.at> <[🔎] 20090407115405.GS4047@intoxicatedmind.net>
On Tue, Apr 07, 2009 at 01:54:05PM +0200, Frank Blendinger wrote: > Hi. > > On Tue 2009-04-07 13:31, maximilian attems <max@stro.at> 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. > Thanks for the explanation. Would you recommend purging yaird completely > then? yes. > 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? see aboves, thus closing. guess we would need a time machine. ;) kind regrads -- maks
--- End Message ---