Debian Bug report logs - #336418
kernel-package: no suitable ramdisk generation tool w/ 2.6.14

version graph

Package: kernel-package; Maintainer for kernel-package is Manoj Srivastava <>; Source for kernel-package is src:kernel-package.

Reported by: "Edward J. Shornock" <>

Date: Sun, 30 Oct 2005 06:33:03 UTC

Severity: normal

Tags: fixed-in-experimental

Found in version kernel-package/9.008.4

Fixed in version kernel-package/10.011

Done: Manoj Srivastava <>

Bug is archived. No further changes may be made.

Toggle useless messages

View this report as an mbox folder, status mbox, maintainer mbox

Report forwarded to, Manoj Srivastava <>:
Bug#336418; Package kernel-package. Full text and rfc822 format available.

Acknowledgement sent to "Edward J. Shornock" <>:
New Bug report received and forwarded. Copy sent to Manoj Srivastava <>. Full text and rfc822 format available.

Message #5 received at (full text, mbox):

From: "Edward J. Shornock" <>
To: Debian Bug Tracking System <>
Subject: kernel-package: no suitable ramdisk generation tool w/ 2.6.14
Date: Sun, 30 Oct 2005 01:28:41 -0500
[Message part 1 (text/plain, inline)]
Package: kernel-package
Version: 9.008.4
Severity: normal

When installing a newly built kernel, I received the following error

# dpkg -i linux-image-2.6.14-1-k7_workstation.1_i386.deb
Selecting previously deselected package linux-image-2.6.14-1-k7.
(Reading database ... 173674 files and directories currently installed.)
Unpacking linux-image-2.6.14-1-k7 (from linux-image-2.6.14-1-k7_workstation.1_i386.deb) ...

You are attempting to install an initrd kernel image (version
2.6.14-1-k7) while running a kernel of version 2.6.14-rc4-1-k7, but
you have no suitable ramdisk generation tool installed among
/usr/sbin/mkinitrd /usr/sbin/mkinitrd.yaird /usr/sbin/mkinitramfs.  This will break the installation, unless a
suitable ramdisk generation tool is also being installed right

Could not find . at /var/lib/dpkg/ line 228.
Setting up linux-image-2.6.14-1-k7 (workstation.1) ...
Failed to find suitable ramdisk generation tool for kernel version 2.6.14-1-k7 on running kernel 2.6.14-rc4-1-k7 in /usr/sbin/mkinitrd /usr/sbin/mkinitrd.yaird /usr/sbin/mkinitramfs
dpkg: error processing linux-image-2.6.14-1-k7 (--install):
 subprocess post-installation script returned error exit status 2
Errors were encountered while processing:

/usr/sbin/mkinitrd DOES exist on the system.

$ ls -l /usr/sbin/mkinitrd
-rwxr-xr-x  1 root root 29308 2005-10-24 03:09 /usr/sbin/mkinitrd

After installing yaird, I was able to install the kernel. 

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.14-rc4-1-k7
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)

Versions of packages kernel-package depends on:
ii  dpkg                package maintenance system for Deb
ii  dpkg-dev                     1.13.11     package building tools for Debian
ii  gcc [c-compiler]             4:4.0.2-1   The GNU C compiler
ii  gcc-3.3 [c-compiler]         1:3.3.6-10  The GNU C compiler
ii  gcc-4.0 [c-compiler]         4.0.2-3     The GNU C compiler
ii  make                         3.80-11     The GNU version of the "make" util
ii  perl                         5.8.7-7     Larry Wall's Practical Extraction 

Versions of packages kernel-package recommends:
ii  bzip2                         1.0.2-10   high-quality block-sorting file co
ii  libc6-dev [libc-dev]          2.3.5-7    GNU C Library: Development Librari

-- no debconf information
[signature.asc (application/pgp-signature, inline)]

Information forwarded to
Bug#336418; Package kernel-package. Full text and rfc822 format available.

Acknowledgement sent to Manoj Srivastava <>:
Extra info received and forwarded to list. Full text and rfc822 format available.

Message #10 received at (full text, mbox):

