-
-
Notifications
You must be signed in to change notification settings - Fork 101
[needs validation] allow RpmNameGlob for versionlock entries #228
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
base: master
Are you sure you want to change the base?
Conversation
As stated in the manpage [1] yum versionlock supports package-wildcard and does not require exact matches for package-names. The following is valid `versionlock.list` content: ``` libvirt*-0:7.6.0-*.* qemu*-0:6.1.0-*.* ``` This commit swaps `Yum::RpmName` with `Yum::RpmNameGlob` for the versionlock `assert_type()` and thus allowing the above mentioned examples. [1] https://man7.org/linux/man-pages/man1/yum-versionlock.1.html
c151ebb to
de4dfd3
Compare
|
versionlock config file is very purely documented, and years of use was just accidental. https://bugzilla.redhat.com/show_bug.cgi?id=1757895#c9 command line supports wildcards, config file never did. only exact match was allowed, so anything else was rejected as a side effect |
|
@vchepkov Verified it's working for RHEL-8 Using But when trying the same after writing the regex directly to |
As stated in the manpage [1] yum versionlock supports package-wildcard
and does not require exact matches for package-names.
The following is valid
versionlock.listcontent:This commit swaps
Yum::RpmNamewithYum::RpmNameGlobfor theversionlock
assert_type()and thus allowing the above mentionedexamples.
[1] https://man7.org/linux/man-pages/man1/yum-versionlock.1.html