Ticket #697 (closed defect: worksforme)
YUMng fails to handle Epoch values correctly in rpms
| Reported by: | Travis Campbell <[email protected]…> | Owned by: | desai |
|---|---|---|---|
| Priority: | major | Milestone: | Bcfg2 1.0.0 Release |
| Component: | bcfg2-client | Version: | |
| Keywords: | Cc: |
Description
I have a package defined as this:
<Package name='perl-LDAP' version='auto' />
The version I have in yum is perl-LDAP-0.33-3.fc6.noarch from RHEL5u3. YUMng is interpreting the Epoch value in the RPM causing the version number to appear to be 1:0.33-3.fc6.noarch which makes bcfg2 fail the version check with:
Running YUMng.Install() Attempting to install packages Single Pass for Install Succeded
Wrong version installed. Want 0.33-3.fc6.noarch, but have 1:0.33-3.fc6.
noarch
Package perl-LDAP failed verification.
hardcoding the version number in the Package works around this.
Attachments
Change History
comment:2 Changed 14 years ago by desai
- Status changed from new to closed
- Resolution set to worksforme
Is this happening with trunk? I can't replicate this (centos 5.3 with perl-LDAP 1:0.33-3.fc6.noarch), either in the install case, or in the verification case. (a system without the package installed installs it, and then verifies properly, and an system with it installed verifies it properly the first time)
