Bug#576925: [linux-base] postinst fails on undefined subroutine
Hi,
which files did it want to update?
I can only guess that you are thinking of the slightly unclear package
upgrade situation.
The skipped lines ([...]) only contained the notification about
automatically installed packages ("The following packages were
automatically installed and are no longer required").
The 3 not upgraded packages are python-twisted-conch (unfulfilled
depends), xserver-xorg-video-ati and xserver-xorg-video-radeon (i do not
want to upgrade them before linux-image-2.6.32-4-686 is installed).
The 2 not fully installed packages are linux-base and
linux-image-2.6.32-4-686.
what is your debconf setup?
post /etc/fstab, grub.cfg, ..
The system is lilo-based (grub does not work here), and was also
affected by bug #574987.
But I think the problem here really is a bug in the postinst script of
linux-base:
> Setting up linux-base (2.6.32-11) ...
> Undefined subroutine &DebianKernel::DiskId::_system called at
> /var/lib/dpkg/info/linux-base.postinst line 547.
> dpkg: error processing linux-base (--configure):
> subprocess installed post-installation script returned error exit
> status 255
The subroutine _system is defined outside the package
DebianKernel::DiskID, but called from inside the package.
Anyway, here are my files:
my fstab:
# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
# /dev/sda3 / ext3 errors=remount-ro 0 1
UUID=86187449-94e6-4f1f-9efc-42da7057c65d / ext3
errors=remount-ro 0 1
/dev/mapper/vg0-tmp /tmp xfs rw,noatime,nodev 0 2
/dev/mapper/vg0-home /home ext3 defaults 0 2
/dev/mapper/vg0-usr /usr ext3 defaults 0 2
/dev/mapper/vg0-var /var ext3 defaults 0 2
# /dev/hda /media/cdrom0 udf,iso9660 user,noauto 0 0
/dev/cdrom1 /media/cdrom0 udf,iso9660 user,noauto 0 0
my lilo.conf:
# Automatically added by lilo postinst script
large-memory
# /etc/lilo.conf - See: `lilo(8)' and `lilo.conf(5)',
# --------------- `install-mbr(8)', `/usr/share/doc/lilo/',
# and `/usr/share/doc/mbr/'.
# +---------------------------------------------------------------+
# | !! Reminder !! |
# | |
# | Don't forget to run `lilo' after you make changes to this |
# | conffile, `/boot/bootmess.txt' (if you have created it), or |
# | install a new kernel. The computer will most likely fail to |
# | boot if a kernel-image post-install script or you don't |
# | remember to run `lilo'. |
# | |
# +---------------------------------------------------------------+
# Specifies the boot device. This is where Lilo installs its boot
# block. It can be either a partition, or the raw device, in which
# case it installs in the MBR, and will overwrite the current MBR.
#
boot=/dev/sda
# Specifies the device that should be mounted as root. (`/')
#
# root = /dev/sda3
root = "UUID=86187449-94e6-4f1f-9efc-42da7057c65d"
# This option may be needed for some software RAID installs.
#
# raid-extra-boot=mbr-only
# Enable map compaction:
# Tries to merge read requests for adjacent sectors into a single
# read request. This drastically reduces load time and keeps the
# map smaller. Using `compact' is especially recommended when
# booting from a floppy disk. It is disabled here by default
# because it doesn't always work.
#
# compact
# Installs the specified file as the new boot sector
# You have the choice between: text, bmp, and menu
# Look in lilo.conf(5) manpage for details
#
#install=menu
# Specifies the location of the map file
#
map=/boot/map
# You can set a password here, and uncomment the `restricted' lines
# in the image definitions below to make it so that a password must
# be typed to boot anything but a default configuration. If a
# command line is given, other than one specified by an `append'
# statement in `lilo.conf', the password will be required, but a
# standard default boot will not require one.
#
# This will, for instance, prevent anyone with access to the
# console from booting with something like `Linux init=/bin/sh',
# and thus becoming `root' without proper authorization.
#
# Note that if you really need this type of security, you will
# likely also want to use `install-mbr' to reconfigure the MBR
# program, as well as set up your BIOS to disallow booting from
# removable disk or CD-ROM, then put a password on getting into the
# BIOS configuration as well. Please RTFM `install-mbr(8)'.
#
# password=tatercounter2000
# Specifies the number of deciseconds (0.1 seconds) LILO should
# wait before booting the first image.
#
delay=20
# You can put a customized boot message up if you like. If you use
# `prompt', and this computer may need to reboot unattended, you
# must specify a `timeout', or it will sit there forever waiting
# for a keypress. `single-key' goes with the `alias' lines in the
# `image' configurations below. eg: You can press `1' to boot
# `Linux', `2' to boot `LinuxOLD', if you uncomment the `alias'.
#
# message=/boot/bootmess.txt
# prompt
# delay=100
# timeout=100
# Specifies the VGA text mode at boot time. (normal, extended, ask, <mode>)
#
# vga=ask
# vga=9
#
# Kernel command line options that apply to all installed images go
# here. See: The `boot-prompt-HOWTO' and `kernel-parameters.txt' in
# the Linux kernel `Documentation' directory.
#
# append=""
# If you used a serial console to install Debian, this option should be
# enabled by default.
# serial=
#
# Boot up Linux by default.
#
default=Linux
image=/vmlinuz
label=Linux
read-only
# restricted
# alias=1
append="quiet"
initrd=/initrd.img
image=/vmlinuz.old
label=LinuxOLD
read-only
optional
# restricted
# alias=2
append="quiet"
initrd=/initrd.img.old
# If you have another OS on this machine to boot, you can uncomment the
# following lines, changing the device name on the `other' line to
# where your other OS' partition is.
#
# other=/dev/hda4
# label=HURD
# restricted
# alias=3
Thanks you
Rainer
Reply to: