This bug is still present in libpython2.7-minimal 2.7.7~rc1-1. Here's the dpkg output when the architecture is not specified.
# dpkg -l libpython2.7-minimal Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-===============================-====================-====================-==================================================================== ii libpython2.7-minimal:amd64 2.7.7~rc1-1 amd64 Minimal subset of the Python language (version 2.7) ii libpython2.7-minimal:i386 2.7.7~rc1-1 i386 Minimal subset of the Python language (version 2.7) # dpkg -L libpython2.7-minimal;echo $? dpkg-query: error: --listfiles needs a valid package name but 'libpython2.7-minimal' is not: ambiguous package name 'libpython2.7-minimal' with more than one installed instance Use --help for help about querying packages. 2 This keeps breaking upgrades which is quite annoying. The workaround is to *purge* the i386 Python packages (if their config files are still around they are still partially installed so dpkg breaks), do the upgrade, then reinstall the i386 Python packages. -- Francois Gouget <[email protected]> http://fgouget.free.fr/ A particle is an irreducible representation of the Poincaré Group - Eugene Wigner
