[Mageia-dev] 64-bit urpmi not "seeing" Core 32 even if enabled ?

Mon Jun 18 17:08:42 CEST 2012

'Twas brillig, and Frank Griffin at 18/06/12 15:40 did gyre and gimble:
+> If this isn't just a case of me not seeing something obvious, I'll enter
+> a bug report...
+> 
+> [ftg at ftgme2 release]$ pwd
+> /mnt/cauldron/i586/media/core/release
+> [ftg at ftgme2 release]$ ls -l *keyring*
+> -rw-r--r-- 1 ftg ftg 717173 Apr 18 18:21
+> gnome-keyring-3.4.1-1.mga2.i586.rpm
+> -rw-r--r-- 1 ftg ftg  19170 Nov 21  2011
+> gnome-keyring-sharp-1.0.2-2.mga2.i586.rpm
+> -rw-r--r-- 1 ftg ftg  13759 Nov 21  2011
+> gnome-keyring-sharp-doc-1.0.2-2.mga2.i586.rpm
+> -rw-r--r-- 1 ftg ftg  24632 Nov 26  2011
+> gnome-python-gnomekeyring-2.32.0-12.mga2.i586.rpm
+> -rw-r--r-- 1 ftg ftg  24829 Nov 20  2011
+> jpilot-keyring-1.8.1-1.mga2.i586.rpm
+> -rw-r--r-- 1 ftg ftg  54372 Apr 18 18:16
+> libgnome-keyring0-3.4.1-1.mga2.i586.rpm
+> -rw-r--r-- 1 ftg ftg  77144 Apr 18 18:16
+> libgnome-keyring-devel-3.4.1-1.mga2.i586.rpm
+> -rw-r--r-- 1 ftg ftg  11033 Apr 18 18:16
+> libgnome-keyring-gir1.0-3.4.1-1.mga2.i586.rpm
+> -rw-r--r-- 1 ftg ftg  33992 Apr 18 18:16
+> libgnome-keyring-i18n-3.4.1-1.mga2.i586.rpm
+> -rw-r--r-- 1 ftg ftg   9647 Jun 14 02:15
+> libsvn-gnome-keyring0-1.7.5-3.mga3.i586.rpm
+> -rw-r--r-- 1 ftg ftg   5763 Jun 14 02:15
+> subversion-gnome-keyring-devel-1.7.5-3.mga3.i586.rpm
+> [ftg at ftgme2 release]$
+> 
+> but
+> [root at ftgme2 init.d]# urpmi gnome-keyring
+> Package gnome-keyring-3.4.1-1.mga2.x86_64 is already installed
+> [root at ftgme2 init.d]# urpmi
+> /mnt/cauldron/i586/media/core/release/gnome-keyring-3.4.1-1.mga2.i586.rpm
+> [root at ftgme2 init.d]# urpmq gnome-keyring-3.4.1-1.mga2.i586.rpm
+> urpmq: cannot read rpm file "gnome-keyring-3.4.1-1.mga2.i586.rpm"
+> [root at ftgme2 init.d]# rpm -i
+> /mnt/cauldron/i586/media/core/release/gnome-keyring-3.4.1-1.mga2.i586.rpm
+> error: Failed dependencies:
+>         libgck-1.so.0 is needed by gnome-keyring-3.4.1-1.mga2.i586
+>         libgcr-base-3.so.1 is needed by gnome-keyring-3.4.1-1.mga2.i586
+>         libpam.so.0 is needed by gnome-keyring-3.4.1-1.mga2.i586
+> [root at ftgme2 init.d]#
+> 
+> rpmdrake using an "in names" search of "gnome-keyring" finds the i586
+> gnome-keyring-debug package, but not the i586 gnome-keyring itself .
+> 
+> I've checked, and Core 32 Release is enabled.
+> 
+> This came about because a Wine app that has been working all along
+> suddenly can't find /usr/lib/pkcs11/gnome-keyring-pkcs11.so which is
+> part of the i586 gnome-keyring package.  Trying to install it, as shown
+> above, gives no joy.
+> 
+> What am I missing here ?
+
+This is pretty standard.
+
+It's not installing gnome-keyring because you already have it installed.
+
+You can install it manually, via rpm -i but this will lead to some other
+problems (i.e. two pacakges with the same name installed, some shared
+files e.g. /usr/bin/gnome-keyring, all the translation messages etc.
+will be overwritten.
+
+Essentually It's not really something we should support even if you can
+force it with rpm directly. One of your rpm -V commands on that package
+(32 vs. 64 bit) will fail.
+
+So the correctly solution if some of the files are missing is to split
+the file:
+
+/usr/lib{64,}/pkcs11/gnome-keyring-pkcs11.so
+
+out into a separate package that is properly libified.
+
+Then you can happily install the different modules for both arches
+without affecting the main gnome-keyring application.
+
+That said, is it offiically supported to use
+/usr/lib{64,}/pkcs11/gnome-keyring-pkcs11.so outside of the main
+gnome-keyring binary? I don't know but it would be worth asking before
+looking to split it all up.
+
+
+Col
+
+
+-- 
+
+Colin Guthrie
+colin(at)mageia.org
+http://colin.guthr.ie/
+
+Day Job:
+  Tribalogic Limited http://www.tribalogic.net/
+Open Source:
+  Mageia Contributor http://www.mageia.org/
+  PulseAudio Hacker http://www.pulseaudio.org/
+  Trac Hacker http://trac.edgewall.org/
+
+
+