Re: Issues with Multi-Arch:same packages on purge

2013-04-27 Thread Andreas Beckmann
On 2013-04-22 21:38, Andreas Beckmann wrote: > On 2013-04-22 07:31, Guillem Jover wrote: >> I guess a way to detect those could be piuparts runs that install >> multiple instances of Multi-Arch:same packages, purge just one of >> them, and compare that the packages created by the first instance >>

Re: not co-installable Multi-Arch:same packages (was: Re: Issues with Multi-Arch:same packages on purge)

2013-04-25 Thread Jakub Wilk
* Andreas Beckmann , 2013-04-25, 21:27: what would be the correct severity? I've been using important (or normal, if only toy^Wexotic architectures were affected) for such file conflicts, regardless of whether you were able to reproduce the bug in practice by co-installing the packages in qu

Re: not co-installable Multi-Arch:same packages (was: Re: Issues with Multi-Arch:same packages on purge)

2013-04-25 Thread Jakub Wilk
* Andreas Beckmann , 2013-04-25, 21:27: trying to overwrite shared '/usr/lib/debug/usr/lib/libffi.so.5.0.10', which is different from other instances of package libffi5-dbg:i386 #650106 Maybe this shouldn't have been MA:same. There's no problem with -dbg packages being MA:same. They just ne

not co-installable Multi-Arch:same packages (was: Re: Issues with Multi-Arch:same packages on purge)

2013-04-25 Thread Andreas Beckmann
On 2013-04-22 21:38, Andreas Beckmann wrote: > On 2013-04-22 07:31, Guillem Jover wrote: >> I guess a way to detect those could be piuparts runs that install >> multiple instances of Multi-Arch:same packages, purge just one of ... > Actually I already tried something similar some time ago, although

Re: Issues with Multi-Arch:same packages on purge

2013-04-22 Thread Andreas Beckmann
On 2013-04-22 07:31, Guillem Jover wrote: > I guess a way to detect those could be piuparts runs that install > multiple instances of Multi-Arch:same packages, purge just one of > them, and compare that the packages created by the first instance > are not removed, and that other files do not get mo

/var/cache/ (was Re: Issues with Multi-Arch:same packages on purge)

2013-04-22 Thread Adam Borowski
On Mon, Apr 22, 2013 at 08:51:01PM +0200, Guillem Jover wrote: > The following snippet seems suspect, although not a big issue anyway > as it's just removing a cache file, although it might leave files > behind on remove/purge: > > ,--- > if [ -d /usr/lib/gio/modules ]; then > # Purge the ca

Re: Issues with Multi-Arch:same packages on purge

2013-04-22 Thread Guillem Jover
On Mon, 2013-04-22 at 19:06:52 +0200, Michael Biebl wrote: > Am 22.04.2013 17:24, schrieb Guillem Jover: > > Other problems might be when maintainer scripts use the running dpkg > > architecture instead of the package architecture (DPKG_MAINTSCRIPT_ARCH) > > to decide when to do stuff, for example

Re: Issues with Multi-Arch:same packages on purge

2013-04-22 Thread Michael Biebl
Am 22.04.2013 17:24, schrieb Guillem Jover: > Other problems might be when maintainer scripts use the running dpkg > architecture instead of the package architecture (DPKG_MAINTSCRIPT_ARCH) > to decide when to do stuff, for example in libglib2.0-0.postrm. Handling multi-arch in the maintainers sc

Re: Issues with Multi-Arch:same packages on purge

2013-04-22 Thread Guillem Jover
On Mon, 2013-04-22 at 16:06:05 +0200, Helmut Grohne wrote: > On Mon, Apr 22, 2013 at 07:31:54AM +0200, Guillem Jover wrote: > > I guess a way to detect those could be piuparts runs that install > > multiple instances of Multi-Arch:same packages, purge just one of > > them, and compare that the pack

Re: Issues with Multi-Arch:same packages on purge

2013-04-22 Thread Helmut Grohne
On Mon, Apr 22, 2013 at 07:31:54AM +0200, Guillem Jover wrote: > I guess a way to detect those could be piuparts runs that install > multiple instances of Multi-Arch:same packages, purge just one of > them, and compare that the packages created by the first instance > are not removed, and that othe