1DNF-VERSIONLOCK(8)             dnf-plugins-core             DNF-VERSIONLOCK(8)
2
3
4

NAME

6       dnf-versionlock - DNF versionlock Plugin
7

DESCRIPTION

9       versionlock  is  a  plugin  that  takes a set of names and versions for
10       packages and excludes all other versions of those packages. This allows
11       you  to  protect  packages from being updated by newer versions. Alter‐
12       nately, it accepts a specific package version to exclude from  updates,
13       e.g.  for  when  it's necessary to skip a specific release of a package
14       that has known issues.
15
16       The plugin provides a command versionlock which allows you to view  and
17       edit the list of locked packages easily.
18
19       The  plugin  will walk each line of the versionlock file, and parse out
20       the name and version of the package. It will then exclude  any  package
21       by  that  name that doesn't match one of the versions listed within the
22       file. This is basically the same as using dnf --exclude for the package
23       name  itself  (as  you cannot exclude installed packages), but dnf will
24       still see the versions you have installed/versionlocked as available so
25       that dnf reinstall will still work, etc.
26
27       It can also work in the opposite way, like a fast exclude, by prefixing
28       a '!' character to the version recorded in the  lock  list  file.  This
29       specifically excludes a package that matches the version exactly.
30
31       Note the versionlock plugin does not apply any excludes in non-transac‐
32       tional operations like repoquery, list, info, etc.
33

SYNOPSIS

35       dnf  versionlock  [options]   [add|exclude|list|delete|clear]   [<pack‐
36       age-name-spec>]
37

ARGUMENTS

39       <package-name-spec>
40              Package spec to lock or exclude.
41

SUBCOMMANDS

43       dnf versionlock add <package-name-spec>
44              Add  a versionlock for all available packages matching the spec.
45              It means that only versions of packages  represented  by  <pack‐
46              age-name-spec>  will  be  available  for transaction operations.
47              Each <package-name-spec> is converted to concrete  NEVRAs  which
48              are  used  for locking. The NEVRAs to lock to are first searched
49              among installed packages and then (if none is found) in all cur‐
50              rently available packages.
51
52              Examples:
53
54                 Locking a package to the version installed:
55
56                     $ dnf repoquery --installed bash
57                     bash-0:5.0.7-1.fc30.x86_64
58
59                     $ dnf repoquery bash
60                     bash-0:5.0.2-1.fc30.i686
61                     bash-0:5.0.2-1.fc30.x86_64
62                     bash-0:5.0.7-1.fc30.i686
63                     bash-0:5.0.7-1.fc30.x86_64
64
65                     $ dnf versionlock add bash
66                     Adding versionlock on: bash-0:5.0.7-1.fc30.*
67
68                 Locking not installed package to any of available versions:
69
70                     $ dnf repoquery --installed mutt
71
72                     $ dnf repoquery mutt
73                     mutt-5:1.11.4-1.fc30.x86_64
74                     mutt-5:1.12.1-3.fc30.x86_64
75
76                     $ dnf versionlock add mutt
77                     Adding versionlock on: mutt-5:1.11.4-1.fc30.*
78                     Adding versionlock on: mutt-5:1.12.1-3.fc30.*
79
80              NOTE:
81                 Be careful when adding specific versions
82
83                 If  you  add a package specifying a version with dnf version‐
84                 lock mutt-5:1.11.4-1.fc30.x86_64 then, if you  run  dnf  ver‐
85                 sionlock     add    mutt    versionlock    will    not    add
86                 mutt-5:1.12.1-3.fc30.x86_64.
87
88       dnf versionlock exclude <package-name-spec>
89              Add an exclude (within  versionlock) for the available  packages
90              matching  the spec. It means that packages represented by <pack‐
91              age-name-spec> will be excluded from transaction operations.
92
93       dnf versionlock list or dnf versionlock
94              List the current versionlock entries.
95
96       dnf versionlock delete <package-name-spec>
97              Remove any matching versionlock entries.
98
99       dnf versionlock clear
100              Remove all versionlock entries.
101

OPTIONS

103       All general DNF options are accepted, see Options  in  dnf(8)  for  de‐
104       tails.
105
106       --raw  Do  not  resolve  <package-name-spec> to NEVRAs to find specific
107              version to lock to. Instead <package-name-spec> are used as they
108              are.  This  enables locking to not yet available versions of the
109              package.  For example you may want to keep the bash  package  on
110              major  version  5  and consume any future updates as far as they
111              keep the major version:
112
113                 $ dnf versionlock add --raw 'bash-5.*'
114                 Adding versionlock on: bash-5.*
115

CONFIGURATION

117       /etc/dnf/plugins/versionlock.conf
118
119       The minimal content of conf file should contain main sections with  en‐
120       abled and locklist parameters.
121
122       locklist
123              This  option  is  a string that points to the file which has the
124              versionlock information in it. Note that the file has  to  exist
125              (or  the versionlock plugin will make dnf exit). However, it can
126              be empty.
127
128              The file takes entries in the format of <package-name-spec> (op‐
129              tionally  prefixed with '!' for excludes).  See Specifying pack‐
130              ages in dnf(8) for details.
131

NOTES

133       A specified package does not have to exist within the  available  cache
134       of  repository  data  to  be considered valid for locking or exclusion.
135       This is by design, to accommodate use cases such as  a  presently  dis‐
136       abled repository. However, a package must exist in the repository cache
137       when the add or exclude subcommands are invoked for it.
138

AUTHOR

140       See AUTHORS in your Core DNF Plugins distribution
141
143       2023, Red Hat, Licensed under GPLv2+
144
145
146
147
1484.4.3                            Oct 06, 2023               DNF-VERSIONLOCK(8)
Impressum