When running lintian on one of the provided integration packages it gives back quite some errors and warnings. Most of them are easy to fix. Please look into this, thanks in advance.
$ lintian -i opsgenie-icinga_2.19.2_all.deb
E: opsgenie-icinga: arch-independent-package-contains-binary-or-object usr/bin/icinga2opsgenie
N:
N: The package contains a binary or object file but is tagged Architecture:
N: all.
N:
N: If this package contains binaries or objects for cross-compiling or
N: binary blobs for other purposes independent of the host architecture
N: (such as BIOS updates or firmware), please add a Lintian override.
N:
N: Severity: serious, Certainty: possible
N:
N: Check: binaries, Type: binary, udeb
N:
E: opsgenie-icinga: unstripped-binary-or-object usr/bin/icinga2opsgenie
N:
N: The package installs an unstripped binary or object file.
N:
N: Please note, that shared libraries have to be stripped with the
N: --strip-unneeded option.
N:
N: Refer to Debian Policy Manual section 10.1 (Binaries) and Debian Policy
N: Manual section 10.2 (Libraries) for details.
N:
N: Severity: important, Certainty: certain
N:
N: Check: binaries, Type: binary, udeb
N:
E: opsgenie-icinga: statically-linked-binary usr/bin/icinga2opsgenie
N:
N: The package installs a statically linked binary or object file.
N:
N: Usually this is a bug. Otherwise, please add an override if your package
N: is an exception. Binaries named *-static and *.static are automatically
N: excluded, as are any binaries in packages named *-static.
N:
N: Severity: important, Certainty: possible
N:
N: Check: binaries, Type: binary, udeb
N:
E: opsgenie-icinga: changelog-file-missing-in-native-package
N:
N: Each Debian package (which provides a /usr/share/doc/<pkg> directory)
N: has to install a changelog file. Since this package seems to be a native
N: Debian package (i.e., there is no upstream source), the file should
N: usually be installed as /usr/share/doc/<pkg>/changelog.gz
N:
N: Note that Lintian may emit this tag if the changelog exists, but it does
N: not look like a Debian changelog.
N:
N: Refer to Debian Policy Manual section 12.7 (Changelog files) for
N: details.
N:
N: Severity: important, Certainty: certain
N:
N: Check: changelog-file, Type: binary
N:
E: opsgenie-icinga: non-etc-file-marked-as-conffile var/opsgenie/marid/scripts/Acknowledge.groovy
N:
N: A file installed in some other directory than /etc is marked as
N: conffile. A conffile typically implies a configuration file, and Policy
N: mandates such files to be in /etc.
N:
N: Refer to Debian Policy Manual section 10.7.2 (Location) for details.
N:
N: Severity: serious, Certainty: possible
N:
N: Check: conffiles, Type: binary
N:
E: opsgenie-icinga: non-etc-file-marked-as-conffile var/opsgenie/marid/scripts/AddNote.groovy
E: opsgenie-icinga: non-etc-file-marked-as-conffile var/opsgenie/marid/scripts/AddRecipient.groovy
E: opsgenie-icinga: non-etc-file-marked-as-conffile ... use --no-tag-display-limit to see all (or pipe to a file/program)
E: opsgenie-icinga: file-in-etc-not-marked-as-conffile etc/init.d/marid
N:
N: Files in /etc must be marked conffiles if they are included in a
N: package. Otherwise they should be created by maintainer scripts.
N:
N: Refer to Debian Policy Manual section 10.7 (Configuration files) for
N: details.
N:
N: Severity: serious, Certainty: certain
N:
N: Check: conffiles, Type: binary
N:
E: opsgenie-icinga: file-in-etc-not-marked-as-conffile etc/opsgenie/icinga2opsgenie.go
E: opsgenie-icinga: file-in-etc-not-marked-as-conffile etc/opsgenie/marid/.keystore
E: opsgenie-icinga: file-in-etc-not-marked-as-conffile ... use --no-tag-display-limit to see all (or pipe to a file/program)
E: opsgenie-icinga: no-copyright-file
N:
N: Each binary package has to include a plain file
N: /usr/share/doc/<pkg>/copyright
N:
N: Refer to Debian Policy Manual section 12.5 (Copyright information) for
N: details.
N:
N: Severity: serious, Certainty: certain
N:
N: Check: copyright-file, Type: binary
N:
E: opsgenie-icinga: extended-description-is-empty
N:
N: The extended description (the lines after the first line of the
N: "Description:" field) is empty.
N:
N: Refer to Debian Policy Manual section 3.4 (The description of a package)
N: for details.
N:
N: Severity: serious, Certainty: certain
N:
N: Check: description, Type: binary, udeb
N:
E: opsgenie-icinga: maintainer-address-missing OpsGenie
N:
N: The maintainer field must contain the package maintainer's name and
N: email address, with the name followed by the address inside angle
N: brackets (< and >). The address seems to be missing.
N:
N: Refer to Debian Policy Manual section 5.6.2 (Maintainer) for details.
N:
N: Severity: serious, Certainty: certain
N:
N: Check: fields, Type: binary, udeb, source
N:
W: opsgenie-icinga: unknown-section default
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:
E: opsgenie-icinga: non-standard-file-permissions-for-etc-init.d-script etc/init.d/marid 0644 != 0755
N:
N: Usually, scripts in the /etc/init.d directory should have mode 0755.
N:
N: Severity: important, Certainty: certain
N:
N: Check: files, Type: binary, udeb
N:
E: opsgenie-icinga: non-standard-dir-in-var var/opsgenie/
N:
N: The FHS says "Applications should generally not add directories to the
N: top level of /var. Such directories should only be added if they have
N: some system-wide implication, and in consultation with the FHS mailing
N: list."
N:
N: Refer to Filesystem Hierarchy Standard (The /var Hierarchy) for details.
N:
N: Severity: important, Certainty: certain
N:
N: Check: files, Type: binary, udeb
N:
W: opsgenie-icinga: file-in-unusual-dir var/opsgenie/marid/scripts/Acknowledge.groovy
N:
N: This file or symbolic link is in a directory where files are not
N: normally installed by Debian packages.
N:
N: Severity: normal, Certainty: certain
N:
N: Check: files, Type: binary, udeb
N:
W: opsgenie-icinga: file-in-unusual-dir var/opsgenie/marid/scripts/AddNote.groovy
W: opsgenie-icinga: file-in-unusual-dir var/opsgenie/marid/scripts/AddRecipient.groovy
W: opsgenie-icinga: file-in-unusual-dir ... use --no-tag-display-limit to see all (or pipe to a file/program)
W: opsgenie-icinga: script-in-etc-init.d-not-registered-via-update-rc.d etc/init.d/marid
N:
N: The package installs an /etc/init.d script which is not registered in
N: the postinst script. This is usually a bug (such as omitting the
N: #DEBHELPER# token) unless you omit the links intentionally for some
N: reason or create the links some other way.
N:
N: Severity: normal, Certainty: possible
N:
N: Check: init.d, Type: binary
N:
E: opsgenie-icinga: init.d-script-does-not-implement-required-option etc/init.d/marid force-reload
N:
N: The /etc/init.d scripts have to support the following command line
N: arguments: start, stop, restart, force-reload.
N:
N: Refer to Debian Policy Manual section 9.3.2 (Writing the scripts) for
N: details.
N:
N: Severity: important, Certainty: certain
N:
N: Check: init.d, Type: binary
N:
W: opsgenie-icinga: jar-not-in-usr-share var/lib/opsgenie/marid/aopalliance-repackaged-2.5.0-b32.jar
N:
N: The classpath listed in some of the files references files outside of
N: /usr/share, while all installed JAR files must be within /usr/share/java
N: for libraries or /usr/share/<package> for JARs for private use.
N:
N: The rationale is that jar files are in almost all cases architecture
N: independent and therefore should be in /usr/share. If the jar file is
N: truly architecture dependent or it cannot be moved since symlinked jar
N: files are not accepted by the application, then please override this
N: tag.
N:
N: Refer to Debian policy for Java section 2.2 (Building Java packages) and
N: Debian policy for Java section 2.3 (Java programs) for details.
N:
N: Severity: normal, Certainty: possible
N:
N: Check: java, Type: binary
N:
W: opsgenie-icinga: jar-not-in-usr-share var/lib/opsgenie/marid/async-http-client-1.7.1.jar
W: opsgenie-icinga: jar-not-in-usr-share var/lib/opsgenie/marid/bsf-2.4.0.jar
W: opsgenie-icinga: jar-not-in-usr-share ... use --no-tag-display-limit to see all (or pipe to a file/program)
W: opsgenie-icinga: codeless-jar var/lib/opsgenie/marid/org.apache.commons.lang-2.6.jar
N:
N: The jar file contains a manifest but no code. This probably indicates
N: that something went wrong at build-time.
N:
N: Severity: normal, Certainty: certain
N:
N: Check: java, Type: binary
N:
W: opsgenie-icinga: binary-without-manpage usr/bin/icinga2opsgenie
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: opsgenie-icinga: script-not-executable etc/init.d/marid
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: opsgenie-icinga: possibly-insecure-handling-of-tmp-files-in-maintainer-script postinst:30
N:
N: The maintainer script seems to access a file in /tmp or some other
N: temporary directory. Since creating temporary files in a world-writable
N: directory is very dangerous, this is likely to be a security bug. Use
N: the tempfile or mktemp utilities to create temporary files in these
N: directories.
N:
N: Refer to Debian Policy Manual section 10.4 (Scripts) for details.
N:
N: Severity: normal, Certainty: possible
N:
N: Check: scripts, Type: binary
N:
W: opsgenie-icinga: maintainer-script-ignores-errors postinst
N:
N: The maintainer script doesn't seem to set the -e flag which ensures that
N: the script's execution is aborted when any executed command fails.
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:
W: opsgenie-icinga: maintainer-script-ignores-errors preinst
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent