Bug 1645564 - [rfe] Allow versionlock to lock only parts of package version
Summary: [rfe] Allow versionlock to lock only parts of package version
Alias: None
Product: Fedora
Classification: Fedora
Component: dnf-plugins-core
Version: 29
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Marek Blaha
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2018-11-02 14:35 UTC by sedrubal
Modified: 2019-11-27 18:10 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2019-11-27 18:10:25 UTC
Type: Bug

Attachments (Terms of Use)

Description sedrubal 2018-11-02 14:35:52 UTC
Description of problem:
While we want to do security updates of some packages automatically, we want to do major feature updates manually. Therefore we want to lock only parts of the package version (which conforms with semver), but dnf versionlock does not allow this, because it immediately expands the version pattern and pins all known versions.

Version-Release number of selected component (if applicable):

How reproducible: Always

Steps to Reproduce:
1. dnf versionlock 'bash-4.*'

Actual results:
dnf prints the following message:
Adding versionlock on: bash-0:4.4.23-5.fc29.*

Expected results:
dnf prints the following message:
Adding versionlock on: bash-4.*

Additional info:
We achieved it by just writing `bash-4.*` to /etc/dnf/plugins/versionlock.list, but this sometimes leads rpm to mess up its database for some reason.
I'm not sure but maybe this is related to 1643676.

Comment 2 Marek Blaha 2018-11-06 06:12:20 UTC
It's related in the sense of the bug reported in https://bugzilla.redhat.com/show_bug.cgi?id=1643676 prevents dnf from parsing "bash-4.*" in the versionlock.list config file as a package specification.

Comment 3 Marek Blaha 2019-10-04 07:10:58 UTC
I created PR https://github.com/rpm-software-management/dnf-plugins-core/pull/363 that adds --raw option to versionlock command.

Comment 4 Ben Cotton 2019-10-31 18:47:36 UTC
This message is a reminder that Fedora 29 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '29'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 29 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 5 Ben Cotton 2019-11-27 18:10:25 UTC
Fedora 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.