Bug#564887: marked as done (two runs of update-initramfs per upgrade)
Your message dated Tue, 23 Mar 2010 23:46:24 +0100
with message-id <20100323224624.GA5481@stro.at>
and subject line Re: Bug#564887: two runs of update-initramfs per upgrade
has caused the Debian Bug report #564887,
regarding two runs of update-initramfs per upgrade
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.)
--
564887: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=564887
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: initramfs-tools
Version: 0.93.4
Severity: wishlist
Below we see two runs of
update-initramfs: Generating /boot/initrd.img-2.6.32-trunk-686
Or maybe even the doc file causes an extra run.
# aptitude full-upgrade
...
Setting up linux-image-2.6.32-trunk-686 (2.6.32-5) ...
Running depmod.
Running update-initramfs.
update-initramfs: Generating /boot/initrd.img-2.6.32-trunk-686
Running update-grub.
Updating /boot/grub/grub.cfg ...
Found linux image: /boot/vmlinuz-2.6.32-trunk-686
Found initrd image: /boot/initrd.img-2.6.32-trunk-686
Found linux image: /boot/vmlinuz-2.6.31-1-686
Found initrd image: /boot/initrd.img-2.6.31-1-686
done
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 2.6.32-trunk-686 /boot/vmlinuz-2.6.32-trunk-686
run-parts: executing /etc/kernel/postinst.d/pm-utils 2.6.32-trunk-686 /boot/vmlinuz-2.6.32-trunk-686
Setting up apt-utils (0.7.25.1) ...
Setting up firmware-linux-free (2.6.32-5) ...
Setting up libwebkit-1.0-2 (1.1.18-1) ...
Setting up linux-doc-2.6.32 (2.6.32-5) ...
Processing triggers for initramfs-tools ...
update-initramfs: Generating /boot/initrd.img-2.6.32-trunk-686
Processing triggers for python-support ...
-- Package-specific info:
-- /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-2.6.32-trunk-686 root=/dev/sda1 ro single
-- /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
postinst_hook = update-grub
postrm_hook = update-grub
-- /etc/initramfs-tools/initramfs.conf
MODULES=most
BUSYBOX=y
KEYMAP=n
BOOT=local
DEVICE=eth0
NFSROOT=auto
-- System Information:
Debian Release: squeeze/sid
APT prefers experimental
APT policy: (990, 'experimental'), (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.32-trunk-686 (SMP w/1 CPU core)
Locale: LANG=zh_TW.UTF-8, LC_CTYPE=zh_TW.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages initramfs-tools depends on:
ii cpio 2.10-1 GNU cpio -- a program to manage ar
ii findutils 4.4.2-1 utilities for finding files--find,
ii klibc-utils 1.5.15-1 small utilities built with klibc f
ii module-init-tools 3.11-1 tools for managing Linux kernel mo
ii udev 150-2 /dev/ and hotplug management daemo
Versions of packages initramfs-tools recommends:
pn busybox | busybox-initramfs <none> (no description available)
initramfs-tools suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
- To: 564887-done@bugs.debian.org
- Subject: Re: Bug#564887: two runs of update-initramfs per upgrade
- From: maximilian attems <max@stro.at>
- Date: Tue, 23 Mar 2010 23:46:24 +0100
- Message-id: <20100323224624.GA5481@stro.at>
- In-reply-to: <873a2bla22.fsf@jidanni.org>
- References: <873a2bla22.fsf@jidanni.org>
On Tue, 12 Jan 2010, jidanni@jidanni.org wrote:
> Package: initramfs-tools
> Version: 0.93.4
> Severity: wishlist
wrong package.
> Below we see two runs of
> update-initramfs: Generating /boot/initrd.img-2.6.32-trunk-686
>
> Or maybe even the doc file causes an extra run.
>
> # aptitude full-upgrade
> ...
> Setting up linux-image-2.6.32-trunk-686 (2.6.32-5) ...
> Running depmod.
> Running update-initramfs.
> update-initramfs: Generating /boot/initrd.img-2.6.32-trunk-686
> Running update-grub.
> Updating /boot/grub/grub.cfg ...
> Found linux image: /boot/vmlinuz-2.6.32-trunk-686
> Found initrd image: /boot/initrd.img-2.6.32-trunk-686
> Found linux image: /boot/vmlinuz-2.6.31-1-686
> Found initrd image: /boot/initrd.img-2.6.31-1-686
> done
> Examining /etc/kernel/postinst.d.
> run-parts: executing /etc/kernel/postinst.d/initramfs-tools 2.6.32-trunk-686 /boot/vmlinuz-2.6.32-trunk-686
> run-parts: executing /etc/kernel/postinst.d/pm-utils 2.6.32-trunk-686 /boot/vmlinuz-2.6.32-trunk-686
> Setting up apt-utils (0.7.25.1) ...
> Setting up firmware-linux-free (2.6.32-5) ...
> Setting up libwebkit-1.0-2 (1.1.18-1) ...
> Setting up linux-doc-2.6.32 (2.6.32-5) ...
> Processing triggers for initramfs-tools ...
> update-initramfs: Generating /boot/initrd.img-2.6.32-trunk-686
> Processing triggers for python-support ...
>
if at all this is a bug in linux-2.6 postinst,
as it creates the initramfs with -c and does *not* update it,
when in the same time you upgrade another package which triggers
an update this is run later.
so this is a trade off for better system stability.
I certainly don't want the linux-2.6 postinst call update and
rely on the trigger mechanism.
not much point in documenting this, thus closing bug report.
--- End Message ---
Reply to: