Bug 852468

Summary: device-mapper* subpackages versioning could cause troubles
Product: Red Hat Enterprise Linux 6 Reporter: Jan Blazek <jblazek>
Component: lvm2Assignee: LVM and device-mapper development team <lvm-team>
Status: CLOSED NOTABUG QA Contact: Cluster QE <mspqa-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.4CC: agk, dwysocha, heinzm, jbrassow, msnitzer, prajnoha, prockai, thornber, zkabelac
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-08-28 17:16:19 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Jan Blazek 2012-08-28 14:54:24 UTC
device-mapper* subpackages of lvm2 package have different version than main lvm2 package. device-mapper NVR is glued together from %{device_mapper_version} and lvm2's %{release}. There could possibly occur a dangerous situation when lvm2 version increases, %{device_mapper_version} wouldn't change but because of lower %release the resulting device-mapper's NVR would be lower than what was already shipped to customers.

Comment 2 Alasdair Kergon 2012-08-28 17:16:19 UTC
"There could possibly occur a dangerous situation when lvm2 version increases, %{device_mapper_version} wouldn't change but because of lower %release "

The %release is NOT lower in such circumstances: your scenario does not arise.
Releases that only affect lvm2, not dm, are rare anyway and unlikely ever to arise in RHEL.  (Version numbers are controlled by upstream and both always change in a .y RHEL release, and neither changes in a .z release.)