[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: dpkg fails to install 32-bit adobe acrobat reader on 64-bit wheezy system: depends issue

On Apr 20, 2012, at 3:23 PM, Guillem Jover wrote:

> 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

Awesome guillem, thanks.

Regarding your previous email:

On Apr 20, 2012, at 11:56 AM, Guillem Jover wrote:

> Either install libgtk2.0-0:i386 (and any other missing dependencies
> from i386), or use also --force-depends (but I don't see how the
> package would work if it's missing appropriate shared libraries?).

I was curious about that too. It turns out that Adobe ships a bunch of libraries
along with the compiled executable and modifies your LD_LIBRARY_PATH. 
I can verify that acroread does run under Wheezy.

I tried installing libgtk2.0-0:i386 that but it seems like not all the appropriate
packages in the dependency chain are multi-arch (or maybe the system is misconfigured):
> chiestand@wheezy:/tmp$ sudo apt-get install -f libgtk2.0-0:i386
> Reading package lists... Done
> Building dependency tree       
> Reading state information... Done
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> The following packages have unmet dependencies:
>  libgtk2.0-0:i386 : Depends: shared-mime-info:i386 but it is not going to be installed
>                     Recommends: hicolor-icon-theme:i386 but it is not installable
> E: Broken packages

If I trace the dependency down a couple levels I get this:
> chiestand@wheezy:/tmp$ sudo apt-get install -f libxml2:i386
> Reading package lists... Done
> Building dependency tree       
> Reading state information... Done
> The following extra packages will be installed:
>   conky-cli emacs23-nox gcc-4.7-base:i386 icedtea-7-jre-cacao icedtea-7-jre-jamvm libc6:i386 libc6-i686:i386 libgcc1:i386 openjdk-7-jre-headless openjdk-7-jre-lib pcb-lesstif pinentry-curses zlib1g:i386
> Suggested packages:
>   apcupsd moc mpd emacs23-common-non-dfsg glibc-doc:i386 locales:i386 sun-java6-fonts fonts-ipafont-gothic fonts-ipafont-mincho ttf-wqy-microhei ttf-wqy-zenhei ttf-indic-fonts pinentry-doc
> Recommended packages:
>   xml-core:i386
> The following packages will be REMOVED:
>   3depict abiword abiword-plugin-grammar abiword-plugin-mathview acedb-other-belvu acedb-other-dotter adobe-flashplugin adun.app aeskulap aisleriot akonadi-server akonadiconsole akregator alacarte alien alien-hunter amide amor arduino
>   ark audacity avahi-daemon avogadro bamfdaemon baobab bauble bibus bind9 bind9-host bind9utils blinken blogilo bomber bovo brasero cadabra cantor cantor-backend-kalgebra caret cb2bib cba cervisia cheese chemical-mime-data
>   chemical-structures chemtool cmake conky-all connectomeviewer context context-modules coq coq-theories coqide ctsim cvsservice dcmtk dconf-tools debhelper default-jdk default-jre deluge deluge-gtk deluge-torrent desktop-base
>   dh-autoreconf dh-make dia dia-common dia-libs dicomscope dnsutils dolphin dragonplayer easychem eclipse eclipse-cdt eclipse-egit eclipse-emf eclipse-emf-examples eclipse-emf-sdk eclipse-gef eclipse-gef-doc eclipse-jdt eclipse-mylyn
> …

A ton of packages would be removed, including libxml2 libxml2-dev libxml2-utils. I'm confused about where the conflict comes from. Is there a tool to help narrow down where the conflict arises?

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.


Attachment: smime.p7s
Description: S/MIME cryptographic signature

Reply to: