Package: dpkg-cross Severity: important X-Debbugs-CC: j...@debian.org, hel...@subdivi.de
I've been investigating an irregularity in apt's cache, in that the longest bucket is like 58 items in the hashtable right now, but only for Package objects. That was libc-mips32-* having conflicts on libc-mip32:*-*-cross, that is, we had 50 wrong conflicts on libc6-mips32 on fake architectures instead of the proper ones. Another example Package: libc6-amd64-i386-cross Conflicts: libc0.1-i386-i386-cross, libc6-amd64:x32-i386-cross, The second one is wrong. Helmut tracked that down to a bug in dpkg-cross. Impact: - The conflicts do nothing, since nothing provides those broken package names+archs. I'm not sure if packages exist that should be matched, though. - APT is not really built to scale with multiple architectures, so everytime it sees libc6-mips it has to iterate over 50 package objects and compare the architecture string against what it is looking for, usually including wildcards. Yikes. Probably since nothing seems to depend on it, those conflicts are a bit void in practice. Would be good to get fixed, is RC if those conflicts are really needed, but otherwise marking it as important, since not sure. -- debian developer - deb.li/jak | jak-linux.org - free software dev ubuntu core developer i speak de, en
