Re: Endianness of data files in MultiArch (was: Please test gzip -9n - related to dpkg with multiarch support)

2012-02-13 Thread Aron Xu
On Sun, Feb 12, 2012 at 08:00, Carsten Hey wrote: > * Aron Xu [2012-02-09 01:22 +0800]: >> Some packages come with data files that endianness matters, and many >> of them are large enough to split into a separate arch:all package if >> endianness were not something to care about. ... > > Debian Po

Re: Bug#659782: does not cope with multiarch packages being installed

2012-02-13 Thread Philipp Kern
On Mon, Feb 13, 2012 at 07:27:18PM +0100, Bill Allombert wrote: > popcon actually uses: > dpkg-query --show --showformat='${status} ${package}\n' > and > dpkg -L $pkg > > What does that give on your system? dpkg-query with those options does not output any arch qualifiers, just the basenames (lib

Re: [Popcon-developers] Bug#659782: does not cope with multiarch packages being installed

2012-02-13 Thread Philipp Kern
On Mon, Feb 13, 2012 at 08:10:44PM +0100, Bill Allombert wrote: > > However ${binary:Package} gives the correct result for the m-a:same package: > > > > $ dpkg-query --show --showformat='${status} ${binary:Package}\n' | egrep > > '(mksh|libc6-i686)' > > install ok installed libc6-i686:i386 > > in

Multiarch file overlap summary and proposal (was: Summary: dpkg shared / reference counted files and version match)

2012-02-13 Thread Russ Allbery
There's been a lot of discussion of this, but it seems to have been fairly inconclusive. We need to decide what we're doing, if anything, for wheezy fairly soon, so I think we need to try to drive this discussion to some concrete conclusions. First, Steve's point here is very good: Steve Langase

Re: Multiarch file overlap summary and proposal (was: Summary: dpkg shared / reference counted files and version match)

2012-02-13 Thread Raphael Hertzog
On Mon, 13 Feb 2012, Russ Allbery wrote: > There's been a lot of discussion of this, but it seems to have been fairly > inconclusive. We need to decide what we're doing, if anything, for wheezy > fairly soon, so I think we need to try to drive this discussion to some > concrete conclusions. Thank