On Fri, 18 Feb 2011, Steve Langasek wrote: > So yeah, that seems ok to me, but I guess you're not convinced or you > wouldn't have asked. :) What other way do you see this working? Should > dpkg auto-remove multiarch packages when an upgrade to _all is requested? > That seems very inconsistent with dpkg's "do what I say" approach, IMHO.
Well, from the implementer point of view, this behaviour is what works with the least modification to dpkg. So I'm happy if we can agree that this is correct. That said when I wrote my non-regression tests, I wrote them in a way that checks that you can upgrade a M-A: foreign foo_1.0_<foreign> to foo_2.0_all (and vice-versa). Because that's what seemed most logical from a user point of view. Upgrading multiple M-A: same to a single foo_2.0_all should definitely be forbidden though. But the opposite foo_1.0_all -> M-A: same foo_2.0_<foreign> ? So I wanted to know how other people feel on this issue. Cheers, -- Raphaël Hertzog ◈ Debian Developer Follow my Debian News ▶ http://RaphaelHertzog.com (English) ▶ http://RaphaelHertzog.fr (Français) -- To UNSUBSCRIBE, email to debian-dpkg-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110218193705.ga13...@rivendell.home.ouaza.com
