Lintian v2.122.0 Options: -i -I -E --pedantic --profile debian N: W: liferea source: mismatched-override source-is-missing [js/purify.min.js] [debian/source/lintian-overrides:4] N: N: The named tag would have been silenced except the context specified with N: the override did not match. N: N: Lintian may now provide a different context for the tag, or something N: could have changed in a new version of your package. Either way, overrides N: work best when you require as little context as needed. N: N: You can use wildcards, such as * or ? in the context to make a match more N: likely. N: N: Please remove or adjust the override. N: N: Visibility: warning N: Show-Always: yes N: Check: lintian N: N: I: liferea source: invalid-dep3-format-patch-no-origin [debian/patches/www-browser.patch] N: N: According to the DEP-3, this patch's headers should contain the Origin N: field. N: N: Please refer to https://dep-team.pages.debian.net/deps/dep3/ for details. N: N: Visibility: info N: Show-Always: no N: Check: debian/patches/dep3 N: N: I: liferea source: out-of-date-standards-version 4.7.0 (released 2024-04-07) (current is 4.7.2) N: N: The source package refers to a Standards-Version older than the one that N: was current at the time the package was created (according to the N: timestamp of the latest debian/changelog entry). Please consider updating N: the package to current Policy and setting this control field N: appropriately. N: N: If the package is already compliant with the current standards, you don't N: have to re-upload the package just to adjust the Standards-Version control N: field. However, please remember to update this field next time you upload N: the package. N: N: See /usr/share/doc/debian-policy/upgrading-checklist.txt.gz in the N: debian-policy package for a summary of changes in newer versions of N: Policy. N: N: Please refer to N: https://www.debian.org/doc/debian-policy/upgrading-checklist.html for N: details. N: N: Visibility: info N: Show-Always: no N: Check: fields/standards-version N: N: I: liferea source: quilt-patch-missing-description [debian/patches/dont-run-tests-with-network] 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, the N: 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: Please refer to https://dep-team.pages.debian.net/deps/dep3/ for details. N: N: Visibility: info N: Show-Always: no N: Check: debian/patches/quilt N: N: I: liferea source: repackaged-source-not-advertised [debian/copyright] N: N: The debian/copyright file mentions Files-Excluded but the source version N: has no repack suffix. N: N: Repackaged sources are expected to indicate in their version number that N: they are different from the upstream release. It is commonly done by N: adding a repack suffix to the upstream version. N: N: The choice of repack suffix depends on the reason for repackaging. When N: some files were excluded because licensing was a concern, the suffix +dfsg N: may be appropriate. In more generic cases, one could chose +ds. N: N: Upstream sources are sometimes repackaged by accident when using old N: versions of dh_make. It can also happen when a maintainer invokes the N: dh_make option --createorig even though it is not needed. N: N: According to the Debian Developer's Reference 6.7.8.2, the repack suffix N: is not required. N: N: Please include such a suffix in the changelog version number to avoid this N: warning. N: N: Please refer to Bug#471537 and N: https://www.debian.org/doc/manuals/developers-reference/best-pkging-practices.html N: for details. N: N: Visibility: info N: Show-Always: no N: Check: debian/copyright/dep5 N: N: I: liferea source: unused-license-paragraph-in-dep5-copyright mpl-2 [debian/copyright:520] N: N: The license paragraph in the machine-readable copyright file is not N: referenced by any files paragraph. It could be a typo in the license name N: or the license paragraph is simply not needed and can be removed. N: N: Please refer to N: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ for N: details. N: N: Visibility: info N: Show-Always: no N: Check: debian/copyright/dep5 N: N: X: liferea source: debian-watch-does-not-check-openpgp-signature [debian/watch] N: N: This watch file does not specify a means to verify the upstream tarball N: using a cryptographic signature. N: N: If upstream distributions provides such signatures, please use the N: pgpsigurlmangle options in this watch file's opts= to generate the URL of N: an upstream OpenPGP signature. This signature is automatically downloaded N: and verified against a keyring stored in debian/upstream/signing-key.asc N: N: Of course, not all upstreams provide such signatures but you could request N: them as a way of verifying that no third party has modified the code after N: its release (projects such as phpmyadmin, unrealircd, and proftpd have N: suffered from this kind of attack). N: N: Please refer to the uscan(1) manual page for details. N: N: Visibility: pedantic N: Show-Always: no N: Check: debian/watch N: Renamed from: debian-watch-does-not-check-gpg-signature N: debian-watch-may-check-gpg-signature N: This tag is experimental. N: N: X: liferea source: prefer-uscan-symlink filenamemangle s%v?@ANY_VERSION@%@PACKAGE@-$1.tar.gz% [debian/watch:7] N: N: Please consider setting USCAN_SYMLINK=rename in your ~/.devscripts N: configuration file instead of using the option filenamemangle in N: debian/watch. N: N: Please check with your team before making changes to sources you maintain N: together. There are circumstances when the filenamemangle option is N: better. N: N: Please refer to the uscan(1) manual page for details. N: N: Visibility: pedantic N: Show-Always: no N: Check: debian/watch N: This tag is experimental. N: N: X: liferea source: upstream-metadata-file-is-missing N: N: This source package is not Debian-native but it does not have a N: debian/upstream/metadata file. N: N: The Upstream MEtadata GAthered with YAml (UMEGAYA) project is an effort to N: collect meta-information about upstream projects from any source package. N: This file is in YAML format and it is used in to feed the data in the N: UltimateDebianDatabase. For example, it can contains the way the authors N: want their software be cited in publications and some bibliographic N: references about the software. N: N: Please add a debian/upstream/metadata file. N: N: Please refer to https://dep-team.pages.debian.net/deps/dep12/ and N: https://wiki.debian.org/UpstreamMetadata for details. N: N: Visibility: pedantic N: Show-Always: no N: Check: debian/upstream/metadata N: This tag is experimental. N: N: X: liferea source: very-long-line-length-in-source-file 571 > 512 [src/xml.c:127] N: N: The source file includes a line length that is well beyond the normally N: human made code line length. N: N: This very long line length does not allow Lintian to do correctly some N: source file checks. N: N: This line could also be the result of some text injected by a computer N: program, and thus could lead to FTBFS bugs. N: N: Last but not least, long line in source code could be used to obfuscate N: the source code and to hide stuff like backdoors or security problems. N: N: It could be due to jslint source comments or other build tool comments. N: N: You may report this issue upstream. N: N: Visibility: pedantic N: Show-Always: no N: Check: files/contents/line-length N: Renamed from: insane-line-length-in-source-file N: This tag is experimental. N: N: Screen: autotools/long-lines N: Advocates: "Russ Allbery" N: Reason: N: Upstream sources using autoconf have traditionally been N: distributed with generated ./configure scripts as well as N: other third-party m4 macro files such as libtool. N: N: When paired with automake, there may also be some intermediate N: Makefile.in files. N: N: A lot of sources potentially contain such files, but they are N: not actionable by either the Debian distributor or by the N: upstream maintainer. N: N: As a side note, modern Debian build protocols will re-create N: many of those files via dh_autoreconf. They are present merely N: to aid in bootstrapping systems where the GNU suite may not yet N: be available. N: N: Read more in Bug#996740. N: N: X: liferea source: very-long-line-length-in-source-file 614 > 512 [opml/feedlist_bg.opml:10] N: X: liferea source: very-long-line-length-in-source-file 955 > 512 [opml/feedlist_he.opml:19] N: 0 hints overridden; 1 unused override