Hi, I don't see anything in the triggered ccache postinst script that could cause this.
Can you reproduce the problem? Could it be that something other than ccache's trigger that causes this? See for instance bug#665727. -- Joel On 8 May 2012 11:10, Yann Dirson <ydir...@free.fr> wrote: > Package: ccache > Version: 3.1.7-1 > Severity: grave > > Cannot configure the new gcc-4.7-base: > > |Preparing to replace gcc-4.7-base:amd64 4.7.0-3 (using > .../gcc-4.7-base_4.7.0-7_amd64.deb) ... > |De-configuring gcc-4.7-base:armel ... > |Unpacking replacement gcc-4.7-base:amd64 ... > |Processing triggers for ccache ... > |Updating symlinks in /usr/lib/ccache ... > |dpkg: error: --configure needs a valid package name but 'gcc-4.7-base' is > not: ambiguous package name 'gcc-4.7-base' with more than one installed > instance > > I have: > > |# dpkg -l 'gcc-4.7-base' > |iU gcc-4.7-base:amd64 4.7.0-7 > |iF gcc-4.7-base:armel 4.7.0-3 > > -- System Information: > Debian Release: wheezy/sid > APT prefers testing > APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (101, > 'experimental') > Architecture: amd64 (x86_64) > > Kernel: Linux 3.2.0-2-amd64 (SMP w/4 CPU cores) > Locale: LANG=C, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/bash > > Versions of packages ccache depends on: > ii libc6 2.13-32 > ii zlib1g 1:1.2.6.dfsg-2 > > ccache recommends no packages. > > Versions of packages ccache suggests: > pn distcc <none> > > -- no debconf information > > > >
