Ben Hutchings <b...@decadent.org.uk> writes: > On Tue, 2012-06-12 at 17:45 +0200, David Kalnischkies wrote: >> On Mon, Jun 11, 2012 at 9:40 PM, Michael Gilbert <mgilb...@debian.org> wrote: >> > In particular, I filed a bug against dpkg requesting that it produce >> > more informative error messages in these cases [0], but I wonder if a >> > part of the solution shouldn't be more automated or at least presented >> > at a higher level through apt/aptitude, etc? >> >> Chicken or the egg? >> >> You need to upgrade to support MultiArch, >> but you need MultiArch to upgrade⦠>> (beside, how would the detection for such a message look like?) > [...] >> Maybe all maintainers who want to use Multi-Arch now in wheezy >> (and therefore drop amd64 packages) should get together and write >> a "what to do after the distribution upgrade" for the release notes, >> a (low priority) debconf message and if you want to be really fancy >> a "transitional" package which shows the same text in case the >> "dropped" binaries are executed. > [...] > > I'd be interested in this for linux-image-amd64:i386. Currently I > expect linux-image-3.2.0-<n>-amd64:i386 to remain in wheezy but we'll > still need to advise the user to enable amd64 ready for wheezy+1. If we > can document multi-arch well enough in release notes etc. then it might > be possible to drop it now. > > Ben.
Luckily you have an i386 package that will be updated to. So you can add something to the NEWS file or even pop up a debconf message telling the user about going multiarch. MfG Goswin -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87haua5gjg.fsf@frosties.localnet