1cmd: lintian --no-cfg --display-level '>=classification' --display-experimental --info --show-overrides '/tmp/debusine-fetch-exec-upload-pn5u_s32/akode_14.1.6~pre2-0ubuntu20.04.0+3.dsc' '/tmp/debusine-fetch-exec-upload-pn5u_s32/akode-dbg_14.1.6~pre2-0ubuntu20.04.0+3_ppc64el.deb' '/tmp/debusine-fetch-exec-upload-pn5u_s32/libakode-dev_14.1.6~pre2-0ubuntu20.04.0+3_ppc64el.deb' '/tmp/debusine-fetch-exec-upload-pn5u_s32/libakode2-bin_14.1.6~pre2-0ubuntu20.04.0+3_ppc64el.deb' '/tmp/debusine-fetch-exec-upload-pn5u_s32/libakode2-ffmpeg_14.1.6~pre2-0ubuntu20.04.0+3_ppc64el.deb' '/tmp/debusine-fetch-exec-upload-pn5u_s32/libakode2-jack_14.1.6~pre2-0ubuntu20.04.0+3_ppc64el.deb' '/tmp/debusine-fetch-exec-upload-pn5u_s32/libakode2-mpeg_14.1.6~pre2-0ubuntu20.04.0+3_ppc64el.deb' '/tmp/debusine-fetch-exec-upload-pn5u_s32/libakode2-pulse_14.1.6~pre2-0ubuntu20.04.0+3_ppc64el.deb' '/tmp/debusine-fetch-exec-upload-pn5u_s32/libakode2_14.1.6~pre2-0ubuntu20.04.0+3_ppc64el.deb' 2output (contains stderr only, stdout was captured): 3 4Files in working directory: 5lintian.txt 6-------------------- 7E: libakode2: sharedobject-in-library-directory-missing-soname usr/lib/powerpc64le-linux-gnu/libakode_alsa_sink.so 8N: 9N: A shared object was identified in a library directory (a directory in 10N: the standard linker path) which doesn't have a SONAME. This is usually 11N: an error. 12N: 13N: SONAMEs are set with something like gcc -Wl,-soname,libfoo.so.0, where 0 14N: is the major version of the library. If your package uses libtool, then 15N: libtool invoked with the right options should be doing this. 16N: 17N: To view the SONAME of a shared library, run readelf -d on the shared 18N: library and look for the tag of type SONAME. 19N: 20N: Severity: error 21N: 22N: Check: shared-libs 23N: 24E: libakode2: sharedobject-in-library-directory-missing-soname usr/lib/powerpc64le-linux-gnu/libakode_mpc_decoder.so 25E: libakode2: sharedobject-in-library-directory-missing-soname usr/lib/powerpc64le-linux-gnu/libakode_oss_sink.so 26E: libakode2: sharedobject-in-library-directory-missing-soname usr/lib/powerpc64le-linux-gnu/libakode_src_resampler.so 27E: libakode2: sharedobject-in-library-directory-missing-soname usr/lib/powerpc64le-linux-gnu/libakode_xiph_decoder.so 28E: libakode2-ffmpeg: sharedobject-in-library-directory-missing-soname usr/lib/powerpc64le-linux-gnu/libakode_ffmpeg_decoder.so 29E: libakode2-jack: sharedobject-in-library-directory-missing-soname usr/lib/powerpc64le-linux-gnu/libakode_jack_sink.so 30E: libakode2-mpeg: sharedobject-in-library-directory-missing-soname usr/lib/powerpc64le-linux-gnu/libakode_mpeg_decoder.so 31E: libakode2-pulse: sharedobject-in-library-directory-missing-soname usr/lib/powerpc64le-linux-gnu/libakode_pulse_sink.so 32W: akode source: ancient-standards-version 3.7.3 (released 2007-12-03) (current is 4.5.0) 33N: 34N: The source package refers to a Standards-Version that has been obsolete 35N: for more than two years. Please update your package to latest Policy and 36N: set this control field appropriately. 37N: 38N: If the package is already compliant with the current standards, you 39N: don't have to re-upload the package just to adjust the Standards-Version 40N: control field. However, please remember to update this field next time 41N: you upload the package. 42N: 43N: See /usr/share/doc/debian-policy/upgrading-checklist.txt.gz in the 44N: debian-policy package for a summary of changes in newer versions of 45N: Policy. 46N: 47N: Refer to 48N: https://www.debian.org/doc/debian-policy/upgrading-checklist.html for 49N: details. 50N: 51N: Severity: warning 52N: 53N: Check: fields/standards-version 54N: 55W: libakode-dev: binary-without-manpage usr/bin/akode-config 56N: 57N: Each binary in /usr/bin, /usr/sbin, /bin, /sbin or /usr/games should 58N: have a manual page 59N: 60N: Note that though the man program has the capability to check for several 61N: program names in the NAMES section, each of these programs should have 62N: its own manual page (a symbolic link to the appropriate manual page is 63N: sufficient) because other manual page viewers such as xman or tkman 64N: don't support this. 65N: 66N: If the name of the man page differs from the binary by case, man may be 67N: able to find it anyway; however, it is still best practice to make the 68N: case of the man page match the case of the binary. 69N: 70N: If the man pages are provided by another package on which this package 71N: depends, Lintian may not be able to determine that man pages are 72N: available. In this case, after confirming that all binaries do have man 73N: pages after this package and its dependencies are installed, please add 74N: a Lintian override. 75N: 76N: Refer to Debian Policy Manual section 12.1 (Manual pages) for details. 77N: 78N: Severity: warning 79N: 80N: Check: documentation/man 81N: 82W: libakode2-bin: binary-without-manpage usr/bin/akodeplay 83W: akode source: debian-source-options-has-custom-compression-settings compression = "xz" (line 2) 84N: 85N: The debian/source/options file for this package specifies a custom 86N: compression level or algorithm. 87N: 88N: Whilst higher levels may reduce the size of big files, they have the 89N: side effect of consuming a lot of memory during both compression and 90N: extraction. This can not only also waste time unnecessarily, it can 91N: cause packages to FTBFS or even fail to install in resource-constrained 92N: environments or architectures. 93N: 94N: Please remove the call and let dpkg-deb(1) select suitable defaults. 95N: 96N: Refer to https://bugs.debian.org/829100 and the dpkg-deb(1) manual page 97N: for details. 98N: 99N: Severity: warning 100N: 101N: Check: debian/source-dir 102N: 103W: akode source: debian-source-options-has-custom-compression-settings compression-level = 9 (line 3) 104W: libakode-dev: spelling-error-in-description runing running 105N: 106N: Lintian found a spelling error in the package description. Lintian has a 107N: list of common misspellings that it looks for. It does not have a 108N: dictionary like a spelling checker does. It is particularly picky about 109N: spelling and capitalization in package descriptions since they're very 110N: visible to end users. 111N: 112N: Severity: warning 113N: 114N: Check: fields/description 115N: 116W: libakode2: spelling-error-in-description runing running 117W: libakode2-bin: spelling-error-in-description runing running 118W: libakode2-ffmpeg: spelling-error-in-description runing running 119W: libakode2-jack: spelling-error-in-description runing running 120W: libakode2-mpeg: spelling-error-in-description runing running 121W: libakode2-pulse: spelling-error-in-description runing running 122I: akode source: binary-control-field-duplicates-source field "priority" in package akode-dbg 123N: 124N: In debian/control, this field for a binary package duplicates the value 125N: inherited from the source package paragraph. This doesn't hurt anything, 126N: but you may want to take advantage of the inheritance and set the value 127N: in only one place. It prevents missing duplicate places that need to be 128N: fixed if the value ever changes. 129N: 130N: Severity: info 131N: 132N: Check: debian/control 133N: 134I: libakode2-bin: conflicts-with-version libakode2 (<< 4:14.1.6~) 135N: 136N: An earlier-than version clause is normally an indication that Breaks 137N: should be used instead of Conflicts. Breaks is a weaker requirement that 138N: provides the package manager more leeway to find a valid upgrade path. 139N: Conflicts should only be used if two packages can never be unpacked at 140N: the same time, or for some situations involving virtual packages (where 141N: a version clause is not appropriate). In particular, when moving files 142N: between packages, use Breaks plus Replaces, not Conflicts plus Replaces. 143N: 144N: Refer to Debian Policy Manual section 7.4 (Conflicting binary packages - 145N: Conflicts) for details. 146N: 147N: Severity: info 148N: 149N: Check: fields/package-relations 150N: 151I: akode source: debian-control-has-obsolete-dbg-package akode-dbg 152N: 153N: The debian/control file includes declaration of -dbg package. 154N: 155N: Debug package are now autogenerated avoiding waste of miror space. 156N: 157N: Please note that -dbg should be dropped from control file and must not 158N: be transitioned to a dummy package depending on -dbgsym. 159N: 160N: Refer to https://wiki.debian.org/AutomaticDebugPackages for details. 161N: 162N: Severity: info 163N: 164N: Check: debian/control 165N: 166I: akode source: debian-watch-file-is-missing 167N: 168N: This source package is not Debian-native but it does not have a 169N: debian/watch file. This file is used for automatic detection of new 170N: upstream versions by the Debian External Health Status project and other 171N: project infrastructure. If this package is maintained upstream, please 172N: consider adding a debian/watch file to detect new releases. 173N: 174N: If the package is not maintained upstream or if upstream uses a 175N: distribution mechanism that cannot be meaningfully monitored by uscan 176N: and the Debian External Health Status project, please consider adding a 177N: debian/watch file containing only comments documenting the situation. 178N: 179N: Refer to Debian Policy Manual section 4.11 (Optional upstream source 180N: location: debian/watch) and the uscan(1) manual page for details. 181N: 182N: Severity: info 183N: 184N: Check: debian/watch 185N: 186I: akode source: duplicate-short-description libakode2 libakode2-bin 187N: 188N: The listed binary packages all share the same short description (the 189N: first line of the Description control field). The package names may 190N: provide enough additional information to distinguish between the 191N: packages, but it's common to also add a word or two to the short 192N: description to clarify the difference. 193N: 194N: Severity: info 195N: 196N: Check: debian/control 197N: 198I: libakode2: hardening-no-bindnow usr/lib/powerpc64le-linux-gnu/libakode.so.2.0.0 199N: 200N: This package provides an ELF binary that lacks the "bindnow" linker 201N: flag. 202N: 203N: This is needed (together with "relro") to make the "Global Offset Table" 204N: (GOT) fully read-only. The bindnow feature trades startup time for 205N: improved security. Please consider enabling this feature or consider 206N: overriding the tag (possibly with a comment about why). 207N: 208N: If you use dpkg-buildflags, you may have to add hardening=+bindnow or 209N: hardening=+all to DEB_BUILD_MAINT_OPTIONS. 210N: 211N: The relevant compiler flags are set in LDFLAGS. 212N: 213N: Refer to https://wiki.debian.org/Hardening for details. 214N: 215N: Severity: info 216N: 217N: Check: binaries 218N: 219I: libakode2: hardening-no-bindnow usr/lib/powerpc64le-linux-gnu/libakode_alsa_sink.so 220I: libakode2: hardening-no-bindnow usr/lib/powerpc64le-linux-gnu/libakode_mpc_decoder.so 221I: libakode2: hardening-no-bindnow usr/lib/powerpc64le-linux-gnu/libakode_oss_sink.so 222I: libakode2: hardening-no-bindnow usr/lib/powerpc64le-linux-gnu/libakode_src_resampler.so 223I: libakode2: hardening-no-bindnow usr/lib/powerpc64le-linux-gnu/libakode_xiph_decoder.so 224I: libakode2-ffmpeg: hardening-no-bindnow usr/lib/powerpc64le-linux-gnu/libakode_ffmpeg_decoder.so 225I: libakode2-jack: hardening-no-bindnow usr/lib/powerpc64le-linux-gnu/libakode_jack_sink.so 226I: libakode2-mpeg: hardening-no-bindnow usr/lib/powerpc64le-linux-gnu/libakode_mpeg_decoder.so 227I: libakode2-pulse: hardening-no-bindnow usr/lib/powerpc64le-linux-gnu/libakode_pulse_sink.so 228I: libakode2: hardening-no-fortify-functions usr/lib/powerpc64le-linux-gnu/libakode.so.2.0.0 229N: 230N: This package provides an ELF binary that lacks the use of fortified libc 231N: functions. Either there are no potentially unfortified functions called 232N: by any routines, all unfortified calls have already been fully validated 233N: at compile-time, or the package was not built with the default Debian 234N: compiler flags defined by dpkg-buildflags. If built using 235N: dpkg-buildflags directly, be sure to import CPPFLAGS. 236N: 237N: NB: Due to false-positives, Lintian ignores some unprotected functions 238N: (e.g. memcpy). 239N: 240N: Refer to https://wiki.debian.org/Hardening and 241N: https://bugs.debian.org/673112 for details. 242N: 243N: Severity: info 244N: 245N: Check: binaries 246N: 247I: akode source: no-dh-sequencer 248N: 249N: This package does not use the dh sequencer in debian/rules. 250N: 251N: While maintainers may use a variety of build systems, this one is by far 252N: the most popular. 253N: 254N: Maintainers are strongly encouraged to use the dh sequencer in new 255N: packages and convert existing ones when appropriate. 256N: 257N: Severity: info 258N: 259N: Check: debian/rules/dh-sequencer 260N: 261I: libakode2: no-symbols-control-file usr/lib/powerpc64le-linux-gnu/libakode.so.2.0.0 262N: 263N: Although the package includes a shared library, the package does not 264N: have a symbols control file. 265N: 266N: dpkg can use symbols files in order to generate more accurate library 267N: dependencies for applications, based on the symbols from the library 268N: that are actually used by the application. 269N: 270N: Refer to the dpkg-gensymbols(1) manual page and 271N: https://wiki.debian.org/UsingSymbolsFiles for details. 272N: 273N: Severity: info 274N: 275N: Check: shared-libs 276N: 277I: akode source: testsuite-autopkgtest-missing 278N: 279N: This package does not declare a test suite. 280N: 281N: Having a test suite aids with automated quality assurance of the archive 282N: outside of your package. For example, if your package has a test suite 283N: it is possible to re-run that test suite when any of your package's 284N: dependencies have a new version and check whether that update causes 285N: problems for your package. 286N: 287N: In addition, since May 2018 these tests now influence migration from 288N: unstable to testing: 289N: 290N: https://lists.debian.org/debian-devel-announce/2018/05/msg00001.html 291N: 292N: Please add a debian/tests/control file to your package to declare a 293N: testsuite, but please make sure to only add autopkgtests if they provide 294N: meaningful coverage of your package. 295N: 296N: Refer to https://ci.debian.net/doc/ for details. 297N: 298N: Severity: info 299N: 300N: Check: testsuite 301N: 302I: libakode2: unused-override sharedobject-in-library-directory-missing-soname [usr/lib/*/libakode_alsa_sink.so] 303N: 304N: Lintian discovered an unused override entry in its database. Most likely 305N: it was used for a false-positive that has been fixed. However, some tags 306N: are only triggered in packages built on certain architectures. In this 307N: case, the override may need an architecture qualifier. 308N: 309N: Alternatively, the additional information provided by Lintian in the 310N: tag's output may changed since the override was last modified. 311N: 312N: If the override is unused, please remove it from the overrides file. 313N: 314N: Refer to Lintian User's Manual section 2.4.3 (Architecture specific 315N: overrides) for details. 316N: 317N: Severity: info 318N: 319N: Check: lintian 320N: 321I: libakode2: unused-override sharedobject-in-library-directory-missing-soname [usr/lib/*/libakode_mpc_decoder.so] 322I: libakode2: unused-override sharedobject-in-library-directory-missing-soname [usr/lib/*/libakode_oss_sink.so] 323I: libakode2: unused-override sharedobject-in-library-directory-missing-soname [usr/lib/*/libakode_src_resampler.so] 324I: libakode2: unused-override sharedobject-in-library-directory-missing-soname [usr/lib/*/libakode_xiph_decoder.so] 325I: libakode2-ffmpeg: unused-override sharedobject-in-library-directory-missing-soname [usr/lib/*/libakode_ffmpeg_decoder.so] 326I: libakode2-jack: unused-override sharedobject-in-library-directory-missing-soname [usr/lib/*/libakode_jack_sink.so] 327I: libakode2-mpeg: unused-override sharedobject-in-library-directory-missing-soname [usr/lib/*/libakode_mpeg_decoder.so] 328I: libakode2-pulse: unused-override sharedobject-in-library-directory-missing-soname [usr/lib/*/libakode_pulse_sink.so] 329I: akode-dbg: wrong-section-according-to-package-name akode-dbg => debug 330N: 331N: This package has a name suggesting that it belongs to a section other 332N: than the one it is currently categorized in. 333N: 334N: Severity: info 335N: 336N: Check: fields/section 337N: 338P: akode source: co-maintained-package-with-no-vcs-fields 339N: 340N: Based on the content of the maintainer and uploader fields this package 341N: is co-maintained but there are no Vcs-* fields. 342N: 343N: It is recommended that shared maintenance of packages are co-ordinated 344N: via a revision control system. 345N: 346N: Severity: pedantic 347N: 348N: Check: fields/vcs 349N: 350P: akode source: duplicate-in-relation-field in libakode-dev depends: libflac-dev (>= 1.1.1-3), libflac-dev 351N: 352N: The given field in the debian/control file contains relations that are 353N: either identical or imply each other. The less restrictive one can be 354N: removed. This is done automatically by dpkg-source and dpkg-gencontrol, 355N: so this does not affect the generated package. 356N: 357N: Severity: pedantic 358N: 359N: Check: debian/control 360N: 361P: akode source: file-contains-trailing-whitespace debian/changelog (line 112) 362N: 363N: This file appears to contain one or more lines with trailing whitespace 364N: characters. 365N: 366N: Whilst typically harmless and merely unsightly, they can often cause 367N: difficult-to-spot issues where tools interpret the whitespace characters 368N: literally as well as introduce unnecessary diff(1) noise. They are thus 369N: best avoided in their entirity. 370N: 371N: Whitespace at the end of lines may be removed with the following: 372N: 373N: $ sed -i -e 's@[[:space:]]*$@@g' debian/control debian/changelog 374N: 375N: If you use Emacs, you can also use "M-x wh-cl" (whitespace-cleanup). 376N: 377N: However, if you wish to only remove trailing spaces and leave trailing 378N: tabs (eg. for Makefiles), you can use the following code snippet: 379N: 380N: $ sed -i -e 's@[ ]*$@@g' debian/rules 381N: 382N: To remove empty lines from the end of a file, you can use: 383N: 384N: $ sed -i -e :a -e '/^\n*$/{$d;N;};/\n$/ba' debian/rules 385N: 386N: Severity: pedantic 387N: 388N: Check: cruft 389N: 390P: akode source: file-contains-trailing-whitespace debian/changelog (line 79) 391P: akode source: no-dep5-copyright 392N: 393N: This package does not use a machine-readable debian/copyright file. 394N: 395N: This format makes it easier to review licenses and can be easily parsed 396N: by Lintian. 397N: 398N: Refer to 399N: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ for 400N: details. 401N: 402N: Severity: pedantic 403N: 404N: Check: debian/copyright 405N: 406P: akode source: no-homepage-field 407N: 408N: This non-native package lacks a Homepage field. If the package has an 409N: upstream home page that contains useful information or resources for the 410N: end user, consider adding a Homepage control field to debian/control. 411N: 412N: Refer to Debian Policy Manual section 5.6.23 (Homepage) for details. 413N: 414N: Severity: pedantic 415N: 416N: Check: fields/homepage 417N: 418P: libakode-dev: old-style-config-script usr/bin/akode-config 419N: 420N: The following file is an old style config file, used to retrieve 421N: information about installed libraries in the system. It is typically 422N: used to compile and link against one or more libraries. 423N: 424N: Using this kind of system to pass compile file is obsolete and will 425N: likely introduce bugs in a multi-arch system. Particularly, this kind of 426N: script could only belong to a package that is not Multi-Arch. 427N: 428N: You should consider to move to pkg-config file and warn your user to not 429N: use this script, and open a bug upstream. 430N: 431N: You should also consider to implement this file as a compatibility 432N: wrapper over pkg-config. 433N: 434N: After fixing every reverse depends of your package and use pkg-config 435N: reverse depends makefile, you should consider to put this script, as a 436N: temporary convenience of your users, under 437N: /usr/lib/$DEB_HOST_MULTIARCH/$PACKAGE/bin where $DEB_HOST_MULTIARCH is 438N: the multi-arch triplet and $PACKAGE is the package name. You should also 439N: consider to add a NEWS.Debian entry. 440N: 441N: Refer to the pkg-config(1) manual page and 442N: http://sources.debian.net/src/imagemagick/8:6.8.9.9-6/debian/NEWS/ for 443N: details. 444N: 445N: Severity: pedantic 446N: 447N: Check: files/config-scripts 448N: 449P: akode source: package-uses-old-debhelper-compat-version 10 450N: 451N: The debhelper compatibility version used by this package is marked as 452N: not recommended by the debhelper developer. You may consider using a 453N: recommended compatibility version. 454N: 455N: The compatibility version can be set by specifying debhelper-compat (= 456N: 12) in your package's Build-Depends, by the legacy debian/compat file or 457N: even by setting and exporting DH_COMPAT in debian/rules. If it is not 458N: set in either place, debhelper defaults to the deprecated compatibility 459N: version 1. 460N: 461N: Refer to the debhelper(7) manual page for details. 462N: 463N: Severity: pedantic 464N: 465N: Check: debhelper 466N: 467P: akode source: rules-requires-root-missing 468N: 469N: The debian/control file is missing an explicit Rules-Requires-Root 470N: field. 471N: 472N: Traditionally, Debian packages have required root privileges for some 473N: debian/rules target requiring a split between build and binary targets. 474N: This makes the builds slower due to the increased amount of invocations 475N: as well as the overhead of fakeroot itself. 476N: 477N: Please specify (eg.) Rules-Requires-Root: no in the debian/control 478N: source stanza, but packagers should verify using diffoscope(1) that the 479N: binaries built with this field present are identical. 480N: 481N: Refer to /usr/share/doc/dpkg-dev/rootless-builds.txt.gz, Debian Policy 482N: Manual section 4.9.2 (debian/rules and Rules-Requires-Root), and Debian 483N: Policy Manual section 5.6.31 (Rules-Requires-Root) for details. 484N: 485N: Severity: pedantic 486N: 487N: Check: debian/control 488N: 489X: akode source: upstream-metadata-file-is-missing 490N: 491N: This source package is not Debian-native but it does not have a 492N: debian/upstream/metadata file. 493N: 494N: The Upstream MEtadata GAthered with YAml (UMEGAYA) project is an effort 495N: to collect meta-information about upstream projects from any source 496N: package. This file is in YAML format and it is used in to feed the data 497N: in the UltimateDebianDatabase. For example, it can contains the way the 498N: authors want their software be cited in publications and some 499N: bibliographic references about the software. 500N: 501N: Please add a debian/upstream/metadata file. 502N: 503N: Refer to https://dep-team.pages.debian.net/deps/dep12/ and 504N: https://wiki.debian.org/UpstreamMetadata for details. 505N: 506N: Severity: pedantic 507N: 508N: Check: debian/upstream/metadata 509N: 510N: This tag is experimental. Please file a bug report if the tag seems 511N: wrong. 512N: 513C: akode-dbg: control-tarball-compression-format xz 514N: 515N: This is the compressor format used for the control.tar tarball. 516N: 517N: Severity: classification 518N: 519N: Check: deb-format 520N: 521N: This tag is a classification. There is no issue in your package. 522N: 523C: libakode-dev: control-tarball-compression-format xz 524C: libakode2: control-tarball-compression-format xz 525C: libakode2-bin: control-tarball-compression-format xz 526C: libakode2-ffmpeg: control-tarball-compression-format xz 527C: libakode2-jack: control-tarball-compression-format xz 528C: libakode2-mpeg: control-tarball-compression-format xz 529C: libakode2-pulse: control-tarball-compression-format xz 530C: akode-dbg: data-tarball-compression-format xz 531N: 532N: This is the compressor format used for the data.tar tarball. 533N: 534N: Severity: classification 535N: 536N: Check: deb-format 537N: 538N: This tag is a classification. There is no issue in your package. 539N: 540C: libakode-dev: data-tarball-compression-format xz 541C: libakode2: data-tarball-compression-format xz 542C: libakode2-bin: data-tarball-compression-format xz 543C: libakode2-ffmpeg: data-tarball-compression-format xz 544C: libakode2-jack: data-tarball-compression-format xz 545C: libakode2-mpeg: data-tarball-compression-format xz 546C: libakode2-pulse: data-tarball-compression-format xz 547C: akode source: debhelper-compat-level 10 548N: 549N: This is the debhelper compat level used specified by this package. 550N: 551N: Severity: classification 552N: 553N: Check: debhelper 554N: 555N: This tag is a classification. There is no issue in your package. 556N: 557C: akode source: debian-build-system cdbs-with-debhelper.mk 558N: 559N: This is the build system that Lintian believes the package is using. 560N: 561N: Severity: classification 562N: 563N: Check: debhelper 564N: 565N: This tag is a classification. There is no issue in your package. 566N: 567C: akode-dbg: no-ctrl-scripts 568N: 569N: The package does not rely on any maintainer scripts (or other executable 570N: control files). 571N: 572N: Severity: classification 573N: 574N: Check: control-files 575N: 576N: This tag is a classification. There is no issue in your package. 577N: 578C: libakode-dev: no-ctrl-scripts 579C: libakode2: no-ctrl-scripts 580C: libakode2-bin: no-ctrl-scripts 581C: libakode2-ffmpeg: no-ctrl-scripts 582C: libakode2-jack: no-ctrl-scripts 583C: libakode2-mpeg: no-ctrl-scripts 584C: libakode2-pulse: no-ctrl-scripts 585C: akode source: package-is-co-maintained 3 586N: 587N: The package is co-maintained but not team-maintained according to the 588N: maintainer/uploaders fields in the debian/control file. 589N: 590N: Severity: classification 591N: 592N: Check: fields/vcs 593N: 594N: This tag is a classification. There is no issue in your package. 595N: 596C: akode-dbg: package-is-maintained-by-individual 597N: 598N: The package is maintained by an individual according to the 599N: maintainer/uploaders fields in the debian/control file. 600N: 601N: Severity: classification 602N: 603N: Check: fields/vcs 604N: 605N: This tag is a classification. There is no issue in your package. 606N: 607C: libakode-dev: package-is-maintained-by-individual 608C: libakode2: package-is-maintained-by-individual 609C: libakode2-bin: package-is-maintained-by-individual 610C: libakode2-ffmpeg: package-is-maintained-by-individual 611C: libakode2-jack: package-is-maintained-by-individual 612C: libakode2-mpeg: package-is-maintained-by-individual 613C: libakode2-pulse: package-is-maintained-by-individual 614C: akode source: patch-system quilt 615N: 616N: This package uses the specified patch system (eg. "quilt" or "dpatch"). 617N: 618N: Severity: classification 619N: 620N: Check: patch-systems 621N: 622N: This tag is a classification. There is no issue in your package. 623N: 624C: akode source: source-format 3.0 (quilt) 625N: 626N: This is the source format declared in the package. 627N: 628N: Severity: classification 629N: 630N: Check: debian/source-dir 631N: 632N: This tag is a classification. There is no issue in your package. 633N: 634C: akode source: standards-version 3.7.3 635N: 636N: The standards version of the package according to Standards-Version 637N: field in the debian/control file. 638N: 639N: Severity: classification 640N: 641N: Check: fields/standards-version 642N: 643N: This tag is a classification. There is no issue in your package. 644N: 645O: akode source: binary-nmu-debian-revision-in-source 4:14.1.6~pre2-0ubuntu20.04.0+3 646N: 647N: The version number of your source package ends in +b and a number or has 648N: a Debian revision containing three parts. These version numbers are used 649N: by binary NMUs and should not be used as the source version. (The +b 650N: form is the current standard; the three-part version number now 651N: obsolete.) 652N: 653N: Refer to Debian Developer's Reference section 5.10.2.1 (Recompilation or 654N: binary-only NMU) for details. 655N: 656N: Severity: warning 657N: 658N: Check: fields/version 659N: 660 661--------------------