Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Re: dpkg fails to install 32-bit adobe acrobat reader on 64-bit wheezy system: depends issue
497 views
Skip to first unread message
Steve Langasek
Apr 20, 2012, 2:50:01 PM4/20/12
to
On Fri, Apr 20, 2012 at 10:40:13AM -0700, Chris Hiestand wrote:
> I tried the debian-user list first with no luck so I'm checking with the
> experts. This seems like some kind of bug in dpkg.
> So this works fine on 64-bit squeeze:
> > chiestand@squeeze:/tmp$ sudo dpkg -i --force-architecture adobereader-enu_9.5.1_i386.deb
> But not on 64-bit wheezy:
> > chiestand@wheezy:/tmp$ sudo dpkg -i --force-architecture adobereader-enu_9.5.1_i386.deb
> > (Reading database ... 783153 files and directories currently installed.)
> > Preparing to replace adobereader-enu 9.5.1 (using areader.old.deb) ...
> > Unpacking replacement adobereader-enu ...
> > dpkg: dependency problems prevent configuration of adobereader-enu:
> > adobereader-enu depends on libgtk2.0-0 (>= 2.4).
> > dpkg: error processing adobereader-enu (--install):
> > dependency problems - leaving unconfigured
> > Processing triggers for man-db ...
> > Errors were encountered while processing:
> > adobereader-enu
> Notice the dependency failure. But the depend is actually satisfied in wheezy:
> > chiestand@wheezy:/tmp$ dpkg -l libgtk2.0-0
> > Desired=Unknown/Install/Remove/Purge/Hold
> > | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
> > |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
> > ||/ Name Version Description
> > +++-===========================-===========================-======================================================================
> > ii libgtk2.0-0:amd64 2.24.10-1 GTK+ graphical user interface library
> Is this a multi-arch issue? I've tried setting up multi-arch:
> > sudo dpkg --add-architecture i386
> > sudo apt-get update
> But I get the same result.
Yes, this is a multiarch issue. It's no longer enough to use
--force-architecture to install packages, because the semantics of forcing
the architecture have changed: it now means, approximately, "install this
package even though it's of an architecture that's not configured", where
previously it meant something more like "pretend this package is of my
system's architecture". The difference is that now, dpkg knows not only
that the package is of the wrong architecture but that its dependencies are
not satisfied.
So to get the previous behavior, you need --force-architecture
--force-depends.
Though hopefully, you will shortly not need to --force at all and will be
able to fully resolve the dependencies using multiarch-enabled library
packages.
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer http://www.debian.org/
slan...@ubuntu.com vor...@debian.org
> I tried the debian-user list first with no luck so I'm checking with the
> experts. This seems like some kind of bug in dpkg.
> So this works fine on 64-bit squeeze:
> > chiestand@squeeze:/tmp$ sudo dpkg -i --force-architecture adobereader-enu_9.5.1_i386.deb
> But not on 64-bit wheezy:
> > chiestand@wheezy:/tmp$ sudo dpkg -i --force-architecture adobereader-enu_9.5.1_i386.deb
> > (Reading database ... 783153 files and directories currently installed.)
> > Preparing to replace adobereader-enu 9.5.1 (using areader.old.deb) ...
> > Unpacking replacement adobereader-enu ...
> > dpkg: dependency problems prevent configuration of adobereader-enu:
> > adobereader-enu depends on libgtk2.0-0 (>= 2.4).
> > dpkg: error processing adobereader-enu (--install):
> > dependency problems - leaving unconfigured
> > Processing triggers for man-db ...
> > Errors were encountered while processing:
> > adobereader-enu
> Notice the dependency failure. But the depend is actually satisfied in wheezy:
> > chiestand@wheezy:/tmp$ dpkg -l libgtk2.0-0
> > Desired=Unknown/Install/Remove/Purge/Hold
> > | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
> > |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
> > ||/ Name Version Description
> > +++-===========================-===========================-======================================================================
> > ii libgtk2.0-0:amd64 2.24.10-1 GTK+ graphical user interface library
> Is this a multi-arch issue? I've tried setting up multi-arch:
> > sudo dpkg --add-architecture i386
> > sudo apt-get update
> But I get the same result.
Yes, this is a multiarch issue. It's no longer enough to use
--force-architecture to install packages, because the semantics of forcing
the architecture have changed: it now means, approximately, "install this
package even though it's of an architecture that's not configured", where
previously it meant something more like "pretend this package is of my
system's architecture". The difference is that now, dpkg knows not only
that the package is of the wrong architecture but that its dependencies are
not satisfied.
So to get the previous behavior, you need --force-architecture
--force-depends.
Though hopefully, you will shortly not need to --force at all and will be
able to fully resolve the dependencies using multiarch-enabled library
packages.
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer http://www.debian.org/
slan...@ubuntu.com vor...@debian.org
Guillem Jover
Apr 20, 2012, 3:00:01 PM4/20/12
to
On Fri, 2012-04-20 at 10:40:13 -0700, Chris Hiestand wrote:
> I tried the debian-user list first with no luck so I'm checking with
> the experts.
> This seems like some kind of bug in dpkg.
This is just missing dependencies or an appropriate force-option.
> I tried the debian-user list first with no luck so I'm checking with
> the experts.
> This seems like some kind of bug in dpkg.
from i386), or use also --force-depends (but I don't see how the
package would work if it's missing appropriate shared libraries?).
regards,
guillem
--
To UNSUBSCRIBE, email to debian-dp...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/20120420185...@gaara.hadrons.org
Guillem Jover
Apr 20, 2012, 6:30:02 PM4/20/12
to
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) ...
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,
> 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
> > 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?
> > dependency problems - leaving unconfigured
> > Processing triggers for man-db ...
> > Errors were encountered while processing:
> > adobereader-enu
>
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
--
To UNSUBSCRIBE, email to debian-dp...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/20120420222...@gaara.hadrons.org
--
To UNSUBSCRIBE, email to debian-dp...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Russ Allbery
Apr 20, 2012, 7:10:02 PM4/20/12
to
Chris Hiestand <chie...@salk.edu> writes:
> libxml2 source shows that it has "Architecture: any", so I'd imagine
> that should be not be a conflict even though there is no Multi-Arch
> field.
No, that's only for source packages and indicates that the package *can*
be built on any architecture. Architecture: all in a binary package means
it can be installed on any architecture; otherwise, it's an
architcture-specific binary package and must be multiarch to be
installable as a non-native architecture (without --force options, of
course).
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-dp...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/87y5pqk...@windlord.stanford.edu
> libxml2 source shows that it has "Architecture: any", so I'd imagine
> that should be not be a conflict even though there is no Multi-Arch
> field.
No, that's only for source packages and indicates that the package *can*
be built on any architecture. Architecture: all in a binary package means
it can be installed on any architecture; otherwise, it's an
architcture-specific binary package and must be multiarch to be
installable as a non-native architecture (without --force options, of
course).
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-dp...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Guillem Jover
Apr 20, 2012, 8:00:02 PM4/20/12
to
On Fri, 2012-04-20 at 16:06:19 -0700, Russ Allbery wrote:
> Chris Hiestand <chie...@salk.edu> writes:
> > libxml2 source shows that it has "Architecture: any", so I'd imagine
> > that should be not be a conflict even though there is no Multi-Arch
> > field.
>
> No, that's only for source packages and indicates that the package *can*
> be built on any architecture. Architecture: all in a binary package means
> it can be installed on any architecture; otherwise, it's an
> architcture-specific binary package and must be multiarch to be
> installable as a non-native architecture (without --force options, of
> course).
To be precise, a foreign arch package could be installed regardless
> Chris Hiestand <chie...@salk.edu> writes:
> > libxml2 source shows that it has "Architecture: any", so I'd imagine
> > that should be not be a conflict even though there is no Multi-Arch
> > field.
>
> No, that's only for source packages and indicates that the package *can*
> be built on any architecture. Architecture: all in a binary package means
> it can be installed on any architecture; otherwise, it's an
> architcture-specific binary package and must be multiarch to be
> installable as a non-native architecture (without --force options, of
> course).
of its multiarch status, as long as there's no other instance present
on the system and dpkg has been configured to recognize that foreign
arch.
regards,
guillem
--
To UNSUBSCRIBE, email to debian-dp...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Russ Allbery
Apr 20, 2012, 8:00:02 PM4/20/12
to
Guillem Jover <gui...@debian.org> writes:
> On Fri, 2012-04-20 at 16:06:19 -0700, Russ Allbery wrote:
>> No, that's only for source packages and indicates that the package
>> *can* be built on any architecture. Architecture: all in a binary
>> package means it can be installed on any architecture; otherwise, it's
>> an architcture-specific binary package and must be multiarch to be
>> installable as a non-native architecture (without --force options, of
>> course).
> To be precise, a foreign arch package could be installed regardless of
> its multiarch status, as long as there's no other instance present on
> the system and dpkg has been configured to recognize that foreign arch.
Oh, right, sorry. If there's no conflict, you can do what you want. If
> On Fri, 2012-04-20 at 16:06:19 -0700, Russ Allbery wrote:
>> No, that's only for source packages and indicates that the package
>> *can* be built on any architecture. Architecture: all in a binary
>> package means it can be installed on any architecture; otherwise, it's
>> an architcture-specific binary package and must be multiarch to be
>> installable as a non-native architecture (without --force options, of
>> course).
> To be precise, a foreign arch package could be installed regardless of
> its multiarch status, as long as there's no other instance present on
> the system and dpkg has been configured to recognize that foreign arch.
you want to install multiple architectures of the same package, they all
have to be multiarch.
--
To UNSUBSCRIBE, email to debian-dp...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/87y5pqj...@windlord.stanford.edu
To UNSUBSCRIBE, email to debian-dp...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Goswin von Brederlow
Apr 25, 2012, 6:00:01 AM4/25/12
to
Guillem Jover <gui...@debian.org> 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
> 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
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 debian-dp...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Jonathan Nieder
Apr 25, 2012, 11:30:03 AM4/25/12
to
Goswin von Brederlow wrote:
> Guillem Jover <gui...@debian.org> 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):
> Guillem Jover <gui...@debian.org> 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):
>>>> 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: dependency problems prevent configuration of adobereader-enu:
>>>> adobereader-enu depends on libgtk2.0-0:any.
>>> 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.
[...]
>>
>> 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.
> How would it know that? If libgtk2.0-0 is Multi-Arch:foreign then
> libgtk2.0-0:amd64 will do just fine.
Just saying what we know might be enough.
> libgtk2.0-0:amd64 will do just fine.
dpkg: dependency problems prevent configuration of adobereader-enu:
--
To UNSUBSCRIBE, email to debian-dp...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
0 new messages