1RPMDEPLINT(1)                     rpmdeplint                     RPMDEPLINT(1)
2
3
4

NAME

6       rpmdeplint  -  a  tool to find errors in RPM packages in the context of
7       their dependency graph
8

SYNOPSIS

10       rpmdeplint COMMAND [--repo NAME,PATH] [RPMPATH]
11
12

DESCRIPTION

14       The rpmdeplint command will test dependency satisfiability of given RPM
15       packages against given repositories.
16

OPTIONS

18       --repo NAME,PATH
19              You  can  provide  multiple  repos of each type. The NAME may be
20              anything you choose. The path must either be a  filesystem  path
21              or a URL. In either case, the path is expected to point at repo‐
22              data/repomd.xml.
23
24       --repos-from-system
25              Use  yum   repos   from   the   system-wide   configuration   in
26              /etc/yum.conf  and /etc/yum.repos.d/*.repo. Repos which are dis‐
27              abled in the configuration (enabled=0) are ignored.
28
29              This option can be combined with one or more --repo options.
30

ARGUMENTS

32       RPMPATH
33              Path to an RPM package. This  can  be  a  relative  or  absolute
34              filesystem path.
35

COMMANDS

37       check  Performs each of the checks listed below.
38
39       check-sat
40              Checks  for  unmet  dependencies  with  the  given  RPM packages
41              against  the  given  repositories.   Each  unmet  dependency  is
42              listed.
43
44       check-repoclosure
45              Checks  for  unmet  dependencies in the given repositories, when
46              considered together with the given packages. This check is simi‐
47              lar  to check-sat, except it checks only packages in the reposi‐
48              tories, not the packages under test.
49
50              Packages are only considered to be available for dependency res‐
51              olution  if they are the latest version and not obsoleted by any
52              other package.  Therefore this check can detect problems where a
53              package under test is updating an existing package in the repos‐
54              itories, but it no longer provides a requirement needed by  some
55              other package in the repositories.
56
57              In  case  a  pre-existing repoclosure problem is found (that is,
58              the same problem exists when considering only  the  repositories
59              without the packages under test) a warning is printed to stderr,
60              but the check is not considered to have failed.
61
62       check-conflicts
63              Checks for undeclared file conflicts in the given RPM  packages:
64              that  is, when one of the given package contains a file which is
65              also contained in some other package.
66
67              This command will not report a file as conflicting  between  two
68              packages if:
69
70              • there  is  an explicit RPM Conflicts between the two packages;
71                or
72
73              • the file’s checksum, permissions, owner, and group are identi‐
74                cal in both packages (RPM allows both packages to own the file
75                in this case); or
76
77              • the file’s color is different between the  two  packages  (RPM
78                will  silently  resolve  the  conflict in favour of the 64-bit
79                file).
80
81       check-upgrade
82              Checks that there are no existing packages in  the  repositories
83              which would upgrade or obsolete the given packages.
84
85              If  this  check fails, it means that the package under test will
86              never be installed (since the package manager will  always  pick
87              the  newer  or obsoleting package from the repositories instead)
88              which is not desirable, assuming the package is intended  as  an
89              update.
90
91       list-deps
92              All dependencies will be listed for each given RPM package.
93

EXIT STATUS

95       0      Normally, exit status is 0 if rpmdeplint executes successfully.
96
97       1      Errors that result in tracebacks, such as infrastructure errors.
98
99       2      Usage error, in case of incorrect use of commands or options.
100
101       3      Failure of a test.
102

EXAMPLES

104       Test  if  an  RPM package has unsatisfied dependencies against a remote
105       repository:
106
107          rpmdeplint check-sat --repo beaker,https://beaker-project.org/yum/client/Fedora23/ my-package.rpm
108
109            Problems with dependency set:
110            nothing provides python(abi) = 2.7 needed by some-package-1.2.3.fc23.noarch
111            nothing provides TurboGears >= 1.1.3 needed by other-package-33.2-1.fc23.noarch
112
113       List all dependencies for my-package.rpm:
114
115          rpmdeplint list-deps --repo beaker,https://beaker-project.org/yum/client/Fedora23/ my-package.rpm
116
117            my-package has 72 dependencies:
118                    basesystem-11-1.fc23.noarch
119                    bash-4.3.42-1.fc23.x86_64
120                    beaker-common-22.1-1.fc22.noarch
121                    ....
122

BUGS

124       Bug reports can be submitted to https://bugzilla.redhat.com/.
125

AUTHOR

127       rpmdeplint contributors
128

130       2022, Red Hat
131
132
133
134
1351.4                              Jan 21, 2022                    RPMDEPLINT(1)
Impressum