Ticket #697 (closed defect: worksforme)

Opened 14 years ago

Last modified 14 years ago

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:


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.


Package perl-LDAP failed verification.

hardcoding the version number in the Package works around this.


Change History

comment:1 Changed 14 years ago by solj

  • Milestone set to Bcfg2 1.0 Release

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)

WARNING! You need to establish a session before you can create or edit tickets. Otherwise the ticket will get treated as spam.


Add a comment

Modify Ticket

Change Properties
<Author field>
as closed
The resolution will be deleted. Next status will be 'reopened'

E-mail address and user name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.