Package: kernel-package
Version: 9.000
Severity: normal
File: /usr/share/kernel-package/image.postinst

Hi, Manoj.

When attempting to install a recently built kernel image, I got the
nonsensical message

/boot/vmlinuz-2.6.11.9 points to /boot/vmlinuz-2.6.11.10 -- doing nothing at 
/var/lib/dpkg/info/kernel-image-2.6.11.10.postinst line 559.

Comparing this postinst to the one from my 2.6.11.9 package, which
built with kernel-package 8.135 and proceeded to install normally,
suggests an accidental nesting error in the logic involving
$force_move.  In particular, it appears that when adding the logic
involving $real_old_target, you accidentally terminated

              if ($real_old_target  && -f "$real_old_target") {

with the
              } else {
                $force_move = 1;
              }

that had previously terminated

            if (-l "$kimage.old") {

and then compensated by adding an extra } around line 597, associating
several intervening blocks of code with the wrong conditionals.

-- System Information:
Debian Release: testing/unstable
Architecture: amd64 (x86_64)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.11.9
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)

Versions of packages kernel-package depends on:
ii  bcc [c-compiler]  0.16.14-1.2.0.1.pure64 16-bit x86 C compiler
ii  dpkg              1.10.28                Package maintenance system for Deb
ii  dpkg-dev          1.10.28                Package building tools for Debian
ii  gcc [c-compiler]  4:3.3.5-3              The GNU C compiler
ii  gcc-3.3 [c-compil 1:3.3.6-6              The GNU C compiler
ii  gcc-3.4 [c-compil 3.4.4-0                The GNU C compiler
ii  gcc-4.0 [c-compil 4.0.0-9                The GNU C compiler
ii  make              3.80-9                 The GNU version of the "make" util
ii  perl              5.8.7-3                Larry Wall's Practical Extraction 

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to