[pkg-wine-party] Bug#676457: migration path from non multiarch to multiarch wine

Michael Gilbert mgilbert at debian.org
Sat Jun 9 16:43:11 UTC 2012

On Sat, Jun 9, 2012 at 10:08 AM, Stephen Kitt wrote:
> Hi,
> On Sat, Jun 09, 2012 at 10:52:43AM +0200, Stefano Zacchiroli wrote:
>> On Sat, Jun 09, 2012 at 03:37:10AM -0400, Michael Gilbert wrote:
>> > > I don't see amd64 packages in pool. The latest package version I see in pool
>> > > is wine-bin_1.4-0.3_amd64.deb. The same with other wine packages for
>> > > amd64 arch.
>> >
>> > That is because the package has been "multiarched."  In other words,
>> > the i386 packages now satisfy the amd64 dependencies.
>> Right, and indeed it works perfectly after adding i386 as a foreign
>> architecture to dpkg. But I'm pretty sure many users will stumble upon
>> the above problem during upgrades, because there is no hint whatsoever
>> (at least using apt or aptitude) that the user should do something
>> manual.
>> So the question is, I guess: what's the migration path from non
>> multiarch wine to multiarch wine?
>> I guess a NEWS.Debian entry telling users what they should do would be a
>> good start, but I'm not sure it would be enough to shield you from tons
>> of bug reports like this one :-)
> Indeed, and by that stage it's too late to do anything about it anyway
> - apt-get/aptitude will always have trouble dealing with the upgrade,
> and for users who haven't previously added the appropriate foreign
> architecture the package will either be removed or held, so
> NEWS.Debian won't be displayed...


I just submitted a bug requesting that dpkg be more
helpful/informative in these situations:

I think that is the correct solution to this problem.

Best wishes,

More information about the pkg-wine-party mailing list