Description of problem:

I'm filing this against device-mapper, but it also applies to lvm2.

FC4 updates provides the following two packages:

device-mapper-1.02.07-2.0.i386.rpm
lvm2-2.02.06-1.0.fc4.i386.rpm

FC5 provides the following two packages:

device-mapper-1.02.02-3.2.i386.rpm
lvm2-2.02.01-1.2.1.i386.rpm

See the problem?  This causes breakage when upgrading an FC4 to an FC5
system.

Version-Release number of selected component (if applicable):

See above.

How reproducible:

Anyone trying to upgrade an FC4 system with yum will encounter problems
because of this.


Steps to Reproduce:
"yum upgrade" with an FC4 system; almost everyone will have device-mapper
  
Actual results:

Lots of conflicts; try to work around them by various combinations of package
removal and re-installation and "rpm --force".  Live with a corrupt RPM database.


Expected results:

A clean upgrade.  Yes, "yum upgrade" works cleanly if package maintainers
are careful to ensure that FCn+1 has versions that rpm/yum considers "newer"
than corresponding packages in FCn.


Additional info:

Please produce new versions of the device-mapper and lvm2 packages that have a
higher version number than any in FC4.  In particular, FC4 seems to have a newer
upstream version of device-mapper than FC5!  Why are you downgrading us?