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

Bug#670900: apt-get upgrade bails out with E: Internal Error, No file name for gcc-4.7-base



Hi!

On Mon, 2012-04-30 at 09:52:43 +0200, Martin Steigerwald wrote:
> Package: apt
> Version: 0.9.2
> Severity: normal

I think this bug report should be serious, because once hit, apt cannot
recover itself in any way, it is pretty easy to get into, and the only
way to proceed is to run for example: «dpkg --configure --pending»,
but that might not be enough if the dependencies are not satisfiable.

> But this report is about the
> 
> E: Internal Error, No file name for gcc-4.7-base
> 
> message.

This only happens whenever at least two Multi-Arch:same instances are
on unpacked state (my guess is that this would happen too for any
status < installed), so this will be fairly easy to trigger for users
whenever an upgrade is interrupted, due to a dpkg error or user
intervention for example.

Here's a session to reproduce this:

  # apt-get download libpam-modules:i386 libpam-modules:amd64

Two instances on unpack state (fail):

  # dpkg --unpack libpam-modules_*.deb
  (Reading database ... 185224 files and directories currently installed.)
  Preparing to replace libpam-modules:i386 1.1.3-7.1 (using libpam-modules_1.1.3-7.1_i386.deb) ...
  Unpacking replacement libpam-modules:i386 ...
  Preparing to replace libpam-modules:amd64 1.1.3-7.1 (using libpam-modules_1.1.3-7.1_amd64.deb) ...
  Unpacking replacement libpam-modules:amd64 ...
  Processing triggers for man-db ...
  # apt-get install -f
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  0 upgraded, 0 newly installed, 0 to remove and 9 not upgraded.
  2 not fully installed or removed.
  After this operation, 0 B of additional disk space will be used.
  E: Internal Error, No file name for libpam-modules
  # dpkg --configure --pending
  Setting up libpam-modules:amd64 (1.1.3-7.1) ...
  Setting up libpam-modules:i386 (1.1.3-7.1) ...

Only one instance on unpack state (pass):

  # dpkg --unpack libpam-modules_1.1.3-7.1_i386.deb
  (Reading database ... 185224 files and directories currently installed.)
  Preparing to replace libpam-modules:i386 1.1.3-7.1 (using libpam-modules_1.1.3-7.1_i386.deb) ...
  Unpacking replacement libpam-modules:i386 ...
  Processing triggers for man-db ...
  gaara:/tmp# apt-get install -f
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  0 upgraded, 0 newly installed, 0 to remove and 9 not upgraded.
  1 not fully installed or removed.
  After this operation, 0 B of additional disk space will be used.
  Setting up libpam-modules:i386 (1.1.3-7.1) ...

thanks,
guillem


Reply to: