2018-07-13 18:47:00 +08:00
# rpmlint
2015-10-03 17:50:39 +08:00
2021-05-27 15:44:27 +08:00
[![Build and Test ](https://github.com/rpm-software-management/rpmlint/actions/workflows/main.yml/badge.svg?branch=main )](https://github.com/rpm-software-management/rpmlint/actions/workflows/main.yml)
2022-03-22 17:51:25 +08:00
[![Build and Test 2 ](https://github.com/rpm-software-management/rpmlint/actions/workflows/main.yml/badge.svg?branch=opensuse )](https://github.com/rpm-software-management/rpmlint/actions/workflows/main.yml)
2022-12-22 18:15:55 +08:00
[![build result ](https://build.opensuse.org/projects/devel:openSUSE:Factory:rpmlint/packages/rpmlint/badge.svg?type=default&repository=openSUSE_Factory )](https://build.opensuse.org/package/show/devel:openSUSE:Factory:rpmlint/rpmlint)
2022-03-08 03:43:08 +08:00
[![repology ](https://repology.org/badge/latest-versions/rpmlint.svg )](https://repology.org/project/rpmlint/versions)
2018-07-13 18:47:00 +08:00
2019-08-15 19:17:48 +08:00
`rpmlint` is a tool for checking common errors in RPM packages.
`rpmlint` can be used to test individual packages before uploading or to check
2018-07-13 18:47:00 +08:00
an entire distribution.
2019-08-15 19:17:48 +08:00
`rpmlint` can check binary RPMs, source RPMs, and plain specfiles, but all
2019-07-13 04:03:30 +08:00
checks do not apply to all argument types.
2019-08-15 19:17:48 +08:00
For best check coverage, run `rpmlint` on source RPMs instead of
2019-07-13 04:03:30 +08:00
plain specfiles.
2015-10-03 17:50:39 +08:00
2019-08-15 19:17:48 +08:00
The idea for `rpmlint` is from the lintian tool of the Debian project.
All the checks reside in `rpmlint/checks` folder. Feel free to provide new
2018-07-13 18:47:00 +08:00
checks and suggestions at:
2015-10-03 17:50:39 +08:00
https://github.com/rpm-software-management/rpmlint
2019-07-15 19:52:30 +08:00
## Install
2019-08-15 19:17:48 +08:00
For installation on your machine you will need the following packages:
2019-07-15 19:52:30 +08:00
2019-08-15 19:42:19 +08:00
Mandatory:
2022-02-11 20:03:56 +08:00
- Python 3.8 or newer
2022-07-24 22:28:12 +08:00
- python3-setuptools, python3-tomli (for `python3 < 3.11` ), python3-tomli-w,
python3-pyxdg, python3-pybeam
2019-07-15 19:52:30 +08:00
- rpm and its python bindings
2020-10-05 17:22:15 +08:00
- binutils, cpio, gzip, bzip, xz and zstd
2019-08-15 19:17:48 +08:00
2021-05-10 13:43:04 +08:00
Optional, for running the test suite:
- devscripts
- dash
- a 32-bit glibc if on a 64-bit architecture
- desktop-file-utils
2019-08-15 19:17:48 +08:00
- libmagic and its python bindings
2021-05-10 13:43:04 +08:00
- enchant and its python bindings, along with en_US and cs_CZ dictionaries
2019-08-15 19:17:48 +08:00
- appstream-util, part of appstream-glib
2019-07-15 19:52:30 +08:00
2021-03-23 04:27:46 +08:00
`rpmlint` is part of most distributions and as an user you can simply
dnf install rpmlint
2019-07-15 19:52:30 +08:00
## Testing
2019-07-13 04:03:30 +08:00
2021-05-16 22:10:32 +08:00
You will need to have all the required modules as listed on the Install section above.
2020-03-25 21:11:13 +08:00
You will also need `pytest` ,`pytest-cov`, `pytest-xdist` , and `pytest-flake8` .
2019-07-15 19:52:30 +08:00
If all the dependencies are present you can just execute tests using:
2020-02-12 16:59:45 +08:00
`python3 -m pytest`
2019-07-15 19:52:30 +08:00
2019-08-15 19:17:48 +08:00
Or even pick one of the tests using `pytest` :
2019-07-26 20:32:58 +08:00
`python3 -m pytest test/test_config.py`
2019-07-26 20:57:33 +08:00
## Bugfixing and contributing
2019-08-15 19:17:48 +08:00
Any help is, of course, welcome but honestly most probable cause for your visit
here is that `rpmlint` is marking something as invalid while it shouldn't or
2019-07-26 20:57:33 +08:00
it is marking something as correct while it should not either :)
2019-08-15 19:17:48 +08:00
Now there is an easy way how to fix that. Our testsuite simply needs an
2019-07-26 20:57:33 +08:00
extension to take the above problem into the account.
Primarily we just need the offending rpm file (best the smallest you can
find or we would soon take few GB to take a checkout) and some basic
expectation of what should happen.
2019-08-15 19:17:48 +08:00
### Example workflow
2019-07-26 20:57:33 +08:00
1) I have rpmfile that should report unreadable zip file
2) I store this file in git under `test/binary/texlive-codepage-doc-2018.151.svn21126-38.1.noarch.rpm`
3) Now I need to figure out what `check` should test this, in this case `test_zip.py`
4) For the testing I will have to devise a small function that validates my expectations:
```
@pytest .mark.parametrize('package', ['binary/texlive-codepage-doc'])
def test_zip2(tmpdir, package, zipcheck):
output, test = zipcheck
test.check(get_tested_package(package, tmpdir))
out = output.print_results(output.results)
assert 'W: unable-to-read-zip' in out
```
As you can see it is not so hard and with each added test we get better
coverage on what is really expected from rpmlint and avoid naughty regressions
2019-08-15 19:17:48 +08:00
in the long run.
2019-07-26 20:57:33 +08:00
2020-03-25 21:21:21 +08:00
Preferable approach for binary packages is to create artificial testcase (to keep binaries small and trivial).
2020-02-12 16:59:45 +08:00
We are currently using OBS to produce binaries:
2021-08-10 20:06:35 +08:00
https://build.opensuse.org/project/show/devel:openSUSE:Factory:rpmlint:tests
2020-02-12 16:59:45 +08:00
For a sample package see:
2021-08-10 20:06:35 +08:00
https://build.opensuse.org/package/show/devel:openSUSE:Factory:rpmlint:tests/non-position-independent-exec
2020-02-12 16:59:45 +08:00
2018-07-13 18:47:00 +08:00
## Configuration
If you want to change configuration options or the list of checks you can
2019-08-15 19:17:48 +08:00
use the following locations:
2018-07-13 18:47:00 +08:00
2020-10-29 16:40:18 +08:00
`/etc/xdg/rpmlint/*toml`
2018-07-13 18:47:00 +08:00
2020-10-29 16:40:18 +08:00
`$XDG_CONFIG_HOME/rpmlint/*toml`
2018-07-13 18:47:00 +08:00
2019-08-15 19:17:48 +08:00
The configuration itself is a `toml` file where for some basic inspiration
2021-03-23 05:24:07 +08:00
you can check up [`rpmlint/configdefaults.toml` ](rpmlint/configdefaults.toml ) which specifies format/defaults.
2015-10-03 17:50:39 +08:00
2020-10-29 16:40:18 +08:00
One can also include additional configuration files (or directories) by using the `--config` option.
Note that all TOML configuration values are merged and not overridden.
So e.g. values in a list are concatenated. If you need an override,
use `*.override.*toml` configuration file, where all defined values are selected as default.
2019-08-15 19:17:48 +08:00
Additional option to control `rpmlint` behaviour is the addition of `rpmlintrc` file
which uses old syntax for compatibility with old `rpmlint` releases, yet
it can be normal `toml` file if you wish:
2015-10-03 17:50:39 +08:00
2021-03-23 05:09:19 +08:00
setBadness('check', 0)
addFilter('test-i-ignore')
2022-05-09 16:05:31 +08:00
The location of `rpmlintrc` can be set using `--rpmlintrc` option.
Or it can load any `*.rpmlintrc` or `*-rpmlintrc` that are located in the same
folder as check RPM file (or a specfile). Note the auto-loading happens only
when one RPM file (or a specfile) is used.
The best practice is to store the name in `$PACKAGE_NAME.rpmlintrc` .
2021-03-23 18:06:54 +08:00
`setBadness` overrides a default badness for a given check and `addFilter` ignores all errors
2021-06-11 19:29:13 +08:00
that match the given regular expression (one cannot filter out errors that are listed in `BlockedFilters`
in a configuration file).