With all packages, there are various issues reported by lintian, regarding mostly incomplete descriptions, etc.
Also, the dependencies between the packages need to be made, checked and/or improved.
And, for various packages debuild complains about dh_pysupport :
dh_pysupport dh_pysupport: This program is deprecated, you should use dh_python2 instead. Migration guide: http://deb.li/dhs2p
Migration guide: http://deb.li/dhs2p
lamake
- No mechanism yet for installing device tree overlays. There are two python scripts in "tools", which can be used to get started on this one. These script would probably end up in a binary package, while the makefiles go to a -dev package.
- should be architecture independent, since it works with gmake.
Lintian output:
dpkg-buildpackage: full upload; Debian-native package (full source is included)
Now running lintian...
I: lamake: using-first-person-in-description line 5: I
N:
N: You should avoid the use of first person ("I will do this..." or "We
N: recommend..."). The computer is not a person and the description does
N: not speak for the maintainer or maintainers. Instead, use a more neutral
N: construction and try to rephrase into factual statements about the
N: package.
N:
N: For example, rather than saying "I don't recommend this package if you
N: are short on memory," say something like "this package is not suitable
N: for low-memory systems."
N:
N: Severity: minor, Certainty: possible
N:
N: Check: description, Type: binary, udeb
N:
I: lamake: using-first-person-in-description line 6: my
I: lamake: using-first-person-in-description line 6: we
I: lamake: using-first-person-in-description line 13: I
I: lamake: using-first-person-in-description line 16: I
W: lamake: script-not-executable usr/include/LaMake/mkshow.py
N:
N: This file starts with the #! sequence that marks interpreted scripts,
N: but it is not executable.
N:
N: Severity: normal, Certainty: certain
N:
N: Check: scripts, Type: binary
N:
W: lamake: script-not-executable usr/include/LaMake/tools/read_slots.py
W: lamake: script-not-executable usr/include/LaMake/tools/set_uenv.py
Finished running lintian.
am335x-pru-package
- convert build of package to use github source ( https://github.com/l4m4re/am335x_pru_package ) instead of tar.gz
Lintian output:
dpkg-buildpackage: full upload (original source is included) Now running lintian... W: am335x-pru-package source: diff-contains-quilt-control-dir debian/.pc N: N: The Debian diff or native package contains files in a directory used by N: quilt, which are not useful in a diff or native package. dpkg-source N: will automatically exclude these if it is passed -I or -i for native and N: non-native packages respectively. N: N: Refer to the dpkg-source(1) manual page for details. N: N: Severity: normal, Certainty: certain N: N: Check: cruft, Type: source N: W: am335x-pru-package source: changelog-should-mention-nmu N: N: When you NMU a package, that fact should be mentioned on the first line N: in the changelog entry. Use the words "NMU" or "Non-maintainer upload" N: (case insensitive). N: N: Maybe you didn't intend this upload to be a NMU, in that case, please N: doublecheck that the most recent entry in the changelog is byte-for-byte N: identical to the maintainer or one of the uploaders. If this is a local N: package (not intended for Debian), you can suppress this warning by N: putting "local" in the version number or "local package" on the first N: line of the changelog entry. N: N: Refer to Debian Developer's Reference section 5.11.3 (Using the DELAYED/ N: queue) for details. N: N: Severity: normal, Certainty: certain N: N: Check: nmu, Type: source N: W: am335x-pru-package source: source-nmu-has-incorrect-version-number 0.20160522-1~l4m4re+20160522+1 N: N: A source NMU should have a Debian revision of "-x.x" (or "+nmuX" for a N: native package). This is to prevent stealing version numbers from the N: maintainer. N: N: Maybe you didn't intend this upload to be a NMU, in that case, please N: doublecheck that the most recent entry in the changelog is byte-for-byte N: identical to the maintainer or one of the uploaders. If this is a local N: package (not intended for Debian), you can suppress this warning by N: putting "local" in the version number or "local package" on the first N: line of the changelog entry. N: N: Refer to Debian Developer's Reference section 5.11.2 (NMUs and N: debian/changelog) for details. N: N: Severity: normal, Certainty: certain N: N: Check: nmu, Type: source N: W: am335x-pru-package source: missing-license-paragraph-in-dep5-copyright bsd-3 (paragraph at line 37) N: N: The files paragraph in the machine readable copyright file references a N: license, for which no standalone license paragraph exists. N: N: Refer to N: http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ for N: details. N: N: Severity: normal, Certainty: possible N: N: Check: source-copyright, Type: source N: W: am335x-pru-package source: newer-standards-version 3.9.5 (current is 3.9.4) N: N: The source package refers to a Standards-Version which is newer than the N: highest one lintian is programmed to check. If the source package is N: correct, then please upgrade lintian to the newest version. (If there is N: no newer lintian version, then please bug lintian-maint@debian.org to N: make one.) N: N: Severity: normal, Certainty: certain N: N: Check: standards-version, Type: source N: I: am335x-pru-package source: debian-watch-file-is-missing N: N: This source package is not Debian-native but it does not have a N: debian/watch file. This file is used for automatic detection of new N: upstream versions by the Debian External Health Status project and other N: project infrastructure. If this package is maintained upstream, please N: consider adding a debian/watch file to detect new releases. N: N: If the package is not maintained upstream or if upstream uses a N: distribution mechanism that cannot be meaningfully monitored by uscan N: and the Debian External Health Status project, please consider adding a N: debian/watch file containing only comments documenting the situation. N: N: Refer to Debian Policy Manual section 4.11 (Optional upstream source N: location: debian/watch) and the uscan(1) manual page for details. N: N: Severity: wishlist, Certainty: certain N: N: Check: watch-file, Type: source N: W: am335x-pru-package: hardening-no-relro usr/bin/pasm N: N: This package provides an ELF binary that lacks the "read-only N: relocation" link flag. This package was likely not built with the N: default Debian compiler flags defined by dpkg-buildflags. If built using N: dpkg-buildflags directly, be sure to import LDFLAGS. N: N: Refer to http://wiki.debian.org/Hardening for details. N: N: Severity: normal, Certainty: certain N: N: Check: binaries, Type: binary, udeb N: W: am335x-pru-package: hardening-no-fortify-functions usr/bin/pasm N: N: This package provides an ELF binary that lacks the use of fortified libc N: functions. Either there are no potentially unfortified functions called N: by any routines, all unfortified calls have already been fully validated N: at compile-time, or the package was not built with the default Debian N: compiler flags defined by dpkg-buildflags. If built using N: dpkg-buildflags directly, be sure to import CPPFLAGS. N: N: NB: Due to false-positives, Lintian ignores some unprotected functions N: (e.g. memcpy). N: N: Refer to http://wiki.debian.org/Hardening and N: http://bugs.debian.org/673112 for details. N: N: Severity: normal, Certainty: possible N: N: Check: binaries, Type: binary, udeb N: W: am335x-pru-package: hardening-no-relro usr/lib/libprussdrv.so W: am335x-pru-package: hardening-no-fortify-functions usr/lib/libprussdrv.so W: am335x-pru-package: hardening-no-relro usr/lib/libprussdrvd.so W: am335x-pru-package: hardening-no-fortify-functions usr/lib/libprussdrvd.so E: am335x-pru-package: description-synopsis-is-duplicated N: N: The first line of the extended Description: should not repeat the N: synopsis exactly. This indicates that either the synopsis is badly N: formed or that the extended description has been wrongly copied and N: pasted. N: N: Refer to Debian Policy Manual section 3.4.2 (The extended description) N: for details. N: N: Severity: important, Certainty: certain N: N: Check: description, Type: binary, udeb N: I: am335x-pru-package: extended-description-is-probably-too-short N: N: The extended description (the lines after the first line of the N: "Description:" field) is only one or two lines long. The extended N: description should provide a user with enough information to decide N: whether they want to install this package, what it contains, and how it N: compares to similar packages. One or two lines is normally not enough to N: do this. N: N: Refer to Debian Developer's Reference section 6.2.1 (General guidelines N: for package descriptions) and Debian Developer's Reference section 6.2.3 N: (The long description) for details. N: N: Severity: minor, Certainty: possible N: N: Check: description, Type: binary, udeb N: E: am335x-pru-package: sharedobject-in-library-directory-missing-soname usr/lib/libprussdrv.so N: N: A shared object was identified in a library directory (a directory in N: the standard linker path) which doesn't have a SONAME. This is usually N: an error. N: N: SONAMEs are set with something like gcc -Wl,-soname,libfoo.so.0, where 0 N: is the major version of the library. If your package uses libtool, then N: libtool invoked with the right options should be doing this. N: N: To view the SONAME of a shared library, run readelf -d on the shared N: library and look for the tag of type SONAME. N: N: Severity: important, Certainty: possible N: N: Check: shared-libs, Type: binary, udeb N: E: am335x-pru-package: sharedobject-in-library-directory-missing-soname usr/lib/libprussdrvd.so Finished running lintian.
freebasic
- built from .tar.gz source. Could perhaps use git repository.
- should probably build a binary (runtime lib) package (libfreebasic?) and a -dev package.
- it seems there are some libs included with freebasic, like gfxlib2 and rtlib, which should probably be moved to separate debian packages. That does not necessarily mean they need to be completely separated from freebasic, but they could.
- dpkg-shlibdeps: warning: package could avoid a useless dependency if debian/freebasic/usr/bin/fbc was not linked against libdl.so.2 (it uses none of the library's symbols)
Lintian output:
dpkg-buildpackage: full upload (original source is included)
Now running lintian...
E: freebasic source: build-depends-on-build-essential build-depends
N:
N: You depend on the build-essential package, which is only a metapackage
N: depending on build tools that have to be installed in all build
N: environments.
N:
N: Refer to Debian Policy Manual section 7.7 (Relationships between source
N: and binary packages - Build-Depends, Build-Depends-Indep,
N: Build-Conflicts, Build-Conflicts-Indep) for details.
N:
N: Severity: important, Certainty: certain
N:
N: Check: fields, Type: binary, udeb, source
N:
I: freebasic source: debian-watch-file-is-missing
N:
N: This source package is not Debian-native but it does not have a
N: debian/watch file. This file is used for automatic detection of new
N: upstream versions by the Debian External Health Status project and other
N: project infrastructure. If this package is maintained upstream, please
N: consider adding a debian/watch file to detect new releases.
N:
N: If the package is not maintained upstream or if upstream uses a
N: distribution mechanism that cannot be meaningfully monitored by uscan
N: and the Debian External Health Status project, please consider adding a
N: debian/watch file containing only comments documenting the situation.
N:
N: Refer to Debian Policy Manual section 4.11 (Optional upstream source
N: location: debian/watch) and the uscan(1) manual page for details.
N:
N: Severity: wishlist, Certainty: certain
N:
N: Check: watch-file, Type: source
N:
I: freebasic: spelling-error-in-binary usr/bin/fbc Ambigious Ambiguous
N:
N: Lintian found a spelling error in the given binary. Lintian has a list
N: of common misspellings that it looks for. It does not have a dictionary
N: like a spelling checker does.
N:
N: If the string containing the spelling error is translated with the help
N: of gettext or a similar tool, please fix the error in the translations
N: as well as the English text to avoid making the translations fuzzy. With
N: gettext, for example, this means you should also fix the spelling
N: mistake in the corresponding msgids in the *.po files.
N:
N: You can often find the word in the source code by running:
N:
N: grep -rw <word> <source-tree>
N:
N: This tag may produce false positives for words that contain non-ASCII
N: characters due to limitations in strings.
N:
N: Severity: minor, Certainty: wild-guess
N:
N: Check: binaries, Type: binary, udeb
N:
W: freebasic: hardening-no-relro usr/bin/fbc
N:
N: This package provides an ELF binary that lacks the "read-only
N: relocation" link flag. This package was likely not built with the
N: default Debian compiler flags defined by dpkg-buildflags. If built using
N: dpkg-buildflags directly, be sure to import LDFLAGS.
N:
N: Refer to http://wiki.debian.org/Hardening for details.
N:
N: Severity: normal, Certainty: certain
N:
N: Check: binaries, Type: binary, udeb
N:
W: freebasic: hardening-no-fortify-functions usr/bin/fbc
N:
N: This package provides an ELF binary that lacks the use of fortified libc
N: functions. Either there are no potentially unfortified functions called
N: by any routines, all unfortified calls have already been fully validated
N: at compile-time, or the package was not built with the default Debian
N: compiler flags defined by dpkg-buildflags. If built using
N: dpkg-buildflags directly, be sure to import CPPFLAGS.
N:
N: NB: Due to false-positives, Lintian ignores some unprotected functions
N: (e.g. memcpy).
N:
N: Refer to http://wiki.debian.org/Hardening and
N: http://bugs.debian.org/673112 for details.
N:
N: Severity: normal, Certainty: possible
N:
N: Check: binaries, Type: binary, udeb
N:
W: freebasic: new-package-should-close-itp-bug
N:
N: This package appears to be the first packaging of a new upstream
N: software package (there is only one changelog entry and the Debian
N: revision is 1), but it does not close any bugs. The initial upload of a
N: new package should close the corresponding ITP bug for that package.
N:
N: This warning can be ignored if the package is not intended for Debian or
N: if it is a split of an existing Debian package.
N:
N: Refer to Debian Developer's Reference section 5.1 (New packages) for
N: details.
N:
N: Severity: normal, Certainty: certain
N:
N: Check: changelog-file, Type: binary
N:
W: freebasic: duplicate-changelog-files usr/share/doc/freebasic/changelog.gz usr/share/doc/freebasic/changelog.txt.gz
N:
N: The package appears to be shipping two copies of the changelog.
N:
N: If the second copy is really needed, consider making it a symlink to the
N: canonical place for the relevant changelog.
N:
N: Both upstream and debian changelogs are checked with this tag.
N:
N: Severity: normal, Certainty: possible
N:
N: Check: duplicate-files, Type: binary
N:
W: freebasic: manpage-has-errors-from-man usr/share/man/man1/fbc.1.gz 10: warning: macro `F' not defined
N:
N: This man page provokes warnings or errors from man.
N:
N: "cannot adjust" or "can't break" are trouble with paragraph filling,
N: usually related to long lines. Adjustment can be helped by left
N: justifying, breaks can be helped with hyphenation, see "Manipulating
N: Filling and Adjusting" and "Manipulating Hyphenation" in the manual.
N:
N: "can't find numbered character" usually means latin1 etc in the input,
N: and this warning indicates characters will be missing from the output.
N: You can change to escapes like \[:a] described on the groff_char man
N: page.
N:
N: Other warnings are often formatting typos, like missing quotes around a
N: string argument to .IP. These are likely to result in lost or malformed
N: output. See the groff_man (or groff_mdoc if using mdoc) man page for
N: information on macros.
N:
N: This test uses man's --warnings option to enable groff warnings that
N: catch common mistakes, such as putting . or ' characters at the start of
N: a line when they are intended as literal text rather than groff
N: commands. This can be fixed either by reformatting the paragraph so that
N: these characters are not at the start of a line, or by adding a
N: zero-width space (\&) immediately before them.
N:
N: At worst, warning messages can be disabled with the .warn directive, see
N: "Debugging" in the groff manual.
N:
N: To test this for yourself you can use the following command:
N: LC_ALL=en_US.UTF-8 MANWIDTH=80 man --warnings -E UTF-8 -l <file> >/dev/null
N:
N: Severity: normal, Certainty: certain
N:
N: Check: manpages, Type: binary
N:
I: freebasic: hyphen-used-as-minus-sign usr/share/man/man1/fbc.1.gz:88
N:
N: This manual page seems to contain a hyphen where a minus sign was
N: intended. By default, "-" chars are interpreted as hyphens (U+2010) by
N: groff, not as minus signs (U+002D). Since options to programs use minus
N: signs (U+002D), this means for example in UTF-8 locales that you cannot
N: cut and paste options, nor search for them easily. The Debian groff
N: package currently forces "-" to be interpreted as a minus sign due to
N: the number of manual pages with this problem, but this is a
N: Debian-specific modification and hopefully eventually can be removed.
N:
N: "-" must be escaped ("\-") to be interpreted as minus. If you really
N: intend a hyphen (normally you don't), write it as "\(hy" to emphasise
N: that fact. See groff(7) and especially groff_char(7) for details, and
N: also the thread starting with
N: http://lists.debian.org/debian-devel/2003/debian-devel-200303/msg01481.h
N: tml
N:
N: If you use some tool that converts your documentation to groff format,
N: this tag may indicate a bug in the tool. Some tools convert dashes of
N: any kind to hyphens. The safe way of converting dashes is to convert
N: them to "\-".
N:
N: Because this error can occur very often, Lintian shows only the first 10
N: occurrences for each man page and give the number of suppressed
N: occurrences. If you want to see all warnings, run Lintian with the
N: -d/--debug option.
N:
N: Refer to /usr/share/doc/groff-base/README.Debian and the groff_char(7)
N: manual page for details.
N:
N: Severity: wishlist, Certainty: possible
N:
N: Check: manpages, Type: binary
N:
I: freebasic: hyphen-used-as-minus-sign usr/share/man/man1/fbc.1.gz:133
I: freebasic: hyphen-used-as-minus-sign usr/share/man/man1/fbc.1.gz:175
I: freebasic: hyphen-used-as-minus-sign usr/share/man/man1/fbc.1.gz:192
Finished running lintian.
fb-doc
- dpkg-shlibdeps: warning: package could avoid a useless dependency if debian/fb-doc/usr/bin/fb-doc was not linked against libm.so.6 (it uses none of the library's symbols)
Lintian output:
Now running lintian... W: fb-doc: hardening-no-relro usr/bin/fb-doc N: N: This package provides an ELF binary that lacks the "read-only N: relocation" link flag. This package was likely not built with the N: default Debian compiler flags defined by dpkg-buildflags. If built using N: dpkg-buildflags directly, be sure to import LDFLAGS. N: N: Refer to http://wiki.debian.org/Hardening for details. N: N: Severity: normal, Certainty: certain N: N: Check: binaries, Type: binary, udeb N: W: fb-doc: hardening-no-fortify-functions usr/bin/fb-doc N: N: This package provides an ELF binary that lacks the use of fortified libc N: functions. Either there are no potentially unfortified functions called N: by any routines, all unfortified calls have already been fully validated N: at compile-time, or the package was not built with the default Debian N: compiler flags defined by dpkg-buildflags. If built using N: dpkg-buildflags directly, be sure to import CPPFLAGS. N: N: NB: Due to false-positives, Lintian ignores some unprotected functions N: (e.g. memcpy). N: N: Refer to http://wiki.debian.org/Hardening and N: http://bugs.debian.org/673112 for details. N: N: Severity: normal, Certainty: possible N: N: Check: binaries, Type: binary, udeb N: E: fb-doc: helper-templates-in-copyright N: N: The /usr/share/doc/<pkg>/copyright file still contains template markers N: from a packaging helper. Please fill in the actual license, upstream N: copyright holders, and download information about the package and remove N: any remaining templates generated by the packaging helper. N: N: Severity: important, Certainty: certain N: N: Check: copyright-file, Type: binary N: W: fb-doc: copyright-has-url-from-dh_make-boilerplate N: N: There is "url://example.com" in your copyright file. This was most N: likely a remnant from the dh_make template. N: N: Make sure you include the real location where you obtained the upstream N: sources (if any). N: N: Refer to Debian Policy Manual section 12.5 (Copyright information) for N: details. N: N: Severity: normal, Certainty: certain N: N: Check: copyright-file, Type: binary N: E: fb-doc: copyright-contains-dh_make-todo-boilerplate N: N: The string "Please also look if..." appears in the copyright file, which N: indicates that you either didn't check the whole source to find N: additional copyright/license, or that you didn't remove that paragraph N: after having done so. N: N: Refer to Debian Policy Manual section 12.5 (Copyright information) for N: details. N: N: Severity: serious, Certainty: possible N: N: Check: copyright-file, Type: binary N: W: fb-doc: readme-debian-contains-debmake-template N: N: The README.Debian file installed by this package contains one of the N: template phrases from the README.Debian provided by deb-make or dh_make: N: N: Comments regarding the package N: So far nothing to say N: <possible notes regarding this package - if none, delete this file> N: N: If there is real information in the file, please delete any generic N: template phrases. If there is nothing to say in the file, it is best N: removed. N: N: Severity: normal, Certainty: certain N: N: Check: debian-readme, Type: binary N: W: fb-doc: documentation-package-not-architecture-independent N: N: Documentation packages usually shouldn't carry anything that requires N: recompiling on various architectures, in order to save space on mirrors. N: N: Severity: normal, Certainty: certain N: N: Check: fields, Type: binary, udeb, source N: W: fb-doc: unknown-section dev N: N: The "Section:" field in this package's control file is not one of the N: sections in use on the ftp archive. Valid sections are currently admin, N: comm, cli-mono, database, debug, devel, doc, editors, electronics, N: embedded, fonts, games, gnome, gnu-r, gnustep, graphics, hamradio, N: haskell, httpd, interpreters, java, kde, libdevel, libs, lisp, N: localization, kernel, mail, math, misc, net, news, ocaml, oldlibs, N: otherosfs, perl, php, python, ruby, science, shells, sound, tex, text, N: utils, vcs, video, web, x11, xfce, zope. N: N: The section name should be preceded by "non-free/" if the package is in N: the non-free archive area, and by "contrib/" if the package is in the N: contrib archive area. N: N: Refer to Debian Policy Manual section 2.4 (Sections) for details. N: N: Severity: normal, Certainty: certain N: N: Check: fields, Type: binary, udeb, source N: W: fb-doc: wrong-section-according-to-package-name fb-doc => doc N: N: This package has a name suggesting that it belongs to a section other N: than the one it is currently categorized in. N: N: Severity: normal, Certainty: possible N: N: Check: fields, Type: binary, udeb, source N: W: fb-doc: binary-without-manpage usr/bin/fb-doc N: N: Each binary in /usr/bin, /usr/sbin, /bin, /sbin or /usr/games should N: have a manual page N: N: Note that though the man program has the capability to check for several N: program names in the NAMES section, each of these programs should have N: its own manual page (a symbolic link to the appropriate manual page is N: sufficient) because other manual page viewers such as xman or tkman N: don't support this. N: N: If the name of the man page differs from the binary by case, man may be N: able to find it anyway; however, it is still best practice to make the N: case of the man page match the case of the binary. N: N: If the man pages are provided by another package on which this package N: depends, lintian may not be able to determine that man pages are N: available. In this case, after confirming that all binaries do have man N: pages after this package and its dependencies are installed, please add N: a lintian override. N: N: Refer to Debian Policy Manual section 12.1 (Manual pages) for details. N: N: Severity: normal, Certainty: possible N: N: Check: manpages, Type: binary N: Finished running lintian.
fb-prussdrv
Currently built using LaMake
- overlay files not installed in the sense that they are not loaded.
Lintian output:
dpkg-genchanges: warning: the current version (0.20160708-1~l4m4re) is earlier than the previous one (1~l4m4re) dpkg-genchanges: including full source code in upload dpkg-source -I -i --after-build fb_prussdrv_l4mr4e_github dpkg-buildpackage: full upload; Debian-native package (full source is included) Now running lintian... W: fb-prussdrv source: native-package-with-dash-version N: N: Native packaging should only be used if a piece of software was written N: specifically to be turned into a Debian package. In this case, the N: version number should not contain a Debian revision part. N: N: Native source packages are sometimes created by accident. In most cases N: the reason is the location of the original source tarball. For version N: 1.0 source packages, dpkg-source determines whether they're non-native N: by looking for a file named <package>_<upversion>.orig.tar.gz in the N: parent directory, where <upversion> is the upstream version from the N: most recent debian/changelog entry. For version 3.0 packages, check N: debian/source/format for an erroneous "(native)" package format. N: N: Severity: normal, Certainty: certain N: N: Check: cruft, Type: source N: W: fb-prussdrv source: superfluous-clutter-in-homepage <insert the upstream URL, if relevant> N: N: The "Homepage:" field in this package's control file contains N: superfluous markup around the URL, like enclosing < and >. This is N: unnecessary and needlessly complicates using this information. N: N: Refer to Debian Policy Manual section 5.6.23 (Homepage) for details. N: N: Severity: normal, Certainty: certain N: N: Check: fields, Type: binary, udeb, source N: W: fb-prussdrv source: bad-homepage <insert the upstream URL, if relevant> N: N: The "Homepage:" field in this package's control file does not contain a N: valid absolute URL. Most probably you forgot to specify the scheme (e.g. N: http). N: N: This tag is also triggered if the scheme is not known by Lintian. N: N: Please file a bug against Lintian, if this tag is triggered for a valid N: homepage URL. N: N: Severity: normal, Certainty: certain N: N: Check: fields, Type: binary, udeb, source N: W: fb-prussdrv: latest-debian-changelog-entry-without-new-version N: N: The latest Debian changelog entry has a version number that's either the N: same or smaller than the version number of the entry before. N: N: Severity: normal, Certainty: certain N: N: Check: changelog-file, Type: binary N: E: fb-prussdrv: helper-templates-in-copyright N: N: The /usr/share/doc/<pkg>/copyright file still contains template markers N: from a packaging helper. Please fill in the actual license, upstream N: copyright holders, and download information about the package and remove N: any remaining templates generated by the packaging helper. N: N: Severity: important, Certainty: certain N: N: Check: copyright-file, Type: binary N: W: fb-prussdrv: copyright-has-url-from-dh_make-boilerplate N: N: There is "url://example.com" in your copyright file. This was most N: likely a remnant from the dh_make template. N: N: Make sure you include the real location where you obtained the upstream N: sources (if any). N: N: Refer to Debian Policy Manual section 12.5 (Copyright information) for N: details. N: N: Severity: normal, Certainty: certain N: N: Check: copyright-file, Type: binary N: E: fb-prussdrv: copyright-contains-dh_make-todo-boilerplate N: N: The string "Please also look if..." appears in the copyright file, which N: indicates that you either didn't check the whole source to find N: additional copyright/license, or that you didn't remove that paragraph N: after having done so. N: N: Refer to Debian Policy Manual section 12.5 (Copyright information) for N: details. N: N: Severity: serious, Certainty: possible N: N: Check: copyright-file, Type: binary N: E: fb-prussdrv: description-is-dh_make-template N: N: The synopsis or the extended description has not been changed from the N: template provided by dh_make. N: N: Severity: serious, Certainty: certain N: N: Check: description, Type: binary, udeb N: I: fb-prussdrv: extended-description-is-probably-too-short N: N: The extended description (the lines after the first line of the N: "Description:" field) is only one or two lines long. The extended N: description should provide a user with enough information to decide N: whether they want to install this package, what it contains, and how it N: compares to similar packages. One or two lines is normally not enough to N: do this. N: N: Refer to Debian Developer's Reference section 6.2.1 (General guidelines N: for package descriptions) and Debian Developer's Reference section 6.2.3 N: (The long description) for details. N: N: Severity: minor, Certainty: possible N: N: Check: description, Type: binary, udeb N: W: fb-prussdrv: unknown-section dev N: N: The "Section:" field in this package's control file is not one of the N: sections in use on the ftp archive. Valid sections are currently admin, N: comm, cli-mono, database, debug, devel, doc, editors, electronics, N: embedded, fonts, games, gnome, gnu-r, gnustep, graphics, hamradio, N: haskell, httpd, interpreters, java, kde, libdevel, libs, lisp, N: localization, kernel, mail, math, misc, net, news, ocaml, oldlibs, N: otherosfs, perl, php, python, ruby, science, shells, sound, tex, text, N: utils, vcs, video, web, x11, xfce, zope. N: N: The section name should be preceded by "non-free/" if the package is in N: the non-free archive area, and by "contrib/" if the package is in the N: contrib archive area. N: N: Refer to Debian Policy Manual section 2.4 (Sections) for details. N: N: Severity: normal, Certainty: certain N: N: Check: fields, Type: binary, udeb, source N: W: fb-prussdrv: superfluous-clutter-in-homepage <insert the upstream URL, if relevant> W: fb-prussdrv: bad-homepage <insert the upstream URL, if relevant> W: fb-prussdrv: executable-not-elf-or-script lib/firmware/PRUSSDRV-00A0.dtbo N: N: This executable file is not an ELF format binary, and does not start N: with the #! sequence that marks interpreted scripts. It might be a sh N: script that fails to name /bin/sh as its shell, or it may be incorrectly N: marked as executable. Sometimes upstream files developed on Windows are N: marked unnecessarily as executable on other systems. N: N: If you are using debhelper to build your package, running dh_fixperms N: will often correct this problem for you. N: N: Refer to Debian Policy Manual section 10.4 (Scripts) for details. N: N: Severity: normal, Certainty: certain N: N: Check: scripts, Type: binary N: Finished running lintian.
libpruio
- Empty binary package. Should contain the .so library, which is now included in the -dev package.
- The html documentation is not included in any package. Probably make a separate -doc package.
Lintian output:
dpkg-gencontrol: warning: Depends field of package libpruio: unknown substitution variable ${shlibs:Depends}
dh_md5sums
dh_builddeb
dpkg-deb: building package `libpruio-dev' in `../libpruio-dev_0.4_armhf.deb'.
dpkg-deb: building package `libpruio' in `../libpruio_0.4_armhf.deb'.
dpkg-genchanges >../libpruio_0.4_armhf.changes
dpkg-genchanges: including full source code in upload
dpkg-source -I -i --after-build libpruio-0.4
dpkg-buildpackage: full upload; Debian-native package (full source is included)
Now running lintian...
I: libpruio source: binary-control-field-duplicates-source field "section" in package libpruio
N:
N: In debian/control, this field for a binary package duplicates the value
N: inherited from the source package paragraph. This doesn't hurt anything,
N: but you may want to take advantage of the inheritance and set the value
N: in only one place. It prevents missing duplicate places that need to be
N: fixed if the value ever changes.
N:
N: Severity: wishlist, Certainty: certain
N:
N: Check: control-file, Type: source
N:
I: libpruio source: duplicate-short-description libpruio libpruio-dev
N:
N: The listed binary packages all share the same short description (the
N: first line of the Description control field). The package names may
N: provide enough additional information to distinguish between the
N: packages, but it's common to also add a word or two to the short
N: description to clarify the difference.
N:
N: Severity: wishlist, Certainty: possible
N:
N: Check: control-file, Type: source
N:
I: libpruio source: duplicate-long-description libpruio libpruio-dev
N:
N: The listed binary packages all share the same extended description. Some
N: additional information in the extended description explaining what is in
N: each package and how it differs from the other packages is useful,
N: particularly for users who aren't familiar with Debian's package naming
N: conventions.
N:
N: Severity: wishlist, Certainty: certain
N:
N: Check: control-file, Type: source
N:
W: libpruio source: debhelper-but-no-misc-depends libpruio-dev
N:
N: The source package uses debhelper, but it does not include
N: ${misc:Depends} in the given binary package's debian/control entry. Any
N: debhelper command may add dependencies to ${misc:Depends} that are
N: required for the work that it does, so recommended best practice is to
N: always add ${misc:Depends} to the dependencies of each binary package if
N: debhelper is in use.
N:
N: Refer to the debhelper(7) manual page for details.
N:
N: Severity: normal, Certainty: possible
N:
N: Check: debhelper, Type: source
N:
W: libpruio source: maintainer-script-lacks-debhelper-token debian/postinst
N:
N: This package is built using debhelper commands that may modify
N: maintainer scripts, but the maintainer scripts do not contain the
N: "#DEBHELPER#" token debhelper uses to modify them.
N:
N: Adding the token to the scripts is recommended.
N:
N: Severity: normal, Certainty: possible
N:
N: Check: debhelper, Type: source
N:
W: libpruio source: maintainer-script-lacks-debhelper-token debian/postrm
W: libpruio source: superfluous-clutter-in-homepage <insert the upstream URL, if relevant>
N:
N: The "Homepage:" field in this package's control file contains
N: superfluous markup around the URL, like enclosing < and >. This is
N: unnecessary and needlessly complicates using this information.
N:
N: Refer to Debian Policy Manual section 5.6.23 (Homepage) for details.
N:
N: Severity: normal, Certainty: certain
N:
N: Check: fields, Type: binary, udeb, source
N:
W: libpruio source: bad-homepage <insert the upstream URL, if relevant>
N:
N: The "Homepage:" field in this package's control file does not contain a
N: valid absolute URL. Most probably you forgot to specify the scheme (e.g.
N: http).
N:
N: This tag is also triggered if the scheme is not known by Lintian.
N:
N: Please file a bug against Lintian, if this tag is triggered for a valid
N: homepage URL.
N:
N: Severity: normal, Certainty: certain
N:
N: Check: fields, Type: binary, udeb, source
N:
W: libpruio-dev: latest-debian-changelog-entry-without-new-version
N:
N: The latest Debian changelog entry has a version number that's either the
N: same or smaller than the version number of the entry before.
N:
N: Severity: normal, Certainty: certain
N:
N: Check: changelog-file, Type: binary
N:
E: libpruio-dev: description-is-dh_make-template
N:
N: The synopsis or the extended description has not been changed from the
N: template provided by dh_make.
N:
N: Severity: serious, Certainty: certain
N:
N: Check: description, Type: binary, udeb
N:
I: libpruio-dev: extended-description-is-probably-too-short
N:
N: The extended description (the lines after the first line of the
N: "Description:" field) is only one or two lines long. The extended
N: description should provide a user with enough information to decide
N: whether they want to install this package, what it contains, and how it
N: compares to similar packages. One or two lines is normally not enough to
N: do this.
N:
N: Refer to Debian Developer's Reference section 6.2.1 (General guidelines
N: for package descriptions) and Debian Developer's Reference section 6.2.3
N: (The long description) for details.
N:
N: Severity: minor, Certainty: possible
N:
N: Check: description, Type: binary, udeb
N:
W: libpruio-dev: superfluous-clutter-in-homepage <insert the upstream URL, if relevant>
W: libpruio-dev: bad-homepage <insert the upstream URL, if relevant>
W: libpruio-dev: postinst-has-useless-call-to-ldconfig
N:
N: The postinst script calls ldconfig even though no shared libraries are
N: installed in a directory controlled by the dynamic library loader.
N:
N: Note this may be triggered by a bug in debhelper, that causes it to
N: auto-generate an ldconfig snippet for packages that does not need it.
N:
N: Refer to Debian Policy Manual section 8.1.1 (ldconfig) and
N: http://bugs.debian.org/204975 for details.
N:
N: Severity: minor, Certainty: certain
N:
N: Check: shared-libs, Type: binary, udeb
N:
W: libpruio-dev: postrm-has-useless-call-to-ldconfig
N:
N: The postrm script calls ldconfig even though no shared libraries are
N: installed in a directory controlled by the dynamic library loader.
N:
N: Note this may be triggered by a bug in debhelper, that causes it to
N: auto-generate an ldconfig snippet for packages that does not need it.
N:
N: Refer to Debian Policy Manual section 8.1.1 (ldconfig) and
N: http://bugs.debian.org/204975 for details.
N:
N: Severity: minor, Certainty: certain
N:
N: Check: shared-libs, Type: binary, udeb
N:
W: libpruio: latest-debian-changelog-entry-without-new-version
E: libpruio: description-is-dh_make-template
I: libpruio: extended-description-is-probably-too-short
W: libpruio: superfluous-clutter-in-homepage <insert the upstream URL, if relevant>
W: libpruio: bad-homepage <insert the upstream URL, if relevant>
W: libpruio: empty-binary-package
N:
N: This binary package appears to be empty, and its description does not
N: say that it's a metapackage or a transitional package. This is often due
N: to problems with updating debhelper *.install files during package
N: renames or similar problems where installation rules don't put files in
N: the correct place.
N:
N: If the package is deliberately empty, please mention in the package long
N: description one of the phrases "metapackage," "dummy," "dependency
N: package," "empty package," or "virtual package."
N:
N: Severity: important, Certainty: wild-guess
N:
N: Check: files, Type: binary, udeb
N:
Finished running lintian.
cmakefbc
- dpkg-shlibdeps: warning: package could avoid a useless dependency if debian/cmakefbc/usr/bin/cmake_fb_deps was not linked against libdl.so.2 (it uses none of the library's symbols)
- dpkg-shlibdeps: warning: package could avoid a useless dependency if debian/cmakefbc/usr/bin/cmake_fb_deps was not linked against libm.so.6 (it uses none of the library's symbols)
- cmake_fb_deps does not seem to check dependencies in /usr/include/freebasic{/BBB} nor /usr/local/include/freebasic{/BBB}. An example from configuring libpruio:
cmake_fb_deps: skipping BBB/pruss_intc_mapping.bi (open failed in
/data/arend/debian/libpruio/libpruio-0.4/src/pruio/pruio.bi)
While the include files are actually there:
arend@beaglebone:~/debian$ cd /usr/include/freebasic/BBB/ arend@beaglebone:/usr/include/freebasic/BBB$ ls prussdrv.bi pruss_intc_mapping.bi arend@beaglebone:/usr/include/freebasic/BBB$ cd /usr/local/include/freebasic/BBB/ arend@beaglebone:/usr/local/include/freebasic/BBB$ ls prussdrv.bi pruss_intc_mapping.bi arend@beaglebone:/usr/local/include/freebasic/BBB$
Lintian output:
dpkg-buildpackage: full upload; Debian-native package (full source is included) Now running lintian... W: cmakefbc: hardening-no-fortify-functions usr/bin/cmake_fb_deps N: N: This package provides an ELF binary that lacks the use of fortified libc N: functions. Either there are no potentially unfortified functions called N: by any routines, all unfortified calls have already been fully validated N: at compile-time, or the package was not built with the default Debian N: compiler flags defined by dpkg-buildflags. If built using N: dpkg-buildflags directly, be sure to import CPPFLAGS. N: N: NB: Due to false-positives, Lintian ignores some unprotected functions N: (e.g. memcpy). N: N: Refer to http://wiki.debian.org/Hardening and N: http://bugs.debian.org/673112 for details. N: N: Severity: normal, Certainty: possible N: N: Check: binaries, Type: binary, udeb N: W: cmakefbc: latest-debian-changelog-entry-without-new-version N: N: The latest Debian changelog entry has a version number that's either the N: same or smaller than the version number of the entry before. N: N: Severity: normal, Certainty: certain N: N: Check: changelog-file, Type: binary N: E: cmakefbc: helper-templates-in-copyright N: N: The /usr/share/doc/<pkg>/copyright file still contains template markers N: from a packaging helper. Please fill in the actual license, upstream N: copyright holders, and download information about the package and remove N: any remaining templates generated by the packaging helper. N: N: Severity: important, Certainty: certain N: N: Check: copyright-file, Type: binary N: W: cmakefbc: copyright-has-url-from-dh_make-boilerplate N: N: There is "url://example.com" in your copyright file. This was most N: likely a remnant from the dh_make template. N: N: Make sure you include the real location where you obtained the upstream N: sources (if any). N: N: Refer to Debian Policy Manual section 12.5 (Copyright information) for N: details. N: N: Severity: normal, Certainty: certain N: N: Check: copyright-file, Type: binary N: E: cmakefbc: copyright-contains-dh_make-todo-boilerplate N: N: The string "Please also look if..." appears in the copyright file, which N: indicates that you either didn't check the whole source to find N: additional copyright/license, or that you didn't remove that paragraph N: after having done so. N: N: Refer to Debian Policy Manual section 12.5 (Copyright information) for N: details. N: N: Severity: serious, Certainty: possible N: N: Check: copyright-file, Type: binary N: W: cmakefbc: readme-debian-contains-debmake-template N: N: The README.Debian file installed by this package contains one of the N: template phrases from the README.Debian provided by deb-make or dh_make: N: N: Comments regarding the package N: So far nothing to say N: <possible notes regarding this package - if none, delete this file> N: N: If there is real information in the file, please delete any generic N: template phrases. If there is nothing to say in the file, it is best N: removed. N: N: Severity: normal, Certainty: certain N: N: Check: debian-readme, Type: binary N: I: cmakefbc: description-synopsis-might-not-be-phrased-properly N: N: The synopsis (first line in the package "Description:" field, the short N: description) ends with a full stop "." character. This is not necessary, N: as the synopsis doesn't need to be a full sentence. It is recommended N: that a descriptive phrase is used instead. N: N: Note also that the synopsis is not part of the rest of the N: "Description:" field. N: N: Refer to Debian Developer's Reference section 6.2.2 (The package N: synopsis, or short description) for details. N: N: Severity: minor, Certainty: possible N: N: Check: description, Type: binary, udeb N: E: cmakefbc: section-is-dh_make-template N: N: The "Section:" field in this package's control file is set to unknown. N: This is not a valid section, and usually means a dh_make template N: control file was used and never modified to set the correct section. N: N: Refer to Debian Policy Manual section 2.4 (Sections) for details. N: N: Severity: serious, Certainty: certain N: N: Check: fields, Type: binary, udeb, source N: W: cmakefbc: binary-without-manpage usr/bin/cmake_fb_deps N: N: Each binary in /usr/bin, /usr/sbin, /bin, /sbin or /usr/games should N: have a manual page N: N: Note that though the man program has the capability to check for several N: program names in the NAMES section, each of these programs should have N: its own manual page (a symbolic link to the appropriate manual page is N: sufficient) because other manual page viewers such as xman or tkman N: don't support this. N: N: If the name of the man page differs from the binary by case, man may be N: able to find it anyway; however, it is still best practice to make the N: case of the man page match the case of the binary. N: N: If the man pages are provided by another package on which this package N: depends, lintian may not be able to determine that man pages are N: available. In this case, after confirming that all binaries do have man N: pages after this package and its dependencies are installed, please add N: a lintian override. N: N: Refer to Debian Policy Manual section 12.1 (Manual pages) for details. N: N: Severity: normal, Certainty: possible N: N: Check: manpages, Type: binary N: Finished running lintian.