From: Manoj Srivastava <>
To: "Edward J. Shornock" <>
Subject: Re: Bug#336418: kernel-package: no suitable ramdisk generation tool w/ 2.6.14
Date: Sun, 30 Oct 2005 08:39:48 -0600
tags 336418 + fixed-in-experimental


        This is not a bug. initrd-tools are not viable post
 2.6.12. Unfortunately,  the version of kernel-package in Sid does not
 correctly modify the Depends: line. The Version in experimental  does

Depends: yaird (>= 0.0.11-8) | linux-initramfs-tools, coreutils | fileutils (>= 4.0)
 Suggests: lilo (>= 19.1) | grub, fdutils, linux-doc-2.6.14-skas3-v9-pre7 | linux-source-2.6.14-skas3-v9-pre7
 Provides: linux-image, linux-image-2.6

Man is demolishing nature ... We are killing things that keep us
alive. Thor Heyerdahl
Manoj Srivastava   <>  <>
1024D/BF24424C print 4966 F272 D093 B493 410B  924B 21BA DABB BF24 424C

Tags added: fixed-in-experimental Request was from Manoj Srivastava <> to Full text and rfc822 format available.

Reply sent to Manoj Srivastava <>:
You have taken responsibility. Full text and rfc822 format available.

Notification sent to "Edward J. Shornock" <>:
Bug acknowledged by developer. Full text and rfc822 format available.

Message #17 received at (full text, mbox):

From: Manoj Srivastava <>
Subject: These bugs are now fixed in the version in unstable
Date: Fri, 02 Dec 2005 18:17:49 -0600
Package: kernel-package
Version: 10.011

