Lintian v2.122.0
Options: -i -I -E --pedantic --profile debian

N:
W: remmina: bad-whatis-entry [usr/share/man/man1/remmina-file-wrapper.1.gz]
N: 
N:   A manual page should start with a NAME section, which lists the program
N:   name and a brief description. The NAME section is used to generate a
N:   database that can be queried by commands like apropos and whatis. You are
N:   seeing this tag because lexgrog was unable to parse the NAME section.
N:   
N:   Manual pages for multiple programs, functions, or files should list each
N:   separated by a comma and a space, followed by \- and a common description.
N:   
N:   Listed items may not contain any spaces. A manual page for a two-level
N:   command such as fs listacl must look like fs_listacl so the list is read
N:   correctly.
N: 
N:   Please refer to the lexgrog(1) manual page, the groff_man(7) manual page,
N:   and the groff_mdoc(7) manual page for details.
N: 
N:   Visibility: warning
N:   Show-Always: no
N:   Check: documentation/manual
N:   Renamed from: manpage-has-bad-whatis-entry
N: 
N:
I: remmina-common: bash-term-in-posix-shell '. $(dirname $0)/functions.sh' [usr/share/remmina/external_tools/remmina_filezilla_sftp.sh:3]
N: 
N:   This script is marked as running under /bin/sh, but it seems to use a
N:   feature found in bash but not in the SUSv3 or POSIX shell specification.
N:   
N:   Some examples are:
N:   
N:   - == in a test, it should use = instead - read without a variable in the
N:   argument - function to define a function - source instead of . - . command
N:   args, passing arguments to commands via source is not supported -
N:   {foo,bar} instead of foo bar - [[ test ]] instead of [ test ] (requires a
N:   Korn shell) - type instead of which or command -v
N: 
N:   Visibility: info
N:   Show-Always: no
N:   Check: shell/non-posix/bash-centric
N: 
N:
I: remmina-common: bash-term-in-posix-shell '. $(dirname $0)/functions.sh' [usr/share/remmina/external_tools/remmina_filezilla_sftp_pki.sh:3]
N:
I: remmina-common: bash-term-in-posix-shell '. $(dirname $0)/functions.sh' [usr/share/remmina/external_tools/remmina_nslookup.sh:3]
N:
I: remmina-common: bash-term-in-posix-shell '. $(dirname $0)/functions.sh' [usr/share/remmina/external_tools/remmina_ping.sh:3]
N:
I: remmina-common: bash-term-in-posix-shell '. $(dirname $0)/functions.sh' [usr/share/remmina/external_tools/remmina_traceroute.sh:3]
N:
I: remmina-common: bash-term-in-posix-shell 'echo -n -e' [usr/share/remmina/external_tools/functions.sh:15]
N:
I: remmina-plugin-kiosk: desktop-entry-lacks-keywords-entry [usr/share/xsessions/remmina-gnome.desktop]
N: 
N:   This .desktop file is either missing a Keywords entry, or it does not
N:   contain keywords above and beyond those already present in the Name or
N:   GenericName entries.
N:   
N:   The Keywords field is intended to show keywords relevant for a .desktop
N:   file.
N:   
N:   Desktop files are organized in key-value pairs and are similar to INI
N:   files.
N:   
N:   The desktop-file-validate tool in the desktop-file-utils package may be
N:   useful when checking the syntax of desktop entries.
N: 
N:   Please refer to
N:   https://specifications.freedesktop.org/desktop-entry-spec/latest/ar01s06.html,
N:   Bug#693918, and
N:   https://wiki.gnome.org/Initiatives/GnomeGoals/DesktopFileKeywords for
N:   details.
N: 
N:   Visibility: info
N:   Show-Always: no
N:   Check: menu-format
N: 
N:
I: remmina: file-references-package-build-path [usr/bin/remmina]
N: 
N:   The listed file or maintainer script appears to reference the build path
N:   used to build the package as specified in the Build-Path field of the
N:   .buildinfo file.
N:   
N:   This is likely to cause the package to be unreproducible, but it may also
N:   indicate that the package will not work correctly outside of the
N:   maintainer's own system.
N:   
N:   Please note that this tag will not appear unless the .buildinfo file
N:   contains a Build-Path field. That field is optional. You may have to set
N:   DEB_BUILD_OPTIONS=buildinfo=+path or use
N:   --buildinfo-option=--always-include-path with dpkg-buildpackage when
N:   building.
N: 
N:   Please refer to https://reproducible-builds.org/,
N:   https://wiki.debian.org/ReproducibleBuilds/BuildinfoFiles, and the
N:   dpkg-genbuildinfo(1) manual page for details.
N: 
N:   Visibility: info
N:   Show-Always: no
N:   Check: files/contents
N: 
N:
I: remmina-plugin-kwallet: hardening-no-fortify-functions [usr/lib/x86_64-linux-gnu/remmina/plugins/remmina-plugin-kwallet.so]
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 by
N:   any routines, all unfortified calls have already been fully validated at
N:   compile-time, or the package was not built with the default Debian
N:   compiler flags defined by dpkg-buildflags. If built using dpkg-buildflags
N:   directly, be sure to import CPPFLAGS.
N:   
N:   NB: Due to false-positives, Lintian ignores some unprotected functions
N:   (e.g. memcpy).
N: 
N:   Please refer to https://wiki.debian.org/Hardening and Bug#673112 for
N:   details.
N: 
N:   Visibility: info
N:   Show-Always: no
N:   Check: binaries/hardening
N: 
N:
I: remmina-plugin-python: hardening-no-fortify-functions [usr/lib/x86_64-linux-gnu/remmina/plugins/remmina-plugin-python_wrapper.so]
N:
P: remmina-common: locale-uses-language-group-code ber [usr/share/locale/ber/]
N: 
N:   The package appears to ship locales for a language group rather than a
N:   language as a subdirectory of /usr/share/locale. The language codes used
N:   in the locale directories are those from the ISO 639-1 and ISO 639-2
N:   standards, and does not include language group codes from the ISO 639-5
N:   standard.
N: 
N:   Please refer to Bug#1013946 for details.
N: 
N:   Visibility: pedantic
N:   Show-Always: no
N:   Check: files/locales
N: 
N:
X: remmina 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: remmina-plugin-kiosk: package-contains-no-arch-dependent-files
N: 
N:   All files in this package are architecture-independent, but the package is
N:   not marked Architecture: all.
N:   
N:   The package should probably be marked Architecture: all.
N: 
N:   Please refer to Architecture (Section 5.6.8) in the Debian Policy Manual
N:   for details.
N: 
N:   Visibility: info
N:   Show-Always: no
N:   Check: files/architecture
N:   This tag is experimental.
N: 
N:
X: remmina source: prefer-uscan-symlink filenamemangle s%.*\/archive\/v(\d\S+)\/Remmina.*\.tar\.gz%remmina-$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: remmina-plugin-x2go: spelling-error-in-binary occured occurred [usr/lib/x86_64-linux-gnu/remmina/plugins/remmina-plugin-x2go.so]
N: 
N:   Lintian found a spelling error in the given binary. Lintian has a list of
N:   common misspellings that it looks for. It does not have a dictionary like
N:   a spelling checker does.
N:   
N:   If the string containing the spelling error is translated with the help of
N:   gettext or a similar tool, please fix the error in the translations as
N:   well as the English text to avoid making the translations fuzzy. With
N:   gettext, for example, this means you should also fix the spelling mistake
N:   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:   Visibility: pedantic
N:   Show-Always: no
N:   Check: binaries/spelling
N:   This tag is experimental.
N: 
N:
X: remmina source: update-debian-copyright 2022 vs 2025 [debian/copyright:40]
N: 
N:   The most recent copyright year mentioned for files in ./debian lags behind
N:   the year in the timestamp for the most recent changelog entry.
N: 
N:   Visibility: pedantic
N:   Show-Always: no
N:   Check: debian/copyright/dep5
N:   This tag is experimental.
N: 
N:
X: remmina source: very-long-line-length-in-source-file 522 > 512 [data/desktop/remmina-gnome.session:5]
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" <rra@debian.org>
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: remmina source: very-long-line-length-in-source-file 568 > 512 [environments/vncserver-ssh-socket-forward/ssh_key.pub:1]