lsbpkgchk - check LSB conformance of a package
lsbpkgchk [-hvnAt] [-L LANANANAME] [-T PRODUCT] [-M MODULE]... ] [-j
JOURNAL] [-d DEPENDENCY] [long-options] pkgname
Measure a package’s conformance to the Linux Standard Base (LSB)
specification. The format of the package and the contents of the
payload are checked. Warnings are produced for anything that is used,
but not contained in the LSB specification.
Print a help message and exit.
Output the program version and LSB version to standard output.
The version and LSB version are always logged to the journal
file irrespective of this option.
Do not create a journal file.
-L LANANNAME, --lanana=LANANANAME
Specify the LANANA registered package or provider name to be
used when evaluating pathnames for FHS conformance.
-t Check the LSB conformance of the executable files in the archive
payload of the package. All shared libraries present in the
package are assumed to be a part of the application, hence
lsbpkgchk does not complain about symbols in executable files
which are provided in those shared libraries.
-r VERSION, --lsb-version=VERSION
Specify the lsb version the application should be checked
-T [core,c++|core,c++,desktop], --lsb-product
Specify the lsb spec/product to load modules for- 3.0, and 3.1,
Also check the symbols found in module modulename. The default
module name is LSB-Core. Other choices are LSB-Graphics and LSB-
C++ (module names are not case-sensitive).
-j JOURNAL, --journal=JOURNAL
Write the journal file to JOURNAL instead of to the default
filename in the current directory.
-d DEPENDENCY, --dependency=DEPENDENCY
Add DEPENDENCY provided by another customer provided package to
the list of expected dependencies. Without this option a package
that has a dependency on another customer provided package will
report that it has an unexpected dependency.
A journal file is created named journal.pkgchk.pkgname where pkgname is
the package specified on the command line. It contains a record of the
test results in a format that can be submitted for LSB Certification.
You must have write access to the current working directory in order to
run lsbpkgchk successfully, or use the -j option to specify an
alternate location for the journal. The journal file can be omitted by
the use of the -n option. Journal files may be examined with the
tjreport tool, available from the LSB project as part of the lsb-
The contributors to the Linux Standard Base.
If you obtained this checker from the LSB ftp site, report bugs at
http://bugs.linuxbase.org or email to <lsb-discuss@linux-
foundation.org>. If you obtained this from your distribution, report
bugs back to the distribution in the normal way.
Should be able to specify where to write the journal file.
Linux Standard Base specification and other documents at