1LOCKS(5) LIBZYPP LOCKS(5)
2
6 locks - libzypp locking file
7
9 The file /etc/zypp/locks is read by libzypp at start-up if zypp.conf
10 allows it. The entries are used for initial locking of packages.
11 Locking a package means not allowing to install or uninstall it.
12 Valid entries are of the form:
14 attribute: value
16 Where attributes and their values are described below.
17 Locks are separated by an empty lines.
19
21 All attributes are lower-case.
22 repo
24 specifies repository restriction. Only alias is accepted.
25 By default all repositories match.
26 type
28 resolvable type restriction. The values can be package, patch,
29 pattern, product and srcpackage.
30 By default all types match.
31 case_sensitive
33 if strings are matched case sensitive. The values are true, false,
34 on, off.
35 The default is case insensitive.
36 install_status
38 status of object. Possible states are installed, not-installed and
39 all. If more install statuses are specified then the last one is
40 used. The values are installed for all packages which are
41 installed, non-installed for packages which can be installed or
42 reinstalled and all for both.
43 The default is all.
44 match_type
46 type of string matching in values. Does not affect type and repo
47 which must be specified exactly. The values are exact, substring,
48 regex for regular expressions, glob for matching as on the command
49 line, and word.
50 The default is substring.
51 query_string
53 String to be matched in multiple attributes. Should be restricted
54 by another attribute with empty value (it is recommended, because
55 without restriction expect some performance problems).
56 version
58 Restrict the lock only to some versions. It contains two parts: an
59 optional operator and the version.
60 The operator is ==, !=, <, >, ⇐, >=. If operator is not specified
61 then == is used.
62 The version has the format [epoch:+]+version[-’release'].
63 Example: version: < 0:0.11.4-2
64 solvable_name
66 name of object (e.g. zypper)
67 solvable_summary
69 summary of object
70 solvable_arch
72 architecture of object (e.g. x86_64, i586)
73 solvable_description
75 description of object
76 solvable_eula
78 license text of objects which request accepting license by user
79 solvable_license
81 license of package (only for package) (e.g. GPL2)
82 solvable_keywords
84 keywords which specify package (only for package)
85 solvable_authors
87 authors of package (only for package)
88 solvable_group
90 package group (only for package) (e.g. Development/Tools/Version
91 Control )
92 update_reference_type
94 reference for update (e.g. bugzilla,cve) (only for patches)
95
97 Exact Package
98 This is the way YaST UI does it. Lock k3b (e.g. you don’t want to
99 update it).
100 -----locks-----
102 type: package
103 solvable_name: k3b
104 match_type: exact
105 case_sensitive: on
106 Package Wildcard
108 This is the way "zypper addlock cross-*-gcc-icecream-backend" does
109 it.
110 -----locks-----
112 type: package
113 solvable_name: cross-*-gcc-icecream-backend
114 match_type: glob
115 case_sensitive: on
116 Versioned Lock
118 Do not install new GCC. This format is used when converting from
119 the openSUSE-10.3 lock format.
120 -----locks-----
122 solvable_name: gcc
123 match_type: glob
124 version: > 4.2
125 Anything named KDE
127 Locks everything which contains kde in the name.
128 -----locks-----
130 solvable_name: kde
131 Anything mentioning KDE
133 Locks everything which contains kde in the name, summary, or
134 description.
135 -----locks-----
137 query_string: kde
138 solvable_name:
139 solvable_summary:
140 solvable_description:
141
143 This manual page only covers the most important attributes. The
144 complete list is available at <http://en.opensuse.org/Libzypp/
145 Locksfile>
146
148 Josef Reidinger <jreidinger@suse.cz <jreidinger@suse.cz>> Manual page
149 contributions by Martin Vidner <mvidner@suse.cz <mvidner@suse.cz>>.
150
152 zypper(8)
153SUSE Linux 2019-11-12 LOCKS(5)