Le dimanche 6 janvier 2013 17:09:48, Helmut Grohne a écrit : > [Adding multiarch-devel to CC for a comment on point 3.] > > On Sun, Jan 06, 2013 at 12:50:35PM +0100, Thomas Preud'homme wrote: > > Ah yes sorry. I searched explicitely for user locking but of course it's > > the case for any shared (among arch) resources modified/removed on > > purge. > > Actually looking at it again I believe that simply removing Multi-Arch > for wheezy would be the best thing to do. My reasons for that are: > > 1) The release time likes one-line-fixes.
Yep and keeping multiarch would be a much bigger change. > 2) None of those libraries has external (i.e. outside of src:dspam) > reverse dependencies. So the benefit of Multi-Arch is kind of > limited. We were saying this on IRC few minutes ago. > 3) Handling shared resources in M-A:same packages is yet an unsolved > problem. As more packages stumble across this problem there will > likely be a helper for such situations. This will not happen for > wheezy, so save yourself a bit of time and just defer this issue. Yeah but I'm not sure a helper would be enough. I was already writing such a small helper for myself (see below) but I stumbled upon the problem of dbconfig-common in my case. It's used with debconf to install conf files and it would be invoked twice if a multiarchified package was installed for 2 different architectures. I'm sure there is some other such example. % cat debian/last_arch_installed #!/bin/sh # Multi-arch was added in dpkg in the same version as the db:Status-Abbrev # virtual field was added to dpkg-query. Hence, either this bug cannot be # encountered, or db:Status-Abbrev virtual field is available in dpkg-query. ! dpkg --assert-multi-arch || ! dpkg-query '-f=${db:Status-Abbrev}\n' -W $1 | grep -vE '(.n|pc)' >/dev/null > > Helmut Best regards, Thomas Preud'homme
signature.asc
Description: This is a digitally signed message part.