kernel-package (10.011) unstable; urgency=low

  * Bug fix: "DEBIAN/ directory doesn't appear to exist at
    image_clean_hook time", thanks to Don Armstrong. Moved the hooks for
    image and headers later in the process.              (Closes: #339659).
  * Bug fix: "kernel-package: kernel-image-deb mentioned in README.gz but
    removed in 10.x", thanks to Marc Haber. Well. The new name is
    stamp-kernel-image. Changed docs, and added kernel-image-deb
    temporarily as an alias.                             (Closes: #340978).

 -- Manoj Srivastava <>  Thu,  1 Dec 2005 15:30:27 -0600

kernel-package (10.010) experimental; urgency=low

  * Bug fix: "kernel-package: Fails to build ppc64 2.6.14 kernel", thanks
    to Juergen Kreileder. Sven Luther provided the patch (Closes: #338449).

 -- Manoj Srivastava <>  Thu, 10 Nov 2005 21:47:09 -0600

kernel-package (10.009) experimental; urgency=low

  * The long obsolete --flavour option is now gone, and --apend-to-version
    should be used. Also, --append-to-version may soon be superceded with
    --abi, stay tuned.
  * Speed up the stripping code in kernel header packages, by only looking
    at the scripts directory (which was the only place with the elf

 -- Manoj Srivastava <>  Wed,  9 Nov 2005 22:55:55 -0600

kernel-package (10.008) experimental; urgency=low

  * Well, it turns out that only on some architectures do we havea binary
    using a dynamically loaded shared library, so the call to dpkg-shlibs
    was failing on the others. Now, go throug a complex dance in which we 
    either call dpkg-shlibs, or edit the control file using Perl, so that
    both cases can be catered to.

 -- Manoj Srivastava <>  Tue,  8 Nov 2005 08:51:08 -0600

kernel-package (10.007) experimental; urgency=low

  * Aaargh, typo in the kernel header rules.
  * The generated packages should not have native version numbers by
    default, since they are not really debain native packages. The problem
    was that the default version generated did not have a -, so chnaged
    that value. The files affected are kernel-pkg.conf, README, 
    kernel/ruleset/misc/ , kernel-pkg.conf.5,
    kernel/docs/README,  kernel/ruleset/misc/ 
  * While looking at Lintian errors, I noticed that apparently
    kernel-headers package carries with it an elf binary, and thus should
    depend on the shared libraries -- but did not. Fixed now by a search
    and a call to dpkg-shlibs. Various minor nitpicks in the default
    Control file also fixed.
  * We also added a make snippet to find and strip the binaries we need to
    run  dpkg-shlibs upon, since that is the policy.
  * kernel/ruleset/targets/ Export the variable IMAGE_TOP before
    calling scripts in $(SRCTOP)/debian/image.d and debian/post-install,
    since that is what they expected. Bad idea changing an exposed
  * kernel/pkg/image/postrm:  Call purge to remove the questions from
    debconf database when the package is purged. 

 -- Manoj Srivastava <>  Tue,  8 Nov 2005 01:03:49 -0600

kernel-package (10.006) experimental; urgency=low

  * Hmm. We need to take special care of the case in which the
    kernel-headers are installed after the kernel-image has been; and the
    build symlink is not setr. In this case, the header postinst now
    correctly installs the build symlink.

 -- Manoj Srivastava <>  Mon,  7 Nov 2005 12:44:21 -0600

kernel-package (10.005) experimental; urgency=low

  * Bug fix: "kernel/image.postinst should mention GRUB", thanks to
    Martin Michlmayr. Well, I don't see why we should mention _any_ boot
    loader at all, so we are no longer biased against grub. (Closes: #336927)
  * Bug fix: "kernel-package: Using dpkg --remove followed by dpkg
    --install does not restore the kernel package", thanks to Daniel
    Jacobowitz. Also: "kernel-package tells me we're being reinstalled AND
    updated". Actually, the installed/updated is just sematics; when you
    reinstall a kernel image you are updating it, and vice versa. The
    actual problem was that while the symbolic links were removed when the
    package was removed, dpkg passed the last-version-configured to the
    postinst, and we took that as evidence that the package had been
    installed before -- which, while true, did not take into account that
    the package was currently uninstalled. The fix is to always see if a
    missing symlink needs to be installed, and not touch existing
    symlinks.                                       (Closes: #336733,  #336517).
  * Added kernel/pkg/headers/create_link as an example. The user can install
    it in the postinst.d directory to set up the /lib/modules/foo/build
    symlink to point to the kernel-headers. This is not needed, since the
    kernel-image postinst already checks in the /usr/src/ directory for an
    installed kernel headers package.
  * Convert the image prerm scripts to debconf as well, the questions are
    asked if we try to remove the running kernel image, or if we are
    removing a kernel version mentioned in boot loader configuration.
  * Have the not overwrite the control or the changelog file. 
  * Added a whole slew of config files, and updated older ones, to bring
    the configurations offered up by default to be more in line with
    official kernels.
  * Fixed substitutions in the kernel image package, there was a duplicate
    =B substitution. 
  * Ran lintian on all the generated packages. Fixed FSF address in all
    the copyright notices, and fixed case in the templates file as
    well. This shall be the last experimental release, barring major

 -- Manoj Srivastava <>  Mon,  7 Nov 2005 10:44:39 -0600

kernel-package (10.004) experimental; urgency=low

  * Bug fix: "using debconf", thanks to Robert Millan      (Closes: #115884)
  * Bug fix: "does not install non-interactively", thanks to Matt Kraai
                                                           (Closes: #247782)
  * This fine tunes the dependencies between targets. All of the package
    building targets are ones that insert themselves into the normal flow
    of policy specified targets, so they must hook themselves into the
    stream. That means, in essence, that they must depend on the configure
    and  corresponding build targets (with stamps) and ensure that the
    prep work is all done before they are invoked. The advantage is that
    nothing is going to be remade more often than it needs to. It also
    means we do not need to produce as many stamp files. So, the only
    dependencies on any of the intermediate targets are targets that have
    not been registered into the ladder created in rulesets/common/
  * The kernel image maintainer scripts have been greatly
    changed. Firstly, they now use  debconf; and a number of questions
    have been moved to the config file (create-kimage-link-$version,
    old-initrd-link, old-dir-initrd-link, old-system-map-link) while
    others are asked conditionally in the postinst (depmod-error,
    depmod-error-initrd, bootloader-test-error, bootloader-error). The
    postinst has also become far less verbose; the users are far better
    educated a decade after this was written, and there are other sources
    of information about booting than the postinst of a kernel image.
  * The preinst also uses debconf. All the questions asked are still here
    -- we just use debconf to ask the user. Also, the priority, and need
    to break non-interactive installs was re-evaluated, and the preinst
    breaks in far fewer cases than it did before. 
  * Second, the postinst gets rid of the code that generated boot floppies
    and created lilo.conf (that latter was probably illegal under current
    policy anyway). The do_boot_enable and do_boot_floppy configuration
    variables in /etc/kernel-img.conf are now invalid.
  * Also, the source tree is not automatically cleaned; the do_clean
    configuration variable, and the environment variable CLEAN_SOURCE are
    now control if the source tree is optionally cleaned after the kernel
    image package is built.

 -- Manoj Srivastava <>  Thu,  3 Nov 2005 23:26:29 -0600

kernel-package (10.003) experimental; urgency=low

  * Bug fix: "can not clean up the kernel source tree", thanks to           
    Chun-Chung Chen.                                         (Closes: #336409)
  * Bug fix: "kernel-package creates packages depending on
    linux-initramfs-tools, should use linux-initramfs-tool", thanks to
    Thomas  Luzat.                                           (Closes: #336724)
  * Bug fix: "/usr/share/doc/kernel-package seems to contain broken
    symlinks", thanks to Thomas Luzat                        (Closes: #336744)
  * This is a major reorganization of the rules file that helps
    create kernel related packages. The crusty old mechanism has been
     removed, the targets are now streamlined, and the policy mandated
     dependencies are now called out into a separate file. This should allow
     a future enhancement to allow end users to override the behavior of
     kernel-package in a fine grained fashion. Also, separating out the
     variable setting for each arch into a separate file should facilitate
     the delegation of that file to the person responsible for kernel images
     for that architecture. And, separating out the policy mandated targets
     into fine grained double colon targets allows people to add in any
     additional make targets for a particular architecture, something long
            One of the factors that made the build mechanism so complex was
     that the rules file had a dual purpose: Initially, when ./debian was not
     present or not populated, it was responsible for populating that, and
     then it was responsible for building the kernel packages, incorporating
     any user customizations.
            Unfortunately, since Make reads all the commands at startup, it
     was difficult to incorporate any customizations, but the modularization
     of the rules file makes it possible to have two top level files, a
     minimal make file whose sole responsibility is to populate ./debian (and
     run clean even when ./debian does not exist), and which uses some of the
     same variable setting make snippets that the final top level Make file
     uses when it resides in ./debian. The task of deciding which top level
     makefile to use has now been relegated to /usr/bin/make-kpkg -- which,
     if there ./debian is empty or not present, first calls the minimal
     Makefile to populate it, and _then_ calls the real ./debian/rules file
     to perform the actual task that it was asked. This little intelligence
     in make-kpkg allows the minimal makefile, and ./debian/rules, to be far
     simpler, and allows them to conform to the standards my other Debian
     packages adhere to.
            The goal of this release was to handle the bugs in the previous
     experimental release, but to create a set of packages indistinguishable
     from the ones created before. Pointedly, non-of the minor lacunae in the
     Debian kernel image postinst scripts have been addressed yet. Also, the
     build process is a little more verbose at the moment than it needs to be.

 -- Manoj Srivastava <>  Wed,  2 Nov 2005 14:16:19 -0600

kernel-package (10.002) experimental; urgency=low

  * Bug fix: "kernel-package: Problem with causes build
    fauilure", thanks to Horms                               (Closes: #335993).
  * This is a fairly large reorganization of the directory and file layout
    for the package. Instead of a mostly flat directory structure with a
    giant monolithic rules files, we are moving towards a more organized
    structure, with finer granularity of files, which may in the future
    facilitate third party replacement and overriding of parts of the build
    mechanism. Also, this reorganization may make the overall structure
    easier to see (though it may also result in it being harder to get the
    big picture, but I doubt that).

    This time around, I am trying to keep substantive changes to a minimum,
    so files have just been broken up, moved around, but the package should
    still more or less behave the way that it always did (apart from changing
    the stem).
    * kernel/rules (DEBDIR): Test to see if we have
      ./debian/, since all kinds of other people create
   * Makefile (install): Adjust for the reorganization of the files, since
     the source files are no longer in their previous locations. Keep the
     destination mostly the same.
   * kernel/rules: This is the one file that has faced the brunt of the
     changes. Large chunks of it have been moved out into separate chunks
     included in this file. The major addition has been are mechanisms to
     allow the file to be broken up. The parts removed are
      o) dpkg-architecture variable are now moved out to
      o) The variables set in the file have mostly been moved to
         ruleset/, which shall be further broken up into
         smaller parts
      o) For example, the per arch variable settings have already been moved
         out of  ruleset/ into ruleset/ -- and
         shall be further fragmented into files in ruleset/arches/, so that
         it would be easier to delegate ownership to domain experts.
      o) The action/rules part of the file have been broken out to
         ruleset/ -- and shall be broken out into
         ruleset/common/ (which contain policy mandated targets,
         and their dependencies, and ruleset/, where the
         grunt work shall be done. It may make sense to further divide
         ruleset/ into separate files for images, headers,
         doc, and manual packages. At a later stage, actually installing
         files into ./debian/tmp-<something> shall be separated out from the
         subsequent packaging into separate targets (probably in the same
         file), to allow finer granularity for debugging.

 -- Manoj Srivastava <>  Fri, 28 Oct 2005 09:03:41 -0500

kernel-package (10.001) experimental; urgency=low

  * Bug fix: "doesn't install: Internal Error: Could not find image
    (/boot/vmlinuz-2.4.27-xxs1500)", thanks to Martin Michlmayr. Well,
    calling kimage vmlinux.srec was breaking the postinst. However, kimage
    does not seem to be used anywhere except in determining the next
    value, namely, kimagesrc -- so I just added .srec to  kimagesrc, and
    thus eliminated the need for hacking the postinst. So the fix was
    earlier in the build process, and not deferred to the postinst.
                                                          (Closes: #333220).
  * Acknowledge the changes made for initrd stuff in the NMU
    series. Thanks to Sven Luther for the work. I have made some changes,
    for example, instead of hard-coding the list of initrd tools one
    considers in the installation phase, now one can set that list by
    editing /etc/kernel-pkg.conf -- and this replaces the hard coded
    list. Of course, the admin at the target location can still over-ride
    that list by editing /etc/kernel-img.con (note, not the same as
    /etc/kernel-pkg.conf above); this makes things slightly more
    flexible. Also, the list of commands does not have to be the fully
    qualified path, the postinst and preinst use the PATH variable to find
    the commands.
  * kernel-img.conf.5: Document the fact that the ramdisk variable can now
    be a space separated list of init ram disk creation commands, which
    need to also support the --supported-host-version and
    --supported-target-version options, just like mkinitrd does. This is
    the list tried at installation time.
  * kernel-pkg.conf.5: Document the fact that one can provide the default
    values for the list by setting INITRD_CMD, but this list can be
    overridden by the one in kernel-img.conf.5. However, the defaults are
    set to a subset of "mkinitrd mkinitrd.yaird mkinitramfs", the subset
    being decided based on the version of the kernel being built, so one
    should refrain from setting this manually -- unless one knows what one
    is doing.
  * kernel/image.postrm, kernel/image.prerm: Added new variable for the
    initrd dependency, and also modified the variable ramdisk to be a
    space separated list of commands, not just a single command.
  * kernel/image.postinst, kernel/image.preinst: Added new variable for
    the initrd dependency, and also modified the variable ramdisk to be a
    space separated list of commands, not just a single
    command. (find_inird_tool): Added function to determine the list of
    viable initrd creation tools present on the target system, and use it
    to select which tool to use for creating the ram fs.
  * Bug fix: "'man make-kpkg' typo: 'thatthis'", thanks to A
    Costa                                                    (Closes: #335316).

 -- Manoj Srivastava <>  Tue, 25 Oct 2005 04:00:35 -0500

"I go on working for the same reason a hen goes on laying eggs."
Manoj Srivastava   <>  <>
1024D/BF24424C print 4966 F272 D093 B493 410B  924B 21BA DABB BF24 424C

Bug archived. Request was from Debbugs Internal Request <> to (Sun, 24 Jun 2007 18:42:53 GMT) Full text and rfc822 format available.

Send a report that this bug log contains spam.

Debian bug tracking system administrator <>. Last modified: Fri Apr 18 10:59:18 2014; Machine Name:

Debian Bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.