linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: "Bryn M. Reeves" <bmr@redhat.com>
To: jlpenneree@ncnumericable.com,
	LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] upgrade lvm2
Date: Mon, 21 Jun 2010 11:46:06 +0100	[thread overview]
Message-ID: <4C1F42EE.5090202@redhat.com> (raw)
In-Reply-To: <1277115228.30102.2.camel@CHP-92AF47.upcnoos.int>

On 06/21/2010 11:13 AM, PENNEREE JEAN-LOUIS wrote:
> Hi,
> 
> I would like to upgrade lvm2 version on a RHEL5 machine.

This isn't really an lvm2/device-mapper related question - your problem
appears to be just package management.

> #rpm -Uvh device-mapper-1.02.39-1.el5.x86_64.rpm
> 
> le fichier /usr/include/libdevmapper-event.h de l'installation de 
> device-mapper-1.02.39-1.el5 entre en conflit avec le fichier du paquetage 
> device-mapper-1.02.20-1.el5
> le fichier /usr/include/libdevmapper.h de l'installation de 
> device-mapper-1.02.39-1.el5 entre en conflit avec le fichier du paquetage 
> device-mapper-1.02.20-1.el5
> le fichier /usr/share/man/man8/dmsetup.8.gz de l'installation de 
> device-mapper-1.02.39-1.el5 entre en conflit avec le fichier du paquetage 
> device-mapper-1.02.20-1.el5

So the files conflict with an older version. It looks like you have an
earlier RPM (1.02.20-1.el5) built for the i386 architecture installed.

This is normal on 64-bit x86 as it is a multilib platform (it means both
32 and 64 bit applications that use the device-mapper library can be
installed and used).

E.g.:

# rpm -q --qf="%{NAME}-%{VERSION}-%{RELEASE}.%{ARCH}\n" device-mapper
device-mapper-1.02.39-1.el5.x86_64
device-mapper-1.02.39-1.el5.i386

When it comes to upgrading however you must update the packages together
in a single transaction, e.g.:

# rpm -Uvh device-mapper-1.02.39-1.el5.x86_64.rpm \
           device-mapper-1.02.39-1.el5.i386.rpm

Alternately use the distribution-supplied update tool (yum for RHEL5) to
apply updates automatically and this will resolve dependencies and pull
in any other requirements automatically.

Regards,
Bryn.

      reply	other threads:[~2010-06-21 10:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-21 10:13 [linux-lvm] upgrade lvm2 PENNEREE JEAN-LOUIS
2010-06-21 10:46 ` Bryn M. Reeves [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4C1F42EE.5090202@redhat.com \
    --to=bmr@redhat.com \
    --cc=jlpenneree@ncnumericable.com \
    --cc=linux-lvm@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).