[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#574031: marked as done (linux-image-2.6.32-3-amd64: Failed to upgrade to version 2.6.32-3-amd64)



Your message dated Thu, 19 Jan 2012 16:39:49 -0600
with message-id <20120119223949.GA17841@burratino>
and subject line Re: [linux-2.6] Failed to upgrade to version 2.6.32-3-amd64
has caused the Debian Bug report #574031,
regarding linux-image-2.6.32-3-amd64: Failed to upgrade to version 2.6.32-3-amd64
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.)


-- 
574031: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=574031
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: linux-2.6
Version: 2.6.32-9
Severity: critical
Justification: breaks the whole system

Hi,

as you can see i have not rebooted my machine yet, which is reasonable because my machine would
be probably left unbootable. During upgrade to kernel version 2.6.32-3, it failed at generating grub.cfg .
So I decided to check postinst script but i found nothing in there. Then I uncommented line with 
atribute strict as it is mentioned in there to be usefull for debuging and I am sending log to you. 
Hopefully it will help you more than it did to me. :)  

-- Package-specific info:
** Kernel log: boot messages should be attached


-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-trunk-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages linux-image-2.6.32-3-amd64 depends on:
ii  debconf [debconf-2.0]        1.5.28      Debian configuration management sy
ii  initramfs-tools [linux-initr 0.93.4      tools for generating an initramfs
ii  module-init-tools            3.12~pre1-1 tools for managing Linux kernel mo

Versions of packages linux-image-2.6.32-3-amd64 recommends:
ii  firmware-linux-free           2.6.32-9   Binary firmware for various driver

Versions of packages linux-image-2.6.32-3-amd64 suggests:
pn  grub | lilo                   <none>     (no description available)
pn  linux-doc-2.6.32              <none>     (no description available)

Versions of packages linux-image-2.6.32-3-amd64 is related to:
pn  firmware-bnx2                 <none>     (no description available)
pn  firmware-bnx2x                <none>     (no description available)
pn  firmware-ipw2x00              <none>     (no description available)
pn  firmware-ivtv                 <none>     (no description available)
ii  firmware-iwlwifi              0.23       Binary firmware for Intel Wireless
pn  firmware-linux                <none>     (no description available)
pn  firmware-linux-nonfree        <none>     (no description available)
pn  firmware-qlogic               <none>     (no description available)
pn  firmware-ralink               <none>     (no description available)

-- debconf information:
  shared/kernel-image/really-run-bootloader: true
  linux-image-2.6.32-3-amd64/prerm/removing-running-kernel-2.6.32-3-amd64: true
  linux-image-2.6.32-3-amd64/postinst/bootloader-test-error-2.6.32-3-amd64:
  linux-image-2.6.32-3-amd64/postinst/missing-firmware-2.6.32-3-amd64:
  linux-image-2.6.32-3-amd64/prerm/would-invalidate-boot-loader-2.6.32-3-amd64: true
  linux-image-2.6.32-3-amd64/postinst/depmod-error-initrd-2.6.32-3-amd64: false
  linux-image-2.6.32-3-amd64/postinst/bootloader-error-2.6.32-3-amd64:


Log from perl using strict atribute :

root@debian:~# aptitude safe-upgrade 
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Reading extended state information      
Initializing package states... Done
Reading task descriptions... Done  
The following packages have been kept back:
  libmagickcore2-extra{a} 
The following partially installed packages will be configured:
  linux-image-2.6.32-3-amd64 
0 packages upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
Need to get 0B of archives. After unpacking 0B will be used.
Writing extended state information... Done
Setting up linux-image-2.6.32-3-amd64 (2.6.32-9) ...
Global symbol "$question" requires explicit package name at /var/lib/dpkg/info/linux-image-2.6.32-3-amd64.postinst line 635.
Global symbol "$question" requires explicit package name at /var/lib/dpkg/info/linux-image-2.6.32-3-amd64.postinst line 637.
Global symbol "$question" requires explicit package name at /var/lib/dpkg/info/linux-image-2.6.32-3-amd64.postinst line 638.
Global symbol "$question" requires explicit package name at /var/lib/dpkg/info/linux-image-2.6.32-3-amd64.postinst line 640.
Global symbol "$question" requires explicit package name at /var/lib/dpkg/info/linux-image-2.6.32-3-amd64.postinst line 641.
Global symbol "$question" requires explicit package name at /var/lib/dpkg/info/linux-image-2.6.32-3-amd64.postinst line 643.
Global symbol "$question" requires explicit package name at /var/lib/dpkg/info/linux-image-2.6.32-3-amd64.postinst line 644.
Global symbol "$question" requires explicit package name at /var/lib/dpkg/info/linux-image-2.6.32-3-amd64.postinst line 647.
Global symbol "$question" requires explicit package name at /var/lib/dpkg/info/linux-image-2.6.32-3-amd64.postinst line 648.
Global symbol "$question" requires explicit package name at /var/lib/dpkg/info/linux-image-2.6.32-3-amd64.postinst line 651.
Global symbol "$question" requires explicit package name at /var/lib/dpkg/info/linux-image-2.6.32-3-amd64.postinst line 652.
Global symbol "$question" requires explicit package name at /var/lib/dpkg/info/linux-image-2.6.32-3-amd64.postinst line 655.
Global symbol "$question" requires explicit package name at /var/lib/dpkg/info/linux-image-2.6.32-3-amd64.postinst line 657.
Global symbol "$question" requires explicit package name at /var/lib/dpkg/info/linux-image-2.6.32-3-amd64.postinst line 662.
Global symbol "$question" requires explicit package name at /var/lib/dpkg/info/linux-image-2.6.32-3-amd64.postinst line 665.
Global symbol "$question" requires explicit package name at /var/lib/dpkg/info/linux-image-2.6.32-3-amd64.postinst line 666.
Global symbol "$ramdisk_cmd" requires explicit package name at /var/lib/dpkg/info/linux-image-2.6.32-3-amd64.postinst line 793.
Global symbol "$ramdisk_cmd" requires explicit package name at /var/lib/dpkg/info/linux-image-2.6.32-3-amd64.postinst line 794.
Global symbol "$ramdisk_cmd" requires explicit package name at /var/lib/dpkg/info/linux-image-2.6.32-3-amd64.postinst line 798.
Global symbol "$ramdisk_cmd" requires explicit package name at /var/lib/dpkg/info/linux-image-2.6.32-3-amd64.postinst line 802.
Global symbol "$answer" requires explicit package name at /var/lib/dpkg/info/linux-image-2.6.32-3-amd64.postinst line 941.
Global symbol "$answer" requires explicit package name at /var/lib/dpkg/info/linux-image-2.6.32-3-amd64.postinst line 942.
Global symbol "$answer" requires explicit package name at /var/lib/dpkg/info/linux-image-2.6.32-3-amd64.postinst line 944.
Execution of /var/lib/dpkg/info/linux-image-2.6.32-3-amd64.postinst aborted due to compilation errors.
dpkg: error processing linux-image-2.6.32-3-amd64 (--configure):
 subprocess installed post-installation script returned error exit status 9
Errors were encountered while processing:
 linux-image-2.6.32-3-amd64
E: Sub-process /usr/bin/dpkg returned an error code (1)


Thank you in advance. 



--- End Message ---
--- Begin Message ---
tags 574031 - unreproducible
quit

Moritz Muehlenhoff wrote:

> Patrik, could you post the error message?

Closing due to lack of response.

I assume this was silently resolved somehow, or we would be receiving
more complaints. ;-)  Sorry we weren't able to figure it out.


--- End Message ---

Reply to: