Your message dated Thu, 22 Feb 2007 23:17:04 +0000 with message-id <[EMAIL PROTECTED]> and subject line Bug#403222: fixed in lilo 1:22.8-1 has caused the attached Bug report 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 I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database)
--- Begin Message ---Package: lilo Version: 1:22.6.1-9 Severity: important After a kernel upgrade, lilo refused to write the information in MBR. twix:/etc/lvm# apt-cache policy linux-image-2.6.18-3-686 linux-image-2.6.18-3-686: Installed: 2.6.18-7 Candidate: 2.6.18-7 Version table: 2.6.18-8 0 99 http://ftp.lug.ro sid/main Packages *** 2.6.18-7 0 900 http://ftp.lug.ro etch/main Packages 100 /var/lib/dpkg/status This is the output if I run by hand and is the same thing stored in /var/log/lilo* twix:/etc/lvm# lilo device-mapper: table ioctl failed: No such device or address Fatal: device-mapper: dm_task_run(DM_DEVICE_TABLE) failed libdevmapper1.02 was upgraded (from 2:1.02.08-1) as an attempt to make lilo recognize the thing, but no avail. twix:/etc/lvm# apt-cache policy libdevmapper1.02 dmsetup libdevmapper1.02: Installed: 2:1.02.12-1 Candidate: 2:1.02.12-1 Version table: *** 2:1.02.12-1 0 99 http://ftp.lug.ro sid/main Packages 100 /var/lib/dpkg/status 2:1.02.08-1 0 900 http://ftp.lug.ro etch/main Packages dmsetup: Installed: 2:1.02.08-1 Candidate: 2:1.02.08-1 Version table: 2:1.02.12-1 0 99 http://ftp.lug.ro sid/main Packages *** 2:1.02.08-1 0 900 http://ftp.lug.ro etch/main Packages 100 /var/lib/dpkg/status twix:/etc/lvm# dmsetup info Name: hdapool-homefilesystem State: ACTIVE Tables present: LIVE Open count: 1 Event number: 0 Major, minor: 254, 1 Number of targets: 2 UUID: LVM-phH0IvJRU30v0gAD64awZMzaG3FLwh6WzyAkYV9zve915YQ5GuoFXcI78Gz0tu2Z Name: hdapool-rootfilesystem State: ACTIVE Tables present: LIVE Open count: 1 Event number: 0 Major, minor: 254, 0 Number of targets: 1 UUID: LVM-phH0IvJRU30v0gAD64awZMzaG3FLwh6W80vcbMjIVabaeeQk0k7trdSoeZxden1Q -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (900, 'testing'), (99, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17-2-686 Locale: LANG=ro_RO.UTF-8, LC_CTYPE=ro_RO.UTF-8 (charmap=UTF-8) Versions of packages lilo depends on: ii debconf 1.5.8 Debian configuration management sy ii libc6 2.3.6.ds1-8 GNU C Library: Shared libraries ii libdevmapper1.02 2:1.02.12-1 The Linux Kernel Device Mapper use ii mbr 1.1.9-2 Master Boot Record for IBM-PC comp lilo recommends no packages. -- debconf information: liloconfig/fstab_broken: liloconfig/banner: liloconfig/liloconf_incompatible: lilo/bad_bitmap: liloconfig/use_lba32: true lilo/upgrade: liloconfig/liloconf_exists: liloconfig/configuring_base: lilo/runme: false liloconfig/use_current_lilo: true liloconfig/wipe_old_liloconf: false liloconfig/instruction: liloconfig/activate_error: liloconfig/select_bitmap: /boot/coffee.bmp liloconfig/lilo_error: lilo/new-config: liloconfig/odd_fstab: liloconfig/install_from_root_device: true liloconfig/make_active_partition: true liloconfig/maintitle: liloconfig/mbr_error: liloconfig/lilo_warning: liloconfig/install_mbr: false liloconfig/no_changes:
--- End Message ---
--- Begin Message ---Source: lilo Source-Version: 1:22.8-1 We believe that the bug you reported is fixed in the latest version of lilo, which is due to be installed in the Debian FTP archive: lilo-doc_22.8-1_all.deb to pool/main/l/lilo/lilo-doc_22.8-1_all.deb lilo_22.8-1.diff.gz to pool/main/l/lilo/lilo_22.8-1.diff.gz lilo_22.8-1.dsc to pool/main/l/lilo/lilo_22.8-1.dsc lilo_22.8-1_i386.deb to pool/main/l/lilo/lilo_22.8-1_i386.deb lilo_22.8.orig.tar.gz to pool/main/l/lilo/lilo_22.8.orig.tar.gz A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andrés Roldán <[EMAIL PROTECTED]> (supplier of updated lilo package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Format: 1.7 Date: Thu, 22 Feb 2007 22:52:37 +0000 Source: lilo Binary: lilo-doc lilo Architecture: source i386 all Version: 1:22.8-1 Distribution: unstable Urgency: low Maintainer: Andrés Roldán <[EMAIL PROTECTED]> Changed-By: Andrés Roldán <[EMAIL PROTECTED]> Description: lilo - LInux LOader - The Classic OS loader can load Linux and others lilo-doc - Documentation for LILO (LInux LOader) Closes: 396487 399057 400150 401393 403222 404409 406543 407697 407847 408576 Changes: lilo (1:22.8-1) unstable; urgency=low . * New upstream release. * Acknowledging NMUs, big thanks guys. Closes: #396487, #399057, #400150, #404409, #406543, #408576 Closes: #407847, #407697, #401393, #403222 * debian/patches/{02_makefile-adds.dpatch,07_devfs_msg.dpatch}: - Updated to fit new version. * debian/patches/17_dont_scan_udev.dpatch: - Not longer applied as upstream already managed this problem. Files: a01bd814d0f48b3881aea37d7d0ea91c 725 admin optional lilo_22.8-1.dsc 3111b5f52cc0dc96ebe8903702a9d29f 449315 admin optional lilo_22.8.orig.tar.gz 7957c2c462e3a4d677792ed0ca2f666c 204636 admin optional lilo_22.8-1.diff.gz 26a3ca815a0a200da94aebaedc182b9d 364974 admin optional lilo_22.8-1_i386.deb 3971590a51c8770e7b1f478bbd9e9381 226734 doc optional lilo-doc_22.8-1_all.deb -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFF3iBQ2OByS7KTlusRAkN4AKClKaU/BOJN7zX5O0W/ltNohb+tMQCcCvV/ L8y5OXk/smBYAjcUEbFjM9E= =mntA -----END PGP SIGNATURE-----
--- End Message ---
