Lintian v2.5.21~bpo70+1 Options: -i -I -E --pedantic --profile ubuntu P: libomxil-bellagio source: debian-control-has-unusual-field-spacing line 106 N: N: The field on this line of debian/control has whitespace other than a N: single space after the colon. This is explicitly permitted in the syntax N: of Debian control files, but as Policy says, it is conventional to put a N: single space after the colon. N: N: Refer to Debian Policy Manual section 5.1 (Syntax of control files) for N: details. N: N: Severity: pedantic, Certainty: certain N: N: Check: control-file, Type: source N: I: libomxil-bellagio source: binary-control-field-duplicates-source field "section" in package libomxil-bellagio0 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: libomxil-bellagio source: binary-control-field-duplicates-source field "section" in package libomxil-bellagio0-components-base I: libomxil-bellagio source: duplicate-long-description libomxil-bellagio0-components-base-dbg libomxil-bellagio0-dbg 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: I: libomxil-bellagio source: vcs-field-not-canonical http://git.debian.org/?p=collab-maint/libomxil-bellagio.git http://anonscm.debian.org/gitweb/?p=collab-maint/libomxil-bellagio.git N: N: The VCS-* field contains an uncanonical URI. Please update to use the N: current canonical URI instead. This reduces the network bandwidth used N: and makes debcheckout work independent of the port forwarding and N: redirections properly working. N: N: The definition of canonical used here is the URIs announced by the N: Alioth admins (see reference). N: N: Note that this check is based on a list of known URIs. Lintian did not N: send a HTTP request to the URI to test this. Should the canonical URI N: have changed, please file a bug against Lintian so the check can be N: updated accordingly. N: N: Refer to N: https://lists.debian.org/debian-devel-announce/2011/05/msg00009.html for N: details. N: N: Severity: minor, Certainty: possible N: N: Check: fields, Type: binary, udeb, source N: I: libomxil-bellagio source: vcs-field-not-canonical git://git.debian.org/git/collab-maint/libomxil-bellagio.git git://anonscm.debian.org/collab-maint/libomxil-bellagio.git W: libomxil-bellagio source: intra-source-package-circular-dependency libomxil-bellagio-bin libomxil-bellagio0 N: N: The listed packages from the same source circularly depend (or N: pre-depend) on each other. This makes it difficult for tools to properly N: handle install/upgrade sequences. Furthermore this complicates automated N: removal of unused packages. N: N: If possible, consider removing or reducing one of the depends. N: N: Note: This check is limited to packages created from the same source N: package. Full circular dependencies between binaries from different N: source packages is beyond the scope of Lintian. N: N: Refer to Debian Policy Manual section 7.2 (Binary Dependencies - N: Depends, Recommends, Suggests, Enhances, Pre-Depends) for details. N: N: Severity: normal, Certainty: certain N: N: Check: group-checks, Type: source N: I: libomxil-bellagio source: quilt-patch-missing-description 0003_fix_docdir.patch N: N: quilt patch files should start with a description of patch. All lines N: before the start of the patch itself are considered part of the N: description. You can edit the description with quilt header -e when the N: patch is at the top of the stack. N: N: As well as a description of the purpose and function of the patch, the N: description should ideally contain author information, a URL for the bug N: report (if any), Debian or upstream bugs fixed by it, upstream status, N: the Debian version and date the patch was first included, and any other N: information that would be useful if someone were investigating the patch N: and underlying problem. Please consider using the DEP-3 format for this N: information. N: N: Refer to http://dep.debian.net/deps/dep3/ for details. N: N: Severity: wishlist, Certainty: certain N: N: Check: patch-systems, Type: source N: I: libomxil-bellagio source: quilt-patch-missing-description 0007_remove_online_sourceforge_logo.patch P: libomxil-bellagio source: debian-watch-may-check-gpg-signature N: N: This watch file does not include a means to verify the upstream tarball N: using cryptographic signature. N: N: If upstream distributions provide such signatures, please use the N: pgpsigurlmangle options in this watch file's opts= to generate the URL N: of an upstream GPG signature. This signature is automatically downloaded N: and verified against a keyring stored in debian/upstream-signing-key.pgp N: N: Of course, not all upstreams provide such signatures, but you could N: request them as a way of verifying that no third party has modified the N: code against their wishes after the release. We have all heard of the N: phpmyadmin, unrealircd, or proftpd security bugs (to mention only a N: few). This would at least make it a lot harder for an attacker to get N: such code to a wider audience via distributions like Debian. N: N: Refer to the uscan(1) manual page for details. N: N: Severity: pedantic, Certainty: certain N: N: Check: watch-file, Type: source N: W: libomxil-bellagio-doc: wrong-name-for-upstream-changelog usr/share/doc/libomxil-bellagio-doc/ChangeLog N: N: If there is an upstream changelog file, it should usually be installed N: as /usr/share/doc//changelog.gz N: N: Refer to Debian Policy Manual section 12.7 (Changelog files) for N: details. N: N: Severity: normal, Certainty: possible N: N: Check: changelog-file, Type: binary N: X: libomxil-bellagio-doc: duplicate-files usr/share/doc/libomxil-bellagio-doc/html/ftv2plastnode.png usr/share/doc/libomxil-bellagio-doc/html/ftv2pnode.png N: N: The package ships the two (or more) files with the exact same contents. N: N: Note: empty files are exempt from this check. N: N: Severity: pedantic, Certainty: possible N: N: Check: duplicate-files, Type: binary N: N: This tag is marked experimental, which means that the code that N: generates it is not as well-tested as the rest of Lintian and might N: still give surprising results. Feel free to ignore experimental tags N: that do not seem to make sense, though of course bug reports are always N: welcome. N: X: libomxil-bellagio-doc: duplicate-files usr/share/doc/libomxil-bellagio-doc/html/ftv2doc.png usr/share/doc/libomxil-bellagio-doc/html/ftv2link.png X: libomxil-bellagio-doc: duplicate-files usr/share/doc/libomxil-bellagio-doc/html/ftv2blank.png usr/share/doc/libomxil-bellagio-doc/html/ftv2lastnode.png usr/share/doc/libomxil-bellagio-doc/html/ftv2node.png usr/share/doc/libomxil-bellagio-doc/html/ftv2vertline.png X: libomxil-bellagio-doc: duplicate-files usr/share/doc/libomxil-bellagio-doc/html/ftv2mlastnode.png usr/share/doc/libomxil-bellagio-doc/html/ftv2mnode.png W: libomxil-bellagio0-components-base-dbg: debug-file-with-no-debug-symbols usr/lib/debug/usr/lib/libomxil-bellagio0/libomxaudio_effects.so.0.0.0 N: N: The binary is installed as a detached "debug symbols" ELF file, but it N: does not appear to have debug information associated with it. N: N: Implementation detail: Lintian currently checks for the ".debug_line" N: section, which is a part of the DWARF standard. N: N: Refer to http://bugs.debian.org/668437 for details. N: N: Severity: normal, Certainty: possible N: N: Check: binaries, Type: binary, udeb N: W: libomxil-bellagio0-components-base-dbg: debug-file-with-no-debug-symbols usr/lib/debug/usr/lib/libomxil-bellagio0/libomxclocksrc.so.0.0.0 W: libomxil-bellagio0-components-base-dbg: debug-file-with-no-debug-symbols usr/lib/debug/usr/lib/libomxil-bellagio0/libomxvideosched.so.0.0.0 X: libomxil-bellagio0-components-base-dbg: package-contains-broken-symlink usr/share/doc/libomxil-bellagio0-components-base-dbg/changelog.Debian.gz ../libomxil-bellagio-bin/changelog.Debian.gz N: N: The package contains a symlink but the destination for the link does not N: exist in the package nor in its direct dependencies. N: N: Severity: normal, Certainty: wild-guess N: N: Check: symlinks, Type: binary, udeb N: N: This tag is marked experimental, which means that the code that N: generates it is not as well-tested as the rest of Lintian and might N: still give surprising results. Feel free to ignore experimental tags N: that do not seem to make sense, though of course bug reports are always N: welcome. N: X: libomxil-bellagio-dev: package-contains-broken-symlink usr/share/doc/libomxil-bellagio-dev/changelog.Debian.gz ../libomxil-bellagio-bin/changelog.Debian.gz I: libomxil-bellagio0-components-base: hardening-no-fortify-functions usr/lib/libomxil-bellagio0/libomxaudio_effects.so.0.0.0 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: wild-guess N: N: Check: binaries, Type: binary, udeb N: I: libomxil-bellagio0-components-base: hardening-no-fortify-functions usr/lib/libomxil-bellagio0/libomxclocksrc.so.0.0.0 I: libomxil-bellagio0-components-base: hardening-no-fortify-functions usr/lib/libomxil-bellagio0/libomxvideosched.so.0.0.0 X: libomxil-bellagio0-components-base: package-contains-broken-symlink usr/share/doc/libomxil-bellagio0-components-base/changelog.Debian.gz ../libomxil-bellagio-bin/changelog.Debian.gz I: libomxil-bellagio0: hardening-no-fortify-functions usr/lib/libomxil-bellagio.so.0.0.0 I: libomxil-bellagio0: package-contains-empty-directory usr/lib/libomxil-bellagio0/ N: N: This package installs an empty directory. This might be intentional but N: it's normally a mistake. If it is intentional, add a lintian override. N: N: If a package ships with or installs empty directories, you can remove N: them in debian/rules by calling: N: N: $ find path/to/base/dir -type d -empty -delete N: N: Severity: wishlist, Certainty: possible N: N: Check: files, Type: binary, udeb N: P: libomxil-bellagio0: maintainer-script-without-set-e prerm N: N: The maintainer script passes -e to the shell on the #! line rather than N: using set -e in the body of the script. This is fine for normal N: operation, but if the script is run by hand with sh /path/to/script N: (common in debugging), -e will not be in effect. It's therefore better N: to use set -e in the body of the script. N: N: Refer to Debian Policy Manual section 10.4 (Scripts) for details. N: N: Severity: pedantic, Certainty: certain N: N: Check: scripts, Type: binary N: P: libomxil-bellagio0: maintainer-script-without-set-e postinst I: libomxil-bellagio0: no-symbols-control-file usr/lib/libomxil-bellagio.so.0.0.0 N: N: Although the package includes a shared library, the package does not N: have a symbols control file. N: N: dpkg can use symbols files in order to generate more accurate library N: dependencies for applications, based on the symbols from the library N: that are actually used by the application. N: N: Refer to the dpkg-gensymbols(1) manual page and N: http://wiki.debian.org/UsingSymbolsFiles for details. N: N: Severity: wishlist, Certainty: certain N: N: Check: shared-libs, Type: binary, udeb N: I: libomxil-bellagio-bin: spelling-error-in-binary usr/bin/omxregister-bellagio succesfully successfully 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 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: I: libomxil-bellagio-bin: hardening-no-fortify-functions usr/bin/omxregister-bellagio W: libomxil-bellagio0-dbg: debug-file-with-no-debug-symbols usr/lib/debug/usr/bin/omxregister-bellagio W: libomxil-bellagio0-dbg: debug-file-with-no-debug-symbols usr/lib/debug/usr/lib/libomxil-bellagio.so.0.0.0 X: libomxil-bellagio0-dbg: package-contains-broken-symlink usr/share/doc/libomxil-bellagio0-dbg/changelog.Debian.gz ../libomxil-bellagio-bin/changelog.Debian.gz