On Thu, 2012-04-05 at 23:34 +0200, Kevin Kofler wrote:
John Reiser wrote:
Or, some packager forgot to use %{?_isa} when specifying package
dependencies which are [or become] architecture-dependent. This is a
common and systematic error which causes much grief. None of the tools
check
Adam Williamson wrote:
AFAICS the real problem here is that an update got unpushed. It seems
like Richard got the 64-bit version of libvirt -3 installed, then the -3
update got unpushed, then something wanted to install the 32-bit version
of libvirt. Obviously, since the update had been
On Thu, 2012-04-19 at 17:14 +0200, Kevin Kofler wrote:
Adam Williamson wrote:
AFAICS the real problem here is that an update got unpushed. It seems
like Richard got the 64-bit version of libvirt -3 installed, then the -3
update got unpushed, then something wanted to install the 32-bit
Adam Williamson wrote:
Um...no? The case listed *below* would be, but updates-testing doesn't
seem particularly relevant to the above case. If updates-testing didn't
exist at all, you'd still have the potential of this problem happening
if updates could be unpushed.
Stable updates cannot be
On Thu, Apr 05, 2012 at 11:34:29PM +0200, Kevin Kofler wrote:
John Reiser wrote:
Or, some packager forgot to use %{?_isa} when specifying package
dependencies which are [or become] architecture-dependent. This is a
common and systematic error which causes much grief. None of the tools
I still get this error several times a week, and I still have no idea
what it means or how I'm supposed to respond to it (other than
fiddling randomly with packages until it goes away).
The latest one:
# yum install /usr/sbin/libvirtd
[... yum spew deleted ...]
Error: Protected multilib
On Thu, Apr 5, 2012 at 2:23 PM, Richard W.M. Jones rjo...@redhat.com wrote:
I still get this error several times a week, and I still have no idea
what it means or how I'm supposed to respond to it (other than
fiddling randomly with packages until it goes away).
The latest one:
# yum install
On Thu, Apr 5, 2012 at 2:41 PM, drago01 drag...@gmail.com wrote:
On Thu, Apr 5, 2012 at 2:23 PM, Richard W.M. Jones rjo...@redhat.com wrote:
I still get this error several times a week, and I still have no idea
what it means or how I'm supposed to respond to it (other than
fiddling randomly
On Thu, Apr 05, 2012 at 01:23:28PM +0100, Richard W.M. Jones wrote:
I still get this error several times a week, and I still have no idea
what it means or how I'm supposed to respond to it (other than
fiddling randomly with packages until it goes away).
The latest one:
# yum install
On Thu, Apr 05, 2012 at 02:13:34PM +0100, Daniel P. Berrange wrote:
On Thu, Apr 05, 2012 at 01:23:28PM +0100, Richard W.M. Jones wrote:
I still get this error several times a week, and I still have no idea
what it means or how I'm supposed to respond to it (other than
fiddling randomly with
# yum install /usr/sbin/libvirtd
Error: Protected multilib versions: libvirt-client-0.9.10-2.fc17.i686 !=
libvirt-client-0.9.10-3.fc17.x86_64
What does the error mean?
...
Or, some packager forgot to use %{?_isa} when specifying package dependencies
which are [or become]
On Thu, 5 Apr 2012, Richard W.M. Jones wrote:
I still get this error several times a week, and I still have no idea
what it means or how I'm supposed to respond to it (other than
fiddling randomly with packages until it goes away).
The latest one:
# yum install /usr/sbin/libvirtd
[... yum
On Thu, Apr 05, 2012 at 06:32:47AM -0700, John Reiser wrote:
# yum install /usr/sbin/libvirtd
Error: Protected multilib versions: libvirt-client-0.9.10-2.fc17.i686 !=
libvirt-client-0.9.10-3.fc17.x86_64
What does the error mean?
...
Or, some packager forgot to use %{?_isa} when
On Thu, Apr 05, 2012 at 06:54:36PM +0100, Richard W.M. Jones wrote:
Is there any information about when this should be used? I don't
think I've ever written a spec file that uses it.
I think it is whenever a package containing a library (i.e. a multilib
package) is required via the package's
On Thu, Apr 5, 2012 at 7:54 PM, Richard W.M. Jones rjo...@redhat.com wrote:
On Thu, Apr 05, 2012 at 06:32:47AM -0700, John Reiser wrote:
# yum install /usr/sbin/libvirtd
Error: Protected multilib versions: libvirt-client-0.9.10-2.fc17.i686 !=
libvirt-client-0.9.10-3.fc17.x86_64
What
John Reiser wrote:
Or, some packager forgot to use %{?_isa} when specifying package
dependencies which are [or become] architecture-dependent. This is a
common and systematic error which causes much grief. None of the tools
check for it, which is another bug^Wopportunity for enhancement.
I get this error all the time, but I can't find a coherent explanation
for what it means.
What is the precise meaning of the protected multilib versions error?
# yum install /lib/ld-linux.so.2
[...]
Error: Protected multilib versions: glibc-2.14.90-4.i686 !=
glibc-2.14.90-1.x86_64
# yum
And now to the list as well...
On 4 Sep 2011 10:01, Niels de Vos ni...@nixpanic.net wrote:
On 4 Sep 2011 09:45, Richard W.M. Jones rjo...@redhat.com wrote:
I get this error all the time, but I can't find a coherent explanation
for what it means.
What is the precise meaning of the protected
Richard W.M. Jones writes:
glibc-common-2.14.90-4.x86_64
glibc-common-2.14.90-1.x86_64
This means that rpm/yum aborted in a middle of a upgrade.
You should clean this up using rpm -e glibc-common-2.14.90-1.x86_64
pgpf62s8f7GEk.pgp
Description: PGP signature
--
devel mailing list
19 matches
Mail list logo
