3.21. Checking cello for sanity
This section shows possible warnings and errors that can occur when checking RPM sanity on the example of the cello SPEC file and pello binary RPM.
3.21.1. Checking the cello SPEC File
Exemple 3.8. Output of running the rpmlint
command on the SPEC file for cello
$ rpmlint ~/rpmbuild/SPECS/cello.spec /home/admiller/rpmbuild/SPECS/cello.spec: W: invalid-url Source0: https://www.example.com/cello/releases/cello-1.0.tar.gz HTTP Error 404: Not Found 0 packages and 1 specfiles checked; 0 errors, 1 warnings.
For cello.spec
, there is only one warning, which says that the URL listed in the Source0
directive is unreachable. This is expected, because the specified example.com
URL does not exist. Presuming that this URL will work in the future, you can ignore this warning.
Exemple 3.9. Output of running the rpmlint
command on the SRPM for cello
$ rpmlint ~/rpmbuild/SRPMS/cello-1.0-1.el8.src.rpm cello.src: W: invalid-url URL: https://www.example.com/cello HTTP Error 404: Not Found cello.src: W: invalid-url Source0: https://www.example.com/cello/releases/cello-1.0.tar.gz HTTP Error 404: Not Found 1 packages and 0 specfiles checked; 0 errors, 2 warnings.
For the cello
SRPM, there is a new warning, which says that the URL specified in the URL
directive is unreachable. Assuming the link will be working in the future, you can ignore this warning.
3.21.2. Checking the cello binary RPM
When checking binary RPMs, rpmlint
checks for the following items:
- Documentation
- Manual pages
- Consistent use of the filesystem hierarchy standard
Exemple 3.10. Output of running the rpmlint
command on the binary RPM for cello
$ rpmlint ~/rpmbuild/RPMS/x86_64/cello-1.0-1.el8.x86_64.rpm cello.x86_64: W: invalid-url URL: https://www.example.com/cello HTTP Error 404: Not Found cello.x86_64: W: no-documentation cello.x86_64: W: no-manual-page-for-binary cello 1 packages and 0 specfiles checked; 0 errors, 3 warnings.
The no-documentation
and no-manual-page-for-binary
warnings say that he RPM has no documentation or manual pages, because you did not provide any. Apart from the above warnings, the RPM passed rpmlint
checks.