1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-dev] 64-bit urpmi not "seeing" Core 32 even if enabled ?
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%2064-bit%20urpmi%20not%20%22seeing%22%20Core%2032%20even%20if%20enabled%20%3F&In-Reply-To=%3C4FDF447A.5%40colin.guthr.ie%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="016612.html">
<LINK REL="Next" HREF="016618.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] 64-bit urpmi not "seeing" Core 32 even if enabled ?</H1>
<B>Colin Guthrie</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%2064-bit%20urpmi%20not%20%22seeing%22%20Core%2032%20even%20if%20enabled%20%3F&In-Reply-To=%3C4FDF447A.5%40colin.guthr.ie%3E"
TITLE="[Mageia-dev] 64-bit urpmi not "seeing" Core 32 even if enabled ?">mageia at colin.guthr.ie
</A><BR>
<I>Mon Jun 18 17:08:42 CEST 2012</I>
<P><UL>
<LI>Previous message: <A HREF="016612.html">[Mageia-dev] 64-bit urpmi not "seeing" Core 32 even if enabled ?
</A></li>
<LI>Next message: <A HREF="016618.html">[Mageia-dev] 64-bit urpmi not "seeing" Core 32 even if enabled ?
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#16614">[ date ]</a>
<a href="thread.html#16614">[ thread ]</a>
<a href="subject.html#16614">[ subject ]</a>
<a href="author.html#16614">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>'Twas brillig, and Frank Griffin at 18/06/12 15:40 did gyre and gimble:
><i> If this isn't just a case of me not seeing something obvious, I'll enter
</I>><i> a bug report...
</I>><i>
</I>><i> [<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">ftg at ftgme2</A> release]$ pwd
</I>><i> /mnt/cauldron/i586/media/core/release
</I>><i> [<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">ftg at ftgme2</A> release]$ ls -l *keyring*
</I>><i> -rw-r--r-- 1 ftg ftg 717173 Apr 18 18:21
</I>><i> gnome-keyring-3.4.1-1.mga2.i586.rpm
</I>><i> -rw-r--r-- 1 ftg ftg 19170 Nov 21 2011
</I>><i> gnome-keyring-sharp-1.0.2-2.mga2.i586.rpm
</I>><i> -rw-r--r-- 1 ftg ftg 13759 Nov 21 2011
</I>><i> gnome-keyring-sharp-doc-1.0.2-2.mga2.i586.rpm
</I>><i> -rw-r--r-- 1 ftg ftg 24632 Nov 26 2011
</I>><i> gnome-python-gnomekeyring-2.32.0-12.mga2.i586.rpm
</I>><i> -rw-r--r-- 1 ftg ftg 24829 Nov 20 2011
</I>><i> jpilot-keyring-1.8.1-1.mga2.i586.rpm
</I>><i> -rw-r--r-- 1 ftg ftg 54372 Apr 18 18:16
</I>><i> libgnome-keyring0-3.4.1-1.mga2.i586.rpm
</I>><i> -rw-r--r-- 1 ftg ftg 77144 Apr 18 18:16
</I>><i> libgnome-keyring-devel-3.4.1-1.mga2.i586.rpm
</I>><i> -rw-r--r-- 1 ftg ftg 11033 Apr 18 18:16
</I>><i> libgnome-keyring-gir1.0-3.4.1-1.mga2.i586.rpm
</I>><i> -rw-r--r-- 1 ftg ftg 33992 Apr 18 18:16
</I>><i> libgnome-keyring-i18n-3.4.1-1.mga2.i586.rpm
</I>><i> -rw-r--r-- 1 ftg ftg 9647 Jun 14 02:15
</I>><i> libsvn-gnome-keyring0-1.7.5-3.mga3.i586.rpm
</I>><i> -rw-r--r-- 1 ftg ftg 5763 Jun 14 02:15
</I>><i> subversion-gnome-keyring-devel-1.7.5-3.mga3.i586.rpm
</I>><i> [<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">ftg at ftgme2</A> release]$
</I>><i>
</I>><i> but
</I>><i> [<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">root at ftgme2</A> init.d]# urpmi gnome-keyring
</I>><i> Package gnome-keyring-3.4.1-1.mga2.x86_64 is already installed
</I>><i> [<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">root at ftgme2</A> init.d]# urpmi
</I>><i> /mnt/cauldron/i586/media/core/release/gnome-keyring-3.4.1-1.mga2.i586.rpm
</I>><i> [<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">root at ftgme2</A> init.d]# urpmq gnome-keyring-3.4.1-1.mga2.i586.rpm
</I>><i> urpmq: cannot read rpm file "gnome-keyring-3.4.1-1.mga2.i586.rpm"
</I>><i> [<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">root at ftgme2</A> init.d]# rpm -i
</I>><i> /mnt/cauldron/i586/media/core/release/gnome-keyring-3.4.1-1.mga2.i586.rpm
</I>><i> error: Failed dependencies:
</I>><i> libgck-1.so.0 is needed by gnome-keyring-3.4.1-1.mga2.i586
</I>><i> libgcr-base-3.so.1 is needed by gnome-keyring-3.4.1-1.mga2.i586
</I>><i> libpam.so.0 is needed by gnome-keyring-3.4.1-1.mga2.i586
</I>><i> [<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">root at ftgme2</A> init.d]#
</I>><i>
</I>><i> rpmdrake using an "in names" search of "gnome-keyring" finds the i586
</I>><i> gnome-keyring-debug package, but not the i586 gnome-keyring itself .
</I>><i>
</I>><i> I've checked, and Core 32 Release is enabled.
</I>><i>
</I>><i> This came about because a Wine app that has been working all along
</I>><i> suddenly can't find /usr/lib/pkcs11/gnome-keyring-pkcs11.so which is
</I>><i> part of the i586 gnome-keyring package. Trying to install it, as shown
</I>><i> above, gives no joy.
</I>><i>
</I>><i> What am I missing here ?
</I>
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
<A HREF="http://colin.guthr.ie/">http://colin.guthr.ie/</A>
Day Job:
Tribalogic Limited <A HREF="http://www.tribalogic.net/">http://www.tribalogic.net/</A>
Open Source:
Mageia Contributor <A HREF="http://www.mageia.org/">http://www.mageia.org/</A>
PulseAudio Hacker <A HREF="http://www.pulseaudio.org/">http://www.pulseaudio.org/</A>
Trac Hacker <A HREF="http://trac.edgewall.org/">http://trac.edgewall.org/</A>
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="016612.html">[Mageia-dev] 64-bit urpmi not "seeing" Core 32 even if enabled ?
</A></li>
<LI>Next message: <A HREF="016618.html">[Mageia-dev] 64-bit urpmi not "seeing" Core 32 even if enabled ?
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#16614">[ date ]</a>
<a href="thread.html#16614">[ thread ]</a>
<a href="subject.html#16614">[ subject ]</a>
<a href="author.html#16614">[ author ]</a>
</LI>
</UL>
<hr>
<a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More information about the Mageia-dev
mailing list</a><br>
</body></html>
|
