Your message dated Thu, 26 Oct 2006 06:17:22 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#351542: fixed in lilo 1:22.6.1-8
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-7+b1
Severity: serious
File: /usr/sbin/update-lilo

Hello,
Due to changes in kernel-package 10.025 (details follows) update-lilo causes
hang up during installation of latest kernel-image packages.

>From changelog of kernel-package:
  * Bug fix: "[powerpc] k-p 10.00x breaks debconf based /etc/kernel/*.d
    scripts like mkvmlinuz", thanks to Sven Luther. Well. In the recent
    10.X series, kernel package has started producing image packages whose
    maintainer scripts use debconf for user interaction. Unfortunately,
    this meant that any hook scripts called in the maintainer scripts for
    the image package (update-grub comes to mind), if they wrote anything
    at all to the STDOUT, would cause debconf to throw hissy fits, since
    it was expecting commands on STDOUT, not random chatter from the hook
    scripts.
  
    One solution was to call db_stop before calling the hook scripts, and
    redirecting stdout to stderr in hte invocation of the
    scripts. Unfortunately, this made any scripts that used debconf
    impossible.

    So, either we ban scripts that are interactive, or scripts that
    scribble on stdout.  Since the former makes some functionality
    impossible (some scripts can deliver added functionality and
    flexibility if they can interact with users), and the latter just
    needs a code change, I would prefer to ask packages that provide
    scripts to be used in kernel image postinst/postrm to use debconf for
    user interaction, and to send diagnostics to STDERR.

Regards
        Artur

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.15-1-amd64-generic
Locale: LANG=C, LC_CTYPE=pl_PL (charmap=ISO-8859-2)

Versions of packages lilo depends on:
ii  debconf                      1.4.70      Debian configuration management sy
ii  libc6                        2.3.5-12.1  GNU C Library: Shared libraries an
ii  libdevmapper1.02             2:1.02.02-1 The Linux Kernel Device Mapper use

lilo recommends no packages.

-- debconf information:
  lilo/bad_bitmap:
  lilo/upgrade:
  lilo/runme: false
* lilo/new-config:

-- 
Pamiętaj, nieszczęsny przyjacielu Czesia: jeśli ma on do wyboru jedzenie
i spotkanie z Tobą, zawsze wybierze jedzenie.
                                                        /Socjonetka/


--- End Message ---
--- Begin Message ---
Source: lilo
Source-Version: 1:22.6.1-8

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.6.1-8_all.deb
  to pool/main/l/lilo/lilo-doc_22.6.1-8_all.deb
lilo_22.6.1-8.diff.gz
  to pool/main/l/lilo/lilo_22.6.1-8.diff.gz
lilo_22.6.1-8.dsc
  to pool/main/l/lilo/lilo_22.6.1-8.dsc
lilo_22.6.1-8_i386.deb
  to pool/main/l/lilo/lilo_22.6.1-8_i386.deb



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: Wed, 25 Oct 2006 15:08:22 +0000
Source: lilo
Binary: lilo-doc lilo
Architecture: source i386 all
Version: 1:22.6.1-8
Distribution: unstable
Urgency: high
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: 295465 333278 338070 340632 351542 356214 378923 379518
Changes: 
 lilo (1:22.6.1-8) unstable; urgency=high
 .
   * debian/patches/06_geometry.dpatch:
     - Patch from Nathanael Nerode <[EMAIL PROTECTED]> to make sure that
       disks marked 'inaccessible' do not have their partition tables checked
       and do not have 'stat' run. (Closes: #379518)
   * debian/patches/06_verbose-errmsg.dpatch:
     - Applied changes suggested by Javier Fernández-Sanguino Pen~a
       <[EMAIL PROTECTED]> because some parts of the patch were never
       executed. (Closes: #295465)
   * debian/{liloconfig,lilo.templates}:
     - Applied changes suggested by Artur R. Czechowski <[EMAIL PROTECTED]>
       to use debconf in liloconfig. (Closes: #351542)
   * debian/patches/17_dont_scan_udev.dpatch:
     - Patch from Noel Maddy <[EMAIL PROTECTED]> to avoid checking the 
/dev/.udev
       directory when scanning /dev. (Closes: #378923)
   * debian/po/{sv,ru,nl,pt_PT}.po:
     - Added and updated translations. Thanks guys.
       (Closes: #333278, #338070, #340632, #356214)
Files: 
 f07e0cfeb8980d36862c8612e5656637 731 base optional lilo_22.6.1-8.dsc
 6e12e81aeebe76622896045b295e397d 192022 base optional lilo_22.6.1-8.diff.gz
 05b889dda67804cc74f082035d95b02b 349106 base optional lilo_22.6.1-8_i386.deb
 d3fbacbff2569894ecc43c367ea47348 225442 doc optional lilo-doc_22.6.1-8_all.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)

iD8DBQFFQK/x2OByS7KTlusRAtoRAJ0VoQPUi0Yef9L2LADOW8wGv0nmLwCfWPfZ
ecs4UGhn+bOMyaLsIgp3hpM=
=EjE4
-----END PGP SIGNATURE-----


--- End Message ---

Reply via email to