Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Yum Versionlock validation is wrong #6

Open
02strich opened this issue Jun 2, 2014 · 2 comments
Open

Yum Versionlock validation is wrong #6

02strich opened this issue Jun 2, 2014 · 2 comments

Comments

@02strich
Copy link

02strich commented Jun 2, 2014

The validation of the name parameter enforces the specification of an epoch, which is not required in RPM as packages do not need to have an epoch value.

@vholer
Copy link
Contributor

vholer commented Nov 6, 2014

I believe it's required, see man yum-versionlock:

   /etc/yum/pluginconf.d/versionlock.list
          The default place to put  package  version  lock  information  (one
          package  and version per. line). The file takes entries in the fol-
          lowing format EPOCH:NAME-VERSION-RELEASE.ARCH See rpm(8)  for  more
          information  on  custom query formats. If the package does not have
          an EPOCH the number will default to 0.

It's good to follow this format otherwise version locking doesn't work or works strange. And I would better not prefix package with default epoch "0:" if missing...

@02strich
Copy link
Author

I actually no longer have the test case available which triggered creating this issue, but I believe the last sentence from the quote did not work or did so in an unexpected way. What is you reason for not making the epoch optional (and thereby following RPM)?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants