Skip to content

Instantly share code, notes, and snippets.

@AltGr
Created February 4, 2013 11:32
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save AltGr/4706236 to your computer and use it in GitHub Desktop.
Save AltGr/4706236 to your computer and use it in GitHub Desktop.
opam lintian warnings
W: opam: hardening-no-relro usr/bin/opam
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: opam: hardening-no-fortify-functions usr/bin/opam
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: opam: hardening-no-relro usr/bin/opam-check
W: opam: hardening-no-fortify-functions usr/bin/opam-check
W: opam: hardening-no-relro usr/bin/opam-mk-repo
W: opam: hardening-no-fortify-functions usr/bin/opam-mk-repo
W: opam: hardening-no-relro usr/bin/opam-repo-check
W: opam: hardening-no-fortify-functions usr/bin/opam-repo-check
W: opam: possible-unindented-list-in-extended-description
N:
N: The package "Description:" contains an unindented line which starts with
N: a dash (-) or asterisk (*). If this was meant to be a list of items
N: these lines need to be indented (dselect would word-wrap these lines
N: otherwise).
N:
N: Refer to Debian Policy Manual section 5.6.13 (Description) for details.
N:
N: Severity: normal, Certainty: possible
N:
N: Check: description, Type: binary, udeb
N:
W: opam: duplicate-changelog-files usr/share/doc/opam/CHANGES.gz usr/share/doc/opam/changelog.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: opam: binary-without-manpage usr/bin/opam-check
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:
W: opam: binary-without-manpage usr/bin/opam-mk-repo
W: opam: binary-without-manpage usr/bin/opam-repo-check
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment