Guillem Jover <[email protected]> writes:
> On Fri, 2012-04-20 at 14:58:33 -0700, Chris Hiestand wrote:
>> Actually now that I'm trying to install from scratch instead of upgrade
>> the message seems to be different (libgtk2.0-0:any instead of libgtk2.0-0):
>
>> > chiestand@wheezy:/tmp$ sudo dpkg -i --force-architecture
>> > adobereader-enu_9.5.1_i386.deb
>> > dpkg: warning: overriding problem because --force enabled:
>> > package architecture (i386) does not match system (amd64)
>> > Selecting previously unselected package adobereader-enu.
>> > (Reading database ... 782797 files and directories currently installed.)
>> > Unpacking adobereader-enu (from adobereader-enu_9.5.1_i386.deb) ...
>> > dpkg: dependency problems prevent configuration of adobereader-enu:
>> > adobereader-enu depends on libgtk2.0-0:any.
>> > dpkg: error processing adobereader-enu (--install):
>> > dependency problems - leaving unconfigured
>> > Processing triggers for man-db ...
>> > Errors were encountered while processing:
>> > adobereader-enu
>>
>> Perhaps the upgrade message should say libgtk2.0-0:i386 instead?
>
> Well, certainly at least something clearer than libgtk2.0-0:any. I've
> put that on my list of messages to clarify for 1.16.3 or 1.16.4.
>
> thanks,
> guillem
How would it know that? If libgtk2.0-0 is Multi-Arch:foreign then
libgtk2.0-0:amd64 will do just fine.
I guess if it knows about libgtk2.0-0:amd64 not bein Multi-Arch:foreign
it can say :i386 but carefull not to assume the same for completly
unknown packages.
MfG
Goswin
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
Archive: http://lists.debian.org/[email protected]
