diff -Nru lintian-2.93.0/bin/annotate-lintian-hints lintian-2.89.0ubuntu1/bin/annotate-lintian-hints --- lintian-2.93.0/bin/annotate-lintian-hints 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/bin/annotate-lintian-hints 1970-01-01 00:00:00.000000000 +0000 @@ -1,220 +0,0 @@ -#!/usr/bin/perl -# -# annotate-lintian-hints -- transform lintian tags into descriptive text -# -# Copyright © 1998 Christian Schwarz and Richard Braakman -# Copyright © 2013 Niels Thykier -# Copyright © 2017 Chris Lamb -# Copyright © 2020 Felix Lechner -# -# This program is free software. It is distributed under the terms of -# the GNU General Public License as published by the Free Software -# Foundation; either version 2 of the License, or (at your option) any -# later version. -# -# This program is distributed in the hope that it will be useful, -# but WITHOUT ANY WARRANTY; without even the implied warranty of -# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the -# GNU General Public License for more details. -# -# You should have received a copy of the GNU General Public License -# along with this program. If not, you can find it on the World Wide -# Web at http://www.gnu.org/copyleft/gpl.html, or write to the Free -# Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, -# MA 02110-1301, USA. - -use v5.20; -use warnings; -use utf8; - -# use Lintian modules that belong to this program -use FindBin; -use lib "$FindBin::RealBin/../lib"; - -# substituted during package build -my $LINTIAN_VERSION; - -use Cwd qw(getcwd realpath); -use File::BaseDir qw(config_home config_files data_home); -use File::Basename; -use Getopt::Long (); - -use Lintian::Output::EWI; -use Lintian::Profile; -use Lintian::Version qw(guess_version); - -use constant EMPTY => q{}; - -binmode(STDOUT, ':encoding(UTF-8)'); - -if (my $coverage_arg = $ENV{'LINTIAN_COVERAGE'}) { - my $p5opt = $ENV{'PERL5OPT'}//EMPTY; - $p5opt .= ' ' if $p5opt ne EMPTY; - $ENV{'PERL5OPT'} = "${p5opt} ${coverage_arg}"; -} - -$ENV{LINTIAN_BASE} = realpath("$FindBin::RealBin/..") - // die 'Cannot resolve LINTIAN_BASE'; - -my $annotate; -my @INCLUDE_DIRS; -my $profile_name; -my $user_dirs = 1; - -my %options = ( - 'annotate|a' => \$annotate, - 'help|h' => \&show_help, - 'include-dir=s' => \@INCLUDE_DIRS, - 'profile=s' => \$profile_name, - 'user-dirs!' => \$user_dirs, - 'version' => \&show_version, -); - -Getopt::Long::Configure('gnu_getopt'); -Getopt::Long::GetOptions(%options) - or die "error parsing options\n"; - -# only absolute paths -my @RESTRICTED_CONFIG_DIRS; - -if ($user_dirs) { - my $data_home; - my $legacy_user_data; - - $data_home = data_home('lintian') - if exists $ENV{'HOME'} || exists $ENV{'XDG_CONFIG_HOME'}; - - $legacy_user_data = "$ENV{HOME}/.lintian" - if exists $ENV{'HOME'}; - - if (defined($data_home) and $data_home !~ m@^/@) { - # Turn the path into an absolute one. Just in case - # someone sets a relative HOME dir. - my $cwd = getcwd(); - $data_home = "${cwd}/${data_home}"; - } - - @RESTRICTED_CONFIG_DIRS = grep { -d } - grep { length } ($data_home, $legacy_user_data, '/etc/lintian'); -} - -# only absolute paths -my @CONFIG_DIRS = grep { -d } - grep { length } map { realpath($_) } ($ENV{'LINTIAN_BASE'}, @INCLUDE_DIRS); - -my $profile = Lintian::Profile->new; -$profile->load($profile_name, \@CONFIG_DIRS, - { 'restricted-search-dirs' => \@RESTRICTED_CONFIG_DIRS }); - -my $output = Lintian::Output::EWI->new; - -# Matches something like: (1:2.0-3) [arch1 arch2] -# - captures the version and the architectures -my $verarchre = qr,(?: \s* \(( [^)]++ )\) \s* \[ ( [^]]++ ) \]),xo; - -# matches the full deal: -# 1 222 3333 4444444 5555 666 777 -# - T: pkg type (version) [arch]: tag [...] -# ^^^^^^^^^^^^^^^^^^^^^ -# Where the marked part(s) are optional values. The numbers above -# the example are the capture groups. -my $TAG_REGEX - = qr/([EWIXOPC]): (\S+)(?: (\S+)(?:$verarchre)?)?: (\S+)(?:\s+(.*))?/; - -my $type_re = qr/(?:binary|changes|source|udeb)/; - -my %already_displayed; - -# Otherwise, read input files or STDIN, watch for tags, and add -# descriptions whenever we see one, can, and haven't already -# explained that tag. Strip off color and HTML sequences. -for my $line () { - print $line; - chomp $line; - - next - if $line =~ /^\s*$/; - - $line =~ s/\e[\[\d;]*m//g; - $line =~ s///g; - $line =~ s,,,g; - - my $tag_name; - if ($annotate) { - - next - unless $line =~ /^(?: # start optional part - (?:\S+)? # Optionally starts with package name - (?: \s*+ \[[^\]]+?\])? # optionally followed by an [arch-list] (like in B-D) - (?: \s*+ $type_re)? # optionally followed by the type - :\s++)? # end optional part - ([\-\.a-zA-Z_0-9]+ (?:\s.+)?)$/x; # [extra] -> $1 - - my $tagdata = $1; - ($tag_name, undef) = split(/ /, $tagdata, 2); - - } else { - my @parts = split_tag($line); - next - unless @parts; - - $tag_name = $parts[5]; - } - - next - if $already_displayed{$tag_name}++; - - my $tag_info = $profile->get_taginfo($tag_name); - next - unless defined $tag_info; - - $output->tag_description($tag_info); -} - -exit; - -=item split_tag - -=cut - -sub split_tag { - my ($line) = @_; - - return - unless $line =~ /^${TAG_REGEX}$/; - - my $pkg_type = $3 // 'binary'; - - return ($1, $2, $pkg_type, $4, $5, $6, $7); -} - -sub show_version { - my $version = $LINTIAN_VERSION // guess_version($ENV{LINTIAN_BASE}); - - die 'Unable to determine the version automatically!?' - unless length $version; - - say "annotate-lintian-hints v$version"; - exit; -} - -sub show_help { - print <<"EOT"; -Usage: annotate-lintian-hints [log-file...] ... - annotate-lintian-hints --annotate [overrides ...] - -Options: - -a, --annotate display descriptions of tags in Lintian overrides - --profile X use vendor profile X to determine severities - --include-dir DIR check for Lintian data in DIR - --[no-]user-dirs whether to include profiles from user directories - --version show version info and exit -EOT - exit; -} - -# Local Variables: -# indent-tabs-mode: nil -# cperl-indent-level: 4 -# End: -# vim: syntax=perl sw=4 sts=4 sr et diff -Nru lintian-2.93.0/bin/build-test-packages lintian-2.89.0ubuntu1/bin/build-test-packages --- lintian-2.93.0/bin/build-test-packages 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/bin/build-test-packages 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,471 @@ +#!/usr/bin/perl + +# Copyright © 1998 Richard Braakman +# Copyright © 2008 Frank Lichtenheld +# Copyright © 2008, 2009 Russ Allbery +# Copyright © 2014 Niels Thykier +# Copyright © 2020 Felix Lechner +# +# This program is free software; you can redistribute it and/or modify +# it under the terms of the GNU General Public License as published by +# the Free Software Foundation; either version 2 of the License, or +# (at your option) any later version. +# +# This program is distributed in the hope that it will be useful, +# but WITHOUT ANY WARRANTY; without even the implied warranty of +# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the +# GNU General Public License for more details. +# +# You should have received a copy of the GNU General Public License +# along with this program. If not, you can find it on the World Wide +# Web at http://www.gnu.org/copyleft/gpl.html, or write to the Free +# Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, +# MA 02110-1301, USA. + +# The harness for Lintian's test suite. For detailed information on +# the test suite layout and naming conventions, see t/tests/README. +# For more information about running tests, see +# doc/tutorial/Lintian/Tutorial/TestSuite.pod + +use v5.20; +use warnings; +use utf8; +use autodie; + +# use Lintian modules that belong to this program +use FindBin; +use lib "$FindBin::RealBin/../lib"; + +use Capture::Tiny qw(capture_merged); +use Cwd qw(realpath); +use File::Copy; +use File::Find::Rule; +use File::stat; +use Getopt::Long; +use IO::Async::Function; +use IO::Async::Loop; +use List::Compare; +use Path::Tiny; +use Time::Duration; +use Time::Moment; +use Time::Piece; +use Try::Tiny; + +use Lintian::IO::Async qw(safe_qx); + +use Test::Lintian::Build qw(build_subject); +use Test::Lintian::ConfigFile qw(read_config); +use Test::Lintian::Helper + qw(rfc822date cache_dpkg_architecture_values get_latest_policy get_recommended_debhelper_version); +use Test::Lintian::Hooks qw(sed_hook sort_lines calibrate); +use Test::Lintian::Prepare qw(prepare); + +use constant SPACE => q{ }; +use constant SLASH => q{/}; +use constant INDENT => q{ }; +use constant NEWLINE => qq{\n}; +use constant TAB => qq{\t}; +use constant EMPTY => q{}; +use constant YES => q{yes}; +use constant NO => q{no}; + +my $processing_start = Time::Moment->from_string(gmtime->datetime . 'Z'); + +# whitelist the environment we permit to avoid things that mess up +# tests, like CFLAGS, DH_OPTIONS, DH_COMPAT, DEB_HOST_ARCH +# TODO: MAKEFLAGS - some of the tests don't cope too well with it +my %PRESERVE_ENV = map { $_ => 1 } qw( + NO_PKG_MANGLE + PATH + TMPDIR + CCACHE_DIR +); + +my @disallowed = grep { !exists $PRESERVE_ENV{$_} } keys %ENV; + +delete $ENV{$_} for @disallowed; + +# Standard pipeline installs ccache; causes write permission errors on Salsa +# https://salsa.debian.org/salsa-ci-team/pipeline/-/issues/164 +$ENV{CCACHE_DISABLE} = 1; + +# Ubuntu auto-builders run pkg-mangle which messes up test packages +$ENV{NO_PKG_MANGLE} //= 'true'; + +$ENV{LINTIAN_BASE} = realpath("$FindBin::RealBin/..") + // die 'Cannot resolve LINTIAN_BASE'; + +# options +my $debug; +my $dump_logs = 1; +my $force_rebuild; +my $numjobs = -1; +my $outpath; +my $verbose = 0; + +Getopt::Long::Configure('bundling'); +unless ( + Getopt::Long::GetOptions( + 'B|force-rebuild' => \$force_rebuild, + 'd|debug+' => \$debug, + 'j|jobs:i' => \$numjobs, + 'L|dump-logs!' => \$dump_logs, + 'v|verbose' => \$verbose, + 'w|work-dir:s' => \$outpath, + 'h|help' => sub {usage(); exit;}, + ) +) { + usage(); + die; +} + +# check number of arguments +die('Please use -h for usage information.') + if @ARGV > 1; + +# get arguments +my ($testset) = @ARGV; + +# default test set +$testset ||= 't'; + +# check test set directory +die "Cannot find testset directory $testset" + unless -d $testset; + +# make sure testset is an absolute path +$testset = path($testset)->absolute->stringify; + +# calculate a default test work directory if none given +$outpath ||= path($testset)->parent->stringify . '/debian/test-out'; + +# create test work directory unless it exists +path($outpath)->mkpath + unless -e $outpath; + +# make sure test work path is a directory +die "Test work directory $outpath is not a directory" + unless -d $outpath; + +# make sure outpath is absolute +$outpath = path($outpath)->relative->stringify; + +say EMPTY; + +# tie verbosity to debug +$verbose = 1 + $debug if $debug; + +# can be 0 without value ("-j"), and -1 if option was not specified at all +$numjobs = default_parallel() if $numjobs <= 0; +say "Running up to $numjobs tests concurrently" + if $numjobs > 1 && $verbose >= 2; + +$ENV{'DUMP_LOGS'} = $dump_logs//NO ? YES : NO; + +# Disable translation support in dpkg as it is a considerable +# unnecessary overhead. +$ENV{'DPKG_NLS'} = 0; + +my $helperpath = "$testset/../bin"; +if (-d $helperpath) { + my $helpers = path($helperpath)->absolute->stringify + // die("Cannot resolve $helperpath: $!"); + $ENV{'PATH'} = "$helpers:$ENV{'PATH'}"; +} + +# get architecture +cache_dpkg_architecture_values(); +say "Host architecture is $ENV{'DEB_HOST_ARCH'}."; + +# get latest policy version and date +($ENV{'POLICY_VERSION'}, $ENV{'POLICY_EPOCH'}) = get_latest_policy(); +say "Latest policy version is $ENV{'POLICY_VERSION'} from " + . rfc822date($ENV{'POLICY_EPOCH'}); + +# get current debhelper compat level; do not name DH_COMPAT; causes conflict +$ENV{'DEFAULT_DEBHELPER_COMPAT'} = get_recommended_debhelper_version(); +say +"Using compat level $ENV{'DEFAULT_DEBHELPER_COMPAT'} as a default for packages built with debhelper."; + +say EMPTY; + +# print environment +my @vars = sort keys %ENV; +say 'Environment:' if @vars; +for my $var (@vars) { say INDENT . "$var=$ENV{$var}" } + +say EMPTY; + +my $status = 0; + +# find spec paths +my @descfiles + = sort File::Find::Rule->file()->name('fill-values')->in("$testset/recipes"); + +my @specpaths = map { path($_)->parent->absolute->stringify } @descfiles; + +# prepare output directories +say 'Preparing the sources for '. scalar @specpaths. ' test packages.' + if @specpaths; + +my @prepqueue = map { path($_)->relative->stringify } @specpaths; + +# for filled templates +my $sourceroot = "$outpath/package-sources"; + +# for built test packages +my $buildroot = "$outpath/packages"; + +my @relative + = map { path($_)->parent->relative("$testset/recipes") } @specpaths; +my @sourcepaths = map {$_->absolute($sourceroot)->stringify } @relative; +my @buildpaths = map {$_->absolute($buildroot)->stringify } @relative; + +# remove obsolete package sources +my @foundsources = map { path($_)->parent->absolute->stringify; } + File::Find::Rule->file->name('fill-values')->in($sourceroot); +my $sourcelc = List::Compare->new('--unsorted', \@foundsources, \@sourcepaths); +my @obsoletesources = $sourcelc->get_Lonly; +path($_)->remove_tree for @obsoletesources; + +# remove obsolete built packages +my @foundpackages = map { path($_)->parent->absolute->stringify; } + File::Find::Rule->file->name('source-files.sha1sums')->in($buildroot); +my $packagelc= List::Compare->new('--unsorted', \@foundpackages, \@buildpaths); +my @obsoletepackages = $packagelc->get_Lonly; +path($_)->remove_tree for @obsoletepackages; + +# remove empty directories +for my $folder (@obsoletesources, @obsoletepackages) { + my $candidate = path($folder)->parent; + while ($candidate->exists && !$candidate->children) { + rmdir $candidate->stringify; + $candidate = $candidate->parent; + } +} + +$ENV{PERL_PATH_TINY_NO_FLOCK} =1; + +my $prepare = IO::Async::Function->new( + code => sub { + my ($specpath) = @_; + + # label process + $0 = "Lintian prepare test: $specpath"; + + # calculate destination + my $relative = path($specpath)->parent->relative("$testset/recipes"); + my $sourcepath = $relative->absolute($sourceroot)->stringify; + my $buildpath = $relative->absolute($buildroot)->relative->stringify; + + my $error; + + # capture output + my $log = capture_merged { + + try { + + # remove destination + path($sourcepath)->remove_tree + if -e $sourcepath; + + # prepare + prepare($specpath, $sourcepath, $testset, $force_rebuild); + + }catch { + # catch any error + $error = $_; + }; + }; + + # save log; + my $logfile = "$sourcepath.log"; + path($logfile)->spew_utf8($log) if $log; + + # print something if there was an error + die(($log // EMPTY) . "Preparation failed for $specpath: $error") + if $error; + + return $specpath; + }, + max_workers => $numjobs, + max_worker_calls => 1, +); + +my $loop = IO::Async::Loop->new; +$loop->add($prepare); + +$SIG{INT} = sub { $prepare->stop; die "Caught a sigint $!" }; +my @preptasks = map {$prepare->call(args => [$_])} sort @prepqueue; + +my $allprepared = Future->wait_all(@preptasks); + +$loop->await($allprepared); + +my @failedprep = $allprepared->failed_futures; +if (@failedprep) { + say EMPTY; + say 'Failed preparation tasks:'; + say NEWLINE . $_->failure for @failedprep; + exit 1; +} else { + say 'Package sources are ready.'; +} + +say EMPTY; + +my $build = IO::Async::Function->new( + code => sub { + my ($specpath, $position, $total) = @_; + + # set a predictable locale + $ENV{'LC_ALL'} = 'C'; + + # many tests create files via debian/rules + umask(022); + + # get destination + my $relative = path($specpath)->parent->relative("$testset/recipes"); + my $sourcepath = $relative->absolute($sourceroot)->relative->stringify; + my $buildpath = $relative->absolute($buildroot)->relative->stringify; + + my $sha1sums + = qx{cd $sourcepath; find . -type f -print0 | sort -z | xargs -0 sha1sum}; + + my $checksum_path = "$buildpath/source-files.sha1sums"; + if (-r $checksum_path) { + my $previous = path($checksum_path)->slurp; + + # only rebuild if needed + return + if $sha1sums eq $previous; + } + + $0 = "Lintian build test: $specpath [$position/$total]"; + say "Building in $buildpath [$position/$total]"; + + path($buildpath)->remove_tree + if -e $buildpath; + path($buildpath)->mkpath; + + # read dynamic file names + my $runfiles = "$sourcepath/files"; + my $files = read_config($runfiles); + + my $error; + + my $log = capture_merged { + + try { + # call runner + build_subject($sourcepath, $buildpath); + }catch { + # catch any error + $error = $_; + }; + }; + + # delete old runner log + my $betterlogpath = $buildpath . SLASH . $files->unfolded_value('Log'); + unlink $betterlogpath if -f $betterlogpath; + + # move the early log for directory preparation to position of runner log + my $earlylogpath = "$sourcepath.log"; + move($earlylogpath, $betterlogpath) if -f $earlylogpath; + + # append runner log to population log + path($betterlogpath)->append_utf8($log) if length $log; + + # add error if there was one + path($betterlogpath)->append_utf8($error) if length $error; + + path($checksum_path)->spew($sha1sums) + unless length $error; + + # print log and die on error + die(($log // EMPTY) . "Builder died for $buildpath: $error") + if length $error; + + return $specpath; + }, + max_workers => $numjobs, + max_worker_calls => 1, +); + +$loop->add($build); + +$SIG{INT} = sub { $build->stop; die "Caught a sigint $!" }; + +my $counter; +my @buildtasks= map {$build->call(args => [$_, ++$counter, scalar @specpaths])} + sort @specpaths; + +my $allbuilt = Future->wait_all(@buildtasks); + +$loop->await($allbuilt); + +my @failedbuilds = $allbuilt->failed_futures; +if (@failedbuilds) { + say EMPTY; + say 'Failed build tasks:'; + say NEWLINE . $_->failure for @failedbuilds; + exit 1; +} else { + say 'All test packages are up to date.'; +} + +say EMPTY; + +my $processing_end = Time::Moment->from_string(gmtime->datetime . 'Z'); +my $duration = duration($processing_start->delta_seconds($processing_end)); +say "Building the test packages took $duration."; + +say EMPTY; + +exit 0; + +# program is done + +=item default_parallel + +=cut + +# Return the default number of parallelization to be used +sub default_parallel { + # check cpuinfo for the number of cores... + my $cpus = safe_qx('nproc'); + if ($cpus =~ m/^\d+$/) { + # Running up to twice the number of cores usually gets the most out + # of the CPUs and disks but it might be too aggressive to be the + # default for -j. Only use +1 then. + return $cpus + 1; + } + + # No decent number of jobs? Just use 2 as a default + return 2; +} + +sub usage { + print <<"END"; +Usage: $0 [options] [-j []] [] + + -d Display additional debugging information + --dump-logs Print build log to STDOUT, if a build fails. + -j [] Run up to jobs in parallel. + If -j is passed without specifying , the number + of jobs started is +1. + -v Be more verbose + --help, -h Print this help and exit + + The optional 3rd parameter causes runtests to only run tests that match + the particular selection. This parameter can be a list of selectors: + what:[,] +END + return; +} + +# Local Variables: +# indent-tabs-mode: nil +# cperl-indent-level: 4 +# End: +# vim: syntax=perl sw=4 sts=4 sr et diff -Nru lintian-2.93.0/bin/build-test-packages-if-needed lintian-2.89.0ubuntu1/bin/build-test-packages-if-needed --- lintian-2.93.0/bin/build-test-packages-if-needed 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/bin/build-test-packages-if-needed 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,95 @@ +#!/bin/sh +# +# Copyright © 2019 Chris Lamb /dev/null | \ + grep MD5Sum: | cut -d' ' -f2 | cut -d_ -f1-2; + dpkg -l | awk '{ print $2 "_" $3 }' + ) | sort +} + +CHECKSUM="$(Checksum_input | sha1sum | cut -d ' ' -f1)" +CACHE_FILENAME="${CACHE_DIR}/${PIPELINE}-${CHECKSUM}.tar.xz" + +echo "Cache filename: ${CACHE_FILENAME}" + +# get some debug output +apt-cache --quiet policy +apt-cache --quiet policy debhelper + +# get prequisites early, otherwise tar fails for lack of xz-utils +env DEBIAN_FRONTEND=noninteractive apt-get --quiet --yes --option dir::cache::archives="${CACHE_DIR}" --option Debug::pkgProblemResolver=yes build-dep . + +mkdir -p .cache + +echo "I: Showing artifacts in .cache" >&2 +ls -al .cache >&2 + +echo "I: Looking for ${CACHE_FILENAME}" >&2 + +if [ -f "${CACHE_FILENAME}" ] +then + echo "I: Extracting ${CACHE_FILENAME}" >&2 + rm -rf debian/test-out/packages + tar xfJ "${CACHE_FILENAME}" +fi + +bin/build-test-packages + +echo "I: Removing obsolete test package artifacts from .cache" >&2 +find .cache \ + -maxdepth 1 \ + -type f \ + -regextype posix-egrep \ + -regex "^\.cache/${PIPELINE}-[[:xdigit:]]{40}\.tar\.xz\$" \ + -print \ + -delete + +echo "I: Removing old-style artifacts (no pipeline in name) from .cache" >&2 +find .cache \ + -maxdepth 1 \ + -type f \ + -regextype posix-egrep \ + -regex '^\.cache/[[:xdigit:]]{40}\.tar\.xz$' \ + -print \ + -delete + +echo "I: Creating ${CACHE_FILENAME}" >&2 +mkdir -p "$(dirname "${CACHE_FILENAME}")" +tar cfJ "${CACHE_FILENAME}" debian/test-out/packages + +cp -v "${CACHE_FILENAME}" test-packages.tar.xz + +echo "I: Showing artifacts in .cache" >&2 +ls -al .cache >&2 diff -Nru lintian-2.93.0/bin/explain-lintian-tags lintian-2.89.0ubuntu1/bin/explain-lintian-tags --- lintian-2.93.0/bin/explain-lintian-tags 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/bin/explain-lintian-tags 1970-01-01 00:00:00.000000000 +0000 @@ -1,183 +0,0 @@ -#!/usr/bin/perl -# -# explain-lintian-tags -- transform lintian tags into descriptive text -# -# Copyright © 1998 Christian Schwarz and Richard Braakman -# Copyright © 2013 Niels Thykier -# Copyright © 2017 Chris Lamb -# Copyright © 2020 Felix Lechner -# -# This program is free software. It is distributed under the terms of -# the GNU General Public License as published by the Free Software -# Foundation; either version 2 of the License, or (at your option) any -# later version. -# -# This program is distributed in the hope that it will be useful, -# but WITHOUT ANY WARRANTY; without even the implied warranty of -# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the -# GNU General Public License for more details. -# -# You should have received a copy of the GNU General Public License -# along with this program. If not, you can find it on the World Wide -# Web at http://www.gnu.org/copyleft/gpl.html, or write to the Free -# Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, -# MA 02110-1301, USA. - -use v5.20; -use warnings; -use utf8; - -# use Lintian modules that belong to this program -use FindBin; -use lib "$FindBin::RealBin/../lib"; - -# substituted during package build -my $LINTIAN_VERSION; - -use Cwd qw(getcwd realpath); -use File::BaseDir qw(config_home config_files data_home); -use File::Basename; -use Getopt::Long (); -use List::MoreUtils qw(any); - -use Lintian::Output::EWI; -use Lintian::Output::HTML; -use Lintian::Output::JSON; -use Lintian::Profile; -use Lintian::Version qw(guess_version); - -use constant EMPTY => q{}; -use constant SPACE => q{ }; -use constant COLON => q{:}; -use constant NEWLINE => qq{\n}; - -binmode(STDOUT, ':encoding(UTF-8)'); - -if (my $coverage_arg = $ENV{'LINTIAN_COVERAGE'}) { - my $p5opt = $ENV{'PERL5OPT'}//EMPTY; - $p5opt .= ' ' if $p5opt ne EMPTY; - $ENV{'PERL5OPT'} = "${p5opt} ${coverage_arg}"; -} - -$ENV{LINTIAN_BASE} = realpath("$FindBin::RealBin/..") - // die 'Cannot resolve LINTIAN_BASE'; - -my $format = 'ewi'; -my @INCLUDE_DIRS; -my $list_tags; -my $profile_name; -my $tags; -my $user_dirs = 1; - -my %options = ( - 'format|f=s' => \$format, - 'help|h' => \&show_help, - 'include-dir=s' => \@INCLUDE_DIRS, - 'list-tags|l' => \$list_tags, - 'profile=s' => \$profile_name, - 'tags|tag|t' => \$tags, - 'user-dirs!' => \$user_dirs, - 'version' => \&show_version, -); - -Getopt::Long::Configure('gnu_getopt'); -Getopt::Long::GetOptions(%options) - or die "error parsing options\n"; - -# only absolute paths -my @RESTRICTED_CONFIG_DIRS; - -if ($user_dirs) { - my $data_home; - my $legacy_user_data; - - $data_home = data_home('lintian') - if exists $ENV{'HOME'} || exists $ENV{'XDG_CONFIG_HOME'}; - - $legacy_user_data = "$ENV{HOME}/.lintian" - if exists $ENV{'HOME'}; - - if (defined($data_home) and $data_home !~ m@^/@) { - # Turn the path into an absolute one. Just in case - # someone sets a relative HOME dir. - my $cwd = getcwd(); - $data_home = "${cwd}/${data_home}"; - } - - @RESTRICTED_CONFIG_DIRS = grep { -d } - grep { length } ($data_home, $legacy_user_data, '/etc/lintian'); -} - -# only absolute paths -my @CONFIG_DIRS = grep { -d } - grep { length } map { realpath($_) } ($ENV{'LINTIAN_BASE'}, @INCLUDE_DIRS); - -my $profile = Lintian::Profile->new; -$profile->load($profile_name, \@CONFIG_DIRS, - { 'restricted-search-dirs' => \@RESTRICTED_CONFIG_DIRS }); - -my $output; - -$format = lc $format; -if ($format eq 'ewi') { - $output = Lintian::Output::EWI->new; - -} elsif ($format eq 'json') { - $output = Lintian::Output::JSON->new; - -} elsif ($format eq 'html') { - $output = Lintian::Output::HTML->new; - -} else { - die "Invalid output format $format\n"; -} - -if ($list_tags) { - say for sort { lc($a->name) cmp lc($b->name) } $profile->enabled_tags; - exit; -} - -# show all tags when none were specified -my @selected = @ARGV; -@selected = $profile->enabled_tags - unless @selected; - -my @available = grep { defined} map { $profile->get_taginfo($_) } @selected; - -my @sorted = sort { lc($a->name) cmp lc($b->name) } @available; - -$output->tag_description($_) for @sorted; - -exit any { !defined $profile->get_taginfo($_) } @selected; - -sub show_version { - my $version = $LINTIAN_VERSION // guess_version($ENV{LINTIAN_BASE}); - - die 'Unable to determine the version automatically!?' - unless length $version; - - say "annotate-lintian-hints v$version"; - exit; -} - -sub show_help { - print <<"EOT"; -Usage: explain-lintian-tags [log-file...] ... - explain-lintian-tags [--tags] tag ... - -Options: - -l, --list-tags list all tags Lintian knows about - -t, --tag, --tags display tag descriptions - --profile X use vendor profile X to determine severities - --include-dir DIR check for Lintian data in DIR - --[no-]user-dirs whether to include profiles from user directories - --version show version info and exit -EOT - exit; -} - -# Local Variables: -# indent-tabs-mode: nil -# cperl-indent-level: 4 -# End: -# vim: syntax=perl sw=4 sts=4 sr et diff -Nru lintian-2.93.0/bin/gitlab-ci-pipeline lintian-2.89.0ubuntu1/bin/gitlab-ci-pipeline --- lintian-2.93.0/bin/gitlab-ci-pipeline 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/bin/gitlab-ci-pipeline 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,96 @@ +#!/bin/bash +# ^^^ bash provides 'time', and is also the standard in .gitlab-ci.yml +# +# Copyright © 2019 Chris Lamb +# Copyright © 2020 Felix Lechner +# +# This program is free software; you can redistribute it and/or modify +# it under the terms of the GNU General Public License as published by +# the Free Software Foundation; either version 2 of the License, or +# (at your option) any later version. +# +# This program is distributed in the hope that it will be useful, +# but WITHOUT ANY WARRANTY; without even the implied warranty of +# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the +# GNU General Public License for more details. +# +# You should have received a copy of the GNU General Public License +# along with this program. If not, you can find it on the World Wide +# Web at http://www.gnu.org/copyleft/gpl.html, or write to the Free +# Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, +# MA 02110-1301, USA. + +set -eux + +CACHE_DIR="${1}" +PIPELINE="${2}" + +Checksum_input () { + # Local files that, if changed, should result in a rebuild of the test + # packages. + find \ + bin/build-test-packages \ + lib/Test/ \ + -type f -print0 | sort -z | xargs -0 sha1sum + + # Rebuild if any build-dependency or installed package changes + ( + apt-get --quiet --yes --print-uris build-dep . 2>/dev/null | \ + grep MD5Sum: | cut -d' ' -f2 | cut -d_ -f1-2; + dpkg -l | awk '{ print $2 "_" $3 }' + ) | sort +} + +# for apt and friends +export DEBIAN_FRONTEND="noninteractive" + +# update package info +apt-get --quiet update + +if [ "${PIPELINE}" == "stable" ] ; then + + # get the release code name + source /etc/os-release + + # ignore status when backports repo is not set up, i.e. unstable or new releases + apt-get --quiet --yes --target-release "${VERSION_CODENAME}-backports" --option dir::cache::archives="${CACHE_DIR}" install debhelper || true + +fi + +# get prequisites early, otherwise tar fails for lack of xz-utils +apt-get --quiet --yes --option dir::cache::archives="${CACHE_DIR}" --option Debug::pkgProblemResolver=yes build-dep . + +mkdir -p "${CACHE_DIR}" +echo "I: Showing artifacts in ${CACHE_DIR}" >&2 +ls -al "${CACHE_DIR}" >&2 + +CHECKSUM="$(Checksum_input | sha1sum | cut -d ' ' -f1)" +CACHE_FILENAME="${CACHE_DIR}/${PIPELINE}-${CHECKSUM}.tar.xz" +echo "I: Looking for ${CACHE_FILENAME}" >&2 + +if [ -f "${CACHE_FILENAME}" ] +then + echo "I: Extracting ${CACHE_FILENAME}" >&2 + rm -rf debian/test-out/packages + tar xfJ "${CACHE_FILENAME}" +fi + +time bin/build-test-packages + +echo "I: Removing obsolete test package artifacts for ${PIPELINE} pipeline from ${CACHE_DIR}" >&2 +find "${CACHE_DIR}" \ + -maxdepth 1 \ + -type f \ + -regextype posix-egrep \ + -regex "^${CACHE_DIR}/${PIPELINE}-[[:xdigit:]]{40}\.tar\.xz\$" \ + -print \ + -delete + +echo "I: Creating ${CACHE_FILENAME}" >&2 +mkdir -p "$(dirname "${CACHE_FILENAME}")" +tar cfJ "${CACHE_FILENAME}" debian/test-out/packages + +echo "I: Showing artifacts in ${CACHE_DIR}" >&2 +ls -al "${CACHE_DIR}" >&2 + +time bin/runtests diff -Nru lintian-2.93.0/bin/lintian lintian-2.89.0ubuntu1/bin/lintian --- lintian-2.93.0/bin/lintian 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/bin/lintian 2020-08-10 09:59:45.000000000 +0000 @@ -39,20 +39,20 @@ use Carp qw(croak verbose); use Config::Tiny; use File::BaseDir qw(config_files data_home); +use File::Basename; use Getopt::Long (); use List::Compare; use List::MoreUtils qw(any none first_value); use Path::Tiny; use POSIX qw(:sys_wait_h); -use Unicode::UTF8 qw(valid_utf8 decode_utf8); -use Lintian::Deb822::Parser qw(parse_dpkg_control_string); +use Lintian::Data; use Lintian::Inspect::Changelog; use Lintian::IPC::Run3 qw(safe_qx); -use Lintian::Output::EWI; +use Lintian::Output::Standard; use Lintian::Pool; use Lintian::Profile; -use Lintian::Version qw(guess_version); +use Lintian::Util qw(version_from_changelog); use constant EMPTY => q{}; use constant SPACE => q{ }; @@ -62,12 +62,14 @@ use constant NEWLINE => qq{\n}; # only in GNOME; need original environment -my $interactive = -t STDIN && (-t *STDOUT || !(-f *STDOUT || -c *STDOUT)); +my $interactive = -t STDIN && (-t STDOUT || !(-f STDOUT || -c STDOUT)); my $hyperlinks_capable = $interactive && qx{env | fgrep -i gnome}; # only do once; layers are additive -binmode(*STDOUT, ':encoding(UTF-8)'); -binmode(*STDERR, ':encoding(UTF-8)'); +binmode(STDOUT, ':encoding(UTF-8)'); +binmode(STDERR, ':encoding(UTF-8)'); + +$0 = join(SPACE, $0, @ARGV); # Globally ignore SIGPIPE. We'd rather deal with error returns from write # than randomly delivered signals. @@ -104,8 +106,6 @@ // die 'Cannot resolve LINTIAN_BASE'; $ENV{LINTIAN_VERSION} = $LINTIAN_VERSION // guess_version($ENV{LINTIAN_BASE}); -die 'Unable to determine the version automatically!?' - unless length $ENV{LINTIAN_VERSION}; if (my $coverage_arg = $ENV{LINTIAN_COVERAGE}) { my $p5opt = $ENV{PERL5OPT} // EMPTY; @@ -129,7 +129,7 @@ exp-output:s fail-on=s@ ftp-master-rejects|F - help|h + help|h:s hide-overrides hyperlinks=s ignore-lintian-env @@ -167,9 +167,6 @@ Getopt::Long::GetOptions(\%command_line, @getoptions) or die "error parsing options\n"; -my @basenames = map { path($_)->basename } @ARGV; -$0 = join(SPACE, "$FindBin::RealBin/$FindBin::RealScript", @basenames); - if (exists $command_line{'version'}) { say "Lintian v$ENV{LINTIAN_VERSION}"; exit; @@ -180,7 +177,7 @@ exit; } -show_help() +show_help(undef, $command_line{help}) if exists $command_line{help}; $command_line{'show-overrides'} = 0 @@ -218,7 +215,7 @@ } $LINTIAN_CFG ||= first_value { length $_ && -f $_ } - ($xdg_config_file, $dot_config_file, '/etc/lintianrc'); + ($xdg_config_file, $dot_config_file); # make path absolute for use elsewhere $xdg_data_home = getcwd() . SLASH . $xdg_data_home @@ -350,13 +347,13 @@ my @display_level; push(@display_level,['=', '>=', 'warning']) - if $selected{'default-display-level'}; + if exists $selected{'default-display-level'}; push(@display_level, ['+', '>=', 'info']) - if $selected{'display-info'}; + if exists $selected{'display-info'}; push(@display_level, ['+', '=', 'pedantic']) - if $selected{'pedantic'}; + if exists $selected{'pedantic'}; sub display_classificationtags { push(@display_level, ['+', '=', 'classification']); @@ -437,7 +434,7 @@ $ENV{LINTIAN_HELPER_DIRS} = join(COLON, @HELPER_DIRS); my @CLOSE_AT_END; -my $OUTPUT = Lintian::Output::EWI->new; +my $OUTPUT = Lintian::Output::Standard->new; my $received_signal; my $exit_code = 0; my $STATUS_FD; @@ -445,7 +442,9 @@ # root permissions? # check if effective UID is 0 if ($> == 0 && !$selected{'allow-root'}) { - warn "warning: running with root privileges is not recommended!\n"; + print STDERR join(q{ }, + 'warning: the authors of lintian do not', + "recommend running it with root privileges!\n"); } if ($selected{'ignore-lintian-env'}) { @@ -454,10 +453,10 @@ # option --all and packages specified at the same time? if ($selected{'packages-from-file'} && $#ARGV+1 > 0) { - warn -"warning: option --packages-from-file cannot be mixed with package parameters!\n"; - warn "(will ignore --packages-from-file option)\n"; - + print STDERR join(q{ }, + 'warning: option --packages-from-file', + "cannot be mixed with package parameters!\n"); + print STDERR "(will ignore --packages-from-file option)\n"; delete($selected{'packages-from-file'}); } @@ -494,12 +493,24 @@ my %output = map { split(/=/) } split(/,/, ($selected{'exp-output'} // EMPTY)); for (keys %output) { if ($_ eq 'format') { - if ($output{$_} eq 'html') { + if ($output{$_} eq 'colons') { + require Lintian::Output::ColonSeparated; + $OUTPUT= Lintian::Output::ColonSeparated->new; + } elsif ($output{$_} eq 'letterqualifier') { + require Lintian::Output::LetterQualifier; + $OUTPUT= Lintian::Output::LetterQualifier->new; + } elsif ($output{$_} eq 'html') { require Lintian::Output::HTML; $OUTPUT = Lintian::Output::HTML->new; + } elsif ($output{$_} eq 'xml') { + require Lintian::Output::XML; + $OUTPUT = Lintian::Output::XML->new; } elsif ($output{$_} eq 'json') { require Lintian::Output::JSON; $OUTPUT = Lintian::Output::JSON->new; + } elsif ($output{$_} eq 'fullewi') { + require Lintian::Output::FullEWI; + $OUTPUT = Lintian::Output::FullEWI->new; } elsif ($output{$_} eq 'universal') { require Lintian::Output::Universal; $OUTPUT = Lintian::Output::Universal->new; @@ -523,8 +534,8 @@ if @not_yet; $ENV{$_} = $config{$_} for @not_yet; -die "The color value must be one of auto, always, or never.\n" - unless (any { $selected{color} eq $_ } qw(auto always never)); +die "The color value must be one of never, always, auto or html.\n" + unless (any { $selected{color} eq $_ } qw(never always auto html)); if ($selected{color} eq 'never') { $selected{hyperlinks} //= 'off'; @@ -537,7 +548,7 @@ $selected{verbose} = -1 if $selected{quiet}; -if ($selected{verbose} || !-t *STDOUT) { +if ($selected{verbose} || !-t STDOUT) { $selected{'tag-display-limit'} //= 0; } else { $selected{'tag-display-limit'} //= 4; @@ -549,14 +560,10 @@ $SIG{__DIE__} = sub { Carp::confess(@_) }; } -$OUTPUT->verbosity($selected{verbose}); +$OUTPUT->verbosity_level($selected{verbose}); $OUTPUT->debug($selected{debug}); -$OUTPUT->color(1) - if $selected{color} eq 'always' - || ($selected{color} eq 'auto' - && -t *STDOUT); - +$OUTPUT->color($selected{color}); $OUTPUT->tty_hyperlinks($hyperlinks_capable&& $selected{hyperlinks} eq 'on'); $OUTPUT->tag_display_limit($selected{'tag-display-limit'}); $OUTPUT->showdescription($selected{info}); @@ -590,9 +597,7 @@ push @ARGV, $file; $ok = 1; } - - show_help() - unless $ok; + show_help() unless $ok; } if ($selected{debug}) { @@ -621,6 +626,8 @@ { 'restricted-search-dirs' => \@RESTRICTED_CONFIG_DIRS }); $OUTPUT->v_msg('Using profile ' . $PROFILE->name . '.'); +Lintian::Data->set_vendor($PROFILE); + # if tags are listed explicitly (--tags) then show them even if # they are pedantic/experimental etc. However, for --check-part # people explicitly have to pass the relevant options. @@ -707,9 +714,9 @@ # in ubuntu, automatic dbgsym packages end with .ddeb die "bad package file name $path (neither .deb, .udeb, .ddeb, .changes, .dsc or .buildinfo file)\n" - unless $path =~ /\.(?:[u|d]?deb|dsc|changes|buildinfo)$/; + unless $path =~ m/\.(?:[u|d]?deb|dsc|changes|buildinfo)$/; - my $absolute = abs_path($path); + my $absolute = Cwd::abs_path($path); die "Cannot resolve $path: $!" unless $absolute; @@ -717,39 +724,12 @@ # create a new group my $group = Lintian::Group->new; $group->pooldir($pool->basedir); - - my $processable = $group->add_processable_from_file($absolute); - - my $parent = path($absolute)->parent->stringify; - - my @files; - - # pull in any additional files - @files = keys %{$processable->files} - if $processable->can('files'); - - for my $basename (@files) { - - # ignore traversal attempts - next - if $basename =~ m{/}; - - die "$parent/$basename does not exist, exiting\n" - unless -f "$parent/$basename"; - - # only care about some files; ddeb is ubuntu dbgsym - next - unless $basename =~ /\.(?:u|d)?deb$/ - || $basename =~ /\.dsc$/ - || $basename =~ /\.buildinfo$/; - - $group->add_processable_from_file("$parent/$basename"); - } + $group->init_from_file($absolute); $pool->add_group($group); }; if ($@) { - warn "Skipping $path: $@\n"; + print STDERR "Skipping $path: $@"; $exit_code = 1; } } @@ -766,6 +746,36 @@ exit $exit_code; +sub guess_version { + my ($lintian_base) = @_; + + my $guess = version_from_git($lintian_base); + $guess ||= version_from_changelog($lintian_base); + + return $guess + if length $guess; + + die 'Unable to determine the version automatically!?'; +} + +=item version_from_git + +=cut + +sub version_from_git { + my ($source_path) = @_; + + my $git_path = "$source_path/.git"; + + return EMPTY + unless -d $git_path; + + my $guess = safe_qx('git', "--git-dir=$git_path", 'describe'); + chomp $guess; + + return ($guess // EMPTY); +} + =item parse_boolean (STR) Attempt to parse STR as a boolean and return its value. @@ -823,12 +833,12 @@ if (not $last) { my @errors = @{$changelog->errors}; if (@errors) { - warn "Cannot parse debian/changelog due to errors:\n"; + print STDERR "Cannot parse debian/changelog due to errors:\n"; for my $error (@errors) { - warn "$error->[2] (line $error->[1])\n"; + print STDERR "$error->[2] (line $error->[1])\n"; } } else { - warn "debian/changelog does not have any data?\n"; + print STDERR "debian/changelog does not have any data?\n"; } exit 1; } @@ -837,9 +847,10 @@ unless (defined $version && defined $source) { $version //= ''; $source //= ''; - warn "Cannot determine source and version from debian/changelog:\n"; - warn "Source: $source\n"; - warn "Version: $source\n"; + print STDERR + "Cannot determine source and version from debian/changelog:\n"; + print STDERR "Source: $source\n"; + print STDERR "Version: $source\n"; exit 1; } # remove the epoch @@ -868,14 +879,12 @@ return $changes if -f $changes; } } - - warn"Cannot find changes file for ${source}/${version}, tried:\n"; - - warn " ${source}_${version}_${_}.changes\n" for @archs; - - warn " in the following dirs:\n"; - warn ' ', join("\n ", @dirs), "\n"; - + print STDERR "Cannot find changes file for ${source}/${version}, tried:\n"; + for my $arch (@archs) { + print STDERR " ${source}_${version}_${arch}.changes\n"; + } + print STDERR " in the following dirs:\n"; + print STDERR ' ', join("\n ", @dirs), "\n"; exit 0; } @@ -978,7 +987,7 @@ if (my $err = $@) { # Don't use L::Output here as it might be (partly) cleaned # up. - warn "warning: closing ${filename} failed: $err\n"; + print STDERR "warning: closing ${filename} failed: $err\n"; } } } @@ -1003,9 +1012,9 @@ } sub show_help { + my (undef, $value) = @_; say "Lintian v$ENV{LINTIAN_VERSION}"; - print <<"EOT-EOT-EOT"; Syntax: lintian [action] [options] [--] [packages] ... Actions: @@ -1016,7 +1025,7 @@ --tags-from-file X like --tags, but read list from file -X X, --dont-check-part X don\'t check certain aspects General options: - -h, --help display this help text + -h, --help display short help text --print-version print unadorned version number and exit -q, --quiet suppress all informational messages -v, --verbose verbose messages @@ -1040,19 +1049,52 @@ --hide-overrides do not output tags that have been overridden (default) --suppress-tags T,... don\'t show the specified tags --suppress-tags-from-file X don\'t show the tags listed in file X +EOT-EOT-EOT + if ($value eq 'extended' || $value eq 'all') { + # Not a special option per se, but most people will probably + # not need it + print <<"EOT-EOT-EOT"; --tag-display-limit X Specify "tag per package" display limit --no-tag-display-limit Disable "tag per package" display limit (equivalent to --tag-display-limit=0) +EOT-EOT-EOT + } + + print <<"EOT-EOT-EOT"; Configuration options: --cfg CONFIGFILE read CONFIGFILE for configuration --no-cfg do not read any config files --ignore-lintian-env ignore LINTIAN_* env variables - --include-dir DIR include checks, libraries (etc.) from DIR + --include-dir DIR include checks, libraries (etc.) from DIR (*) -j X, --jobs X limit the number of parallel unpacking jobs to X - --[no-]user-dirs whether to use files from user directories + --[no-]user-dirs whether to use files from user directories (*) +EOT-EOT-EOT -Some options were omitted. Please check the manual page for the complete list. + if ($value eq 'extended' || $value eq 'all') { + print <<"EOT-EOT-EOT"; +Developer/Special usage options: + --allow-root suppress lintian\'s warning when run as root + -d, --debug turn Lintian\'s debug messages on (repeatable) + --keep-lab keep lab after run + --packages-from-file X process the packages in a file (if "-" use stdin) + --perf-debug turn on performance debugging + --perf-output X send performance logging to file (or fd w. \&X) + --status-log X send status logging to file (or fd w. \&X) [internal use only] EOT-EOT-EOT + } + + print <<"EOT-EOT-EOT"; + +Options marked with (*) should be the first options if given at all. +EOT-EOT-EOT + + unless ($value eq 'extended' || $value eq 'all') { + print <<"EOT-EOT-EOT"; + +Note that some options have been omitted, use "--help=extended" to see them +all. +EOT-EOT-EOT + } exit; } diff -Nru lintian-2.93.0/bin/lintian-info lintian-2.89.0ubuntu1/bin/lintian-info --- lintian-2.93.0/bin/lintian-info 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/bin/lintian-info 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,290 @@ +#!/usr/bin/perl +# +# lintian-info -- transform lintian tags into descriptive text +# +# Copyright © 1998 Christian Schwarz and Richard Braakman +# Copyright © 2013 Niels Thykier +# Copyright © 2017 Chris Lamb +# Copyright © 2020 Felix Lechner +# +# This program is free software. It is distributed under the terms of +# the GNU General Public License as published by the Free Software +# Foundation; either version 2 of the License, or (at your option) any +# later version. +# +# This program is distributed in the hope that it will be useful, +# but WITHOUT ANY WARRANTY; without even the implied warranty of +# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the +# GNU General Public License for more details. +# +# You should have received a copy of the GNU General Public License +# along with this program. If not, you can find it on the World Wide +# Web at http://www.gnu.org/copyleft/gpl.html, or write to the Free +# Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, +# MA 02110-1301, USA. + +use v5.20; +use warnings; +use utf8; + +# use Lintian modules that belong to this program +use FindBin; +use lib "$FindBin::RealBin/../lib"; + +# substituted during package build +my $LINTIAN_VERSION; + +use Cwd qw(getcwd realpath); +use File::BaseDir qw(config_home config_files data_home); +use File::Basename; +use Getopt::Long (); +use List::MoreUtils qw(all); +use Path::Tiny; + +use Lintian::Data; +use Lintian::IPC::Run3 qw(safe_qx); +use Lintian::Profile; +use Lintian::Util qw(version_from_changelog); + +use constant EMPTY => q{}; +use constant SPACE => q{ }; +use constant COLON => q{:}; + +binmode(STDOUT, ':encoding(UTF-8)'); + +if (my $coverage_arg = $ENV{'LINTIAN_COVERAGE'}) { + my $p5opt = $ENV{'PERL5OPT'}//EMPTY; + $p5opt .= ' ' if $p5opt ne EMPTY; + $ENV{'PERL5OPT'} = "${p5opt} ${coverage_arg}"; +} + +$ENV{LINTIAN_BASE} = realpath("$FindBin::RealBin/..") + // die 'Cannot resolve LINTIAN_BASE'; + +my $annotate; +my @INCLUDE_DIRS; +my $list_tags; +my $profile_name; +my $tags; +my $user_dirs = 1; + +my %options = ( + 'annotate|a' => \$annotate, + 'help|h' => \&show_help, + 'include-dir=s' => \@INCLUDE_DIRS, + 'list-tags|l' => \$list_tags, + 'profile=s' => \$profile_name, + 'tags|tag|t' => \$tags, + 'user-dirs!' => \$user_dirs, + 'version' => \&show_version, +); + +Getopt::Long::Configure('gnu_getopt'); +Getopt::Long::GetOptions(%options) + or die "error parsing options\n"; + +# only absolute paths +my @RESTRICTED_CONFIG_DIRS; + +if ($user_dirs) { + my $data_home; + my $legacy_user_data; + + $data_home = data_home('lintian') + if exists $ENV{'HOME'} || exists $ENV{'XDG_CONFIG_HOME'}; + + $legacy_user_data = "$ENV{HOME}/.lintian" + if exists $ENV{'HOME'}; + + if (defined($data_home) and $data_home !~ m@^/@) { + # Turn the path into an absolute one. Just in case + # someone sets a relative HOME dir. + my $cwd = getcwd(); + $data_home = "${cwd}/${data_home}"; + } + + @RESTRICTED_CONFIG_DIRS = grep { -d } + grep { length } ($data_home, $legacy_user_data, '/etc/lintian'); +} + +# only absolute paths +my @CONFIG_DIRS = grep { -d } + grep { length } map { realpath($_) } ($ENV{'LINTIAN_BASE'}, @INCLUDE_DIRS); + +my $profile = Lintian::Profile->new; +$profile->load($profile_name, \@CONFIG_DIRS, + { 'restricted-search-dirs' => \@RESTRICTED_CONFIG_DIRS }); + +Lintian::Data->set_vendor($profile); + +if ($list_tags) { + say for sort $profile->enabled_tags; + exit; +} + +# If tag mode was specified, read the arguments as tags and display the +# descriptions for each one. (We don't currently display the severity, +# although that would be nice.) +if ($tags) { + my %taginfos = map { $_ => $profile->get_taginfo($_) } @ARGV; + + for my $name (keys %taginfos) { + + my $code = 'N'; + my $description = 'N: Unknown tag.'; + + my $info = $taginfos{$name}; + if (defined $info) { + $code = $info->code; + $description = $info->description('text', 'N: '); + chomp $description; + } + + say $code . COLON . SPACE . $name; + say 'N:'; + say $description; + say 'N:'; + } + + exit !all { defined } values %taginfos; +} + +# Matches something like: (1:2.0-3) [arch1 arch2] +# - captures the version and the architectures +my $verarchre = qr,(?: \s* \(( [^)]++ )\) \s* \[ ( [^]]++ ) \]),xo; + +# matches the full deal: +# 1 222 3333 4444444 5555 666 777 +# - T: pkg type (version) [arch]: tag [...] +# ^^^^^^^^^^^^^^^^^^^^^ +# Where the marked part(s) are optional values. The numbers above +# the example are the capture groups. +my $TAG_REGEX + = qr/([EWIXOPC]): (\S+)(?: (\S+)(?:$verarchre)?)?: (\S+)(?:\s+(.*))?/; + +my $type_re = qr/(?:binary|changes|source|udeb)/; + +my %already_displayed; + +# Otherwise, read input files or STDIN, watch for tags, and add +# descriptions whenever we see one, can, and haven't already +# explained that tag. Strip off color and HTML sequences. +while (<>) { + print; + chomp; + + next + if /^\s*$/; + + s/\e[\[\d;]*m//g; + s///g; + s,,,g; + + my $tag; + if ($annotate) { + + next + unless m/^(?: # start optional part + (?:\S+)? # Optionally starts with package name + (?: \s*+ \[[^\]]+?\])? # optionally followed by an [arch-list] (like in B-D) + (?: \s*+ $type_re)? # optionally followed by the type + :\s++)? # end optional part + ([\-\.a-zA-Z_0-9]+ (?:\s.+)?)$/x; # [extra] -> $1 + my $tagdata = $1; + ($tag, undef) = split / /, $tagdata, 2; + + } else { + my @parts = split_tag($_); + next unless @parts; + $tag = $parts[5]; + } + + next + if $already_displayed{$tag}++; + + my $info = $profile->get_taginfo($tag); + next + unless $info; + + print "N:\n"; + print $info->description('text', 'N: '); + print "N:\n"; +} + +exit; + +sub show_version { + my $version = $LINTIAN_VERSION // guess_version($ENV{LINTIAN_BASE}); + + say "lintian-info v$version"; + exit; +} + +sub guess_version { + my ($lintian_base) = @_; + + my $guess = version_from_git($lintian_base); + $guess ||= version_from_changelog($lintian_base); + + return $guess + if length $guess; + + die 'Unable to determine the version automatically!?'; +} + +=item version_from_git + +=cut + +sub version_from_git { + my ($source_path) = @_; + + my $git_path = "$source_path/.git"; + + return EMPTY + unless -d $git_path; + + my $guess = safe_qx('git', "--git-dir=$git_path", 'describe'); + chomp $guess; + + return ($guess // EMPTY); +} + +=item split_tag + +=cut + +sub split_tag { + my ($tag_input) = @_; + + return + unless $tag_input =~ /^${TAG_REGEX}$/; + + my $pkg_type = $3 // 'binary'; + + return ($1, $2, $pkg_type, $4, $5, $6, $7); +} + +sub show_help { + print <<"EOT"; +Usage: lintian-info [log-file...] ... + lintian-info --annotate [overrides ...] + lintian-info --tags tag ... + +Options: + -a, --annotate display descriptions of tags in Lintian overrides + -l, --list-tags list all tags Lintian knows about + -t, --tag, --tags display tag descriptions + --profile X use vendor profile X to determine severities + --include-dir DIR check for Lintian data in DIR + --[no-]user-dirs whether to include profiles from user directories + --version show version info and exit +EOT + exit; +} + +# Local Variables: +# indent-tabs-mode: nil +# cperl-indent-level: 4 +# End: +# vim: syntax=perl sw=4 sts=4 sr et diff -Nru lintian-2.93.0/bin/runtests lintian-2.89.0ubuntu1/bin/runtests --- lintian-2.93.0/bin/runtests 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/bin/runtests 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,670 @@ +#!/usr/bin/perl + +# Copyright © 1998 Richard Braakman +# Copyright © 2008 Frank Lichtenheld +# Copyright © 2008, 2009 Russ Allbery +# Copyright © 2014 Niels Thykier +# Copyright © 2020 Felix Lechner +# +# This program is free software; you can redistribute it and/or modify +# it under the terms of the GNU General Public License as published by +# the Free Software Foundation; either version 2 of the License, or +# (at your option) any later version. +# +# This program is distributed in the hope that it will be useful, +# but WITHOUT ANY WARRANTY; without even the implied warranty of +# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the +# GNU General Public License for more details. +# +# You should have received a copy of the GNU General Public License +# along with this program. If not, you can find it on the World Wide +# Web at http://www.gnu.org/copyleft/gpl.html, or write to the Free +# Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, +# MA 02110-1301, USA. + +# The harness for Lintian's test suite. For detailed information on +# the test suite layout and naming conventions, see t/tests/README. +# For more information about running tests, see +# doc/tutorial/Lintian/Tutorial/TestSuite.pod +# + +use v5.20; +use warnings; +use utf8; +use autodie; + +# use Lintian modules that belong to this program +use FindBin; +use lib "$FindBin::RealBin/../lib"; + +use Capture::Tiny qw(capture_merged); +use Cwd qw(realpath); +use File::Basename; +use File::Path qw(make_path); +use File::Spec::Functions qw(abs2rel rel2abs splitpath splitdir); +use File::stat; +use Getopt::Long; +use List::MoreUtils qw(any uniq); +use List::Util qw(max); +use IO::Async::Function; +use IO::Async::Loop; +use Path::Tiny; +use TAP::Formatter::Console; +use TAP::Formatter::File; +use TAP::Harness; +use TAP::Parser::Aggregator; +use Term::ANSIColor; +use Time::Duration; +use Time::Moment; +use Time::Piece; +use Try::Tiny; + +use Lintian::IO::Async qw(safe_qx); + +use Test::Lintian::ConfigFile qw(read_config); +use Test::Lintian::Filter + qw(find_selected_scripts find_selected_lintian_testpaths); +use Test::Lintian::Helper + qw(rfc822date cache_dpkg_architecture_values get_latest_policy get_recommended_debhelper_version); +use Test::Lintian::Prepare qw(filleval); +use Test::Lintian::Run qw(logged_runner); +use Test::ScriptAge qw(perl_modification_epoch our_modification_epoch); + +use constant SPACE => q{ }; +use constant INDENT => q{ }; +use constant NEWLINE => qq{\n}; +use constant EMPTY => q{}; +use constant YES => q{yes}; +use constant NO => q{no}; + +# display output immediately +STDOUT->autoflush; + +my $processing_start = Time::Moment->from_string(gmtime->datetime . 'Z'); + +# whitelist the environment we permit to avoid things that mess up +# tests, like CFLAGS, DH_OPTIONS, DH_COMPAT, DEB_HOST_ARCH +my %PRESERVE_ENV = map { $_ => 1 } qw( + LINTIAN_TEST_INSTALLED + PATH + TMPDIR +); + +my @disallowed = grep { !exists $PRESERVE_ENV{$_} } keys %ENV; + +delete $ENV{$_} for @disallowed; + +if (($ENV{LINTIAN_TEST_INSTALLED} // 'no') eq 'yes') { + + $ENV{LINTIAN_UNDER_TEST} = realpath('/usr/bin/lintian') + // die 'Lintian is not installed'; + +} else { + $ENV{LINTIAN_UNDER_TEST} = $FindBin::RealBin . '/lintian'; +} + +$ENV{LINTIAN_BASE} + = realpath(dirname(dirname($ENV{LINTIAN_UNDER_TEST}))) + // die 'Cannot resolve LINTIAN_BASE'; + +# options +my $coverage; +my $debug; +my $dump_logs = 1; +my $numjobs = -1; +my $keep_going; +my $onlyrun; +my $outpath; +my $unattended; +my $verbose = 0; + +Getopt::Long::Configure('bundling'); +unless ( + Getopt::Long::GetOptions( + 'c|coverage:s' => \$coverage, + 'd|debug+' => \$debug, + 'j|jobs:i' => \$numjobs, + 'k|keep-going' => \$keep_going, + 'L|dump-logs!' => \$dump_logs, + 'o|onlyrun:s' => \$onlyrun, + 'u|unattended' => \$unattended, + 'v|verbose' => \$verbose, + 'w|work-dir:s' => \$outpath, + 'h|help' => sub {usage(); exit;}, + ) +) { + usage(); + die; +} + +# check number of arguments +die('Please use -h for usage information.') + if @ARGV > 1; + +# get arguments +my ($testset) = @ARGV; + +# default test set +$testset ||= 't'; + +# check test set directory +die "Cannot find testset directory $testset" + unless -d $testset; + +# make sure testset is an absolute path +$testset = rel2abs($testset); + +# calculate a default test work directory if none given +$outpath ||= dirname($testset) . '/debian/test-out'; + +# create test work directory unless it exists +make_path($outpath) + unless -e $outpath; + +# make sure test work path is a directory +die "Test work directory $outpath is not a directory" + unless -d $outpath; + +# make sure outpath is absolute +$outpath = rel2abs($outpath); + +my $ACTIVE_JOBS = 0; + +my $output_is_tty = -t STDOUT; + +# get lintian modification date +my @lintianparts = ( + 'checks', 'collection', 'commands', 'data', + 'bin', 'profiles', 'vendors', 'lib/Lintian' +); +my @lintianfiles + = map { File::Find::Rule->file->in("$ENV{'LINTIAN_BASE'}/$_") }@lintianparts; +push(@lintianfiles, Cwd::realpath($ENV{'LINTIAN_UNDER_TEST'})); +$ENV{'LINTIAN_EPOCH'} + = max(map { -e $_ ? stat($_)->mtime : time } @lintianfiles); +say 'Lintian modified on '. rfc822date($ENV{'LINTIAN_EPOCH'}); + +my $error; +my $string = capture_merged { + my @command = ($ENV{'LINTIAN_UNDER_TEST'}, '--version'); + system(@command) == 0 + or $error = "system @command failed: $?"; +}; +die $string . $error + if length $error; + +chomp $string; +my ($version) = $string =~ qr/^\S+\s+v(.+)$/; +die 'Cannot get Lintian version' unless length $version; +say "Version under test is $version."; + +say EMPTY; + +# set environment for coverage +if (defined $coverage) { + # Only collect coverage for stuff that D::NYTProf and + # Test::Pod::Coverage cannot do for us. This makes cover use less + # RAM in the other end. + my @criteria = qw(statement branch condition path subroutine); + my $args= '-MDevel::Cover=-silent,1,+ignore,^(.*/)?t/scripts/.+'; + $args .= ',+ignore,/usr/bin/.*,+ignore,(.*/)?Dpkg'; + $args .= ',-coverage,' . join(',-coverage,', @criteria); + $args .= ',' . $coverage if $coverage ne ''; + $ENV{'LINTIAN_COVERAGE'} = $args; + + $ENV{'HARNESS_PERL_SWITCHES'} //= EMPTY; + $ENV{'HARNESS_PERL_SWITCHES'} .= SPACE . $args; +} + +# Devel::Cover + one cover_db + multiple processes is a recipe +# for corruptions. Force $numjobs to 1 if we are running under +# coverage. +$numjobs = 1 if exists $ENV{'LINTIAN_COVERAGE'}; + +# tie verbosity to debug +$verbose = 1 + $debug if $debug; + +# can be 0 without value ("-j"), and -1 if option was not specified at all +$numjobs = default_parallel() if $numjobs <= 0; +say "Running up to $numjobs tests concurrently" + if $numjobs > 1 && $verbose >= 2; + +$ENV{'DUMP_LOGS'} = $dump_logs//NO ? YES : NO; + +# Disable translation support in dpkg as it is a considerable +# unnecessary overhead. +$ENV{'DPKG_NLS'} = 0; + +my $helperpath = "$testset/../bin"; +if (-d $helperpath) { + my $helpers = rel2abs($helperpath)// die("Cannot resolve $helperpath: $!"); + $ENV{'PATH'} = "$helpers:$ENV{'PATH'}"; +} + +# get architecture +cache_dpkg_architecture_values(); +say "Host architecture is $ENV{'DEB_HOST_ARCH'}."; + +# get latest policy version and date +($ENV{'POLICY_VERSION'}, $ENV{'POLICY_EPOCH'}) = get_latest_policy(); +say "Latest policy version is $ENV{'POLICY_VERSION'} from " + . rfc822date($ENV{'POLICY_EPOCH'}); + +# get current debhelper compat level; do not name DH_COMPAT; causes conflict +$ENV{'DEFAULT_DEBHELPER_COMPAT'} = get_recommended_debhelper_version(); +say +"Using compat level $ENV{'DEFAULT_DEBHELPER_COMPAT'} as a default for packages built with debhelper."; + +# get harness date, including templates, skeletons and whitelists +my @harnessparts + = ('bin', 't/runners', 't/templates', 't/skeletons', 't/whitelists'); +my @harnessfiles + = map { File::Find::Rule->file->in("$ENV{'LINTIAN_BASE'}/$_") }@harnessparts; +my $harness_files_epoch + = max(map { -e $_ ? stat($_)->mtime : time } @harnessfiles); +$ENV{'HARNESS_EPOCH'} + = max(our_modification_epoch, perl_modification_epoch, $harness_files_epoch); +say 'Harness modified on '. rfc822date($ENV{'HARNESS_EPOCH'}); + +say EMPTY; + +# print environment +my @vars = sort keys %ENV; +say 'Environment:' if @vars; +for my $var (@vars) { say INDENT . "$var=$ENV{$var}" } + +say EMPTY; + +my $status = 0; + +my $formatter = TAP::Formatter::File->new({ + errors => 1, + jobs => $numjobs, +}); +$formatter = TAP::Formatter::Console->new({ + errors => 1, + jobs => $numjobs, + color => 1, + }) if -t STDOUT; + +my $harness = TAP::Harness->new({ + formatter => $formatter, + jobs => $numjobs, + lib => ["$ENV{'LINTIAN_BASE'}/lib"], +}); + +my $aggregator = TAP::Parser::Aggregator->new; +$aggregator->start; + +my @runscripts; +my $scriptpath = "$testset/scripts"; + +# add selected scripts +push(@runscripts, find_selected_scripts($scriptpath, $onlyrun)); + +# always add internal harness tests +my @requiredscripts; +@requiredscripts + = sort File::Find::Rule->file()->name('*.t')->in("$scriptpath/harness") + unless length $onlyrun; +push(@runscripts, @requiredscripts); + +# remove any duplicates +@runscripts = uniq @runscripts; + +# make all paths relative +@runscripts = map { abs2rel($_) } @runscripts; + +say 'Running selected and required Perl test scripts.'; +say EMPTY; + +# run scripts through harness +$harness->aggregate_tests($aggregator, sort @runscripts); + +unless (!@runscripts || $aggregator->all_passed || $keep_going) { + $aggregator->stop; + $formatter->summary($aggregator); + exit 1; +} + +say EMPTY; + +# find test paths +my @testpaths = find_selected_lintian_testpaths($testset, $onlyrun); + +# for built test packages +my $buildroot = "$outpath/packages"; + +# for built test packages +my $evalroot = "$outpath/eval"; + +# prepare test +my $filleval = IO::Async::Function->new( + code => sub { + my ($specpath) = @_; + + # label process + $0 = "Lintian prepare test: $specpath"; + + # calculate destination + my $relative = path($specpath)->relative("$testset/recipes"); + my $buildpath = $relative->absolute($buildroot)->stringify; + my $evalpath = $relative->absolute($evalroot)->relative->stringify; + + my $error; + + # capture output + my $log = capture_merged { + + try { + + # remove destination + path($evalpath)->remove_tree + if -e $evalpath; + + path($evalpath)->mkpath; + + # prepare + filleval("$specpath/eval", $evalpath, $testset); + + my $traversal = Cwd::realpath("$buildpath/subject"); + + if (length $traversal) { + die "Cannot link to subject in $buildpath" + if system("cd $evalpath; ln -s $traversal subject"); + } + + }catch { + # catch any error + $error = $_; + }; + }; + + # save log; + my $logfile = "$evalpath/log"; + path($logfile)->spew_utf8($log) if $log; + + # print something if there was an error + die(($log // EMPTY) . "Preparation failed for $specpath: $error") + if $error; + + return $specpath; + }, + max_workers => $numjobs, + max_worker_calls => 1, +); + +my $loop = IO::Async::Loop->new; +$loop->add($filleval); + +$SIG{INT} = sub { $filleval->stop; die "Caught a sigint $!" }; +my @filltasks = map {$filleval->call(args => [$_])} sort @testpaths; + +my $allfilled = Future->wait_all(@filltasks); + +$loop->await($allfilled); + +# remap paths from testset to outpath to get work directories +my @workpaths + = map { rel2abs(abs2rel($_, "$testset/recipes"), "$outpath/eval") } + @testpaths; + +# if ($platforms ne 'any') { +# my @wildcards = split(SPACE, $platforms); +# my @matches= map { +# qx{dpkg-architecture -a $ENV{'DEB_HOST_ARCH'} -i $_; echo -n \$?} +# } @wildcards; +# unless (any { $_ == 0 } @matches) { +# say 'Architecture mismatch'; +# return; +# } +# } + +# make all paths relative to current directory +@workpaths = map { path($_)->relative } @workpaths; + +# add the scripts in generated tests to be run +my @workscripts; +for my $path (@workpaths) { + + my @runners = File::Find::Rule->file->name('*.t')->in($path); + + die "No runner in $path" + unless scalar @runners; + die "More than one runner in $path" + if scalar @runners > 1; + + push(@workscripts, @runners); +} + +# run scripts through harness +$harness->aggregate_tests($aggregator, sort @workscripts); + +$aggregator->stop; +$formatter->summary($aggregator); + +say EMPTY; + +$status = 1 + unless $aggregator->all_passed; + +if (-t STDOUT && !$unattended) { + my @failed = $aggregator->failed; + say 'Offering to re-calibrate the tags expected in tests that failed.' + if @failed; + + my $accept_all; + + for my $scriptpath (@failed) { + my $workpath = dirname($scriptpath); + + my $descpath = "$workpath/desc"; + my $testcase = read_config($descpath); + + my $relative = abs2rel($workpath, $evalroot); + my $testpath = abs2rel(rel2abs($relative, "$testset/recipes")); + + say EMPTY; + say 'Failed test: ' . colored($testpath, 'bold white on_blue'); + + my $match_strategy = $testcase->unfolded_value('Match-Strategy'); + + if ($match_strategy eq 'tags') { + + my $diffpath = "$workpath/tagdiff"; + next + unless -r $diffpath; + + my $diff = path($diffpath)->slurp; + print $diff; + + } elsif ($match_strategy eq 'literal') { + + my $actualpath = "$workpath/literal.actual.parsed"; + next + unless -r $actualpath; + my @command + = ('diff', '-uN', "$testpath/eval/literal", $actualpath); + say join(SPACE, @command); + system(@command); + + } else { + say +"Do not know how to fix tests using matching strategy $match_strategy."; + next; + } + + unless ($accept_all) { + + print +'>>> Fix test (y), accept all (a), do not fix (n), quit (q/default)? '; + + my $decision = ; + chomp $decision; + + last + if $decision eq 'q' || $decision eq EMPTY; + + next + unless $decision eq 'y' || $decision eq 'a'; + + $accept_all = 1 + if $decision eq 'a'; + } + + if ($match_strategy eq 'tags') { + + # create tags if needed; helps when writing new tests + my $tagspath = "$testpath/eval/tags"; + path($tagspath)->touch + unless -e $tagspath; + + my $diffpath = "$workpath/tagdiff"; + next + unless -r $diffpath; + + my @adjustargs = ($diffpath, $tagspath); + unshift(@adjustargs, '-i') + unless $accept_all; + + die "Cannot run tagadjust for $testpath" + if system('tagadjust', @adjustargs); + + # also copy the new tags to workpath; no need to rebuild + die "Cannot copy updated tags to $workpath" + if system('cp', $tagspath, "$workpath/tags"); + + } elsif ($match_strategy eq 'literal') { + + my $actualpath = "$workpath/literal.actual.parsed"; + next + unless -r $actualpath; + + die "Cannot copy to accept literal output for $testpath" + if system('cp', $actualpath, "$testpath/eval/literal"); + + } + } + + say NEWLINE . 'Accepted all remaining tag changes.' + if $accept_all; + +} else { + my @crashed = $aggregator->parse_errors; + + say 'Showing full logs for tests with parse errors.' + if @crashed; + + for my $absolutepath (@crashed) { + my $scriptpath = abs2rel($absolutepath); + my $workpath = dirname($scriptpath); + + say EMPTY; + say "Log for test $scriptpath:"; + + my $logpath = "$workpath/log"; + my $log = path($logpath)->slurp; + print $log; + } +} + +# give a hint if not enough tests were run +unless (scalar @runscripts - scalar @requiredscripts + scalar @workscripts + || $onlyrun eq 'minimal:') { + quick_hint($onlyrun); + exit 1; +} + +my $processing_end = Time::Moment->from_string(gmtime->datetime . 'Z'); +my $duration = duration($processing_start->delta_seconds($processing_end)); +say "The test suite ran for $duration."; + +say EMPTY; + +exit $status; + +# program is done + +=item default_parallel + +=cut + +# Return the default number of parallelization to be used +sub default_parallel { + # check cpuinfo for the number of cores... + my $cpus = safe_qx('nproc'); + if ($cpus =~ m/^\d+$/) { + # Running up to twice the number of cores usually gets the most out + # of the CPUs and disks but it might be too aggressive to be the + # default for -j. Only use +1 then. + return $cpus + 1; + } + + # No decent number of jobs? Just use 2 as a default + return 2; +} + +sub usage { + print <<"END"; +Usage: $0 [options] [-j []] + + --onlyrun Select only some tests for a quick check + --coverage Run Lintian under Devel::Cover (Warning: painfully slow) + -d Display additional debugging information + --dump-logs Print build log to STDOUT, if a build fails. + -j [] Run up to jobs in parallel. + If -j is passed without specifying , the number + of jobs started is +1. + -k Do not stop after one failed test + -v Be more verbose + --help, -h Print this help and exit + + The option --onlyrun causes runtests to only run tests that match + the particular selection. This parameter can be a list of selectors: + what:[,] + + * test: + - Run the named test. Please note that testnames may not be + unique, so it may run more than one test. + * script:( || ) + - Run the named code quality script or all in the named directory. + E.g. "01-critic" will run all tests in "t/scripts/01-critic/". + * check: + - Run all tests related to the given check. + * suite: + - Run all tests in the named suite. + * tag: + - Run any test that lists in "Test-For" or + "Test-Against". + +Test artifacts are cached in --work-dir [default: debian/test-out] and +will generally be reused to save time. To recreate the test packages, +run 'bin/build-test-packages'. +END + return; +} + +sub quick_hint { + my ($selection) = @_; + print <<"END"; + +No tests were selected by your filter: + + $selection + +To select your tests, please use an appropriate argument with a +selector like: + + 'suite:', 'test:', 'check:', 'tag:', or 'script:' + +You can also use 'minimal:', which runs only the tests that cannot +be turned off, such as the internal tests for the harness. +END + return; +} + +# Local Variables: +# indent-tabs-mode: nil +# cperl-indent-level: 4 +# End: +# vim: syntax=perl sw=4 sts=4 sr et diff -Nru lintian-2.93.0/bin/spellintian lintian-2.89.0ubuntu1/bin/spellintian --- lintian-2.93.0/bin/spellintian 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/bin/spellintian 2020-08-10 09:59:45.000000000 +0000 @@ -39,10 +39,11 @@ use Getopt::Long (); use Path::Tiny; +use Lintian::Data; use Lintian::IPC::Run3 qw(safe_qx); use Lintian::Spelling qw(check_spelling check_spelling_picky); use Lintian::Profile; -use Lintian::Version qw(guess_version); +use Lintian::Util qw(version_from_changelog); use constant EMPTY => q{}; use constant COLON => q{:}; @@ -116,6 +117,8 @@ $profile->load(undef, \@CONFIG_DIRS, { 'restricted-search-dirs' => \@RESTRICTED_CONFIG_DIRS }); +Lintian::Data->set_vendor($profile); + my $exit_code = 0; unless (@ARGV) { @@ -138,12 +141,39 @@ exit $exit_code; +sub guess_version { + my ($lintian_base) = @_; + + my $guess = version_from_git($lintian_base); + $guess ||= version_from_changelog($lintian_base); + + return $guess + if length $guess; + + die 'Unable to determine the version automatically!?'; +} + +=item version_from_git + +=cut + +sub version_from_git { + my ($source_path) = @_; + + my $git_path = "$source_path/.git"; + + return EMPTY + unless -d $git_path; + + my $guess = safe_qx('git', "--git-dir=$git_path", 'describe'); + chomp $guess; + + return ($guess // EMPTY); +} + sub show_version { my $version = $LINTIAN_VERSION // guess_version($ENV{LINTIAN_BASE}); - die 'Unable to determine the version automatically!?' - unless length $version; - say "spellintian v$version"; exit; } diff -Nru lintian-2.93.0/bin/split-desc lintian-2.89.0ubuntu1/bin/split-desc --- lintian-2.93.0/bin/split-desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/bin/split-desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,108 @@ +#!/usr/bin/perl + +use v5.20; +use warnings; +use utf8; + +use List::MoreUtils qw(any); +use Path::Tiny; + +use constant EMPTY => q{}; + +die 'Please specify exactly one argument' + unless @ARGV == 1; + +my $path = $ARGV[0]; + +#print "Splitting $path\n"; + +my $contents = path($path)->slurp; + +#print $contents; + +my @testlabels = qw( + Check + Default-Lintian-Options + Lintian-Command-Line + Match-Strategy + Options + Output-Format + Profile + References + Test-Against + Test-Architectures + Test-Conflicts + Test-Depends + Todo +); + +my $build = EMPTY; +my $eval = EMPTY; +my $comments = EMPTY; + +while ($contents =~ s/\n(\#[^\n]*\n)/\n/) { + $comments .= $1; +} + +while ($contents =~ s/^([^:]+\:[^\n]*\n(?: [^\n]+\n)*)//) { + + my $field = $1; + + my ($label) = ($field =~ /^([^:]+)\:/); + # print "Found $label\n"; + + if ($label eq 'Testname') { + $eval .= $field; + $build .= $field; + next; + } + + if (any {/^$label$/} @testlabels) { + $eval .= $field; + + } else { + $build .= $field; + } +} + +die 'Unknown data at the end' + if length $contents; + +path($path)->remove; + +my $parent = path($path)->parent->stringify; + +my $temppath = $parent . ' (new)'; +path($parent)->move($temppath); +path($parent)->mkpath; + +my $buildpath = path($parent)->child('build-spec')->stringify; +my $evalpath = path($parent)->child('eval')->stringify; + +path($parent)->mkpath; +path($temppath)->move($buildpath); +path($evalpath)->mkpath; + +my $fillvalues = path($buildpath)->child('fill-values')->stringify; +my $desc = path($evalpath)->child('desc'); + +path($fillvalues)->spew($build); +path($desc)->spew($eval); + +path($fillvalues)->append($comments); +path($desc)->append($comments); + +my @move + = qw(tags literal skip post-test test-calibration tag-list suppress lintian-include-dir); + +for my $transfer (@move) { + + my $sourcepath = path($buildpath)->child($transfer)->stringify; + my $destpath = path($evalpath)->child($transfer)->stringify; + + path($sourcepath)->move($destpath) + if -e $sourcepath; +} + +#print "Build:\n$build\n"; +#print "Eval:\n$eval\n"; diff -Nru lintian-2.93.0/bin/tagadjust lintian-2.89.0ubuntu1/bin/tagadjust --- lintian-2.93.0/bin/tagadjust 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/bin/tagadjust 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,152 @@ +#!/usr/bin/perl + +# Copyright © 2019 Felix Lechner +# +# This program is free software; you can redistribute it and/or modify +# it under the terms of the GNU General Public License as published by +# the Free Software Foundation; either version 2 of the License, or +# (at your option) any later version. +# +# This program is distributed in the hope that it will be useful, +# but WITHOUT ANY WARRANTY; without even the implied warranty of +# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the +# GNU General Public License for more details. +# +# You should have received a copy of the GNU General Public License +# along with this program. If not, you can find it on the World Wide +# Web at http://www.gnu.org/copyleft/gpl.html, or write to the Free +# Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, +# MA 02110-1301, USA. + +# The harness for Lintian's test suite. For detailed information on +# the test suite layout and naming conventions, see t/tests/README. +# For more information about running tests, see +# doc/tutorial/Lintian/Tutorial/TestSuite.pod +# + +use v5.20; +use warnings; +use utf8; +use autodie; + +# use Lintian modules that belong to this program +use FindBin; +use lib "$FindBin::RealBin/../lib"; + +use Cwd; +use Capture::Tiny qw(capture_merged); +use Getopt::Long; +use List::Util qw(all); +use Path::Tiny; +use Term::ANSIColor; + +use Test::Lintian::Output::Universal qw(parse_line order); + +use constant EMPTY => q{}; +use constant SPACE => q{ }; +use constant COLON => q{:}; +use constant LPARENS => q{(}; +use constant RPARENS => q{)}; +use constant NEWLINE => qq{\n}; + +# options +my $interactive; + +Getopt::Long::Configure; +unless ( + Getopt::Long::GetOptions( + 'i|interactive' => \$interactive, + 'help|h' => sub {usage(); exit;}, + ) +) { + usage(); + die; +} + +# check arguments and options +die "Please use -h for usage information.\n" + if scalar @ARGV != 2; + +# get arguments +my ($diffpath, $tagspath) = @ARGV; + +my @difflines = path($diffpath)->lines_utf8; +chomp @difflines; + +my @tagslines = path($tagspath)->lines_utf8; +chomp @tagslines; + +my $changed; + +foreach my $line (@difflines) { + my ($sign, $stripped) = $line =~ qr/^([+-])(.*)$/; + + die "$diffpath is not a tagdiff file" + unless length $sign && defined $stripped; + + if ($interactive) { + + my $command; + my $color; + + if ($sign eq '+') { + $command = 'Add'; + $color = 'bold bright_white on_green'; + } else { + $command = 'Remove'; + $color = 'bold bright_white on_red'; + } + + my $colored = $stripped; + $colored = colored($stripped, $color) + if -t STDOUT; + print "$colored - $command (y/n/q)? "; + + my $decision = ; + chomp $decision; + exit if $decision eq 'q'; + next unless $decision eq 'y'; + } + + if ($sign eq '+') { + # say "Adding: $stripped"; + push(@tagslines, $stripped); + } else { + # say "Removing: $stripped"; + # remove the first match only + my $found = 0; + @tagslines = grep {$_ ne $stripped || $found++} @tagslines; + } + + $changed = 1; +} + +exit unless $changed; + +# also sort output into preferred order +my $joined = EMPTY; +$joined .= $_ . NEWLINE + for reverse sort { order($a) cmp order($b) } @tagslines; +path($tagspath)->spew_utf8($joined); + +exit; + +sub usage { + print <<"END"; +Usage: $0 -i + + --interactive, -i Apply interactively + + Applies to so that the new file represents the + changes. Please use tagdiff to create the file with the changes. + + The tags are then sorted in the order preferred for universal tags. +END + return; +} + +# Local Variables: +# indent-tabs-mode: nil +# cperl-indent-level: 4 +# End: +# vim: syntax=perl sw=4 sts=4 sr et diff -Nru lintian-2.93.0/bin/tagdiff lintian-2.89.0ubuntu1/bin/tagdiff --- lintian-2.93.0/bin/tagdiff 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/bin/tagdiff 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,122 @@ +#!/usr/bin/perl + +# Copyright © 2019 Felix Lechner +# +# This program is free software; you can redistribute it and/or modify +# it under the terms of the GNU General Public License as published by +# the Free Software Foundation; either version 2 of the License, or +# (at your option) any later version. +# +# This program is distributed in the hope that it will be useful, +# but WITHOUT ANY WARRANTY; without even the implied warranty of +# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the +# GNU General Public License for more details. +# +# You should have received a copy of the GNU General Public License +# along with this program. If not, you can find it on the World Wide +# Web at http://www.gnu.org/copyleft/gpl.html, or write to the Free +# Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, +# MA 02110-1301, USA. + +# The harness for Lintian's test suite. For detailed information on +# the test suite layout and naming conventions, see t/tests/README. +# For more information about running tests, see +# doc/tutorial/Lintian/Tutorial/TestSuite.pod +# + +use v5.20; +use warnings; +use utf8; +use autodie; + +# use Lintian modules that belong to this program +use FindBin; +use lib "$FindBin::RealBin/../lib"; + +use Getopt::Long; +use List::Util qw(all); +use Path::Tiny; +use Term::ANSIColor qw(:constants); +use Text::Diff; + +use Test::Lintian::Output::Universal qw(order); + +use constant EMPTY => q{}; +use constant SPACE => q{ }; +use constant NEWLINE => qq{\n}; + +no warnings 'redefine'; + +sub Text::Diff::Unified::file_header { return EMPTY; } +sub Text::Diff::Unified::hunk_header { return EMPTY; } + +# options +Getopt::Long::Configure; +unless ( + Getopt::Long::GetOptions( + 'help|h' => sub {usage(); exit;}, + ) +) { + usage(); + die; +} + +# check arguments and options +die "Please use -h for usage information.\n" + if scalar @ARGV != 2; + +# get arguments +my ($expectedpath, $actualpath) = @ARGV; + +my @expected + = reverse sort { order($a) cmp order($b) } (path($expectedpath)->lines_utf8); +my @actual + = reverse sort { order($a) cmp order($b) }(path($actualpath)->lines_utf8); + +my $diff = diff(\@expected, \@actual, { CONTEXT => 0 }); + +my @lines = split(NEWLINE, $diff); +chomp @lines; + +# sort before applying color +@lines = reverse sort @lines; + +# apply color when on a terminal +if (-t STDOUT) { + + my $green = GREEN; + my $red = RED; + my $reset = RESET; + + s/^(\+.*)$/$green$1$reset/ for @lines; + s/^(\-.*)$/$red$1$reset/ for @lines; +} + +print $_ . NEWLINE for @lines; + +exit; + +sub usage { + print <<"END"; +Usage: $0 + + Print differences between the tag information in the two files. The files + must in a CSV format delimited by '|'. The easiest way to obtain such a + file is to use tagextract. + + The output is sorted lexigraphically in reverse order. If the arguments + are reversed, the new output can also be generated from the old one by + reversing the signs and sorting again in reverse order (under LC_ALL=C). + It only works with uncolored output. + + Returns with a zero exit code under normal conditions, even when the tags + do not match. +END + return; +} + +# Local Variables: +# indent-tabs-mode: nil +# cperl-indent-level: 4 +# End: +# vim: syntax=perl sw=4 sts=4 sr et diff -Nru lintian-2.93.0/bin/tagextract lintian-2.89.0ubuntu1/bin/tagextract --- lintian-2.93.0/bin/tagextract 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/bin/tagextract 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,122 @@ +#!/usr/bin/perl + +# Copyright © 2019 Felix Lechner +# +# This program is free software; you can redistribute it and/or modify +# it under the terms of the GNU General Public License as published by +# the Free Software Foundation; either version 2 of the License, or +# (at your option) any later version. +# +# This program is distributed in the hope that it will be useful, +# but WITHOUT ANY WARRANTY; without even the implied warranty of +# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the +# GNU General Public License for more details. +# +# You should have received a copy of the GNU General Public License +# along with this program. If not, you can find it on the World Wide +# Web at http://www.gnu.org/copyleft/gpl.html, or write to the Free +# Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, +# MA 02110-1301, USA. + +# The harness for Lintian's test suite. For detailed information on +# the test suite layout and naming conventions, see t/tests/README. +# For more information about running tests, see +# doc/tutorial/Lintian/Tutorial/TestSuite.pod +# + +use v5.20; +use warnings; +use utf8; +use autodie; + +# use Lintian modules that belong to this program +use FindBin; +use lib "$FindBin::RealBin/../lib"; + +use Getopt::Long; +use List::Util qw(all); +use Path::Tiny; + +use Test::Lintian::Output::EWI; +use Test::Lintian::Output::FullEWI; +use Test::Lintian::Output::LetterQualifier; +use Test::Lintian::Output::ColonSeparated; +use Test::Lintian::Output::XML; + +# options +my $format; + +Getopt::Long::Configure; +unless ( + Getopt::Long::GetOptions( + 'f|format=s' => \$format, + 'help|h' => sub {usage(); exit;}, + ) +) { + usage(); + die; +} + +# check arguments and options +die "Please use -h for usage information.\n" + if scalar @ARGV < 1 || scalar @ARGV > 2; + +# get arguments +my ($inpath, $outpath) = @ARGV; + +die "File $inpath does not exist.\n" + unless -f $inpath; + +my $text = path($inpath)->slurp_utf8; +my $converted = to_universal($format, $text); + +if (defined $outpath) { + path($outpath)->spew_utf8($converted); +}else { + print $converted; +} + +exit; + +sub to_universal { + my ($format, $text) = @_; + + if ($format eq 'EWI') { + return Test::Lintian::Output::EWI::to_universal($text); + }elsif ($format eq 'letterqualifier') { + return Test::Lintian::Output::LetterQualifier::to_universal($text); + }elsif ($format eq 'fullewi') { + return Test::Lintian::Output::FullEWI::to_universal($text); + }elsif ($format eq 'colons') { + return Test::Lintian::Output::ColonSeparated::to_universal($text); + }elsif ($format eq 'xml') { + return Test::Lintian::Output::XML::to_universal($text); + } + + die "Unknown format: $format\n"; +} + +sub usage { + print <<"END"; +Usage: $0 -f + + --format, -f Format of Lintian output file + + Extracts tag information from a variety of Lintian output formats. The + output format is a simplified EWI format without letter code. Other + notable differences are that the binary package type is always displayed. + + The tags are sorted in a reverse order, but with the package type pulled + to the front. That way package types are grouped. Source packages are at + the top. + + Prints to stdout when no is given. +END + return; +} + +# Local Variables: +# indent-tabs-mode: nil +# cperl-indent-level: 4 +# End: +# vim: syntax=perl sw=4 sts=4 sr et diff -Nru lintian-2.93.0/bin/tagsort lintian-2.89.0ubuntu1/bin/tagsort --- lintian-2.93.0/bin/tagsort 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/bin/tagsort 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,92 @@ +#!/usr/bin/perl + +# Copyright © 2019 Felix Lechner +# +# This program is free software; you can redistribute it and/or modify +# it under the terms of the GNU General Public License as published by +# the Free Software Foundation; either version 2 of the License, or +# (at your option) any later version. +# +# This program is distributed in the hope that it will be useful, +# but WITHOUT ANY WARRANTY; without even the implied warranty of +# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the +# GNU General Public License for more details. +# +# You should have received a copy of the GNU General Public License +# along with this program. If not, you can find it on the World Wide +# Web at http://www.gnu.org/copyleft/gpl.html, or write to the Free +# Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, +# MA 02110-1301, USA. + +# The harness for Lintian's test suite. For detailed information on +# the test suite layout and naming conventions, see t/tests/README. +# For more information about running tests, see +# doc/tutorial/Lintian/Tutorial/TestSuite.pod +# + +use v5.20; +use warnings; +use utf8; +use autodie; + +# use Lintian modules that belong to this program +use FindBin; +use lib "$FindBin::RealBin/../lib"; + +use Cwd; +use Getopt::Long; +use List::Util qw(all); +use Path::Tiny; +use Term::ANSIColor; + +use Test::Lintian::Output::Universal qw(parse_line order); + +use constant EMPTY => q{}; +use constant SPACE => q{ }; +use constant COLON => q{:}; +use constant LPARENS => q{(}; +use constant RPARENS => q{)}; +use constant NEWLINE => qq{\n}; + +Getopt::Long::Configure; +unless ( + Getopt::Long::GetOptions( + 'help|h' => sub {usage(); exit;}, + ) +) { + usage(); + die; +} + +# check arguments and options +die "Please use -h for usage information.\n" + if scalar @ARGV != 1; + +# get arguments +my ($tagspath) = @ARGV; + +my @tagslines = path($tagspath)->lines_utf8; +chomp @tagslines; + +my $joined = EMPTY; +$joined .= $_ . NEWLINE + for reverse sort { order($a) cmp order($b) } @tagslines; + +path($tagspath)->spew_utf8($joined); + +exit; + +sub usage { + print <<"END"; +Usage: $0 + + Sorts tagfile in the order preferred for universal tags. +END + return; +} + +# Local Variables: +# indent-tabs-mode: nil +# cperl-indent-level: 4 +# End: +# vim: syntax=perl sw=4 sts=4 sr et diff -Nru lintian-2.93.0/checks/changes-file.pm lintian-2.89.0ubuntu1/checks/changes-file.pm --- lintian-2.93.0/checks/changes-file.pm 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/checks/changes-file.pm 2020-08-10 09:59:45.000000000 +0000 @@ -46,7 +46,7 @@ my $files = $processable->files; my $path - = readlink(path($processable->basedir)->child('changes')->stringify); + = readlink(path($processable->groupdir)->child('changes')->stringify); my %num_checksums; $path =~ s#/[^/]+$##; foreach my $file (keys %$files) { diff -Nru lintian-2.93.0/checks/deb-format.pm lintian-2.89.0ubuntu1/checks/deb-format.pm --- lintian-2.93.0/checks/deb-format.pm 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/checks/deb-format.pm 2020-08-10 09:59:45.000000000 +0000 @@ -57,7 +57,7 @@ my $processable = $self->processable; # deb is a symlink. - my $deb = path($processable->basedir)->child('deb')->stringify; + my $deb = path($processable->groupdir)->child('deb')->stringify; # set to one when something is so bad that we can't continue my $failed; @@ -224,34 +224,27 @@ # error output when processing the package. We want to report # those as tags unless they're just tar noise that doesn't # represent an actual problem. - for my $file (keys %ERRORS) { - - my $path = path($processable->basedir)->child($file)->stringify; - next - unless -e $path && -s _; - - open(my $fd, '<', $path); - - while (my $line = <$fd>) { - chomp($line); - $line =~ s,^(?:[/\w]+/)?tar: ,,; - - # Record size errors are harmless. Ignore implausibly - # old timestamps in the data section since we already - # check for that elsewhere, but still warn for - # control. - next - if $line =~ /^Record size =/; - - next - if $line =~ /implausibly old time stamp/ - && $ERRORS{$file} eq 'tar-errors-from-data'; - - $self->tag($ERRORS{$file}, $line); + my $tag = $ERRORS{$file}; + my $path = path($processable->groupdir)->child($file)->stringify; + if (-s $path) { + open(my $fd, '<', $path); + while (my $line = <$fd>) { + chomp($line); + $line =~ s,^(?:[/\w]+/)?tar: ,,; + + # Record size errors are harmless. Ignore implausibly + # old timestamps in the data section since we already + # check for that elsewhere, but still warn for + # control. + next if $line =~ /^Record size =/; + if ($tag eq 'tar-errors-from-data') { + next if $line =~ /implausibly old time stamp/; + } + $self->tag($tag, $line); + } + close($fd); } - - close $fd; } return; diff -Nru lintian-2.93.0/checks/debian/changelog.pm lintian-2.89.0ubuntu1/checks/debian/changelog.pm --- lintian-2.93.0/checks/debian/changelog.pm 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/checks/debian/changelog.pm 2020-08-10 09:59:45.000000000 +0000 @@ -356,7 +356,7 @@ # Check a NEWS.Debian file if we have one. Save the parsed version of the # file for later checks against the changelog file. my $news; - my $dnews = path($processable->basedir)->child('NEWS.Debian')->stringify; + my $dnews = path($processable->groupdir)->child('NEWS.Debian')->stringify; if (-f $dnews) { my $bytes = path($dnews)->slurp; @@ -489,7 +489,7 @@ } } - my $dchpath = path($processable->basedir)->child('changelog')->stringify; + my $dchpath = path($processable->groupdir)->child('changelog')->stringify; # Everything below involves opening and reading the changelog file, so bail # with a warning at this point if all we have is a symlink. Ubuntu permits # such symlinks, so their profile will suppress this tag. diff -Nru lintian-2.93.0/checks/debian/copyright/dep5.pm lintian-2.89.0ubuntu1/checks/debian/copyright/dep5.pm --- lintian-2.93.0/checks/debian/copyright/dep5.pm 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/checks/debian/copyright/dep5.pm 2020-08-10 09:59:45.000000000 +0000 @@ -29,29 +29,33 @@ use List::Compare; use List::MoreUtils qw(any all none uniq); -use Text::Glob qw(match_glob); use XML::LibXML; use Lintian::Deb822::File; use Lintian::Relation::Version qw(versions_compare); +use constant { + WC_TYPE_REGEX => 'REGEX', + WC_TYPE_FILE => 'FILE', + WC_TYPE_DESCENDANTS => 'DESCENDANTS', +}; + use constant EMPTY => q{}; use constant SPACE => q{ }; -use constant SLASH => q{/}; -use constant COLON => q{:}; use constant ASTERISK => q{*}; use constant LEFT_SQUARE => q{[}; use constant RIGHT_SQUARE => q{]}; +use constant QUESTION_MARK => q{?}; +use constant BACKSLASH => q{\\}; use Moo; use namespace::clean; with 'Lintian::Check'; -my $LAST_SIGNIFICANT_DEP5_CHANGE = '0+svn~166'; -my $LAST_DEP5_OVERHAUL = '0+svn~148'; - -my %NEW_FIELD_NAMES = ( +my $dep5_last_normative_change = '0+svn~166'; +my $dep5_last_overhaul = '0+svn~148'; +my %dep5_renamed_fields = ( 'Format-Specification' => 'Format', 'Maintainer' => 'Upstream-Contact', 'Upstream-Maintainer' => 'Upstream-Contact', @@ -75,7 +79,7 @@ # another check complains about legacy encoding, if needed my @valid_utf8 = grep { $_->is_valid_utf8 } @files; - $self->check_dep5_copyright($_) for @valid_utf8; + $self->check_dep5_copyright($_)for @valid_utf8; return; } @@ -207,7 +211,7 @@ } elsif ($version =~ /svn$/) { $self->tag('unversioned-copyright-format-uri', $uri); - } elsif (versions_compare($version, '<<', $LAST_SIGNIFICANT_DEP5_CHANGE)) { + } elsif (versions_compare($version, '<<', $dep5_last_normative_change)) { $self->tag('out-of-date-copyright-format-uri', $uri); } elsif ($uri =~ m,^http://www\.debian\.org/,) { @@ -215,7 +219,15 @@ } return - if versions_compare($version, '<<', $LAST_DEP5_OVERHAUL); + if versions_compare($version, '<<', $dep5_last_overhaul); + + $self->parse_dep5($copyright_file, $contents); + + return; +} + +sub parse_dep5 { + my ($self, $file, $contents) = @_; # probably DEP 5 format; let's try more checks my $deb822 = Lintian::Deb822::File->new; @@ -227,8 +239,7 @@ chomp $@; $@ =~ s/^syntax error in //; - $self->tag('syntax-error-in-dep5-copyright', - $copyright_file->name . COLON . SPACE . $@); + $self->tag('syntax-error-in-dep5-copyright', "$file: $@"); return; } @@ -329,12 +340,10 @@ } } - my @not_unique - = grep { @{$found_standalone{$_}} > 1 } keys %found_standalone; - for my $name (@not_unique) { - - next - if $name eq 'public-domain'; + for my $name ( + grep { $_ ne 'public-domain' } + grep { @{$found_standalone{$_}} > 1 } keys %found_standalone + ) { $self->tag('dep5-copyright-license-name-not-unique', $name,'(line ' . $_->position('License') . ')') @@ -343,14 +352,15 @@ my ($header, @followers) = @sections; - my @obsolete_fields = grep { $header->exists($_) } keys %NEW_FIELD_NAMES; - for my $old_name (@obsolete_fields) { + my @obsolete = grep { $header->exists($_) } keys %dep5_renamed_fields; + for my $name (@obsolete) { + my $position = $header->position($name); $self->tag( 'obsolete-field-in-dep5-copyright', - $old_name, - $NEW_FIELD_NAMES{$old_name}, - '(line ' . $header->position($old_name) . ')' + $name, + $dep5_renamed_fields{$name}, + "(line $position)" ); } @@ -360,47 +370,32 @@ unless ($self->processable->native) { - my @orig_files - = grep { $_->is_file } $self->processable->orig->sorted_list; - my @orig_names = map { $_->name } @orig_files; + my @files = grep { $_->is_file } $self->processable->orig->sorted_list; my @wildcards = $header->trimmed_list('Files-Excluded'); for my $wildcard (@wildcards) { - my @offenders = escape_errors($wildcard); - $self->tag('invalid-escape-sequence-in-dep5-copyright', $_) - for @offenders; - - next - if @offenders; - - # also match dir/filename for Files-Excluded: dir - unless ($wildcard =~ /\*/ || $wildcard =~ /\?/) { - - my $candidate = $wildcard; - $candidate .= SLASH - unless $candidate =~ m{/$}; - - my $item = $self->processable->orig->lookup($candidate); + my ($wc_value, $wc_type, $wildcard_error) + = parse_wildcard($wildcard); - $wildcard = $candidate . ASTERISK - if defined $item && $item->is_dir; + if (defined $wildcard_error) { + $self->tag('invalid-escape-sequence-in-dep5-copyright', + $wildcard_error); + next; } - local $Text::Glob::strict_leading_dot = 0; - local $Text::Glob::strict_wildcard_slash = 0; - - # disable Text::Glob character classes and alternations - my $dulled = $wildcard; - $dulled =~ s/([{}\[\]])/\\$1/g; + # also match dir/filename for Files-Excluded: dir + $wc_value = qr{^$wc_value(?:/|$)} + if $wc_type eq WC_TYPE_FILE; - my @unwanted = match_glob($dulled, @orig_names); + for my $srcfile (@files) { - for my $name (@unwanted) { + next + if $srcfile =~ m{^(?:debian|\.pc)/}; - $self->tag('source-includes-file-in-files-excluded', $name) - unless $name =~ m{^(?:debian|\.pc)/}; + $self->tag('source-includes-file-in-files-excluded', $srcfile) + if $srcfile =~ qr{^$wc_value}; } } } @@ -440,31 +435,34 @@ $_->position ) for @unknown_sections; - my @shipped_items; - + my $index; if ($self->processable->native) { - @shipped_items = $self->processable->patched->sorted_list; - + $index = $self->processable->patched; } else { - @shipped_items = $self->processable->orig->sorted_list; + $index = $self->processable->orig; + } + + my @allpaths = $index->sorted_list; + + unless ($self->processable->native) { - # remove ./debian folder from orig, if any - @shipped_items = grep { $_ !~ m{^debian/} } @shipped_items + # remove existing ./debian folder, if any + @allpaths = grep { $_ !~ m{^debian/} } @allpaths if $self->processable->fields->value('Format') eq '3.0 (quilt)'; - # add ./ debian folder from patched my $debian_dir = $self->processable->patched->resolve_path('debian/'); - push(@shipped_items, $debian_dir->descendants) + push(@allpaths, $debian_dir->descendants) if $debian_dir; } - my @shipped_names - = sort map { $_->name } grep { $_->is_file } @shipped_items; + my @shippedfiles = sort map { $_->name } grep { $_->is_file } @allpaths; - my @license_names= grep { m,(^|/)(COPYING[^/]*|LICENSE)$, } @shipped_names; - my @quilt_names = grep { m,^\.pc/, } @shipped_names; + my @licensefiles= grep { m,(^|/)(COPYING[^/]*|LICENSE)$, } @shippedfiles; + my @quiltfiles = grep { m,^\.pc/, } @shippedfiles; - my @names_with_comma = grep { /,/ } @shipped_names; + my %file_shipped = map { $_ => 1 } @shippedfiles; + + my @names_with_comma = grep { /,/ } @allpaths; my @fields_with_comma = grep { $_->value('Files') =~ /,/ } @followers; if (@fields_with_comma && !@names_with_comma) { @@ -559,40 +557,58 @@ for my $wildcard (@wildcards) { - my @offenders = escape_errors($wildcard); - - $self->tag( - 'invalid-escape-sequence-in-dep5-copyright', - $_. ' (paragraph at line '. $section->position. ')' - ) for @offenders; + my ($wc_value, $wc_type, $wildcard_error) + = parse_wildcard($wildcard); - next - if @offenders; + if (defined $wildcard_error) { + $self->tag('invalid-escape-sequence-in-dep5-copyright', + substr($wildcard_error, 0, 2) + . ' (paragraph at line ' + . $section->position + . ')'); + next; + } - local $Text::Glob::strict_leading_dot = 0; - local $Text::Glob::strict_wildcard_slash = 0; + my @covered_files; - # disable Text::Glob character classes and alternations - my $dulled = $wildcard; - $dulled =~ s/([{}\[\]])/\\$1/g; + if ($wc_type eq WC_TYPE_FILE) { + @covered_files = ($wc_value) + if $file_shipped{$wc_value}; + + } elsif ($wc_type eq WC_TYPE_DESCENDANTS) { + + # special-case Files: * + if ($wc_value eq EMPTY) { + @covered_files = @shippedfiles; + + } elsif ($wc_value =~ /^debian\//) { + my $parent= $self->processable->patched->lookup($wc_value); + @covered_files= grep { $_->is_file }$parent->descendants + if $parent; + + } else { + my $parent = $index->lookup($wc_value); + @covered_files= grep { $_->is_file }$parent->descendants + if $parent; + } - my @covered = match_glob($dulled, @shipped_names); + } else { + @covered_files = grep { $_ =~ $wc_value } @shippedfiles; + } - for my $name (@covered) { - $wildcards_same_section_by_file{$name} //= []; - push(@{$wildcards_same_section_by_file{$name}}, $wildcard); + for my $file (@covered_files) { + $wildcards_same_section_by_file{$file} //= []; + push(@{$wildcards_same_section_by_file{$file}}, $wildcard); } } - my @overwritten = grep { length $wildcard_by_file{$_} } + my @overwritten = grep { $wildcard_by_file{$_} } keys %wildcards_same_section_by_file; - - for my $name (@overwritten) { + for my $file (@overwritten) { my $winning_wildcard - = @{$wildcards_same_section_by_file{$name}}[-1]; - my $loosing_wildcard = $wildcard_by_file{$name}; - + = @{$wildcards_same_section_by_file{$file}}[-1]; + my $loosing_wildcard = $wildcard_by_file{$file}; my $winner_depth = ($winning_wildcard =~ tr{/}{}); my $looser_depth = ($loosing_wildcard =~ tr{/}{}); @@ -615,7 +631,7 @@ . join(SPACE, @{$wildcards_same_section_by_file{$_}}) . RIGHT_SQUARE, "for $_" - ) for @overmatched_same_section; + )for @overmatched_same_section; push(@redundant_wildcards, map { @{$wildcards_same_section_by_file{$_}} } @@ -648,49 +664,42 @@ $self->tag( 'wildcard-matches-nothing-in-dep5-copyright', "$wildcard (line " . $_->position('Files') . ')' - ) for @{$sections_by_wildcard{$wildcard}}; + )for @{$sections_by_wildcard{$wildcard}}; } my %sections_by_file; - for my $name (keys %wildcard_by_file) { - - $sections_by_file{$name} //= []; - my $wildcard = $wildcard_by_file{$name}; - + for my $file (keys %wildcard_by_file) { + $sections_by_file{$file} //= []; push( - @{$sections_by_file{$name}}, - @{$sections_by_wildcard{$wildcard}}); + @{$sections_by_file{$file}}, + @{$sections_by_wildcard{$wildcard_by_file{$file}}}); } my %license_identifiers_by_file; - for my $name (keys %sections_by_file) { - - $license_identifiers_by_file{$name} //= []; - + for my $file (keys %sections_by_file) { + $license_identifiers_by_file{$file} //= []; push( - @{$license_identifiers_by_file{$name}}, + @{$license_identifiers_by_file{$file}}, $license_identifier_by_section{$_->position} - ) for @{$sections_by_file{$name}}; + )for @{$sections_by_file{$file}}; } my @xml_searchspace = keys %license_identifiers_by_file; - # do not examine Lintian's test suite for appstream metadata + # do not search Lintian's test suite for appstream metadata @xml_searchspace = grep { $_ !~ m{t/} } @xml_searchspace if $self->processable->name eq 'lintian'; - for my $name (@xml_searchspace) { - + for my $srcfile (@xml_searchspace) { next - if $name =~ '^\.pc/'; - + if $srcfile =~ '^\.pc/'; next - unless $name =~ /\.xml$/; + unless $srcfile =~ /\.xml$/; my $parser = XML::LibXML->new; $parser->set_option('no_network', 1); - my $file = $self->processable->patched->resolve_path($name); + my $file = $self->processable->patched->resolve_path($srcfile); my $doc = eval {$parser->parse_file($file->unpacked_path);}; next unless $doc; @@ -708,23 +717,24 @@ next unless $seen; - my @wanted = @{$license_identifiers_by_file{$name}}; + my @wanted = @{$license_identifiers_by_file{$srcfile}}; my @mismatched = grep { $_ ne $seen } @wanted; $self->tag('inconsistent-appstream-metadata-license', - $name, "($seen != $_)") + $srcfile, "($seen != $_)") for @mismatched; } - my @no_license_needed = (@quilt_names, @license_names); + my @no_license_needed = (@quiltfiles, @licensefiles); my $unlicensed_lc - = List::Compare->new(\@shipped_names, \@no_license_needed); + = List::Compare->new(\@shippedfiles, \@no_license_needed); my @license_needed = $unlicensed_lc->get_Lonly; - my @not_covered + my @files_not_covered = grep { !@{$sections_by_file{$_} // []} } @license_needed; - $self->tag('file-without-copyright-information',$_) for @not_covered; + $self->tag('file-without-copyright-information',$_) + for @files_not_covered; my @all_positions = map { $_->position } @@ -750,7 +760,6 @@ for @missing_standalone; for my $name (grep { $_ ne 'public-domain' } @unused_standalone) { - $self->tag('unused-license-paragraph-in-dep5-copyright', $name,'(line ' . $_->position('License') . ')') for @{$found_standalone{$name}}; @@ -765,22 +774,103 @@ # license files do not require their own entries in d/copyright. my $license_lc - = List::Compare->new(\@license_names, [keys %sections_by_wildcard]); - my @listed_licences = $license_lc->get_intersection; + = List::Compare->new(\@licensefiles, [keys %sections_by_wildcard]); + my @listedlicensefiles = $license_lc->get_intersection; $self->tag('license-file-listed-in-debian-copyright',$_) - for @listed_licences; + for @listedlicensefiles; return; } -sub escape_errors { - my ($escaped) = @_; +sub dequote_backslashes { + my ($string) = @_; + + return ($string, undef) + if index($string, BACKSLASH) == -1; + + my $error; + eval { + $string =~ s{ + ([^\\]+) | + (\\[\\]) | + (.+) + }{ + if (defined $1) { + quotemeta($1); + } elsif (defined $2) { + $2; + } else { + $error = $3; + die; + } + }egx; + }; + + if ($@) { + return (undef, $error); + } + + return ($string, undef); +} - my @sequences = ($escaped =~ m{\\.?}g); - my @illegal = grep { $_ !~ m{^\\[*?]$} } @sequences; +sub parse_wildcard { + my ($regex_src) = @_; - return @illegal; + return (EMPTY, WC_TYPE_DESCENDANTS, undef) + if $regex_src eq ASTERISK; + + my $error; + + if (index($regex_src, QUESTION_MARK) == -1) { + + my $star_index = index($regex_src, ASTERISK); + + if ($star_index == -1) { + # Regular file-match, dequote "\\" if any and stop here. + ($regex_src, $error) = dequote_backslashes($regex_src); + + return ($regex_src, WC_TYPE_FILE, $error); + } + + if ($star_index + 1 == length $regex_src + && substr($regex_src, -2) eq '/*') { + # Files: some-dir/* + $regex_src = substr($regex_src, 0, -1); + + ($regex_src, $error) = dequote_backslashes($regex_src); + + return ($regex_src, WC_TYPE_DESCENDANTS, $error); + } + } + + eval { + $regex_src =~ s{ + (\*) | + (\?) | + ([^*?\\]+) | + (\\[\\*?]) | + (.+) + }{ + if (defined $1) { + '.*'; + } elsif (defined $2) { + '.' + } elsif (defined $3) { + quotemeta($3); + } elsif (defined $4) { + $4; + } else { + $error = $5; + die; + } + }egx; + }; + if ($@) { + return (undef, undef, $error); + } else { + return (qr/^(?:$regex_src)$/, WC_TYPE_REGEX, undef); + } } 1; diff -Nru lintian-2.93.0/checks/debian/copyright.pm lintian-2.89.0ubuntu1/checks/debian/copyright.pm --- lintian-2.93.0/checks/debian/copyright.pm 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/checks/debian/copyright.pm 2020-08-10 09:59:45.000000000 +0000 @@ -163,7 +163,7 @@ } my $dcopy - = path($self->processable->basedir)->child('copyright')->stringify; + = path($self->processable->groupdir)->child('copyright')->stringify; my $bytes = path($dcopy)->slurp; diff -Nru lintian-2.93.0/checks/debian/lintian-overrides/comments.pm lintian-2.89.0ubuntu1/checks/debian/lintian-overrides/comments.pm --- lintian-2.93.0/checks/debian/lintian-overrides/comments.pm 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/checks/debian/lintian-overrides/comments.pm 2020-08-10 09:59:45.000000000 +0000 @@ -46,30 +46,23 @@ for my $context (keys %{$declared_overrides->{$tagname}}) { my $entry = $declared_overrides->{$tagname}{$context}; - + my $line = $entry->{line}; my @comments = @{$entry->{comments}}; - my $override_position = $entry->{line}; - - my $position = $override_position - scalar @comments; - for my $comment (@comments) { - - check_spelling( - $comment, - $self->group->spelling_exceptions, - $self->emitter( - 'spelling-in-override-comment', - "$tagname (line $position)" - )); - check_spelling_picky( - $comment, - $self->emitter( - 'capitalization-in-override-comment', - "$tagname (line $position)" - )); - } continue { - $position++; - } + check_spelling( + $_, + $self->group->spelling_exceptions, + $self->emitter( + 'spelling-in-override-comment', + "$tagname (line $line)" + ))for @comments; + + check_spelling_picky( + $_, + $self->emitter( + 'capitalization-in-override-comment', + "$tagname (line $line)" + ))for @comments; } } diff -Nru lintian-2.93.0/checks/debian/patches/dep3.pm lintian-2.89.0ubuntu1/checks/debian/patches/dep3.pm --- lintian-2.93.0/checks/debian/patches/dep3.pm 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/checks/debian/patches/dep3.pm 2020-08-10 09:59:45.000000000 +0000 @@ -47,8 +47,7 @@ unless $item->is_file; return - if $item->name eq 'debian/patches/series' - || $item->name eq 'debian/patches/README'; + if $item->name eq 'debian/patches/series'; my $bytes = $item->bytes; return diff -Nru lintian-2.93.0/checks/debian/upstream/signing-key.pm lintian-2.89.0ubuntu1/checks/debian/upstream/signing-key.pm --- lintian-2.93.0/checks/debian/upstream/signing-key.pm 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/checks/debian/upstream/signing-key.pm 2020-08-10 09:59:45.000000000 +0000 @@ -26,7 +26,6 @@ use autodie; use File::Temp; -use List::Util qw(pairs); use Lintian::Data; use Lintian::IPC::Run3 qw(safe_qx); @@ -84,14 +83,11 @@ next; } - # remove comments - $output =~ s/^#[^\n]*$//mg; - - # split into separate keys - my @keys = split(/^:public key packet:.*$/m, $output); - - # discard leading information - shift @keys; + # parse command output into separate keys + my @keys + = ($output + =~ m/(^:public key packet:(?:\n|\z)(?:(?!:public key packet:).+(?:\n|\z))*)/mg + ); unless (scalar @keys) { $self->tag('public-upstream-key-unusable', @@ -99,21 +95,20 @@ next; } - for my $key (@keys) { + foreach my $key (@keys) { # parse each key into separate packets - my ($public_key, @pieces) = split(/^(:.+)$/m, $key); - my @packets = pairs @pieces; + my @packets = ($key =~ m/(^:.+(?:\n|\z)(?:^\t.+(?:\n|\z))*)/mg); # require at least one packet - unless (length $public_key) { + unless (scalar @packets) { $self->tag('public-upstream-key-unusable', - $key_name,'has no public key'); + $key_name,'has no packets'); next; } # look for key identifier - unless ($public_key =~ qr/^\s*keyid:\s+(\S+)$/m) { + unless ($packets[0] =~ (qr/\skeyid:\s+(\S+)\s/)) { $self->tag('public-upstream-key-unusable', $key_name, 'has no keyid'); next; @@ -122,14 +117,10 @@ # look for third-party signatures my @thirdparty; - for my $packet (@packets) { - - my $header = $packet->[0]; - if ($header =~ qr/^:signature packet: algo \d+, keyid (\S*)$/){ - - my $signatory = $1; - push(@thirdparty, $signatory) - unless $signatory eq $keyid; + foreach my $packet (@packets) { + if ($packet =~ qr/^:signature packet: algo \d+, keyid (\S*)\n/) + { + push(@thirdparty, $1) if $1 ne $keyid; } } diff -Nru lintian-2.93.0/checks/documentation/manual.pm lintian-2.89.0ubuntu1/checks/documentation/manual.pm --- lintian-2.93.0/checks/documentation/manual.pm 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/checks/documentation/manual.pm 2020-08-10 09:59:45.000000000 +0000 @@ -302,55 +302,63 @@ my @lines = split(/\n/, $stderr); - for my $line (@lines) { - - chomp $line; - + for (@lines) { # Devel::Cover causes some annoying deep recursion # warnings and sometimes in our child process. # Filter them out, but only during coverage. next if LINTIAN_COVERAGE - && $line =~ m{ + and m{ \A Deep [ ] recursion [ ] on [ ] subroutine [ ] "[^"]+" [ ] at [ ] .*B/Deparse.pm [ ] line [ ] \d+}xsm; # ignore progress information from man next - if $line =~ /^Reformatting/; + if /^Reformatting/; next - if $line =~ /^\s*$/; + if /^\s*$/; - # ignore errors from gzip; dealt with elsewhere + # ignore errors from gzip, will be dealt with at other places next - if $line =~ /^\bgzip\b/; + if /^(?:man|gzip)/; # ignore wrapping failures for Asian man pages (groff problem) if ($language =~ /^(?:ja|ko|zh)/) { next - if $line =~ /warning \[.*\]: cannot adjust line/; + if /warning \[.*\]: cannot adjust line/; next - if $line =~ /warning \[.*\]: can\'t break line/; + if /warning \[.*\]: can\'t break line/; } # ignore wrapping failures if they contain URLs (.UE is an # extension for marking the end of a URL). next - if $line - =~ /:(\d+): warning \[.*\]: (?:can\'t break|cannot adjust) line/ - && ( $manfile[$1 - 1] =~ m,(?:https?|ftp|file)://.+,i - || $manfile[$1 - 1] =~ m,^\s*\.\s*UE\b,); + if + /:(\d+): warning \[.*\]: (?:can\'t break|cannot adjust) line/ + and( $manfile[$1 - 1] =~ m,(?:https?|ftp|file)://.+,i + or $manfile[$1 - 1] =~ m,^\s*\.\s*UE\b,); # ignore common undefined macros from pod2man << Perl 5.10 next - if $line =~ /warning: (?:macro )?\'(?:Tr|IX)\' not defined/; + if /warning: (?:macro )?\'(?:Tr|IX)\' not defined/; + + chomp; + s/^[^:]+: //; + s/^://; + + $self->tag('groff-message', $file, $_); + + last; + } - $line =~ s/^[^:]+: //; - $line =~ s/^://; + if ($status) { + my $message = "Non-zero status $status from @command"; + $message .= COLON . NEWLINE . $stderr + if length $stderr; - $self->tag('groff-message', $file, $line); + warn $message; } chdir($savedir); diff -Nru lintian-2.93.0/checks/documentation.pm lintian-2.89.0ubuntu1/checks/documentation.pm --- lintian-2.93.0/checks/documentation.pm 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/checks/documentation.pm 2020-08-10 09:59:45.000000000 +0000 @@ -76,7 +76,7 @@ } # doxygen md5sum - if ($file->name =~ m{^usr/share/doc/$ppkg/[^/]+/.+\.md5$}s) { + if ($file->name =~ m,^usr/share/doc/$ppkg/[^/]+/.+\.md5$,) { $self->tag('useless-autogenerated-doxygen-file', $file->name) if $file->parent_dir->child('doxygen.png'); @@ -84,15 +84,16 @@ # doxygen compressed map if ( - $file->name =~ m{^usr/share/doc/(?:.+/)?(?:doxygen|html)/ - .*\.map\.$COMPRESS_FILE_EXTENSIONS_OR_ALL}xs + $file->name =~ m,^usr/share/doc/(?:.+/)?(?:doxygen|html)/ + .*\.map\.$COMPRESS_FILE_EXTENSIONS_OR_ALL,x ) { $self->tag('compressed-documentation', $file->name); } if( $file->is_file && $file->name !~ m,^etc/, - && $file->name !~ m,^usr/share/(?:doc|help)/,) { + && $file->name !~ m,^usr/share/(?:doc|help)/, + && $self->processable->source ne 'lintian') { foreach my $taboo ($DOCUMENTATION_FILE_REGEX->all) { @@ -111,10 +112,6 @@ if $file->dirname =~ m{templates?(?:\.d)?/}; next - if $file->basename =~ m{\.txt$} - and $file->dirname =~ m{^usr/lib/python3/.*\.egg-info/}s; - - next if $file->basename =~ m{^README}xi and $file->bytes =~ m{this directory}xi; @@ -155,8 +152,8 @@ # uses __init__.py to mark module directories. unless ($file->name =~ m,^usr/share/doc/(?:[^/]+/)?examples/, or $file->name - =~ m{^usr/share/doc/(?:.+/)?(?:doxygen|html)/.*\.map$}s - or $file->name=~ m{^usr/share/doc/(?:.+/)?__init__\.py$}s){ + =~ m,^usr/share/doc/(?:.+/)?(?:doxygen|html)/.*\.map$, + or $file->name=~ m,^usr/share/doc/(?:.+/)?__init__\.py$,){ $self->tag('zero-byte-file-in-doc-directory', $file->name); } @@ -165,7 +162,7 @@ # gzipped zero byte files: # 276 is 255 bytes (maximal length for a filename) # + gzip overhead - if ( $file->name =~ m{\.gz$} + if ( $file->name =~ m,.gz$, and $file->is_regular_file and $file->size <= 276 and $file->file_info =~ m/gzip compressed/) { @@ -185,7 +182,7 @@ } # contains an INSTALL file? - if ($file->name =~ m{^usr/share/doc/$ppkg/INSTALL(?:\..+)*$}s){ + if ($file->name =~ m,^usr/share/doc/$ppkg/INSTALL(?:\..+)*$,){ $self->tag('package-contains-upstream-installation-documentation', $file->name); } diff -Nru lintian-2.93.0/checks/fields/package-relations.pm lintian-2.89.0ubuntu1/checks/fields/package-relations.pm --- lintian-2.93.0/checks/fields/package-relations.pm 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/checks/fields/package-relations.pm 2020-08-10 09:59:45.000000000 +0000 @@ -559,7 +559,7 @@ my ($dep, $pkg_name) = @{$d}; my $replacement = $OBSOLETE_PACKAGES->value($pkg_name) // ''; - + next if $processable->source eq 'lintian'; $replacement = ' => ' . $replacement if $replacement ne ''; if ( $pkg_name eq $alternatives[0][0] diff -Nru lintian-2.93.0/checks/files/hierarchy/path-segments.pm lintian-2.89.0ubuntu1/checks/files/hierarchy/path-segments.pm --- lintian-2.93.0/checks/files/hierarchy/path-segments.pm 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/checks/files/hierarchy/path-segments.pm 2020-08-10 09:59:45.000000000 +0000 @@ -31,20 +31,16 @@ with 'Lintian::Check'; sub visit_installed_files { - my ($self, $item) = @_; + my ($self, $file) = @_; - return - unless $item->is_dir; + my @segments = split(m{/}, $file->dirname); - my @segments = split(m{/}, $item->name); - return - unless @segments; + # List::MoreUtils has 'duplicates' starting at 0.423 + my %count; + $count{$_}++ for @segments; + my @repeated = grep { $count{$_} > 1 } keys %count; - my $final = $segments[-1]; - my $count = scalar grep { $final eq $_ } @segments; - - $self->tag('repeated-path-segment', $final, $item->name) - if $count > 1; + $self->tag('repeated-path-segment', $_, $file->name) for @repeated; return; } diff -Nru lintian-2.93.0/checks/languages/ocaml.pm lintian-2.89.0ubuntu1/checks/languages/ocaml.pm --- lintian-2.93.0/checks/languages/ocaml.pm 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/checks/languages/ocaml.pm 2020-08-10 09:59:45.000000000 +0000 @@ -59,23 +59,20 @@ sub setup_installed_files { my ($self) = @_; - for my $item ($self->processable->installed->sorted_list) { - - my $ar_info = $item->ar_info; - next - unless scalar keys %{$ar_info}; - - # ends in a slash - my $dirname = $item->dirname; - - for my $count (keys %{$ar_info}) { - - my $member = $ar_info->{$count}{name}; - # Note: a .o may be legitimately in several different .a - $self->provided_o->{"$dirname$member"} = $item->name - if length $member; + open(my $fd, '<', + path($self->processable->groupdir)->child('ar-info')->stringify); + while (my $line = <$fd>) { + chomp($line); + if ($line =~ /^(?:\.\/)?([^:]+): (.*)$/) { + my ($filename, $contents) = ($1, $2); + my $dirname = dirname($filename); + for my $entry (split m/ /, $contents) { + # Note: a .o may be legitimately in several different .a + $self->provided_o->{"$dirname/$entry"} = $filename; + } } } + close($fd); # is it a library package? $self->_set_is_lib_package(1) diff -Nru lintian-2.93.0/checks/md5sums.pm lintian-2.89.0ubuntu1/checks/md5sums.pm --- lintian-2.93.0/checks/md5sums.pm 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/checks/md5sums.pm 2020-08-10 09:59:45.000000000 +0000 @@ -68,7 +68,8 @@ # ignore if package contains no files return - if -z path($self->processable->basedir)->child('md5sums')->stringify; + if -z path($self->processable->groupdir)->child('md5sums') + ->stringify; $self->tag('no-md5sums-control-file') unless $self->only_conffiles; diff -Nru lintian-2.93.0/checks/tar-errors.pm lintian-2.89.0ubuntu1/checks/tar-errors.pm --- lintian-2.93.0/checks/tar-errors.pm 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/checks/tar-errors.pm 2020-08-10 09:59:45.000000000 +0000 @@ -45,8 +45,8 @@ sub source { my ($self) = @_; - my $basedir = $self->processable->basedir; - my @paths = grep { -e $_ && -s _ } map { "$basedir/$_" } @ERROR_LOGS; + my $groupdir = $self->processable->groupdir; + my @paths = grep { -s } map { "$groupdir/$_" } @ERROR_LOGS; for my $path (@paths) { diff -Nru lintian-2.93.0/checks/upstream-signature.pm lintian-2.89.0ubuntu1/checks/upstream-signature.pm --- lintian-2.93.0/checks/upstream-signature.pm 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/checks/upstream-signature.pm 2020-08-10 09:59:45.000000000 +0000 @@ -84,7 +84,7 @@ my @allsigs = map { @{$signatures{$_}} } @origtar; for my $signature (@allsigs) { - my $path = $processable->basedir . SLASH . $signature; + my $path = $processable->groupdir . SLASH . $signature; my $contents = path($path)->slurp; if ($contents =~ /^-----BEGIN PGP ARMORED FILE-----/m) { diff -Nru lintian-2.93.0/data/files/documentation-file-regex lintian-2.89.0ubuntu1/data/files/documentation-file-regex --- lintian-2.93.0/data/files/documentation-file-regex 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/data/files/documentation-file-regex 2020-08-10 09:59:45.000000000 +0000 @@ -1,24 +1,11 @@ # a list of regex for detecting documentation file checked against basename # regex (xi) -\.docx?$ -\.html?$ -\.info$ -\.latex$ \.markdown$ -\.md$ -\.odt$ -\.pdf$ -\.readme$ -\.rmd$ -\.rst$ -\.rtf$ -\.tex$ -\.txt$ -^code[-_]of[-_]conduct$ -^contribut(?:e|ing)$ -^copyright$ -^licen[sc]es?$ -^howto$ -^patents?$ -^readme(?:\.?first|\.1st|\.debian|\.source)?$ -^todos?$ +\.r?md$ +^readme(?![a-z]) +^readmefirst +^patents?(?:\.|$) +^licen[sc]es?(?:\.txt|$) +^contribut(?:e|ing)(?:\.|$) +^code[-_]of +^todos?(?:\.|$) diff -Nru lintian-2.93.0/data/files/fonts lintian-2.89.0ubuntu1/data/files/fonts --- lintian-2.93.0/data/files/fonts 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/data/files/fonts 2020-08-10 09:59:45.000000000 +0000 @@ -2,14 +2,14 @@ # package that contains the font. Only packages starting with ttf-, # otf-, t1-, xfonts- and fonts- are searched for fonts. # -# Last updated: 2020-08-23 +# Last updated: 2018-01-13 1015sn.ttf ttf-aenigma 1015snr.ttf ttf-aenigma 18holes.ttf ttf-aenigma -3270-regular.otf fonts-3270 -3270condensed-regular.otf fonts-3270 -3270semicondensed-regular.otf fonts-3270 +3270medium.otf fonts-3270 +3270narrow.otf fonts-3270 +3270seminarrow.otf fonts-3270 36daysag.ttf ttf-aenigma 36daythk.ttf ttf-aenigma 3dlet.ttf ttf-aenigma @@ -42,7 +42,7 @@ aboriginalserifregular943.ttf fonts-lg-aboriginal abydosb_hint.ttf fonts-ancient-scripts abydosr_hint.ttf fonts-ancient-scripts -abyssinicasil-regular.ttf fonts-sil-abyssinica +abyssinicasil-r.ttf fonts-sil-abyssinica accanthisadfstd-bold.otf fonts-adf-accanthis accanthisadfstd-bolditalic.otf fonts-adf-accanthis accanthisadfstd-italic.otf fonts-adf-accanthis @@ -107,56 +107,23 @@ aescrawl.ttf ttf-aenigma aesymatt.ttf ttf-aenigma aftermat.ttf ttf-aenigma -akatab-regular.ttf fonts-sil-akatab akkadian_hint.ttf fonts-ancient-scripts aksharyogini2normal.ttf fonts-aksharyogini2 -alegreyasans-black.otf fonts-alegreya-sans -alegreyasans-blackitalic.otf fonts-alegreya-sans -alegreyasans-bold.otf fonts-alegreya-sans -alegreyasans-bolditalic.otf fonts-alegreya-sans -alegreyasans-extrabold.otf fonts-alegreya-sans -alegreyasans-extrabolditalic.otf fonts-alegreya-sans -alegreyasans-italic.otf fonts-alegreya-sans -alegreyasans-light.otf fonts-alegreya-sans -alegreyasans-lightitalic.otf fonts-alegreya-sans -alegreyasans-medium.otf fonts-alegreya-sans -alegreyasans-mediumitalic.otf fonts-alegreya-sans -alegreyasans-regular.otf fonts-alegreya-sans -alegreyasans-thin.otf fonts-alegreya-sans -alegreyasans-thinitalic.otf fonts-alegreya-sans -alegreyasanssc-black.otf fonts-alegreya-sans -alegreyasanssc-blackitalic.otf fonts-alegreya-sans -alegreyasanssc-bold.otf fonts-alegreya-sans -alegreyasanssc-bolditalic.otf fonts-alegreya-sans -alegreyasanssc-extrabold.otf fonts-alegreya-sans -alegreyasanssc-extrabolditalic.otf fonts-alegreya-sans -alegreyasanssc-italic.otf fonts-alegreya-sans -alegreyasanssc-light.otf fonts-alegreya-sans -alegreyasanssc-lightitalic.otf fonts-alegreya-sans -alegreyasanssc-medium.otf fonts-alegreya-sans -alegreyasanssc-mediumitalic.otf fonts-alegreya-sans -alegreyasanssc-regular.otf fonts-alegreya-sans -alegreyasanssc-thin.otf fonts-alegreya-sans -alegreyasanssc-thinitalic.otf fonts-alegreya-sans alexander_hint.ttf fonts-ancient-scripts alfa-beta.ttf fonts-linex alfios_b.otf fonts-ancient-scripts alfios_i.otf fonts-ancient-scripts alfios_j.otf fonts-ancient-scripts alfios_r.otf fonts-ancient-scripts -alkalami-light.ttf fonts-sil-alkalami -alkalami-regular.ttf fonts-sil-alkalami -allerta_medium.otf fonts-allerta -allerta_stencil.otf fonts-allerta alphbeta.ttf ttf-aenigma amalgama.ttf ttf-aenigma amalgamo.ttf ttf-aenigma amiri-bold.ttf fonts-hosny-amiri amiri-boldslanted.ttf fonts-hosny-amiri +amiri-quran-colored.ttf fonts-hosny-amiri +amiri-quran.ttf fonts-hosny-amiri amiri-regular.ttf fonts-hosny-amiri amiri-slanted.ttf fonts-hosny-amiri -amiriquran.ttf fonts-hosny-amiri -amiriqurancolored.ttf fonts-hosny-amiri amit.otf fonts-ldco amit.ttf fonts-ldco amplitud.ttf ttf-aenigma @@ -170,7 +137,7 @@ andikanewbasic-i.ttf fonts-sil-andikanewbasic andikanewbasic-r.ttf fonts-sil-andikanewbasic ani.ttf fonts-beng-extra -anjalioldlipi-regular.ttf fonts-smc-anjalioldlipi +anjalioldlipi.ttf fonts-smc-anjalioldlipi annapurnasil-bold.ttf fonts-sil-annapurna annapurnasil-regular.ttf fonts-sil-annapurna aoyagi-soseki.ttf fonts-aoyagi-soseki @@ -179,23 +146,22 @@ apibolit.ttf fonts-linex apiitali.ttf fonts-linex apiregul.ttf fonts-linex -apropal-bold.otf fonts-apropal arimo-bold.ttf fonts-croscore arimo-bolditalic.ttf fonts-croscore arimo-italic.ttf fonts-croscore arimo-regular.ttf fonts-croscore aroania_hint.ttf fonts-ancient-scripts arthriti.ttf ttf-aenigma -arundinasans-bold.ttf fonts-arundina -arundinasans-boldoblique.ttf fonts-arundina -arundinasans-oblique.ttf fonts-arundina -arundinasans.ttf fonts-arundina -arundinasansmono-bold.ttf fonts-arundina -arundinasansmono-boldoblique.ttf fonts-arundina -arundinasansmono-oblique.ttf fonts-arundina -arundinasansmono.ttf fonts-arundina -arundinaserif-bold.ttf fonts-arundina -arundinaserif.ttf fonts-arundina +arundinasans-bold.ttf fonts-sipa-arundina +arundinasans-boldoblique.ttf fonts-sipa-arundina +arundinasans-oblique.ttf fonts-sipa-arundina +arundinasans.ttf fonts-sipa-arundina +arundinasansmono-bold.ttf fonts-sipa-arundina +arundinasansmono-boldoblique.ttf fonts-sipa-arundina +arundinasansmono-oblique.ttf fonts-sipa-arundina +arundinasansmono.ttf fonts-sipa-arundina +arundinaserif-bold.ttf fonts-sipa-arundina +arundinaserif.ttf fonts-sipa-arundina asana-math.otf fonts-oflb-asana-math aseab_hint.ttf fonts-ancient-scripts aseai_hint.ttf fonts-ancient-scripts @@ -228,7 +194,6 @@ averiaserifgwf-light.ttf fonts-averia-serif-gwf averiaserifgwf-lightitalic.ttf fonts-averia-serif-gwf averiaserifgwf-regular.ttf fonts-averia-serif-gwf -awaminastaliq-regular.ttf fonts-sil-awami-nastaliq b018012d.pfb t1-cyrillic b018015d.pfb t1-cyrillic b018032d.pfb t1-cyrillic @@ -236,14 +201,6 @@ b2sq.ttf ttf-aenigma b2sqol1.ttf ttf-aenigma b2sqol2.ttf ttf-aenigma -b612-bold.otf fonts-b612 -b612-bolditalic.otf fonts-b612 -b612-italic.otf fonts-b612 -b612-regular.otf fonts-b612 -b612mono-bold.otf fonts-b612 -b612mono-bolditalic.otf fonts-b612 -b612mono-italic.otf fonts-b612 -b612mono-regular.otf fonts-b612 babeboit.ttf fonts-linex babebold.ttf fonts-linex babelita.ttf fonts-linex @@ -251,7 +208,6 @@ babelstonehan.ttf fonts-babelstone-han babelstonemodern.ttf fonts-babelstone-modern backlash.ttf ttf-aenigma -bajaderka-regular.otf fonts-bajaderka balker.ttf fonts-dustin bandal.ttf fonts-alee bandless.ttf ttf-aenigma @@ -263,29 +219,51 @@ baskervaldadfstd-heavy.otf fonts-adf-baskervald baskervaldadfstd-heavyitalic.otf fonts-adf-baskervald baskervaldadfstd-italic.otf fonts-adf-baskervald +baskervaldadfstd-regular.otf ttf-adf-baskervald baskervaldadfstd.otf fonts-adf-baskervald +baskervaldadfstdheavy-oblique.otf ttf-adf-baskervald +baskervaldadfstdheavy.otf ttf-adf-baskervald batang.ttf fonts-baekmuk bebasneue-bold.otf fonts-bebas-neue bebasneue-book.otf fonts-bebas-neue bebasneue-light.otf fonts-bebas-neue bebasneue-regular.otf fonts-bebas-neue bebasneue-thin.otf fonts-bebas-neue -becausewebuild-regular.otf fonts-bwht -becauseweconnect-regular.otf fonts-bwht -becausewecreate-regular.otf fonts-bwht -becausewelearn-regular.otf fonts-bwht -becausewementor-regular.otf fonts-bwht -becauseweorganize-regular.otf fonts-bwht bendable.ttf ttf-aenigma berenika-bold.ttf fonts-klaudia-berenika berenika-boldoblique.ttf fonts-klaudia-berenika berenika-oblique.ttf fonts-klaudia-berenika berenika.ttf fonts-klaudia-berenika +berenisadf-bold.otf ttf-adf-berenis +berenisadf-bolditalic.otf ttf-adf-berenis +berenisadf-book.otf ttf-adf-berenis +berenisadf-italic.otf ttf-adf-berenis +berenisadfcd-bold.otf ttf-adf-berenis +berenisadfcd-bolditalic.otf ttf-adf-berenis +berenisadfcd-book.otf ttf-adf-berenis +berenisadfcd-italic.otf ttf-adf-berenis +berenisadfmed-bold.otf ttf-adf-berenis +berenisadfmed-bolditalic.otf ttf-adf-berenis +berenisadfmed-italic.otf ttf-adf-berenis +berenisadfmed-regular.otf ttf-adf-berenis +berenisadfno2-bold.otf ttf-adf-berenis +berenisadfno2-bolditalic.otf ttf-adf-berenis +berenisadfno2-book.otf ttf-adf-berenis +berenisadfno2-italic.otf ttf-adf-berenis +berenisadfno2cd-bold.otf ttf-adf-berenis +berenisadfno2cd-bolditalic.otf ttf-adf-berenis +berenisadfno2cd-book.otf ttf-adf-berenis +berenisadfno2cd-italic.otf ttf-adf-berenis +berenisadfno2style-bold.otf ttf-adf-berenis +berenisadfno2style-book.otf ttf-adf-berenis berenisadfpro-bold.otf fonts-adf-berenis berenisadfpro-bolditalic.otf fonts-adf-berenis berenisadfpro-italic.otf fonts-adf-berenis berenisadfpro-regular.otf fonts-adf-berenis -berenisadfpromath-regular.otf fonts-adf-berenis +berenisadfprosc-bold.otf fonts-adf-berenis +berenisadfprosc-bolditalic.otf fonts-adf-berenis +berenisadfprosc-italic.otf fonts-adf-berenis +berenisadfprosc-regular.otf fonts-adf-berenis beteckna.ttf fonts-beteckna betecknags-bold.ttf fonts-beteckna betecknags-italic.ttf fonts-beteckna @@ -311,14 +289,7 @@ blonibld.ttf ttf-aenigma blonirex.ttf ttf-aenigma blox2.ttf ttf-aenigma -bmdohyeon_ttf.ttf fonts-woowa-bm -bmeuljirottf.ttf fonts-woowa-bm -bmhanna_11yrs_ttf.ttf fonts-woowa-bm -bmhannaair_ttf.ttf fonts-woowa-bm -bmhannapro.ttf fonts-woowa-bm -bmjua_ttf.ttf fonts-woowa-bm -bmkiranghaerang-ttf.ttf fonts-woowa-bm -bmyeonsung_ttf.ttf fonts-woowa-bm +bm-hanna.ttf fonts-woowa-hanna bobcayge.ttf ttf-aenigma bobcaygr.ttf ttf-aenigma bocuma.ttf ttf-aenigma @@ -345,10 +316,6 @@ c0419bt_.pfb xfonts-scalable c0582bt_.pfb xfonts-scalable c0583bt_.pfb xfonts-scalable -c059-bdita.otf fonts-urw-base35 -c059-bold.otf fonts-urw-base35 -c059-italic.otf fonts-urw-base35 -c059-roman.otf fonts-urw-base35 c059013d.pfb t1-cyrillic c059016d.pfb t1-cyrillic c059033d.pfb t1-cyrillic @@ -373,14 +340,11 @@ caladea-italic.ttf fonts-crosextra-caladea caladea-regular.ttf fonts-crosextra-caladea caliban.ttf fonts-georgewilliams -campania.otf fonts-campania -campania.ttf fonts-campania candystr.ttf ttf-aenigma cantarell-bold.otf fonts-cantarell -cantarell-extrabold.otf fonts-cantarell -cantarell-light.otf fonts-cantarell +cantarell-boldoblique.otf fonts-cantarell +cantarell-oblique.otf fonts-cantarell cantarell-regular.otf fonts-cantarell -cantarell-thin.otf fonts-cantarell cardo104s.ttf fonts-cardo cardob101.ttf fonts-cardo cardoi99.ttf fonts-cardo @@ -388,10 +352,6 @@ carlito-bolditalic.ttf fonts-crosextra-carlito carlito-italic.ttf fonts-crosextra-carlito carlito-regular.ttf fonts-crosextra-carlito -cascadiacode.ttf fonts-cascadia-code -cascadiacodepl.ttf fonts-cascadia-code -cascadiamono.ttf fonts-cascadia-code -cascadiamonopl.ttf fonts-cascadia-code caslon-black.ttf fonts-georgewilliams caslonbold.ttf fonts-georgewilliams caslonitalic.ttf fonts-georgewilliams @@ -411,8 +371,7 @@ charissilcompact-r.ttf fonts-sil-charis-compact chemrea.ttf ttf-aenigma chemreb.ttf ttf-aenigma -cherrybomb-regular.otf fonts-cherrybomb -chilanka-regular.otf fonts-smc-chilanka +chilanka-regular.ttf fonts-smc-chilanka chintzy.ttf ttf-aenigma chintzys.ttf ttf-aenigma chumbly.ttf ttf-aenigma @@ -422,14 +381,6 @@ clasict2.ttf ttf-aenigma claw1.ttf ttf-aenigma claw2.ttf ttf-aenigma -clearsans-bold.ttf fonts-clear-sans -clearsans-bolditalic.ttf fonts-clear-sans -clearsans-italic.ttf fonts-clear-sans -clearsans-light.ttf fonts-clear-sans -clearsans-medium.ttf fonts-clear-sans -clearsans-mediumitalic.ttf fonts-clear-sans -clearsans-regular.ttf fonts-clear-sans -clearsans-thin.ttf fonts-clear-sans cleavttr.ttf ttf-aenigma cmex10.ttf fonts-lyx cmmi10.ttf fonts-lyx @@ -481,23 +432,6 @@ comfortaa-bold.ttf fonts-comfortaa comfortaa-light.ttf fonts-comfortaa comfortaa-regular.ttf fonts-comfortaa -comicneue-angular-regular.otf fonts-comic-neue -comicneue-angular_bold.otf fonts-comic-neue -comicneue-angular_bold_oblique.otf fonts-comic-neue -comicneue-angular_light.otf fonts-comic-neue -comicneue-angular_light_oblique.otf fonts-comic-neue -comicneue-angular_oblique.otf fonts-comic-neue -comicneue-regular.otf fonts-comic-neue -comicneue_bold.otf fonts-comic-neue -comicneue_bold_oblique.otf fonts-comic-neue -comicneue_light.otf fonts-comic-neue -comicneue_light_oblique.otf fonts-comic-neue -comicneue_oblique.otf fonts-comic-neue -compagnon-bold.otf fonts-compagnon -compagnon-italic.otf fonts-compagnon -compagnon-light.otf fonts-compagnon -compagnon-medium.otf fonts-compagnon -compagnon-roman.otf fonts-compagnon compc1o.ttf ttf-aenigma compc1s.ttf ttf-aenigma compc2o.ttf ttf-aenigma @@ -517,7 +451,6 @@ crkdownr.ttf ttf-aenigma crkdwno1.ttf ttf-aenigma crkdwno2.ttf ttf-aenigma -crystal.ttf fonts-povray cupola.ttf fonts-georgewilliams cwfs.ttf fonts-cwtex-fs cwheib.ttf fonts-cwtex-heib @@ -525,8 +458,6 @@ cwming.ttf fonts-cwtex-ming cwyen.ttf fonts-cwtex-yen cyprominoan_hint.ttf fonts-ancient-scripts -cyrvetic.ttf fonts-povray -d050000l.otf fonts-urw-base35 damase.ttf fonts-mph-2b-damase dancingscript-bold.otf fonts-dancingscript dancingscript-regular.otf fonts-dancingscript @@ -598,7 +529,7 @@ dejavuserifcondensed.ttf fonts-dejavu-extra dejavuserifcondensed.ttf ttf-dejavu-extra dejima-mincho-r227.ttf fonts-dejima-mincho -delphine.ttf fonts-sjfonts +delphine.ttf ttf-sjfonts denemo.ttf ttf-denemo dented.ttf ttf-aenigma dephun2.ttf ttf-aenigma @@ -625,54 +556,54 @@ droidsansfallbackfull.ttf fonts-droid-fallback dseg14classic-bold.ttf fonts-dseg dseg14classic-bolditalic.ttf fonts-dseg -dseg14classic-italic.ttf fonts-dseg dseg14classic-light.ttf fonts-dseg dseg14classic-lightitalic.ttf fonts-dseg +dseg14classic-miniitalic.ttf fonts-dseg dseg14classic-regular.ttf fonts-dseg +dseg14classic-regularitalic.ttf fonts-dseg dseg14classicmini-bold.ttf fonts-dseg dseg14classicmini-bolditalic.ttf fonts-dseg -dseg14classicmini-italic.ttf fonts-dseg dseg14classicmini-light.ttf fonts-dseg dseg14classicmini-lightitalic.ttf fonts-dseg dseg14classicmini-regular.ttf fonts-dseg dseg14modern-bold.ttf fonts-dseg dseg14modern-bolditalic.ttf fonts-dseg -dseg14modern-italic.ttf fonts-dseg dseg14modern-light.ttf fonts-dseg dseg14modern-lightitalic.ttf fonts-dseg dseg14modern-regular.ttf fonts-dseg +dseg14modern-regularitalic.ttf fonts-dseg dseg14modernmini-bold.ttf fonts-dseg dseg14modernmini-bolditalic.ttf fonts-dseg -dseg14modernmini-italic.ttf fonts-dseg dseg14modernmini-light.ttf fonts-dseg dseg14modernmini-lightitalic.ttf fonts-dseg dseg14modernmini-regular.ttf fonts-dseg +dseg14modernmini-regularitalic.ttf fonts-dseg +dseg77seggchan-regular.ttf fonts-dseg +dseg77seggchanmini-regular.ttf fonts-dseg dseg7classic-bold.ttf fonts-dseg dseg7classic-bolditalic.ttf fonts-dseg -dseg7classic-italic.ttf fonts-dseg dseg7classic-light.ttf fonts-dseg dseg7classic-lightitalic.ttf fonts-dseg dseg7classic-regular.ttf fonts-dseg +dseg7classic-regularitalic.ttf fonts-dseg dseg7classicmini-bold.ttf fonts-dseg dseg7classicmini-bolditalic.ttf fonts-dseg -dseg7classicmini-italic.ttf fonts-dseg dseg7classicmini-light.ttf fonts-dseg dseg7classicmini-lightitalic.ttf fonts-dseg dseg7classicmini-regular.ttf fonts-dseg +dseg7classicmini-regularitalic.ttf fonts-dseg dseg7modern-bold.ttf fonts-dseg dseg7modern-bolditalic.ttf fonts-dseg -dseg7modern-italic.ttf fonts-dseg dseg7modern-light.ttf fonts-dseg dseg7modern-lightitalic.ttf fonts-dseg dseg7modern-regular.ttf fonts-dseg +dseg7modern-regularitalic.ttf fonts-dseg dseg7modernmini-bold.ttf fonts-dseg dseg7modernmini-bolditalic.ttf fonts-dseg -dseg7modernmini-italic.ttf fonts-dseg dseg7modernmini-light.ttf fonts-dseg dseg7modernmini-lightitalic.ttf fonts-dseg dseg7modernmini-regular.ttf fonts-dseg -dseg7seggchan-regular.ttf fonts-dseg -dseg7seggchanmini-regular.ttf fonts-dseg +dseg7modernmini-regularitalic.ttf fonts-dseg dsegweather.ttf fonts-dseg dustismo.ttf fonts-dustin dustismo_bold.ttf fonts-dustin @@ -685,7 +616,7 @@ dynamic.ttf ttf-aenigma dyphusio.ttf ttf-aenigma dystorqu.ttf ttf-aenigma -dyuthi-regular.ttf fonts-smc-dyuthi +dyuthi.ttf fonts-smc-dyuthi ebgaramond-initials.otf fonts-ebgaramond-extra ebgaramond-initials.ttf fonts-ebgaramond-extra ebgaramond-initialsf1.otf fonts-ebgaramond-extra @@ -698,8 +629,6 @@ ebgaramond08-regular.ttf fonts-ebgaramond-extra ebgaramond12-allsc.otf fonts-ebgaramond-extra ebgaramond12-allsc.ttf fonts-ebgaramond-extra -ebgaramond12-bold.otf fonts-ebgaramond -ebgaramond12-bold.ttf fonts-ebgaramond-extra ebgaramond12-italic.otf fonts-ebgaramond ebgaramond12-italic.ttf fonts-ebgaramond-extra ebgaramond12-regular.otf fonts-ebgaramond @@ -743,27 +672,15 @@ entplain.ttf ttf-aenigma entypo.ttf fonts-entypo esint10.ttf fonts-lyx -essays1743-bold.ttf fonts-essays1743 -essays1743-bolditalic.ttf fonts-essays1743 -essays1743-italic.ttf fonts-essays1743 -essays1743.ttf fonts-essays1743 +essays1743-bold.ttf ttf-essays1743 +essays1743-bolditalic.ttf ttf-essays1743 +essays1743-italic.ttf ttf-essays1743 +essays1743.ttf ttf-essays1743 eufm10.ttf fonts-lyx eunjin.ttf fonts-alee eunjinnakseo.ttf fonts-alee euphor3d.ttf ttf-aenigma euphoric.ttf ttf-aenigma -eurof35.ttf fonts-eurofurence -eurof36.ttf fonts-eurofurence -eurof55.ttf fonts-eurofurence -eurof56.ttf fonts-eurofurence -eurof75.ttf fonts-eurofurence -eurof76.ttf fonts-eurofurence -eurofc35.ttf fonts-eurofurence -eurofc36.ttf fonts-eurofurence -eurofc55.ttf fonts-eurofurence -eurofc56.ttf fonts-eurofurence -eurofc75.ttf fonts-eurofurence -eurofc76.ttf fonts-eurofurence euterpe.ttf fonts-oflb-euterpe exagger8.ttf ttf-aenigma extracti.ttf ttf-aenigma @@ -792,16 +709,8 @@ fbsbltc.ttf ttf-aenigma fbsbltc2.ttf ttf-aenigma femkeklaver.ttf fonts-femkeklaver -ferritecore-regular.otf fonts-ferrite-core feta.ttf ttf-denemo -fetteclassicunzfraktur.ttf fonts-cegui fidgety.ttf ttf-aenigma -firacode-bold.ttf fonts-firacode -firacode-light.ttf fonts-firacode -firacode-medium.ttf fonts-firacode -firacode-regular.ttf fonts-firacode -firacode-retina.ttf fonts-firacode -firacode-semibold.ttf fonts-firacode flatline.ttf fonts-dustin flipside.ttf ttf-aenigma fontawesome-webfont.ttf fonts-font-awesome @@ -810,8 +719,6 @@ fontawesome.otf fonts-glewlwyd fonts-sambhota-tsugring.otf fonts-sambhota-tsugring forcible.ttf ttf-aenigma -forkawesome-webfont.ttf fonts-fork-awesome -foulisgreek.ttf fonts-junicode freaktur.ttf ttf-aenigma freefarsi-bold.ttf fonts-freefarsi freefarsi-bolditalic.ttf fonts-freefarsi @@ -844,12 +751,10 @@ freeserifitalic.ttf fonts-freefont-ttf frizzed.ttf ttf-aenigma fullcomp.ttf ttf-aenigma -futharkadapted.ttf fonts-cegui galapogo.ttf ttf-aenigma galsilb.ttf fonts-sil-galatia galsilr.ttf fonts-sil-galatia galvaniz.ttf ttf-aenigma -gamaliel.ttf fonts-gamaliel gaposiso.ttf ttf-aenigma gaposiss.ttf ttf-aenigma gardiner_hint.ttf fonts-ancient-scripts @@ -865,9 +770,6 @@ gasping.ttf ttf-aenigma gather.ttf ttf-aenigma gathrgap.ttf ttf-aenigma -gayathri-bold.otf fonts-smc-gayathri -gayathri-regular.otf fonts-smc-gayathri -gayathri-thin.otf fonts-smc-gayathri gbsn00lp.ttf fonts-arphic-gbsn00lp genbasb.ttf fonts-sil-gentium-basic genbasbi.ttf fonts-sil-gentium-basic @@ -922,6 +824,10 @@ gilliusadf-conditalic.otf fonts-adf-gillius gilliusadf-italic.otf fonts-adf-gillius gilliusadf-regular.otf fonts-adf-gillius +gilliusadfcd-bold.otf ttf-adf-gillius +gilliusadfcd-bolditalic.otf ttf-adf-gillius +gilliusadfcd-italic.otf ttf-adf-gillius +gilliusadfcd-regular.otf ttf-adf-gillius gilliusadfno2-bold.otf fonts-adf-gillius gilliusadfno2-boldcond.otf fonts-adf-gillius gilliusadfno2-boldconditalic.otf fonts-adf-gillius @@ -930,11 +836,12 @@ gilliusadfno2-conditalic.otf fonts-adf-gillius gilliusadfno2-italic.otf fonts-adf-gillius gilliusadfno2-regular.otf fonts-adf-gillius +gilliusadfno2cd-bold.otf ttf-adf-gillius +gilliusadfno2cd-bolditalic.otf ttf-adf-gillius +gilliusadfno2cd-italic.otf ttf-adf-gillius +gilliusadfno2cd-regular.otf ttf-adf-gillius gkai00mp.ttf fonts-arphic-gkai00mp -glass_tty_vt220.ttf fonts-glasstty glyphicons-halflings-regular.ttf fonts-glewlwyd -glyphicons-halflings-regular.ttf fonts-glyphicons-halflings -gnutypewriter.ttf fonts-gnutypewriter go-bold-italic.ttf fonts-go go-bold.ttf fonts-go go-italic.ttf fonts-go @@ -945,14 +852,17 @@ go-mono-italic.ttf fonts-go go-mono.ttf fonts-go go-regular.ttf fonts-go -go-smallcaps-italic.ttf fonts-go -go-smallcaps.ttf fonts-go goffer.ttf fonts-senamirmir-washra gosebmp2.ttf ttf-aenigma gosebmps.ttf ttf-aenigma gothu___.ttf fonts-uralic gothub__.ttf fonts-uralic -goudybookletter1911.otf fonts-goudybookletter +goudybookletter1911bold.otf fonts-goudybookletter +goudybookletter1911bold.ttf fonts-goudybookletter +goudybookletter1911italic.otf fonts-goudybookletter +goudybookletter1911italic.ttf fonts-goudybookletter +goudybookletter1911light.otf fonts-goudybookletter +goudybookletter1911light.ttf fonts-goudybookletter gr8higts.ttf ttf-aenigma granular.ttf ttf-aenigma grapple.ttf ttf-aenigma @@ -960,7 +870,6 @@ graviseg.ttf ttf-aenigma gravitat.ttf ttf-aenigma graze.ttf ttf-aenigma -greatvibes-regular.ttf fonts-cegui grotesq.ttf ttf-aenigma grudge.ttf ttf-aenigma grudge2.ttf ttf-aenigma @@ -975,30 +884,27 @@ gyroresh.ttf ttf-aenigma gyrose.ttf ttf-aenigma gyrosesq.ttf ttf-aenigma -hack-bold.ttf fonts-hack -hack-bolditalic.ttf fonts-hack -hack-italic.ttf fonts-hack -hack-regular.ttf fonts-hack +hack-bold.otf fonts-hack-otf +hack-bold.ttf fonts-hack-ttf +hack-bolditalic.otf fonts-hack-otf +hack-bolditalic.ttf fonts-hack-ttf +hack-italic.otf fonts-hack-otf +hack-italic.ttf fonts-hack-ttf +hack-regular.otf fonts-hack-otf +hack-regular.ttf fonts-hack-ttf hackslsh.ttf ttf-aenigma hairball.ttf ttf-aenigma -hamlet-cicero12.otf fonts-gotico-antiqua -hamlet-tertia18.otf fonts-gotico-antiqua hanamina.ttf fonts-hanazono hanaminb.ttf fonts-hanazono handmedo.ttf ttf-aenigma handmeds.ttf ttf-aenigma -harmattan-bold.ttf fonts-sil-harmattan -harmattan-regular.ttf fonts-sil-harmattan +harmattan-r.ttf fonts-sil-harmattan harsinai.otf fonts-ldco harsinai.ttf fonts-ldco hassle.ttf ttf-aenigma -havana-regular.otf fonts-havana hbevel.ttf ttf-aenigma hdmaker.ttf ttf-aenigma hearts.ttf ttf-aenigma -hermit-bold.otf fonts-hermit -hermit-light.otf fonts-hermit -hermit-medium.otf fonts-hermit hidekel.otf fonts-ldco hidekel.ttf fonts-ldco hillock.ttf ttf-aenigma @@ -1018,7 +924,6 @@ ikariusadfstd-italic.otf fonts-adf-ikarius ikariusadfstd-regular.otf fonts-adf-ikarius ilits.ttf ttf-aenigma -imfepirm29p.ttf fonts-cegui imposs.ttf ttf-aenigma inconsolata.otf fonts-inconsolata induni-c-bold.otf fonts-johnsmith-induni @@ -1045,24 +950,6 @@ inevitab.ttf ttf-aenigma inkswipe.ttf ttf-aenigma inktank.ttf ttf-aenigma -inter-black.otf fonts-inter -inter-blackitalic.otf fonts-inter -inter-bold.otf fonts-inter -inter-bolditalic.otf fonts-inter -inter-extrabold.otf fonts-inter -inter-extrabolditalic.otf fonts-inter -inter-extralight.otf fonts-inter -inter-extralightitalic.otf fonts-inter -inter-italic.otf fonts-inter -inter-light.otf fonts-inter -inter-lightitalic.otf fonts-inter -inter-medium.otf fonts-inter -inter-mediumitalic.otf fonts-inter -inter-regular.otf fonts-inter -inter-semibold.otf fonts-inter -inter-semibolditalic.otf fonts-inter -inter-thin.otf fonts-inter -inter-thinitalic.otf fonts-inter intersc.ttf ttf-aenigma intersec.ttf ttf-aenigma interso.ttf ttf-aenigma @@ -1081,6 +968,7 @@ irianisadfstd-bolditalic.otf fonts-adf-irianis irianisadfstd-italic.otf fonts-adf-irianis irianisadfstd-regular.otf fonts-adf-irianis +irianisadfstylestd-bditalic.otf ttf-adf-irianis irianisadfstylestd-bold.otf fonts-adf-irianis irianisadfstylestd-bolditalic.otf fonts-adf-irianis irianisadfstylestd-italic.otf fonts-adf-irianis @@ -1105,8 +993,6 @@ jekyll.ttf ttf-aenigma jeopardi.ttf ttf-aenigma jeopardt.ttf ttf-aenigma -jessen-cicero12.otf fonts-gotico-antiqua -jessen-mittel14.otf fonts-gotico-antiqua jiret.ttf fonts-senamirmir-washra jmacscrl.ttf ttf-aenigma joltcaff.ttf ttf-aenigma @@ -1144,11 +1030,10 @@ junicode.ttf fonts-junicode junkyard.ttf fonts-dustin jupiterc.ttf ttf-aenigma -jura-bold.otf fonts-jura -jura-light.otf fonts-jura -jura-medium.otf fonts-jura -jura-regular.otf fonts-jura -jura-semibold.otf fonts-jura +jura-book.ttf fonts-jura +jura-demibold.ttf fonts-jura +jura-light.ttf fonts-jura +jura-medium.ttf fonts-jura kacstart.ttf fonts-kacst kacstbook.ttf fonts-kacst kacstdecorative.ttf fonts-kacst @@ -1175,17 +1060,11 @@ karla-bolditalic.ttf fonts-karla karla-italic.ttf fonts-karla karla-regular.ttf fonts-karla -karlatamilinclined-bold.ttf fonts-karla -karlatamilinclined-regular.ttf fonts-karla -karlatamilupright-bold.ttf fonts-karla -karlatamilupright-regular.ttf fonts-karla -karmilla-bold.ttf fonts-karmilla -karmilla-regular.ttf fonts-karmilla -karumbi-regular.ttf fonts-smc-karumbi +karumbi.ttf fonts-smc-karumbi kataacti.ttf ttf-aenigma katainac.ttf ttf-aenigma kaushanscript-regular.otf fonts-kaushanscript -keraleeyam-regular.ttf fonts-smc-keraleeyam +keraleeyam.ttf fonts-smc-keraleeyam keyrialt.ttf ttf-aenigma keyridge.ttf ttf-aenigma khmeros.ttf fonts-khmeros @@ -1225,7 +1104,6 @@ klaudia-boldoblique.ttf fonts-klaudia-berenika klaudia-oblique.ttf fonts-klaudia-berenika klaudia.ttf fonts-klaudia-berenika -klingon-piqad-hasta.ttf fonts-cegui knot.ttf ttf-aenigma komatuna-p.ttf fonts-komatuna komatuna.ttf fonts-komatuna @@ -1272,20 +1150,7 @@ lato-semibolditalic.ttf fonts-lato lato-thin.ttf fonts-lato lato-thinitalic.ttf fonts-lato -le-murmure.otf fonts-le-murmure -leaguespartan-black.otf fonts-league-spartan -leaguespartan-bold.otf fonts-league-spartan -leaguespartan-extrabold.otf fonts-league-spartan -leaguespartan-extralight.otf fonts-league-spartan -leaguespartan-light.otf fonts-league-spartan -leaguespartan-medium.otf fonts-league-spartan -leaguespartan-regular.otf fonts-league-spartan -leaguespartan-semibold.otf fonts-league-spartan leckerlione-regular.otf fonts-leckerli-one -lemonada-bold.otf fonts-lemonada -lemonada-light.otf fonts-lemonada -lemonada-regular.otf fonts-lemonada -lemonada-semibold.otf fonts-lemonada lethargi.ttf ttf-aenigma lexigulim.ttf fonts-lexi-gulim lexisaebomr.ttf fonts-lexi-saebom @@ -1452,14 +1317,15 @@ lynx.ttf ttf-aenigma macropsi.ttf ttf-aenigma madscrwl.ttf ttf-aenigma +maitreyasymbols.ttf fonts-maitreya manchufont.ttf fonts-manchufont -manjari-bold.otf fonts-smc-manjari -manjari-regular.otf fonts-smc-manjari -manjari-thin.otf fonts-smc-manjari +manjari-bold.ttf fonts-smc-manjari +manjari-regular.ttf fonts-smc-manjari +manjari-thin.ttf fonts-smc-manjari markedfool.ttf fonts-dustin marlett.ttf fonts-wine +marvosym.ttf ttf-marvosym materialdesignicons-webfont.ttf fonts-materialdesignicons-webfont -materialicons-regular.ttf fonts-material-design-icons-iconfont mathjax_ams-regular.otf fonts-mathjax mathjax_caligraphic-bold.otf fonts-mathjax mathjax_caligraphic-regular.otf fonts-mathjax @@ -1485,8 +1351,8 @@ mathjax_winchrome-regular.otf fonts-mathjax mathjax_winie6-regular.otf fonts-mathjax maya_hint.ttf fonts-ancient-scripts -meera-regular.ttf fonts-smc-meera -meerainimai-regular.ttf fonts-meera-inimai +meera.ttf fonts-smc-meera +meeratamil.ttf fonts-meera-taml mekanusadfstd-bold.otf fonts-adf-mekanus mekanusadfstd-bolditalic.otf fonts-adf-mekanus mekanusadfstd-italic.otf fonts-adf-mekanus @@ -1517,11 +1383,9 @@ mimaalt2.ttf ttf-aenigma mimafuse.ttf ttf-aenigma mincer.ttf ttf-aenigma -mingzat-regular.ttf fonts-sil-mingzat minikott.ttf ttf-aenigma minikstt.ttf ttf-aenigma misaki_gothic.ttf fonts-misaki -misaki_gothic_2nd.ttf fonts-misaki misaki_mincho.ttf fonts-misaki mishmash.ttf ttf-aenigma miso.otf fonts-ldco @@ -1547,37 +1411,6 @@ mondulkiri-i.ttf fonts-sil-mondulkiri mondulkiri-r.ttf fonts-sil-mondulkiri monkphon.ttf ttf-aenigma -monof55.ttf fonts-monofur -monof56.ttf fonts-monofur -monoid-bold-halfloose.ttf fonts-monoid-halfloose -monoid-bold-halftight.ttf fonts-monoid-halftight -monoid-bold-loose.ttf fonts-monoid-loose -monoid-bold-tight.ttf fonts-monoid-tight -monoid-bold.ttf fonts-monoid -monoid-italic-halfloose.ttf fonts-monoid-halfloose -monoid-italic-halftight.ttf fonts-monoid-halftight -monoid-italic-loose.ttf fonts-monoid-loose -monoid-italic-tight.ttf fonts-monoid-tight -monoid-italic.ttf fonts-monoid -monoid-regular-halfloose.ttf fonts-monoid-halfloose -monoid-regular-halftight.ttf fonts-monoid-halftight -monoid-regular-loose.ttf fonts-monoid-loose -monoid-regular-tight.ttf fonts-monoid-tight -monoid-regular.ttf fonts-monoid -monoid-retina-halfloose.ttf fonts-monoid-halfloose -monoid-retina-halftight.ttf fonts-monoid-halftight -monoid-retina-loose.ttf fonts-monoid-loose -monoid-retina-tight.ttf fonts-monoid-tight -monoid-retina.ttf fonts-monoid -monoisome-regular-halfloose.ttf fonts-monoid-halfloose -monoisome-regular-halftight.ttf fonts-monoid-halftight -monoisome-regular-loose.ttf fonts-monoid-loose -monoisome-regular-tight.ttf fonts-monoid-tight -monoisome-regular.ttf fonts-monoid -mononoki-bold.ttf fonts-mononoki -mononoki-bolditalic.ttf fonts-mononoki -mononoki-italic.ttf fonts-mononoki -mononoki-regular.ttf fonts-mononoki monou___.ttf fonts-uralic moronmis.ttf ttf-aenigma mplus-1c-black.ttf fonts-mplus @@ -1655,7 +1488,6 @@ nafeesweb.ttf fonts-nafees nakula.ttf fonts-nakula nanosecw.ttf ttf-aenigma -nanumbarungothic-yethangul.ttf fonts-nanum-extra nanumbarungothic.ttf fonts-nanum nanumbarungothicbold.ttf fonts-nanum nanumbarungothiclight.ttf fonts-nanum-extra @@ -1665,27 +1497,20 @@ nanumbrush.ttf fonts-nanum-extra nanumgothic.ttf fonts-nanum nanumgothicbold.ttf fonts-nanum -nanumgothiccoding.ttf fonts-nanum -nanumgothiccodingbold.ttf fonts-nanum +nanumgothiccoding-bold.ttf fonts-nanum-coding +nanumgothiccoding.ttf fonts-nanum-coding nanumgothiceco.ttf fonts-nanum-eco nanumgothicecobold.ttf fonts-nanum-eco nanumgothicecoextrabold.ttf fonts-nanum-eco -nanumgothicecor.ttf fonts-nanum-extra nanumgothicextrabold.ttf fonts-nanum-extra nanumgothiclight.ttf fonts-nanum-extra -nanummyeongjo-yethangul.ttf fonts-nanum-extra nanummyeongjo.ttf fonts-nanum nanummyeongjobold.ttf fonts-nanum nanummyeongjoeco.ttf fonts-nanum-eco nanummyeongjoecobold.ttf fonts-nanum-eco nanummyeongjoecoextrabold.ttf fonts-nanum-eco -nanummyeongjoecor.ttf fonts-nanum-extra nanummyeongjoextrabold.ttf fonts-nanum-extra nanumpen.ttf fonts-nanum-extra -nanumsquare_acb.ttf fonts-nanum-extra -nanumsquare_aceb.ttf fonts-nanum-extra -nanumsquare_acl.ttf fonts-nanum-extra -nanumsquare_acr.ttf fonts-nanum-extra nanumsquareb.ttf fonts-nanum nanumsquareeb.ttf fonts-nanum-extra nanumsquarel.ttf fonts-nanum-extra @@ -1703,22 +1528,6 @@ neural.ttf ttf-aenigma neuralol.ttf ttf-aenigma nilus_hint.ttf fonts-ancient-scripts -nimbusmonops-bold.otf fonts-urw-base35 -nimbusmonops-bolditalic.otf fonts-urw-base35 -nimbusmonops-italic.otf fonts-urw-base35 -nimbusmonops-regular.otf fonts-urw-base35 -nimbusroman-bold.otf fonts-urw-base35 -nimbusroman-bolditalic.otf fonts-urw-base35 -nimbusroman-italic.otf fonts-urw-base35 -nimbusroman-regular.otf fonts-urw-base35 -nimbussans-bold.otf fonts-urw-base35 -nimbussans-bolditalic.otf fonts-urw-base35 -nimbussans-italic.otf fonts-urw-base35 -nimbussans-regular.otf fonts-urw-base35 -nimbussansnarrow-bold.otf fonts-urw-base35 -nimbussansnarrow-boldoblique.otf fonts-urw-base35 -nimbussansnarrow-oblique.otf fonts-urw-base35 -nimbussansnarrow-regular.otf fonts-urw-base35 noam.otf fonts-ldco noam.ttf fonts-ldco nominal.ttf ttf-aenigma @@ -1736,2080 +1545,211 @@ norasi.ttf fonts-tlwg-norasi-ttf nostalgi.ttf ttf-aenigma notocoloremoji.ttf fonts-noto-color-emoji -notokufiarabic-black.ttf fonts-noto-unhinted -notokufiarabic-bold.ttf fonts-noto-core -notokufiarabic-extrabold.ttf fonts-noto-unhinted -notokufiarabic-extralight.ttf fonts-noto-unhinted -notokufiarabic-light.ttf fonts-noto-unhinted -notokufiarabic-medium.ttf fonts-noto-extra -notokufiarabic-regular.ttf fonts-noto-core -notokufiarabic-semibold.ttf fonts-noto-extra -notokufiarabic-thin.ttf fonts-noto-unhinted +notokufiarabic-bold.ttf fonts-noto-hinted +notokufiarabic-regular.ttf fonts-noto-hinted notomono-regular.ttf fonts-noto-mono -notomusic-regular.ttf fonts-noto-core -notonaskharabic-bold.ttf fonts-noto-core -notonaskharabic-regular.ttf fonts-noto-core -notonaskharabicui-bold.ttf fonts-noto-ui-core -notonaskharabicui-regular.ttf fonts-noto-ui-core -notonastaliqurdu-bold.ttf fonts-noto-core -notonastaliqurdu-regular.ttf fonts-noto-core -notosans-black.ttf fonts-noto-extra -notosans-blackitalic.ttf fonts-noto-extra -notosans-bold.ttf fonts-noto-core -notosans-bolditalic.ttf fonts-noto-core -notosans-condensed.ttf fonts-noto-extra -notosans-condensedblack.ttf fonts-noto-extra -notosans-condensedblackitalic.ttf fonts-noto-extra -notosans-condensedbold.ttf fonts-noto-extra -notosans-condensedbolditalic.ttf fonts-noto-extra -notosans-condensedextrabold.ttf fonts-noto-extra -notosans-condensedextrabolditalic.ttf fonts-noto-extra -notosans-condensedextralight.ttf fonts-noto-extra -notosans-condensedextralightitalic.ttf fonts-noto-extra -notosans-condenseditalic.ttf fonts-noto-extra -notosans-condensedlight.ttf fonts-noto-extra -notosans-condensedlightitalic.ttf fonts-noto-extra -notosans-condensedmedium.ttf fonts-noto-extra -notosans-condensedmediumitalic.ttf fonts-noto-extra -notosans-condensedsemibold.ttf fonts-noto-extra -notosans-condensedsemibolditalic.ttf fonts-noto-extra -notosans-condensedthin.ttf fonts-noto-extra -notosans-condensedthinitalic.ttf fonts-noto-extra -notosans-extrabold.ttf fonts-noto-extra -notosans-extrabolditalic.ttf fonts-noto-extra -notosans-extracondensed.ttf fonts-noto-extra -notosans-extracondensedblack.ttf fonts-noto-extra -notosans-extracondensedblackitalic.ttf fonts-noto-extra -notosans-extracondensedbold.ttf fonts-noto-extra -notosans-extracondensedbolditalic.ttf fonts-noto-extra -notosans-extracondensedextrabold.ttf fonts-noto-extra -notosans-extracondensedextrabolditalic.ttf fonts-noto-extra -notosans-extracondensedextralight.ttf fonts-noto-extra -notosans-extracondensedextralightitalic.ttf fonts-noto-extra -notosans-extracondenseditalic.ttf fonts-noto-extra -notosans-extracondensedlight.ttf fonts-noto-extra -notosans-extracondensedlightitalic.ttf fonts-noto-extra -notosans-extracondensedmedium.ttf fonts-noto-extra -notosans-extracondensedmediumitalic.ttf fonts-noto-extra -notosans-extracondensedsemibold.ttf fonts-noto-extra -notosans-extracondensedsemibolditalic.ttf fonts-noto-extra -notosans-extracondensedthin.ttf fonts-noto-extra -notosans-extracondensedthinitalic.ttf fonts-noto-extra -notosans-extralight.ttf fonts-noto-extra -notosans-extralightitalic.ttf fonts-noto-extra -notosans-italic.ttf fonts-noto-core -notosans-light.ttf fonts-noto-extra -notosans-lightitalic.ttf fonts-noto-extra -notosans-medium.ttf fonts-noto-extra -notosans-mediumitalic.ttf fonts-noto-extra -notosans-regular.ttf fonts-noto-core -notosans-semibold.ttf fonts-noto-extra -notosans-semibolditalic.ttf fonts-noto-extra -notosans-semicondensed.ttf fonts-noto-extra -notosans-semicondensedblack.ttf fonts-noto-extra -notosans-semicondensedblackitalic.ttf fonts-noto-extra -notosans-semicondensedbold.ttf fonts-noto-extra -notosans-semicondensedbolditalic.ttf fonts-noto-extra -notosans-semicondensedextrabold.ttf fonts-noto-extra -notosans-semicondensedextrabolditalic.ttf fonts-noto-extra -notosans-semicondensedextralight.ttf fonts-noto-extra -notosans-semicondensedextralightitalic.ttf fonts-noto-extra -notosans-semicondenseditalic.ttf fonts-noto-extra -notosans-semicondensedlight.ttf fonts-noto-extra -notosans-semicondensedlightitalic.ttf fonts-noto-extra -notosans-semicondensedmedium.ttf fonts-noto-extra -notosans-semicondensedmediumitalic.ttf fonts-noto-extra -notosans-semicondensedsemibold.ttf fonts-noto-extra -notosans-semicondensedsemibolditalic.ttf fonts-noto-extra -notosans-semicondensedthin.ttf fonts-noto-extra -notosans-semicondensedthinitalic.ttf fonts-noto-extra -notosans-thin.ttf fonts-noto-extra -notosans-thinitalic.ttf fonts-noto-extra -notosansadlam-regular.ttf fonts-noto-core -notosansadlamunjoined-regular.ttf fonts-noto-core -notosansanatolianhieroglyphs-regular.ttf fonts-noto-core -notosansarabic-black.ttf fonts-noto-extra -notosansarabic-bold.ttf fonts-noto-core -notosansarabic-condensed.ttf fonts-noto-extra -notosansarabic-condensedblack.ttf fonts-noto-extra -notosansarabic-condensedbold.ttf fonts-noto-extra -notosansarabic-condensedextrabold.ttf fonts-noto-extra -notosansarabic-condensedextralight.ttf fonts-noto-extra -notosansarabic-condensedlight.ttf fonts-noto-extra -notosansarabic-condensedmedium.ttf fonts-noto-extra -notosansarabic-condensedsemibold.ttf fonts-noto-extra -notosansarabic-condensedthin.ttf fonts-noto-extra -notosansarabic-extrabold.ttf fonts-noto-extra -notosansarabic-extracondensed.ttf fonts-noto-extra -notosansarabic-extracondensedblack.ttf fonts-noto-extra -notosansarabic-extracondensedbold.ttf fonts-noto-extra -notosansarabic-extracondensedextrabold.ttf fonts-noto-extra -notosansarabic-extracondensedextralight.ttf fonts-noto-extra -notosansarabic-extracondensedlight.ttf fonts-noto-extra -notosansarabic-extracondensedmedium.ttf fonts-noto-extra -notosansarabic-extracondensedsemibold.ttf fonts-noto-extra -notosansarabic-extracondensedthin.ttf fonts-noto-extra -notosansarabic-extralight.ttf fonts-noto-extra -notosansarabic-light.ttf fonts-noto-extra -notosansarabic-medium.ttf fonts-noto-extra -notosansarabic-regular.ttf fonts-noto-core -notosansarabic-semibold.ttf fonts-noto-extra -notosansarabic-semicondensed.ttf fonts-noto-extra -notosansarabic-semicondensedblack.ttf fonts-noto-extra -notosansarabic-semicondensedbold.ttf fonts-noto-extra -notosansarabic-semicondensedextrabold.ttf fonts-noto-extra -notosansarabic-semicondensedextralight.ttf fonts-noto-extra -notosansarabic-semicondensedlight.ttf fonts-noto-extra -notosansarabic-semicondensedmedium.ttf fonts-noto-extra -notosansarabic-semicondensedsemibold.ttf fonts-noto-extra -notosansarabic-semicondensedthin.ttf fonts-noto-extra -notosansarabic-thin.ttf fonts-noto-extra -notosansarabicui-black.ttf fonts-noto-ui-extra -notosansarabicui-bold.ttf fonts-noto-ui-core -notosansarabicui-condensed.ttf fonts-noto-ui-extra -notosansarabicui-condensedblack.ttf fonts-noto-ui-extra -notosansarabicui-condensedbold.ttf fonts-noto-ui-extra -notosansarabicui-condensedextrabold.ttf fonts-noto-ui-extra -notosansarabicui-condensedextralight.ttf fonts-noto-ui-extra -notosansarabicui-condensedlight.ttf fonts-noto-ui-extra -notosansarabicui-condensedmedium.ttf fonts-noto-ui-extra -notosansarabicui-condensedsemibold.ttf fonts-noto-ui-extra -notosansarabicui-condensedthin.ttf fonts-noto-ui-extra -notosansarabicui-extrabold.ttf fonts-noto-ui-extra -notosansarabicui-extracondensed.ttf fonts-noto-ui-extra -notosansarabicui-extracondensedblack.ttf fonts-noto-ui-extra -notosansarabicui-extracondensedbold.ttf fonts-noto-ui-extra -notosansarabicui-extracondensedextrabold.ttf fonts-noto-ui-extra -notosansarabicui-extracondensedextralight.ttf fonts-noto-ui-extra -notosansarabicui-extracondensedlight.ttf fonts-noto-ui-extra -notosansarabicui-extracondensedmedium.ttf fonts-noto-ui-extra -notosansarabicui-extracondensedsemibold.ttf fonts-noto-ui-extra -notosansarabicui-extracondensedthin.ttf fonts-noto-ui-extra -notosansarabicui-extralight.ttf fonts-noto-ui-extra -notosansarabicui-light.ttf fonts-noto-ui-extra -notosansarabicui-medium.ttf fonts-noto-ui-extra -notosansarabicui-regular.ttf fonts-noto-ui-core -notosansarabicui-semibold.ttf fonts-noto-ui-extra -notosansarabicui-semicondensed.ttf fonts-noto-ui-extra -notosansarabicui-semicondensedblack.ttf fonts-noto-ui-extra -notosansarabicui-semicondensedbold.ttf fonts-noto-ui-extra -notosansarabicui-semicondensedextrabold.ttf fonts-noto-ui-extra -notosansarabicui-semicondensedextralight.ttf fonts-noto-ui-extra -notosansarabicui-semicondensedlight.ttf fonts-noto-ui-extra -notosansarabicui-semicondensedmedium.ttf fonts-noto-ui-extra -notosansarabicui-semicondensedsemibold.ttf fonts-noto-ui-extra -notosansarabicui-semicondensedthin.ttf fonts-noto-ui-extra -notosansarabicui-thin.ttf fonts-noto-ui-extra -notosansarmenian-black.ttf fonts-noto-extra -notosansarmenian-bold.ttf fonts-noto-core -notosansarmenian-condensed.ttf fonts-noto-extra -notosansarmenian-condensedblack.ttf fonts-noto-extra -notosansarmenian-condensedbold.ttf fonts-noto-extra -notosansarmenian-condensedextrabold.ttf fonts-noto-extra -notosansarmenian-condensedextralight.ttf fonts-noto-extra -notosansarmenian-condensedlight.ttf fonts-noto-extra -notosansarmenian-condensedmedium.ttf fonts-noto-extra -notosansarmenian-condensedsemibold.ttf fonts-noto-extra -notosansarmenian-condensedthin.ttf fonts-noto-extra -notosansarmenian-extrabold.ttf fonts-noto-extra -notosansarmenian-extracondensed.ttf fonts-noto-extra -notosansarmenian-extracondensedblack.ttf fonts-noto-extra -notosansarmenian-extracondensedbold.ttf fonts-noto-extra -notosansarmenian-extracondensedextrabold.ttf fonts-noto-extra -notosansarmenian-extracondensedextralight.ttf fonts-noto-extra -notosansarmenian-extracondensedlight.ttf fonts-noto-extra -notosansarmenian-extracondensedmedium.ttf fonts-noto-extra -notosansarmenian-extracondensedsemibold.ttf fonts-noto-extra -notosansarmenian-extracondensedthin.ttf fonts-noto-extra -notosansarmenian-extralight.ttf fonts-noto-extra -notosansarmenian-light.ttf fonts-noto-extra -notosansarmenian-medium.ttf fonts-noto-extra -notosansarmenian-regular.ttf fonts-noto-core -notosansarmenian-semibold.ttf fonts-noto-extra -notosansarmenian-semicondensed.ttf fonts-noto-extra -notosansarmenian-semicondensedblack.ttf fonts-noto-extra -notosansarmenian-semicondensedbold.ttf fonts-noto-extra -notosansarmenian-semicondensedextrabold.ttf fonts-noto-extra -notosansarmenian-semicondensedextralight.ttf fonts-noto-extra -notosansarmenian-semicondensedlight.ttf fonts-noto-extra -notosansarmenian-semicondensedmedium.ttf fonts-noto-extra -notosansarmenian-semicondensedsemibold.ttf fonts-noto-extra -notosansarmenian-semicondensedthin.ttf fonts-noto-extra -notosansarmenian-thin.ttf fonts-noto-extra -notosansavestan-regular.ttf fonts-noto-core -notosansbamum-regular.ttf fonts-noto-core -notosansbassavah-regular.ttf fonts-noto-core -notosansbatak-regular.ttf fonts-noto-core -notosansbengali-black.ttf fonts-noto-extra -notosansbengali-bold.ttf fonts-noto-core -notosansbengali-condensed.ttf fonts-noto-extra -notosansbengali-extrabold.ttf fonts-noto-extra -notosansbengali-extracondensed.ttf fonts-noto-extra -notosansbengali-extralight.ttf fonts-noto-extra -notosansbengali-light.ttf fonts-noto-extra -notosansbengali-medium.ttf fonts-noto-extra -notosansbengali-regular.ttf fonts-noto-core -notosansbengali-semibold.ttf fonts-noto-extra -notosansbengali-semicondensed.ttf fonts-noto-extra -notosansbengali-thin.ttf fonts-noto-extra -notosansbengaliui-black.ttf fonts-noto-ui-extra -notosansbengaliui-bold.ttf fonts-noto-ui-core -notosansbengaliui-condensed.ttf fonts-noto-ui-extra -notosansbengaliui-extrabold.ttf fonts-noto-ui-extra -notosansbengaliui-extracondensed.ttf fonts-noto-ui-extra -notosansbengaliui-extralight.ttf fonts-noto-ui-extra -notosansbengaliui-light.ttf fonts-noto-ui-extra -notosansbengaliui-medium.ttf fonts-noto-ui-extra -notosansbengaliui-regular.ttf fonts-noto-ui-core -notosansbengaliui-semibold.ttf fonts-noto-ui-extra -notosansbengaliui-semicondensed.ttf fonts-noto-ui-extra -notosansbengaliui-thin.ttf fonts-noto-ui-extra -notosansbhaiksuki-regular.ttf fonts-noto-core -notosansbrahmi-regular.ttf fonts-noto-core -notosansbuginese-regular.ttf fonts-noto-core -notosansbuhid-regular.ttf fonts-noto-core -notosanscanadianaboriginal-black.ttf fonts-noto-extra -notosanscanadianaboriginal-bold.ttf fonts-noto-core -notosanscanadianaboriginal-extrabold.ttf fonts-noto-extra -notosanscanadianaboriginal-extralight.ttf fonts-noto-extra -notosanscanadianaboriginal-light.ttf fonts-noto-extra -notosanscanadianaboriginal-medium.ttf fonts-noto-extra -notosanscanadianaboriginal-regular.ttf fonts-noto-core -notosanscanadianaboriginal-semibold.ttf fonts-noto-extra -notosanscanadianaboriginal-thin.ttf fonts-noto-extra -notosanscarian-regular.ttf fonts-noto-core -notosanscaucasianalbanian-regular.ttf fonts-noto-core -notosanschakma-regular.ttf fonts-noto-core -notosanscham-black.ttf fonts-noto-extra -notosanscham-bold.ttf fonts-noto-core -notosanscham-extrabold.ttf fonts-noto-extra -notosanscham-extralight.ttf fonts-noto-extra -notosanscham-light.ttf fonts-noto-extra -notosanscham-medium.ttf fonts-noto-extra -notosanscham-regular.ttf fonts-noto-core -notosanscham-semibold.ttf fonts-noto-extra -notosanscham-thin.ttf fonts-noto-extra -notosanscherokee-black.ttf fonts-noto-extra -notosanscherokee-bold.ttf fonts-noto-core -notosanscherokee-extrabold.ttf fonts-noto-extra -notosanscherokee-extralight.ttf fonts-noto-extra -notosanscherokee-light.ttf fonts-noto-extra -notosanscherokee-medium.ttf fonts-noto-extra -notosanscherokee-regular.ttf fonts-noto-core -notosanscherokee-semibold.ttf fonts-noto-extra -notosanscherokee-thin.ttf fonts-noto-extra -notosanscoptic-regular.ttf fonts-noto-core -notosanscuneiform-regular.ttf fonts-noto-core -notosanscypriot-regular.ttf fonts-noto-core -notosansdeseret-regular.ttf fonts-noto-core -notosansdevanagari-black.ttf fonts-noto-extra -notosansdevanagari-bold.ttf fonts-noto-core -notosansdevanagari-condensed.ttf fonts-noto-extra -notosansdevanagari-condensedblack.ttf fonts-noto-extra -notosansdevanagari-condensedbold.ttf fonts-noto-extra -notosansdevanagari-condensedextrabold.ttf fonts-noto-extra -notosansdevanagari-condensedextralight.ttf fonts-noto-extra -notosansdevanagari-condensedlight.ttf fonts-noto-extra -notosansdevanagari-condensedmedium.ttf fonts-noto-extra -notosansdevanagari-condensedsemibold.ttf fonts-noto-extra -notosansdevanagari-condensedthin.ttf fonts-noto-extra -notosansdevanagari-extrabold.ttf fonts-noto-extra -notosansdevanagari-extracondensed.ttf fonts-noto-extra -notosansdevanagari-extracondensedblack.ttf fonts-noto-extra -notosansdevanagari-extracondensedbold.ttf fonts-noto-extra -notosansdevanagari-extracondensedextrabold.ttf fonts-noto-extra -notosansdevanagari-extracondensedextralight.ttf fonts-noto-extra -notosansdevanagari-extracondensedlight.ttf fonts-noto-extra -notosansdevanagari-extracondensedmedium.ttf fonts-noto-extra -notosansdevanagari-extracondensedsemibold.ttf fonts-noto-extra -notosansdevanagari-extracondensedthin.ttf fonts-noto-extra -notosansdevanagari-extralight.ttf fonts-noto-extra -notosansdevanagari-light.ttf fonts-noto-extra -notosansdevanagari-medium.ttf fonts-noto-extra -notosansdevanagari-regular.ttf fonts-noto-core -notosansdevanagari-semibold.ttf fonts-noto-extra -notosansdevanagari-semicondensed.ttf fonts-noto-extra -notosansdevanagari-semicondensedblack.ttf fonts-noto-extra -notosansdevanagari-semicondensedbold.ttf fonts-noto-extra -notosansdevanagari-semicondensedextrabold.ttf fonts-noto-extra -notosansdevanagari-semicondensedextralight.ttf fonts-noto-extra -notosansdevanagari-semicondensedlight.ttf fonts-noto-extra -notosansdevanagari-semicondensedmedium.ttf fonts-noto-extra -notosansdevanagari-semicondensedsemibold.ttf fonts-noto-extra -notosansdevanagari-semicondensedthin.ttf fonts-noto-extra -notosansdevanagari-thin.ttf fonts-noto-extra -notosansdevanagariui-black.ttf fonts-noto-ui-extra -notosansdevanagariui-bold.ttf fonts-noto-ui-core -notosansdevanagariui-condensed.ttf fonts-noto-ui-extra -notosansdevanagariui-condensedblack.ttf fonts-noto-ui-extra -notosansdevanagariui-condensedbold.ttf fonts-noto-ui-extra -notosansdevanagariui-condensedextrabold.ttf fonts-noto-ui-extra -notosansdevanagariui-condensedextralight.ttf fonts-noto-ui-extra -notosansdevanagariui-condensedlight.ttf fonts-noto-ui-extra -notosansdevanagariui-condensedmedium.ttf fonts-noto-ui-extra -notosansdevanagariui-condensedsemibold.ttf fonts-noto-ui-extra -notosansdevanagariui-condensedthin.ttf fonts-noto-ui-extra -notosansdevanagariui-extrabold.ttf fonts-noto-ui-extra -notosansdevanagariui-extracondensed.ttf fonts-noto-ui-extra -notosansdevanagariui-extracondensedblack.ttf fonts-noto-ui-extra -notosansdevanagariui-extracondensedbold.ttf fonts-noto-ui-extra -notosansdevanagariui-extracondensedextrabold.ttf fonts-noto-ui-extra -notosansdevanagariui-extracondensedextralight.ttf fonts-noto-ui-extra -notosansdevanagariui-extracondensedlight.ttf fonts-noto-ui-extra -notosansdevanagariui-extracondensedmedium.ttf fonts-noto-ui-extra -notosansdevanagariui-extracondensedsemibold.ttf fonts-noto-ui-extra -notosansdevanagariui-extracondensedthin.ttf fonts-noto-ui-extra -notosansdevanagariui-extralight.ttf fonts-noto-ui-extra -notosansdevanagariui-light.ttf fonts-noto-ui-extra -notosansdevanagariui-medium.ttf fonts-noto-ui-extra -notosansdevanagariui-regular.ttf fonts-noto-ui-core -notosansdevanagariui-semibold.ttf fonts-noto-ui-extra -notosansdevanagariui-semicondensed.ttf fonts-noto-ui-extra -notosansdevanagariui-semicondensedblack.ttf fonts-noto-ui-extra -notosansdevanagariui-semicondensedbold.ttf fonts-noto-ui-extra -notosansdevanagariui-semicondensedextrabold.ttf fonts-noto-ui-extra -notosansdevanagariui-semicondensedextralight.ttf fonts-noto-ui-extra -notosansdevanagariui-semicondensedlight.ttf fonts-noto-ui-extra -notosansdevanagariui-semicondensedmedium.ttf fonts-noto-ui-extra -notosansdevanagariui-semicondensedsemibold.ttf fonts-noto-ui-extra -notosansdevanagariui-semicondensedthin.ttf fonts-noto-ui-extra -notosansdevanagariui-thin.ttf fonts-noto-ui-extra -notosansdisplay-black.ttf fonts-noto-extra -notosansdisplay-blackitalic.ttf fonts-noto-extra -notosansdisplay-bold.ttf fonts-noto-core -notosansdisplay-bolditalic.ttf fonts-noto-core -notosansdisplay-condensed.ttf fonts-noto-extra -notosansdisplay-condensedblack.ttf fonts-noto-extra -notosansdisplay-condensedblackitalic.ttf fonts-noto-extra -notosansdisplay-condensedbold.ttf fonts-noto-extra -notosansdisplay-condensedbolditalic.ttf fonts-noto-extra -notosansdisplay-condensedextrabold.ttf fonts-noto-extra -notosansdisplay-condensedextrabolditalic.ttf fonts-noto-extra -notosansdisplay-condensedextralight.ttf fonts-noto-extra -notosansdisplay-condensedextralightitalic.ttf fonts-noto-extra -notosansdisplay-condenseditalic.ttf fonts-noto-extra -notosansdisplay-condensedlight.ttf fonts-noto-extra -notosansdisplay-condensedlightitalic.ttf fonts-noto-extra -notosansdisplay-condensedmedium.ttf fonts-noto-extra -notosansdisplay-condensedmediumitalic.ttf fonts-noto-extra -notosansdisplay-condensedsemibold.ttf fonts-noto-extra -notosansdisplay-condensedsemibolditalic.ttf fonts-noto-extra -notosansdisplay-condensedthin.ttf fonts-noto-extra -notosansdisplay-condensedthinitalic.ttf fonts-noto-extra -notosansdisplay-extrabold.ttf fonts-noto-extra -notosansdisplay-extrabolditalic.ttf fonts-noto-extra -notosansdisplay-extracondensed.ttf fonts-noto-extra -notosansdisplay-extracondensedblack.ttf fonts-noto-extra -notosansdisplay-extracondensedblackitalic.ttf fonts-noto-extra -notosansdisplay-extracondensedbold.ttf fonts-noto-extra -notosansdisplay-extracondensedbolditalic.ttf fonts-noto-extra -notosansdisplay-extracondensedextrabold.ttf fonts-noto-extra -notosansdisplay-extracondensedextrabolditalic.ttf fonts-noto-extra -notosansdisplay-extracondensedextralight.ttf fonts-noto-extra -notosansdisplay-extracondensedextralightitalic.ttf fonts-noto-extra -notosansdisplay-extracondenseditalic.ttf fonts-noto-extra -notosansdisplay-extracondensedlight.ttf fonts-noto-extra -notosansdisplay-extracondensedlightitalic.ttf fonts-noto-extra -notosansdisplay-extracondensedmedium.ttf fonts-noto-extra -notosansdisplay-extracondensedmediumitalic.ttf fonts-noto-extra -notosansdisplay-extracondensedsemibold.ttf fonts-noto-extra -notosansdisplay-extracondensedsemibolditalic.ttf fonts-noto-extra -notosansdisplay-extracondensedthin.ttf fonts-noto-extra -notosansdisplay-extracondensedthinitalic.ttf fonts-noto-extra -notosansdisplay-extralight.ttf fonts-noto-extra -notosansdisplay-extralightitalic.ttf fonts-noto-extra -notosansdisplay-italic.ttf fonts-noto-core -notosansdisplay-light.ttf fonts-noto-extra -notosansdisplay-lightitalic.ttf fonts-noto-extra -notosansdisplay-medium.ttf fonts-noto-extra -notosansdisplay-mediumitalic.ttf fonts-noto-extra -notosansdisplay-regular.ttf fonts-noto-core -notosansdisplay-semibold.ttf fonts-noto-extra -notosansdisplay-semibolditalic.ttf fonts-noto-extra -notosansdisplay-semicondensed.ttf fonts-noto-extra -notosansdisplay-semicondensedblack.ttf fonts-noto-extra -notosansdisplay-semicondensedblackitalic.ttf fonts-noto-extra -notosansdisplay-semicondensedbold.ttf fonts-noto-extra -notosansdisplay-semicondensedbolditalic.ttf fonts-noto-extra -notosansdisplay-semicondensedextrabold.ttf fonts-noto-extra -notosansdisplay-semicondensedextrabolditalic.ttf fonts-noto-extra -notosansdisplay-semicondensedextralight.ttf fonts-noto-extra -notosansdisplay-semicondensedextralightitalic.ttf fonts-noto-extra -notosansdisplay-semicondenseditalic.ttf fonts-noto-extra -notosansdisplay-semicondensedlight.ttf fonts-noto-extra -notosansdisplay-semicondensedlightitalic.ttf fonts-noto-extra -notosansdisplay-semicondensedmedium.ttf fonts-noto-extra -notosansdisplay-semicondensedmediumitalic.ttf fonts-noto-extra -notosansdisplay-semicondensedsemibold.ttf fonts-noto-extra -notosansdisplay-semicondensedsemibolditalic.ttf fonts-noto-extra -notosansdisplay-semicondensedthin.ttf fonts-noto-extra -notosansdisplay-semicondensedthinitalic.ttf fonts-noto-extra -notosansdisplay-thin.ttf fonts-noto-extra -notosansdisplay-thinitalic.ttf fonts-noto-extra -notosansduployan-regular.ttf fonts-noto-core -notosansegyptianhieroglyphs-regular.ttf fonts-noto-core -notosanselbasan-regular.ttf fonts-noto-core -notosansethiopic-black.ttf fonts-noto-extra -notosansethiopic-bold.ttf fonts-noto-core -notosansethiopic-condensed.ttf fonts-noto-extra -notosansethiopic-condensedblack.ttf fonts-noto-extra -notosansethiopic-condensedbold.ttf fonts-noto-extra -notosansethiopic-condensedextrabold.ttf fonts-noto-extra -notosansethiopic-condensedextralight.ttf fonts-noto-extra -notosansethiopic-condensedlight.ttf fonts-noto-extra -notosansethiopic-condensedmedium.ttf fonts-noto-extra -notosansethiopic-condensedsemibold.ttf fonts-noto-extra -notosansethiopic-condensedthin.ttf fonts-noto-extra -notosansethiopic-extrabold.ttf fonts-noto-extra -notosansethiopic-extracondensed.ttf fonts-noto-extra -notosansethiopic-extracondensedblack.ttf fonts-noto-extra -notosansethiopic-extracondensedbold.ttf fonts-noto-extra -notosansethiopic-extracondensedextrabold.ttf fonts-noto-extra -notosansethiopic-extracondensedextralight.ttf fonts-noto-extra -notosansethiopic-extracondensedlight.ttf fonts-noto-extra -notosansethiopic-extracondensedmedium.ttf fonts-noto-extra -notosansethiopic-extracondensedsemibold.ttf fonts-noto-extra -notosansethiopic-extracondensedthin.ttf fonts-noto-extra -notosansethiopic-extralight.ttf fonts-noto-extra -notosansethiopic-light.ttf fonts-noto-extra -notosansethiopic-medium.ttf fonts-noto-extra -notosansethiopic-regular.ttf fonts-noto-core -notosansethiopic-semibold.ttf fonts-noto-extra -notosansethiopic-semicondensed.ttf fonts-noto-extra -notosansethiopic-semicondensedblack.ttf fonts-noto-extra -notosansethiopic-semicondensedbold.ttf fonts-noto-extra -notosansethiopic-semicondensedextrabold.ttf fonts-noto-extra -notosansethiopic-semicondensedextralight.ttf fonts-noto-extra -notosansethiopic-semicondensedlight.ttf fonts-noto-extra -notosansethiopic-semicondensedmedium.ttf fonts-noto-extra -notosansethiopic-semicondensedsemibold.ttf fonts-noto-extra -notosansethiopic-semicondensedthin.ttf fonts-noto-extra -notosansethiopic-thin.ttf fonts-noto-extra -notosansgeorgian-black.ttf fonts-noto-extra -notosansgeorgian-bold.ttf fonts-noto-core -notosansgeorgian-condensed.ttf fonts-noto-extra -notosansgeorgian-condensedblack.ttf fonts-noto-extra -notosansgeorgian-condensedbold.ttf fonts-noto-extra -notosansgeorgian-condensedextrabold.ttf fonts-noto-extra -notosansgeorgian-condensedextralight.ttf fonts-noto-extra -notosansgeorgian-condensedlight.ttf fonts-noto-extra -notosansgeorgian-condensedmedium.ttf fonts-noto-extra -notosansgeorgian-condensedsemibold.ttf fonts-noto-extra -notosansgeorgian-condensedthin.ttf fonts-noto-extra -notosansgeorgian-extrabold.ttf fonts-noto-extra -notosansgeorgian-extracondensed.ttf fonts-noto-extra -notosansgeorgian-extracondensedblack.ttf fonts-noto-extra -notosansgeorgian-extracondensedbold.ttf fonts-noto-extra -notosansgeorgian-extracondensedextrabold.ttf fonts-noto-extra -notosansgeorgian-extracondensedextralight.ttf fonts-noto-extra -notosansgeorgian-extracondensedlight.ttf fonts-noto-extra -notosansgeorgian-extracondensedmedium.ttf fonts-noto-extra -notosansgeorgian-extracondensedsemibold.ttf fonts-noto-extra -notosansgeorgian-extracondensedthin.ttf fonts-noto-extra -notosansgeorgian-extralight.ttf fonts-noto-extra -notosansgeorgian-light.ttf fonts-noto-extra -notosansgeorgian-medium.ttf fonts-noto-extra -notosansgeorgian-regular.ttf fonts-noto-core -notosansgeorgian-semibold.ttf fonts-noto-extra -notosansgeorgian-semicondensed.ttf fonts-noto-extra -notosansgeorgian-semicondensedblack.ttf fonts-noto-extra -notosansgeorgian-semicondensedbold.ttf fonts-noto-extra -notosansgeorgian-semicondensedextrabold.ttf fonts-noto-extra -notosansgeorgian-semicondensedextralight.ttf fonts-noto-extra -notosansgeorgian-semicondensedlight.ttf fonts-noto-extra -notosansgeorgian-semicondensedmedium.ttf fonts-noto-extra -notosansgeorgian-semicondensedsemibold.ttf fonts-noto-extra -notosansgeorgian-semicondensedthin.ttf fonts-noto-extra -notosansgeorgian-thin.ttf fonts-noto-extra -notosansglagolitic-regular.ttf fonts-noto-core -notosansgothic-regular.ttf fonts-noto-core -notosansgrantha-regular.ttf fonts-noto-core -notosansgujarati-bold.ttf fonts-noto-core -notosansgujarati-regular.ttf fonts-noto-core -notosansgujaratiui-bold.ttf fonts-noto-ui-core -notosansgujaratiui-regular.ttf fonts-noto-ui-core -notosansgunjalagondi-regular.ttf fonts-noto-unhinted -notosansgurmukhi-black.ttf fonts-noto-extra -notosansgurmukhi-bold.ttf fonts-noto-core -notosansgurmukhi-condensed.ttf fonts-noto-extra -notosansgurmukhi-condensedblack.ttf fonts-noto-extra -notosansgurmukhi-condensedbold.ttf fonts-noto-extra -notosansgurmukhi-condensedextrabold.ttf fonts-noto-extra -notosansgurmukhi-condensedextralight.ttf fonts-noto-extra -notosansgurmukhi-condensedlight.ttf fonts-noto-extra -notosansgurmukhi-condensedmedium.ttf fonts-noto-extra -notosansgurmukhi-condensedsemibold.ttf fonts-noto-extra -notosansgurmukhi-condensedthin.ttf fonts-noto-extra -notosansgurmukhi-extrabold.ttf fonts-noto-extra -notosansgurmukhi-extracondensed.ttf fonts-noto-extra -notosansgurmukhi-extracondensedblack.ttf fonts-noto-extra -notosansgurmukhi-extracondensedbold.ttf fonts-noto-extra -notosansgurmukhi-extracondensedextrabold.ttf fonts-noto-extra -notosansgurmukhi-extracondensedextralight.ttf fonts-noto-extra -notosansgurmukhi-extracondensedlight.ttf fonts-noto-extra -notosansgurmukhi-extracondensedmedium.ttf fonts-noto-extra -notosansgurmukhi-extracondensedsemibold.ttf fonts-noto-extra -notosansgurmukhi-extracondensedthin.ttf fonts-noto-extra -notosansgurmukhi-extralight.ttf fonts-noto-extra -notosansgurmukhi-light.ttf fonts-noto-extra -notosansgurmukhi-medium.ttf fonts-noto-extra -notosansgurmukhi-regular.ttf fonts-noto-core -notosansgurmukhi-semibold.ttf fonts-noto-extra -notosansgurmukhi-semicondensed.ttf fonts-noto-extra -notosansgurmukhi-semicondensedblack.ttf fonts-noto-extra -notosansgurmukhi-semicondensedbold.ttf fonts-noto-extra -notosansgurmukhi-semicondensedextrabold.ttf fonts-noto-extra -notosansgurmukhi-semicondensedextralight.ttf fonts-noto-extra -notosansgurmukhi-semicondensedlight.ttf fonts-noto-extra -notosansgurmukhi-semicondensedmedium.ttf fonts-noto-extra -notosansgurmukhi-semicondensedsemibold.ttf fonts-noto-extra -notosansgurmukhi-semicondensedthin.ttf fonts-noto-extra -notosansgurmukhi-thin.ttf fonts-noto-extra -notosansgurmukhiui-black.ttf fonts-noto-ui-extra -notosansgurmukhiui-bold.ttf fonts-noto-ui-core -notosansgurmukhiui-condensed.ttf fonts-noto-ui-extra -notosansgurmukhiui-condensedblack.ttf fonts-noto-ui-extra -notosansgurmukhiui-condensedbold.ttf fonts-noto-ui-extra -notosansgurmukhiui-condensedextrabold.ttf fonts-noto-ui-extra -notosansgurmukhiui-condensedextralight.ttf fonts-noto-ui-extra -notosansgurmukhiui-condensedlight.ttf fonts-noto-ui-extra -notosansgurmukhiui-condensedmedium.ttf fonts-noto-ui-extra -notosansgurmukhiui-condensedsemibold.ttf fonts-noto-ui-extra -notosansgurmukhiui-condensedthin.ttf fonts-noto-ui-extra -notosansgurmukhiui-extrabold.ttf fonts-noto-ui-extra -notosansgurmukhiui-extracondensed.ttf fonts-noto-ui-extra -notosansgurmukhiui-extracondensedblack.ttf fonts-noto-ui-extra -notosansgurmukhiui-extracondensedbold.ttf fonts-noto-ui-extra -notosansgurmukhiui-extracondensedextrabold.ttf fonts-noto-ui-extra -notosansgurmukhiui-extracondensedextralight.ttf fonts-noto-ui-extra -notosansgurmukhiui-extracondensedlight.ttf fonts-noto-ui-extra -notosansgurmukhiui-extracondensedmedium.ttf fonts-noto-ui-extra -notosansgurmukhiui-extracondensedsemibold.ttf fonts-noto-ui-extra -notosansgurmukhiui-extracondensedthin.ttf fonts-noto-ui-extra -notosansgurmukhiui-extralight.ttf fonts-noto-ui-extra -notosansgurmukhiui-light.ttf fonts-noto-ui-extra -notosansgurmukhiui-medium.ttf fonts-noto-ui-extra -notosansgurmukhiui-regular.ttf fonts-noto-ui-core -notosansgurmukhiui-semibold.ttf fonts-noto-ui-extra -notosansgurmukhiui-semicondensed.ttf fonts-noto-ui-extra -notosansgurmukhiui-semicondensedblack.ttf fonts-noto-ui-extra -notosansgurmukhiui-semicondensedbold.ttf fonts-noto-ui-extra -notosansgurmukhiui-semicondensedextrabold.ttf fonts-noto-ui-extra -notosansgurmukhiui-semicondensedextralight.ttf fonts-noto-ui-extra -notosansgurmukhiui-semicondensedlight.ttf fonts-noto-ui-extra -notosansgurmukhiui-semicondensedmedium.ttf fonts-noto-ui-extra -notosansgurmukhiui-semicondensedsemibold.ttf fonts-noto-ui-extra -notosansgurmukhiui-semicondensedthin.ttf fonts-noto-ui-extra -notosansgurmukhiui-thin.ttf fonts-noto-ui-extra -notosanshanifirohingya-regular.ttf fonts-noto-core -notosanshanunoo-regular.ttf fonts-noto-core -notosanshatran-regular.ttf fonts-noto-core -notosanshebrew-black.ttf fonts-noto-extra -notosanshebrew-bold.ttf fonts-noto-core -notosanshebrew-condensed.ttf fonts-noto-extra -notosanshebrew-condensedblack.ttf fonts-noto-extra -notosanshebrew-condensedbold.ttf fonts-noto-extra -notosanshebrew-condensedextrabold.ttf fonts-noto-extra -notosanshebrew-condensedextralight.ttf fonts-noto-extra -notosanshebrew-condensedlight.ttf fonts-noto-extra -notosanshebrew-condensedmedium.ttf fonts-noto-extra -notosanshebrew-condensedsemibold.ttf fonts-noto-extra -notosanshebrew-condensedthin.ttf fonts-noto-extra -notosanshebrew-extrabold.ttf fonts-noto-extra -notosanshebrew-extracondensed.ttf fonts-noto-extra -notosanshebrew-extracondensedblack.ttf fonts-noto-extra -notosanshebrew-extracondensedbold.ttf fonts-noto-extra -notosanshebrew-extracondensedextrabold.ttf fonts-noto-extra -notosanshebrew-extracondensedextralight.ttf fonts-noto-extra -notosanshebrew-extracondensedlight.ttf fonts-noto-extra -notosanshebrew-extracondensedmedium.ttf fonts-noto-extra -notosanshebrew-extracondensedsemibold.ttf fonts-noto-extra -notosanshebrew-extracondensedthin.ttf fonts-noto-extra -notosanshebrew-extralight.ttf fonts-noto-extra -notosanshebrew-light.ttf fonts-noto-extra -notosanshebrew-medium.ttf fonts-noto-extra -notosanshebrew-regular.ttf fonts-noto-core -notosanshebrew-semibold.ttf fonts-noto-extra -notosanshebrew-semicondensed.ttf fonts-noto-extra -notosanshebrew-semicondensedblack.ttf fonts-noto-extra -notosanshebrew-semicondensedbold.ttf fonts-noto-extra -notosanshebrew-semicondensedextrabold.ttf fonts-noto-extra -notosanshebrew-semicondensedextralight.ttf fonts-noto-extra -notosanshebrew-semicondensedlight.ttf fonts-noto-extra -notosanshebrew-semicondensedmedium.ttf fonts-noto-extra -notosanshebrew-semicondensedsemibold.ttf fonts-noto-extra -notosanshebrew-semicondensedthin.ttf fonts-noto-extra -notosanshebrew-thin.ttf fonts-noto-extra -notosansimperialaramaic-regular.ttf fonts-noto-core -notosansindicsiyaqnumbers-regular.ttf fonts-noto-core -notosansinscriptionalpahlavi-regular.ttf fonts-noto-core -notosansinscriptionalparthian-regular.ttf fonts-noto-core -notosansjavanese-bold.ttf fonts-noto-core -notosansjavanese-regular.ttf fonts-noto-core -notosanskaithi-regular.ttf fonts-noto-core -notosanskannada-black.ttf fonts-noto-extra -notosanskannada-bold.ttf fonts-noto-core -notosanskannada-condensed.ttf fonts-noto-extra -notosanskannada-condensedblack.ttf fonts-noto-extra -notosanskannada-condensedbold.ttf fonts-noto-extra -notosanskannada-condensedextrabold.ttf fonts-noto-extra -notosanskannada-condensedextralight.ttf fonts-noto-extra -notosanskannada-condensedlight.ttf fonts-noto-extra -notosanskannada-condensedmedium.ttf fonts-noto-extra -notosanskannada-condensedsemibold.ttf fonts-noto-extra -notosanskannada-condensedthin.ttf fonts-noto-extra -notosanskannada-extrabold.ttf fonts-noto-extra -notosanskannada-extracondensed.ttf fonts-noto-extra -notosanskannada-extracondensedblack.ttf fonts-noto-extra -notosanskannada-extracondensedbold.ttf fonts-noto-extra -notosanskannada-extracondensedextrabold.ttf fonts-noto-extra -notosanskannada-extracondensedextralight.ttf fonts-noto-extra -notosanskannada-extracondensedlight.ttf fonts-noto-extra -notosanskannada-extracondensedmedium.ttf fonts-noto-extra -notosanskannada-extracondensedsemibold.ttf fonts-noto-extra -notosanskannada-extracondensedthin.ttf fonts-noto-extra -notosanskannada-extralight.ttf fonts-noto-extra -notosanskannada-light.ttf fonts-noto-extra -notosanskannada-medium.ttf fonts-noto-extra -notosanskannada-regular.ttf fonts-noto-core -notosanskannada-semibold.ttf fonts-noto-extra -notosanskannada-semicondensed.ttf fonts-noto-extra -notosanskannada-semicondensedblack.ttf fonts-noto-extra -notosanskannada-semicondensedbold.ttf fonts-noto-extra -notosanskannada-semicondensedextrabold.ttf fonts-noto-extra -notosanskannada-semicondensedextralight.ttf fonts-noto-extra -notosanskannada-semicondensedlight.ttf fonts-noto-extra -notosanskannada-semicondensedmedium.ttf fonts-noto-extra -notosanskannada-semicondensedsemibold.ttf fonts-noto-extra -notosanskannada-semicondensedthin.ttf fonts-noto-extra -notosanskannada-thin.ttf fonts-noto-extra -notosanskannadaui-black.ttf fonts-noto-ui-extra -notosanskannadaui-bold.ttf fonts-noto-ui-core -notosanskannadaui-condensed.ttf fonts-noto-ui-extra -notosanskannadaui-condensedblack.ttf fonts-noto-ui-extra -notosanskannadaui-condensedbold.ttf fonts-noto-ui-extra -notosanskannadaui-condensedextrabold.ttf fonts-noto-ui-extra -notosanskannadaui-condensedextralight.ttf fonts-noto-ui-extra -notosanskannadaui-condensedlight.ttf fonts-noto-ui-extra -notosanskannadaui-condensedmedium.ttf fonts-noto-ui-extra -notosanskannadaui-condensedsemibold.ttf fonts-noto-ui-extra -notosanskannadaui-condensedthin.ttf fonts-noto-ui-extra -notosanskannadaui-extrabold.ttf fonts-noto-ui-extra -notosanskannadaui-extracondensed.ttf fonts-noto-ui-extra -notosanskannadaui-extracondensedblack.ttf fonts-noto-ui-extra -notosanskannadaui-extracondensedbold.ttf fonts-noto-ui-extra -notosanskannadaui-extracondensedextrabold.ttf fonts-noto-ui-extra -notosanskannadaui-extracondensedextralight.ttf fonts-noto-ui-extra -notosanskannadaui-extracondensedlight.ttf fonts-noto-ui-extra -notosanskannadaui-extracondensedmedium.ttf fonts-noto-ui-extra -notosanskannadaui-extracondensedsemibold.ttf fonts-noto-ui-extra -notosanskannadaui-extracondensedthin.ttf fonts-noto-ui-extra -notosanskannadaui-extralight.ttf fonts-noto-ui-extra -notosanskannadaui-light.ttf fonts-noto-ui-extra -notosanskannadaui-medium.ttf fonts-noto-ui-extra -notosanskannadaui-regular.ttf fonts-noto-ui-core -notosanskannadaui-semibold.ttf fonts-noto-ui-extra -notosanskannadaui-semicondensed.ttf fonts-noto-ui-extra -notosanskannadaui-semicondensedblack.ttf fonts-noto-ui-extra -notosanskannadaui-semicondensedbold.ttf fonts-noto-ui-extra -notosanskannadaui-semicondensedextrabold.ttf fonts-noto-ui-extra -notosanskannadaui-semicondensedextralight.ttf fonts-noto-ui-extra -notosanskannadaui-semicondensedlight.ttf fonts-noto-ui-extra -notosanskannadaui-semicondensedmedium.ttf fonts-noto-ui-extra -notosanskannadaui-semicondensedsemibold.ttf fonts-noto-ui-extra -notosanskannadaui-semicondensedthin.ttf fonts-noto-ui-extra -notosanskannadaui-thin.ttf fonts-noto-ui-extra -notosanskayahli-regular.ttf fonts-noto-core -notosanskharoshthi-regular.ttf fonts-noto-core -notosanskhmer-black.ttf fonts-noto-extra -notosanskhmer-bold.ttf fonts-noto-core -notosanskhmer-condensed.ttf fonts-noto-extra -notosanskhmer-condensedblack.ttf fonts-noto-extra -notosanskhmer-condensedbold.ttf fonts-noto-extra -notosanskhmer-condensedextrabold.ttf fonts-noto-extra -notosanskhmer-condensedextralight.ttf fonts-noto-extra -notosanskhmer-condensedlight.ttf fonts-noto-extra -notosanskhmer-condensedmedium.ttf fonts-noto-extra -notosanskhmer-condensedsemibold.ttf fonts-noto-extra -notosanskhmer-condensedthin.ttf fonts-noto-extra -notosanskhmer-extrabold.ttf fonts-noto-extra -notosanskhmer-extracondensed.ttf fonts-noto-extra -notosanskhmer-extracondensedblack.ttf fonts-noto-extra -notosanskhmer-extracondensedbold.ttf fonts-noto-extra -notosanskhmer-extracondensedextrabold.ttf fonts-noto-extra -notosanskhmer-extracondensedextralight.ttf fonts-noto-extra -notosanskhmer-extracondensedlight.ttf fonts-noto-extra -notosanskhmer-extracondensedmedium.ttf fonts-noto-extra -notosanskhmer-extracondensedsemibold.ttf fonts-noto-extra -notosanskhmer-extracondensedthin.ttf fonts-noto-extra -notosanskhmer-extralight.ttf fonts-noto-extra -notosanskhmer-light.ttf fonts-noto-extra -notosanskhmer-medium.ttf fonts-noto-extra -notosanskhmer-regular.ttf fonts-noto-core -notosanskhmer-semibold.ttf fonts-noto-extra -notosanskhmer-semicondensed.ttf fonts-noto-extra -notosanskhmer-semicondensedblack.ttf fonts-noto-extra -notosanskhmer-semicondensedbold.ttf fonts-noto-extra -notosanskhmer-semicondensedextrabold.ttf fonts-noto-extra -notosanskhmer-semicondensedextralight.ttf fonts-noto-extra -notosanskhmer-semicondensedlight.ttf fonts-noto-extra -notosanskhmer-semicondensedmedium.ttf fonts-noto-extra -notosanskhmer-semicondensedsemibold.ttf fonts-noto-extra -notosanskhmer-semicondensedthin.ttf fonts-noto-extra -notosanskhmer-thin.ttf fonts-noto-extra -notosanskhmerui-black.ttf fonts-noto-ui-extra -notosanskhmerui-bold.ttf fonts-noto-ui-core -notosanskhmerui-condensed.ttf fonts-noto-ui-extra -notosanskhmerui-condensedblack.ttf fonts-noto-ui-extra -notosanskhmerui-condensedbold.ttf fonts-noto-ui-extra -notosanskhmerui-condensedextrabold.ttf fonts-noto-ui-extra -notosanskhmerui-condensedextralight.ttf fonts-noto-ui-extra -notosanskhmerui-condensedlight.ttf fonts-noto-ui-extra -notosanskhmerui-condensedmedium.ttf fonts-noto-ui-extra -notosanskhmerui-condensedsemibold.ttf fonts-noto-ui-extra -notosanskhmerui-condensedthin.ttf fonts-noto-ui-extra -notosanskhmerui-extrabold.ttf fonts-noto-ui-extra -notosanskhmerui-extracondensed.ttf fonts-noto-ui-extra -notosanskhmerui-extracondensedblack.ttf fonts-noto-ui-extra -notosanskhmerui-extracondensedbold.ttf fonts-noto-ui-extra -notosanskhmerui-extracondensedextrabold.ttf fonts-noto-ui-extra -notosanskhmerui-extracondensedextralight.ttf fonts-noto-ui-extra -notosanskhmerui-extracondensedlight.ttf fonts-noto-ui-extra -notosanskhmerui-extracondensedmedium.ttf fonts-noto-ui-extra -notosanskhmerui-extracondensedsemibold.ttf fonts-noto-ui-extra -notosanskhmerui-extracondensedthin.ttf fonts-noto-ui-extra -notosanskhmerui-extralight.ttf fonts-noto-ui-extra -notosanskhmerui-light.ttf fonts-noto-ui-extra -notosanskhmerui-medium.ttf fonts-noto-ui-extra -notosanskhmerui-regular.ttf fonts-noto-ui-core -notosanskhmerui-semibold.ttf fonts-noto-ui-extra -notosanskhmerui-semicondensed.ttf fonts-noto-ui-extra -notosanskhmerui-semicondensedblack.ttf fonts-noto-ui-extra -notosanskhmerui-semicondensedbold.ttf fonts-noto-ui-extra -notosanskhmerui-semicondensedextrabold.ttf fonts-noto-ui-extra -notosanskhmerui-semicondensedextralight.ttf fonts-noto-ui-extra -notosanskhmerui-semicondensedlight.ttf fonts-noto-ui-extra -notosanskhmerui-semicondensedmedium.ttf fonts-noto-ui-extra -notosanskhmerui-semicondensedsemibold.ttf fonts-noto-ui-extra -notosanskhmerui-semicondensedthin.ttf fonts-noto-ui-extra -notosanskhmerui-thin.ttf fonts-noto-ui-extra -notosanskhojki-regular.ttf fonts-noto-core -notosanskhudawadi-regular.ttf fonts-noto-core -notosanslao-black.ttf fonts-noto-extra -notosanslao-bold.ttf fonts-noto-core -notosanslao-condensed.ttf fonts-noto-extra -notosanslao-condensedblack.ttf fonts-noto-extra -notosanslao-condensedbold.ttf fonts-noto-extra -notosanslao-condensedextrabold.ttf fonts-noto-extra -notosanslao-condensedextralight.ttf fonts-noto-extra -notosanslao-condensedlight.ttf fonts-noto-extra -notosanslao-condensedmedium.ttf fonts-noto-extra -notosanslao-condensedsemibold.ttf fonts-noto-extra -notosanslao-condensedthin.ttf fonts-noto-extra -notosanslao-extrabold.ttf fonts-noto-extra -notosanslao-extracondensed.ttf fonts-noto-extra -notosanslao-extracondensedblack.ttf fonts-noto-extra -notosanslao-extracondensedbold.ttf fonts-noto-extra -notosanslao-extracondensedextrabold.ttf fonts-noto-extra -notosanslao-extracondensedextralight.ttf fonts-noto-extra -notosanslao-extracondensedlight.ttf fonts-noto-extra -notosanslao-extracondensedmedium.ttf fonts-noto-extra -notosanslao-extracondensedsemibold.ttf fonts-noto-extra -notosanslao-extracondensedthin.ttf fonts-noto-extra -notosanslao-extralight.ttf fonts-noto-extra -notosanslao-light.ttf fonts-noto-extra -notosanslao-medium.ttf fonts-noto-extra -notosanslao-regular.ttf fonts-noto-core -notosanslao-semibold.ttf fonts-noto-extra -notosanslao-semicondensed.ttf fonts-noto-extra -notosanslao-semicondensedblack.ttf fonts-noto-extra -notosanslao-semicondensedbold.ttf fonts-noto-extra -notosanslao-semicondensedextrabold.ttf fonts-noto-extra -notosanslao-semicondensedextralight.ttf fonts-noto-extra -notosanslao-semicondensedlight.ttf fonts-noto-extra -notosanslao-semicondensedmedium.ttf fonts-noto-extra -notosanslao-semicondensedsemibold.ttf fonts-noto-extra -notosanslao-semicondensedthin.ttf fonts-noto-extra -notosanslao-thin.ttf fonts-noto-extra -notosanslaoui-black.ttf fonts-noto-ui-extra -notosanslaoui-bold.ttf fonts-noto-ui-core -notosanslaoui-condensed.ttf fonts-noto-ui-extra -notosanslaoui-condensedblack.ttf fonts-noto-ui-extra -notosanslaoui-condensedbold.ttf fonts-noto-ui-extra -notosanslaoui-condensedextrabold.ttf fonts-noto-ui-extra -notosanslaoui-condensedextralight.ttf fonts-noto-ui-extra -notosanslaoui-condensedlight.ttf fonts-noto-ui-extra -notosanslaoui-condensedmedium.ttf fonts-noto-ui-extra -notosanslaoui-condensedsemibold.ttf fonts-noto-ui-extra -notosanslaoui-condensedthin.ttf fonts-noto-ui-extra -notosanslaoui-extrabold.ttf fonts-noto-ui-extra -notosanslaoui-extracondensed.ttf fonts-noto-ui-extra -notosanslaoui-extracondensedblack.ttf fonts-noto-ui-extra -notosanslaoui-extracondensedbold.ttf fonts-noto-ui-extra -notosanslaoui-extracondensedextrabold.ttf fonts-noto-ui-extra -notosanslaoui-extracondensedextralight.ttf fonts-noto-ui-extra -notosanslaoui-extracondensedlight.ttf fonts-noto-ui-extra -notosanslaoui-extracondensedmedium.ttf fonts-noto-ui-extra -notosanslaoui-extracondensedsemibold.ttf fonts-noto-ui-extra -notosanslaoui-extracondensedthin.ttf fonts-noto-ui-extra -notosanslaoui-extralight.ttf fonts-noto-ui-extra -notosanslaoui-light.ttf fonts-noto-ui-extra -notosanslaoui-medium.ttf fonts-noto-ui-extra -notosanslaoui-regular.ttf fonts-noto-ui-core -notosanslaoui-semibold.ttf fonts-noto-ui-extra -notosanslaoui-semicondensed.ttf fonts-noto-ui-extra -notosanslaoui-semicondensedblack.ttf fonts-noto-ui-extra -notosanslaoui-semicondensedbold.ttf fonts-noto-ui-extra -notosanslaoui-semicondensedextrabold.ttf fonts-noto-ui-extra -notosanslaoui-semicondensedextralight.ttf fonts-noto-ui-extra -notosanslaoui-semicondensedlight.ttf fonts-noto-ui-extra -notosanslaoui-semicondensedmedium.ttf fonts-noto-ui-extra -notosanslaoui-semicondensedsemibold.ttf fonts-noto-ui-extra -notosanslaoui-semicondensedthin.ttf fonts-noto-ui-extra -notosanslaoui-thin.ttf fonts-noto-ui-extra -notosanslepcha-regular.ttf fonts-noto-core -notosanslimbu-regular.ttf fonts-noto-core -notosanslineara-regular.ttf fonts-noto-core -notosanslinearb-regular.ttf fonts-noto-core -notosanslisu-bold.ttf fonts-noto-unhinted -notosanslisu-medium.ttf fonts-noto-unhinted -notosanslisu-regular.ttf fonts-noto-core -notosanslisu-semibold.ttf fonts-noto-unhinted -notosanslycian-regular.ttf fonts-noto-core -notosanslydian-regular.ttf fonts-noto-core -notosansmahajani-regular.ttf fonts-noto-core -notosansmalayalam-black.ttf fonts-noto-extra -notosansmalayalam-bold.ttf fonts-noto-core -notosansmalayalam-condensed.ttf fonts-noto-extra -notosansmalayalam-condensedblack.ttf fonts-noto-extra -notosansmalayalam-condensedbold.ttf fonts-noto-extra -notosansmalayalam-condensedextrabold.ttf fonts-noto-extra -notosansmalayalam-condensedextralight.ttf fonts-noto-extra -notosansmalayalam-condensedlight.ttf fonts-noto-extra -notosansmalayalam-condensedmedium.ttf fonts-noto-extra -notosansmalayalam-condensedsemibold.ttf fonts-noto-extra -notosansmalayalam-condensedthin.ttf fonts-noto-extra -notosansmalayalam-extrabold.ttf fonts-noto-extra -notosansmalayalam-extracondensed.ttf fonts-noto-extra -notosansmalayalam-extracondensedblack.ttf fonts-noto-extra -notosansmalayalam-extracondensedbold.ttf fonts-noto-extra -notosansmalayalam-extracondensedextrabold.ttf fonts-noto-extra -notosansmalayalam-extracondensedextralight.ttf fonts-noto-extra -notosansmalayalam-extracondensedlight.ttf fonts-noto-extra -notosansmalayalam-extracondensedmedium.ttf fonts-noto-extra -notosansmalayalam-extracondensedsemibold.ttf fonts-noto-extra -notosansmalayalam-extracondensedthin.ttf fonts-noto-extra -notosansmalayalam-extralight.ttf fonts-noto-extra -notosansmalayalam-light.ttf fonts-noto-extra -notosansmalayalam-medium.ttf fonts-noto-extra -notosansmalayalam-regular.ttf fonts-noto-core -notosansmalayalam-semibold.ttf fonts-noto-extra -notosansmalayalam-semicondensed.ttf fonts-noto-extra -notosansmalayalam-semicondensedblack.ttf fonts-noto-extra -notosansmalayalam-semicondensedbold.ttf fonts-noto-extra -notosansmalayalam-semicondensedextrabold.ttf fonts-noto-extra -notosansmalayalam-semicondensedextralight.ttf fonts-noto-extra -notosansmalayalam-semicondensedlight.ttf fonts-noto-extra -notosansmalayalam-semicondensedmedium.ttf fonts-noto-extra -notosansmalayalam-semicondensedsemibold.ttf fonts-noto-extra -notosansmalayalam-semicondensedthin.ttf fonts-noto-extra -notosansmalayalam-thin.ttf fonts-noto-extra -notosansmalayalamui-black.ttf fonts-noto-ui-extra -notosansmalayalamui-bold.ttf fonts-noto-ui-core -notosansmalayalamui-condensed.ttf fonts-noto-ui-extra -notosansmalayalamui-condensedblack.ttf fonts-noto-ui-extra -notosansmalayalamui-condensedbold.ttf fonts-noto-ui-extra -notosansmalayalamui-condensedextrabold.ttf fonts-noto-ui-extra -notosansmalayalamui-condensedextralight.ttf fonts-noto-ui-extra -notosansmalayalamui-condensedlight.ttf fonts-noto-ui-extra -notosansmalayalamui-condensedmedium.ttf fonts-noto-ui-extra -notosansmalayalamui-condensedsemibold.ttf fonts-noto-ui-extra -notosansmalayalamui-condensedthin.ttf fonts-noto-ui-extra -notosansmalayalamui-extrabold.ttf fonts-noto-ui-extra -notosansmalayalamui-extracondensed.ttf fonts-noto-ui-extra -notosansmalayalamui-extracondensedblack.ttf fonts-noto-ui-extra -notosansmalayalamui-extracondensedbold.ttf fonts-noto-ui-extra -notosansmalayalamui-extracondensedextrabold.ttf fonts-noto-ui-extra -notosansmalayalamui-extracondensedextralight.ttf fonts-noto-ui-extra -notosansmalayalamui-extracondensedlight.ttf fonts-noto-ui-extra -notosansmalayalamui-extracondensedmedium.ttf fonts-noto-ui-extra -notosansmalayalamui-extracondensedsemibold.ttf fonts-noto-ui-extra -notosansmalayalamui-extracondensedthin.ttf fonts-noto-ui-extra -notosansmalayalamui-extralight.ttf fonts-noto-ui-extra -notosansmalayalamui-light.ttf fonts-noto-ui-extra -notosansmalayalamui-medium.ttf fonts-noto-ui-extra -notosansmalayalamui-regular.ttf fonts-noto-ui-core -notosansmalayalamui-semibold.ttf fonts-noto-ui-extra -notosansmalayalamui-semicondensed.ttf fonts-noto-ui-extra -notosansmalayalamui-semicondensedblack.ttf fonts-noto-ui-extra -notosansmalayalamui-semicondensedbold.ttf fonts-noto-ui-extra -notosansmalayalamui-semicondensedextrabold.ttf fonts-noto-ui-extra -notosansmalayalamui-semicondensedextralight.ttf fonts-noto-ui-extra -notosansmalayalamui-semicondensedlight.ttf fonts-noto-ui-extra -notosansmalayalamui-semicondensedmedium.ttf fonts-noto-ui-extra -notosansmalayalamui-semicondensedsemibold.ttf fonts-noto-ui-extra -notosansmalayalamui-semicondensedthin.ttf fonts-noto-ui-extra -notosansmalayalamui-thin.ttf fonts-noto-ui-extra -notosansmandaic-regular.ttf fonts-noto-core -notosansmanichaean-regular.ttf fonts-noto-core -notosansmarchen-regular.ttf fonts-noto-core -notosansmasaramgondi-regular.ttf fonts-noto-unhinted -notosansmath-regular.ttf fonts-noto-core -notosansmayannumerals-regular.ttf fonts-noto-core -notosansmeeteimayek-regular.ttf fonts-noto-core -notosansmendekikakui-regular.ttf fonts-noto-core -notosansmeroitic-regular.ttf fonts-noto-core -notosansmiao-regular.ttf fonts-noto-core -notosansmodi-regular.ttf fonts-noto-core -notosansmongolian-regular.ttf fonts-noto-core -notosansmono-black.ttf fonts-noto-extra -notosansmono-bold.ttf fonts-noto-core -notosansmono-condensed.ttf fonts-noto-extra -notosansmono-condensedblack.ttf fonts-noto-extra -notosansmono-condensedbold.ttf fonts-noto-extra -notosansmono-condensedextrabold.ttf fonts-noto-extra -notosansmono-condensedextralight.ttf fonts-noto-extra -notosansmono-condensedlight.ttf fonts-noto-extra -notosansmono-condensedmedium.ttf fonts-noto-extra -notosansmono-condensedsemibold.ttf fonts-noto-extra -notosansmono-condensedthin.ttf fonts-noto-extra -notosansmono-extrabold.ttf fonts-noto-extra -notosansmono-extracondensed.ttf fonts-noto-extra -notosansmono-extracondensedblack.ttf fonts-noto-extra -notosansmono-extracondensedbold.ttf fonts-noto-extra -notosansmono-extracondensedextrabold.ttf fonts-noto-extra -notosansmono-extracondensedextralight.ttf fonts-noto-extra -notosansmono-extracondensedlight.ttf fonts-noto-extra -notosansmono-extracondensedmedium.ttf fonts-noto-extra -notosansmono-extracondensedsemibold.ttf fonts-noto-extra -notosansmono-extracondensedthin.ttf fonts-noto-extra -notosansmono-extralight.ttf fonts-noto-extra -notosansmono-light.ttf fonts-noto-extra -notosansmono-medium.ttf fonts-noto-extra -notosansmono-regular.ttf fonts-noto-core -notosansmono-semibold.ttf fonts-noto-extra -notosansmono-semicondensed.ttf fonts-noto-extra -notosansmono-semicondensedblack.ttf fonts-noto-extra -notosansmono-semicondensedbold.ttf fonts-noto-extra -notosansmono-semicondensedextrabold.ttf fonts-noto-extra -notosansmono-semicondensedextralight.ttf fonts-noto-extra -notosansmono-semicondensedlight.ttf fonts-noto-extra -notosansmono-semicondensedmedium.ttf fonts-noto-extra -notosansmono-semicondensedsemibold.ttf fonts-noto-extra -notosansmono-semicondensedthin.ttf fonts-noto-extra -notosansmono-thin.ttf fonts-noto-extra -notosansmro-regular.ttf fonts-noto-core -notosansmultani-regular.ttf fonts-noto-core -notosansmyanmar-black.ttf fonts-noto-extra -notosansmyanmar-bold.ttf fonts-noto-core -notosansmyanmar-condensed.ttf fonts-noto-extra -notosansmyanmar-condensedblack.ttf fonts-noto-extra -notosansmyanmar-condensedbold.ttf fonts-noto-extra -notosansmyanmar-condensedextrabold.ttf fonts-noto-extra -notosansmyanmar-condensedextralight.ttf fonts-noto-extra -notosansmyanmar-condensedlight.ttf fonts-noto-extra -notosansmyanmar-condensedmedium.ttf fonts-noto-extra -notosansmyanmar-condensedsemibold.ttf fonts-noto-extra -notosansmyanmar-condensedthin.ttf fonts-noto-extra -notosansmyanmar-extrabold.ttf fonts-noto-extra -notosansmyanmar-extracondensed.ttf fonts-noto-extra -notosansmyanmar-extracondensedblack.ttf fonts-noto-extra -notosansmyanmar-extracondensedbold.ttf fonts-noto-extra -notosansmyanmar-extracondensedextrabold.ttf fonts-noto-extra -notosansmyanmar-extracondensedextralight.ttf fonts-noto-extra -notosansmyanmar-extracondensedlight.ttf fonts-noto-extra -notosansmyanmar-extracondensedmedium.ttf fonts-noto-extra -notosansmyanmar-extracondensedsemibold.ttf fonts-noto-extra -notosansmyanmar-extracondensedthin.ttf fonts-noto-extra -notosansmyanmar-extralight.ttf fonts-noto-extra -notosansmyanmar-light.ttf fonts-noto-extra -notosansmyanmar-medium.ttf fonts-noto-extra -notosansmyanmar-regular.ttf fonts-noto-core -notosansmyanmar-semibold.ttf fonts-noto-extra -notosansmyanmar-semicondensed.ttf fonts-noto-extra -notosansmyanmar-semicondensedblack.ttf fonts-noto-extra -notosansmyanmar-semicondensedbold.ttf fonts-noto-extra -notosansmyanmar-semicondensedextrabold.ttf fonts-noto-extra -notosansmyanmar-semicondensedextralight.ttf fonts-noto-extra -notosansmyanmar-semicondensedlight.ttf fonts-noto-extra -notosansmyanmar-semicondensedmedium.ttf fonts-noto-extra -notosansmyanmar-semicondensedsemibold.ttf fonts-noto-extra -notosansmyanmar-semicondensedthin.ttf fonts-noto-extra -notosansmyanmar-thin.ttf fonts-noto-extra -notosansmyanmarui-black.ttf fonts-noto-ui-extra -notosansmyanmarui-bold.ttf fonts-noto-ui-core -notosansmyanmarui-condensed.ttf fonts-noto-ui-extra -notosansmyanmarui-condensedblack.ttf fonts-noto-ui-extra -notosansmyanmarui-condensedbold.ttf fonts-noto-ui-extra -notosansmyanmarui-condensedextrabold.ttf fonts-noto-ui-extra -notosansmyanmarui-condensedextralight.ttf fonts-noto-ui-extra -notosansmyanmarui-condensedlight.ttf fonts-noto-ui-extra -notosansmyanmarui-condensedmedium.ttf fonts-noto-ui-extra -notosansmyanmarui-condensedsemibold.ttf fonts-noto-ui-extra -notosansmyanmarui-condensedthin.ttf fonts-noto-ui-extra -notosansmyanmarui-extrabold.ttf fonts-noto-ui-extra -notosansmyanmarui-extracondensed.ttf fonts-noto-ui-extra -notosansmyanmarui-extracondensedblack.ttf fonts-noto-ui-extra -notosansmyanmarui-extracondensedbold.ttf fonts-noto-ui-extra -notosansmyanmarui-extracondensedextrabold.ttf fonts-noto-ui-extra -notosansmyanmarui-extracondensedextralight.ttf fonts-noto-ui-extra -notosansmyanmarui-extracondensedlight.ttf fonts-noto-ui-extra -notosansmyanmarui-extracondensedmedium.ttf fonts-noto-ui-extra -notosansmyanmarui-extracondensedsemibold.ttf fonts-noto-ui-extra -notosansmyanmarui-extracondensedthin.ttf fonts-noto-ui-extra -notosansmyanmarui-extralight.ttf fonts-noto-ui-extra -notosansmyanmarui-light.ttf fonts-noto-ui-extra -notosansmyanmarui-medium.ttf fonts-noto-ui-extra -notosansmyanmarui-regular.ttf fonts-noto-ui-core -notosansmyanmarui-semibold.ttf fonts-noto-ui-extra -notosansmyanmarui-semicondensed.ttf fonts-noto-ui-extra -notosansmyanmarui-semicondensedblack.ttf fonts-noto-ui-extra -notosansmyanmarui-semicondensedbold.ttf fonts-noto-ui-extra -notosansmyanmarui-semicondensedextrabold.ttf fonts-noto-ui-extra -notosansmyanmarui-semicondensedextralight.ttf fonts-noto-ui-extra -notosansmyanmarui-semicondensedlight.ttf fonts-noto-ui-extra -notosansmyanmarui-semicondensedmedium.ttf fonts-noto-ui-extra -notosansmyanmarui-semicondensedsemibold.ttf fonts-noto-ui-extra -notosansmyanmarui-semicondensedthin.ttf fonts-noto-ui-extra -notosansmyanmarui-thin.ttf fonts-noto-ui-extra -notosansnabataean-regular.ttf fonts-noto-core -notosansnewa-regular.ttf fonts-noto-core -notosansnewtailue-regular.ttf fonts-noto-core -notosansnko-regular.ttf fonts-noto-core -notosansogham-regular.ttf fonts-noto-core -notosansolchiki-bold.ttf fonts-noto-unhinted -notosansolchiki-medium.ttf fonts-noto-unhinted -notosansolchiki-regular.ttf fonts-noto-core -notosansolchiki-semibold.ttf fonts-noto-unhinted -notosansoldhungarian-regular.ttf fonts-noto-core -notosansolditalic-regular.ttf fonts-noto-core -notosansoldnortharabian-regular.ttf fonts-noto-core -notosansoldpermic-regular.ttf fonts-noto-core -notosansoldpersian-regular.ttf fonts-noto-core -notosansoldsogdian-regular.ttf fonts-noto-core -notosansoldsoutharabian-regular.ttf fonts-noto-core -notosansoldturkic-regular.ttf fonts-noto-core -notosansoriya-bold.ttf fonts-noto-core -notosansoriya-regular.ttf fonts-noto-core -notosansoriyaui-bold.ttf fonts-noto-ui-core -notosansoriyaui-regular.ttf fonts-noto-ui-core -notosansosage-regular.ttf fonts-noto-core -notosansosmanya-regular.ttf fonts-noto-core -notosanspahawhhmong-regular.ttf fonts-noto-core -notosanspalmyrene-regular.ttf fonts-noto-core -notosanspaucinhau-regular.ttf fonts-noto-core -notosansphagspa-regular.ttf fonts-noto-core -notosansphoenician-regular.ttf fonts-noto-core -notosanspsalterpahlavi-regular.ttf fonts-noto-core -notosansrejang-regular.ttf fonts-noto-core -notosansrunic-regular.ttf fonts-noto-core -notosanssamaritan-regular.ttf fonts-noto-core -notosanssaurashtra-regular.ttf fonts-noto-core -notosanssharada-regular.ttf fonts-noto-core -notosansshavian-regular.ttf fonts-noto-core -notosanssiddham-regular.ttf fonts-noto-core -notosanssinhala-black.ttf fonts-noto-extra -notosanssinhala-bold.ttf fonts-noto-core -notosanssinhala-condensed.ttf fonts-noto-extra -notosanssinhala-condensedblack.ttf fonts-noto-extra -notosanssinhala-condensedbold.ttf fonts-noto-extra -notosanssinhala-condensedextrabold.ttf fonts-noto-extra -notosanssinhala-condensedextralight.ttf fonts-noto-extra -notosanssinhala-condensedlight.ttf fonts-noto-extra -notosanssinhala-condensedmedium.ttf fonts-noto-extra -notosanssinhala-condensedsemibold.ttf fonts-noto-extra -notosanssinhala-condensedthin.ttf fonts-noto-extra -notosanssinhala-extrabold.ttf fonts-noto-extra -notosanssinhala-extracondensed.ttf fonts-noto-extra -notosanssinhala-extracondensedblack.ttf fonts-noto-extra -notosanssinhala-extracondensedbold.ttf fonts-noto-extra -notosanssinhala-extracondensedextrabold.ttf fonts-noto-extra -notosanssinhala-extracondensedextralight.ttf fonts-noto-extra -notosanssinhala-extracondensedlight.ttf fonts-noto-extra -notosanssinhala-extracondensedmedium.ttf fonts-noto-extra -notosanssinhala-extracondensedsemibold.ttf fonts-noto-extra -notosanssinhala-extracondensedthin.ttf fonts-noto-extra -notosanssinhala-extralight.ttf fonts-noto-extra -notosanssinhala-light.ttf fonts-noto-extra -notosanssinhala-medium.ttf fonts-noto-extra -notosanssinhala-regular.ttf fonts-noto-core -notosanssinhala-semibold.ttf fonts-noto-extra -notosanssinhala-semicondensed.ttf fonts-noto-extra -notosanssinhala-semicondensedblack.ttf fonts-noto-extra -notosanssinhala-semicondensedbold.ttf fonts-noto-extra -notosanssinhala-semicondensedextrabold.ttf fonts-noto-extra -notosanssinhala-semicondensedextralight.ttf fonts-noto-extra -notosanssinhala-semicondensedlight.ttf fonts-noto-extra -notosanssinhala-semicondensedmedium.ttf fonts-noto-extra -notosanssinhala-semicondensedsemibold.ttf fonts-noto-extra -notosanssinhala-semicondensedthin.ttf fonts-noto-extra -notosanssinhala-thin.ttf fonts-noto-extra -notosanssinhalaui-black.ttf fonts-noto-ui-extra -notosanssinhalaui-bold.ttf fonts-noto-ui-core -notosanssinhalaui-condensed.ttf fonts-noto-ui-extra -notosanssinhalaui-condensedblack.ttf fonts-noto-ui-extra -notosanssinhalaui-condensedbold.ttf fonts-noto-ui-extra -notosanssinhalaui-condensedextrabold.ttf fonts-noto-ui-extra -notosanssinhalaui-condensedextralight.ttf fonts-noto-ui-extra -notosanssinhalaui-condensedlight.ttf fonts-noto-ui-extra -notosanssinhalaui-condensedmedium.ttf fonts-noto-ui-extra -notosanssinhalaui-condensedsemibold.ttf fonts-noto-ui-extra -notosanssinhalaui-condensedthin.ttf fonts-noto-ui-extra -notosanssinhalaui-extrabold.ttf fonts-noto-ui-extra -notosanssinhalaui-extracondensed.ttf fonts-noto-ui-extra -notosanssinhalaui-extracondensedblack.ttf fonts-noto-ui-extra -notosanssinhalaui-extracondensedbold.ttf fonts-noto-ui-extra -notosanssinhalaui-extracondensedextrabold.ttf fonts-noto-ui-extra -notosanssinhalaui-extracondensedextralight.ttf fonts-noto-ui-extra -notosanssinhalaui-extracondensedlight.ttf fonts-noto-ui-extra -notosanssinhalaui-extracondensedmedium.ttf fonts-noto-ui-extra -notosanssinhalaui-extracondensedsemibold.ttf fonts-noto-ui-extra -notosanssinhalaui-extracondensedthin.ttf fonts-noto-ui-extra -notosanssinhalaui-extralight.ttf fonts-noto-ui-extra -notosanssinhalaui-light.ttf fonts-noto-ui-extra -notosanssinhalaui-medium.ttf fonts-noto-ui-extra -notosanssinhalaui-regular.ttf fonts-noto-ui-core -notosanssinhalaui-semibold.ttf fonts-noto-ui-extra -notosanssinhalaui-semicondensed.ttf fonts-noto-ui-extra -notosanssinhalaui-semicondensedblack.ttf fonts-noto-ui-extra -notosanssinhalaui-semicondensedbold.ttf fonts-noto-ui-extra -notosanssinhalaui-semicondensedextrabold.ttf fonts-noto-ui-extra -notosanssinhalaui-semicondensedextralight.ttf fonts-noto-ui-extra -notosanssinhalaui-semicondensedlight.ttf fonts-noto-ui-extra -notosanssinhalaui-semicondensedmedium.ttf fonts-noto-ui-extra -notosanssinhalaui-semicondensedsemibold.ttf fonts-noto-ui-extra -notosanssinhalaui-semicondensedthin.ttf fonts-noto-ui-extra -notosanssinhalaui-thin.ttf fonts-noto-ui-extra -notosanssogdian-regular.ttf fonts-noto-unhinted -notosanssorasompeng-regular.ttf fonts-noto-core -notosanssoyombo-regular.ttf fonts-noto-unhinted -notosanssundanese-regular.ttf fonts-noto-core -notosanssylotinagri-regular.ttf fonts-noto-core -notosanssymbols-black.ttf fonts-noto-extra -notosanssymbols-bold.ttf fonts-noto-core -notosanssymbols-extrabold.ttf fonts-noto-extra -notosanssymbols-extralight.ttf fonts-noto-extra -notosanssymbols-light.ttf fonts-noto-extra -notosanssymbols-medium.ttf fonts-noto-extra -notosanssymbols-regular.ttf fonts-noto-core -notosanssymbols-semibold.ttf fonts-noto-extra -notosanssymbols-thin.ttf fonts-noto-extra -notosanssymbols2-regular.ttf fonts-noto-core -notosanssyriac-black.ttf fonts-noto-extra -notosanssyriac-regular.ttf fonts-noto-core -notosanssyriac-thin.ttf fonts-noto-extra -notosanstagalog-regular.ttf fonts-noto-core -notosanstagbanwa-regular.ttf fonts-noto-core -notosanstaile-regular.ttf fonts-noto-core -notosanstaitham-regular.ttf fonts-noto-core -notosanstaiviet-regular.ttf fonts-noto-core -notosanstakri-regular.ttf fonts-noto-core -notosanstamil-black.ttf fonts-noto-extra -notosanstamil-bold.ttf fonts-noto-core -notosanstamil-condensed.ttf fonts-noto-extra -notosanstamil-condensedblack.ttf fonts-noto-extra -notosanstamil-condensedbold.ttf fonts-noto-extra -notosanstamil-condensedextrabold.ttf fonts-noto-extra -notosanstamil-condensedextralight.ttf fonts-noto-extra -notosanstamil-condensedlight.ttf fonts-noto-extra -notosanstamil-condensedmedium.ttf fonts-noto-extra -notosanstamil-condensedsemibold.ttf fonts-noto-extra -notosanstamil-condensedthin.ttf fonts-noto-extra -notosanstamil-extrabold.ttf fonts-noto-extra -notosanstamil-extracondensed.ttf fonts-noto-extra -notosanstamil-extracondensedblack.ttf fonts-noto-extra -notosanstamil-extracondensedbold.ttf fonts-noto-extra -notosanstamil-extracondensedextrabold.ttf fonts-noto-extra -notosanstamil-extracondensedextralight.ttf fonts-noto-extra -notosanstamil-extracondensedlight.ttf fonts-noto-extra -notosanstamil-extracondensedmedium.ttf fonts-noto-extra -notosanstamil-extracondensedsemibold.ttf fonts-noto-extra -notosanstamil-extracondensedthin.ttf fonts-noto-extra -notosanstamil-extralight.ttf fonts-noto-extra -notosanstamil-light.ttf fonts-noto-extra -notosanstamil-medium.ttf fonts-noto-extra -notosanstamil-regular.ttf fonts-noto-core -notosanstamil-semibold.ttf fonts-noto-extra -notosanstamil-semicondensed.ttf fonts-noto-extra -notosanstamil-semicondensedblack.ttf fonts-noto-extra -notosanstamil-semicondensedbold.ttf fonts-noto-extra -notosanstamil-semicondensedextrabold.ttf fonts-noto-extra -notosanstamil-semicondensedextralight.ttf fonts-noto-extra -notosanstamil-semicondensedlight.ttf fonts-noto-extra -notosanstamil-semicondensedmedium.ttf fonts-noto-extra -notosanstamil-semicondensedsemibold.ttf fonts-noto-extra -notosanstamil-semicondensedthin.ttf fonts-noto-extra -notosanstamil-thin.ttf fonts-noto-extra -notosanstamilsupplement-regular.ttf fonts-noto-core -notosanstamilui-black.ttf fonts-noto-ui-extra -notosanstamilui-bold.ttf fonts-noto-ui-core -notosanstamilui-condensed.ttf fonts-noto-ui-extra -notosanstamilui-condensedblack.ttf fonts-noto-ui-extra -notosanstamilui-condensedbold.ttf fonts-noto-ui-extra -notosanstamilui-condensedextrabold.ttf fonts-noto-ui-extra -notosanstamilui-condensedextralight.ttf fonts-noto-ui-extra -notosanstamilui-condensedlight.ttf fonts-noto-ui-extra -notosanstamilui-condensedmedium.ttf fonts-noto-ui-extra -notosanstamilui-condensedsemibold.ttf fonts-noto-ui-extra -notosanstamilui-condensedthin.ttf fonts-noto-ui-extra -notosanstamilui-extrabold.ttf fonts-noto-ui-extra -notosanstamilui-extracondensed.ttf fonts-noto-ui-extra -notosanstamilui-extracondensedblack.ttf fonts-noto-ui-extra -notosanstamilui-extracondensedbold.ttf fonts-noto-ui-extra -notosanstamilui-extracondensedextrabold.ttf fonts-noto-ui-extra -notosanstamilui-extracondensedextralight.ttf fonts-noto-ui-extra -notosanstamilui-extracondensedlight.ttf fonts-noto-ui-extra -notosanstamilui-extracondensedmedium.ttf fonts-noto-ui-extra -notosanstamilui-extracondensedsemibold.ttf fonts-noto-ui-extra -notosanstamilui-extracondensedthin.ttf fonts-noto-ui-extra -notosanstamilui-extralight.ttf fonts-noto-ui-extra -notosanstamilui-light.ttf fonts-noto-ui-extra -notosanstamilui-medium.ttf fonts-noto-ui-extra -notosanstamilui-regular.ttf fonts-noto-ui-core -notosanstamilui-semibold.ttf fonts-noto-ui-extra -notosanstamilui-semicondensed.ttf fonts-noto-ui-extra -notosanstamilui-semicondensedblack.ttf fonts-noto-ui-extra -notosanstamilui-semicondensedbold.ttf fonts-noto-ui-extra -notosanstamilui-semicondensedextrabold.ttf fonts-noto-ui-extra -notosanstamilui-semicondensedextralight.ttf fonts-noto-ui-extra -notosanstamilui-semicondensedlight.ttf fonts-noto-ui-extra -notosanstamilui-semicondensedmedium.ttf fonts-noto-ui-extra -notosanstamilui-semicondensedsemibold.ttf fonts-noto-ui-extra -notosanstamilui-semicondensedthin.ttf fonts-noto-ui-extra -notosanstamilui-thin.ttf fonts-noto-ui-extra -notosanstelugu-black.ttf fonts-noto-extra -notosanstelugu-bold.ttf fonts-noto-core -notosanstelugu-condensed.ttf fonts-noto-extra -notosanstelugu-condensedblack.ttf fonts-noto-extra -notosanstelugu-condensedbold.ttf fonts-noto-extra -notosanstelugu-condensedextrabold.ttf fonts-noto-extra -notosanstelugu-condensedextralight.ttf fonts-noto-extra -notosanstelugu-condensedlight.ttf fonts-noto-extra -notosanstelugu-condensedmedium.ttf fonts-noto-extra -notosanstelugu-condensedsemibold.ttf fonts-noto-extra -notosanstelugu-condensedthin.ttf fonts-noto-extra -notosanstelugu-extrabold.ttf fonts-noto-extra -notosanstelugu-extracondensed.ttf fonts-noto-extra -notosanstelugu-extracondensedblack.ttf fonts-noto-extra -notosanstelugu-extracondensedbold.ttf fonts-noto-extra -notosanstelugu-extracondensedextrabold.ttf fonts-noto-extra -notosanstelugu-extracondensedextralight.ttf fonts-noto-extra -notosanstelugu-extracondensedlight.ttf fonts-noto-extra -notosanstelugu-extracondensedmedium.ttf fonts-noto-extra -notosanstelugu-extracondensedsemibold.ttf fonts-noto-extra -notosanstelugu-extracondensedthin.ttf fonts-noto-extra -notosanstelugu-extralight.ttf fonts-noto-extra -notosanstelugu-light.ttf fonts-noto-extra -notosanstelugu-medium.ttf fonts-noto-extra -notosanstelugu-regular.ttf fonts-noto-core -notosanstelugu-semibold.ttf fonts-noto-extra -notosanstelugu-semicondensed.ttf fonts-noto-extra -notosanstelugu-semicondensedblack.ttf fonts-noto-extra -notosanstelugu-semicondensedbold.ttf fonts-noto-extra -notosanstelugu-semicondensedextrabold.ttf fonts-noto-extra -notosanstelugu-semicondensedextralight.ttf fonts-noto-extra -notosanstelugu-semicondensedlight.ttf fonts-noto-extra -notosanstelugu-semicondensedmedium.ttf fonts-noto-extra -notosanstelugu-semicondensedsemibold.ttf fonts-noto-extra -notosanstelugu-semicondensedthin.ttf fonts-noto-extra -notosanstelugu-thin.ttf fonts-noto-extra -notosansteluguui-black.ttf fonts-noto-ui-extra -notosansteluguui-bold.ttf fonts-noto-ui-core -notosansteluguui-condensed.ttf fonts-noto-ui-extra -notosansteluguui-condensedblack.ttf fonts-noto-ui-extra -notosansteluguui-condensedbold.ttf fonts-noto-ui-extra -notosansteluguui-condensedextrabold.ttf fonts-noto-ui-extra -notosansteluguui-condensedextralight.ttf fonts-noto-ui-extra -notosansteluguui-condensedlight.ttf fonts-noto-ui-extra -notosansteluguui-condensedmedium.ttf fonts-noto-ui-extra -notosansteluguui-condensedsemibold.ttf fonts-noto-ui-extra -notosansteluguui-condensedthin.ttf fonts-noto-ui-extra -notosansteluguui-extrabold.ttf fonts-noto-ui-extra -notosansteluguui-extracondensed.ttf fonts-noto-ui-extra -notosansteluguui-extracondensedblack.ttf fonts-noto-ui-extra -notosansteluguui-extracondensedbold.ttf fonts-noto-ui-extra -notosansteluguui-extracondensedextrabold.ttf fonts-noto-ui-extra -notosansteluguui-extracondensedextralight.ttf fonts-noto-ui-extra -notosansteluguui-extracondensedlight.ttf fonts-noto-ui-extra -notosansteluguui-extracondensedmedium.ttf fonts-noto-ui-extra -notosansteluguui-extracondensedsemibold.ttf fonts-noto-ui-extra -notosansteluguui-extracondensedthin.ttf fonts-noto-ui-extra -notosansteluguui-extralight.ttf fonts-noto-ui-extra -notosansteluguui-light.ttf fonts-noto-ui-extra -notosansteluguui-medium.ttf fonts-noto-ui-extra -notosansteluguui-regular.ttf fonts-noto-ui-core -notosansteluguui-semibold.ttf fonts-noto-ui-extra -notosansteluguui-semicondensed.ttf fonts-noto-ui-extra -notosansteluguui-semicondensedblack.ttf fonts-noto-ui-extra -notosansteluguui-semicondensedbold.ttf fonts-noto-ui-extra -notosansteluguui-semicondensedextrabold.ttf fonts-noto-ui-extra -notosansteluguui-semicondensedextralight.ttf fonts-noto-ui-extra -notosansteluguui-semicondensedlight.ttf fonts-noto-ui-extra -notosansteluguui-semicondensedmedium.ttf fonts-noto-ui-extra -notosansteluguui-semicondensedsemibold.ttf fonts-noto-ui-extra -notosansteluguui-semicondensedthin.ttf fonts-noto-ui-extra -notosansteluguui-thin.ttf fonts-noto-ui-extra -notosansthaana-black.ttf fonts-noto-extra -notosansthaana-bold.ttf fonts-noto-core -notosansthaana-extrabold.ttf fonts-noto-extra -notosansthaana-extralight.ttf fonts-noto-extra -notosansthaana-light.ttf fonts-noto-extra -notosansthaana-medium.ttf fonts-noto-extra -notosansthaana-regular.ttf fonts-noto-core -notosansthaana-semibold.ttf fonts-noto-extra -notosansthaana-thin.ttf fonts-noto-extra -notosansthai-black.ttf fonts-noto-extra -notosansthai-bold.ttf fonts-noto-core -notosansthai-condensed.ttf fonts-noto-extra -notosansthai-condensedblack.ttf fonts-noto-extra -notosansthai-condensedbold.ttf fonts-noto-extra -notosansthai-condensedextrabold.ttf fonts-noto-extra -notosansthai-condensedextralight.ttf fonts-noto-extra -notosansthai-condensedlight.ttf fonts-noto-extra -notosansthai-condensedmedium.ttf fonts-noto-extra -notosansthai-condensedsemibold.ttf fonts-noto-extra -notosansthai-condensedthin.ttf fonts-noto-extra -notosansthai-extrabold.ttf fonts-noto-extra -notosansthai-extracondensed.ttf fonts-noto-extra -notosansthai-extracondensedblack.ttf fonts-noto-extra -notosansthai-extracondensedbold.ttf fonts-noto-extra -notosansthai-extracondensedextrabold.ttf fonts-noto-extra -notosansthai-extracondensedextralight.ttf fonts-noto-extra -notosansthai-extracondensedlight.ttf fonts-noto-extra -notosansthai-extracondensedmedium.ttf fonts-noto-extra -notosansthai-extracondensedsemibold.ttf fonts-noto-extra -notosansthai-extracondensedthin.ttf fonts-noto-extra -notosansthai-extralight.ttf fonts-noto-extra -notosansthai-light.ttf fonts-noto-extra -notosansthai-medium.ttf fonts-noto-extra -notosansthai-regular.ttf fonts-noto-core -notosansthai-semibold.ttf fonts-noto-extra -notosansthai-semicondensed.ttf fonts-noto-extra -notosansthai-semicondensedblack.ttf fonts-noto-extra -notosansthai-semicondensedbold.ttf fonts-noto-extra -notosansthai-semicondensedextrabold.ttf fonts-noto-extra -notosansthai-semicondensedextralight.ttf fonts-noto-extra -notosansthai-semicondensedlight.ttf fonts-noto-extra -notosansthai-semicondensedmedium.ttf fonts-noto-extra -notosansthai-semicondensedsemibold.ttf fonts-noto-extra -notosansthai-semicondensedthin.ttf fonts-noto-extra -notosansthai-thin.ttf fonts-noto-extra -notosansthaiui-black.ttf fonts-noto-ui-extra -notosansthaiui-bold.ttf fonts-noto-ui-core -notosansthaiui-condensed.ttf fonts-noto-ui-extra -notosansthaiui-condensedblack.ttf fonts-noto-ui-extra -notosansthaiui-condensedbold.ttf fonts-noto-ui-extra -notosansthaiui-condensedextrabold.ttf fonts-noto-ui-extra -notosansthaiui-condensedextralight.ttf fonts-noto-ui-extra -notosansthaiui-condensedlight.ttf fonts-noto-ui-extra -notosansthaiui-condensedmedium.ttf fonts-noto-ui-extra -notosansthaiui-condensedsemibold.ttf fonts-noto-ui-extra -notosansthaiui-condensedthin.ttf fonts-noto-ui-extra -notosansthaiui-extrabold.ttf fonts-noto-ui-extra -notosansthaiui-extracondensed.ttf fonts-noto-ui-extra -notosansthaiui-extracondensedblack.ttf fonts-noto-ui-extra -notosansthaiui-extracondensedbold.ttf fonts-noto-ui-extra -notosansthaiui-extracondensedextrabold.ttf fonts-noto-ui-extra -notosansthaiui-extracondensedextralight.ttf fonts-noto-ui-extra -notosansthaiui-extracondensedlight.ttf fonts-noto-ui-extra -notosansthaiui-extracondensedmedium.ttf fonts-noto-ui-extra -notosansthaiui-extracondensedsemibold.ttf fonts-noto-ui-extra -notosansthaiui-extracondensedthin.ttf fonts-noto-ui-extra -notosansthaiui-extralight.ttf fonts-noto-ui-extra -notosansthaiui-light.ttf fonts-noto-ui-extra -notosansthaiui-medium.ttf fonts-noto-ui-extra -notosansthaiui-regular.ttf fonts-noto-ui-core -notosansthaiui-semibold.ttf fonts-noto-ui-extra -notosansthaiui-semicondensed.ttf fonts-noto-ui-extra -notosansthaiui-semicondensedblack.ttf fonts-noto-ui-extra -notosansthaiui-semicondensedbold.ttf fonts-noto-ui-extra -notosansthaiui-semicondensedextrabold.ttf fonts-noto-ui-extra -notosansthaiui-semicondensedextralight.ttf fonts-noto-ui-extra -notosansthaiui-semicondensedlight.ttf fonts-noto-ui-extra -notosansthaiui-semicondensedmedium.ttf fonts-noto-ui-extra -notosansthaiui-semicondensedsemibold.ttf fonts-noto-ui-extra -notosansthaiui-semicondensedthin.ttf fonts-noto-ui-extra -notosansthaiui-thin.ttf fonts-noto-ui-extra -notosanstibetan-bold.ttf fonts-noto-core -notosanstibetan-regular.ttf fonts-noto-core -notosanstifinagh-regular.ttf fonts-noto-core -notosanstirhuta-regular.ttf fonts-noto-core -notosansugaritic-regular.ttf fonts-noto-core -notosansvai-regular.ttf fonts-noto-core -notosanswancho-regular.ttf fonts-noto-unhinted -notosanswarangciti-regular.ttf fonts-noto-core -notosansyi-regular.ttf fonts-noto-core -notosanszanabazarsquare-regular.ttf fonts-noto-unhinted -notoserif-black.ttf fonts-noto-extra -notoserif-blackitalic.ttf fonts-noto-extra -notoserif-bold.ttf fonts-noto-core -notoserif-bolditalic.ttf fonts-noto-core -notoserif-condensed.ttf fonts-noto-extra -notoserif-condensedblack.ttf fonts-noto-extra -notoserif-condensedblackitalic.ttf fonts-noto-extra -notoserif-condensedbold.ttf fonts-noto-extra -notoserif-condensedbolditalic.ttf fonts-noto-extra -notoserif-condensedextrabold.ttf fonts-noto-extra -notoserif-condensedextrabolditalic.ttf fonts-noto-extra -notoserif-condensedextralight.ttf fonts-noto-extra -notoserif-condensedextralightitalic.ttf fonts-noto-extra -notoserif-condenseditalic.ttf fonts-noto-extra -notoserif-condensedlight.ttf fonts-noto-extra -notoserif-condensedlightitalic.ttf fonts-noto-extra -notoserif-condensedmedium.ttf fonts-noto-extra -notoserif-condensedmediumitalic.ttf fonts-noto-extra -notoserif-condensedsemibold.ttf fonts-noto-extra -notoserif-condensedsemibolditalic.ttf fonts-noto-extra -notoserif-condensedthin.ttf fonts-noto-extra -notoserif-condensedthinitalic.ttf fonts-noto-extra -notoserif-extrabold.ttf fonts-noto-extra -notoserif-extrabolditalic.ttf fonts-noto-extra -notoserif-extracondensed.ttf fonts-noto-extra -notoserif-extracondensedblack.ttf fonts-noto-extra -notoserif-extracondensedblackitalic.ttf fonts-noto-extra -notoserif-extracondensedbold.ttf fonts-noto-extra -notoserif-extracondensedbolditalic.ttf fonts-noto-extra -notoserif-extracondensedextrabold.ttf fonts-noto-extra -notoserif-extracondensedextrabolditalic.ttf fonts-noto-extra -notoserif-extracondensedextralight.ttf fonts-noto-extra -notoserif-extracondensedextralightitalic.ttf fonts-noto-extra -notoserif-extracondenseditalic.ttf fonts-noto-extra -notoserif-extracondensedlight.ttf fonts-noto-extra -notoserif-extracondensedlightitalic.ttf fonts-noto-extra -notoserif-extracondensedmedium.ttf fonts-noto-extra -notoserif-extracondensedmediumitalic.ttf fonts-noto-extra -notoserif-extracondensedsemibold.ttf fonts-noto-extra -notoserif-extracondensedsemibolditalic.ttf fonts-noto-extra -notoserif-extracondensedthin.ttf fonts-noto-extra -notoserif-extracondensedthinitalic.ttf fonts-noto-extra -notoserif-extralight.ttf fonts-noto-extra -notoserif-extralightitalic.ttf fonts-noto-extra -notoserif-italic.ttf fonts-noto-core -notoserif-light.ttf fonts-noto-extra -notoserif-lightitalic.ttf fonts-noto-extra -notoserif-medium.ttf fonts-noto-extra -notoserif-mediumitalic.ttf fonts-noto-extra -notoserif-regular.ttf fonts-noto-core -notoserif-semibold.ttf fonts-noto-extra -notoserif-semibolditalic.ttf fonts-noto-extra -notoserif-semicondensed.ttf fonts-noto-extra -notoserif-semicondensedblack.ttf fonts-noto-extra -notoserif-semicondensedblackitalic.ttf fonts-noto-extra -notoserif-semicondensedbold.ttf fonts-noto-extra -notoserif-semicondensedbolditalic.ttf fonts-noto-extra -notoserif-semicondensedextrabold.ttf fonts-noto-extra -notoserif-semicondensedextrabolditalic.ttf fonts-noto-extra -notoserif-semicondensedextralight.ttf fonts-noto-extra -notoserif-semicondensedextralightitalic.ttf fonts-noto-extra -notoserif-semicondenseditalic.ttf fonts-noto-extra -notoserif-semicondensedlight.ttf fonts-noto-extra -notoserif-semicondensedlightitalic.ttf fonts-noto-extra -notoserif-semicondensedmedium.ttf fonts-noto-extra -notoserif-semicondensedmediumitalic.ttf fonts-noto-extra -notoserif-semicondensedsemibold.ttf fonts-noto-extra -notoserif-semicondensedsemibolditalic.ttf fonts-noto-extra -notoserif-semicondensedthin.ttf fonts-noto-extra -notoserif-semicondensedthinitalic.ttf fonts-noto-extra -notoserif-thin.ttf fonts-noto-extra -notoserif-thinitalic.ttf fonts-noto-extra -notoserifahom-regular.ttf fonts-noto-core -notoserifarmenian-black.ttf fonts-noto-extra -notoserifarmenian-bold.ttf fonts-noto-core -notoserifarmenian-condensed.ttf fonts-noto-extra -notoserifarmenian-condensedblack.ttf fonts-noto-extra -notoserifarmenian-condensedbold.ttf fonts-noto-extra -notoserifarmenian-condensedextrabold.ttf fonts-noto-extra -notoserifarmenian-condensedextralight.ttf fonts-noto-extra -notoserifarmenian-condensedlight.ttf fonts-noto-extra -notoserifarmenian-condensedmedium.ttf fonts-noto-extra -notoserifarmenian-condensedsemibold.ttf fonts-noto-extra -notoserifarmenian-condensedthin.ttf fonts-noto-extra -notoserifarmenian-extrabold.ttf fonts-noto-extra -notoserifarmenian-extracondensed.ttf fonts-noto-extra -notoserifarmenian-extracondensedblack.ttf fonts-noto-extra -notoserifarmenian-extracondensedbold.ttf fonts-noto-extra -notoserifarmenian-extracondensedextrabold.ttf fonts-noto-extra -notoserifarmenian-extracondensedextralight.ttf fonts-noto-extra -notoserifarmenian-extracondensedlight.ttf fonts-noto-extra -notoserifarmenian-extracondensedmedium.ttf fonts-noto-extra -notoserifarmenian-extracondensedsemibold.ttf fonts-noto-extra -notoserifarmenian-extracondensedthin.ttf fonts-noto-extra -notoserifarmenian-extralight.ttf fonts-noto-extra -notoserifarmenian-light.ttf fonts-noto-extra -notoserifarmenian-medium.ttf fonts-noto-extra -notoserifarmenian-regular.ttf fonts-noto-core -notoserifarmenian-semibold.ttf fonts-noto-extra -notoserifarmenian-semicondensed.ttf fonts-noto-extra -notoserifarmenian-semicondensedblack.ttf fonts-noto-extra -notoserifarmenian-semicondensedbold.ttf fonts-noto-extra -notoserifarmenian-semicondensedextrabold.ttf fonts-noto-extra -notoserifarmenian-semicondensedextralight.ttf fonts-noto-extra -notoserifarmenian-semicondensedlight.ttf fonts-noto-extra -notoserifarmenian-semicondensedmedium.ttf fonts-noto-extra -notoserifarmenian-semicondensedsemibold.ttf fonts-noto-extra -notoserifarmenian-semicondensedthin.ttf fonts-noto-extra -notoserifarmenian-thin.ttf fonts-noto-extra -notoserifbalinese-regular.ttf fonts-noto-core -notoserifbengali-black.ttf fonts-noto-extra -notoserifbengali-bold.ttf fonts-noto-core -notoserifbengali-condensed.ttf fonts-noto-extra -notoserifbengali-condensedblack.ttf fonts-noto-extra -notoserifbengali-condensedbold.ttf fonts-noto-extra -notoserifbengali-condensedextrabold.ttf fonts-noto-extra -notoserifbengali-condensedextralight.ttf fonts-noto-extra -notoserifbengali-condensedlight.ttf fonts-noto-extra -notoserifbengali-condensedmedium.ttf fonts-noto-extra -notoserifbengali-condensedsemibold.ttf fonts-noto-extra -notoserifbengali-condensedthin.ttf fonts-noto-extra -notoserifbengali-extrabold.ttf fonts-noto-extra -notoserifbengali-extracondensed.ttf fonts-noto-extra -notoserifbengali-extracondensedblack.ttf fonts-noto-extra -notoserifbengali-extracondensedbold.ttf fonts-noto-extra -notoserifbengali-extracondensedextrabold.ttf fonts-noto-extra -notoserifbengali-extracondensedextralight.ttf fonts-noto-extra -notoserifbengali-extracondensedlight.ttf fonts-noto-extra -notoserifbengali-extracondensedmedium.ttf fonts-noto-extra -notoserifbengali-extracondensedsemibold.ttf fonts-noto-extra -notoserifbengali-extracondensedthin.ttf fonts-noto-extra -notoserifbengali-extralight.ttf fonts-noto-extra -notoserifbengali-light.ttf fonts-noto-extra -notoserifbengali-medium.ttf fonts-noto-extra -notoserifbengali-regular.ttf fonts-noto-core -notoserifbengali-semibold.ttf fonts-noto-extra -notoserifbengali-semicondensed.ttf fonts-noto-extra -notoserifbengali-semicondensedblack.ttf fonts-noto-extra -notoserifbengali-semicondensedbold.ttf fonts-noto-extra -notoserifbengali-semicondensedextrabold.ttf fonts-noto-extra -notoserifbengali-semicondensedextralight.ttf fonts-noto-extra -notoserifbengali-semicondensedlight.ttf fonts-noto-extra -notoserifbengali-semicondensedmedium.ttf fonts-noto-extra -notoserifbengali-semicondensedsemibold.ttf fonts-noto-extra -notoserifbengali-semicondensedthin.ttf fonts-noto-extra -notoserifbengali-thin.ttf fonts-noto-extra -notoserifdevanagari-black.ttf fonts-noto-extra -notoserifdevanagari-bold.ttf fonts-noto-core -notoserifdevanagari-condensed.ttf fonts-noto-extra -notoserifdevanagari-condensedblack.ttf fonts-noto-extra -notoserifdevanagari-condensedbold.ttf fonts-noto-extra -notoserifdevanagari-condensedextrabold.ttf fonts-noto-extra -notoserifdevanagari-condensedextralight.ttf fonts-noto-extra -notoserifdevanagari-condensedlight.ttf fonts-noto-extra -notoserifdevanagari-condensedmedium.ttf fonts-noto-extra -notoserifdevanagari-condensedsemibold.ttf fonts-noto-extra -notoserifdevanagari-condensedthin.ttf fonts-noto-extra -notoserifdevanagari-extrabold.ttf fonts-noto-extra -notoserifdevanagari-extracondensed.ttf fonts-noto-extra -notoserifdevanagari-extracondensedblack.ttf fonts-noto-extra -notoserifdevanagari-extracondensedbold.ttf fonts-noto-extra -notoserifdevanagari-extracondensedextrabold.ttf fonts-noto-extra -notoserifdevanagari-extracondensedextralight.ttf fonts-noto-extra -notoserifdevanagari-extracondensedlight.ttf fonts-noto-extra -notoserifdevanagari-extracondensedmedium.ttf fonts-noto-extra -notoserifdevanagari-extracondensedsemibold.ttf fonts-noto-extra -notoserifdevanagari-extracondensedthin.ttf fonts-noto-extra -notoserifdevanagari-extralight.ttf fonts-noto-extra -notoserifdevanagari-light.ttf fonts-noto-extra -notoserifdevanagari-medium.ttf fonts-noto-extra -notoserifdevanagari-regular.ttf fonts-noto-core -notoserifdevanagari-semibold.ttf fonts-noto-extra -notoserifdevanagari-semicondensed.ttf fonts-noto-extra -notoserifdevanagari-semicondensedblack.ttf fonts-noto-extra -notoserifdevanagari-semicondensedbold.ttf fonts-noto-extra -notoserifdevanagari-semicondensedextrabold.ttf fonts-noto-extra -notoserifdevanagari-semicondensedextralight.ttf fonts-noto-extra -notoserifdevanagari-semicondensedlight.ttf fonts-noto-extra -notoserifdevanagari-semicondensedmedium.ttf fonts-noto-extra -notoserifdevanagari-semicondensedsemibold.ttf fonts-noto-extra -notoserifdevanagari-semicondensedthin.ttf fonts-noto-extra -notoserifdevanagari-thin.ttf fonts-noto-extra -notoserifdisplay-black.ttf fonts-noto-extra -notoserifdisplay-blackitalic.ttf fonts-noto-extra -notoserifdisplay-bold.ttf fonts-noto-core -notoserifdisplay-bolditalic.ttf fonts-noto-core -notoserifdisplay-condensed.ttf fonts-noto-extra -notoserifdisplay-condensedblack.ttf fonts-noto-extra -notoserifdisplay-condensedblackitalic.ttf fonts-noto-extra -notoserifdisplay-condensedbold.ttf fonts-noto-extra -notoserifdisplay-condensedbolditalic.ttf fonts-noto-extra -notoserifdisplay-condensedextrabold.ttf fonts-noto-extra -notoserifdisplay-condensedextrabolditalic.ttf fonts-noto-extra -notoserifdisplay-condensedextralight.ttf fonts-noto-extra -notoserifdisplay-condensedextralightitalic.ttf fonts-noto-extra -notoserifdisplay-condenseditalic.ttf fonts-noto-extra -notoserifdisplay-condensedlight.ttf fonts-noto-extra -notoserifdisplay-condensedlightitalic.ttf fonts-noto-extra -notoserifdisplay-condensedmedium.ttf fonts-noto-extra -notoserifdisplay-condensedmediumitalic.ttf fonts-noto-extra -notoserifdisplay-condensedsemibold.ttf fonts-noto-extra -notoserifdisplay-condensedsemibolditalic.ttf fonts-noto-extra -notoserifdisplay-condensedthin.ttf fonts-noto-extra -notoserifdisplay-condensedthinitalic.ttf fonts-noto-extra -notoserifdisplay-extrabold.ttf fonts-noto-extra -notoserifdisplay-extrabolditalic.ttf fonts-noto-extra -notoserifdisplay-extracondensed.ttf fonts-noto-extra -notoserifdisplay-extracondensedblack.ttf fonts-noto-extra -notoserifdisplay-extracondensedblackitalic.ttf fonts-noto-extra -notoserifdisplay-extracondensedbold.ttf fonts-noto-extra -notoserifdisplay-extracondensedbolditalic.ttf fonts-noto-extra -notoserifdisplay-extracondensedextrabold.ttf fonts-noto-extra -notoserifdisplay-extracondensedextrabolditalic.ttf fonts-noto-extra -notoserifdisplay-extracondensedextralight.ttf fonts-noto-extra -notoserifdisplay-extracondensedextralightitalic.ttf fonts-noto-extra -notoserifdisplay-extracondenseditalic.ttf fonts-noto-extra -notoserifdisplay-extracondensedlight.ttf fonts-noto-extra -notoserifdisplay-extracondensedlightitalic.ttf fonts-noto-extra -notoserifdisplay-extracondensedmedium.ttf fonts-noto-extra -notoserifdisplay-extracondensedmediumitalic.ttf fonts-noto-extra -notoserifdisplay-extracondensedsemibold.ttf fonts-noto-extra -notoserifdisplay-extracondensedsemibolditalic.ttf fonts-noto-extra -notoserifdisplay-extracondensedthin.ttf fonts-noto-extra -notoserifdisplay-extracondensedthinitalic.ttf fonts-noto-extra -notoserifdisplay-extralight.ttf fonts-noto-extra -notoserifdisplay-extralightitalic.ttf fonts-noto-extra -notoserifdisplay-italic.ttf fonts-noto-core -notoserifdisplay-light.ttf fonts-noto-extra -notoserifdisplay-lightitalic.ttf fonts-noto-extra -notoserifdisplay-medium.ttf fonts-noto-extra -notoserifdisplay-mediumitalic.ttf fonts-noto-extra -notoserifdisplay-regular.ttf fonts-noto-core -notoserifdisplay-semibold.ttf fonts-noto-extra -notoserifdisplay-semibolditalic.ttf fonts-noto-extra -notoserifdisplay-semicondensed.ttf fonts-noto-extra -notoserifdisplay-semicondensedblack.ttf fonts-noto-extra -notoserifdisplay-semicondensedblackitalic.ttf fonts-noto-extra -notoserifdisplay-semicondensedbold.ttf fonts-noto-extra -notoserifdisplay-semicondensedbolditalic.ttf fonts-noto-extra -notoserifdisplay-semicondensedextrabold.ttf fonts-noto-extra -notoserifdisplay-semicondensedextrabolditalic.ttf fonts-noto-extra -notoserifdisplay-semicondensedextralight.ttf fonts-noto-extra -notoserifdisplay-semicondensedextralightitalic.ttf fonts-noto-extra -notoserifdisplay-semicondenseditalic.ttf fonts-noto-extra -notoserifdisplay-semicondensedlight.ttf fonts-noto-extra -notoserifdisplay-semicondensedlightitalic.ttf fonts-noto-extra -notoserifdisplay-semicondensedmedium.ttf fonts-noto-extra -notoserifdisplay-semicondensedmediumitalic.ttf fonts-noto-extra -notoserifdisplay-semicondensedsemibold.ttf fonts-noto-extra -notoserifdisplay-semicondensedsemibolditalic.ttf fonts-noto-extra -notoserifdisplay-semicondensedthin.ttf fonts-noto-extra -notoserifdisplay-semicondensedthinitalic.ttf fonts-noto-extra -notoserifdisplay-thin.ttf fonts-noto-extra -notoserifdisplay-thinitalic.ttf fonts-noto-extra -notoserifdogra-regular.ttf fonts-noto-core -notoserifethiopic-black.ttf fonts-noto-extra -notoserifethiopic-bold.ttf fonts-noto-core -notoserifethiopic-condensed.ttf fonts-noto-extra -notoserifethiopic-condensedblack.ttf fonts-noto-extra -notoserifethiopic-condensedbold.ttf fonts-noto-extra -notoserifethiopic-condensedextrabold.ttf fonts-noto-extra -notoserifethiopic-condensedextralight.ttf fonts-noto-extra -notoserifethiopic-condensedlight.ttf fonts-noto-extra -notoserifethiopic-condensedmedium.ttf fonts-noto-extra -notoserifethiopic-condensedsemibold.ttf fonts-noto-extra -notoserifethiopic-condensedthin.ttf fonts-noto-extra -notoserifethiopic-extrabold.ttf fonts-noto-extra -notoserifethiopic-extracondensed.ttf fonts-noto-extra -notoserifethiopic-extracondensedblack.ttf fonts-noto-extra -notoserifethiopic-extracondensedbold.ttf fonts-noto-extra -notoserifethiopic-extracondensedextrabold.ttf fonts-noto-extra -notoserifethiopic-extracondensedextralight.ttf fonts-noto-extra -notoserifethiopic-extracondensedlight.ttf fonts-noto-extra -notoserifethiopic-extracondensedmedium.ttf fonts-noto-extra -notoserifethiopic-extracondensedsemibold.ttf fonts-noto-extra -notoserifethiopic-extracondensedthin.ttf fonts-noto-extra -notoserifethiopic-extralight.ttf fonts-noto-extra -notoserifethiopic-light.ttf fonts-noto-extra -notoserifethiopic-medium.ttf fonts-noto-extra -notoserifethiopic-regular.ttf fonts-noto-core -notoserifethiopic-semibold.ttf fonts-noto-extra -notoserifethiopic-semicondensed.ttf fonts-noto-extra -notoserifethiopic-semicondensedblack.ttf fonts-noto-extra -notoserifethiopic-semicondensedbold.ttf fonts-noto-extra -notoserifethiopic-semicondensedextrabold.ttf fonts-noto-extra -notoserifethiopic-semicondensedextralight.ttf fonts-noto-extra -notoserifethiopic-semicondensedlight.ttf fonts-noto-extra -notoserifethiopic-semicondensedmedium.ttf fonts-noto-extra -notoserifethiopic-semicondensedsemibold.ttf fonts-noto-extra -notoserifethiopic-semicondensedthin.ttf fonts-noto-extra -notoserifethiopic-thin.ttf fonts-noto-extra -notoserifgeorgian-black.ttf fonts-noto-extra -notoserifgeorgian-bold.ttf fonts-noto-core -notoserifgeorgian-condensed.ttf fonts-noto-extra -notoserifgeorgian-condensedblack.ttf fonts-noto-extra -notoserifgeorgian-condensedbold.ttf fonts-noto-extra -notoserifgeorgian-condensedextrabold.ttf fonts-noto-extra -notoserifgeorgian-condensedextralight.ttf fonts-noto-extra -notoserifgeorgian-condensedlight.ttf fonts-noto-extra -notoserifgeorgian-condensedmedium.ttf fonts-noto-extra -notoserifgeorgian-condensedsemibold.ttf fonts-noto-extra -notoserifgeorgian-condensedthin.ttf fonts-noto-extra -notoserifgeorgian-extrabold.ttf fonts-noto-extra -notoserifgeorgian-extracondensed.ttf fonts-noto-extra -notoserifgeorgian-extracondensedblack.ttf fonts-noto-extra -notoserifgeorgian-extracondensedbold.ttf fonts-noto-extra -notoserifgeorgian-extracondensedextrabold.ttf fonts-noto-extra -notoserifgeorgian-extracondensedextralight.ttf fonts-noto-extra -notoserifgeorgian-extracondensedlight.ttf fonts-noto-extra -notoserifgeorgian-extracondensedmedium.ttf fonts-noto-extra -notoserifgeorgian-extracondensedsemibold.ttf fonts-noto-extra -notoserifgeorgian-extracondensedthin.ttf fonts-noto-extra -notoserifgeorgian-extralight.ttf fonts-noto-extra -notoserifgeorgian-light.ttf fonts-noto-extra -notoserifgeorgian-medium.ttf fonts-noto-extra -notoserifgeorgian-regular.ttf fonts-noto-core -notoserifgeorgian-semibold.ttf fonts-noto-extra -notoserifgeorgian-semicondensed.ttf fonts-noto-extra -notoserifgeorgian-semicondensedblack.ttf fonts-noto-extra -notoserifgeorgian-semicondensedbold.ttf fonts-noto-extra -notoserifgeorgian-semicondensedextrabold.ttf fonts-noto-extra -notoserifgeorgian-semicondensedextralight.ttf fonts-noto-extra -notoserifgeorgian-semicondensedlight.ttf fonts-noto-extra -notoserifgeorgian-semicondensedmedium.ttf fonts-noto-extra -notoserifgeorgian-semicondensedsemibold.ttf fonts-noto-extra -notoserifgeorgian-semicondensedthin.ttf fonts-noto-extra -notoserifgeorgian-thin.ttf fonts-noto-extra -notoserifgujarati-black.ttf fonts-noto-extra -notoserifgujarati-bold.ttf fonts-noto-core -notoserifgujarati-extrabold.ttf fonts-noto-extra -notoserifgujarati-extralight.ttf fonts-noto-extra -notoserifgujarati-light.ttf fonts-noto-extra -notoserifgujarati-medium.ttf fonts-noto-extra -notoserifgujarati-regular.ttf fonts-noto-core -notoserifgujarati-semibold.ttf fonts-noto-extra -notoserifgujarati-thin.ttf fonts-noto-extra -notoserifgurmukhi-black.ttf fonts-noto-extra -notoserifgurmukhi-bold.ttf fonts-noto-core -notoserifgurmukhi-extrabold.ttf fonts-noto-extra -notoserifgurmukhi-extralight.ttf fonts-noto-extra -notoserifgurmukhi-light.ttf fonts-noto-extra -notoserifgurmukhi-medium.ttf fonts-noto-extra -notoserifgurmukhi-regular.ttf fonts-noto-core -notoserifgurmukhi-semibold.ttf fonts-noto-extra -notoserifgurmukhi-thin.ttf fonts-noto-extra -notoserifhebrew-black.ttf fonts-noto-extra -notoserifhebrew-bold.ttf fonts-noto-core -notoserifhebrew-condensed.ttf fonts-noto-extra -notoserifhebrew-condensedblack.ttf fonts-noto-extra -notoserifhebrew-condensedbold.ttf fonts-noto-extra -notoserifhebrew-condensedextrabold.ttf fonts-noto-extra -notoserifhebrew-condensedextralight.ttf fonts-noto-extra -notoserifhebrew-condensedlight.ttf fonts-noto-extra -notoserifhebrew-condensedmedium.ttf fonts-noto-extra -notoserifhebrew-condensedsemibold.ttf fonts-noto-extra -notoserifhebrew-condensedthin.ttf fonts-noto-extra -notoserifhebrew-extrabold.ttf fonts-noto-extra -notoserifhebrew-extracondensed.ttf fonts-noto-extra -notoserifhebrew-extracondensedblack.ttf fonts-noto-extra -notoserifhebrew-extracondensedbold.ttf fonts-noto-extra -notoserifhebrew-extracondensedextrabold.ttf fonts-noto-extra -notoserifhebrew-extracondensedextralight.ttf fonts-noto-extra -notoserifhebrew-extracondensedlight.ttf fonts-noto-extra -notoserifhebrew-extracondensedmedium.ttf fonts-noto-extra -notoserifhebrew-extracondensedsemibold.ttf fonts-noto-extra -notoserifhebrew-extracondensedthin.ttf fonts-noto-extra -notoserifhebrew-extralight.ttf fonts-noto-extra -notoserifhebrew-light.ttf fonts-noto-extra -notoserifhebrew-medium.ttf fonts-noto-extra -notoserifhebrew-regular.ttf fonts-noto-core -notoserifhebrew-semibold.ttf fonts-noto-extra -notoserifhebrew-semicondensed.ttf fonts-noto-extra -notoserifhebrew-semicondensedblack.ttf fonts-noto-extra -notoserifhebrew-semicondensedbold.ttf fonts-noto-extra -notoserifhebrew-semicondensedextrabold.ttf fonts-noto-extra -notoserifhebrew-semicondensedextralight.ttf fonts-noto-extra -notoserifhebrew-semicondensedlight.ttf fonts-noto-extra -notoserifhebrew-semicondensedmedium.ttf fonts-noto-extra -notoserifhebrew-semicondensedsemibold.ttf fonts-noto-extra -notoserifhebrew-semicondensedthin.ttf fonts-noto-extra -notoserifhebrew-thin.ttf fonts-noto-extra -notoserifkannada-black.ttf fonts-noto-extra -notoserifkannada-bold.ttf fonts-noto-core -notoserifkannada-extrabold.ttf fonts-noto-extra -notoserifkannada-extralight.ttf fonts-noto-extra -notoserifkannada-light.ttf fonts-noto-extra -notoserifkannada-medium.ttf fonts-noto-extra -notoserifkannada-regular.ttf fonts-noto-core -notoserifkannada-semibold.ttf fonts-noto-extra -notoserifkannada-thin.ttf fonts-noto-extra -notoserifkhmer-black.ttf fonts-noto-extra -notoserifkhmer-bold.ttf fonts-noto-core -notoserifkhmer-condensed.ttf fonts-noto-extra -notoserifkhmer-condensedblack.ttf fonts-noto-extra -notoserifkhmer-condensedbold.ttf fonts-noto-extra -notoserifkhmer-condensedextrabold.ttf fonts-noto-extra -notoserifkhmer-condensedextralight.ttf fonts-noto-extra -notoserifkhmer-condensedlight.ttf fonts-noto-extra -notoserifkhmer-condensedmedium.ttf fonts-noto-extra -notoserifkhmer-condensedsemibold.ttf fonts-noto-extra -notoserifkhmer-condensedthin.ttf fonts-noto-extra -notoserifkhmer-extrabold.ttf fonts-noto-extra -notoserifkhmer-extracondensed.ttf fonts-noto-extra -notoserifkhmer-extracondensedblack.ttf fonts-noto-extra -notoserifkhmer-extracondensedbold.ttf fonts-noto-extra -notoserifkhmer-extracondensedextrabold.ttf fonts-noto-extra -notoserifkhmer-extracondensedextralight.ttf fonts-noto-extra -notoserifkhmer-extracondensedlight.ttf fonts-noto-extra -notoserifkhmer-extracondensedmedium.ttf fonts-noto-extra -notoserifkhmer-extracondensedsemibold.ttf fonts-noto-extra -notoserifkhmer-extracondensedthin.ttf fonts-noto-extra -notoserifkhmer-extralight.ttf fonts-noto-extra -notoserifkhmer-light.ttf fonts-noto-extra -notoserifkhmer-medium.ttf fonts-noto-extra -notoserifkhmer-regular.ttf fonts-noto-core -notoserifkhmer-semibold.ttf fonts-noto-extra -notoserifkhmer-semicondensed.ttf fonts-noto-extra -notoserifkhmer-semicondensedblack.ttf fonts-noto-extra -notoserifkhmer-semicondensedbold.ttf fonts-noto-extra -notoserifkhmer-semicondensedextrabold.ttf fonts-noto-extra -notoserifkhmer-semicondensedextralight.ttf fonts-noto-extra -notoserifkhmer-semicondensedlight.ttf fonts-noto-extra -notoserifkhmer-semicondensedmedium.ttf fonts-noto-extra -notoserifkhmer-semicondensedsemibold.ttf fonts-noto-extra -notoserifkhmer-semicondensedthin.ttf fonts-noto-extra -notoserifkhmer-thin.ttf fonts-noto-extra -notoseriflao-black.ttf fonts-noto-extra -notoseriflao-bold.ttf fonts-noto-core -notoseriflao-condensed.ttf fonts-noto-extra -notoseriflao-condensedblack.ttf fonts-noto-extra -notoseriflao-condensedbold.ttf fonts-noto-extra -notoseriflao-condensedextrabold.ttf fonts-noto-extra -notoseriflao-condensedextralight.ttf fonts-noto-extra -notoseriflao-condensedlight.ttf fonts-noto-extra -notoseriflao-condensedmedium.ttf fonts-noto-extra -notoseriflao-condensedsemibold.ttf fonts-noto-extra -notoseriflao-condensedthin.ttf fonts-noto-extra -notoseriflao-extrabold.ttf fonts-noto-extra -notoseriflao-extracondensed.ttf fonts-noto-extra -notoseriflao-extracondensedblack.ttf fonts-noto-extra -notoseriflao-extracondensedbold.ttf fonts-noto-extra -notoseriflao-extracondensedextrabold.ttf fonts-noto-extra -notoseriflao-extracondensedextralight.ttf fonts-noto-extra -notoseriflao-extracondensedlight.ttf fonts-noto-extra -notoseriflao-extracondensedmedium.ttf fonts-noto-extra -notoseriflao-extracondensedsemibold.ttf fonts-noto-extra -notoseriflao-extracondensedthin.ttf fonts-noto-extra -notoseriflao-extralight.ttf fonts-noto-extra -notoseriflao-light.ttf fonts-noto-extra -notoseriflao-medium.ttf fonts-noto-extra -notoseriflao-regular.ttf fonts-noto-core -notoseriflao-semibold.ttf fonts-noto-extra -notoseriflao-semicondensed.ttf fonts-noto-extra -notoseriflao-semicondensedblack.ttf fonts-noto-extra -notoseriflao-semicondensedbold.ttf fonts-noto-extra -notoseriflao-semicondensedextrabold.ttf fonts-noto-extra -notoseriflao-semicondensedextralight.ttf fonts-noto-extra -notoseriflao-semicondensedlight.ttf fonts-noto-extra -notoseriflao-semicondensedmedium.ttf fonts-noto-extra -notoseriflao-semicondensedsemibold.ttf fonts-noto-extra -notoseriflao-semicondensedthin.ttf fonts-noto-extra -notoseriflao-thin.ttf fonts-noto-extra -notoserifmalayalam-black.ttf fonts-noto-extra -notoserifmalayalam-bold.ttf fonts-noto-core -notoserifmalayalam-extrabold.ttf fonts-noto-extra -notoserifmalayalam-extralight.ttf fonts-noto-extra -notoserifmalayalam-light.ttf fonts-noto-extra -notoserifmalayalam-medium.ttf fonts-noto-extra -notoserifmalayalam-regular.ttf fonts-noto-core -notoserifmalayalam-semibold.ttf fonts-noto-extra -notoserifmalayalam-thin.ttf fonts-noto-extra -notoserifmyanmar-black.ttf fonts-noto-extra -notoserifmyanmar-bold.ttf fonts-noto-core -notoserifmyanmar-condensed.ttf fonts-noto-extra -notoserifmyanmar-condensedblack.ttf fonts-noto-extra -notoserifmyanmar-condensedbold.ttf fonts-noto-extra -notoserifmyanmar-condensedextrabold.ttf fonts-noto-extra -notoserifmyanmar-condensedextralight.ttf fonts-noto-extra -notoserifmyanmar-condensedlight.ttf fonts-noto-extra -notoserifmyanmar-condensedmedium.ttf fonts-noto-extra -notoserifmyanmar-condensedsemibold.ttf fonts-noto-extra -notoserifmyanmar-condensedthin.ttf fonts-noto-extra -notoserifmyanmar-extrabold.ttf fonts-noto-extra -notoserifmyanmar-extracondensed.ttf fonts-noto-extra -notoserifmyanmar-extracondensedblack.ttf fonts-noto-extra -notoserifmyanmar-extracondensedbold.ttf fonts-noto-extra -notoserifmyanmar-extracondensedextrabold.ttf fonts-noto-extra -notoserifmyanmar-extracondensedextralight.ttf fonts-noto-extra -notoserifmyanmar-extracondensedlight.ttf fonts-noto-extra -notoserifmyanmar-extracondensedmedium.ttf fonts-noto-extra -notoserifmyanmar-extracondensedsemibold.ttf fonts-noto-extra -notoserifmyanmar-extracondensedthin.ttf fonts-noto-extra -notoserifmyanmar-extralight.ttf fonts-noto-extra -notoserifmyanmar-light.ttf fonts-noto-extra -notoserifmyanmar-medium.ttf fonts-noto-extra -notoserifmyanmar-regular.ttf fonts-noto-core -notoserifmyanmar-semibold.ttf fonts-noto-extra -notoserifmyanmar-semicondensed.ttf fonts-noto-extra -notoserifmyanmar-semicondensedblack.ttf fonts-noto-extra -notoserifmyanmar-semicondensedbold.ttf fonts-noto-extra -notoserifmyanmar-semicondensedextrabold.ttf fonts-noto-extra -notoserifmyanmar-semicondensedextralight.ttf fonts-noto-extra -notoserifmyanmar-semicondensedlight.ttf fonts-noto-extra -notoserifmyanmar-semicondensedmedium.ttf fonts-noto-extra -notoserifmyanmar-semicondensedsemibold.ttf fonts-noto-extra -notoserifmyanmar-semicondensedthin.ttf fonts-noto-extra -notoserifmyanmar-thin.ttf fonts-noto-extra -notoserifsinhala-black.ttf fonts-noto-extra -notoserifsinhala-bold.ttf fonts-noto-core -notoserifsinhala-condensed.ttf fonts-noto-extra -notoserifsinhala-condensedblack.ttf fonts-noto-extra -notoserifsinhala-condensedbold.ttf fonts-noto-extra -notoserifsinhala-condensedextrabold.ttf fonts-noto-extra -notoserifsinhala-condensedextralight.ttf fonts-noto-extra -notoserifsinhala-condensedlight.ttf fonts-noto-extra -notoserifsinhala-condensedmedium.ttf fonts-noto-extra -notoserifsinhala-condensedsemibold.ttf fonts-noto-extra -notoserifsinhala-condensedthin.ttf fonts-noto-extra -notoserifsinhala-extrabold.ttf fonts-noto-extra -notoserifsinhala-extracondensed.ttf fonts-noto-extra -notoserifsinhala-extracondensedblack.ttf fonts-noto-extra -notoserifsinhala-extracondensedbold.ttf fonts-noto-extra -notoserifsinhala-extracondensedextrabold.ttf fonts-noto-extra -notoserifsinhala-extracondensedextralight.ttf fonts-noto-extra -notoserifsinhala-extracondensedlight.ttf fonts-noto-extra -notoserifsinhala-extracondensedmedium.ttf fonts-noto-extra -notoserifsinhala-extracondensedsemibold.ttf fonts-noto-extra -notoserifsinhala-extracondensedthin.ttf fonts-noto-extra -notoserifsinhala-extralight.ttf fonts-noto-extra -notoserifsinhala-light.ttf fonts-noto-extra -notoserifsinhala-medium.ttf fonts-noto-extra -notoserifsinhala-regular.ttf fonts-noto-core -notoserifsinhala-semibold.ttf fonts-noto-extra -notoserifsinhala-semicondensed.ttf fonts-noto-extra -notoserifsinhala-semicondensedblack.ttf fonts-noto-extra -notoserifsinhala-semicondensedbold.ttf fonts-noto-extra -notoserifsinhala-semicondensedextrabold.ttf fonts-noto-extra -notoserifsinhala-semicondensedextralight.ttf fonts-noto-extra -notoserifsinhala-semicondensedlight.ttf fonts-noto-extra -notoserifsinhala-semicondensedmedium.ttf fonts-noto-extra -notoserifsinhala-semicondensedsemibold.ttf fonts-noto-extra -notoserifsinhala-semicondensedthin.ttf fonts-noto-extra -notoserifsinhala-thin.ttf fonts-noto-extra -notoseriftamil-black.ttf fonts-noto-extra -notoseriftamil-bold.ttf fonts-noto-core -notoseriftamil-condensed.ttf fonts-noto-extra -notoseriftamil-condensedblack.ttf fonts-noto-extra -notoseriftamil-condensedbold.ttf fonts-noto-extra -notoseriftamil-condensedextrabold.ttf fonts-noto-extra -notoseriftamil-condensedextralight.ttf fonts-noto-extra -notoseriftamil-condensedlight.ttf fonts-noto-extra -notoseriftamil-condensedmedium.ttf fonts-noto-extra -notoseriftamil-condensedsemibold.ttf fonts-noto-extra -notoseriftamil-condensedthin.ttf fonts-noto-extra -notoseriftamil-extrabold.ttf fonts-noto-extra -notoseriftamil-extracondensed.ttf fonts-noto-extra -notoseriftamil-extracondensedblack.ttf fonts-noto-extra -notoseriftamil-extracondensedbold.ttf fonts-noto-extra -notoseriftamil-extracondensedextrabold.ttf fonts-noto-extra -notoseriftamil-extracondensedextralight.ttf fonts-noto-extra -notoseriftamil-extracondensedlight.ttf fonts-noto-extra -notoseriftamil-extracondensedmedium.ttf fonts-noto-extra -notoseriftamil-extracondensedsemibold.ttf fonts-noto-extra -notoseriftamil-extracondensedthin.ttf fonts-noto-extra -notoseriftamil-extralight.ttf fonts-noto-extra -notoseriftamil-light.ttf fonts-noto-extra -notoseriftamil-medium.ttf fonts-noto-extra -notoseriftamil-regular.ttf fonts-noto-core -notoseriftamil-semibold.ttf fonts-noto-extra -notoseriftamil-semicondensed.ttf fonts-noto-extra -notoseriftamil-semicondensedblack.ttf fonts-noto-extra -notoseriftamil-semicondensedbold.ttf fonts-noto-extra -notoseriftamil-semicondensedextrabold.ttf fonts-noto-extra -notoseriftamil-semicondensedextralight.ttf fonts-noto-extra -notoseriftamil-semicondensedlight.ttf fonts-noto-extra -notoseriftamil-semicondensedmedium.ttf fonts-noto-extra -notoseriftamil-semicondensedsemibold.ttf fonts-noto-extra -notoseriftamil-semicondensedthin.ttf fonts-noto-extra -notoseriftamil-thin.ttf fonts-noto-extra -notoseriftamilslanted-black.ttf fonts-noto-extra -notoseriftamilslanted-bold.ttf fonts-noto-core -notoseriftamilslanted-condensed.ttf fonts-noto-extra -notoseriftamilslanted-condensedblack.ttf fonts-noto-extra -notoseriftamilslanted-condensedbold.ttf fonts-noto-extra -notoseriftamilslanted-condensedextrabold.ttf fonts-noto-extra -notoseriftamilslanted-condensedextralight.ttf fonts-noto-extra -notoseriftamilslanted-condensedlight.ttf fonts-noto-extra -notoseriftamilslanted-condensedmedium.ttf fonts-noto-extra -notoseriftamilslanted-condensedsemibold.ttf fonts-noto-extra -notoseriftamilslanted-condensedthin.ttf fonts-noto-extra -notoseriftamilslanted-extrabold.ttf fonts-noto-extra -notoseriftamilslanted-extracondensed.ttf fonts-noto-extra -notoseriftamilslanted-extracondensedblack.ttf fonts-noto-extra -notoseriftamilslanted-extracondensedbold.ttf fonts-noto-extra -notoseriftamilslanted-extracondensedextrabold.ttf fonts-noto-extra -notoseriftamilslanted-extracondensedextralight.ttf fonts-noto-extra -notoseriftamilslanted-extracondensedlight.ttf fonts-noto-extra -notoseriftamilslanted-extracondensedmedium.ttf fonts-noto-extra -notoseriftamilslanted-extracondensedsemibold.ttf fonts-noto-extra -notoseriftamilslanted-extracondensedthin.ttf fonts-noto-extra -notoseriftamilslanted-extralight.ttf fonts-noto-extra -notoseriftamilslanted-light.ttf fonts-noto-extra -notoseriftamilslanted-medium.ttf fonts-noto-extra -notoseriftamilslanted-regular.ttf fonts-noto-core -notoseriftamilslanted-semibold.ttf fonts-noto-extra -notoseriftamilslanted-semicondensed.ttf fonts-noto-extra -notoseriftamilslanted-semicondensedblack.ttf fonts-noto-extra -notoseriftamilslanted-semicondensedbold.ttf fonts-noto-extra -notoseriftamilslanted-semicondensedextrabold.ttf fonts-noto-extra -notoseriftamilslanted-semicondensedextralight.ttf fonts-noto-extra -notoseriftamilslanted-semicondensedlight.ttf fonts-noto-extra -notoseriftamilslanted-semicondensedmedium.ttf fonts-noto-extra -notoseriftamilslanted-semicondensedsemibold.ttf fonts-noto-extra -notoseriftamilslanted-semicondensedthin.ttf fonts-noto-extra -notoseriftamilslanted-thin.ttf fonts-noto-extra -notoseriftangut-regular.ttf fonts-noto-core -notoseriftelugu-black.ttf fonts-noto-extra -notoseriftelugu-bold.ttf fonts-noto-core -notoseriftelugu-extrabold.ttf fonts-noto-extra -notoseriftelugu-extralight.ttf fonts-noto-extra -notoseriftelugu-light.ttf fonts-noto-extra -notoseriftelugu-medium.ttf fonts-noto-extra -notoseriftelugu-regular.ttf fonts-noto-core -notoseriftelugu-semibold.ttf fonts-noto-extra -notoseriftelugu-thin.ttf fonts-noto-extra -notoserifthai-black.ttf fonts-noto-extra -notoserifthai-bold.ttf fonts-noto-core -notoserifthai-condensed.ttf fonts-noto-extra -notoserifthai-condensedblack.ttf fonts-noto-extra -notoserifthai-condensedbold.ttf fonts-noto-extra -notoserifthai-condensedextrabold.ttf fonts-noto-extra -notoserifthai-condensedextralight.ttf fonts-noto-extra -notoserifthai-condensedlight.ttf fonts-noto-extra -notoserifthai-condensedmedium.ttf fonts-noto-extra -notoserifthai-condensedsemibold.ttf fonts-noto-extra -notoserifthai-condensedthin.ttf fonts-noto-extra -notoserifthai-extrabold.ttf fonts-noto-extra -notoserifthai-extracondensed.ttf fonts-noto-extra -notoserifthai-extracondensedblack.ttf fonts-noto-extra -notoserifthai-extracondensedbold.ttf fonts-noto-extra -notoserifthai-extracondensedextrabold.ttf fonts-noto-extra -notoserifthai-extracondensedextralight.ttf fonts-noto-extra -notoserifthai-extracondensedlight.ttf fonts-noto-extra -notoserifthai-extracondensedmedium.ttf fonts-noto-extra -notoserifthai-extracondensedsemibold.ttf fonts-noto-extra -notoserifthai-extracondensedthin.ttf fonts-noto-extra -notoserifthai-extralight.ttf fonts-noto-extra -notoserifthai-light.ttf fonts-noto-extra -notoserifthai-medium.ttf fonts-noto-extra -notoserifthai-regular.ttf fonts-noto-core -notoserifthai-semibold.ttf fonts-noto-extra -notoserifthai-semicondensed.ttf fonts-noto-extra -notoserifthai-semicondensedblack.ttf fonts-noto-extra -notoserifthai-semicondensedbold.ttf fonts-noto-extra -notoserifthai-semicondensedextrabold.ttf fonts-noto-extra -notoserifthai-semicondensedextralight.ttf fonts-noto-extra -notoserifthai-semicondensedlight.ttf fonts-noto-extra -notoserifthai-semicondensedmedium.ttf fonts-noto-extra -notoserifthai-semicondensedsemibold.ttf fonts-noto-extra -notoserifthai-semicondensedthin.ttf fonts-noto-extra -notoserifthai-thin.ttf fonts-noto-extra -notoseriftibetan-black.ttf fonts-noto-extra -notoseriftibetan-bold.ttf fonts-noto-core -notoseriftibetan-extrabold.ttf fonts-noto-extra -notoseriftibetan-extralight.ttf fonts-noto-extra -notoseriftibetan-light.ttf fonts-noto-extra -notoseriftibetan-medium.ttf fonts-noto-extra -notoseriftibetan-regular.ttf fonts-noto-core -notoseriftibetan-semibold.ttf fonts-noto-extra -notoseriftibetan-thin.ttf fonts-noto-extra +notonaskharabic-bold.ttf fonts-noto-hinted +notonaskharabic-regular.ttf fonts-noto-hinted +notonaskharabicui-bold.ttf fonts-noto-hinted +notonaskharabicui-regular.ttf fonts-noto-hinted +notonastaliqurdu-regular.ttf fonts-noto-unhinted +notosans-bold.ttf fonts-noto-hinted +notosans-bolditalic.ttf fonts-noto-hinted +notosans-italic.ttf fonts-noto-hinted +notosans-regular.ttf fonts-noto-hinted +notosansadlam-regular.ttf fonts-noto-hinted +notosansadlamunjoined-regular.ttf fonts-noto-hinted +notosansanatolianhieroglyphs-regular.ttf fonts-noto-unhinted +notosansarabic-bold.ttf fonts-noto-hinted +notosansarabic-regular.ttf fonts-noto-hinted +notosansarabicui-bold.ttf fonts-noto-hinted +notosansarabicui-regular.ttf fonts-noto-hinted +notosansarmenian-bold.ttf fonts-noto-hinted +notosansarmenian-regular.ttf fonts-noto-hinted +notosansavestan-regular.ttf fonts-noto-hinted +notosansbalinese-regular.ttf fonts-noto-unhinted +notosansbamum-regular.ttf fonts-noto-hinted +notosansbatak-regular.ttf fonts-noto-unhinted +notosansbengali-bold.ttf fonts-noto-hinted +notosansbengali-regular.ttf fonts-noto-hinted +notosansbengaliui-bold.ttf fonts-noto-hinted +notosansbengaliui-regular.ttf fonts-noto-hinted +notosansbrahmi-regular.ttf fonts-noto-unhinted +notosansbuginese-regular.ttf fonts-noto-unhinted +notosansbuhid-regular.ttf fonts-noto-hinted +notosanscanadianaboriginal-regular.ttf fonts-noto-unhinted +notosanscarian-regular.ttf fonts-noto-hinted +notosanschakma-regular.ttf fonts-noto-hinted +notosanscham-bold.ttf fonts-noto-unhinted +notosanscham-regular.ttf fonts-noto-unhinted +notosanscherokee-bold.ttf fonts-noto-hinted +notosanscherokee-regular.ttf fonts-noto-hinted +notosanscoptic-regular.ttf fonts-noto-unhinted +notosanscuneiform-regular.ttf fonts-noto-unhinted +notosanscypriot-regular.ttf fonts-noto-hinted +notosansdeseret-regular.ttf fonts-noto-hinted +notosansdevanagari-bold.ttf fonts-noto-hinted +notosansdevanagari-regular.ttf fonts-noto-hinted +notosansdevanagariui-bold.ttf fonts-noto-hinted +notosansdevanagariui-regular.ttf fonts-noto-hinted +notosansdisplay-bold.ttf fonts-noto-hinted +notosansdisplay-bolditalic.ttf fonts-noto-hinted +notosansdisplay-italic.ttf fonts-noto-hinted +notosansdisplay-regular.ttf fonts-noto-hinted +notosansegyptianhieroglyphs-regular.ttf fonts-noto-unhinted +notosansethiopic-bold.ttf fonts-noto-hinted +notosansethiopic-regular.ttf fonts-noto-hinted +notosansgeorgian-bold.ttf fonts-noto-hinted +notosansgeorgian-regular.ttf fonts-noto-hinted +notosansglagolitic-regular.ttf fonts-noto-hinted +notosansgothic-regular.ttf fonts-noto-hinted +notosansgujarati-bold.ttf fonts-noto-hinted +notosansgujarati-regular.ttf fonts-noto-hinted +notosansgujaratiui-bold.ttf fonts-noto-hinted +notosansgujaratiui-regular.ttf fonts-noto-hinted +notosansgurmukhi-bold.ttf fonts-noto-hinted +notosansgurmukhi-regular.ttf fonts-noto-hinted +notosansgurmukhiui-bold.ttf fonts-noto-hinted +notosansgurmukhiui-regular.ttf fonts-noto-hinted +notosanshanunoo-regular.ttf fonts-noto-unhinted +notosanshebrew-bold.ttf fonts-noto-hinted +notosanshebrew-regular.ttf fonts-noto-hinted +notosansimperialaramaic-regular.ttf fonts-noto-unhinted +notosansinscriptionalpahlavi-regular.ttf fonts-noto-unhinted +notosansinscriptionalparthian-regular.ttf fonts-noto-unhinted +notosansjavanese-regular.ttf fonts-noto-unhinted +notosanskaithi-regular.ttf fonts-noto-unhinted +notosanskannada-bold.ttf fonts-noto-hinted +notosanskannada-regular.ttf fonts-noto-hinted +notosanskannadaui-bold.ttf fonts-noto-hinted +notosanskannadaui-regular.ttf fonts-noto-hinted +notosanskayahli-regular.ttf fonts-noto-hinted +notosanskharoshthi-regular.ttf fonts-noto-unhinted +notosanskhmer-bold.ttf fonts-noto-hinted +notosanskhmer-regular.ttf fonts-noto-hinted +notosanskhmerui-bold.ttf fonts-noto-hinted +notosanskhmerui-regular.ttf fonts-noto-hinted +notosanslao-bold.ttf fonts-noto-hinted +notosanslao-regular.ttf fonts-noto-hinted +notosanslaoui-bold.ttf fonts-noto-hinted +notosanslaoui-regular.ttf fonts-noto-hinted +notosanslepcha-regular.ttf fonts-noto-unhinted +notosanslimbu-regular.ttf fonts-noto-unhinted +notosanslinearb-regular.ttf fonts-noto-unhinted +notosanslisu-regular.ttf fonts-noto-hinted +notosanslycian-regular.ttf fonts-noto-unhinted +notosanslydian-regular.ttf fonts-noto-unhinted +notosansmalayalam-bold.ttf fonts-noto-hinted +notosansmalayalam-regular.ttf fonts-noto-hinted +notosansmalayalamui-bold.ttf fonts-noto-hinted +notosansmalayalamui-regular.ttf fonts-noto-hinted +notosansmandaic-regular.ttf fonts-noto-hinted +notosansmeeteimayek-regular.ttf fonts-noto-unhinted +notosansmongolian-regular.ttf fonts-noto-unhinted +notosansmono-bold.ttf fonts-noto-hinted +notosansmono-regular.ttf fonts-noto-hinted +notosansmyanmar-bold.ttf fonts-noto-hinted +notosansmyanmar-regular.ttf fonts-noto-hinted +notosansmyanmarui-bold.ttf fonts-noto-hinted +notosansmyanmarui-regular.ttf fonts-noto-hinted +notosansnewtailue-regular.ttf fonts-noto-unhinted +notosansnko-regular.ttf fonts-noto-hinted +notosansogham-regular.ttf fonts-noto-unhinted +notosansolchiki-regular.ttf fonts-noto-hinted +notosansolditalic-regular.ttf fonts-noto-unhinted +notosansoldpersian-regular.ttf fonts-noto-unhinted +notosansoldsoutharabian-regular.ttf fonts-noto-unhinted +notosansoldturkic-regular.ttf fonts-noto-hinted +notosansoriya-bold.ttf fonts-noto-hinted +notosansoriya-regular.ttf fonts-noto-hinted +notosansoriyaui-bold.ttf fonts-noto-hinted +notosansoriyaui-regular.ttf fonts-noto-hinted +notosansosage-regular.ttf fonts-noto-hinted +notosansosmanya-regular.ttf fonts-noto-hinted +notosansphagspa-regular.ttf fonts-noto-unhinted +notosansphoenician-regular.ttf fonts-noto-unhinted +notosansrejang-regular.ttf fonts-noto-unhinted +notosansrunic-regular.ttf fonts-noto-unhinted +notosanssamaritan-regular.ttf fonts-noto-unhinted +notosanssaurashtra-regular.ttf fonts-noto-unhinted +notosansshavian-regular.ttf fonts-noto-hinted +notosanssinhala-bold.ttf fonts-noto-hinted +notosanssinhala-regular.ttf fonts-noto-hinted +notosanssinhalaui-bold.ttf fonts-noto-hinted +notosanssinhalaui-regular.ttf fonts-noto-hinted +notosanssundanese-regular.ttf fonts-noto-unhinted +notosanssylotinagri-regular.ttf fonts-noto-unhinted +notosanssymbols-bold.ttf fonts-noto-hinted +notosanssymbols-regular.ttf fonts-noto-hinted +notosanssymbols2-regular.ttf fonts-noto-unhinted +notosanssyriaceastern-regular.ttf fonts-noto-unhinted +notosanssyriacestrangela-regular.ttf fonts-noto-unhinted +notosanssyriacwestern-regular.ttf fonts-noto-unhinted +notosanstagalog-regular.ttf fonts-noto-unhinted +notosanstagbanwa-regular.ttf fonts-noto-unhinted +notosanstaile-regular.ttf fonts-noto-unhinted +notosanstaitham-regular.ttf fonts-noto-unhinted +notosanstaiviet-regular.ttf fonts-noto-unhinted +notosanstamil-bold.ttf fonts-noto-hinted +notosanstamil-regular.ttf fonts-noto-hinted +notosanstamilui-bold.ttf fonts-noto-hinted +notosanstamilui-regular.ttf fonts-noto-hinted +notosanstelugu-bold.ttf fonts-noto-hinted +notosanstelugu-regular.ttf fonts-noto-hinted +notosansteluguui-bold.ttf fonts-noto-hinted +notosansteluguui-regular.ttf fonts-noto-hinted +notosansthaana-bold.ttf fonts-noto-hinted +notosansthaana-regular.ttf fonts-noto-hinted +notosansthai-bold.ttf fonts-noto-hinted +notosansthai-regular.ttf fonts-noto-hinted +notosansthaiui-bold.ttf fonts-noto-hinted +notosansthaiui-regular.ttf fonts-noto-hinted +notosanstibetan-bold.ttf fonts-noto-hinted +notosanstibetan-regular.ttf fonts-noto-hinted +notosanstifinagh-regular.ttf fonts-noto-hinted +notosansugaritic-regular.ttf fonts-noto-unhinted +notosansvai-regular.ttf fonts-noto-hinted +notosansyi-regular.ttf fonts-noto-unhinted +notoserif-bold.ttf fonts-noto-hinted +notoserif-bolditalic.ttf fonts-noto-hinted +notoserif-italic.ttf fonts-noto-hinted +notoserif-regular.ttf fonts-noto-hinted +notoserifarmenian-bold.ttf fonts-noto-hinted +notoserifarmenian-regular.ttf fonts-noto-hinted +notoserifbengali-bold.ttf fonts-noto-hinted +notoserifbengali-regular.ttf fonts-noto-hinted +notoserifdevanagari-bold.ttf fonts-noto-hinted +notoserifdevanagari-regular.ttf fonts-noto-hinted +notoserifdisplay-bold.ttf fonts-noto-hinted +notoserifdisplay-bolditalic.ttf fonts-noto-hinted +notoserifdisplay-italic.ttf fonts-noto-hinted +notoserifdisplay-regular.ttf fonts-noto-hinted +notoserifethiopic-bold.ttf fonts-noto-hinted +notoserifethiopic-regular.ttf fonts-noto-hinted +notoserifgeorgian-bold.ttf fonts-noto-hinted +notoserifgeorgian-regular.ttf fonts-noto-hinted +notoserifgujarati-bold.ttf fonts-noto-hinted +notoserifgujarati-regular.ttf fonts-noto-hinted +notoserifhebrew-bold.ttf fonts-noto-hinted +notoserifhebrew-regular.ttf fonts-noto-hinted +notoserifkannada-bold.ttf fonts-noto-hinted +notoserifkannada-regular.ttf fonts-noto-hinted +notoserifkhmer-bold.ttf fonts-noto-hinted +notoserifkhmer-regular.ttf fonts-noto-hinted +notoseriflao-bold.ttf fonts-noto-hinted +notoseriflao-regular.ttf fonts-noto-hinted +notoserifmalayalam-bold.ttf fonts-noto-hinted +notoserifmalayalam-regular.ttf fonts-noto-hinted +notoserifmyanmar-bold.ttf fonts-noto-hinted +notoserifmyanmar-regular.ttf fonts-noto-hinted +notoserifsinhala-bold.ttf fonts-noto-hinted +notoserifsinhala-regular.ttf fonts-noto-hinted +notoseriftamil-bold.ttf fonts-noto-hinted +notoseriftamil-regular.ttf fonts-noto-hinted +notoseriftelugu-bold.ttf fonts-noto-hinted +notoseriftelugu-regular.ttf fonts-noto-hinted +notoserifthai-bold.ttf fonts-noto-hinted +notoserifthai-regular.ttf fonts-noto-hinted notqr.ttf ttf-aenigma nsecthck.ttf ttf-aenigma nsecthin.ttf ttf-aenigma @@ -3834,10 +1774,7 @@ octicons.ttf fonts-octicons offkiltl.ttf ttf-aenigma offkiltr.ttf ttf-aenigma -okolaksbold.ttf fonts-okolaks -okolaksbolditalic.ttf fonts-okolaks -okolaksregular.ttf fonts-okolaks -okolaksregularitalic.ttf fonts-okolaks +okolaks_gbold.ttf fonts-okolaks oldaniaadfstd-bold.otf fonts-adf-oldania oldaniaadfstd-bolditalic.otf fonts-adf-oldania oldaniaadfstd-italic.otf fonts-adf-oldania @@ -3872,17 +1809,12 @@ opiated.ttf ttf-aenigma oradanogsrr.ttf fonts-oradano-mincho-gsrr orbicula.ttf ttf-aenigma -osifont.ttf fonts-osifont osp-din.ttf fonts-opendin outersid.ttf ttf-aenigma overhead.ttf ttf-aenigma oxygen-sans-bold.ttf fonts-oxygen oxygen-sans.ttf fonts-oxygen oxygenmono-regular.ttf fonts-oxygen -p052-bold.otf fonts-urw-base35 -p052-bolditalic.otf fonts-urw-base35 -p052-italic.otf fonts-urw-base35 -p052-roman.otf fonts-urw-base35 p052003d.pfb t1-cyrillic p052004d.pfb t1-cyrillic p052023d.pfb t1-cyrillic @@ -3896,7 +1828,6 @@ pallu___.ttf fonts-uralic pallub__.ttf fonts-uralic pallui__.ttf fonts-uralic -parix-hybrid111r.otf fonts-gotico-antiqua patchsans.otf fonts-ldco patchsans.ttf fonts-ldco patchserif.otf fonts-ldco @@ -3927,30 +1858,12 @@ pneuwide.ttf ttf-aenigma ponnala.ttf fonts-teluguvijayam pothana2000.ttf fonts-telu-extra -povlogo.ttf fonts-povray powdwrk5.ttf ttf-aenigma powerlinesymbols.otf fonts-powerline prociono.otf fonts-prociono +procionott.ttf fonts-prociono progenisis.ttf fonts-dustin -proggytiny.ttf fonts-proggy pseudo.ttf ttf-aenigma -ptc55f.ttf fonts-paratype -ptc75f.ttf fonts-paratype -ptf55f.ttf fonts-paratype -ptf56f.ttf fonts-paratype -ptf75f.ttf fonts-paratype -ptf76f.ttf fonts-paratype -ptm55f.ttf fonts-paratype -ptm75f.ttf fonts-paratype -ptn57f.ttf fonts-paratype -ptn77f.ttf fonts-paratype -ptolemy-greatprimer18.otf fonts-gotico-antiqua -pts55f.ttf fonts-paratype -pts56f.ttf fonts-paratype -pts75f.ttf fonts-paratype -pts76f.ttf fonts-paratype -ptz55f.ttf fonts-paratype -ptz56f.ttf fonts-paratype purisa-bold.otf fonts-tlwg-purisa-otf purisa-bold.ttf fonts-tlwg-purisa-ttf purisa-boldoblique.otf fonts-tlwg-purisa-otf @@ -3959,87 +1872,6 @@ purisa-oblique.ttf fonts-tlwg-purisa-ttf purisa.otf fonts-tlwg-purisa-otf purisa.ttf fonts-tlwg-purisa-ttf -px_ami_bios-2y.ttf fonts-pc-extra -px_ami_bios.ttf fonts-pc-extra -px_amstradpc1512-2y.ttf fonts-pc -px_amstradpc1512.ttf fonts-pc-extra -px_ati_8x14.ttf fonts-pc-extra -px_ati_8x16.ttf fonts-pc-extra -px_ati_8x8-2y.ttf fonts-pc-extra -px_ati_8x8.ttf fonts-pc-extra -px_ati_9x14.ttf fonts-pc-extra -px_ati_9x16.ttf fonts-pc-extra -px_ati_smallw_6x8.ttf fonts-pc-extra -px_att_pc6300-2x.ttf fonts-pc-extra -px_att_pc6300.ttf fonts-pc-extra -px_compaqthin_8x14.ttf fonts-pc-extra -px_compaqthin_8x16.ttf fonts-pc-extra -px_compaqthin_8x8.ttf fonts-pc-extra -px_dtk_bios-2y.ttf fonts-pc-extra -px_dtk_bios.ttf fonts-pc-extra -px_ibm_3270pc.ttf fonts-pc-extra -px_ibm_bios-2x.ttf fonts-pc-extra -px_ibm_bios-2y.ttf fonts-pc-extra -px_ibm_bios.ttf fonts-pc-extra -px_ibm_cga-2y.ttf fonts-pc -px_ibm_cga.ttf fonts-pc -px_ibm_cgathin-2y.ttf fonts-pc-extra -px_ibm_cgathin.ttf fonts-pc-extra -px_ibm_conv-2x.ttf fonts-pc-extra -px_ibm_conv-2y.ttf fonts-pc-extra -px_ibm_conv.ttf fonts-pc-extra -px_ibm_ega8-2x.ttf fonts-pc-extra -px_ibm_ega8.ttf fonts-pc -px_ibm_ega9-2x.ttf fonts-pc-extra -px_ibm_ega9.ttf fonts-pc-extra -px_ibm_iso8.ttf fonts-pc-extra -px_ibm_iso9.ttf fonts-pc-extra -px_ibm_mda.ttf fonts-pc -px_ibm_pgc-2x.ttf fonts-pc-extra -px_ibm_pgc.ttf fonts-pc-extra -px_ibm_ps2thin1.ttf fonts-pc-extra -px_ibm_ps2thin2.ttf fonts-pc-extra -px_ibm_ps2thin3.ttf fonts-pc-extra -px_ibm_ps2thin4.ttf fonts-pc-extra -px_ibm_vga8-2x.ttf fonts-pc-extra -px_ibm_vga8.ttf fonts-pc -px_ibm_vga9-2x.ttf fonts-pc-extra -px_ibm_vga9.ttf fonts-pc -px_itt_bios-2y.ttf fonts-pc-extra -px_itt_bios.ttf fonts-pc-extra -px_kaypro2k-2y.ttf fonts-pc-extra -px_kaypro2k.ttf fonts-pc-extra -px_phoenix_bios-2y.ttf fonts-pc-extra -px_phoenix_bios.ttf fonts-pc-extra -px_phoenixega_8x14.ttf fonts-pc-extra -px_phoenixega_8x16.ttf fonts-pc-extra -px_phoenixega_8x8-2y.ttf fonts-pc-extra -px_phoenixega_8x8.ttf fonts-pc-extra -px_phoenixega_9x14.ttf fonts-pc-extra -px_tandynew_225-2y.ttf fonts-pc-extra -px_tandynew_225.ttf fonts-pc-extra -px_tandynew_mono.ttf fonts-pc-extra -px_tandynew_tv-2y.ttf fonts-pc-extra -px_tandynew_tv.ttf fonts-pc-extra -px_tandyold_225-2y.ttf fonts-pc-extra -px_tandyold_225.ttf fonts-pc-extra -px_tandyold_tv-2y.ttf fonts-pc-extra -px_tandyold_tv.ttf fonts-pc-extra -px_toshibalcd_8x16.ttf fonts-pc-extra -px_toshibalcd_8x8.ttf fonts-pc-extra -px_verite_8x14.ttf fonts-pc-extra -px_verite_8x16.ttf fonts-pc-extra -px_verite_8x8-2y.ttf fonts-pc-extra -px_verite_8x8.ttf fonts-pc-extra -px_verite_9x14.ttf fonts-pc-extra -px_verite_9x16.ttf fonts-pc-extra -px_vga_squarepx.ttf fonts-pc -px_vtech_bios-2y.ttf fonts-pc-extra -px_vtech_bios.ttf fonts-pc-extra -px_wyse700a-2y.ttf fonts-pc-extra -px_wyse700a.ttf fonts-pc-extra -px_wyse700b-2y.ttf fonts-pc-extra -px_wyse700b.ttf fonts-pc-extra qbicle1.ttf ttf-aenigma qbicle2.ttf ttf-aenigma qbicle3.ttf ttf-aenigma @@ -4065,10 +1897,6 @@ quercus_bold.ttf fonts-linex quercus_bold_it.ttf fonts-linex quercus_it.ttf fonts-linex -quicksand-bold.ttf fonts-quicksand -quicksand-light.ttf fonts-quicksand -quicksand-medium.ttf fonts-quicksand -quicksand-regular.ttf fonts-quicksand quillexo.ttf ttf-aenigma quillexs.ttf ttf-aenigma rachana-bold.ttf fonts-smc-rachana @@ -4098,14 +1926,6 @@ relapse.ttf ttf-aenigma revert.ttf ttf-aenigma revertro.ttf ttf-aenigma -rg2014b.ttf fonts-roadgeek -rg2014c.ttf fonts-roadgeek -rg2014d.ttf fonts-roadgeek -rg2014e.ttf fonts-roadgeek -rg2014eem.ttf fonts-roadgeek -rg2014em.ttf fonts-roadgeek -rg2014f.ttf fonts-roadgeek -richstyle.ttf fonts-cegui rictydiminished-bold.ttf fonts-ricty-diminished rictydiminished-boldoblique.ttf fonts-ricty-diminished rictydiminished-oblique.ttf fonts-ricty-diminished @@ -4114,7 +1934,6 @@ rictydiminisheddiscord-boldoblique.ttf fonts-ricty-diminished rictydiminisheddiscord-oblique.ttf fonts-ricty-diminished rictydiminisheddiscord-regular.ttf fonts-ricty-diminished -rit-sundar.ttf fonts-rit-sundar roboto-black.ttf fonts-roboto-fontface roboto-black.ttf fonts-roboto-hinted roboto-black.ttf fonts-roboto-unhinted @@ -4167,20 +1986,12 @@ robotocondensed-light.ttf fonts-roboto-unhinted robotocondensed-lightitalic.ttf fonts-roboto-hinted robotocondensed-lightitalic.ttf fonts-roboto-unhinted -robotocondensed-medium.ttf fonts-roboto-hinted -robotocondensed-medium.ttf fonts-roboto-unhinted -robotocondensed-mediumitalic.ttf fonts-roboto-hinted -robotocondensed-mediumitalic.ttf fonts-roboto-unhinted robotocondensed-regular.ttf fonts-roboto-hinted robotocondensed-regular.ttf fonts-roboto-unhinted -robotoslab-bold.otf fonts-roboto-slab -robotoslab-light.otf fonts-roboto-slab -robotoslab-regular.otf fonts-roboto-slab -robotoslab-thin.otf fonts-roboto-slab -romandeadfno2std-demibold.otf fonts-adf-romande -romandeadfno2std-demibolditalic.otf fonts-adf-romande -romandeadfno2std-italic.otf fonts-adf-romande -romandeadfno2std-regular.otf fonts-adf-romande +robotoslab-bold.ttf fonts-roboto-slab +robotoslab-light.ttf fonts-roboto-slab +robotoslab-regular.ttf fonts-roboto-slab +robotoslab-thin.ttf fonts-roboto-slab romandeadfscriptstd-italic.otf fonts-adf-romande romandeadfstd-demibold.otf fonts-adf-romande romandeadfstd-demibolditalic.otf fonts-adf-romande @@ -4191,25 +2002,14 @@ romau___.ttf fonts-uralic romaub__.ttf fonts-uralic romaui__.ttf fonts-uralic -rot-protoroman102r.otf fonts-gotico-antiqua rotund.ttf ttf-aenigma rotundo.ttf ttf-aenigma roughday.ttf ttf-aenigma rsfs10.ttf fonts-lyx rufscript010.ttf fonts-rufscript -rusch-goticoantiqua100g.otf fonts-gotico-antiqua -rusch-r-bizarre-protoroman103r.otf fonts-gotico-antiqua ryuker.ttf ttf-aenigma saab.ttf fonts-guru-extra sahadeva.ttf fonts-sahadeva -salaowu-bold.ttf fonts-sil-shimenkan-salaowu -salaowu-regular.ttf fonts-sil-shimenkan-salaowu -salaowubook-bold.ttf fonts-sil-shimenkan-salaowu -salaowubook-regular.ttf fonts-sil-shimenkan-salaowu -salaowuextralight-bold.ttf fonts-sil-shimenkan-salaowu -salaowuextralight-regular.ttf fonts-sil-shimenkan-salaowu -salaowulight-bold.ttf fonts-sil-shimenkan-salaowu -salaowulight-regular.ttf fonts-sil-shimenkan-salaowu samanata.ttf fonts-deva-extra samyak-devanagari.ttf fonts-samyak-deva samyak-gujarati.ttf fonts-samyak-gujr @@ -4222,14 +2022,6 @@ sansub__.ttf fonts-uralic sansubi_.ttf fonts-uralic sansui__.ttf fonts-uralic -sapushan-bold.ttf fonts-sil-shimenkan-sapushan -sapushan-regular.ttf fonts-sil-shimenkan-sapushan -sapushanbook-bold.ttf fonts-sil-shimenkan-sapushan -sapushanbook-regular.ttf fonts-sil-shimenkan-sapushan -sapushanextralight-bold.ttf fonts-sil-shimenkan-sapushan -sapushanextralight-regular.ttf fonts-sil-shimenkan-sapushan -sapushanlight-bold.ttf fonts-sil-shimenkan-sapushan -sapushanlight-regular.ttf fonts-sil-shimenkan-sapushan sarai.ttf fonts-sarai sarcasti.ttf ttf-aenigma saunder.ttf ttf-aenigma @@ -4256,52 +2048,6 @@ setbackt.ttf ttf-aenigma setofont-ex.ttf fonts-seto setofont.ttf fonts-seto -shimenkan-bold.ttf fonts-sil-shimenkan -shimenkan-regular.ttf fonts-sil-shimenkan -shimenkanbook-bold.ttf fonts-sil-shimenkan -shimenkanbook-regular.ttf fonts-sil-shimenkan -shimenkanextralight-bold.ttf fonts-sil-shimenkan -shimenkanextralight-regular.ttf fonts-sil-shimenkan -shimenkangsm-bold.ttf fonts-sil-shimenkan-gsm -shimenkangsm-regular.ttf fonts-sil-shimenkan-gsm -shimenkangsmbook-bold.ttf fonts-sil-shimenkan-gsm -shimenkangsmbook-regular.ttf fonts-sil-shimenkan-gsm -shimenkangsmextralight-bold.ttf fonts-sil-shimenkan-gsm -shimenkangsmextralight-regular.ttf fonts-sil-shimenkan-gsm -shimenkangsmlight-bold.ttf fonts-sil-shimenkan-gsm -shimenkangsmlight-regular.ttf fonts-sil-shimenkan-gsm -shimenkanguifan-bold.ttf fonts-sil-shimenkan-guifan -shimenkanguifan-regular.ttf fonts-sil-shimenkan-guifan -shimenkanguifanbook-bold.ttf fonts-sil-shimenkan-guifan -shimenkanguifanbook-regular.ttf fonts-sil-shimenkan-guifan -shimenkanguifanextralight-bold.ttf fonts-sil-shimenkan-guifan -shimenkanguifanextralight-regular.ttf fonts-sil-shimenkan-guifan -shimenkanguifanlight-bold.ttf fonts-sil-shimenkan-guifan -shimenkanguifanlight-regular.ttf fonts-sil-shimenkan-guifan -shimenkanmas-bold.ttf fonts-sil-shimenkan-mas -shimenkanmas-regular.ttf fonts-sil-shimenkan-mas -shimenkanmasbook-bold.ttf fonts-sil-shimenkan-mas -shimenkanmasbook-regular.ttf fonts-sil-shimenkan-mas -shimenkanmasextralight-bold.ttf fonts-sil-shimenkan-mas -shimenkanmasextralight-regular.ttf fonts-sil-shimenkan-mas -shimenkanmaslight-bold.ttf fonts-sil-shimenkan-mas -shimenkanmaslight-regular.ttf fonts-sil-shimenkan-mas -shimenkanmgs-bold.ttf fonts-sil-shimenkan-mgs -shimenkanmgs-regular.ttf fonts-sil-shimenkan-mgs -shimenkanmgsbook-bold.ttf fonts-sil-shimenkan-mgs -shimenkanmgsbook-regular.ttf fonts-sil-shimenkan-mgs -shimenkanmgsextralight-bold.ttf fonts-sil-shimenkan-mgs -shimenkanmgsextralight-regular.ttf fonts-sil-shimenkan-mgs -shimenkanmgslight-bold.ttf fonts-sil-shimenkan-mgs -shimenkanmgslight-regular.ttf fonts-sil-shimenkan-mgs -shimenkanzonghe-bold.ttf fonts-sil-shimenkan-zonghe -shimenkanzonghe-regular.ttf fonts-sil-shimenkan-zonghe -shimenkanzonghebook-bold.ttf fonts-sil-shimenkan-zonghe -shimenkanzonghebook-regular.ttf fonts-sil-shimenkan-zonghe -shimenkanzongheextralight-bold.ttf fonts-sil-shimenkan-zonghe -shimenkanzongheextralight-regular.ttf fonts-sil-shimenkan-zonghe -shimenkanzonghelight-bold.ttf fonts-sil-shimenkan-zonghe -shimenkanzonghelight-regular.ttf fonts-sil-shimenkan-zonghe sideways.ttf ttf-aenigma sileot.ttf fonts-sil-ezra sileotsr.ttf fonts-sil-ezra @@ -4318,31 +2064,16 @@ snbi.ttf fonts-sil-sophia-nubian sni.ttf fonts-sil-sophia-nubian snr.ttf fonts-sil-sophia-nubian -solidemirageetroit.otf fonts-solide-mirage -solidemiragemono.otf fonts-solide-mirage -solothurn-bold.otf fonts-adf-solothurn -solothurn-boldoblique.otf fonts-adf-solothurn -solothurn-medium.otf fonts-adf-solothurn -solothurn-mediumoblique.otf fonts-adf-solothurn -solothurn-oblique.otf fonts-adf-solothurn -solothurn-regular.otf fonts-adf-solothurn -souffletvert-hybrid106r.otf fonts-gotico-antiqua spaciouo.ttf ttf-aenigma spacious.ttf ttf-aenigma spastic2.ttf ttf-aenigma spheroid.ttf ttf-aenigma spheroix.ttf ttf-aenigma -spira-protoroman110r.otf fonts-gotico-antiqua splatz2.ttf ttf-aenigma -spleen-12x24.otf fonts-spleen -spleen-16x32.otf fonts-spleen -spleen-32x64.otf fonts-spleen -spleen-8x16.otf fonts-spleen sqroute.ttf ttf-aenigma stagnati.ttf ttf-aenigma -standardsymbolsps.otf fonts-urw-base35 -staypuft.ttf fonts-staypuft -stevehand.ttf fonts-sjfonts +staypuft.ttf ttf-staypuft +stevehand.ttf ttf-sjfonts sticks.otf fonts-ldco sticks.ttf fonts-ldco stix-bold.otf fonts-stix @@ -4438,7 +2169,7 @@ strande2.ttf ttf-aenigma strokes.otf fonts-ldco strokes.ttf fonts-ldco -summersby.ttf fonts-summersby +summersby.ttf ttf-summersby supragc.ttf ttf-aenigma supragl.ttf ttf-aenigma suruma.ttf fonts-smc-suruma @@ -4468,6 +2199,26 @@ switzeraadf-medium.otf fonts-adf-switzera switzeraadf-mediumitalic.otf fonts-adf-switzera switzeraadf-regular.otf fonts-adf-switzera +switzeraadfbold-italic.otf ttf-adf-switzera +switzeraadfbold.otf ttf-adf-switzera +switzeraadfcd-bold.otf ttf-adf-switzera +switzeraadfcd-bolditalic.otf ttf-adf-switzera +switzeraadfcd-italic.otf ttf-adf-switzera +switzeraadfcd-regular.otf ttf-adf-switzera +switzeraadfex-bold.otf ttf-adf-switzera +switzeraadfex-bolditalic.otf ttf-adf-switzera +switzeraadfex-italic.otf ttf-adf-switzera +switzeraadfex-regular.otf ttf-adf-switzera +switzeraadfextrabold-italic.otf ttf-adf-switzera +switzeraadfextrabold.otf ttf-adf-switzera +switzeraadflight-bold.otf ttf-adf-switzera +switzeraadflight-bolditalic.otf ttf-adf-switzera +switzeraadflight-italic.otf ttf-adf-switzera +switzeraadflight-regular.otf ttf-adf-switzera +switzeraadflightcd-bold.otf ttf-adf-switzera +switzeraadflightcd-bolditalic.otf ttf-adf-switzera +switzeraadflightcd-italic.otf ttf-adf-switzera +switzeraadflightcd-regular.otf ttf-adf-switzera symbol.ttf fonts-wine symbola_hint.ttf fonts-symbola symmetry.ttf ttf-aenigma @@ -4475,8 +2226,6 @@ syntheti.ttf ttf-aenigma syracuse.ttf ttf-aenigma tagbanwa.ttf ttf-tagbanwa -tagmukay-bold.ttf fonts-sil-tagmukay -tagmukay-regular.ttf fonts-sil-tagmukay tahoma.ttf fonts-wine tahomabd.ttf fonts-wine taiheritagepro-bold.ttf fonts-sil-taiheritagepro @@ -4488,14 +2237,6 @@ tamu_kadampari.ttf fonts-taml-tamu tamu_kalyani.ttf fonts-taml-tamu tamu_maduram.ttf fonts-taml-tamu -taogu-bold.ttf fonts-sil-shimenkan-taogu -taogu-regular.ttf fonts-sil-shimenkan-taogu -taogubook-bold.ttf fonts-sil-shimenkan-taogu -taogubook-regular.ttf fonts-sil-shimenkan-taogu -taoguextralight-bold.ttf fonts-sil-shimenkan-taogu -taoguextralight-regular.ttf fonts-sil-shimenkan-taogu -taogulight-bold.ttf fonts-sil-shimenkan-taogu -taogulight-regular.ttf fonts-sil-shimenkan-taogu teams.pfb t1-teams teamsb.pfb t1-teams teamsbi.pfb t1-teams @@ -4551,7 +2292,6 @@ thwart.ttf ttf-aenigma tibetanmachineuni.ttf fonts-tibetan-machine tibetansambhotayigchung.ttf fonts-sambhota-yigchung -timrom.ttf fonts-povray tinos-bold.ttf fonts-croscore tinos-bolditalic.ttf fonts-croscore tinos-italic.ttf fonts-croscore @@ -4666,10 +2406,17 @@ tlwgtypo-oblique.ttf fonts-tlwg-typo-ttf tlwgtypo.otf fonts-tlwg-typo-otf tlwgtypo.ttf fonts-tlwg-typo-ttf -tnua-libre.ttf fonts-cegui tomsontalks.ttf fonts-tomsontalks tonik.ttf ttf-aenigma tragic2.ttf ttf-aenigma +tribunadfmedcdstd-bold.otf ttf-adf-tribun +tribunadfmedcdstd-bolditalic.otf ttf-adf-tribun +tribunadfmedcdstd-italic.otf ttf-adf-tribun +tribunadfmedcdstd-regular.otf ttf-adf-tribun +tribunadfmedstd-bold.otf ttf-adf-tribun +tribunadfmedstd-bolditalic.otf ttf-adf-tribun +tribunadfmedstd-italic.otf ttf-adf-tribun +tribunadfmedstd-regular.otf ttf-adf-tribun tribunadfstd-bold.otf fonts-adf-tribun tribunadfstd-boldcond.otf fonts-adf-tribun tribunadfstd-boldconditalic.otf fonts-adf-tribun @@ -4682,7 +2429,6 @@ tribunadfstd-medium.otf fonts-adf-tribun tribunadfstd-mediumitalic.otf fonts-adf-tribun tribunadfstd-regular.otf fonts-adf-tribun -triodpostnaja.ttf fonts-triod-postnaja tscu_comic.ttf fonts-taml-tscu tscu_paranar.ttf fonts-taml-tscu tscu_paranarb.ttf fonts-taml-tscu @@ -4817,8 +2563,6 @@ ume-tms3.ttf fonts-horai-umefont ume-ugo4.ttf fonts-horai-umefont ume-ugo5.ttf fonts-horai-umefont -umeplus-cl-gothic.ttf fonts-umeplus-cl -umeplus-clp-gothic.ttf fonts-umeplus-cl umeplus-gothic.ttf fonts-umeplus umeplus-p-gothic.ttf fonts-umeplus umpush-bold.otf fonts-tlwg-umpush-otf @@ -4850,20 +2594,23 @@ ungraphicbold.ttf fonts-unfonts-core ungungseo.ttf fonts-unfonts-core unidings_hint.ttf fonts-ancient-scripts -unifont.ttf fonts-unifont -unifont_csur.ttf fonts-unifont -unifont_sample.ttf fonts-unifont -unifont_upper.ttf fonts-unifont -unifur.ttf fonts-eurofurence +unifont.ttf ttf-unifont +unifont_csur.ttf ttf-unifont +unifont_sample.ttf ttf-unifont +unifont_upper.ttf ttf-unifont unikuweb.ttf fonts-unikurdweb united.ttf ttf-aenigma +universalisadfcdstd-bdoblique.otf ttf-adf-universalis +universalisadfcdstd-bold.otf ttf-adf-universalis +universalisadfcdstd-oblique.otf ttf-adf-universalis +universalisadfcdstd-regular.otf ttf-adf-universalis universalisadfstd-bold.otf fonts-adf-universalis universalisadfstd-boldcond.otf fonts-adf-universalis -universalisadfstd-boldcondit.otf fonts-adf-universalis -universalisadfstd-bolditalic.otf fonts-adf-universalis +universalisadfstd-boldcondobl.otf fonts-adf-universalis +universalisadfstd-boldoblique.otf fonts-adf-universalis universalisadfstd-cond.otf fonts-adf-universalis -universalisadfstd-conditalic.otf fonts-adf-universalis -universalisadfstd-italic.otf fonts-adf-universalis +universalisadfstd-condoblique.otf fonts-adf-universalis +universalisadfstd-oblique.otf fonts-adf-universalis universalisadfstd-regular.otf fonts-adf-universalis unjamobatang.ttf fonts-unfonts-extra unjamodotum.ttf fonts-unfonts-extra @@ -4889,15 +2636,7 @@ upraise.ttf ttf-aenigma urcompi.ttf ttf-aenigma urcompo.ttf ttf-aenigma -uroob-regular.ttf fonts-smc-uroob -urwbookman-demi.otf fonts-urw-base35 -urwbookman-demiitalic.otf fonts-urw-base35 -urwbookman-light.otf fonts-urw-base35 -urwbookman-lightitalic.otf fonts-urw-base35 -urwgothic-book.otf fonts-urw-base35 -urwgothic-bookoblique.otf fonts-urw-base35 -urwgothic-demi.otf fonts-urw-base35 -urwgothic-demioblique.otf fonts-urw-base35 +uroob.ttf fonts-smc-uroob utkal.ttf fonts-orya-extra vacantz.ttf ttf-aenigma vanished.ttf ttf-aenigma @@ -4946,11 +2685,7 @@ vollkorn-blackitalic.ttf fonts-vollkorn vollkorn-bold.ttf fonts-vollkorn vollkorn-bolditalic.ttf fonts-vollkorn -vollkorn-extrabold.ttf fonts-vollkorn -vollkorn-extrabolditalic.ttf fonts-vollkorn vollkorn-italic.ttf fonts-vollkorn -vollkorn-medium.ttf fonts-vollkorn -vollkorn-mediumitalic.ttf fonts-vollkorn vollkorn-regular.ttf fonts-vollkorn vollkorn-semibold.ttf fonts-vollkorn vollkorn-semibolditalic.ttf fonts-vollkorn @@ -5023,138 +2758,13 @@ yonder.ttf ttf-aenigma yoshisst.ttf ttf-aenigma yourcomp.ttf ttf-aenigma -yozba_.ttf fonts-yozvox-yozfont-antique -yozba_90.ttf fonts-yozvox-yozfont-antique -yozba_90i.ttf fonts-yozvox-yozfont-antique -yozba_i.ttf fonts-yozvox-yozfont-antique -yozbaf.ttf fonts-yozvox-yozfont-antique -yozbaf90.ttf fonts-yozvox-yozfont-antique -yozbaf90i.ttf fonts-yozvox-yozfont-antique -yozbafi.ttf fonts-yozvox-yozfont-antique -yozbap.ttf fonts-yozvox-yozfont-antique -yozbap90.ttf fonts-yozvox-yozfont-antique -yozbc_.ttf fonts-yozvox-yozfont-cute -yozbc_90.ttf fonts-yozvox-yozfont-cute -yozbc_90i.ttf fonts-yozvox-yozfont-cute -yozbc_i.ttf fonts-yozvox-yozfont-cute -yozbcf.ttf fonts-yozvox-yozfont-cute -yozbcf90.ttf fonts-yozvox-yozfont-cute -yozbcf90i.ttf fonts-yozvox-yozfont-cute -yozbcfi.ttf fonts-yozvox-yozfont-cute -yozbe_.ttf fonts-yozvox-yozfont-edu -yozbe_90.ttf fonts-yozvox-yozfont-edu -yozbe_90i.ttf fonts-yozvox-yozfont-edu -yozbe_i.ttf fonts-yozvox-yozfont-edu -yozbe_m.ttf fonts-yozvox-yozfont-edu -yozbe_m90.ttf fonts-yozvox-yozfont-edu -yozbef.ttf fonts-yozvox-yozfont-edu -yozbef90.ttf fonts-yozvox-yozfont-edu -yozbef90i.ttf fonts-yozvox-yozfont-edu -yozbefi.ttf fonts-yozvox-yozfont-edu -yozbefm.ttf fonts-yozvox-yozfont-edu -yozbefm90.ttf fonts-yozvox-yozfont-edu -yozbn_.ttf fonts-yozvox-yozfont-new-kana -yozbn_90.ttf fonts-yozvox-yozfont-new-kana -yozbn_90i.ttf fonts-yozvox-yozfont-new-kana -yozbn_i.ttf fonts-yozvox-yozfont-new-kana -yozbn_m.ttf fonts-yozvox-yozfont-new-kana -yozbn_m90.ttf fonts-yozvox-yozfont-new-kana -yozbnf.ttf fonts-yozvox-yozfont-new-kana -yozbnf90.ttf fonts-yozvox-yozfont-new-kana -yozbnf90i.ttf fonts-yozvox-yozfont-new-kana -yozbnfi.ttf fonts-yozvox-yozfont-new-kana -yozbnfm.ttf fonts-yozvox-yozfont-new-kana -yozbnfm90.ttf fonts-yozvox-yozfont-new-kana -yozbs_.ttf fonts-yozvox-yozfont-standard-kana -yozbs_90.ttf fonts-yozvox-yozfont-standard-kana -yozbs_90i.ttf fonts-yozvox-yozfont-standard-kana -yozbs_i.ttf fonts-yozvox-yozfont-standard-kana -yozbsf.ttf fonts-yozvox-yozfont-standard-kana -yozbsf90.ttf fonts-yozvox-yozfont-standard-kana -yozbsf90i.ttf fonts-yozvox-yozfont-standard-kana -yozbsfi.ttf fonts-yozvox-yozfont-standard-kana -yozbsp.ttf fonts-yozvox-yozfont-standard-kana -yozbsp90.ttf fonts-yozvox-yozfont-standard-kana -yozra_.ttf fonts-yozvox-yozfont-antique -yozra_90.ttf fonts-yozvox-yozfont-antique -yozra_90i.ttf fonts-yozvox-yozfont-antique -yozra_i.ttf fonts-yozvox-yozfont-antique -yozraf.ttf fonts-yozvox-yozfont-antique -yozraf90.ttf fonts-yozvox-yozfont-antique -yozraf90i.ttf fonts-yozvox-yozfont-antique -yozrafi.ttf fonts-yozvox-yozfont-antique -yozrap.ttf fonts-yozvox-yozfont-antique -yozrap90.ttf fonts-yozvox-yozfont-antique -yozrc_.ttf fonts-yozvox-yozfont-cute -yozrc_90.ttf fonts-yozvox-yozfont-cute -yozrc_90i.ttf fonts-yozvox-yozfont-cute -yozrc_i.ttf fonts-yozvox-yozfont-cute -yozrcf.ttf fonts-yozvox-yozfont-cute -yozrcf90.ttf fonts-yozvox-yozfont-cute -yozrcf90i.ttf fonts-yozvox-yozfont-cute -yozrcfi.ttf fonts-yozvox-yozfont-cute -yozre_.ttf fonts-yozvox-yozfont-edu -yozre_90.ttf fonts-yozvox-yozfont-edu -yozre_90i.ttf fonts-yozvox-yozfont-edu -yozre_i.ttf fonts-yozvox-yozfont-edu -yozre_m.ttf fonts-yozvox-yozfont-edu -yozre_m90.ttf fonts-yozvox-yozfont-edu -yozref.ttf fonts-yozvox-yozfont-edu -yozref90.ttf fonts-yozvox-yozfont-edu -yozref90i.ttf fonts-yozvox-yozfont-edu -yozrefi.ttf fonts-yozvox-yozfont-edu -yozrefm.ttf fonts-yozvox-yozfont-edu -yozrefm90.ttf fonts-yozvox-yozfont-edu -yozrex.ttf fonts-yozvox-yozfont-edu -yozrex90.ttf fonts-yozvox-yozfont-edu -yozrexf.ttf fonts-yozvox-yozfont-edu -yozrexf90.ttf fonts-yozvox-yozfont-edu -yozrexm.ttf fonts-yozvox-yozfont-edu -yozrexm90.ttf fonts-yozvox-yozfont-edu -yozrn_.ttf fonts-yozvox-yozfont-new-kana -yozrn_90.ttf fonts-yozvox-yozfont-new-kana -yozrn_90i.ttf fonts-yozvox-yozfont-new-kana -yozrn_i.ttf fonts-yozvox-yozfont-new-kana -yozrn_m.ttf fonts-yozvox-yozfont-new-kana -yozrn_m90.ttf fonts-yozvox-yozfont-new-kana -yozrnf.ttf fonts-yozvox-yozfont-new-kana -yozrnf90.ttf fonts-yozvox-yozfont-new-kana -yozrnf90i.ttf fonts-yozvox-yozfont-new-kana -yozrnfi.ttf fonts-yozvox-yozfont-new-kana -yozrnfm.ttf fonts-yozvox-yozfont-new-kana -yozrnfm90.ttf fonts-yozvox-yozfont-new-kana -yozrnx.ttf fonts-yozvox-yozfont-new-kana -yozrnx90.ttf fonts-yozvox-yozfont-new-kana -yozrnxf.ttf fonts-yozvox-yozfont-new-kana -yozrnxf90.ttf fonts-yozvox-yozfont-new-kana -yozrnxm.ttf fonts-yozvox-yozfont-new-kana -yozrnxm90.ttf fonts-yozvox-yozfont-new-kana -yozrs_.ttf fonts-yozvox-yozfont-standard-kana -yozrs_90.ttf fonts-yozvox-yozfont-standard-kana -yozrs_90i.ttf fonts-yozvox-yozfont-standard-kana -yozrs_i.ttf fonts-yozvox-yozfont-standard-kana -yozrsf.ttf fonts-yozvox-yozfont-standard-kana -yozrsf90.ttf fonts-yozvox-yozfont-standard-kana -yozrsf90i.ttf fonts-yozvox-yozfont-standard-kana -yozrsfi.ttf fonts-yozvox-yozfont-standard-kana -yozrsp.ttf fonts-yozvox-yozfont-standard-kana -yozrsp90.ttf fonts-yozvox-yozfont-standard-kana -yozrsx.ttf fonts-yozvox-yozfont-standard-kana -yozrsx90.ttf fonts-yozvox-yozfont-standard-kana -yozrsxf.ttf fonts-yozvox-yozfont-standard-kana -yozrsxf90.ttf fonts-yozvox-yozfont-standard-kana -yozrsxm.ttf fonts-yozvox-yozfont-standard-kana -yozrsxm90.ttf fonts-yozvox-yozfont-standard-kana yrsa-bold.ttf fonts-yrsa-rasa yrsa-light.ttf fonts-yrsa-rasa yrsa-medium.ttf fonts-yrsa-rasa yrsa-regular.ttf fonts-yrsa-rasa yrsa-semibold.ttf fonts-yrsa-rasa -z003-mediumitalic.otf fonts-urw-base35 z003034d.pfb t1-cyrillic zaghawaberia.otf fonts-sil-zaghawa-beria -zainer-goticoantiqua96g.otf fonts-gotico-antiqua -zainer-initials45mm.otf fonts-gotico-antiqua zelan.ttf fonts-senamirmir-washra zeldadxt.ttf ttf-aenigma zenith.ttf ttf-aenigma diff -Nru lintian-2.93.0/data/menu-format/known-desktop-keys lintian-2.89.0ubuntu1/data/menu-format/known-desktop-keys --- lintian-2.93.0/data/menu-format/known-desktop-keys 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/data/menu-format/known-desktop-keys 2020-08-10 09:59:45.000000000 +0000 @@ -19,7 +19,6 @@ NotShowIn OnlyShowIn Path -PrefersNonDefaultGPU StartupNotify StartupWMClass Terminal diff -Nru lintian-2.93.0/data/scripts/interpreters lintian-2.89.0ubuntu1/data/scripts/interpreters --- lintian-2.93.0/data/scripts/interpreters 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/data/scripts/interpreters 2020-08-10 09:59:45.000000000 +0000 @@ -79,7 +79,6 @@ pypy => /usr/bin python => /usr/bin, python:any | python-minimal:any | python2:any | python2-minimal:any python2 => /usr/bin, python:any | python-minimal:any | python2:any | python2-minimal:any -python3 => /usr/bin, python3:any | python3-minimal:any pforth => /usr/bin racket => /usr/bin rake => /usr/bin diff -Nru lintian-2.93.0/data/scripts/versioned-interpreters lintian-2.89.0ubuntu1/data/scripts/versioned-interpreters --- lintian-2.93.0/data/scripts/versioned-interpreters 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/data/scripts/versioned-interpreters 2020-08-10 09:59:45.000000000 +0000 @@ -75,7 +75,6 @@ octave => /usr/bin, octave([\d.]+), octave$1, 3.0 3.2 pike => /usr/bin, pike([\d.]+), pike$1 | pike$1-core, 7.6 7.8, @NO_DEFAULT_DEPS@ python => /usr/bin, python([\d.]+), python$1:any | python$1-minimal:any, 2.7, @SKIP_UNVERSIONED@ -python3 => /usr/bin, python3([\d.]+), python3$1:any | python3$1-minimal:any, 3.4 3.5 3.7 3.8, @SKIP_UNVERSIONED@ ruby => /usr/bin, ruby([\d.]+), ruby$1, 1.8 1.9, @SKIP_UNVERSIONED@ runghc => /usr/bin, runghc(\d+), ghc$1, 6, ghc scsh => /usr/bin, scsh-([\d.]+), scsh-$1, 0.6 diff -Nru lintian-2.93.0/debian/changelog lintian-2.89.0ubuntu1/debian/changelog --- lintian-2.93.0/debian/changelog 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/debian/changelog 2021-05-13 21:58:37.000000000 +0000 @@ -1,88 +1,9 @@ -lintian (2.93.0) unstable; urgency=medium +lintian (2.89.0ubuntu1) groovy; urgency=medium - [ Felix Lechner ] - * Process display options according to truth value, not presence. - (Closes: #969406) - * Only announce left over processes in debug mode, fixing autopkgtest - failures. - * Clean up profile code and drop {VENDOR} notation in profile names. - * Support newlines in file names. (Re: #929729) + * Teach lintian that impish and hirsute are valid Ubuntu releases. + (LP: #1928392) - [ Peter Pentchev ] - * Ignore *.txt files in Python egg-info directories. - - [ Reiner Herrmann ] - * Add PrefersNonDefaultGPU to known-desktop-keys. - - -- Chris Lamb Thu, 03 Sep 2020 21:54:58 +0000 - -lintian (2.92.0) unstable; urgency=medium - - [ Felix Lechner ] - * Drop obsolete output formats ColonSeparated, FullEWI, LetterQualifier - and XML. - * Provide a Perl-native implementation to index and extract tar files in - parallel. (Closes: #968611) - * Reduce visibility level of redundant-globbing-patterns to pedantic. - (Closes: #967961) - * Reset file_info for TeX Font Metric files incorrectly categorized as gzip. - (Closes: #963589) - * Replace python2 with python3 in debian/tests/control. (Closes: #936952) - * Split bin/lintian-info into separate annotate-lintian-hints and - explain-lintian-tags. - * Drop Lintian version from tag URLs offered in "standalone" HTML mode. - * Use Text::Glob to match globbing patterns to file names in - debian/copyright. - * Remove IO::Async from Depends in debian/control and move to - debian/tests/control. - - * Update tag description files: - - Rename file extensions from *.desc to *.tag. - - For friendlier field names, rename Info: to Explanation: and Ref: to - See-Also: - - Use Text::Markdown::Discount to facilitate Markdown content. - - Also decode HTML5 entities in plain output; add - libhtml-html5-entities-perl to debian/control. - - Replace underscores with the _ HTML5 entity. - - [ Chris Lamb ] - * Don't emit patch-not-forwarded-upstream for README files under - debian/patches. (Closes: #968845) - * Update private/generate-tag-summary to reflect change of tag definition - filename extension change from .desc → .tag. - - [ Dmitry Shachnev ] - * Refresh data/files/fonts using refresh-fonts-data script. - - -- Chris Lamb Fri, 28 Aug 2020 12:29:46 +0100 - -lintian (2.91.0) unstable; urgency=medium - - [ Felix Lechner ] - * Set most spelling-related tags to info or pedantic level and improve - line references for spelling errors in override files. (Re: #968416) - * Issue the repeated-path-segments tag only directories only. - * For the first time, unpack tarballs in orig index and use centralized - streaming unpacker. - - [ Chris Lamb ] - * Clarify the grammar of the package-uses-old-debhelper-compat-version - tag. - - -- Chris Lamb Thu, 20 Aug 2020 21:20:00 +0000 - -lintian (2.90.0) unstable; urgency=medium - - [ Felix Lechner ] - * Un-deprecate /etc/lintianrc, remove file on upgrade and ship in - doc/examples. (Closes: #968326) - * Move all executables not meant for shipping to ./private. - * Large number of internal changes to use IPC::Run3 over IO::Async. - - [ Andrius Merkys ] - * Fix a typo in the long description of the breakout-link tag. - - -- Chris Lamb Fri, 14 Aug 2020 08:55:33 +0000 + -- Brian Murray Thu, 13 May 2021 14:58:37 -0700 lintian (2.89.0) unstable; urgency=medium diff -Nru lintian-2.93.0/debian/control lintian-2.89.0ubuntu1/debian/control --- lintian-2.93.0/debian/control 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/debian/control 2021-05-13 21:58:37.000000000 +0000 @@ -1,7 +1,8 @@ Source: lintian Section: devel Priority: optional -Maintainer: Debian Lintian Maintainers +Maintainer: Ubuntu Developers +XSBC-Original-Maintainer: Debian Lintian Maintainers Uploaders: Colin Watson , Russ Allbery , @@ -47,7 +48,9 @@ libfile-basedir-perl, libfile-find-rule-perl, libfont-ttf-perl, - libhtml-html5-entities-perl, + libhtml-parser-perl, + libio-async-perl, + libio-async-loop-epoll-perl (>= 0.20), libipc-run3-perl, libjson-maybexs-perl, liblist-compare-perl, @@ -58,12 +61,9 @@ libnamespace-clean-perl, libpath-tiny-perl, libperlio-gzip-perl, - libproc-processtable-perl, libsereal-decoder-perl, libsereal-encoder-perl, - libtext-glob-perl, libtext-levenshteinxs-perl, - libtext-markdown-discount-perl, libtext-xslate-perl, libtime-duration-perl, libtime-moment-perl, @@ -73,6 +73,7 @@ libunicode-utf8-perl, liburi-perl, libxml-libxml-perl, + libxml-writer-perl, libyaml-libyaml-perl, lzip | clzip, lzop, diff -Nru lintian-2.93.0/debian/lintian.links lintian-2.89.0ubuntu1/debian/lintian.links --- lintian-2.93.0/debian/lintian.links 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/debian/lintian.links 2020-08-10 09:59:45.000000000 +0000 @@ -1,7 +1,4 @@ usr/share/lintian/bin/lintian usr/bin/lintian -usr/share/lintian/bin/explain-lintian-tags usr/bin/explain-lintian-tags -usr/share/lintian/bin/annotate-lintian-hints usr/bin/annotate-lintian-hints -usr/share/lintian/bin/annotate-lintian-hints usr/bin/lintian-info -usr/share/man/man1/annotate-lintian-tags.1.gz usr/share/man/man1/lintian-info.1.gz +usr/share/lintian/bin/lintian-info usr/bin/lintian-info usr/share/lintian/bin/spellintian usr/bin/spellintian usr/share/doc/lintian/lintian.rst usr/share/doc/lintian/lintian.txt diff -Nru lintian-2.93.0/debian/lintian.maintscript lintian-2.89.0ubuntu1/debian/lintian.maintscript --- lintian-2.93.0/debian/lintian.maintscript 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/debian/lintian.maintscript 1970-01-01 00:00:00.000000000 +0000 @@ -1 +0,0 @@ -rm_conffile /etc/lintianrc 2.90.0~ lintian diff -Nru lintian-2.93.0/debian/rules lintian-2.89.0ubuntu1/debian/rules --- lintian-2.93.0/debian/rules 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/debian/rules 2020-08-10 09:59:45.000000000 +0000 @@ -8,7 +8,8 @@ profiles/debian/ftp-master-auto-reject.profile pod2man := pod2man --center "Debian Package Checker" --release "Lintian v$(VER)" pod2mansources := $(wildcard man/*.pod) -docsources := doc/lintian.rst README.md $(pod2mansources) +docsource := doc/lintian.rst README.md man/lintian.pod.in \ + $(pod2mansources) perlprovides := data/fields/perl-provides autoreject_data := $(wildcard private/build-time-data/*) @@ -40,11 +41,12 @@ $(tmp)/usr/share/lintian/bin/lintian-info $(PERL) -p -i -e 's/my \$$LINTIAN_VERSION;/my \$$LINTIAN_VERSION = q{$(VER)};/;' \ $(tmp)/usr/share/lintian/bin/spellintian + install -m 644 doc/lintianrc.example $(tmp)/etc/lintianrc profiles: $(profiles); -$(profiles): $(autoreject_data) private/generate-profiles - private/generate-profiles +$(profiles): $(autoreject_data) private/generate-profiles.pl + private/generate-profiles.pl api-doc: private/generate-html-docs doc/api.html @@ -52,12 +54,13 @@ .PHONY: generate-docs generate-docs: generate-docs-stamp -generate-docs-stamp: $(docsources) +generate-docs-stamp: $(docsource) dh_testdir # A UTF-8 locale seemed appropriate; manual uses § character cd doc && LC_ALL=en_US.UTF-8 rst2html lintian.rst > lintian.html mkdir -p man/man1/ man/man3/ - $(pod2man) --name lintian --section=1 man/lintian.pod > man/man1/lintian.1 + private/generate-lintian-pod | \ + $(pod2man) --name lintian --section=1 > man/man1/lintian.1 set -e ; for POD in $(pod2mansources) ; do \ BASENAME=$$(basename "$$POD" .pod) ; \ $(pod2man) --section=1 "$$POD" > "man/man1/$$BASENAME".1 ; \ diff -Nru lintian-2.93.0/debian/salsa-ci.yml lintian-2.89.0ubuntu1/debian/salsa-ci.yml --- lintian-2.93.0/debian/salsa-ci.yml 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/debian/salsa-ci.yml 2020-08-10 09:59:45.000000000 +0000 @@ -13,6 +13,3 @@ RELEASE: 'buster-backports' extends: .build-package allow_failure: true - -variables: - SALSA_CI_LINTIAN_FAIL_WARNING: 1 diff -Nru lintian-2.93.0/debian/tests/build-and-evaluate-test-packages lintian-2.89.0ubuntu1/debian/tests/build-and-evaluate-test-packages --- lintian-2.93.0/debian/tests/build-and-evaluate-test-packages 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/debian/tests/build-and-evaluate-test-packages 2020-08-10 09:59:45.000000000 +0000 @@ -5,7 +5,7 @@ export LINTIAN_TEST_INSTALLED=yes WORKDIR="$AUTOPKGTEST_TMP/$(basename $0)" -private/build-test-packages --debug --work-dir="$WORKDIR" -private/runtests --debug --unattended --keep-going --work-dir="$WORKDIR" --onlyrun="suite:recipes" +bin/build-test-packages --debug --work-dir="$WORKDIR" +bin/runtests --debug --unattended --keep-going --work-dir="$WORKDIR" --onlyrun="suite:recipes" rm -rf "${WORKDIR}" diff -Nru lintian-2.93.0/debian/tests/control lintian-2.89.0ubuntu1/debian/tests/control --- lintian-2.93.0/debian/tests/control 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/debian/tests/control 2020-08-10 09:59:45.000000000 +0000 @@ -19,8 +19,6 @@ gcc-mingw-w64-x86-64, gpg-agent, javahelper, - libio-async-perl, - libio-async-loop-epoll-perl (>= 0.20), libpod-coverage-trustpod-perl, libtest-minimumversion-perl, libtest-perl-critic-perl, @@ -36,10 +34,9 @@ mingw-w64-tools, pkg-js-tools, pkg-php-tools, - python3, - python3-dev, + python2, + python-all-dev, python3-numpy, quilt, - tidy, uglifyjs, zip, diff -Nru lintian-2.93.0/doc/examples/lintianrc lintian-2.89.0ubuntu1/doc/examples/lintianrc --- lintian-2.93.0/doc/examples/lintianrc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/doc/examples/lintianrc 1970-01-01 00:00:00.000000000 +0000 @@ -1,56 +0,0 @@ -# /etc/lintianrc -- Lintian configuration file -# -# Note, that Lintian has reasonable default values for all variables -# specified below. Thus, you don't have to change this file unless you -# want something special. -# -# Also note, that this file uses a special syntax: -# Empty lines are allowed, comments are introduced by a hash sign (#). -# All other lines must have the format -# VAR=text -# or -# VAR="text" -# or -# VAR = text -# It is allowed to use `~' and `$HOME' in the variables, but not other -# shell/environment variables. - -# Enable info tags by default (--display info) -#display-info = yes - -# Limit the number of parallel unpacking jobs to X (--jobs) -#jobs = 8 - -# Enable pedantic tags by default (--pedantic) -#pedantic = yes - -# Enable experimental tags by default (--display-experimental) -#display-experimental = yes - -# Enable colored output for terminal output (--color) -#color = auto - -# Show overridden tags (--show-overrides) -#show-overrides = yes - -# Ignore all overrides (--no-override) -#override = no - -# Verbose output by default (--verbose) -#verbose = yes - -# Quiet by default (--quiet) -#quiet = yes - -# Use a different directory for temporary files - useful if /tmp is a -# tmpfs with "limited" capacity. -#TMPDIR="/var/tmp" - -# Suppress the listed tags (--suppress-tags) -#suppress-tags = debian-watch-does-not-check-gpg-signature - -# Suppress the tags listed in the specified file (--suppress-tags-from-file) -#suppress-tags-from-file = /path/to/file.txt - -# Specify "tag per package" display limit (--tag-display-limit) -#tag-display-limit = 42 diff -Nru lintian-2.93.0/doc/lintianrc.example lintian-2.89.0ubuntu1/doc/lintianrc.example --- lintian-2.93.0/doc/lintianrc.example 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/doc/lintianrc.example 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,56 @@ +# /etc/lintianrc -- Lintian configuration file +# +# Note, that Lintian has reasonable default values for all variables +# specified below. Thus, you don't have to change this file unless you +# want something special. +# +# Also note, that this file uses a special syntax: +# Empty lines are allowed, comments are introduced by a hash sign (#). +# All other lines must have the format +# VAR=text +# or +# VAR="text" +# or +# VAR = text +# It is allowed to use `~' and `$HOME' in the variables, but not other +# shell/environment variables. + +# Enable info tags by default (--display info) +#display-info = yes + +# Limit the number of parallel unpacking jobs to X (--jobs) +#jobs = 8 + +# Enable pedantic tags by default (--pedantic) +#pedantic = yes + +# Enable experimental tags by default (--display-experimental) +#display-experimental = yes + +# Enable colored output for terminal output (--color) +#color = auto + +# Show overridden tags (--show-overrides) +#show-overrides = yes + +# Ignore all overrides (--no-override) +#override = no + +# Verbose output by default (--verbose) +#verbose = yes + +# Quiet by default (--quiet) +#quiet = yes + +# Use a different directory for temporary files - useful if /tmp is a +# tmpfs with "limited" capacity. +#TMPDIR="/var/tmp" + +# Suppress the listed tags (--suppress-tags) +#suppress-tags = debian-watch-does-not-check-gpg-signature + +# Suppress the tags listed in the specified file (--suppress-tags-from-file) +#suppress-tags-from-file = /path/to/file.txt + +# Specify "tag per package" display limit (--tag-display-limit) +#tag-display-limit = 42 diff -Nru lintian-2.93.0/doc/tutorial/Lintian/Tutorial/TestSuite.pod lintian-2.89.0ubuntu1/doc/tutorial/Lintian/Tutorial/TestSuite.pod --- lintian-2.93.0/doc/tutorial/Lintian/Tutorial/TestSuite.pod 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/doc/tutorial/Lintian/Tutorial/TestSuite.pod 2020-08-10 09:59:45.000000000 +0000 @@ -24,7 +24,7 @@ To run the full suite: - $ rm -rf debian/test-out; private/build-test-packages; private/runtests + $ rm -rf debian/test-out; t/bin/build-test-packages; t/bin/runtests While writing a new tag (or check) you probably only want to run a particular (subset of the) test(s). See L. This is -done by passing I<--coverage> to I. Example: +done by passing I<--coverage> to I. Example: - $ private/runtests --coverage --dump-logs -j1 -k t debian/test-out + $ t/bin/runtests --coverage --dump-logs -j1 -k t debian/test-out Please note that L does not seem to handle multiple threads too well. You may see spurious warnings/errors if you run the @@ -96,15 +96,15 @@ allows you to "slowly" build up the coverage database over multiple runs. Example: - $ private/runtests --coverage --dump-logs -j1 -k t debian/test-out suite:scripts - $ private/runtests --coverage --dump-logs -j1 -k t debian/test-out suite:debs - $ private/runtests --coverage --dump-logs -j1 -k t debian/test-out suite:source + $ t/bin/runtests --coverage --dump-logs -j1 -k t debian/test-out suite:scripts + $ t/bin/runtests --coverage --dump-logs -j1 -k t debian/test-out suite:debs + $ t/bin/runtests --coverage --dump-logs -j1 -k t debian/test-out suite:source ... Or: - $ private/runtests --coverage --dump-logs -j1 -k t debian/test-out $check - $ private/runtests --coverage --dump-logs -j1 -k t debian/test-out legacy + $ t/bin/runtests --coverage --dump-logs -j1 -k t debian/test-out $check + $ t/bin/runtests --coverage --dump-logs -j1 -k t debian/test-out legacy =head1 SEE ALSO diff -Nru lintian-2.93.0/doc/tutorial/Lintian/Tutorial/WritingTests.pod lintian-2.89.0ubuntu1/doc/tutorial/Lintian/Tutorial/WritingTests.pod --- lintian-2.93.0/doc/tutorial/Lintian/Tutorial/WritingTests.pod 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/doc/tutorial/Lintian/Tutorial/WritingTests.pod 2020-08-10 09:59:45.000000000 +0000 @@ -208,7 +208,7 @@ OR - $ private/runtests --dump-logs t debian/test-out pkg-deb-check-general + $ t/bin/runtests --dump-logs t debian/test-out pkg-deb-check-general However, it will not emit the correct tags unless pkg/deb-check is part of the debian/main lintian profile. If your check is a part of a diff -Nru lintian-2.93.0/lib/Lintian/Command/Simple.pm lintian-2.89.0ubuntu1/lib/Lintian/Command/Simple.pm --- lintian-2.93.0/lib/Lintian/Command/Simple.pm 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/lib/Lintian/Command/Simple.pm 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,176 @@ +# Copyright © 2010 Raphael Geissert +# +# This program is free software; you can redistribute it and/or modify it +# under the terms of the GNU General Public License as published by the Free +# Software Foundation; either version 2 of the License, or (at your option) +# any later version. +# +# This program is distributed in the hope that it will be useful, but WITHOUT +# ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or +# FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for +# more details. +# +# You should have received a copy of the GNU General Public License along with +# this program. If not, see . + +package Lintian::Command::Simple; + +use v5.20; +use warnings; +use utf8; + +use Exporter qw(import); +use POSIX qw(:sys_wait_h); + +our @EXPORT_OK = qw(wait_any kill_all); + +=head1 NAME + +Lintian::Command::Simple - Run commands without pipes + +=head1 SYNOPSIS + + use Lintian::Command::Simple qw(wait_any); + + my %pid_info; + my $pid = fork() // die("fork: $!"); + exec('do', 'something') if $pid == 0; + $pid_info{$pid} = "A useful value associated with $pid"; + + my ($termiated_pid, $value) = wait_any(\%pid_info); + ...; + +=head1 DESCRIPTION + +Lintian::Command::Simple allows running commands with the capability of +running them "in the background" (asynchronously.) + +Pipes are not handled at all, except for those handled internally by +the shell. See 'perldoc -f exec's note about shell metacharacters. +If you want to pipe to/from Perl, look at Lintian::Command instead. + +=over 4 + +=item wait_any (hashref[, nohang]) + +When starting multiple processes asynchronously, it is common to wait +until the first is done. While the CORE::wait() function is usually +used for that very purpose, it does not provide the desired results +when the processes were started via the OO interface. + +To help with this task, wait_any() can take a hash ref where the key +of each entry is the pid of that command. There are no requirements +for the value (which can be used for any application specific +purpose). + +Under this mode, wait_any() waits until any child process is done. +The key (and value) associated the pid of the reaped child will then +be removed from the hashref. The exitcode of the child is available +via C<$?> as usual. + +The results and return value are undefined when under this mode +wait_any() "accidentally" reaps a process not listed in the hashref. + +The return value in scalar context is value associated with the pid of +the reaped processed. In list context, the pid and value are returned +as a pair. + +Whenever waitpid() would return -1, wait_any() returns undef or a null +value so that it is safe to: + + while($cmd = wait_any(\%hash)) { something; } + +The same is true whenever the hash reference points to an empty hash. + +If C is also given, wait_any will attempt to reap any child +process non-blockingly. If no child can be reaped, it will +immediately return (like there were no more processes left) instead of +waiting. + +=cut + +sub wait_any { + my ($jobs, $nohang) = @_; + my $reaped_pid; + my $extra; + + $nohang = WNOHANG if $nohang; + $nohang //= 0; + + return unless scalar keys %$jobs; + + $reaped_pid = waitpid(-1, $nohang); + + if ($reaped_pid == -1 or ($nohang and $reaped_pid == 0)) { + return; + } + + # Did we reap some other pid? + return unless exists $jobs->{$reaped_pid}; + + $extra = delete $jobs->{$reaped_pid}; + return ($reaped_pid, $extra) if wantarray; + return $extra; +} + +=item kill_all(hashref[, signal]) + +In a similar way to wait_any(), it is possible to pass a hash +reference to kill_all(). It will then kill all of the processes +(default signal being "TERM") followed by a reaping of the processes. +All reaped processes (and their values) will be removed from the set. + +Any entries remaining in the hashref are processes that did not +terminate (or did not terminate yet). + +=cut + +sub kill_all { + my ($jobs, $signal) = @_; + my $count = 0; + my @jobs; + + $signal //= 'TERM'; + + foreach my $pid (keys %$jobs) { + push @jobs, $pid if kill $signal, $pid; + } + + foreach my $pid (@jobs) { + if (waitpid($pid, 0) == $pid) { + $count++; + delete $jobs->{$pid}; + } + } + + return scalar @jobs; +} + +1; + +__END__ + +=back + +=head1 NOTES + +Unless specified by prefixing the package name, every reference to a +function/method in this documentation refers to the functions/methods +provided by this package itself. + +=head1 CAVEATS + +Combining asynchronous jobs (e.g. via Lintian::Command) and calls to +wait_any() can lead to unexpected results. + +=head1 AUTHOR + +Originally written by Raphael Geissert for Lintian. + +=cut + +# Local Variables: +# indent-tabs-mode: nil +# cperl-indent-level: 4 +# End: +# vim: syntax=perl sw=4 sts=4 sr et diff -Nru lintian-2.93.0/lib/Lintian/Deb822/Section.pm lintian-2.89.0ubuntu1/lib/Lintian/Deb822/Section.pm --- lintian-2.93.0/lib/Lintian/Deb822/Section.pm 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/lib/Lintian/Deb822/Section.pm 2020-08-10 09:59:45.000000000 +0000 @@ -191,24 +191,6 @@ return $self->verbatim->{$exact} // EMPTY; } -=item text (FIELD) - -=cut - -sub text { - my ($self, $name) = @_; - - my $text = $self->untrimmed_value($name); - - # remove leading space in each line - $text =~ s/^[ \t]//mg; - - # remove dot place holder for empty lines - $text =~ s/^\.$//mg; - - return $text; -} - =item set (FIELD, VALUE) =cut diff -Nru lintian-2.93.0/lib/Lintian/Group.pm lintian-2.89.0ubuntu1/lib/Lintian/Group.pm --- lintian-2.93.0/lib/Lintian/Group.pm 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/lib/Lintian/Group.pm 2020-08-10 09:59:45.000000000 +0000 @@ -24,7 +24,8 @@ use utf8; use autodie; -use Carp qw(croak); +use Carp; +use Cwd; use Devel::Size qw(total_size); use File::Spec; use List::Compare; @@ -33,7 +34,9 @@ use POSIX qw(ENOENT); use Time::HiRes qw(gettimeofday tv_interval); use Time::Piece; +use Unicode::UTF8 qw(valid_utf8 decode_utf8); +use Lintian::Deb822::Parser qw(parse_dpkg_control_string); use Lintian::Processable::Binary; use Lintian::Processable::Buildinfo; use Lintian::Processable::Changes; @@ -43,6 +46,9 @@ use constant EMPTY => q{}; use constant SPACE => q{ }; +use constant HYPHEN => q{-}; +use constant SLASH => q{/}; +use constant UNDERSCORE => q{_}; use Moo; use namespace::clean; @@ -128,6 +134,8 @@ =item C +=item C + =cut has pooldir => (is => 'rw', default => EMPTY); @@ -146,11 +154,17 @@ has cache => (is => 'rw', default => sub { {} }); has profile => (is => 'rw', default => sub { {} }); -=item add_processable_from_file +has saved_direct_dependencies => (is => 'rw', default => sub { {} }); +has saved_direct_reliants => (is => 'rw', default => sub { {} }); +has saved_spelling_exceptions => (is => 'rw', default => sub { {} }); + +=item Lintian::Group->init_from_file (FILE) + +Add all processables from .changes or .buildinfo file FILE. =cut -sub add_processable_from_file { +sub _get_processable { my ($self, $file) = @_; my $absolute = path($file)->realpath->stringify; @@ -182,64 +196,160 @@ $processable->pooldir($self->pooldir); $processable->init($absolute); + return $processable; +} + +# populates $self from a buildinfo or changes file. +sub init_from_file { + my ($self, $path) = @_; + + return + unless defined $path; + + my $processable = $self->_get_processable($path); + return + unless $processable; + $self->add_processable($processable); - return $processable; + my ($type) = $path =~ m/\.(buildinfo|changes)$/; + return + unless defined $type; + + my $bytes = path($path)->slurp; + + my $contents; + if(valid_utf8($bytes)) { + $contents = decode_utf8($bytes); + } else { + # try to proceed with nat'l encoding; stopping here breaks tests + $contents = $bytes; + } + + my @paragraphs; + @paragraphs = parse_dpkg_control_string($contents) + or die "$path is not a valid $type file"; + my $info = $paragraphs[0]; + + my $dir = $path; + if ($path =~ m,^/+[^/]++$,){ + # it is "/files.changes?" + # - In case you were wondering, we were told not to ask :) + # See #624149 + $dir = '/'; + } else { + # it is "/files.changes" + $dir =~ s,(.+)/[^/]+$,$1,; + } + my $key = $type eq 'buildinfo' ? 'Checksums-Sha256' : 'Files'; + for my $line (split(/\n/, $info->{$key}//'')) { + + next + unless defined $line; + + # trim both ends + $line =~ s/^\s+|\s+$//g; + + next + if $line eq EMPTY; + + # Ignore files that may lead to path traversal issues. + + # We do not need (eg.) md5sum, size, section or priority + # - just the file name please. + my $file = (split(/\s+/, $line))[-1]; + + # If the field is malformed, $file may be undefined; we also + # skip it, if it contains a "/" since that is most likely a + # traversal attempt + next + if !$file || $file =~ m,/,; + + die "$dir/$file does not exist, exiting\n" + unless -f "$dir/$file"; + + # only care about some files; ddeb is ubuntu dbgsym + next + unless $file =~ /\.(?:u|d)?deb$/ + || $file =~ m/\.dsc$/ + || $file =~ m/\.buildinfo$/; + + my $payload = $self->_get_processable("$dir/$file"); + $self->add_processable($payload); + } + + return 1; } -=item process +=item unpack -Process group. +Unpack this group. =cut -sub process { - my ($self, $ignored_overrides, $option, $OUTPUT)= @_; - - $self->processing_start(gmtime->datetime . 'Z'); +sub unpack { + my ($self, $OUTPUT)= @_; my $groupname = $self->name; local $SIG{__WARN__} = sub { warn "Warning in group $groupname: $_[0]" }; - $OUTPUT->v_msg('Starting on group ' . $self->name); - my @processables = $self->get_processables; for my $processable (@processables) { - path($processable->basedir)->mkpath - unless -e $processable->basedir; + $processable->create; - symlink($processable->path, $processable->link) - unless -l $processable->link; + # for sources pull in all related files so unpacked does not fail + if ($processable->type eq 'source') { + my (undef, $dir, undef)= File::Spec->splitpath($processable->path); + for my $fs (split(/\n/, $processable->fields->value('Files'))) { + + # trim both ends + $fs =~ s/^\s+|\s+$//g; + + next if $fs eq ''; + my @t = split(/\s+/, $fs); + next if ($t[2] =~ m,/,); + symlink("$dir/$t[2]", $processable->groupdir . "/$t[2]") + or croak("cannot symlink file $t[2]: $!"); + } + } + } - if ($processable->can('unpack')) { + $OUTPUT->v_msg('Unpacking packages in group ' . $self->name); - my $unpack_start = [gettimeofday]; - $OUTPUT->v_msg( - 'Unpacking packages in processable ' . $processable->name); + my @unpack = grep { $_->can('unpack') } @processables; - $processable->unpack; + my $savedir = getcwd; + $_->unpack for @unpack; + chdir($savedir); - my $unpack_raw_res = tv_interval($unpack_start); - my $unpack_tres = sprintf('%.3fs', $unpack_raw_res); + return; +} - $OUTPUT->debug_msg(1, - 'Unpack of ' . $processable->name . " done ($unpack_tres)"); - $OUTPUT->perf_log( - $self->name . ",total-processable-unpack,$unpack_raw_res"); - } - } +=item process + +Process group. + +=cut + +sub process { + my ($self, $ignored_overrides, $option, $OUTPUT)= @_; + + $self->processing_start(gmtime->datetime . 'Z'); my $success = 1; my $timer = [gettimeofday]; + my $groupname = $self->name; + local $SIG{__WARN__} = sub { warn "Warning in group $groupname: $_[0]" }; + for my $processable ($self->get_processables){ my $declared_overrides; $OUTPUT->debug_msg(1, - 'Base directory for processable: ' . $processable->basedir); + 'Base directory for group: ' . $processable->groupdir); unless ($option->{'no-override'}) { @@ -311,17 +421,14 @@ my $raw_res = tv_interval($timer); if ($err) { - my $message = $err; - $message - .= "warning: cannot run $checkname check on package $procid\n"; - $message .= "skipping check of $procid\n"; - warn $message; - + print STDERR $err; + print STDERR "internal error: cannot run $checkname check", + " on package $procid\n"; + $OUTPUT->warning("skipping check of $procid"); $success = 0; next; } - my $tres = sprintf('%.3fs', $raw_res); $OUTPUT->debug_msg(1, "Check script $checkname for $procid done ($tres)"); @@ -523,6 +630,10 @@ croak 'Not a supported type (' . $processable->type . ')' unless exists $SUPPORTED_TYPES{$processable->type}; + my $dir = $self->_pool_path($processable); + + $processable->groupdir($dir); + if ($processable->type eq 'changes') { die 'Cannot add another ' . $processable->type . ' file' if $self->changes; @@ -554,6 +665,44 @@ return 1; } +# Given the package meta data (src_name, type, name, version, arch) return the +# path to it in the Lab. The path returned will be absolute. +sub _pool_path { + my ($self, $processable) = @_; + + my $dir = $self->pooldir; + my $prefix; + + # If it is at least 4 characters and starts with "lib", use "libX" + # as prefix + if ($processable->source =~ m/^lib./) { + $prefix = substr $processable->source, 0, 4; + } else { + $prefix = substr $processable->source, 0, 1; + } + + my $path + = $prefix + . SLASH + . $processable->source + . SLASH + . $processable->name + . UNDERSCORE + . $processable->version; + $path .= UNDERSCORE . $processable->architecture + unless $processable->type eq 'source'; + $path .= UNDERSCORE . $processable->type; + + # Turn spaces into dashes - spaces do appear in architectures + # (i.e. for changes files). + $path =~ s/\s/-/g; + + # Also replace ":" with "_" as : is usually used for path separator + $path =~ s/:/_/g; + + return "$dir/pool/$path"; +} + =item $group->get_processables([$type]) Returns an array of all processables in $group. The processables are @@ -626,8 +775,6 @@ =cut -has saved_direct_dependencies => (is => 'rw', default => sub { {} }); - sub direct_dependencies { my ($self, $processable) = @_; @@ -678,8 +825,6 @@ =cut -has saved_direct_reliants => (is => 'rw', default => sub { {} }); - sub direct_reliants { my ($self, $processable) = @_; @@ -726,28 +871,30 @@ =cut -has spelling_exceptions => ( - is => 'rw', - lazy => 1, - default => sub { - my ($self) = @_; +sub spelling_exceptions { + my ($self) = @_; - my %exceptions; + return $self->saved_spelling_exceptions + if keys %{$self->saved_spelling_exceptions}; - for my $processable ($self->get_processables) { + my %exceptions; - my @names = ($processable->name, $processable->source); - push(@names, $processable->debian_control->installables) - if $processable->type eq 'source'; - - foreach my $name (@names) { - $exceptions{$name} = 1; - $exceptions{$_} = 1 for split m/-/, $name; - } + foreach my $processable ($self->get_processables) { + + my @names = ($processable->name, $processable->source); + push(@names, $processable->debian_control->installables) + if $processable->type eq 'source'; + + foreach my $name (@names) { + $exceptions{$name} = 1; + $exceptions{$_} = 1 for split m/-/, $name; } + } - return \%exceptions; - }); + $self->saved_spelling_exceptions(\%exceptions); + + return $self->saved_spelling_exceptions; +} =back diff -Nru lintian-2.93.0/lib/Lintian/Index/Ar.pm lintian-2.89.0ubuntu1/lib/Lintian/Index/Ar.pm --- lintian-2.93.0/lib/Lintian/Index/Ar.pm 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/lib/Lintian/Index/Ar.pm 2020-08-10 09:59:45.000000000 +0000 @@ -25,7 +25,7 @@ use Cwd; use Path::Tiny; -use Lintian::IPC::Run3 qw(safe_qx); +use Lintian::IO::Async qw(safe_qx); use constant EMPTY => q{}; use constant SPACE => q{ }; @@ -57,40 +57,40 @@ =cut sub add_ar { - my ($self) = @_; + my ($self, $groupdir) = @_; + + my $basket = "$groupdir/ar-info"; + + unlink($basket) + if -e $basket; my $savedir = getcwd; chdir($self->basedir); - my @archives - = grep { $_->name =~ /\.a$/ && $_->is_regular_file } $self->sorted_list; + my @archives; + foreach my $file ($self->sorted_list) { - for my $archive (@archives) { + next + unless $file->is_regular_file && $file =~ m{ \. a \Z }xsm; # skip empty archives to avoid ar error message; happens in tests next - unless $archive->size; - - my %ar_info; + unless $file->size; # fails silently for non-ar files (#934899); probably creates empty entries # in case of trouble, please try: "next if $?;" underneath it - my $output = safe_qx('ar', 't', $archive); - my @members = split(/\n/, $output); + my $output = safe_qx('ar', 't', $file); + my @contents = split(/\n/, $output); - my $count = 1; - for my $member (@members) { - - # more info could be added with -v above - $ar_info{$count}{name} = $member; - - } continue { - $count++; - } - - $archive->ar_info(\%ar_info); + my $line = $file . COLON; + $line .= SPACE . $_ for @contents; + push(@archives, $line); } + my $string = EMPTY; + $string .= $_ . NEWLINE for @archives; + path($basket)->spew($string); + chdir($savedir); return; diff -Nru lintian-2.93.0/lib/Lintian/Index/Control.pm lintian-2.89.0ubuntu1/lib/Lintian/Index/Control.pm --- lintian-2.93.0/lib/Lintian/Index/Control.pm 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/lib/Lintian/Index/Control.pm 2020-08-10 09:59:45.000000000 +0000 @@ -25,8 +25,24 @@ use utf8; use autodie; +use IO::Async::Loop; +use IO::Async::Process; use Path::Tiny; +use Lintian::Index::Item; +use Lintian::IO::Async qw(safe_qx); + +# read up to 40kB at a time. this happens to be 4096 "tar records" +# (with a block-size of 512 and a block factor of 20, which appear to +# be the defaults). when we do full reads and writes of READ_SIZE (the +# OS willing), the receiving end will never be with an incomplete +# record. +use constant READ_SIZE => 4096 * 20 * 512; + +use constant EMPTY => q{}; +use constant COLON => q{:}; +use constant NEWLINE => qq{\n}; + use Moo; use namespace::clean; @@ -60,29 +76,183 @@ =item collect +=item unpack + =cut sub collect { - my ($self, $processable_dir) = @_; + my ($self, $groupdir) = @_; # control files are not installed relative to the system root # disallow absolute paths and symbolic links + my $basedir = path($groupdir)->child('control')->stringify; + $self->basedir($basedir); - my @command = (qw(dpkg-deb --ctrl-tarfile), "$processable_dir/deb"); - my ($extract_errors, $index_errors) - = $self->create_from_piped_tar(\@command); - + $self->unpack($groupdir); $self->load; $self->add_fileinfo; $self->add_scripts; $self->add_control; - path("$processable_dir/control-errors")->spew_utf8($extract_errors) - if length $extract_errors; + return; +} + +sub unpack { + my ($self, $groupdir) = @_; + + path($self->basedir)->remove_tree + if -d $self->basedir; + + my $controlerrorspath = "$groupdir/control-errors"; + my $indexerrorspath = "$groupdir/control-index-errors"; + + for my $path ($controlerrorspath, $indexerrorspath) { + unlink($path) if -e $path; + } + + mkdir($self->basedir, 0777); + + my $debpath = "$groupdir/deb"; + return + unless -f $debpath; + + my $loop = IO::Async::Loop->new; + + # get control tarball from deb + my $deberror; + my $dpkgdeb = $loop->new_future; + my @debcommand = ('dpkg-deb', '--ctrl-tarfile', $debpath); + my $debprocess = IO::Async::Process->new( + command => [@debcommand], + stdout => { via => 'pipe_read' }, + stderr => { into => \$deberror }, + on_finish => sub { + my ($self, $exitcode) = @_; + my $status = ($exitcode >> 8); + + if ($status) { + my $message= "Non-zero status $status from @debcommand"; + $message .= COLON . NEWLINE . $deberror + if length $deberror; + $dpkgdeb->fail($message); + return; + } + + $dpkgdeb->done("Done with @debcommand"); + return; + }); + + # extract the tarball's contents + my $extracterror; + my $extractor = $loop->new_future; + my @extractcommand = ( + 'tar', '--no-same-owner','--no-same-permissions', '-mxf', + '-', '-C', $self->basedir + ); + my $extractprocess = IO::Async::Process->new( + command => [@extractcommand], + stdin => { via => 'pipe_write' }, + stderr => { into => \$extracterror }, + on_finish => sub { + my ($self, $exitcode) = @_; + my $status = ($exitcode >> 8); + + if ($status) { + my $message = "Non-zero status $status from @extractcommand"; + $message .= COLON . NEWLINE . $extracterror + if length $extracterror; + $extractor->fail($message); + return; + } + + $extractor->done("Done with @extractcommand"); + return; + }); + + # create index of control.tar.gz + my $index; + my $indexerror; + my $indexer = $loop->new_future; + my @indexcommand = ( + 'tar', '--list','--verbose','--utc','--full-time','--quoting-style=c', + '--file', '-' + ); + my $indexprocess = IO::Async::Process->new( + command => [@indexcommand], + stdin => { via => 'pipe_write' }, + stdout => { into => \$index }, + stderr => { into => \$indexerror }, + on_finish => sub { + my ($self, $exitcode) = @_; + my $status = ($exitcode >> 8); + + if ($status) { + my $message = "Non-zero status $status from @indexcommand"; + $message .= COLON . NEWLINE . $indexerror + if length $indexerror; + $indexer->fail($message); + return; + } + + $indexer->done("Done with @indexcommand"); + return; + }); + + $extractprocess->stdin->configure(write_len => READ_SIZE); + $indexprocess->stdin->configure(write_len => READ_SIZE); + + $debprocess->stdout->configure( + read_len => READ_SIZE, + on_read => sub { + my ($stream, $buffref, $eof) = @_; + + if (length $$buffref) { + $extractprocess->stdin->write($$buffref); + $indexprocess->stdin->write($$buffref); + + $$buffref = EMPTY; + } + + if ($eof) { + $extractprocess->stdin->close_when_empty; + $indexprocess->stdin->close_when_empty; + } + + return 0; + }, + ); + + $loop->add($debprocess); + $loop->add($indexprocess); + $loop->add($extractprocess); + + my $composite = Future->needs_all($dpkgdeb, $extractor, $indexer); + + # awaits, and dies on failure with message from failed constituent + $composite->get; + + # not recording dpkg-deb errors anywhere + path($controlerrorspath)->append($extracterror) + if length $extracterror; + path($indexerrorspath)->append($indexerror) + if length $indexerror; + + my @lines = split(/\n/, $index); + + my %all; + for my $line (@lines) { + + my $entry = Lintian::Index::Item->new; + $entry->init_from_tar_output($line); + + $all{$entry->name} = $entry; + } + + $self->catalog(\%all); - path("$processable_dir/control-index-errors")->spew_utf8($index_errors) - if length $index_errors; + # fix permissions + safe_qx('chmod', '-R', 'u+rX,o-w', $self->basedir); return; } diff -Nru lintian-2.93.0/lib/Lintian/Index/FileInfo.pm lintian-2.89.0ubuntu1/lib/Lintian/Index/FileInfo.pm --- lintian-2.93.0/lib/Lintian/Index/FileInfo.pm 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/lib/Lintian/Index/FileInfo.pm 2020-08-10 09:59:45.000000000 +0000 @@ -23,11 +23,19 @@ use autodie; use Cwd; -use IPC::Run3; +use IO::Async::Loop; +use IO::Async::Process; +use IO::Async::Routine; +use Path::Tiny; +use Try::Tiny; + +use Lintian::Util qw(drop_relative_prefix); use constant EMPTY => q{}; use constant SPACE => q{ }; use constant COMMA => q{,}; +use constant COLON => q{:}; +use constant NEWLINE => qq{\n}; use constant NULL => qq{\0}; use Moo::Role; @@ -50,6 +58,56 @@ =over 4 +=item check_magic + +=cut + +sub check_magic { + my ($path, $type) = @_; + + # the file program is regularly wrong here; determine type properly + return ($path, $type) + unless $path =~ m/\.gz$/ + && -f $path + && !-l $path + && $type !~ m/compressed/; + + open(my $fd, '<', $path) + or die "Cannot open $path"; + + my $size = sysread($fd, my $buffer, 1024); + + close($fd) + or warn "Cannot close $path"; + + # need to read at least 9 bytes + return ($path, $type) + unless $size >= 9; + + # translation of the unpack + # nn nn , NN NN NN NN, nn nn, cc - bytes read + # $magic, __ __ __ __, __ __, $comp - variables + my ($magic, undef, undef, $compression) = unpack('nNnc', $buffer); + + my $text = EMPTY; + + # gzip file magic + if ($magic == 0x1f8b){ + + $text = 'gzip compressed data'; + + # 2 for max compression; RFC1952 suggests this is a + # flag and not a value, hence bit operation + $text .= COMMA . SPACE . 'max compression' + if $compression & 2; + } + + $type .= COMMA . SPACE . $text + if $text; + + return ($path, $type); +} + =item add_fileinfo =cut @@ -60,27 +118,42 @@ my $savedir = getcwd; chdir($self->basedir); - my @files = grep { $_->is_file } $self->sorted_list; - - my $input = EMPTY; - $input .= $_->name . NULL for @files; + my $loop = IO::Async::Loop->new; - my $stdout; - - my @command = ( + my @generatecommand = ( 'xargs', '--null','--no-run-if-empty', 'file', '--no-pad', '--print0', '--print0', '--' ); + my $generatedone = $loop->new_future; + + my $output; + my $generate = IO::Async::Process->new( + command => [@generatecommand], + stdin => { via => 'pipe_write' }, + stdout => { into => \$output }, + on_finish => sub { + # ignore failures; file returns non-zero on parse errors + # output then contains "ERROR" messages but is still usable + + $generatedone->done('Done with @generatecommand'); + return; + }); - # ignore failures; file returns non-zero on parse errors - # output then contains "ERROR" messages but is still usable - run3(\@command, \$input, \$stdout); + $loop->add($generate); + + # get the regular files in the index + my @files = grep { $_->is_file } $self->sorted_list; + + $generate->stdin->write($_->name . NULL) for @files; + + $generate->stdin->close_when_empty; + $generatedone->get; my %fileinfo; - $stdout =~ s/\0$//; + $output =~ s/\0$//; - my @lines = split(/\0/, $stdout, -1); + my @lines = split(/\0/, $output, -1); die 'Did not get an even number lines from file command.' unless @lines % 2 == 0; @@ -89,52 +162,21 @@ my $type = shift @lines; - die "syntax error in file-info output: '$path' '$type'" - unless length $path && length $type; + unless(length $path && length $type) { - # drop relative prefix, if present - $path =~ s{^\./}{}; + warn "syntax error in file-info output: '$path' '$type'"; + next; + } - $fileinfo{$path} = $type; - } + ($path, $type) = check_magic($path, $type); - $_->file_info($fileinfo{$_->name}) for @files; - - # some files need to be corrected - my @probably_compressed - = grep { $_->name =~ /\.gz$/i && $_->file_info !~ /compressed/ } @files; - - for my $file (@probably_compressed) { - - my $buffer = $file->magic(9); - next - unless length $buffer; - - # translation of the unpack - # nn nn , NN NN NN NN, nn nn, cc - bytes read - # $magic, __ __ __ __, __ __, $comp - variables - my ($magic, undef, undef, $compression) = unpack('nNnc', $buffer); - - # gzip file magic - next - unless $magic == 0x1f8b; - - my $text = 'gzip compressed data'; - - # 2 for max compression; RFC1952 suggests this is a - # flag and not a value, hence bit operation - $text .= COMMA . SPACE . 'max compression' - if $compression & 2; + # remove relative prefix, if present + $path = drop_relative_prefix($path); - my $new_type = $file->file_info . COMMA . SPACE . $text; - $file->file_info($new_type); + $fileinfo{$path} = $type; } - # some TFMs are categorized as gzip, see Bug#963589 - my @not_gzip - = grep { $_->name =~ /\.tfm$/i && $_->file_info =~ /gzip compressed data/ } - @files; - $_->file_info('data') for @not_gzip; + $_->file_info($fileinfo{$_->name}) for @files; chdir($savedir); diff -Nru lintian-2.93.0/lib/Lintian/Index/Installed.pm lintian-2.89.0ubuntu1/lib/Lintian/Index/Installed.pm --- lintian-2.93.0/lib/Lintian/Index/Installed.pm 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/lib/Lintian/Index/Installed.pm 2020-08-10 09:59:45.000000000 +0000 @@ -25,8 +25,26 @@ use utf8; use autodie; +use IO::Async::Loop; +use IO::Async::Process; use Path::Tiny; +use Lintian::Index::Item; +use Lintian::IO::Async qw(safe_qx); + +# Read up to 40kB at the time. This happens to be 4096 "tar records" +# (with a block-size of 512 and a block factor of 20, which appears to +# be the default). When we do full reads and writes of READ_SIZE (the +# OS willing), the receiving end will never be with an incomplete +# record. +use constant READ_SIZE => 4096 * 1024 * 10; + +use constant EMPTY => q{}; +use constant SPACE => q{ }; +use constant COLON => q{:}; +use constant SLASH => q{/}; +use constant NEWLINE => qq{\n}; + use Moo; use namespace::clean; @@ -64,23 +82,24 @@ =item collect +=item unpack + =cut sub collect { - my ($self, $processable_dir) = @_; + my ($self, $groupdir) = @_; # binary packages are anchored to the system root # allow absolute paths and symbolic links $self->anchored(1); + my $basedir = path($groupdir)->child('unpacked')->stringify; + $self->basedir($basedir); - my @command = (qw(dpkg-deb --fsys-tarfile), "$processable_dir/deb"); - my ($extract_errors, $index_errors) - = $self->create_from_piped_tar(\@command); - + $self->unpack($groupdir); $self->load; $self->add_md5sums; - $self->add_ar; + $self->add_ar($groupdir); $self->add_fileinfo; $self->add_scripts; @@ -88,11 +107,208 @@ $self->add_strings; $self->add_java; - path("$processable_dir/unpacked-errors")->spew_utf8($extract_errors) - if length $extract_errors; + return; +} + +sub unpack { + my ($self, $groupdir) = @_; + + path($self->basedir)->remove_tree + if -d $self->basedir; + + for my $file (qw(index-errors unpacked-errors)) { + unlink("$groupdir/$file") + if -e "$groupdir/$file"; + } + + mkdir($self->basedir, 0777); + + my $loop = IO::Async::Loop->new; + + # get system tarball from deb + my $deberror; + my $dpkgdeb = $loop->new_future; + my $debprocess = IO::Async::Process->new( + command => ['dpkg-deb', '--fsys-tarfile', "$groupdir/deb"], + stdout => { via => 'pipe_read' }, + stderr => { into => \$deberror }, + on_finish => sub { + my ($self, $exitcode) = @_; + my $status = ($exitcode >> 8); + + if ($status) { + my $message + = "Non-zero status $status from dpkg-deb for control"; + $message .= COLON . NEWLINE . $deberror + if length $deberror; + $dpkgdeb->fail($message); + return; + } + + $dpkgdeb->done('Done with dpkg-deb'); + return; + }); + + # extract the tarball's contents + my $extracterror; + my $extractor = $loop->new_future; + my $extractprocess = IO::Async::Process->new( + command => [ + 'tar', '--no-same-owner', '--no-same-permissions', + '-mxf','-', '-C', $self->basedir + ], + stdin => { via => 'pipe_write' }, + stderr => { into => \$extracterror }, + on_finish => sub { + my ($self, $exitcode) = @_; + my $status = ($exitcode >> 8); + + if ($status) { + my $message = "Non-zero status $status from extract tar"; + $message .= COLON . NEWLINE . $extracterror + if length $extracterror; + $extractor->fail($message); + return; + } + + $extractor->done('Done with extract tar'); + return; + }); + + my @tar_options= ( + '--list', '--verbose', + '--utc', '--full-time', + '--quoting-style=c','--file' + ); + + # create index (named-owner) + my $named; + my $namederror; + my $namedindexer = $loop->new_future; + my $namedindexprocess = IO::Async::Process->new( + command => ['tar', @tar_options, '-'], + stdin => { via => 'pipe_write' }, + stdout => { into => \$named }, + stderr => { into => \$namederror }, + on_finish => sub { + my ($self, $exitcode) = @_; + my $status = ($exitcode >> 8); + + if ($status) { + my $message = "Non-zero status $status from index tar"; + $message .= COLON . NEWLINE . $namederror + if length $namederror; + $namedindexer->fail($message); + return; + } + + $namedindexer->done('Done with named index tar'); + return; + }); + + # create index (numeric-owner) + my $numeric; + my $numericerror; + my $numericindexer = $loop->new_future; + my $numericindexprocess = IO::Async::Process->new( + command =>['tar', '--numeric-owner', @tar_options, '-'], + stdin => { via => 'pipe_write' }, + stdout => { into => \$numeric }, + stderr => { into => \$numericerror }, + on_finish => sub { + my ($self, $exitcode) = @_; + my $status = ($exitcode >> 8); + + if ($status) { + my $message = "Non-zero status $status from index tar"; + $message .= COLON . NEWLINE . $numericerror + if length $numericerror; + $numericindexer->fail($message); + return; + } + + $numericindexer->done('Done with tar'); + return; + }); + + $extractprocess->stdin->configure(write_len => READ_SIZE,); + $namedindexprocess->stdin->configure(write_len => READ_SIZE,); + $numericindexprocess->stdin->configure(write_len => READ_SIZE,); + + $debprocess->stdout->configure( + read_len => READ_SIZE, + on_read => sub { + my ($stream, $buffref, $eof) = @_; + + if (length $$buffref) { + $extractprocess->stdin->write($$buffref); + $namedindexprocess->stdin->write($$buffref); + $numericindexprocess->stdin->write($$buffref); + + $$buffref = EMPTY; + } + + if ($eof) { + $extractprocess->stdin->close_when_empty; + $namedindexprocess->stdin->close_when_empty; + $numericindexprocess->stdin->close_when_empty; + } + + return 0; + }, + ); + + $loop->add($debprocess); + $loop->add($extractprocess); + $loop->add($namedindexprocess); + $loop->add($numericindexprocess); + + my $composite + = Future->needs_all($dpkgdeb, $extractor, $namedindexer,$numericindexer); + + # awaits, and dies on failure with message from failed constituent + $composite->get; + + path("$groupdir/unpacked-errors")->append($deberror // EMPTY); + path("$groupdir/unpacked-errors")->append($extracterror // EMPTY); + path("$groupdir/index-errors")->append($namederror // EMPTY); + + my @named_owner = split(/\n/, $named); + my @numeric_owner = split(/\n/, $numeric); + + my %all; + for my $line (@named_owner) { + + my $entry = Lintian::Index::Item->new; + $entry->init_from_tar_output($line); + + $all{$entry->name} = $entry; + } + + # get numerical owners from second list + for my $line (@numeric_owner) { + + my $entry = Lintian::Index::Item->new; + $entry->init_from_tar_output($line); + + die 'Numerical index lists extra files for file name '. $entry->name + unless exists $all{$entry->name}; + + # copy numerical uid and gid + $all{$entry->name}->uid($entry->owner); + $all{$entry->name}->gid($entry->group); + } + + $self->catalog(\%all); + + # remove error files if empty + unlink("$groupdir/index-errors") + if -z "$groupdir/index-errors"; + unlink("$groupdir/unpacked-errors") + if -z "$groupdir/unpacked-errors"; - path("$processable_dir/index-errors")->spew_utf8($index_errors) - if length $index_errors; + # fix permissions + safe_qx('chmod', '-R', 'u+rwX,go-w', $self->basedir); return; } diff -Nru lintian-2.93.0/lib/Lintian/Index/Item.pm lintian-2.89.0ubuntu1/lib/Lintian/Index/Item.pm --- lintian-2.93.0/lib/Lintian/Index/Item.pm 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/lib/Lintian/Index/Item.pm 2020-08-10 09:59:45.000000000 +0000 @@ -1124,10 +1124,6 @@ coerce => sub { my ($text) = @_; return ($text // EMPTY); }, default => EMPTY ); -has ar_info => ( - is => 'rw', - coerce => sub { my ($hashref) = @_; return ($hashref // {}); }, - default => sub { {} }); has control => ( is => 'rw', coerce => sub { my ($hashref) = @_; return ($hashref // {}); }, diff -Nru lintian-2.93.0/lib/Lintian/Index/Java.pm lintian-2.89.0ubuntu1/lib/Lintian/Index/Java.pm --- lintian-2.93.0/lib/Lintian/Index/Java.pm 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/lib/Lintian/Index/Java.pm 2020-08-10 09:59:45.000000000 +0000 @@ -63,23 +63,25 @@ my @files = grep { $_->is_file } $self->sorted_list; - # Wheezy's version of file calls "jar files" for "Zip archive". - # Newer versions seem to call them "Java Jar file". - # Jessie also introduced "Java archive data (JAR)"... - my @java_files = grep { - $_->file_info=~ / - Java [ ] (?:Jar [ ] file|archive [ ] data) - | Zip [ ] archive - | JAR /x; - } @files; - my @lines; - for my $file (@java_files) { + foreach my $file (@files) { + + # Wheezy's version of file calls "jar files" for "Zip archive". + # Newer versions seem to call them "Java Jar file". + # Jessie also introduced "Java archive data (JAR)"... + next + unless $file->file_info=~ m/ + Java [ ] (?:Jar [ ] file|archive [ ] data) + | Zip [ ] archive + | JAR /x; push(@lines, parse_jar($file->name)) if $file->name =~ m#\S+\.jar$#i; } + return + unless @lines; + my $file; my $file_list; my $manifest = 0; @@ -115,7 +117,7 @@ } } - $_->java_info($java_info{$_->name}) for @java_files; + $_->java_info($java_info{$_->name}) for @files; chdir($savedir); diff -Nru lintian-2.93.0/lib/Lintian/Index/Md5sums.pm lintian-2.89.0ubuntu1/lib/Lintian/Index/Md5sums.pm --- lintian-2.93.0/lib/Lintian/Index/Md5sums.pm 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/lib/Lintian/Index/Md5sums.pm 2020-08-10 09:59:45.000000000 +0000 @@ -23,11 +23,18 @@ use autodie; use Cwd; -use IPC::Run3; +use IO::Async::Loop; +use IO::Async::Process; +use Path::Tiny; -use Lintian::Util qw(read_md5sums); +use Lintian::IO::Async qw(safe_qx); +use Lintian::Util qw(drop_relative_prefix read_md5sums); use constant EMPTY => q{}; +use constant SPACE => q{ }; +use constant COLON => q{:}; +use constant BACKSLASH => q{\\}; +use constant NEWLINE => qq{\n}; use constant NULL => qq{\0}; use Moo::Role; @@ -60,25 +67,48 @@ my $savedir = getcwd; chdir($self->basedir); - # get the regular files in the index - my @files = grep { $_->is_file } $self->sorted_list; - - my $input = EMPTY; - $input .= $_->name . NULL for @files; + my $loop = IO::Async::Loop->new; + my $future = $loop->new_future; + my @command= ('xargs', '--null', '--no-run-if-empty', 'md5sum', '--'); my $stdout; my $errors; - my @command = ('xargs', '--null', '--no-run-if-empty', 'md5sum', '--'); - run3(\@command, \$input, \$stdout, \$errors); + my $calculate = IO::Async::Process->new( + command => [@command], + stdin => { via => 'pipe_write' }, + stdout => { into => \$stdout }, + stderr => { into => \$errors }, + on_finish => sub { + my ($self, $exitcode) = @_; + my $status = ($exitcode >> 8); + + if ($status) { + my $message = "Command @command exited with status $status"; + $message .= COLON . NEWLINE . $errors + if length $errors; + $future->fail($message); + return; + } + + $future->done('Done with @command'); + return; + }); + + $loop->add($calculate); + + # get the regular files in the index + my @files = grep { $_->is_file } $self->sorted_list; + + # pipe file names to xargs process + $calculate->stdin->write($_->name . NULL) for @files; - my $status = ($? >> 8); - die "Cannot run @command: $errors\n" - if $status; + $calculate->stdin->close_when_empty; + $future->get; my ($md5sums, undef) = read_md5sums($stdout); - $_->md5sum($md5sums->{$_->name}) for @files; + $_->md5sum($md5sums->{$_->name})for @files; chdir($savedir); diff -Nru lintian-2.93.0/lib/Lintian/Index/Objdump.pm lintian-2.89.0ubuntu1/lib/Lintian/Index/Objdump.pm --- lintian-2.93.0/lib/Lintian/Index/Objdump.pm 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/lib/Lintian/Index/Objdump.pm 2020-08-10 09:59:45.000000000 +0000 @@ -25,7 +25,7 @@ use Cwd; use Path::Tiny; -use Lintian::IPC::Run3 qw(safe_qx); +use Lintian::IO::Async qw(safe_qx); use Lintian::Util qw(locate_helper_tool); use constant EMPTY => q{}; diff -Nru lintian-2.93.0/lib/Lintian/Index/Orig.pm lintian-2.89.0ubuntu1/lib/Lintian/Index/Orig.pm --- lintian-2.93.0/lib/Lintian/Index/Orig.pm 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/lib/Lintian/Index/Orig.pm 2020-08-10 09:59:45.000000000 +0000 @@ -25,12 +25,21 @@ use utf8; use autodie; +use Carp; +use Cwd(); +use IO::Async::Loop; +use IO::Async::Process; use List::MoreUtils qw(uniq); use Path::Tiny; +use Lintian::Deb822::Parser qw(read_dpkg_control); +use Lintian::Index::Item; + use constant EMPTY => q{}; use constant SPACE => q{ }; +use constant COLON => q{:}; use constant SLASH => q{/}; +use constant NEWLINE => qq{\n}; use Moo; use namespace::clean; @@ -67,50 +76,153 @@ =cut sub collect { - my ($self, $processable_dir, $components) = @_; + my ($self, $groupdir) = @_; # source packages can be unpacked anywhere; no anchored roots $self->allow_empty(1); - $self->create($processable_dir, $components); + $self->create($groupdir); $self->load; return; } -my %DECOMPRESS_COMMAND = ( - 'gz' => 'gzip --decompress --stdout', - 'bz2' => 'bzip2 --decompress --stdout', - 'xz' => 'xz --decompress --stdout', -); - sub create { - my ($self, $processable_dir, $components) = @_; + my ($self, $groupdir) = @_; + + my $dsclink = "$groupdir/dsc"; + my $dscpath = Cwd::realpath($dsclink); + die "Cannot resolve 'dsc' link: $dsclink" + unless $dscpath; + die "The 'dsc' link does not point to a file: $dscpath" + unless -e $dscpath; + + # determine source and version; handles missing fields + + my @paragraphs; + @paragraphs = read_dpkg_control($dscpath) + or croak $dscpath . ' is not valid dsc file'; + my $dinfo = $paragraphs[0]; + + my $name = $dinfo->{Source} // EMPTY; + my $version = $dinfo->{Version} // EMPTY; + my $architecture = 'source'; + + # it is its own source package + my $source = $name; + my $source_version = $version; + + croak $dscpath . ' is missing Source field' + unless length $name; + + # Version handling is based on Dpkg::Version::parseversion. + my $noepoch = $source_version; + if ($noepoch =~ /:/) { + $noepoch =~ s/^(?:\d+):(.+)/$1/ + or die "Bad version number '$noepoch'"; + } + + my $baserev = $source . '_' . $noepoch; + + # strip debian revision + $noepoch =~ s/(.+)-(?:.*)$/$1/; + my $base = $source . '_' . $noepoch; + + my @files = split(/\n/, $dinfo->{Files} // EMPTY); + + my %components; + for my $line (@files) { + + # strip leading whitespace + $line =~ s/^\s*//; + + next + unless length $line; + + # get file name + my (undef, undef, $name) = split(/\s+/, $line); + + next + unless length $name; + + # skip if files in subdirs + next + if $name =~ m{/}; + + # Look for $pkg_$version.orig(-$comp)?.tar.$ext (non-native) + # or $pkg_$version.tar.$ext (native) + # - This deliberately does not look for the debian packaging + # even when this would be a tarball. + if ($name + =~ /^(?:\Q$base\E\.orig(?:-(.*))?|\Q$baserev\E)\.tar\.(?:gz|bz2|lzma|xz)$/ + ) { + $components{$name} = $1 // EMPTY; + } + } + + die 'Could not find any source components' + unless %components; my %all; - for my $tarball (sort keys %{$components}) { + for my $tarball (sort keys %components) { + + my $component = $components{$tarball}; + + my @tar_options= ( + '--list', '--verbose', + '--utc', '--full-time', + '--quoting-style=c','--file' + ); + + # may not be needed; modern tar recognizes lzma and xz + if ($tarball =~ /\.(lzma|xz)\z/) { + unshift @tar_options, "--$1"; + } + + my @tar = ('tar', @tar_options, "$groupdir/$tarball"); + + my $loop = IO::Async::Loop->new; + my $future = $loop->new_future; + my $stdout; + my $stderr; + + my $process = IO::Async::Process->new( + command => [@tar], + stdout => { into => \$stdout }, + stderr => { into => \$stderr }, + on_finish => sub { + my ($self, $exitcode) = @_; + my $status = ($exitcode >> 8); + + path("$groupdir/orig-index-errors")->append($stderr // EMPTY); + + if ($status) { + my $message + = "Non-zero status $status from tar for $tarball"; + $message .= COLON . NEWLINE . $stderr + if length $stderr; + $future->fail($message); + return; + } - my $component = $components->{$tarball}; + $future->done("Done with tar for $tarball"); + return; + }); - my ($extension) = ($tarball =~ /\.([^.]+)$/); - die "Source component $tarball has no file exension\n" - unless length $extension; + $loop->add($process); - my $decompress = $DECOMPRESS_COMMAND{lc $extension}; - die "Don't know how to decompress $tarball" - unless $decompress; + $future->get; - my @command = (split(SPACE, $decompress), "$processable_dir/$tarball"); + my @lines = split(/\n/, $stdout); - my ($extract_errors, $index_errors) - = $self->create_from_piped_tar(\@command, $component); + my %single; + for my $line (@lines) { - path("$processable_dir/orig-index-errors")->append($index_errors) - if length $index_errors; + my $entry = Lintian::Index::Item->new; + $entry->init_from_tar_output($line); - # produce composite index for multiple components - my %single = %{$self->catalog}; - $self->catalog({}); + $single{$entry->name} = $entry; + } # remove base directory from output delete $single{''} diff -Nru lintian-2.93.0/lib/Lintian/Index/Patched.pm lintian-2.89.0ubuntu1/lib/Lintian/Index/Patched.pm --- lintian-2.93.0/lib/Lintian/Index/Patched.pm 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/lib/Lintian/Index/Patched.pm 2020-08-10 09:59:45.000000000 +0000 @@ -26,13 +26,22 @@ use autodie; use Cwd; -use IPC::Run3; +use IO::Async::Loop; +use IO::Async::Process; use Path::Tiny; use Lintian::Index::Item; -use Lintian::IPC::Run3 qw(safe_qx); +use Lintian::IO::Async qw(safe_qx); + +# Read up to 40kB at the time. This happens to be 4096 "tar records" +# (with a block-size of 512 and a block factor of 20, which appears to +# be the default). When we do full reads and writes of READ_SIZE (the +# OS willing), the receiving end will never be with an incomplete +# record. +use constant READ_SIZE => 4096 * 1024 * 10; use constant EMPTY => q{}; +use constant SPACE => q{ }; use constant COLON => q{:}; use constant SLASH => q{/}; use constant NEWLINE => qq{\n}; @@ -70,14 +79,18 @@ =item collect +=item unpack + =cut sub collect { - my ($self, $processable_dir) = @_; + my ($self, $groupdir) = @_; # source packages can be unpacked anywhere; no anchored roots + my $basedir = path($groupdir)->child('unpacked')->stringify; + $self->basedir($basedir); - $self->create($processable_dir); + $self->unpack($groupdir); $self->load; $self->add_md5sums; @@ -87,46 +100,60 @@ return; } -=item create - -=cut - -sub create { - my ($self, $processable_dir) = @_; +sub unpack { + my ($self, $groupdir) = @_; my $savedir = getcwd; path($self->basedir)->remove_tree if -d $self->basedir; + for my $file (qw(index-errors unpacked-errors)) { + unlink("$groupdir/$file") if -e "$groupdir/$file"; + } + print "N: Using dpkg-source to unpack\n" if $ENV{'LINTIAN_DEBUG'}; my $saved_umask = umask; umask 0000; - my @unpack_command = ( - qw(dpkg-source -q --no-check --extract), - "$processable_dir/dsc", $self->basedir - ); - - # ignore STDOUT; older versions are not completely quiet with -q - my $unpack_error; - - run3(\@unpack_command, undef, undef, \$unpack_error); - - my $status = ($? >> 8); - if ($status) { - my $message = "Non-zero status $status from @unpack_command"; - $message .= COLON . NEWLINE . $unpack_error - if length $unpack_error; + # Ignore STDOUT of the child process because older versions of + # dpkg-source print things out even with -q. + my $loop = IO::Async::Loop->new; + my $future = $loop->new_future; + my $dpkgerror; + + my $process = IO::Async::Process->new( + command =>[ + 'dpkg-source', '-q','--no-check', '-x', + "$groupdir/dsc", $self->basedir + ], + stderr => { into => \$dpkgerror }, + on_finish => sub { + my ($self, $exitcode) = @_; + my $status = ($exitcode >> 8); + + if ($status) { + my $message = "Non-zero status $status from dpkg-source"; + $message .= COLON . NEWLINE . $dpkgerror + if length $dpkgerror; + $future->fail($message); + return; + } + + $future->done('Done with dpkg-deb'); + return; + }); - die $message; - } + $loop->add($process); + + # awaits, and dies with message on failure + $future->get; umask $saved_umask; - path("$processable_dir/unpacked-errors")->append($unpack_error // EMPTY); + path("$groupdir/unpacked-errors")->append($dpkgerror // EMPTY); # chdir for index_src chdir($self->basedir); @@ -190,6 +217,9 @@ # fix permissions safe_qx('chmod', '-R', 'u+rwX,o+rX,o-w', $self->basedir); + # remove error file if empty + unlink("$groupdir/unpacked-errors") if -z "$groupdir/unpacked-errors"; + chdir($savedir); return; diff -Nru lintian-2.93.0/lib/Lintian/Index/Strings.pm lintian-2.89.0ubuntu1/lib/Lintian/Index/Strings.pm --- lintian-2.93.0/lib/Lintian/Index/Strings.pm 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/lib/Lintian/Index/Strings.pm 2020-08-10 09:59:45.000000000 +0000 @@ -24,7 +24,7 @@ use Path::Tiny; -use Lintian::IPC::Run3 qw(safe_qx); +use Lintian::IO::Async qw(safe_qx); use constant DOT => q{.}; use constant GZ => q{gz}; @@ -57,7 +57,7 @@ my ($self) = @_; my @files = grep { $_->is_file } $self->sorted_list; - for my $file (@files) { + foreach my $file (@files) { next if $file->name =~ m,^usr/lib/debug/,; diff -Nru lintian-2.93.0/lib/Lintian/Index.pm lintian-2.89.0ubuntu1/lib/Lintian/Index.pm --- lintian-2.93.0/lib/Lintian/Index.pm 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/lib/Lintian/Index.pm 2020-08-10 09:59:45.000000000 +0000 @@ -27,9 +27,6 @@ use Path::Tiny; use Lintian::Index::Item; -use Lintian::IO::Select qw(unpack_and_index_piped_tar); -use Lintian::IPC::Run3 qw(safe_qx); - use Lintian::Util qw(perm2oct); use constant EMPTY => q{}; @@ -87,22 +84,7 @@ has catalog => (is => 'rw', default => sub { {} }); has saved_sorted_list => (is => 'rw', default => sub { [] }); - -has basedir => ( - is => 'rw', - trigger => sub { - my ($self, $folder) = @_; - - return - unless length $folder; - - # create directory - path($folder)->mkpath({ chmod => 0777 }) - unless -e $folder; - }, - default => EMPTY -); - +has basedir => (is => 'rw', default => EMPTY); has anchored => (is => 'rw', default => 0); has allow_empty => (is => 'rw', default => 0); @@ -167,58 +149,6 @@ return $self->lookup->resolve_path($name); } -=item create_from_piped_tar - -=cut - -sub create_from_piped_tar { - my ($self, $command, $subfolder) = @_; - - my $extract_dir = $self->basedir; - - if (length $subfolder) { - $extract_dir .= "/$subfolder"; - path($extract_dir)->mkpath({ chmod => 0777 }); - } - - my ($named, $numeric, $extract_errors, $index_errors) - = unpack_and_index_piped_tar($command, $extract_dir); - - # fix permissions - safe_qx('chmod', '-R', 'u+rwX,go-w', $extract_dir); - - my @named_owner = split(/\n/, $named); - my @numeric_owner = split(/\n/, $numeric); - - my %catalog; - - for my $line (@named_owner) { - - my $entry = Lintian::Index::Item->new; - $entry->init_from_tar_output($line); - - $catalog{$entry->name} = $entry; - } - - # get numerical owners from second list - for my $line (@numeric_owner) { - - my $entry = Lintian::Index::Item->new; - $entry->init_from_tar_output($line); - - die 'Numerical index lists extra files for file name '. $entry->name - unless exists $catalog{$entry->name}; - - # keep numerical uid and gid - $catalog{$entry->name}->uid($entry->owner); - $catalog{$entry->name}->gid($entry->group); - } - - $self->catalog(\%catalog); - - return ($extract_errors, $index_errors); -} - =item load =cut diff -Nru lintian-2.93.0/lib/Lintian/IO/Async.pm lintian-2.89.0ubuntu1/lib/Lintian/IO/Async.pm --- lintian-2.93.0/lib/Lintian/IO/Async.pm 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/lib/Lintian/IO/Async.pm 2020-08-10 09:59:45.000000000 +0000 @@ -36,16 +36,13 @@ @EXPORT_OK = qw( get_deb_info safe_qx - unpack_and_index_piped_tar ); } use Carp qw(croak); use IO::Async::Loop; -use IO::Async::Process; use Lintian::Deb822::File; -use Lintian::Index::Item; # read up to 40kB at a time. this happens to be 4096 "tar records" # (with a block-size of 512 and a block factor of 20, which appear to @@ -221,162 +218,6 @@ return $sections[0]; } -=item unpack_and_index_piped_tar - -=cut - -sub unpack_and_index_piped_tar { - my ($command, $basedir) = @_; - - my $loop = IO::Async::Loop->new; - - # get system tarball from deb - my $deberror; - my $dpkgdeb = $loop->new_future; - my $debprocess = IO::Async::Process->new( - command => $command, - stdout => { via => 'pipe_read' }, - stderr => { into => \$deberror }, - on_finish => sub { - my ($self, $exitcode) = @_; - my $status = ($exitcode >> 8); - - if ($status) { - my $message - = "Non-zero status $status from dpkg-deb for control"; - $message .= COLON . NEWLINE . $deberror - if length $deberror; - $dpkgdeb->fail($message); - return; - } - - $dpkgdeb->done('Done with dpkg-deb'); - return; - }); - - # extract the tarball's contents - my $extracterror; - my $extractor = $loop->new_future; - my $extractprocess = IO::Async::Process->new( - command => [ - qw(tar --no-same-owner --no-same-permissions --touch --extract --file - -C), - $basedir - ], - stdin => { via => 'pipe_write' }, - stderr => { into => \$extracterror }, - on_finish => sub { - my ($self, $exitcode) = @_; - my $status = ($exitcode >> 8); - - if ($status) { - my $message = "Non-zero status $status from extract tar"; - $message .= COLON . NEWLINE . $extracterror - if length $extracterror; - $extractor->fail($message); - return; - } - - $extractor->done('Done with extract tar'); - return; - }); - - my @tar_options - = qw(--list --verbose --utc --full-time --quoting-style=c --file -); - - # create index (named-owner) - my $named; - my $namederror; - my $namedindexer = $loop->new_future; - my $namedindexprocess = IO::Async::Process->new( - command => ['tar', @tar_options], - stdin => { via => 'pipe_write' }, - stdout => { into => \$named }, - stderr => { into => \$namederror }, - on_finish => sub { - my ($self, $exitcode) = @_; - my $status = ($exitcode >> 8); - - if ($status) { - my $message = "Non-zero status $status from index tar"; - $message .= COLON . NEWLINE . $namederror - if length $namederror; - $namedindexer->fail($message); - return; - } - - $namedindexer->done('Done with named index tar'); - return; - }); - - # create index (numeric-owner) - my $numeric; - my $numericerror; - my $numericindexer = $loop->new_future; - my $numericindexprocess = IO::Async::Process->new( - command =>['tar', '--numeric-owner', @tar_options], - stdin => { via => 'pipe_write' }, - stdout => { into => \$numeric }, - stderr => { into => \$numericerror }, - on_finish => sub { - my ($self, $exitcode) = @_; - my $status = ($exitcode >> 8); - - if ($status) { - my $message = "Non-zero status $status from index tar"; - $message .= COLON . NEWLINE . $numericerror - if length $numericerror; - $numericindexer->fail($message); - return; - } - - $numericindexer->done('Done with tar'); - return; - }); - - $extractprocess->stdin->configure(write_len => READ_SIZE,); - $namedindexprocess->stdin->configure(write_len => READ_SIZE,); - $numericindexprocess->stdin->configure(write_len => READ_SIZE,); - - $debprocess->stdout->configure( - read_len => READ_SIZE, - on_read => sub { - my ($stream, $buffref, $eof) = @_; - - if (length $$buffref) { - $extractprocess->stdin->write($$buffref); - $namedindexprocess->stdin->write($$buffref); - $numericindexprocess->stdin->write($$buffref); - - $$buffref = EMPTY; - } - - if ($eof) { - $extractprocess->stdin->close_when_empty; - $namedindexprocess->stdin->close_when_empty; - $numericindexprocess->stdin->close_when_empty; - } - - return 0; - }, - ); - - $loop->add($debprocess); - $loop->add($extractprocess); - $loop->add($namedindexprocess); - $loop->add($numericindexprocess); - - my $composite - = Future->needs_all($dpkgdeb, $extractor, $namedindexer,$numericindexer); - - # awaits, and dies on failure with message from failed constituent - $composite->get; - - my $extract_errors = ($deberror // EMPTY) . ($extracterror // EMPTY); - my $index_errors = $namederror; - - return ($named, $numeric, $extract_errors, $index_errors); -} - =back =head1 SEE ALSO diff -Nru lintian-2.93.0/lib/Lintian/IO/Select.pm lintian-2.89.0ubuntu1/lib/Lintian/IO/Select.pm --- lintian-2.93.0/lib/Lintian/IO/Select.pm 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/lib/Lintian/IO/Select.pm 1970-01-01 00:00:00.000000000 +0000 @@ -1,252 +0,0 @@ -# Hey emacs! This is a -*- Perl -*- script! -# -# Lintian::IO::Select -- Perl utility functions for lintian -# -# Copyright © 2020 Felix Lechner -# -# This program is free software; you can redistribute it and/or modify -# it under the terms of the GNU General Public License as published by -# the Free Software Foundation; either version 2 of the License, or -# (at your option) any later version. -# -# This program is distributed in the hope that it will be useful, -# but WITHOUT ANY WARRANTY; without even the implied warranty of -# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the -# GNU General Public License for more details. -# -# You should have received a copy of the GNU General Public License -# along with this program. If not, you can find it on the World Wide -# Web at http://www.gnu.org/copyleft/gpl.html, or write to the Free -# Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, -# MA 02110-1301, USA. - -package Lintian::IO::Select; - -use v5.20; -use warnings; -use utf8; -use autodie; - -use Exporter qw(import); - -our @EXPORT_OK; - -BEGIN { - - @EXPORT_OK = qw( - unpack_and_index_piped_tar - ); -} - -use IPC::Open3; -use IO::Select; -use Symbol; - -# read up to 40kB at a time. this happens to be 4096 "tar records" -# (with a block-size of 512 and a block factor of 20, which appear to -# be the defaults). when we do full reads and writes of READ_SIZE (the -# OS willing), the receiving end will never be with an incomplete -# record. -use constant TAR_RECORD_SIZE => 20 * 512; - -use constant EMPTY => q{}; -use constant COLON => q{:}; -use constant NEWLINE => qq{\n}; - -=head1 NAME - -Lintian::IO::Select - process functions based on IO::Select - -=head1 SYNOPSIS - - use Lintian::IO::Select; - -=head1 DESCRIPTION - -This module contains process functions based on IO::Select. - -=head1 FUNCTIONS - -=over 4 - -=item unpack_and_index_piped_tar - -=cut - -sub unpack_and_index_piped_tar { - my ($command, $basedir) = @_; - - my @pids; - - my $select = IO::Select->new; - - my $produce_stdin; - my $produce_stdout; - my $produce_stderr = gensym; - - my @produce_command = @{$command}; - - my $produce_pid; - eval{ - $produce_pid = open3( - $produce_stdin, $produce_stdout, - $produce_stderr, @produce_command - ); - }; - die $@ if $@; - - close $produce_stdin; - - push(@pids, $produce_pid); - - $select->add($produce_stdout, $produce_stderr); - - my $extract_stdin; - my $extract_stdout; - my $extract_stderr = gensym; - - my @extract_command = ( - qw(tar --no-same-owner --no-same-permissions --touch --extract --file - -C), - $basedir - ); - - my $extract_pid; - eval{ - $extract_pid = open3( - $extract_stdin, $extract_stdout, - $extract_stderr, @extract_command - ); - }; - die $@ if $@; - - push(@pids, $extract_pid); - - $select->add($extract_stdout, $extract_stderr); - - my @index_options - = qw(--list --verbose --utc --full-time --quoting-style=c --file -); - - my $named_stdin; - my $named_stdout; - my $named_stderr = gensym; - - my @named_command = ('tar', @index_options); - - my $named_pid; - eval{ - $named_pid - = open3($named_stdin, $named_stdout, $named_stderr, @named_command); - }; - die $@ if $@; - - push(@pids, $named_pid); - - $select->add($named_stdout, $named_stderr); - - my $numeric_stdin; - my $numeric_stdout; - my $numeric_stderr = gensym; - - my @numeric_command = ('tar', '--numeric-owner', @index_options); - - my $numeric_pid; - eval{ - $numeric_pid = open3( - $numeric_stdin, $numeric_stdout, - $numeric_stderr, @numeric_command - ); - }; - die $@ if $@; - - push(@pids, $numeric_pid); - - $select->add($numeric_stdout, $numeric_stderr); - - my $named = EMPTY; - my $numeric = EMPTY; - - my $produce_errors = EMPTY; - my $extract_errors = EMPTY; - my $named_errors = EMPTY; - - while (my @ready = $select->can_read) { - - for my $handle (@ready) { - - my $buffer; - my $length = sysread($handle, $buffer, 4096 * TAR_RECORD_SIZE); - - die "Error from child: $!\n" - unless defined $length; - - if ($length == 0){ - if ($handle == $produce_stdout) { - close $extract_stdin; - close $named_stdin; - close $numeric_stdin; - } - $select->remove($handle); - next; - } - - if ($handle == $produce_stdout) { - print $extract_stdin $buffer; - print $named_stdin $buffer; - print $numeric_stdin $buffer; - - } elsif ($handle == $named_stdout) { - $named .= $buffer; - - } elsif ($handle == $numeric_stdout) { - $numeric .= $buffer; - - } elsif ($handle == $produce_stderr) { - $produce_errors .= $buffer; - - } elsif ($handle == $extract_stderr) { - $extract_errors .= $buffer; - - } elsif ($handle == $named_stderr) { - $named_errors .= $buffer; - - # } else { - # die "Shouldn't be here\n"; - } - } - } - - close $produce_stdout; - close $produce_stderr; - - close $extract_stdout; - close $extract_stderr; - - close $named_stdout; - close $named_stderr; - - close $numeric_stdout; - close $numeric_stderr; - - waitpid($_, 0) for @pids; - - my $tar_errors = ($produce_errors // EMPTY) . ($extract_errors // EMPTY); - my $index_errors = $named_errors; - - return ($named, $numeric, $tar_errors, $index_errors); -} - -=back - -=head1 SEE ALSO - -lintian(1) - -=cut - -1; - -# Local Variables: -# indent-tabs-mode: nil -# cperl-indent-level: 4 -# End: -# vim: syntax=perl sw=4 sts=4 sr et diff -Nru lintian-2.93.0/lib/Lintian/IPC/Run3.pm lintian-2.89.0ubuntu1/lib/Lintian/IPC/Run3.pm --- lintian-2.93.0/lib/Lintian/IPC/Run3.pm 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/lib/Lintian/IPC/Run3.pm 2020-08-10 09:59:45.000000000 +0000 @@ -34,7 +34,6 @@ BEGIN { @EXPORT_OK = qw( - get_deb_info safe_qx ); } @@ -42,18 +41,7 @@ use Carp qw(croak); use IPC::Run3; -use Lintian::Deb822::File; - -# read up to 40kB at a time. this happens to be 4096 "tar records" -# (with a block-size of 512 and a block factor of 20, which appear to -# be the defaults). when we do full reads and writes of READ_SIZE (the -# OS willing), the receiving end will never be with an incomplete -# record. -use constant TAR_RECORD_SIZE => 20 * 512; - use constant EMPTY => q{}; -use constant COLON => q{:}; -use constant NEWLINE => qq{\n}; =head1 NAME @@ -96,58 +84,6 @@ return $stdout; } -=item get_deb_info(DEBFILE) - -Extracts the control file from DEBFILE and returns it as a hashref. - -DEBFILE must be an ar file containing a "control.tar.gz" member, which -in turn should contain a "control" file. If the "control" file is -empty this will return an empty list. - -Note: the control file is only expected to have a single paragraph and -thus only the first is returned (in the unlikely case that there are -more than one). - -=cut - -sub get_deb_info { - my ($path) = @_; - - # get control.tar.gz; dpkg-deb -f $file is slow; use tar instead - my @dpkg_command = ('dpkg-deb', '--ctrl-tarfile', $path); - - my $dpkg_pid = open(my $from_dpkg, '-|', @dpkg_command) - or die "Cannot run @dpkg_command: $!"; - - # would like to set buffer size to 4096 & TAR_RECORD_SIZE - - # get binary control file - my $stdout; - my $stderr; - my @tar_command = ('tar', '--wildcards', '-xO', '-f', '-', '*control'); - run3(\@tar_command, $from_dpkg, \$stdout, \$stderr); - - my $status = ($? >> 8); - if ($status) { - - my $message= "Non-zero status $status from @tar_command"; - $message .= COLON . NEWLINE . $stderr - if length $stderr; - - die $message; - } - - close $from_dpkg - or warn "close failed for handle from @dpkg_command: $!"; - - waitpid($dpkg_pid, 0); - - my $deb822 = Lintian::Deb822::File->new; - my @sections = $deb822->parse_string($stdout); - - return $sections[0]; -} - =back =head1 SEE ALSO diff -Nru lintian-2.93.0/lib/Lintian/Output/ColonSeparated.pm lintian-2.89.0ubuntu1/lib/Lintian/Output/ColonSeparated.pm --- lintian-2.93.0/lib/Lintian/Output/ColonSeparated.pm 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/lib/Lintian/Output/ColonSeparated.pm 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,254 @@ +# Tags::ColonSeparated -- Perl tags functions for lintian +# $Id: Tags.pm 489 2005-09-17 00:06:30Z djpig $ + +# Copyright © 2005,2008 Frank Lichtenheld +# +# This program is free software; you can redistribute it and/or modify +# it under the terms of the GNU General Public License as published by +# the Free Software Foundation; either version 2 of the License, or +# (at your option) any later version. +# +# This program is distributed in the hope that it will be useful, +# but WITHOUT ANY WARRANTY; without even the implied warranty of +# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the +# GNU General Public License for more details. +# +# You should have received a copy of the GNU General Public License +# along with this program. If not, you can find it on the World Wide +# Web at http://www.gnu.org/copyleft/gpl.html, or write to the Free +# Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, +# MA 02110-1301, USA. + +package Lintian::Output::ColonSeparated; + +use v5.20; +use warnings; +use utf8; + +use constant EMPTY => q{}; +use constant SPACE => q{ }; +use constant COLON => q{:}; +use constant NEWLINE => qq{\n}; + +use Moo; +use namespace::clean; + +with 'Lintian::Output'; + +=head1 NAME + +Lintian::Output::ColonSeparated - colon-separated tag output + +=head1 SYNOPSIS + + use Lintian::Output::ColonSeparated; + +=head1 DESCRIPTION + +Provides colon-separated tag output. + +=head1 INSTANCE METHODS + +=over 4 + +=item issue_tags + +Print all tags passed in array. A separate arguments with processables +is necessary to report in case no tags were found. + +=cut + +my %code_priority = ( + 'E' => 30, + 'W' => 40, + 'I' => 50, + 'P' => 60, + 'X' => 70, + 'C' => 80, + 'O' => 90, +); + +my %type_priority = ( + 'source' => 30, + 'binary' => 40, + 'udeb' => 50, + 'changes' => 60, + 'buildinfo' => 70, +); + +sub issue_tags { + my ($self, $groups) = @_; + + my @processables = map { $_->get_processables } @{$groups // []}; + + my @pending; + for my $processable (@processables) { + + # get tags + my @tags = @{$processable->tags}; + + # associate tags with processable + $_->processable($processable) for @tags; + + # remove circular references + $processable->tags([]); + + push(@pending, @tags); + } + + $self->print_start_pkg($_) for @processables; + + my @sorted = sort { + defined $a->override <=> defined $b->override + || $code_priority{$a->info->code} <=> $code_priority{$b->info->code} + || $a->name cmp $b->name + || $type_priority{$a->processable->type} + <=> $type_priority{$b->processable->type} + || $a->processable->name cmp $b->processable->name + || $a->context cmp $b->context + } @pending; + + $self->print_tag($_) for @sorted; + + return; +} + +=item print_tag + +=cut + +sub print_tag { + my ($self, $tag) = @_; + + my $tag_info = $tag->info; + my $information = $tag->context; + my $override = $tag->override; + my $processable = $tag->processable; + + my $odata = EMPTY; + if ($override) { + $odata = $override->{tag}; + my $context = $override->{context}; + $context =~ s/[^[:print:]]/?/g; + $odata .= SPACE . $context + if length $context; + } + + $self->issuedtags->{$tag_info->name}++; + + $information =~ s/[^[:print:]]/?/g; + + my @args = ( + 'tag', + $tag_info->code, + $tag_info->effective_severity, + ($tag_info->experimental ? 'X' : EMPTY) + . (defined $override ? 'O' : EMPTY), + $processable->name, + $processable->version, + $processable->architecture, + $processable->type, + $tag_info->name, + $information, + $odata, + ); + + my @quoted = map { + s/\\/\\\\/g; + s/\Q:\E/\\:/g; + $_ + } @args; + + my $output = join(COLON, @quoted) . NEWLINE; + print {$self->stdout} $output; + + return; +} + +=item C + +Called before lintian starts to handle each package. The version in +Lintian::Output uses v_msg() for output. Called from Tags::select_pkg(). + +=cut + +sub print_start_pkg { + my ($self, $processable) = @_; + + my $object = 'package'; + $object = 'file' + if $processable->type eq 'changes'; + + $self->v_msg( + $self->delimiter, + 'Processing '. $processable->type. " $object ". $processable->name, + '(version ' + . $processable->version + . ', arch ' + . $processable->architecture . ') ...' + ); + return; +} + +sub _delimiter { + return; +} + +sub _message { + my ($self, @args) = @_; + + foreach (@args) { + $self->_print('message', $_); + } + return; +} + +sub _warning { + my ($self, @args) = @_; + + foreach (@args) { + $self->_print('warning', $_); + } + return; +} + +sub _print { + my ($self, @args) = @_; + + my $output = $self->string(@args); + print {$self->stdout} $output; + return; +} + +=item string + +=cut + +sub string { + my ($self, @args) = @_; + + return join(':', _quote_char(':', @args))."\n"; +} + +sub _quote_char { + my ($char, @items) = @_; + + foreach (@items) { + s/\\/\\\\/g; + s/\Q$char\E/\\$char/g; + } + + return @items; +} + +=back + +=cut + +1; + +# Local Variables: +# indent-tabs-mode: nil +# cperl-indent-level: 4 +# End: +# vim: syntax=perl sw=4 sts=4 sr et diff -Nru lintian-2.93.0/lib/Lintian/Output/EWI.pm lintian-2.89.0ubuntu1/lib/Lintian/Output/EWI.pm --- lintian-2.93.0/lib/Lintian/Output/EWI.pm 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/lib/Lintian/Output/EWI.pm 1970-01-01 00:00:00.000000000 +0000 @@ -1,348 +0,0 @@ -# Copyright © 2008 Frank Lichtenheld -# -# This program is free software; you can redistribute it and/or modify -# it under the terms of the GNU General Public License as published by -# the Free Software Foundation; either version 2 of the License, or -# (at your option) any later version. -# -# This program is distributed in the hope that it will be useful, -# but WITHOUT ANY WARRANTY; without even the implied warranty of -# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the -# GNU General Public License for more details. -# -# You should have received a copy of the GNU General Public License -# along with this program. If not, you can find it on the World Wide -# Web at http://www.gnu.org/copyleft/gpl.html, or write to the Free -# Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, -# MA 02110-1301, USA. - -package Lintian::Output::EWI; - -use v5.20; -use warnings; -use utf8; - -use HTML::HTML5::Entities; -use Term::ANSIColor (); -use Text::Wrap; - -# for tty hyperlinks -use constant OSC_HYPERLINK => qq{\033]8;;}; -use constant OSC_DONE => qq{\033\\}; - -use constant SPACE => q{ }; -use constant COLON => q{:}; -use constant NEWLINE => qq{\n}; - -use Moo; -use namespace::clean; - -with 'Lintian::Output'; - -=head1 NAME - -Lintian::Output::EWI - standard tag output - -=head1 SYNOPSIS - - use Lintian::Output::EWI; - -=head1 DESCRIPTION - -Provides standard tag output. - -=head1 INSTANCE METHODS - -=over 4 - -=item issue_tags - -Print all tags passed in array. A separate arguments with processables -is necessary to report in case no tags were found. - -=cut - -my %code_priority = ( - 'E' => 30, - 'W' => 40, - 'I' => 50, - 'P' => 60, - 'X' => 70, - 'C' => 80, - 'O' => 90, -); - -my %type_priority = ( - 'source' => 30, - 'binary' => 40, - 'udeb' => 50, - 'changes' => 60, - 'buildinfo' => 70, -); - -sub issue_tags { - my ($self, $groups) = @_; - - my @processables = map { $_->get_processables } @{$groups // []}; - - my @pending; - for my $processable (@processables) { - - # get tags - my @tags = @{$processable->tags}; - - # associate tags with processable - $_->processable($processable) for @tags; - - # remove circular references - $processable->tags([]); - - push(@pending, @tags); - } - - my @sorted = sort { - defined $a->override <=> defined $b->override - || $code_priority{$a->info->code} <=> $code_priority{$b->info->code} - || $a->name cmp $b->name - || $type_priority{$a->processable->type} - <=> $type_priority{$b->processable->type} - || $a->processable->name cmp $b->processable->name - || $a->context cmp $b->context - } @pending; - - $self->print_tag($_) for @sorted; - - return; -} - -=item C - -Print a tag. The first two arguments are hash reference with the -information about the package and the tag, $context is the context -information for the tag (if any) as an array reference, and $override -is either undef if the tag is not overridden or a hash with -override info for this tag. - -=cut - -sub print_tag { - my ($self, $tag) = @_; - - my $tag_info = $tag->info; - my $information = $tag->context; - my $override = $tag->override; - my $processable = $tag->processable; - - $information = ' ' . $self->_quote_print($information) - if $information ne ''; - my $code = $tag_info->code; - my $tag_color = ($tag->override ? 'bright_black' : $self->{colors}{$code}); - my $fpkg_info= $self->_format_pkg_info($processable, $tag_info, $override); - my $tag_name = $tag_info->name; - my $limit = $self->tag_display_limit; - my $output; - - # Limit the output so people do not drown in tags. Some tags are - # insanely noisy (hi static-library-has-unneeded-section) - if ($limit) { - my $proc_id = $processable->identifier; - my $emitted_count= $self->proc_id2tag_count->{$proc_id}{$tag_name}++; - return if $emitted_count >= $limit; - my $msg - = ' ... use --no-tag-display-limit to see all (or pipe to a file/program)'; - $information = $self->_quote_print($msg) - if $emitted_count >= $limit-1; - } - - my $text = $tag_name; - $text = Term::ANSIColor::colored($tag_name, $tag_color) - if $self->color; - - if ($self->tty_hyperlinks && $self->color) { - my $target= 'https://lintian.debian.org/tags/' . $tag_name . '.html'; - $output .= $self->osc_hyperlink($text, $target); - } else { - $output .= $text; - } - - if ($override && @{ $override->{comments} }) { - for my $c (@{ $override->{comments} }) { - $self->msg($self->_quote_print($c)); - } - } - - say "$fpkg_info: $output$information"; - - $self->tag_description($tag_info) - if $self->showdescription && !$self->issued_tag($tag_info->name); - - return; -} - -=item C<_quote_print($string)> - -Called to quote a string. By default it will replace all -non-printables with "?". Sub-classes can override it if -they allow non-ascii printables etc. - -=cut - -sub _quote_print { - my ($self, $string) = @_; - $string =~ s/[^[:print:]]/?/g; - return $string; -} - -=item C - -=cut - -sub osc_hyperlink { - my ($self, $text, $target) = @_; - - my $start = OSC_HYPERLINK . $target . OSC_DONE; - my $end = OSC_HYPERLINK . OSC_DONE; - - return $start . $text . $end; -} - -sub _format_pkg_info { - my ($self, $processable, $tag_info, $override) = @_; - my $code = $tag_info->code; - $code = 'X' if $tag_info->experimental; - $code = 'O' if defined $override; - my $type = ''; - $type = SPACE . $processable->type if $processable->type ne 'binary'; - return "$code: " . $processable->name . $type; -} - -=item issuedtags - -Hash containing the names of tags which have been issued. - -=cut - -has issuedtags => (is => 'rw', default => sub { {} }); - -=item C - -Indicate that the named tag has been issued. Returns a boolean value -indicating whether the tag had previously been issued by the object. - -=cut - -sub issued_tag { - my ($self, $tag_name) = @_; - - return $self->issuedtags->{$tag_name}++ ? 1 : 0; -} - -=item tag_description - -=cut - -sub tag_description { - my ($self, $tag_info) = @_; - - my $code = 'N'; - my $description = 'N: Unknown tag.'; - - if (defined $tag_info) { - - $code = $tag_info->code; - - my $plain_text = markdown_to_plain($tag_info->markdown_description); - $description = indent_and_wrap($plain_text, 'N: '); - - chomp $description; - } - - my $output = 'N:' . NEWLINE; - $output .= $code . COLON . SPACE . $tag_info->name . NEWLINE; - $output .= 'N:' . NEWLINE; - $output .= $description . NEWLINE; - $output .= 'N:' . NEWLINE; - - print $output; - - return; -} - -=item indent_and_wrap - -=cut - -sub indent_and_wrap { - my ($text, $indent) = @_; - - my @paragraphs = split(/\n{2,}/, $text); - - my @indented; - for my $paragraph (@paragraphs) { - - if ($paragraph =~ /^\s/) { - - # do not wrap preformatted lines; indent only - my @lines = split(/\n/, $paragraph); - my $indented_paragraph= join(NEWLINE, map { $indent . $_ } @lines); - - push(@indented, $indented_paragraph); - - } else { - # reduce whitespace throughout, including newlines - $paragraph =~ s/\s+/ /g; - - # trim beginning and end of each line - $paragraph =~ s/^\s+|\s+$//mg; - - # do not wrap long words like urls, see #719769 - local $Text::Wrap::huge = 'overflow'; - - my $wrapped_paragraph = wrap($indent, $indent, $paragraph); - - push(@indented, $wrapped_paragraph); - } - } - - my $formatted = join(NEWLINE . $indent . NEWLINE, @indented) . NEWLINE; - - return $formatted; -} - -=item markdown_to_plain - -=cut - -sub markdown_to_plain { - my ($markdown) = @_; - - # use angular brackets for emphasis - $markdown =~ s{|}{<}g; - $markdown =~ s{|}{>}g; - - # drop Markdown hyperlinks - $markdown =~ s{\[([^\]]+)\]\([^\)]+\)}{$1}g; - - # drop all HTML tags except Markdown shorthand <$url> - $markdown =~ s{<(?![a-z]+://)[^>]+>}{}g; - - # drop brackets around Markdown shorthand <$url> - $markdown =~ s{<([a-z]+://[^>]+)>}{$1}g; - - # substitute HTML entities - my $plain = decode_entities($markdown); - - return $plain; -} - -=back - -=cut - -1; - -# Local Variables: -# indent-tabs-mode: nil -# cperl-indent-level: 4 -# End: -# vim: syntax=perl sw=4 sts=4 sr et diff -Nru lintian-2.93.0/lib/Lintian/Output/FullEWI.pm lintian-2.89.0ubuntu1/lib/Lintian/Output/FullEWI.pm --- lintian-2.93.0/lib/Lintian/Output/FullEWI.pm 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/lib/Lintian/Output/FullEWI.pm 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,298 @@ +# Copyright © 2011 Niels Thykier +# +# This program is free software; you can redistribute it and/or modify +# it under the terms of the GNU General Public License as published by +# the Free Software Foundation; either version 2 of the License, or +# (at your option) any later version. +# +# This program is distributed in the hope that it will be useful, +# but WITHOUT ANY WARRANTY; without even the implied warranty of +# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the +# GNU General Public License for more details. +# +# You should have received a copy of the GNU General Public License +# along with this program. If not, you can find it on the World Wide +# Web at http://www.gnu.org/copyleft/gpl.html, or write to the Free +# Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, +# MA 02110-1301, USA. + +package Lintian::Output::FullEWI; + +# The FullEWI always emit *full* package metadata even if it is +# redundant (that is, optional values are always included) when +# emitting tags. +# Other than that, it is identical to the normal output. +# +# When parsing a lintian.log written in format, it is no longer +# ambiguous which package is referred to (even if --verbose is +# not used). +# +# The full format of the emitted tag is: +# +# C: name type (version) [arch]: tag [...] +# +# Note the "[...]" is the context which may or may not be present +# depending on the tag. +# +# Notable cases: +# * binary packages include type classification +# * source packages include an architecture, which is always +# "source". +# * "[arch]" may contain spaces (and generally do for .changes) +# files. +# * "(version)" may contain colon (i.e. epoch versions) + +use v5.20; +use warnings; +use utf8; + +use HTML::Entities; +use Term::ANSIColor (); + +# for tty hyperlinks +use constant OSC_HYPERLINK => qq{\033]8;;}; +use constant OSC_DONE => qq{\033\\}; + +use Moo; +use namespace::clean; + +with 'Lintian::Output'; + +=head1 NAME + +Lintian::Output::FullEWI -- output module + +=head1 SYNOPSIS + + use Lintian::Output::FullEWI; + +=head1 DESCRIPTION + +A parent class specializing in Lintian output. + +=head1 INSTANCE METHODS + +=over 4 + +=item issue_tags + +Print all tags passed in array. A separate arguments with processables +is necessary to report in case no tags were found. + +=cut + +my %code_priority = ( + 'E' => 30, + 'W' => 40, + 'I' => 50, + 'P' => 60, + 'X' => 70, + 'C' => 80, + 'O' => 90, +); + +my %type_priority = ( + 'source' => 30, + 'binary' => 40, + 'udeb' => 50, + 'changes' => 60, + 'buildinfo' => 70, +); + +sub issue_tags { + my ($self, $groups) = @_; + + my @processables = map { $_->get_processables } @{$groups // []}; + + my @pending; + for my $processable (@processables) { + + # get tags + my @tags = @{$processable->tags}; + + # associate tags with processable + $_->processable($processable) for @tags; + + # remove circular references + $processable->tags([]); + + push(@pending, @tags); + } + + $self->print_start_pkg($_) for @processables; + + my @sorted = sort { + defined $a->override <=> defined $b->override + || $code_priority{$a->info->code} <=> $code_priority{$b->info->code} + || $a->name cmp $b->name + || $type_priority{$a->processable->type} + <=> $type_priority{$b->processable->type} + || $a->processable->name cmp $b->processable->name + || $a->context cmp $b->context + } @pending; + + $self->print_tag($_) for @sorted; + + return; +} + +=item C + +Print a tag. The first two arguments are hash reference with the +information about the package and the tag, $context is the context +information for the tag (if any) as an array reference, and $override +is either undef if the tag is not overridden or a hash with +override info for this tag. + +=cut + +sub print_tag { + my ($self, $tag) = @_; + + my $tag_info = $tag->info; + my $information = $tag->context; + my $override = $tag->override; + my $processable = $tag->processable; + + $information = ' ' . $self->_quote_print($information) + if $information ne ''; + my $code = $tag_info->code; + my $tag_color = $self->{colors}{$code}; + my $fpkg_info= $self->_format_pkg_info($processable, $tag_info, $override); + my $tag_name = $tag_info->name; + my $limit = $self->tag_display_limit; + my $output; + + # Limit the output so people do not drown in tags. Some tags are + # insanely noisy (hi static-library-has-unneeded-section) + if ($limit) { + my $proc_id = $processable->identifier; + my $emitted_count + = $self->{'proc_id2tag_count'}{$proc_id}{$tag_name}++; + return if $emitted_count >= $limit; + my $msg + = ' ... use --no-tag-display-limit to see all (or pipe to a file/program)'; + $information = $self->_quote_print($msg) + if $emitted_count >= $limit-1; + } + if ($self->_do_color && $self->color eq 'html') { + my $escaped = encode_entities($tag_name); + $information = encode_entities($information); + $output .= qq($escaped); + + } else { + my $text = $tag_name; + $text = Term::ANSIColor::colored($tag_name, $tag_color) + if $self->_do_color; + + if ($self->tty_hyperlinks) { + my $target + = 'https://lintian.debian.org/tags/' . $tag_name . '.html'; + $output .= $self->osc_hyperlink($text, $target); + } else { + $output .= $text; + } + } + + if ($override && @{ $override->{comments} }) { + foreach my $c (@{ $override->{comments} }) { + $self->msg($self->_quote_print($c)); + } + } + + $self->_print('', $fpkg_info, "$output$information"); + if (not $self->issued_tag($tag_info->name) and $self->showdescription) { + my $description; + if ($self->_do_color && $self->color eq 'html') { + $description = $tag_info->description('html', ' '); + } else { + $description = $tag_info->description('text', ' '); + } + $self->_print('', 'N', ''); + $self->_print('', 'N', split("\n", $description)); + $self->_print('', 'N', ''); + } + return; +} + +=item C + +Called before lintian starts to handle each package. The version in +Lintian::Output uses v_msg() for output. Called from Tags::select_pkg(). + +=cut + +sub print_start_pkg { + my ($self, $processable) = @_; + + my $object = 'package'; + $object = 'file' + if $processable->type eq 'changes'; + + $self->v_msg( + $self->delimiter, + 'Processing '. $processable->type. " $object ". $processable->name, + '(version ' + . $processable->version + . ', arch ' + . $processable->architecture . ') ...' + ); + return; +} + +=item C<_quote_print($string)> + +Called to quote a string. By default it will replace all +non-printables with "?". Sub-classes can override it if +they allow non-ascii printables etc. + +=cut + +sub _quote_print { + my ($self, $string) = @_; + $string =~ s/[^[:print:]]/?/g; + return $string; +} + +# Overridden from Lintian::Output +sub _format_pkg_info { + my ($self, $processable, $tag_info, $override) = @_; + my $code = $tag_info->code; + $code = 'X' if $tag_info->experimental; + $code = 'O' if defined $override; + my $version = $processable->version; + my $arch = ''; + my $type = $processable->type; + $arch = $processable->architecture if $processable->type ne 'source'; + $arch = 'source' unless $arch; + return "$code: " . $processable->name . " $type ($version) [$arch]"; +} + +=item C + +=cut + +sub osc_hyperlink { + my ($self, $text, $target) = @_; + + my $start = OSC_HYPERLINK . $target . OSC_DONE; + my $end = OSC_HYPERLINK . OSC_DONE; + + return $start . $text . $end; +} + +=back + +=head1 SEE ALSO + +lintian(1) + +=cut + +1; + +# Local Variables: +# indent-tabs-mode: nil +# cperl-indent-level: 4 +# End: +# vim: syntax=perl sw=4 sts=4 sr et diff -Nru lintian-2.93.0/lib/Lintian/Output/HTML.pm lintian-2.89.0ubuntu1/lib/Lintian/Output/HTML.pm --- lintian-2.93.0/lib/Lintian/Output/HTML.pm 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/lib/Lintian/Output/HTML.pm 2020-08-10 09:59:45.000000000 +0000 @@ -23,7 +23,6 @@ use utf8; use autodie; -use Text::Markdown::Discount qw(markdown); use Text::Xslate; use Time::Duration; use Time::Moment; @@ -55,18 +54,6 @@ =over 4 -=item BUILD - -=cut - -sub BUILD { - my ($self, $args) = @_; - - $self->delimiter(EMPTY); - - return; -} - =item issue_tags Print all tags passed in array. A separate arguments with processables @@ -168,7 +155,8 @@ $tag{name} = $input->info->name; - $tag{url} = "https://lintian.debian.org/tags/$tag{name}.html"; + $tag{url} + = "https://lintian.debian.org/$lintian_version/tags/$tag{name}.html"; $tag{context} = $input->context if length $input->context; @@ -187,23 +175,22 @@ $tag{comments} = \@comments if @comments; } + + $self->issuedtags->{$input->info->name}++; } return \@tags; } -=item tag_description - -=cut - -sub tag_description { - my ($self, $tag_info) = @_; - - say '

Name: ' . $tag_info->name . '

'; - say EMPTY; - - print markdown($tag_info->markdown_description); +sub _delimiter { + return; +} +sub _print { + my ($self, $stream, $lead, @args) = @_; + $stream ||= $self->stderr; + my $output = $self->string($lead, @args); + print {$stream} $output; return; } diff -Nru lintian-2.93.0/lib/Lintian/Output/JSON.pm lintian-2.89.0ubuntu1/lib/Lintian/Output/JSON.pm --- lintian-2.93.0/lib/Lintian/Output/JSON.pm 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/lib/Lintian/Output/JSON.pm 2020-08-10 09:59:45.000000000 +0000 @@ -51,18 +51,6 @@ =over 4 -=item BUILD - -=cut - -sub BUILD { - my ($self, $args) = @_; - - $self->delimiter(EMPTY); - - return; -} - =item issue_tags Print all tags passed in array. A separate arguments with processables @@ -176,55 +164,22 @@ $tag{'override-comments'} = \@comments if @comments; } + + $self->issuedtags->{$input->info->name}++; } return \@tags; } -=item tag_description - -=cut - -sub tag_description { - my ($self, $tag_info) = @_; - - my %output; - - $output{Name} = $tag_info->name; - $output{'Name-Spaced'} = $tag_info->name_spaced - if length $tag_info->name_spaced; - - $output{Explanation} = $tag_info->explanation; - $output{'See-Also'} = $tag_info->see_also - if @{$tag_info->see_also}; - - $output{Check} = $tag_info->check; - $output{Visibility} = $tag_info->visibility; - $output{Experimental} = $tag_info->experimental - if length $tag_info->experimental; - - $output{'Renamed-From'} = $tag_info->renamed_from - if @{$tag_info->renamed_from}; - - # convert to UTF-8 prior to encoding in JSON - my $encoder = JSON->new; - $encoder->canonical; - $encoder->utf8; - $encoder->pretty; - - my $json = $encoder->encode(\%output); - - # duplicate STDOUT - open(my $RAW, '>&', *STDOUT) or die 'Cannot dup STDOUT'; - - # avoid all PerlIO layers such as utf8 - binmode($RAW, ':raw'); - - # output encoded JSON to the raw handle - print {$RAW} $json; - - close $RAW; +sub _delimiter { + return; +} +sub _print { + my ($self, $stream, $lead, @args) = @_; + $stream ||= $self->stderr; + my $output = $self->string($lead, @args); + print {$stream} $output; return; } diff -Nru lintian-2.93.0/lib/Lintian/Output/LetterQualifier.pm lintian-2.89.0ubuntu1/lib/Lintian/Output/LetterQualifier.pm --- lintian-2.93.0/lib/Lintian/Output/LetterQualifier.pm 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/lib/Lintian/Output/LetterQualifier.pm 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,235 @@ +# Copyright © 2008 Jordà Polo +# +# This program is free software; you can redistribute it and/or modify +# it under the terms of the GNU General Public License as published by +# the Free Software Foundation; either version 2 of the License, or +# (at your option) any later version. +# +# This program is distributed in the hope that it will be useful, +# but WITHOUT ANY WARRANTY; without even the implied warranty of +# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the +# GNU General Public License for more details. +# +# You should have received a copy of the GNU General Public License +# along with this program. If not, you can find it on the World Wide +# Web at http://www.gnu.org/copyleft/gpl.html, or write to the Free +# Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, +# MA 02110-1301, USA. + +package Lintian::Output::LetterQualifier; + +use v5.20; +use warnings; +use utf8; + +use Term::ANSIColor qw(colored); +use Lintian::Tag::Info (); + +use constant EMPTY => q{}; +use constant SPACE => q{ }; +use constant NEWLINE => qq{\n}; + +use Moo; +use namespace::clean; + +with 'Lintian::Output'; + +my %codes = ( + 'classification' => 'C', + 'pedantic' => 'P', + 'info' => 'I', + 'warning' => 'W', + 'error' => 'E', +); + +my %lq_default_colors = ( + 'pedantic' => 'green', + 'info' => 'cyan', + 'warning' => 'yellow', + 'error' => 'red', +); + +=head1 NAME + +Lintian::Output::LetterQualifier - letter qualifier tag output + +=head1 SYNOPSIS + + use Lintian::Output::LetterQualifier; + +=head1 DESCRIPTION + +Provides letter qualifier tag output. + +=head1 INSTANCE METHODS + +=over 4 + +=item BUILD + +=cut + +sub BUILD { + my ($self) = @_; + + $self->colors({%lq_default_colors}); + + return; +} + +=item issue_tags + +Print all tags passed in array. A separate arguments with processables +is necessary to report in case no tags were found. + +=cut + +my %code_priority = ( + 'E' => 30, + 'W' => 40, + 'I' => 50, + 'P' => 60, + 'X' => 70, + 'C' => 80, + 'O' => 90, +); + +my %type_priority = ( + 'source' => 30, + 'binary' => 40, + 'udeb' => 50, + 'changes' => 60, + 'buildinfo' => 70, +); + +sub issue_tags { + my ($self, $groups) = @_; + + my @processables = map { $_->get_processables } @{$groups // []}; + + my @pending; + for my $processable (@processables) { + + # get tags + my @tags = @{$processable->tags}; + + # associate tags with processable + $_->processable($processable) for @tags; + + # remove circular references + $processable->tags([]); + + push(@pending, @tags); + } + + $self->print_start_pkg($_) for @processables; + + my @sorted = sort { + defined $a->override <=> defined $b->override + || $code_priority{$a->info->code} <=> $code_priority{$b->info->code} + || $a->name cmp $b->name + || $type_priority{$a->processable->type} + <=> $type_priority{$b->processable->type} + || $a->processable->name cmp $b->processable->name + || $a->context cmp $b->context + } @pending; + + $self->print_tag($_) for @sorted; + + return; +} + +=item print_tag + +=cut + +sub print_tag { + my ($self, $tag) = @_; + + my $tag_info = $tag->info; + my $information = $tag->context; + my $override = $tag->override; + my $processable = $tag->processable; + + my $code = $tag_info->code; + $code = 'X' if $tag_info->experimental; + $code = 'O' if defined($override); + + my $severity = $tag_info->effective_severity; + my $lq = $codes{$severity}; + + my $pkg = $processable->name; + my $type + = ($processable->type ne 'binary') ? SPACE . $processable->type : EMPTY; + + my $tagname = $tag_info->name; + + $information = ' ' . $self->_quote_print($information) + if $information ne ''; + + if ($self->_do_color) { + my $color = $self->colors->{$severity}; + $lq = colored($lq, $color); + $tagname = colored($tagname, $color); + } + + $self->_print('', "$code\[$lq\]: $pkg$type", "$tagname$information"); + if (not $self->issued_tag($tag_info->name) and $self->showdescription) { + my $description = $tag_info->description('text', ' '); + $self->_print('', 'N', ''); + $self->_print('', 'N', split("\n", $description)); + $self->_print('', 'N', ''); + } + return; +} + +=item C + +Called before lintian starts to handle each package. The version in +Lintian::Output uses v_msg() for output. Called from Tags::select_pkg(). + +=cut + +sub print_start_pkg { + my ($self, $processable) = @_; + + my $object = 'package'; + $object = 'file' + if $processable->type eq 'changes'; + + $self->v_msg( + $self->delimiter, + 'Processing '. $processable->type. " $object ". $processable->name, + '(version ' + . $processable->version + . ', arch ' + . $processable->architecture . ') ...' + ); + return; +} + +=item C<_quote_print($string)> + +Called to quote a string. By default it will replace all +non-printables with "?". Sub-classes can override it if +they allow non-ascii printables etc. + +=cut + +sub _quote_print { + my ($self, $string) = @_; + $string =~ s/[^[:print:]]/?/g; + return $string; +} + +=back + +=cut + +1; + +# Local Variables: +# indent-tabs-mode: nil +# cperl-indent-level: 4 +# End: +# vim: syntax=perl sw=4 sts=4 sr et diff -Nru lintian-2.93.0/lib/Lintian/Output/Standard.pm lintian-2.89.0ubuntu1/lib/Lintian/Output/Standard.pm --- lintian-2.93.0/lib/Lintian/Output/Standard.pm 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/lib/Lintian/Output/Standard.pm 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,273 @@ +# Copyright © 2008 Frank Lichtenheld +# +# This program is free software; you can redistribute it and/or modify +# it under the terms of the GNU General Public License as published by +# the Free Software Foundation; either version 2 of the License, or +# (at your option) any later version. +# +# This program is distributed in the hope that it will be useful, +# but WITHOUT ANY WARRANTY; without even the implied warranty of +# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the +# GNU General Public License for more details. +# +# You should have received a copy of the GNU General Public License +# along with this program. If not, you can find it on the World Wide +# Web at http://www.gnu.org/copyleft/gpl.html, or write to the Free +# Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, +# MA 02110-1301, USA. + +package Lintian::Output::Standard; + +use v5.20; +use warnings; +use utf8; + +use HTML::Entities; +use Term::ANSIColor (); + +# for tty hyperlinks +use constant OSC_HYPERLINK => qq{\033]8;;}; +use constant OSC_DONE => qq{\033\\}; + +use constant SPACE => q{ }; + +use Moo; +use namespace::clean; + +with 'Lintian::Output'; + +=head1 NAME + +Lintian::Output::Standard - standard tag output + +=head1 SYNOPSIS + + use Lintian::Output::Standard; + +=head1 DESCRIPTION + +Provides standard tag output. + +=head1 INSTANCE METHODS + +=over 4 + +=item issue_tags + +Print all tags passed in array. A separate arguments with processables +is necessary to report in case no tags were found. + +=cut + +my %code_priority = ( + 'E' => 30, + 'W' => 40, + 'I' => 50, + 'P' => 60, + 'X' => 70, + 'C' => 80, + 'O' => 90, +); + +my %type_priority = ( + 'source' => 30, + 'binary' => 40, + 'udeb' => 50, + 'changes' => 60, + 'buildinfo' => 70, +); + +sub issue_tags { + my ($self, $groups) = @_; + + my @processables = map { $_->get_processables } @{$groups // []}; + + my @pending; + for my $processable (@processables) { + + # get tags + my @tags = @{$processable->tags}; + + # associate tags with processable + $_->processable($processable) for @tags; + + # remove circular references + $processable->tags([]); + + push(@pending, @tags); + } + + $self->print_start_pkg($_) for @processables; + + my @sorted = sort { + defined $a->override <=> defined $b->override + || $code_priority{$a->info->code} <=> $code_priority{$b->info->code} + || $a->name cmp $b->name + || $type_priority{$a->processable->type} + <=> $type_priority{$b->processable->type} + || $a->processable->name cmp $b->processable->name + || $a->context cmp $b->context + } @pending; + + $self->print_tag($_) for @sorted; + + return; +} + +=item C + +Print a tag. The first two arguments are hash reference with the +information about the package and the tag, $context is the context +information for the tag (if any) as an array reference, and $override +is either undef if the tag is not overridden or a hash with +override info for this tag. + +=cut + +sub print_tag { + my ($self, $tag) = @_; + + my $tag_info = $tag->info; + my $information = $tag->context; + my $override = $tag->override; + my $processable = $tag->processable; + + $information = ' ' . $self->_quote_print($information) + if $information ne ''; + my $code = $tag_info->code; + my $tag_color = ($tag->override ? 'bright_black' : $self->{colors}{$code}); + my $fpkg_info= $self->_format_pkg_info($processable, $tag_info, $override); + my $tag_name = $tag_info->name; + my $limit = $self->tag_display_limit; + my $output; + + # Limit the output so people do not drown in tags. Some tags are + # insanely noisy (hi static-library-has-unneeded-section) + if ($limit) { + my $proc_id = $processable->identifier; + my $emitted_count + = $self->{'proc_id2tag_count'}{$proc_id}{$tag_name}++; + return if $emitted_count >= $limit; + my $msg + = ' ... use --no-tag-display-limit to see all (or pipe to a file/program)'; + $information = $self->_quote_print($msg) + if $emitted_count >= $limit-1; + } + if ($self->_do_color && $self->color eq 'html') { + my $escaped = encode_entities($tag_name); + $information = encode_entities($information); + $output .= qq($escaped); + + } else { + my $text = $tag_name; + $text = Term::ANSIColor::colored($tag_name, $tag_color) + if $self->_do_color; + + if ($self->tty_hyperlinks && $self->_do_color) { + my $target + = 'https://lintian.debian.org/tags/' . $tag_name . '.html'; + $output .= $self->osc_hyperlink($text, $target); + } else { + $output .= $text; + } + } + + if ($override && @{ $override->{comments} }) { + foreach my $c (@{ $override->{comments} }) { + $self->msg($self->_quote_print($c)); + } + } + + $self->_print('', $fpkg_info, "$output$information"); + if (not $self->issued_tag($tag_info->name) and $self->showdescription) { + my $description; + if ($self->_do_color && $self->color eq 'html') { + $description = $tag_info->description('html', ' '); + } else { + $description = $tag_info->description('text', ' '); + } + $self->_print('', 'N', ''); + $self->_print('', 'N', split("\n", $description)); + $self->_print('', 'N', ''); + } + return; +} + +=item C + +Called before lintian starts to handle each package. The version in +Lintian::Output uses v_msg() for output. Called from Tags::select_pkg(). + +=cut + +sub print_start_pkg { + my ($self, $processable) = @_; + + my $object = 'package'; + $object = 'file' + if $processable->type eq 'changes'; + + $self->v_msg( + $self->delimiter, + 'Processing '. $processable->type. " $object ". $processable->name, + '(version ' + . $processable->version + . ', arch ' + . $processable->architecture . ') ...' + ); + return; +} + +=item C<_quote_print($string)> + +Called to quote a string. By default it will replace all +non-printables with "?". Sub-classes can override it if +they allow non-ascii printables etc. + +=cut + +sub _quote_print { + my ($self, $string) = @_; + $string =~ s/[^[:print:]]/?/g; + return $string; +} + +=item C + +=cut + +sub osc_hyperlink { + my ($self, $text, $target) = @_; + + my $start = OSC_HYPERLINK . $target . OSC_DONE; + my $end = OSC_HYPERLINK . OSC_DONE; + + return $start . $text . $end; +} + +# Helper function to "print_tag" to decide the output format of the tag line. Used by +# the "FullEWI" subclass. +# +sub _format_pkg_info { + my ($self, $processable, $tag_info, $override) = @_; + my $code = $tag_info->code; + $code = 'X' if $tag_info->experimental; + $code = 'O' if defined $override; + my $type = ''; + $type = SPACE . $processable->type if $processable->type ne 'binary'; + return "$code: " . $processable->name . $type; +} + +=back + +=cut + +1; + +__END__ + +# Local Variables: +# indent-tabs-mode: nil +# cperl-indent-level: 4 +# End: +# vim: syntax=perl sw=4 sts=4 sr et diff -Nru lintian-2.93.0/lib/Lintian/Output/Universal.pm lintian-2.89.0ubuntu1/lib/Lintian/Output/Universal.pm --- lintian-2.93.0/lib/Lintian/Output/Universal.pm 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/lib/Lintian/Output/Universal.pm 2020-08-10 09:59:45.000000000 +0000 @@ -129,11 +129,21 @@ my @sorted = reverse sort { order($a) cmp order($b) } @lines; - say $_ for @sorted; + print { $self->stdout } $_ . NEWLINE for @sorted; return; } +sub _message { + my ($self, @args) = @_; + return; +} + +sub _warning { + my ($self, @args) = @_; + return; +} + =item order =cut diff -Nru lintian-2.93.0/lib/Lintian/Output/XML.pm lintian-2.89.0ubuntu1/lib/Lintian/Output/XML.pm --- lintian-2.93.0/lib/Lintian/Output/XML.pm 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/lib/Lintian/Output/XML.pm 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,228 @@ +# Copyright © 2008 Frank Lichtenheld +# +# This program is free software; you can redistribute it and/or modify +# it under the terms of the GNU General Public License as published by +# the Free Software Foundation; either version 2 of the License, or +# (at your option) any later version. +# +# This program is distributed in the hope that it will be useful, +# but WITHOUT ANY WARRANTY; without even the implied warranty of +# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the +# GNU General Public License for more details. +# +# You should have received a copy of the GNU General Public License +# along with this program. If not, you can find it on the World Wide +# Web at http://www.gnu.org/copyleft/gpl.html, or write to the Free +# Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, +# MA 02110-1301, USA. + +package Lintian::Output::XML; + +use v5.20; +use warnings; +use utf8; + +use Time::Piece; +use XML::Writer; + +use constant EMPTY => q{}; +use constant SPACE => q{ }; +use constant NEWLINE => qq{\n}; + +use Moo; +use namespace::clean; + +with 'Lintian::Output'; + +=head1 NAME + +Lintian::Output::XML - XML tag output + +=head1 SYNOPSIS + + use Lintian::Output::XML; + +=head1 DESCRIPTION + +Provides XML tag output. + +=head1 INSTANCE METHODS + +=over 4 + +=item issue_tags + +Print all tags passed in array. A separate arguments with processables +is necessary to report in case no tags were found. + +=cut + +my %code_priority = ( + 'E' => 30, + 'W' => 40, + 'I' => 50, + 'P' => 60, + 'X' => 70, + 'C' => 80, + 'O' => 90, +); + +sub issue_tags { + my ($self, $groups) = @_; + + my $writer + = XML::Writer->new(OUTPUT => 'self', DATA_MODE => 1, DATA_INDENT => 2); + + $writer->xmlDecl('utf-8'); + + $writer->startTag('lintian-run'); + $writer->dataElement('lintian-version', $ENV{LINTIAN_VERSION}) + if length $ENV{LINTIAN_VERSION}; + + $writer->startTag('groups'); + + for my $group (@{$groups // []}) { + + $writer->startTag('group'); + + # grab group data from first processable + my $first = ($group->get_processables)[0]; + + $writer->dataElement('source-name', $first->source); + $writer->dataElement('source-version', $first->source_version); + $writer->dataElement('run-start', gmtime->datetime); + + $writer->startTag('input-files'); + + my @singles = grep { defined } + map { $group->$_ } ('source', 'changes', 'buildinfo'); + for my $processable (@singles) { + + $writer->startTag($processable->type); + $self->taglist($writer, $processable->tags); + $writer->endTag($processable->type); + } + + my @installables = $group->get_binary_processables; + if (@installables) { + + $writer->startTag('installables'); + + my @sorted = sort { $a->type cmp $b->type } @installables; + for my $processable (@sorted) { + + $writer->startTag('installable'); + + $writer->dataElement('package-name', $processable->name); + $writer->dataElement('version', $processable->version) + if $processable->version ne $first->source_version; + + $writer->dataElement('architecture', + $processable->architecture); + + my $container = $processable->type; + $container =~ s/^binary$/deb/; + $writer->dataElement('container', $container); + + $self->taglist($writer, $processable->tags); + + $writer->endTag('installable'); + } + + $writer->endTag('installables'); + } + + $writer->endTag('input-files'); + $writer->endTag('group'); + } + + $writer->endTag('groups'); + + $writer->endTag('lintian-run'); + $writer->end(); + + print { $self->stdout } $writer->to_string; + + return; +} + +=item C + +=cut + +sub taglist { + my ($self, $writer, $tags) = @_; + + $writer->startTag('tags'); + + my @sorted = sort { + defined $a->override <=> defined $b->override + || $code_priority{$a->info->code}<=> $code_priority{$b->info->code} + || $a->name cmp $b->name + || $a->context cmp $b->context + } @{$tags // []}; + + for my $tag (@sorted) { + + $writer->startTag('tag',(severity => $tag->info->effective_severity,)); + + $writer->dataElement('name', $tag->info->name); + + my $printable = $tag->context; + $printable =~ s/[^[:print:]]/?/g; + + $writer->dataElement('context', $printable) + if length $printable; + + $writer->dataElement('experimental', 'yes') + if $tag->info->experimental; + + if ($tag->override) { + + $writer->startTag('override'); + $writer->dataElement('origin', 'maintainer'); + + my @comments = @{ $tag->override->{comments} // [] }; + if (@comments) { + + $writer->startTag('comments'); + $writer->dataElement('line', $_) for @comments; + $writer->endTag('comments'); + } + + $writer->endTag('override'); + } + + $writer->endTag('tag'); + + $self->issuedtags->{$tag->info->name}++; + } + + $writer->endTag('tags'); + + return; +} + +sub _delimiter { + return; +} + +sub _print { + my ($self, $stream, $lead, @args) = @_; + $stream ||= $self->stderr; + my $output = $self->string($lead, @args); + print {$stream} $output; + return; +} + +=back + +=cut + +1; + +# Local Variables: +# indent-tabs-mode: nil +# cperl-indent-level: 4 +# End: +# vim: syntax=perl sw=4 sts=4 sr et diff -Nru lintian-2.93.0/lib/Lintian/Output.pm lintian-2.89.0ubuntu1/lib/Lintian/Output.pm --- lintian-2.93.0/lib/Lintian/Output.pm 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/lib/Lintian/Output.pm 2020-08-10 09:59:45.000000000 +0000 @@ -32,11 +32,21 @@ =head1 SYNOPSIS + # non-OO + use Lintian::Output qw(:messages); + + $Lintian::Output::GLOBAL->verbosity_level(1); + + msg("Something interesting"); + v_msg("Something less interesting"); + debug_msg(3, "Something very specific"); + + # OO use Lintian::Output; my $out = Lintian::Output->new; - $out->verbosity(-1); + $out->verbosity_level(-1); $out->msg("Something interesting"); $out->v_msg("Something less interesting"); $out->debug_msg(3, "Something very specific"); @@ -56,10 +66,17 @@ =over 4 -=item html - =item color +Can take the values "never", "always", "auto" or "html". + +Whether to colorize tags based on their severity. The default is "never", +which never uses color. "always" will always use color, "auto" will use +color only if the output is going to a terminal. + +"html" will output HTML tags with a color style attribute (instead +of ANSI color escape sequences). + =item colors =item debug @@ -67,12 +84,24 @@ If set to a positive integer, will enable all debug messages issued with a level lower or equal to its value. +=item issuedtags + +Hash containing the names of tags which have been issued. + =item perf_debug =item perf_log_fd =item proc_id2tag_count +=item stdout + +I/O handle to use for output of messages and tags. Defaults to C<\*STDOUT>. + +=item stderr + +I/O handle to use for warnings. Defaults to C<\*STDERR>. + =item showdescription Whether to show the description of a tag when printing it. @@ -83,20 +112,17 @@ Get/Set the number of times a tag is emitted per processable. -=item verbosity +=item verbosity_level Determine how verbose the output should be. "0" is the default value (tags and msg only), "-1" is quiet (tags only) and "1" is verbose (tags, msg and v_msg). -=item C - =back =cut -has html => (is => 'rw', default => 0); -has color => (is => 'rw', default => 0); +has color => (is => 'rw', default => 'never'); has colors => ( is => 'rw', default => sub { @@ -108,18 +134,19 @@ 'C' => 'blue', } }); +has issuedtags => (is => 'rw', default => sub { {} }); has perf_debug => (is => 'rw', default => 0); has perf_log_fd => (is => 'rw', default => sub { \*STDOUT }); has proc_id2tag_count => (is => 'rw', default => sub { {} }); +has stderr => (is => 'rw', default => sub { \*STDERR }); +has stdout => (is => 'rw', default => sub { \*STDOUT }); has tag_display_limit => (is => 'rw', default => 4); has tty_hyperlinks => (is => 'rw', default => 0); -has verbosity => (is => 'rw', default => 0); +has verbosity_level => (is => 'rw', default => 0); has debug => (is => 'rw', default => sub { {} }); has showdescription => (is => 'rw', default => sub { {} }); -has delimiter => (is => 'rw', default => '----'); - =head1 CLASS/INSTANCE METHODS These methods can be used both with and without an object. If no object @@ -130,12 +157,12 @@ =item C Will output the strings given in @args, one per line, each line prefixed -with 'N: '. Will do nothing if verbosity is less than 0. +with 'N: '. Will do nothing if verbosity_level is less than 0. =item C Will output the strings given in @args, one per line, each line prefixed -with 'N: '. Will do nothing unless verbosity is greater than 0. +with 'N: '. Will do nothing unless verbosity_level is greater than 0. =item C @@ -150,33 +177,40 @@ sub msg { my ($self, @args) = @_; - return - if $self->verbosity < 0; - - say "N: $_" for @args; - + return if $self->verbosity_level < 0; + $self->_message(@args); return; } sub v_msg { my ($self, @args) = @_; - return - unless $self->verbosity > 0; - - say "N: $_" for @args; - + return unless $self->verbosity_level > 0; + $self->_message(@args); return; } sub debug_msg { my ($self, $level, @args) = @_; - return - unless $self->debug && ($self->debug >= $level); + return unless $self->debug && ($self->debug >= $level); + + $self->_message(@args); + return; +} + +=item C - say "N: $_" for @args; +Will output the strings given in @args on stderr, one per line, each line +prefixed with 'warning: '. + +=cut +sub warning { + my ($self, @args) = @_; + + return if $self->verbosity_level < 0; + $self->_warning(@args); return; } @@ -196,11 +230,177 @@ return unless $self->perf_debug; - say { $self->perf_log_fd } $_ for @args; + $self->_print($self->perf_log_fd, '', @args); + return; +} + +=item C + +Gives back a string that is usable for separating messages in the output. +Note: This does not print anything, it just gives back the string, use +with one of the methods above, e.g. + + v_msg('foo', delimiter(), 'bar'); + +=cut + +sub delimiter { + my ($self) = @_; + + return $self->_delimiter; +} + +=item C + +Indicate that the named tag has been issued. Returns a boolean value +indicating whether the tag had previously been issued by the object. + +=cut + +sub issued_tag { + my ($self, $tag_name) = @_; + + return $self->issuedtags->{$tag_name}++ ? 1 : 0; +} + +=item C + +TODO: Is this part of the public interface? + +=cut + +sub string { + my ($self, $lead, @args) = @_; + + my $output = ''; + if (@args) { + my $prefix = ''; + $prefix = "$lead: " if $lead; + foreach (@args) { + $output .= "${prefix}${_}\n"; + } + } elsif ($lead) { + $output .= $lead.".\n"; + } + + return $output; +} + +=back + +=head1 INSTANCE METHODS FOR SUBCLASSING +The following methods are only intended for subclassing and are +only available as instance methods. The methods mentioned in +L +usually only check whether they should do anything at all (according +to the values of verbosity_level and debug) and then call one of +the following methods to do the actual printing. Almost all of them +finally call _print() to do that. This convoluted scheme is necessary +to be able to use the methods above as class methods and still make +the behaviour overridable in subclasses. + +=over 4 + +=item C<_message(@args)> + +Called by msg(), v_msg(), and debug_msg() to print the +message. + +=cut + +sub _message { + my ($self, @args) = @_; + + $self->_print('', 'N', @args); + return; +} + +=item C<_warning(@args)> + +Called by warning() to print the warning. + +=cut + +sub _warning { + my ($self, @args) = @_; + + $self->_print($self->stderr, 'warning', @args); + return; +} + +=item C<_print($stream, $lead, @args)> + +Called by _message(), _warning(), and print_tag() to do +the actual printing. + +If you override these three methods, you can change +the calling convention for this method to pretty much +whatever you want. + +The version in Lintian::Output prints the strings in +@args, one per line, each line preceded by $lead to +the I/O handle given in $stream. + +=cut + +sub _print { + my ($self, $stream, $lead, @args) = @_; + $stream ||= $self->stdout; + + my $output = $self->string($lead, @args); + print {$stream} $output; return; } +=item C<_delimiter()> + +Called by delimiter(). + +=cut + +sub _delimiter { + return '----'; +} + +=item C<_do_color()> + +Called by print_tag() to determine whether to produce colored +output. + +=cut + +sub _do_color { + my ($self) = @_; + + return ( + $self->color eq 'always' + || $self->color eq 'html' + || ($self->color eq 'auto' + && -t $self->stdout)); +} + +1; + +__END__ + +=back + +=head1 EXPORTS + +Lintian::Output exports nothing by default, but the following export +tags are available: + +=over 4 + +=item :messages + +Exports all the methods in L + +=item :util + +Exports all the methods in L + =back =head1 SEE ALSO @@ -209,8 +409,6 @@ =cut -1; - # Local Variables: # indent-tabs-mode: nil # cperl-indent-level: 4 diff -Nru lintian-2.93.0/lib/Lintian/Pool.pm lintian-2.89.0ubuntu1/lib/Lintian/Pool.pm --- lintian-2.93.0/lib/Lintian/Pool.pm 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/lib/Lintian/Pool.pm 2020-08-10 09:59:45.000000000 +0000 @@ -25,14 +25,18 @@ use utf8; use autodie; -use Cwd qw(getcwd); +use Carp qw(croak); +use Cwd; use List::MoreUtils qw(any); use Time::HiRes qw(gettimeofday tv_interval); use Path::Tiny; use POSIX qw(:sys_wait_h); -use Proc::ProcessTable; use Lintian::Group; +use Lintian::Util; + +use constant EMPTY => q{}; +use constant SPACE => q{ }; use Moo; use namespace::clean; @@ -154,11 +158,24 @@ for my $group (values %{$self->groups}) { + $OUTPUT->v_msg('Starting on group ' . $group->name); + my $total_start = [gettimeofday]; + my $group_start = [gettimeofday]; $group->profile($PROFILE); $group->jobs($option->{'jobs'}); + $group->unpack($OUTPUT); + + my $raw_res = tv_interval($group_start); + my $tres = sprintf('%.3fs', $raw_res); + + $OUTPUT->debug_msg(1, 'Unpack of ' . $group->name . " done ($tres)"); + $OUTPUT->perf_log($group->name . ",total-group-unpack,${raw_res}"); + + my %reported_count; + my $success= $group->process(\%ignored_overrides, $option, $OUTPUT); # associate all tags with processable @@ -184,7 +201,6 @@ || $_->name eq 'unused-override' } @tags; - my %reported_count; $reported_count{$_->info->effective_severity}++ for @reported_trusted; $reported_count{experimental} += scalar @reported_experimental; $reported_count{override} += scalar @override; @@ -241,30 +257,25 @@ # put tags back into their respective processables push(@{$_->processable->tags}, $_) for @tags; - # interruptions can leave processes behind (manpages); wait and reap - if ($$exit_code_ref == 1) { - 1 while waitpid(-1, WNOHANG) > 0; - } - - if ($option->{debug}) { - my $process_table = Proc::ProcessTable->new; - my @leftover= grep { $_->ppid == $$ } @{$process_table->table}; - - # announce left over processes, see commit 3bbcc3b - if (@leftover) { - warn "\nSome processes were left over (maybe unreaped):\n"; - - my $FORMAT = " %-12s %-12s %-8s %-24s %s\n"; - printf($FORMAT, 'PID', 'TTY', 'STATUS', 'START', 'COMMAND'); - - printf($FORMAT, - $_->pid,$_->ttydev,$_->state,scalar(localtime($_->start)), - $_->cmndline) - for @leftover; - + if ($$exit_code_ref != 1) { + # Double check that no processes are running; + # hopefully it will catch regressions like 3bbcc3b + # earlier. + # + # Unfortunately, the cleanup via IO::Async::Function seems keep + # a worker unreaped; disabling. Should be revisited. + # + if (waitpid(-1, WNOHANG) != -1) { $$exit_code_ref = 1; - die "Aborting.\n"; + die 'Unreaped processes after running checks!?'; } + } else { + # If we are interrupted in (e.g.) checks/manpages, it + # tends to leave processes behind. No reason to flag + # an error for that - but we still try to reap the + # children if they are now done. + + 1 while waitpid(-1, WNOHANG) > 0; } # remove group files diff -Nru lintian-2.93.0/lib/Lintian/Processable/Binary/Changelog.pm lintian-2.89.0ubuntu1/lib/Lintian/Processable/Binary/Changelog.pm --- lintian-2.93.0/lib/Lintian/Processable/Binary/Changelog.pm 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/lib/Lintian/Processable/Binary/Changelog.pm 2020-08-10 09:59:45.000000000 +0000 @@ -38,7 +38,7 @@ use List::MoreUtils qw(first_value); use Path::Tiny; -use Lintian::IPC::Run3 qw(safe_qx); +use Lintian::IO::Async qw(safe_qx); use Lintian::Util qw(is_ancestor_of); use Moo::Role; @@ -67,19 +67,19 @@ sub add_changelog { my ($self) = @_; - my $changelogpath = path($self->basedir)->child('changelog')->stringify; + my $changelogpath = path($self->groupdir)->child('changelog')->stringify; unlink($changelogpath) if -e $changelogpath || -l $changelogpath; # Extract NEWS.Debian files as well, with similar precautions. # Ignore any symlinks to other packages here; in that case, we # just won't check the file. - my $newspath = path($self->basedir)->child('NEWS.Debian')->stringify; + my $newspath = path($self->groupdir)->child('NEWS.Debian')->stringify; unlink($newspath) if -l $newspath or -e _; - my $unpackedpath = path($self->basedir)->child('unpacked')->stringify; + my $unpackedpath = path($self->groupdir)->child('unpacked')->stringify; my $packagepath = "$unpackedpath/usr/share/doc/" . $self->name; # pretend we did not find anything if parent dir is outside package @@ -126,7 +126,7 @@ my $link = readlink($packagechangelogpath); if ($link =~ /\.\./ || ($link =~ m%/% && $link !~ m%^[^/]+(?:/+[^/]+)*\z%)) { - symlink($self->basedir . '/file-is-in-another-package', + symlink($self->groupdir . '/file-is-in-another-package', $changelogpath); undef $packagechangelogpath; } elsif (!-f $packagechangelogpath) { diff -Nru lintian-2.93.0/lib/Lintian/Processable/Binary/Copyright.pm lintian-2.89.0ubuntu1/lib/Lintian/Processable/Binary/Copyright.pm --- lintian-2.93.0/lib/Lintian/Processable/Binary/Copyright.pm 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/lib/Lintian/Processable/Binary/Copyright.pm 2020-08-10 09:59:45.000000000 +0000 @@ -66,11 +66,11 @@ sub add_copyright { my ($self) = @_; - my $unpackedpath = path($self->basedir)->child('unpacked')->stringify; + my $unpackedpath = path($self->groupdir)->child('unpacked')->stringify; return unless -d $unpackedpath; - my $copyrightpath = path($self->basedir)->child('copyright')->stringify; + my $copyrightpath = path($self->groupdir)->child('copyright')->stringify; unlink($copyrightpath) if -e $copyrightpath; diff -Nru lintian-2.93.0/lib/Lintian/Processable/Binary.pm lintian-2.89.0ubuntu1/lib/Lintian/Processable/Binary.pm --- lintian-2.93.0/lib/Lintian/Processable/Binary.pm 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/lib/Lintian/Processable/Binary.pm 2020-08-10 09:59:45.000000000 +0000 @@ -25,7 +25,7 @@ use Carp qw(croak); use Path::Tiny; -use Lintian::IPC::Run3 qw(get_deb_info); +use Lintian::IO::Async qw(get_deb_info); use constant COLON => q{:}; use constant SLASH => q{/}; diff -Nru lintian-2.93.0/lib/Lintian/Processable/Changelog.pm lintian-2.89.0ubuntu1/lib/Lintian/Processable/Changelog.pm --- lintian-2.93.0/lib/Lintian/Processable/Changelog.pm 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/lib/Lintian/Processable/Changelog.pm 2020-08-10 09:59:45.000000000 +0000 @@ -61,43 +61,51 @@ Returns the changelog of the source package as a Parse::DebianChangelog object, or C if the changelog cannot be resolved safely. +=item saved_changelog + +Returns the cached changelog information. + =cut -has changelog => ( - is => 'rw', - lazy => 1, - default => sub { - my ($self) = @_; +has saved_changelog => (is => 'rw'); + +sub changelog { + my ($self) = @_; - my $dch; + return $self->saved_changelog + if defined $self->saved_changelog; - if ($self->type eq 'source') { - my $file = $self->patched->resolve_path('debian/changelog'); + my $dch; - return - unless $file && $file->is_open_ok; + if ($self->type eq 'source') { + my $file = $self->patched->resolve_path('debian/changelog'); - $dch = $file->unpacked_path; + return + unless $file && $file->is_open_ok; - } else { - $dch = path($self->basedir)->child('changelog')->stringify; + $dch = $file->unpacked_path; - return - unless -f $dch && !-l $dch; - } + } else { + $dch = path($self->groupdir)->child('changelog')->stringify; - my $bytes = path($dch)->slurp; return - unless valid_utf8($bytes); + unless -f $dch && !-l $dch; + } + + my $bytes = path($dch)->slurp; + return + unless valid_utf8($bytes); + + # check for UTF-8 + my $contents = decode_utf8($bytes); - # check for UTF-8 - my $contents = decode_utf8($bytes); + my $changelog = Lintian::Inspect::Changelog->new; + $changelog->parse($contents); - my $changelog = Lintian::Inspect::Changelog->new; - $changelog->parse($contents); + $self->saved_changelog($changelog); - return $changelog; - }); + return $self->saved_changelog; +} 1; diff -Nru lintian-2.93.0/lib/Lintian/Processable/Control.pm lintian-2.89.0ubuntu1/lib/Lintian/Processable/Control.pm --- lintian-2.93.0/lib/Lintian/Processable/Control.pm 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/lib/Lintian/Processable/Control.pm 2020-08-10 09:59:45.000000000 +0000 @@ -22,9 +22,10 @@ use utf8; use autodie; -use Lintian::Index::Control; +use Path::Tiny; -use constant SLASH => q{/}; +use Lintian::Index::Control; +use Lintian::Index::Item; use Moo::Role; use namespace::clean; @@ -56,13 +57,63 @@ is => 'rw', lazy => 1, default => sub { - my ($self) = @_; + return Lintian::Index::Control->new; + }); - my $index = Lintian::Index::Control->new; - $index->basedir($self->basedir . SLASH . 'control'); +=item control_index (FILE) - return $index; - }); +Returns a L to FILE in the control.tar.gz. +FILE must be relative to the root of the control.tar.gz and must be +without leading slash (or "./"). If FILE is not in the +control.tar.gz, it returns C. + +To get a list of entries in the control.tar.gz, see +L. To actually access the underlying file +(e.g. the contents), use L. + +Note that the "root directory" (denoted by the empty string) will +always be present, even if the underlying tarball omits it. + +=cut + +sub control_index { + my ($self, $file) = @_; + + return $self->control->lookup($file); +} + +=item sorted_control_index + +Returns a sorted array of file names listed in the control.tar.gz. +The names will not have a leading slash (or "./") and can be passed +to L or L as is. + +The array will not contain the entry for the "root" of the +control.tar.gz. + +=cut + +sub sorted_control_index { + my ($self) = @_; + + return $self->control->sorted_list; +} + +=item control_index_resolved_path(PATH) + +Resolve PATH (relative to the root of the package) and return the +L denoting the resolved path. + +The resolution is done using +L. + +=cut + +sub control_index_resolved_path { + my ($self, $path) = @_; + + return $self->control->resolve_path($path); +} =back diff -Nru lintian-2.93.0/lib/Lintian/Processable/Diffstat.pm lintian-2.89.0ubuntu1/lib/Lintian/Processable/Diffstat.pm --- lintian-2.93.0/lib/Lintian/Processable/Diffstat.pm 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/lib/Lintian/Processable/Diffstat.pm 2020-08-10 09:59:45.000000000 +0000 @@ -1,7 +1,6 @@ # -*- perl -*- Lintian::Processable::Diffstat -- access to collected diffstat data # -# Copyright © 1998 Richard Braakman -# Copyright © 2019-2020 Felix Lechner +# Copyright © 2019 Felix Lechner # # This program is free software; you can redistribute it and/or modify it # under the terms of the GNU General Public License as published by the Free @@ -23,13 +22,9 @@ use utf8; use autodie; -use IPC::Run3; use Path::Tiny; use constant EMPTY => q{}; -use constant COLON => q{:}; -use constant UNDERSCORE => q{_}; -use constant NEWLINE => qq{\n}; use Moo::Role; use namespace::clean; @@ -51,57 +46,6 @@ =over 4 -=item add_diffstat - -=cut - -sub add_diffstat { - my ($self) = @_; - - my $noepoch = $self->fields->value('Version'); - - # strip epoch - $noepoch =~ s/^\d://; - - my $diffname = $self->name . UNDERSCORE . $noepoch . '.diff.gz'; - my $diffpath = path($self->basedir)->child($diffname)->stringify; - return - unless -f $diffpath; - - my @gunzip_command = ('gunzip', '--stdout', $diffpath); - my $gunzip_pid = open(my $from_gunzip, '-|', @gunzip_command) - or die "Cannot run @gunzip_command: $!"; - - my $stdout; - my $stderr; - my @diffstat_command = ('diffstat', '-p1'); - run3(\@diffstat_command, $from_gunzip, \$stdout, \$stderr); - - my $status = ($? >> 8); - if ($status) { - - my $message= "Non-zero status $status from @diffstat_command"; - $message .= COLON . NEWLINE . $stderr - if length $stderr; - - die $message; - } - - close $from_gunzip - or warn "close failed for handle from @gunzip_command: $!"; - - waitpid($gunzip_pid, 0); - - # remove summary in last line - chomp $stdout; - $stdout =~ s/.*\Z//; - - # copy all lines except the last - path($self->basedir)->child('diffstat')->spew($stdout); - - return; -} - =item diffstat Returns the path to diffstat output run on the Debian packaging diff @@ -109,17 +53,28 @@ packages without a "diff.gz" component, this returns the path to an empty file (this may be a device like /dev/null). +=item saved_diffstat + +Returns the cached diffstat information. + =cut +has saved_diffstat => (is => 'rw', default => EMPTY); + sub diffstat { my ($self) = @_; - my $diffstat = path($self->basedir)->child('diffstat')->stringify; + return $self->saved_diffstat + if length $self->saved_diffstat; + + my $dstat = path($self->groupdir)->child('diffstat')->stringify; + + $dstat = '/dev/null' + unless -e $dstat; - $diffstat = '/dev/null' - unless -e $diffstat; + $self->saved_diffstat($dstat); - return $diffstat; + return $self->saved_diffstat; } 1; diff -Nru lintian-2.93.0/lib/Lintian/Processable/Fields/Files.pm lintian-2.89.0ubuntu1/lib/Lintian/Processable/Fields/Files.pm --- lintian-2.93.0/lib/Lintian/Processable/Fields/Files.pm 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/lib/Lintian/Processable/Fields/Files.pm 2020-08-10 09:59:45.000000000 +0000 @@ -3,7 +3,7 @@ # # Copyright © 2010 Adam D. Barratt # Copyright © 2018 Chris Lamb -# Copyright © 2019-2020 Felix Lechner +# Copyright © 2019 Felix Lechner # # This program is free software; you can redistribute it and/or modify it # under the terms of the GNU General Public License as published by the Free @@ -90,74 +90,79 @@ =back +=item saved_files + =cut -has files => ( - is => 'rw', - lazy => 1, - default => +has saved_files => (is => 'rwp', default => sub { {} }); - sub { - my ($self) = @_; +sub files { + my ($self) = @_; - my %files; + return $self->saved_files + if scalar keys %{$self->saved_files}; - my @lines = split(/\n/, $self->fields->value('Files')); + my %files; - # trim both ends of each line - s/^\s+|\s+$//g for @lines; + my $file_list = $self->fields->value('Files'); - for my $line (grep { length } @lines) { + local $_; - my @fields = split(/\s+/, $line); - my $basename = $fields[-1]; + for (split /\n/, $file_list) { - # ignore traversals - next - if $basename =~ m{/}; + # trim both ends + s/^\s+|\s+$//g; - my ($md5sum, $size, $section, $priority) = @fields; + next if $_ eq ''; - $files{$basename}{checksums}{Md5} = { - 'sum' => $md5sum, - 'filesize' => $size, - }; + my @fields = split(/\s+/, $_); + my $file = $fields[-1]; + + next + if $file =~ m,/,; + + my ($md5sum, $size, $section, $priority) = @fields; - $files{$basename}{name} = $basename; - $files{$basename}{size} = $size; + $files{$file}{checksums}{Md5} = { + 'sum' => $md5sum, + 'filesize' => $size, + }; - unless ($self->type eq 'source') { + $files{$file}{name} = $file; + $files{$file}{size} = $size; - $files{$basename}{section} = $section; - $files{$basename}{priority} = $priority; - } + unless ($self->type eq 'source') { + + $files{$file}{section} = $section; + $files{$file}{priority} = $priority; } + } - for my $algorithm (qw(Sha1 Sha256)) { + foreach my $alg (qw(Sha1 Sha256)) { - my @lines - = split(/\n/, $self->fields->value("Checksums-$algorithm")); + my $list = $self->fields->value("Checksums-$alg"); - # trim both ends of each line - s/^\s+|\s+$//g for @lines; + for (split /\n/, $list) { - for my $line (grep { length } @lines) { + # trim both ends + s/^\s+|\s+$//g; - my ($checksum, $size, $basename) = split(/\s+/, $line); + next if $_ eq ''; - # ignore traversals - next - if $basename =~ m{/}; + my ($checksum, $size, $file) = split(/\s+/, $_); + next if $file =~ m,/,; - $files{$basename}{checksums}{$algorithm} = { - 'sum' => $checksum, - 'filesize' => $size - }; - } + $files{$file}{checksums}{$alg} = { + 'sum' => $checksum, + 'filesize' => $size + }; } + } + + $self->_set_saved_files(\%files); - return \%files; - }); + return $self->saved_files; +} =back diff -Nru lintian-2.93.0/lib/Lintian/Processable/Hardening.pm lintian-2.89.0ubuntu1/lib/Lintian/Processable/Hardening.pm --- lintian-2.93.0/lib/Lintian/Processable/Hardening.pm 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/lib/Lintian/Processable/Hardening.pm 2020-08-10 09:59:45.000000000 +0000 @@ -61,7 +61,7 @@ return $self->{hardening_info} if exists $self->{hardening_info}; - my $hardf = path($self->basedir)->child('hardening-info')->stringify; + my $hardf = path($self->groupdir)->child('hardening-info')->stringify; my %hardening_info; diff -Nru lintian-2.93.0/lib/Lintian/Processable/Installable.pm lintian-2.89.0ubuntu1/lib/Lintian/Processable/Installable.pm --- lintian-2.93.0/lib/Lintian/Processable/Installable.pm 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/lib/Lintian/Processable/Installable.pm 2020-08-10 09:59:45.000000000 +0000 @@ -66,12 +66,12 @@ sub unpack { my ($self) = @_; - $self->installed->collect($self->basedir); + $self->installed->collect($self->groupdir); # cause parsing of concatenated data $self->objdump_info; - $self->control->collect($self->basedir); + $self->control->collect($self->groupdir); $self->add_changelog; $self->add_copyright; diff -Nru lintian-2.93.0/lib/Lintian/Processable/Installed.pm lintian-2.89.0ubuntu1/lib/Lintian/Processable/Installed.pm --- lintian-2.93.0/lib/Lintian/Processable/Installed.pm 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/lib/Lintian/Processable/Installed.pm 2020-08-10 09:59:45.000000000 +0000 @@ -25,9 +25,10 @@ use autodie; use utf8; -use Lintian::Index::Installed; +use Path::Tiny; -use constant SLASH => q{/}; +use Lintian::Index::Installed; +use Lintian::Index::Item; use Moo::Role; use namespace::clean; @@ -59,13 +60,66 @@ is => 'rw', lazy => 1, default => sub { - my ($self) = @_; + return Lintian::Index::Installed->new; + }); - my $index = Lintian::Index::Installed->new; - $index->basedir($self->basedir . SLASH . 'unpacked'); +=item index (FILE) - return $index; - }); +Returns a L to FILE in the package. FILE +must be relative to the root of the unpacked package and must be +without leading slash (or "./"). If FILE is not in the package, it +returns C. If FILE is supposed to be a directory, it must be +given with a trailing slash. Example: + + my $file = $info->index ("usr/bin/lintian"); + my $dir = $info->index ("usr/bin/"); + +To get a list of entries in the package, see L. To +actually access the underlying file (e.g. the contents), use +L. + +Note that the "root directory" (denoted by the empty string) will +always be present, even if the underlying tarball omits it. + +=cut + +sub index { + my ($self, $file) = @_; + + return $self->installed->lookup($file); +} + +=item sorted_index + +Returns a sorted array of file names listed in the package. The names +will not have a leading slash (or "./") and can be passed to +L or L as is. + +The array will not contain the entry for the "root" of the package. + +=cut + +sub sorted_index { + my ($self) = @_; + + return $self->installed->sorted_list; +} + +=item index_resolved_path(PATH) + +Resolve PATH (relative to the root of the package) and return the +L denoting the resolved path. + +The resolution is done using +L. + +=cut + +sub index_resolved_path { + my ($self, $path) = @_; + + return $self->installed->resolve_path($path); +} =back diff -Nru lintian-2.93.0/lib/Lintian/Processable/Orig.pm lintian-2.89.0ubuntu1/lib/Lintian/Processable/Orig.pm --- lintian-2.93.0/lib/Lintian/Processable/Orig.pm 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/lib/Lintian/Processable/Orig.pm 2020-08-10 09:59:45.000000000 +0000 @@ -22,9 +22,10 @@ use utf8; use autodie; -use Lintian::Index::Orig; +use Path::Tiny; -use constant SLASH => q{/}; +use Lintian::Index::Item; +use Lintian::Index::Orig; use Moo::Role; use namespace::clean; @@ -56,13 +57,58 @@ is => 'rw', lazy => 1, default => sub { - my ($self) = @_; + return Lintian::Index::Orig->new; + }); - my $index = Lintian::Index::Orig->new; - $index->basedir($self->basedir . SLASH . 'orig'); +=item orig_index (FILE) - return $index; - }); +Like L except orig_index is based on the "orig tarballs" of +the source packages. + +For native packages L and L are generally +identical. + +NB: If sorted_index includes a debian packaging, it is was +contained in upstream part of the source package (or the package is +native). + +=cut + +sub orig_index { + my ($self, $file) = @_; + + return $self->orig->lookup($file); +} + +=item sorted_orig_index + +=cut + +sub sorted_orig_index { + my ($self) = @_; + + return $self->orig->sorted_list; +} + +=item orig_index_resolved_path(PATH) + +Resolve PATH (relative to the root of the package) and return the +L denoting the resolved path. + +The resolution is done using +L. + +NB: If orig_index_resolved_path includes a debian packaging, it is was +contained in upstream part of the source package (or the package is +native). + +=cut + +sub orig_index_resolved_path { + my ($self, $path) = @_; + + return $self->orig->resolve_path($path); +} =back diff -Nru lintian-2.93.0/lib/Lintian/Processable/Overrides.pm lintian-2.89.0ubuntu1/lib/Lintian/Processable/Overrides.pm --- lintian-2.93.0/lib/Lintian/Processable/Overrides.pm 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/lib/Lintian/Processable/Overrides.pm 2020-08-10 09:59:45.000000000 +0000 @@ -57,11 +57,11 @@ sub add_overrides { my ($self) = @_; - my $unpackedpath = path($self->basedir)->child('unpacked')->stringify; + my $unpackedpath = path($self->groupdir)->child('unpacked')->stringify; die "No unpacked data in $unpackedpath" unless -d $unpackedpath; - my $overridepath = path($self->basedir)->child('override')->stringify; + my $overridepath = path($self->groupdir)->child('override')->stringify; unlink($overridepath) if -e $overridepath; @@ -129,7 +129,7 @@ my @comments; my %previous; - my $path = path($self->basedir)->child('override')->stringify; + my $path = path($self->groupdir)->child('override')->stringify; return unless -f $path; diff -Nru lintian-2.93.0/lib/Lintian/Processable/Patched.pm lintian-2.89.0ubuntu1/lib/Lintian/Processable/Patched.pm --- lintian-2.93.0/lib/Lintian/Processable/Patched.pm 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/lib/Lintian/Processable/Patched.pm 2020-08-10 09:59:45.000000000 +0000 @@ -24,9 +24,10 @@ use utf8; use autodie; -use Lintian::Index::Patched; +use Path::Tiny; -use constant SLASH => q{/}; +use Lintian::Index::Item; +use Lintian::Index::Patched; use Moo::Role; use namespace::clean; @@ -58,13 +59,84 @@ is => 'rw', lazy => 1, default => sub { - my ($self) = @_; + return Lintian::Index::Patched->new; + }); - my $index = Lintian::Index::Patched->new; - $index->basedir($self->basedir . SLASH . 'unpacked'); +=item index (FILE) - return $index; - }); +The index of a source package is not very well defined for non-native +source packages. This method gives the index of the "unpacked" +package (with 3.0 (quilt), this implies patches have been applied). + +If you want the index of what is listed in the upstream orig tarballs, +then there is L. + +For native packages, the two indices are generally the same as they +only have one tarball and their debian packaging is included in that +tarball. + +IMPLEMENTATION DETAIL/CAVEAT: Lintian currently (2.5.11) generates +this by running "find(1)" after unpacking the source package. +This has three consequences. + +First it means that (original) owner/group data is lost; Lintian +inserts "root/root" here. This is usually not a problem as +owner/group information for source packages do not really follow any +standards. + +Secondly, permissions are modified by A) umask and B) laboratory +set{g,u}id bits (the laboratory on lintian.d.o has setgid). This is +*not* corrected/altered. Note Lintian (usually) breaks if any of the +"user" bits are set in the umask, so that part of the permission bit +I be reliable. + +Again, this shouldn't be a problem as permissions in source packages +are usually not important. Though if accuracy is needed here, +L may used instead (assuming it has the file in +question). + +Third, hardlinking information is lost and no attempt has been made +to restore it. + +=cut + +sub index { + my ($self, $file) = @_; + + return $self->patched->lookup($file); +} + +=item sorted_index + +Returns a sorted array of file names listed in the package. The names +will not have a leading slash (or "./") and can be passed to +L or L as is. + +The array will not contain the entry for the "root" of the package. + +=cut + +sub sorted_index { + my ($self) = @_; + + return $self->patched->sorted_list; +} + +=item index_resolved_path(PATH) + +Resolve PATH (relative to the root of the package) and return the +L denoting the resolved path. + +The resolution is done using +L. + +=cut + +sub index_resolved_path { + my ($self, $path) = @_; + + return $self->patched->resolve_path($path); +} =back diff -Nru lintian-2.93.0/lib/Lintian/Processable/Source/Components.pm lintian-2.89.0ubuntu1/lib/Lintian/Processable/Source/Components.pm --- lintian-2.93.0/lib/Lintian/Processable/Source/Components.pm 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/lib/Lintian/Processable/Source/Components.pm 1970-01-01 00:00:00.000000000 +0000 @@ -1,122 +0,0 @@ -# -*- perl -*- -# Lintian::Processable::Source::Components -- interface to orig tag components -# -# Copyright © 2020 Felix Lechner -# -# This program is free software; you can redistribute it and/or modify it -# under the terms of the GNU General Public License as published by the Free -# Software Foundation; either version 2 of the License, or (at your option) -# any later version. -# -# This program is distributed in the hope that it will be useful, but WITHOUT -# ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or -# FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for -# more details. -# -# You should have received a copy of the GNU General Public License along with -# this program. If not, see . - -package Lintian::Processable::Source::Components; - -use v5.20; -use warnings; -use utf8; - -use constant EMPTY => q{}; - -use Moo::Role; -use namespace::clean; - -=head1 NAME - -Lintian::Processable::Source::Components - interface to orig tar components - -=head1 SYNOPSIS - - use Moo; - - with 'Lintian::Processable::Source::Components'; - -=head1 DESCRIPTION - -Lintian::Processable::Source::Components provides an interface to data for -upstream source components. Most sources only use one tarball. - -=head1 INSTANCE METHODS - -=over 4 - -=item components - -Returns a reference to a hash containing information about source components -listed in the .dsc file. The key is the filename, and the value is the name -of the component. - -=cut - -has components => ( - is => 'rw', - lazy => 1, - default => sub { - my ($self) = @_; - - # determine source and version; handle missing fields - my $name = $self->fields->value('Source'); - my $version = $self->fields->value('Version'); - my $architecture = 'source'; - - # it is its own source package - my $source = $name; - my $source_version = $version; - - # version handling based on Dpkg::Version::parseversion. - my $noepoch = $source_version; - if ($noepoch =~ /:/) { - $noepoch =~ s/^(?:\d+):(.+)/$1/ - or die "Bad version number '$noepoch'"; - } - - my $baserev = $source . '_' . $noepoch; - - # strip debian revision - $noepoch =~ s/(.+)-(?:.*)$/$1/; - my $base = $source . '_' . $noepoch; - - my $files = $self->files; - - my %components; - for my $name (keys %{$files}) { - - # Look for $pkg_$version.orig(-$comp)?.tar.$ext (non-native) - # or $pkg_$version.tar.$ext (native) - # - This deliberately does not look for the debian packaging - # even when this would be a tarball. - if ($name - =~ /^(?:\Q$base\E\.orig(?:-(.*))?|\Q$baserev\E)\.tar\.(?:gz|bz2|lzma|xz)$/ - ) { - $components{$name} = $1 // EMPTY; - } - } - - return \%components; - }); - -=back - -=head1 AUTHOR - -Originally written by Adam D. Barratt for Lintian. - -=head1 SEE ALSO - -lintian(1), L - -=cut - -1; - -# Local Variables: -# indent-tabs-mode: nil -# cperl-indent-level: 4 -# End: -# vim: syntax=perl sw=4 sts=4 sr et diff -Nru lintian-2.93.0/lib/Lintian/Processable/Source/Diffstat.pm lintian-2.89.0ubuntu1/lib/Lintian/Processable/Source/Diffstat.pm --- lintian-2.93.0/lib/Lintian/Processable/Source/Diffstat.pm 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/lib/Lintian/Processable/Source/Diffstat.pm 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,150 @@ +# -*- perl -*- +# +# Lintian::Processable::Source::Diffstat -- lintian collection script for source packages + +# Copyright © 1998 Richard Braakman +# Copyright © 2019 Felix Lechner +# +# This program is free software; you can redistribute it and/or modify +# it under the terms of the GNU General Public License as published by +# the Free Software Foundation; either version 2 of the License, or +# (at your option) any later version. +# +# This program is distributed in the hope that it will be useful, +# but WITHOUT ANY WARRANTY; without even the implied warranty of +# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the +# GNU General Public License for more details. +# +# You should have received a copy of the GNU General Public License +# along with this program. If not, you can find it on the World Wide +# Web at http://www.gnu.org/copyleft/gpl.html, or write to the Free +# Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, +# MA 02110-1301, USA. + +# This could be written more easily in shell script, but I'm trying +# to keep everything as perl to cut down on the number of processes +# that need to be started in a lintian scan. Eventually all the +# perl code will be perl modules, so only one perl interpreter +# need be started. + +package Lintian::Processable::Source::Diffstat; + +use v5.20; +use warnings; +use utf8; +use autodie; + +use Path::Tiny; + +use Lintian::Deb822::Parser qw(read_dpkg_control); +use Lintian::IO::Async qw(safe_qx); + +use constant EMPTY => q{}; +use constant UNDERSCORE => q{_}; +use constant NEWLINE => qq{\n}; + +use Moo::Role; +use namespace::clean; + +=head1 NAME + +Lintian::Processable::Source::Diffstat - collect diffstat information + +=head1 SYNOPSIS + + Lintian::Processable::Source::Diffstat::collect(undef, undef, undef); + +=head1 DESCRIPTION + +Lintian::Processable::Source::Diffstat collects diffstat information. + +=head1 INSTANCE METHODS + +=over 4 + +=item add_diffstat + +=cut + +sub add_diffstat { + my ($self) = @_; + + my $dscpath = path($self->groupdir)->child('dsc')->stringify; + die 'diffstat invoked with wrong dir argument' + unless -f $dscpath; + + my $patchpath = path($self->groupdir)->child('debian-patch')->stringify; + unlink($patchpath) + if -e $patchpath + or -l $patchpath; + + my @paragraphs; + @paragraphs = read_dpkg_control($dscpath); + my $data = $paragraphs[0]; + + my $version = $data->{'Version'}; + $version =~ s/^\d://; #Remove epoch for this + + my $diffname = $self->name . UNDERSCORE . $version . '.diff.gz'; + my $diffpath = path($self->groupdir)->child($diffname)->stringify; + return + unless -f $diffpath; + + my $contents = safe_qx('gunzip', '--stdout', $diffpath); + path($patchpath)->spew($contents); + + my $loop = IO::Async::Loop->new; + my $future = $loop->new_future; + + my @command = ('diffstat', '-p1', $patchpath); + $loop->run_child( + command => [@command], + on_finish => sub { + my ($pid, $exitcode, $stdout, $stderr) = @_; + my $status = ($exitcode >> 8); + + if ($status) { + my $message = "Command @command exited with status $status"; + $message .= ": $stderr" if length $stderr; + $future->fail($message); + return; + } + + $future->done($stdout); + }); + + # will raise an exception when failed + my $diffstat = $future->get; + + # remove the last line; + chomp $diffstat; + my @lines = split(/\n/, $diffstat); + pop @lines; + $diffstat = EMPTY; + $diffstat .= $_ . NEWLINE for @lines; + + # copy all lines except the last + path($self->groupdir)->child('diffstat')->spew($diffstat); + + return; +} + +=back + +=head1 AUTHOR + +Originally written by Richard Braakman for Lintian. + +=head1 SEE ALSO + +lintian(1) + +=cut + +1; + +# Local Variables: +# indent-tabs-mode: nil +# cperl-indent-level: 4 +# End: +# vim: syntax=perl sw=4 sts=4 sr et diff -Nru lintian-2.93.0/lib/Lintian/Processable/Source/Format.pm lintian-2.89.0ubuntu1/lib/Lintian/Processable/Source/Format.pm --- lintian-2.93.0/lib/Lintian/Processable/Source/Format.pm 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/lib/Lintian/Processable/Source/Format.pm 2020-08-10 09:59:45.000000000 +0000 @@ -104,7 +104,7 @@ $version =~ s/^\d+://; my $diffname = $self->name . UNDERSCORE . "$version.diff.gz"; - my $diffpath = path($self->basedir)->child($diffname)->stringify; + my $diffpath = path($self->groupdir)->child($diffname)->stringify; return 0 if -f $diffpath; diff -Nru lintian-2.93.0/lib/Lintian/Processable/Source.pm lintian-2.89.0ubuntu1/lib/Lintian/Processable/Source.pm --- lintian-2.93.0/lib/Lintian/Processable/Source.pm 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/lib/Lintian/Processable/Source.pm 2020-08-10 09:59:45.000000000 +0000 @@ -24,12 +24,10 @@ use autodie; use Carp qw(croak); -use File::Spec; use Path::Tiny; use Lintian::Deb822::File; -use constant EMPTY => q{}; use constant COLON => q{:}; use constant SLASH => q{/}; @@ -46,7 +44,7 @@ 'Lintian::Processable::Orig', 'Lintian::Processable::Overrides', 'Lintian::Processable::Patched', - 'Lintian::Processable::Source::Components', + 'Lintian::Processable::Source::Diffstat', 'Lintian::Processable::Source::Format', 'Lintian::Processable::Source::Relation', 'Lintian::Processable::Source::Repacked'; @@ -135,21 +133,12 @@ sub unpack { my ($self) = @_; - my $parent = path($self->path)->parent->stringify; - - # pull in all related files for unpacking - for my $basename (keys %{$self->files}) { - - symlink("$parent/$basename", $self->basedir . "/$basename") - or die "cannot symlink file $basename: $!"; - } - - $self->patched->collect($self->basedir); + $self->patched->collect($self->groupdir); $self->add_diffstat; $self->add_overrides; - $self->orig->collect($self->basedir, $self->components) + $self->orig->collect($self->groupdir) unless $self->native; return; diff -Nru lintian-2.93.0/lib/Lintian/Processable/Udeb.pm lintian-2.89.0ubuntu1/lib/Lintian/Processable/Udeb.pm --- lintian-2.93.0/lib/Lintian/Processable/Udeb.pm 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/lib/Lintian/Processable/Udeb.pm 2020-08-10 09:59:45.000000000 +0000 @@ -25,7 +25,7 @@ use Carp qw(croak); use Path::Tiny; -use Lintian::IPC::Run3 qw(get_deb_info); +use Lintian::IO::Async qw(get_deb_info); use constant COLON => q{:}; use constant SLASH => q{/}; diff -Nru lintian-2.93.0/lib/Lintian/Processable.pm lintian-2.89.0ubuntu1/lib/Lintian/Processable.pm --- lintian-2.93.0/lib/Lintian/Processable.pm 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/lib/Lintian/Processable.pm 2020-08-10 09:59:45.000000000 +0000 @@ -30,7 +30,6 @@ use constant EMPTY => q{}; use constant COLON => q{:}; use constant SLASH => q{/}; -use constant UNDERSCORE => q{_}; use constant EVIL_CHARACTERS => qr,[/&|;\$"'<>],; @@ -121,7 +120,7 @@ Returns a reference to lab this Processable is in. -=item $proc->basedir +=item $proc->groupdir Returns the base directory of this package inside the lab. @@ -129,6 +128,10 @@ Returns a reference to the extra fields related to this entry. +=item saved_link + +Returns a reference to the extra fields related to this entry. + =cut has path => (alias => 'pkg_path', is => 'rw', default => EMPTY); @@ -185,30 +188,10 @@ has fields => (is => 'rw', default => sub { Lintian::Deb822::Section->new; }); has pooldir => (is => 'rw', default => EMPTY); -has basedir => ( - is => 'rw', - lazy => 1, - default => sub { - my ($self) = @_; - - my $path - = $self->source. SLASH. $self->name. UNDERSCORE. $self->version; - $path .= UNDERSCORE . $self->architecture - unless $self->type eq 'source'; - $path .= UNDERSCORE . $self->type; - - # architectures can contain spaces in changes files - $path =~ s/\s/-/g; - - # colon can be a path separator - $path =~ s/:/_/g; - - my $basedir = $self->pooldir . "/$path"; - - return $basedir; - }); +has groupdir => (is => 'rw', default => EMPTY); has link_label => (is => 'rw', default => EMPTY); +has saved_link => (is => 'rw', default => EMPTY); =item C @@ -241,8 +224,8 @@ sub remove { my ($self) = @_; - path($self->basedir)->remove_tree - if -e $self->basedir; + path($self->groupdir)->remove_tree + if -e $self->groupdir; return; } @@ -284,22 +267,48 @@ =cut -has link => ( - is => 'rw', - lazy => 1, - default => sub { - my ($self) = @_; +sub link { + my ($self) = @_; + + unless (length $self->saved_link) { croak 'Please set base directory for processable first' - unless length $self->basedir; + unless length $self->groupdir; croak 'Please set link label for processable first' unless length $self->link_label; - my $link = path($self->basedir)->child($self->link_label)->stringify; + my $link = path($self->groupdir)->child($self->link_label)->stringify; + $self->saved_link($link); + } + + return $self->saved_link; +} + +=item create + +Creates a link to the input file near where all files in that +group will be unpacked and analyzed. + +=cut + +sub create { + my ($self) = @_; + + return + if -l $self->link; + + croak 'Please set base directory for processable first' + unless length $self->groupdir; + + path($self->groupdir)->mkpath + unless -e $self->groupdir; - return $link; - }); + symlink($self->path, $self->link) + or croak 'symlinking ' . $self->path . "failed: $!"; + + return; +} =item guess_name diff -Nru lintian-2.93.0/lib/Lintian/Profile.pm lintian-2.89.0ubuntu1/lib/Lintian/Profile.pm --- lintian-2.93.0/lib/Lintian/Profile.pm 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/lib/Lintian/Profile.pm 2020-08-10 09:59:45.000000000 +0000 @@ -1,6 +1,6 @@ # Copyright © 2011 Niels Thykier +# Copyright © 2020 Felix Lechner # Copyright © 2018 Chris Lamb -# Copyright © 2020 Felix Lechner # # This program is free software; you can redistribute it and/or modify # it under the terms of the GNU General Public License as published by @@ -27,13 +27,12 @@ use Carp qw(croak); use File::Find::Rule; use List::Compare; -use List::MoreUtils qw(any none uniq first_value); +use List::MoreUtils qw(any none uniq); use Path::Tiny; use Dpkg::Vendor qw(get_current_vendor get_vendor_info); use Lintian::Check::Info; -use Lintian::Data; use Lintian::Deb822::File; use Lintian::Tag::Info; @@ -158,33 +157,10 @@ coerce => sub { my ($arrayref) = @_; return ($arrayref // []); }, default => sub { [] }); -has known_vendors => ( +has vendor_cache => ( is => 'rw', - lazy => 1, coerce => sub { my ($arrayref) = @_; return ($arrayref // []); }, - default => sub { - - my $vendor = Dpkg::Vendor::get_current_vendor(); - croak 'Could not determine the current vendor' - unless $vendor; - - my @vendors; - push(@vendors, lc $vendor); - - while ($vendor) { - my $info = Dpkg::Vendor::get_vendor_info($vendor); - # Cannot happen atm, but in case Dpkg::Vendor changes its internals - # or our code changes - croak "Could not look up the parent vendor of $vendor" - unless $info; - - $vendor = $info->{'Parent'}; - push(@vendors, lc $vendor) - if $vendor; - } - - return \@vendors; - }); + default => sub { [] }); =item load ([$profname[, $ipath[, $extra]]]) @@ -200,41 +176,47 @@ =cut sub load { - my ($self, $name, $include_path, $extra) = @_; + my ($self, $name, $ipath, $extra) = @_; - my @full_inc_path; + my ($profile, @full_inc_path); - unless (defined $include_path) { + unless (defined $ipath) { # Temporary fix (see _safe_include_path) - push(@full_inc_path, "$ENV{'HOME'}/.lintian") - if length $ENV{'HOME'}; - - push(@full_inc_path, '/etc/lintian'); - - # ENV{LINTIAN_BASE} replaces /usr/share/lintian if present. - $include_path = [$ENV{LINTIAN_BASE} // '/usr/share/lintian']; - - push(@full_inc_path, @{$include_path}); + @full_inc_path = (_default_inc_path()); + $ipath = [$ENV{LINTIAN_BASE} // '/usr/share/lintian']; } - push(@full_inc_path, @{ $extra->{'restricted-search-dirs'} // [] }) - if defined $extra; - - push(@full_inc_path, @{$include_path}); + if (defined $extra) { + if (exists($extra->{'restricted-search-dirs'})) { + @full_inc_path = @{ $extra->{'restricted-search-dirs'} }; + } + } + push @full_inc_path, @$ipath; $self->saved_include_path(\@full_inc_path); - $self->saved_safe_include_path($include_path); + $self->saved_safe_include_path($ipath); - Lintian::Data->set_vendor($self); + if (defined $name) { + croak "Illegal profile name $name" + if $name =~ m{^/} + || $name =~ m{\.}; + ($profile, undef) = $self->_find_vendor_profile($name); + } else { + ($profile, $name) = $self->_find_vendor_profile; + } + + croak "Cannot find profile $name (in " + . join(', ', map { "$_/profiles" } @$ipath).')' + unless $profile; - for my $tagdir ($self->_safe_include_path('tags')) { + # populate known tags and their check associations + for my $tagroot ($self->_safe_include_path('tags')) { next - unless -d $tagdir; + unless -d $tagroot; - my @tagpaths - = File::Find::Rule->file->name(qw(*.tag *.desc))->in($tagdir); - for my $tagpath (@tagpaths) { + my @descfiles = File::Find::Rule->file()->name('*.desc')->in($tagroot); + for my $tagpath (@descfiles) { my $taginfo = Lintian::Tag::Info->new; $taginfo->load($tagpath); @@ -242,52 +224,42 @@ die "Tag in $tagpath is not associated with a check" unless length $taginfo->check; - next - if exists $self->known_tags_by_name->{$taginfo->name}; - - $self->known_tags_by_name->{$taginfo->name} = $taginfo; - $self->check_tagnames->{$taginfo->check} //= []; - push(@{$self->check_tagnames->{$taginfo->check}},$taginfo->name); + unless (exists $self->known_tags_by_name->{$taginfo->name}) { + $self->known_tags_by_name->{$taginfo->name} = $taginfo; + push( + @{$self->check_tagnames->{$taginfo->check}}, + $taginfo->name + ); + } } } - for my $checkdir ($self->_safe_include_path('checks')) { + my @checkdirs = grep { -d $_ } $self->_safe_include_path('checks'); - next - unless -d $checkdir; + for my $checkdir (@checkdirs) { - my @checkpaths= File::Find::Rule->file->name('*.pm')->in($checkdir); + my @descpaths= File::Find::Rule->file->name('*.pm')->in($checkdir); - for my $checkpath (@checkpaths) { - my $relative = path($checkpath)->relative($checkdir)->stringify; + for my $desc (@descpaths) { + my $relative = path($desc)->relative($checkdir)->stringify; my ($name) = ($relative =~ qr/^(.*)\.pm$/); - - # ignore duplicates - next - if exists $self->known_checks_by_name->{$name}; - - my $check = Lintian::Check::Info->new; - $check->basedir($checkdir); - $check->name($name); - $check->load; - - $self->known_checks_by_name->{$name} = $check; + # _parse_check ignores duplicates on its own + $self->_parse_check($name, $checkdir); } } - # add internal 'lintian' check to allow issuance of such tags + # load internal 'lintian' check to allow issuance of such tags my $lintian = Lintian::Check::Info->new; $lintian->name('lintian'); $self->known_checks_by_name->{lintian} = $lintian; - $self->read_profile($name); + $self->_read_profile($profile); # record known aliases for my $taginfo (values %{ $self->known_tags_by_name }) { my @taken - = grep { defined $self->known_aliases->{$_} } - @{$taginfo->renamed_from}; + = grep { defined $self->known_aliases->{$_} } @{$taginfo->aliases}; die 'These aliases of the tag ' . $taginfo->name @@ -295,11 +267,10 @@ . join(SPACE, @taken) if @taken; - $self->known_aliases->{$_} = $taginfo->name - for @{$taginfo->renamed_from}; + $self->known_aliases->{$_} = $taginfo->name for @{$taginfo->aliases}; } - return; + return $self; } =item $prof->known_tags @@ -459,37 +430,40 @@ return @{ $self->saved_safe_include_path }; } -=item read_profile - -=cut - -sub read_profile { - my ($self, $requested_name) = @_; - - my @search_space; - - if (!defined $requested_name) { - @search_space = map { "$_/main" } @{$self->known_vendors}; +# $prof->_find_profile ($name) +# +# Finds a profile called $name in the search directories and returns +# the path to it. If $name does not contain a slash, then it will look +# for a profile called "$name/main" instead of $name. +# +# Returns a non-truth value if the profile could not be found. $name +# cannot contain any dots. - } elsif ($requested_name !~ m{/}) { - @search_space = ("$requested_name/main"); +sub _find_profile { + my ($self, $name) = @_; - } elsif ($requested_name =~ m{^[^.]+/[^/.]+$}) { - @search_space = ($requested_name); + croak "$name is not a valid profile name" + if $name =~ m{\.}; - } else { - croak "$requested_name is not a valid profile name"; - } + # $vendor is short for $vendor/main + $name = "$name/main" + unless $name =~ m{/}; - my @candidates; - for my $include_path ($self->include_path('profiles')) { - push(@candidates, map { "$include_path/$_.profile" } @search_space); + my $filename = "$name.profile"; + foreach my $path ($self->include_path('profiles')) { + return "$path/$filename" + if -e "$path/$filename"; } - my $path = first_value { -e } @candidates; + return EMPTY; +} - croak 'Could not find a profile matching: ' . join(SPACE, @search_space) - unless length $path; +# $self->_read_profile($path) +# +# Parses the profile stored in the file $path; if this method returns +# normally, the profile will have been parsed successfully. +sub _read_profile { + my ($self, $path) = @_; my $deb822 = Lintian::Deb822::File->new; my @paragraphs = $deb822->read_file($path); @@ -499,7 +473,7 @@ croak "Profile has no header in $path" unless defined $header; - my $name = $header->unfolded_value('Profile'); + my $name = neat_value($header->value('Profile')); croak "Profile has no name in $path" unless length $name; @@ -513,37 +487,146 @@ croak "Recursive definition of $name" if exists $self->parent_map->{$name}; - # Mark as being loaded. - $self->parent_map->{$name} = 0; + $self->parent_map->{$name} = 0; # Mark as being loaded. $self->name($name) unless length $self->name; - $self->read_profile($header->unfolded_value('Extends')) - if $header->exists('Extends'); + my $parentname = neat_value($header->value('Extends')); + if (length $parentname){ + croak "Invalid Extends field in $path" + if $parentname =~ m{\.}; + + my ($parentpath, undef) = $self->_find_vendor_profile($parentname); + croak "Cannot find $parentname, which $name extends" + unless $parentpath; + + $self->_read_profile($parentpath); + } # Add the profile to the "chain" after loading its parent (if # any). push(@{$self->profile_list}, $name); + $self->_read_profile_tags($name, $header); + + my $counter = 2; # section counter + for my $section (@sections){ + $self->_read_profile_section($name, $section, $counter++); + } + + return; +} + +=item neat_value + +=cut + +sub neat_value { + my ($input) = @_; + + return EMPTY + unless length $input; + + my $output = $input; + + # unwrap continuation lines + $output =~ s/\n/ /g; + + # trim both ends + $output =~ s/^\s+|\s+$//g; + + # reduce multiple spaces to one + $output =~ s/\s+/ /g; + + return $output; +} + +# $self->_read_profile_section($profile, $section, $position) +# +# Parses and applies the effects of $section (a paragraph +# in the profile). $profile is the name of the profile and +# $no is section number (both of these are only used for +# error reporting). +sub _read_profile_section { + my ($self, $profile, $section, $position) = @_; + + my @valid_fields = qw(Tags Overridable Severity); + my @unknown_fields = $section->extra(@valid_fields); + croak "Unknown fields in section $position of profile $profile: " + . join(SPACE, @unknown_fields) + if @unknown_fields; + + my @tags = split(/\s*,\s*/, neat_value($section->value('Tags'))); + croak + "Tags field missing or empty in section $position of profile $profile" + unless @tags; + + my $severity = neat_value($section->value('Severity')); + croak +"Profile $profile contains invalid severity $severity in section $position" + if length $severity && none { $severity eq $_ } + @Lintian::Tag::Info::SEVERITIES; + + my $overridable + = $self->_parse_boolean(neat_value($section->value('Overridable')), + -1, $profile,$position); + + foreach my $tag (@tags) { + + my $taginfo = $self->known_tags_by_name->{$tag}; + croak "Unknown check $tag in $profile (section $position)" + unless defined $taginfo; + + croak +"Classification tag $tag cannot take a severity (profile $profile, section $position" + if $taginfo->original_severity eq 'classification'; + + $taginfo->effective_severity($severity) + if length $severity; + + if ($overridable != -1) { + if ($overridable) { + delete $self->non_overridable_tags->{$tag}; + } else { + $self->non_overridable_tags->{$tag} = 1; + } + } + } + + return; +} + +# $self->_read_profile_tags($profile, $header) +# +# Interprets the {dis,en}able-tags{,-from-check} fields from +# the profile header $header. $profile is the name of the +# profile (used for error reporting). +# +# If it returns, the enabled tags will be updated to reflect +# the tags enabled/disabled by this profile (but not its +# parents). +sub _read_profile_tags{ + my ($self, $profile, $header) = @_; + my @valid_fields = qw(Profile Extends Enable-Tags-From-Check Disable-Tags-From-Check Enable-Tags Disable-Tags); my @unknown_fields = $header->extra(@valid_fields); - croak "Unknown fields in header of profile $name: " + croak "Unknown fields in header of profile $profile: " . join(SPACE, @unknown_fields) if @unknown_fields; my @enable_checks - = $header->trimmed_list('Enable-Tags-From-Check', qr/\s*,\s*/); + = split(/\s*,\s*/,neat_value($header->value('Enable-Tags-From-Check'))); my @disable_checks - = $header->trimmed_list('Disable-Tags-From-Check', qr/\s*,\s*/); + = split(/\s*,\s*/,neat_value($header->value('Disable-Tags-From-Check'))); # List::MoreUtils has 'duplicates' starting at 0.423 my @allchecks = (@enable_checks, @disable_checks); my %count; $count{$_}++ for @allchecks; my @duplicate_checks = grep { $count{$_} > 1 } keys %count; - die "These checks appear in profile $name more than once: " + die "These checks appear in profile $profile more than once: " . join(SPACE, @duplicate_checks) if @duplicate_checks; @@ -551,35 +634,24 @@ my @needed_checks = grep { !exists $self->known_checks_by_name->{$_} } @allchecks; - for my $name (@needed_checks) { + for my $check (@needed_checks) { my $location; for my $directory ($self->_safe_include_path('checks')) { - if (-f "$directory/$name.desc") { + if (-f "$directory/$check.desc") { $location = $directory; last; } } - croak "Profile $name references unknown check $name" + croak "Profile $profile references unknown check $check" unless defined $location; - # ignore duplicates - next - if exists $self->known_checks_by_name->{$name}; - - my $info = Lintian::Check::Info->new; - $info->basedir($location); - $info->name($name); - $info->load; - - $self->known_checks_by_name->{$name} = $info; + my $check = $self->_parse_check($check, $location); } # associate tags with checks for my $check (values %{ $self->known_checks_by_name }) { - - $self->check_tagnames->{$check->name} //= []; my @tagnames = @{$self->check_tagnames->{$check->name}}; my @taginfos = map { $self->known_tags_by_name->{$_} } @tagnames; @@ -588,15 +660,17 @@ $check->add_taginfo($_) for @taginfos; } - my @enable_tags = $header->trimmed_list('Enable-Tags', qr/\s*,\s*/); - my @disable_tags = $header->trimmed_list('Disable-Tags', qr/\s*,\s*/); + my @enable_tags + = split(/\s*,\s*/, neat_value($header->value('Enable-Tags'))); + my @disable_tags + = split(/\s*,\s*/, neat_value($header->value('Disable-Tags'))); # List::MoreUtils has 'duplicates' starting at 0.423 my @alltags = (@enable_tags, @disable_tags); %count = (); $count{$_}++ for @alltags; my @duplicate_tags = grep { $count{$_} > 1 } keys %count; - die "These tags appear in in profile $name more than once: " + die "These tags appear in in profile $profile more than once: " . join(SPACE, @duplicate_tags) if @duplicate_tags; @@ -609,64 +683,12 @@ my @unknown_tags = grep { !exists $self->known_tags_by_name->{$_} } uniq(@enable_tags, @disable_tags); - croak "Unknown tags in profile $name: " . join(SPACE, @unknown_tags) + croak "Unknown tags in profile $profile: " . join(SPACE, @unknown_tags) if @unknown_tags; $self->enable_tag($_) for @enable_tags; $self->disable_tag($_) for @disable_tags; - # section counter - my $position = 2; - - for my $section (@sections){ - - my @valid_fields = qw(Tags Overridable Severity); - my @unknown_fields = $section->extra(@valid_fields); - croak "Unknown fields in section $position of profile $name: " - . join(SPACE, @unknown_fields) - if @unknown_fields; - - my @tags = $section->trimmed_list('Tags', qr/\s*,\s*/); - croak - "Tags field missing or empty in section $position of profile $name" - unless @tags; - - my $severity = $section->unfolded_value('Severity'); - croak -"Profile $name contains invalid severity $severity in section $position" - if length $severity && none { $severity eq $_ } - @Lintian::Tag::Info::SEVERITIES; - - my $overridable - = $self->_parse_boolean($section->unfolded_value('Overridable'), - -1, $name,$position); - - for my $tagname (@tags) { - - my $taginfo = $self->known_tags_by_name->{$tagname}; - croak "Unknown tag $tagname in $name (section $position)" - unless defined $taginfo; - - croak -"Classification tag $tagname cannot take a severity (profile $name, section $position" - if $taginfo->visibility eq 'classification'; - - $taginfo->effective_severity($severity) - if length $severity; - - if ($overridable != -1) { - if ($overridable) { - delete $self->non_overridable_tags->{$tagname}; - } else { - $self->non_overridable_tags->{$tagname} = 1; - } - } - } - - } continue { - $position++; - } - return; } @@ -695,6 +717,96 @@ croak "$text is not a boolean value in $profile (section $position)"; } +sub _parse_check { + my ($self, $name, $directory) = @_; + + return $self->known_checks_by_name->{$name} + if exists $self->known_checks_by_name->{$name}; + + my $check = Lintian::Check::Info->new; + $check->basedir($directory); + $check->name($name); + $check->load; + + $self->known_checks_by_name->{$name} = $check; + + # needed for checks without tags + $self->check_tagnames->{$name} //= []; + + return $check; +} + +sub _default_inc_path { + my @path; + + push(@path, "$ENV{'HOME'}/.lintian") + if length $ENV{'HOME'}; + + push(@path, '/etc/lintian'); + + # ENV{LINTIAN_BASE} replaces /usr/share/lintian if present. + push(@path, $ENV{LINTIAN_BASE} // '/usr/share/lintian'); + + return @path; +} + +sub _find_vendor_profile { + my ($self, $prof) = @_; + my @vendors; + + if (defined $prof and $prof !~ m/[{}]/) { + # no substitution required... + return ($self->_find_profile($prof), $prof); + + } elsif (defined $prof) { + my $cpy = $prof; + # Check for unknown (or broken) subst. + $cpy =~ s/\Q{VENDOR}\E//g; + croak "Unknown substitution \"$1\" (in \"$prof\")" + if $cpy =~ m/\{([^ \}]+)\}/; + croak "Bad, broken or empty substitution marker in \"$prof\"" + if $cpy =~ m/[{}]/; + } + + $prof //= '{VENDOR}/main'; + + @vendors = @{ $self->vendor_cache }; + unless (@vendors) { + + my $vendor = Dpkg::Vendor::get_current_vendor(); + croak 'Could not determine the current vendor' + unless $vendor; + + push(@vendors, lc $vendor); + while ($vendor) { + my $info = Dpkg::Vendor::get_vendor_info($vendor); + # Cannot happen atm, but in case Dpkg::Vendor changes its internals + # or our code changes + croak "Could not look up the parent vendor of $vendor" + unless $info; + + $vendor = $info->{'Parent'}; + push(@vendors, lc $vendor) + if $vendor; + } + + $self->vendor_cache(\@vendors); + } + + foreach my $vendor (@vendors) { + + my $profname = $prof; + $profname =~ s/\Q{VENDOR}\E/$vendor/g; + + my $file = $self->_find_profile($profname); + + return ($file, $profname) + if $file; + } + + croak "Could not find a profile matching $prof for vendor $vendors[0]"; +} + =item display_level_for_tag =cut diff -Nru lintian-2.93.0/lib/Lintian/Tag/Info.pm lintian-2.89.0ubuntu1/lib/Lintian/Tag/Info.pm --- lintian-2.93.0/lib/Lintian/Tag/Info.pm 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/lib/Lintian/Tag/Info.pm 2020-08-10 09:59:45.000000000 +0000 @@ -29,15 +29,12 @@ use Lintian::Data; use Lintian::Deb822::File; +use Lintian::Tag::TextUtil + qw(dtml_to_html dtml_to_text split_paragraphs wrap_paragraphs); use constant EMPTY => q{}; use constant SPACE => q{ }; use constant SLASH => q{/}; -use constant COMMA => q{,}; -use constant LEFT_PARENTHESIS => q{(}; -use constant RIGHT_PARENTHESIS => q{)}; - -use constant PARAGRAPH_BREAK => qq{\n\n}; use Moo; use namespace::clean; @@ -45,25 +42,18 @@ # Ordered lists of severities, used for display level parsing. our @SEVERITIES= qw(classification pedantic info warning error); -# loads the first time info is called +# The URL to a web man page service. NAME is replaced by the man page +# name and SECTION with the section to form a valid URL. This is used +# when formatting references to manual pages into HTML to provide a link +# to the manual page. +our $MANURL + = 'https://manpages.debian.org/cgi-bin/man.cgi?query=NAME&sektion=SECTION'; + +# Stores the parsed manual reference data. Loaded the first time info() +# is called. our $MANUALS = Lintian::Data->new('output/manual-references', qr/::/,\&_load_manual_data); -sub _load_manual_data { - my ($key, $rawvalue, $pval) = @_; - - my ($section, $title, $url) = split m/::/, $rawvalue, 3; - my $ret; - if (not defined $pval) { - $ret = $pval = {}; - } - - $pval->{$section}{title} = $title; - $pval->{$section}{url} = $url; - - return $ret; -} - =head1 NAME Lintian::Tag::Info - Lintian interface to tag metadata @@ -84,7 +74,7 @@ =item tag -=item visibility +=item original_severity =item effective_severity @@ -96,11 +86,11 @@ =item experimental -=item explanation +=item info -=item see_also +=item references -=item renamed_from +=item aliases =cut @@ -110,7 +100,7 @@ default => EMPTY ); -has visibility => ( +has original_severity => ( is => 'rw', lazy => 1, coerce => sub { @@ -164,18 +154,19 @@ default => 0 ); -has explanation => ( +has info => ( is => 'rw', coerce => sub { my ($text) = @_; return ($text // EMPTY); }, default => EMPTY ); -has see_also => ( +has references => ( is => 'rw', - coerce => sub { my ($arrayref) = @_; return ($arrayref // []); }, - default => sub { [] }); + coerce => sub { my ($text) = @_; return ($text // EMPTY); }, + default => EMPTY +); -has renamed_from => ( +has aliases => ( is => 'rw', coerce => sub { my ($arrayref) = @_; return ($arrayref // []); }, default => sub { [] }); @@ -208,26 +199,18 @@ $self->name($name); - $self->visibility($fields->value('Severity')); + $self->original_severity($fields->value('Severity')); $self->experimental($fields->value('Experimental') eq 'yes'); - $self->explanation($fields->text('Explanation') || $fields->text('Info')); - - my @see_also - = split(/,/, $fields->value('See-Also') || $fields->value('Ref')); - - # trim both ends of each - s/^\s+|\s+$//g for @see_also; + $self->info($fields->value('Info')); + $self->references($fields->value('Ref')); - my @markdown = map { markdown_citation($_) } @see_also; - $self->see_also(\@markdown); - - $self->renamed_from([$fields->trimmed_list('Renamed-From')]); + $self->aliases([$fields->trimmed_list('Renamed-From')]); croak "No Tag field in $tagpath" unless length $self->name; - $self->effective_severity($self->visibility); + $self->effective_severity($self->original_severity); return; } @@ -257,162 +240,147 @@ return $CODES{$self->effective_severity}; } -=item markdown_description +=item description([FORMAT [, INDENT]]) -=cut +Returns the formatted description (the Info field) for a tag. FORMAT must +be either C or C and defaults to C if no format is +specified. If C, returns wrapped paragraphs formatted in plain text +with a right margin matching the Text::Wrap default, preserving as +verbatim paragraphs that begin with whitespace. If C, return +paragraphs formatted in HTML. -sub markdown_description { - my ($self) = @_; - - my $description = $self->explanation; - - my @extras; - - my $references = $self->markdown_reference_statement; - push(@extras, $references) - if length $references; - - push(@extras, 'Severity: '. $self->visibility); - - push(@extras, 'Check: ' . $self->check) - if length $self->check; - - push(@extras, 'Renamed from: ' . join(SPACE, @{$self->renamed_from})) - if @{$self->renamed_from}; - - push(@extras, 'This tag is experimental.') - if $self->experimental; - - push(@extras, - 'This tag is a classification. There is no issue in your package.') - if $self->visibility eq 'classification'; - - $description .= PARAGRAPH_BREAK . $_ for @extras; - - return $description; -} - -=item markdown_reference_statement +If INDENT is specified, the string INDENT is prepended to each line of the +formatted output. =cut -sub markdown_reference_statement { - my ($self) = @_; - - my @references = @{$self->see_also}; - - return EMPTY - unless @references; - - # remove and save last element - my $last = pop @references; - - my $text = EMPTY; - my $oxfordcomma = (@references > 1 ? COMMA : EMPTY); - $text = join(', ', @references) . "$oxfordcomma and " - if @references; - - $text .= $last; - - return "Refer to $text for details."; +# Parse manual reference data from the data file. +sub _load_manual_data { + my ($key, $rawvalue, $pval) = @_; + my ($section, $title, $url) = split m/::/, $rawvalue, 3; + my $ret; + if (not defined $pval) { + $ret = $pval = {}; + } + $pval->{$section}{title} = $title; + $pval->{$section}{url} = $url; + return $ret; } -=item markdown_citation - -=cut - -sub markdown_citation { - my ($citation) = @_; - - my $markdown; - - if ($citation =~ /^([\w-]+)\s+(.+)$/) { - $markdown = markdown_from_manuals($1, $2); +# Format a reference to a manual in the HTML that Lintian uses internally +# for tag descriptions and return the result. Takes the name of the +# manual and the name of the section. Returns an empty string if the +# argument isn't a known manual. +sub _manual_reference { + my ($manual, $section) = @_; + return '' unless $MANUALS->known($manual); + + my $man = $MANUALS->value($manual); + # Start with the reference to the overall manual. + my $title = $man->{''}{title}; + my $url = $man->{''}{url}; + my $text = $url ? qq($title) : $title; - } elsif ($citation =~ /^([\w.-]+)\((\d\w*)\)$/) { - my ($name, $section) = ($1, $2); - my $url - ="https://manpages.debian.org/cgi-bin/man.cgi?query=$name&sektion=$section"; - my $hyperlink = markdown_hyperlink($citation, $url); - $markdown = "the $hyperlink manual page"; - - } elsif ($citation =~ m{^(ftp|https?)://}) { - $markdown = markdown_hyperlink(undef, $citation); - - } elsif ($citation =~ m{^/}) { - $markdown = markdown_hyperlink($citation, "file://$citation"); - - } elsif ($citation =~ m{^(?:Bug)?#(\d+)$}) { - my $bugnumber = $1; - $markdown - = markdown_hyperlink($citation,"https://bugs.debian.org/$bugnumber"); + # Add the section information, if present, and a direct link to that + # section of the manual where possible. + if ($section and $section =~ /^[A-Z]+$/) { + $text .= " appendix $section"; + } elsif ($section and $section =~ /^\d+$/) { + $text .= " chapter $section"; + } elsif ($section and $section =~ /^[A-Z\d.]+$/) { + $text .= " section $section"; + } + if ($section and exists $man->{$section}) { + my $sec_title = $man->{$section}{title}; + my $sec_url = $man->{$section}{url}; + $text.= + $sec_url + ? qq[ ($sec_title)] + : qq[ ($sec_title)]; } - return $markdown // $citation; + return $text; } -=item markdown_from_manuals - -=cut - -sub markdown_from_manuals { - my ($volume, $section) = @_; - - return EMPTY - unless $MANUALS->known($volume); - - my $entry = $MANUALS->value($volume); - - # start with the citation to the overall manual. - my $title = $entry->{''}{title}; - my $url = $entry->{''}{url}; - - my $markdown = markdown_hyperlink($title, $url); +# Format the contents of the Ref attribute of a tag. Handles manual +# references in the form
, manpage references in the +# form (
), and URLs. +sub _format_reference { + my ($field) = @_; + my @refs; + for my $ref (split(/,\s*/, $field)) { + my $text; + if ($ref =~ /^([\w-]+)\s+(.+)$/) { + $text = _manual_reference($1, $2); + } elsif ($ref =~ /^([\w.-]+)\((\d\w*)\)$/) { + my ($name, $section) = ($1, $2); + my $url = $MANURL; + $url =~ s/NAME/$name/g; + $url =~ s/SECTION/$section/g; + $text = qq(the $ref manual page); + } elsif ($ref =~ m,^(ftp|https?)://,) { + $text = qq($ref); + } elsif ($ref =~ m,^/,) { + $text = qq($ref); + } elsif ($ref =~ m,^#(\d+)$,) { + my $url = qq(https://bugs.debian.org/$1); + $text = qq($url); + } + push(@refs, $text) if $text; + } - return $markdown - unless length $section; + # Now build an English list of the results with appropriate commas and + # conjunctions. + my $text = ''; + if ($#refs >= 2) { + $text = join(', ', splice(@refs, 0, $#refs)); + $text = "Refer to $text, and @refs for details."; + } elsif ($#refs >= 0) { + $text = 'Refer to ' . join(' and ', @refs) . ' for details.'; + } + return $text; +} - # Add the section information, if present, and a direct link to that - # section of the manual where possible. - if ($section =~ /^[A-Z]+$/) { - $markdown .= " appendix $section"; +# Returns the formatted tag description. +sub description { + my ($self, $format, $indent) = @_; - } elsif ($section =~ /^\d+$/) { - $markdown .= " chapter $section"; + $format //= 'text'; + croak "unknown output format $format" + unless $format eq 'text' || $format eq 'html'; - } elsif ($section =~ /^[A-Z\d.]+$/) { - $markdown .= " section $section"; - } + # build tag description + my $info = $self->info; - return $markdown - unless exists $entry->{$section}; + # remove leading spaces + $info =~ s/\n[ \t]/\n/g; - my $section_title = $entry->{$section}{title}; - my $section_url = $entry->{$section}{url}; + my @paragraphs = split_paragraphs($info); - $markdown - .= SPACE - . LEFT_PARENTHESIS - . markdown_hyperlink($section_title, $section_url) - . RIGHT_PARENTHESIS; + push(@paragraphs, EMPTY, _format_reference($self->references)) + if length $self->references; - return $markdown; -} + push(@paragraphs, EMPTY,'Severity: '. $self->original_severity); -=item markdown_hyperlink + push(@paragraphs, EMPTY, 'Check: ' . $self->check) + if length $self->check; -=cut + push(@paragraphs, + EMPTY, +'This tag is experimental. Please file a bug report if the tag seems wrong.' + )if $self->experimental; -sub markdown_hyperlink { - my ($text, $url) = @_; + push(@paragraphs, + EMPTY, + 'This tag is a classification. There is no issue in your package.') + if $self->original_severity eq 'classification'; - return $text - unless length $url; + $indent //= EMPTY; - return "<$url>" - unless length $text; + return wrap_paragraphs('HTML', $indent, dtml_to_html(@paragraphs)) + if $format eq 'html'; - return "[$text]($url)"; + return wrap_paragraphs($indent, dtml_to_text(@paragraphs)); } =back diff -Nru lintian-2.93.0/lib/Lintian/Tag/TextUtil.pm lintian-2.89.0ubuntu1/lib/Lintian/Tag/TextUtil.pm --- lintian-2.93.0/lib/Lintian/Tag/TextUtil.pm 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/lib/Lintian/Tag/TextUtil.pm 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,277 @@ +# Hey emacs! This is a -*- Perl -*- script! +# Lintian::Tag::TextUtil -- Perl utility functions for lintian + +# Copyright © 1998 Christian Schwarz and Richard Braakman +# +# This program is free software; you can redistribute it and/or modify +# it under the terms of the GNU General Public License as published by +# the Free Software Foundation; either version 2 of the License, or +# (at your option) any later version. +# +# This program is distributed in the hope that it will be useful, +# but WITHOUT ANY WARRANTY; without even the implied warranty of +# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the +# GNU General Public License for more details. +# +# You should have received a copy of the GNU General Public License +# along with this program. If not, you can find it on the World Wide +# Web at http://www.gnu.org/copyleft/gpl.html, or write to the Free +# Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, +# MA 02110-1301, USA. + +package Lintian::Tag::TextUtil; + +use v5.20; +use warnings; +use utf8; + +use Exporter qw(import); +our @EXPORT_OK= qw(split_paragraphs wrap_paragraphs dtml_to_html dtml_to_text); + +# requires wrap() function +use Text::Wrap; + +=head1 NAME + +Lintian::Tag::TextUtil -- text utility functions related to tags + +=head1 SYNOPSIS + + use Lintian::Tag::TextUtil; + +=head1 DESCRIPTION + +A class with text utilities. + +=head1 INSTANCE METHODS + +=over 4 + +=item html_wrap + +=cut + +# html_wrap -- word-wrap a paragraph. The wrap() function from Text::Wrap +# is not suitable, because it chops words that are longer than the line +# length. +sub html_wrap { + my ($lead, @text) = @_; + my @words = split(' ', join(' ', @text)); + # subtract 1 to compensate for the lack of a space before the first word. + my $ll = length($lead) - 1; + my $cnt = 0; + my $r = ''; + + while ($cnt <= $#words) { + if ($ll + 1 + length($words[$cnt]) > 76) { + if ($cnt == 0) { + # We're at the start of a line, and word still does not + # fit. Don't wrap it. + $r .= $lead . shift(@words) . "\n"; + } else { + # start new line + $r .= $lead . join(' ', splice(@words, 0, $cnt)) . "\n"; + $ll = length($lead) - 1; + $cnt = 0; + } + } else { + $ll += 1 + length($words[$cnt]); + $cnt++; + } + } + + if ($#words >= 0) { + # finish last line + $r .= $lead . join(' ', @words) . "\n"; + } + + return $r; +} + +=item split_paragraphs + +=cut + +# split_paragraphs -- splits a bunch of text lines into paragraphs. +# This function returns a list of paragraphs. +# Paragraphs are separated by empty lines. Each empty line is a +# paragraph. Furthermore, indented lines are considered a paragraph. +sub split_paragraphs { + return '' unless (@_); + + my $t = join("\n",@_); + + my ($l,@o); + while ($t) { + $t =~ s/^\.\n/\n/; + # starts with space or empty line? + if (($t =~ s/^([ \t][^\n]*)\n?//) or ($t =~ s/^()\n//)) { + #FLUSH; + if ($l) { + + # trim both ends + $l =~ s/^\s+|\s+$//g; + + $l =~ s/\s++/ /g; + push(@o,$l); + undef $l; + } + # + push(@o,$1); + } + # normal line? + elsif ($t =~ s/^([^\n]*)\n?//) { + $l .= "$1 "; + } + # what else can happen? + else { + die 'internal error in wrap'; + } + } + #FLUSH; + if ($l) { + + # trim both ends + $l =~ s/^\s+|\s+$//g; + + $l =~ s/\s++/ /g; + push(@o,$l); + undef $l; + } + # + + return @o; +} + +=item dtml_to_html + +=cut + +sub dtml_to_html { + my @o; + + my $pre=0; + for $_ (@_) { + s{\&maint\;} + {Lintian maintainer}xsm; + s{\&debdev\;} + {debian-devel}xsm; + + # empty line? + if (/^\s*$/) { + if ($pre) { + push(@o,"\n"); + } + } + # preformatted line? + elsif (/^\s/) { + if (not $pre) { + push(@o,'
');
+                $pre=1;
+            }
+            push(@o,$_);
+        }
+        # normal line
+        else {
+            if ($pre) {
+                my $last = pop @o;
+                $last =~ s,\n?$,
\n,; + push @o, $last; + $pre=0; + } + push(@o,"

$_

\n"); + } + } + if ($pre) { + my $last = pop @o; + $last =~ s,\n?$,\n,; + push @o, $last; + $pre=0; + } + + return @o; +} + +=item dtml_to_text + +=cut + +sub dtml_to_text { + for $_ (@_) { + # substitute Lintian &tags; + s,&maint;,lintian-maint\@debian.org,g; + s,&debdev;,debian-devel\@lists.debian.org,g; + + # substitute HTML + s,,<,g; + s,,>,g; + s,<[^>]+>,,g; + + # substitute HTML &tags; + s,<,<,g; + s,>,>,g; + s,&,\&,g; + + # preformatted? + if (not /^\s/) { + # no. + + s,\s\s+, ,g; + s,^ ,,; + s, $,,; + } + } + + return @_; +} + +=item wrap_paragraphs + +=cut + +# wrap_paragraphs -- wrap paragraphs in dpkg/dselect style. +# indented lines are not wrapped but displayed "as is" +sub wrap_paragraphs { + my $lead = shift; + my $html = 0; + + if ($lead eq 'HTML') { + $html = 1; + $lead = shift; + } + + my $o; + # Tell Text::Wrap that very long "words" (e.g. URLs) should rather + # "overflow" the column width than be broken into multiple lines. + # (#719769) + local $Text::Wrap::huge = 'overflow'; + for my $t (split_paragraphs(@_)) { + # empty or indented line? + if ($t eq '' or $t =~ /^\s/) { + $o .= "$lead$t\n"; + } else { + if ($html) { + $o .= html_wrap($lead, "$t\n"); + } else { + $o .= wrap($lead, $lead, "$t\n"); + } + } + } + return $o; +} + +=back + +=head1 SEE ALSO + +lintian(1) + +=cut + +1; + +# Local Variables: +# indent-tabs-mode: nil +# cperl-indent-level: 4 +# End: +# vim: syntax=perl sw=4 sts=4 sr et diff -Nru lintian-2.93.0/lib/Lintian/Version.pm lintian-2.89.0ubuntu1/lib/Lintian/Version.pm --- lintian-2.93.0/lib/Lintian/Version.pm 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/lib/Lintian/Version.pm 1970-01-01 00:00:00.000000000 +0000 @@ -1,105 +0,0 @@ -# -# Copyright © 1998 Christian Schwarz and Richard Braakman -# Copyright © 2013 Niels Thykier -# Copyright © 2017 Chris Lamb -# Copyright © 2020 Felix Lechner -# -# This program is free software; you can redistribute it and/or modify -# it under the terms of the GNU General Public License as published by -# the Free Software Foundation; either version 2 of the License, or -# (at your option) any later version. -# -# This program is distributed in the hope that it will be useful, -# but WITHOUT ANY WARRANTY; without even the implied warranty of -# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the -# GNU General Public License for more details. -# -# You should have received a copy of the GNU General Public License -# along with this program. If not, you can find it on the World Wide -# Web at http://www.gnu.org/copyleft/gpl.html, or write to the Free -# Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, -# MA 02110-1301, USA. - -package Lintian::Version; - -use v5.20; -use warnings; -use utf8; - -our @EXPORT_OK = (qw( - guess_version -)); - -use Exporter qw(import); - -use Lintian::IPC::Run3 qw(safe_qx); -use Lintian::Util qw(version_from_changelog); - -use constant EMPTY => q{}; - -=head1 NAME - -Lintian::Version - routines to determine Lintian version - -=head1 SYNOPSIS - - use Lintian::Version; - -=head1 DESCRIPTION - -Lintian::Version can help guess the current Lintian version. - -=head1 INSTANCE METHODS - -=over 4 - -=item guess_version - -=cut - -sub guess_version { - my ($lintian_base) = @_; - - my $guess = version_from_git($lintian_base); - $guess ||= version_from_changelog($lintian_base); - - return $guess; -} - -=item version_from_git - -=cut - -sub version_from_git { - my ($source_path) = @_; - - my $git_path = "$source_path/.git"; - - return EMPTY - unless -d $git_path; - - my $guess = safe_qx('git', "--git-dir=$git_path", 'describe'); - chomp $guess; - - return ($guess // EMPTY); -} - -=back - -=head1 AUTHOR - -Originally written by Niels Thykier for Lintian. - -=head1 SEE ALSO - -lintian(1) - -=cut - -1; - -# Local Variables: -# indent-tabs-mode: nil -# cperl-indent-level: 4 -# End: -# vim: syntax=perl sw=4 sts=4 sr et diff -Nru lintian-2.93.0/lib/Test/Lintian/Filter.pm lintian-2.89.0ubuntu1/lib/Test/Lintian/Filter.pm --- lintian-2.93.0/lib/Test/Lintian/Filter.pm 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/lib/Test/Lintian/Filter.pm 2020-08-10 09:59:45.000000000 +0000 @@ -327,8 +327,8 @@ # read tags from specification my $temp = Path::Tiny->tempfile; die "tagextract failed: $!" - if system('private/tagextract', '-f', 'EWI', "$testpath/tags", - $temp->stringify); + if + system('bin/tagextract', '-f', 'EWI', "$testpath/tags",$temp->stringify); my @lines = $temp->lines_utf8({ chomp => 1 }); my $csv = Text::CSV->new({ sep_char => '|' }); diff -Nru lintian-2.93.0/lib/Test/Lintian/Output/ColonSeparated.pm lintian-2.89.0ubuntu1/lib/Test/Lintian/Output/ColonSeparated.pm --- lintian-2.93.0/lib/Test/Lintian/Output/ColonSeparated.pm 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/lib/Test/Lintian/Output/ColonSeparated.pm 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,125 @@ +# Copyright © 2019 Felix Lechner +# +# This program is free software; you can redistribute it and/or modify +# it under the terms of the GNU General Public License as published by +# the Free Software Foundation; either version 2 of the License, or +# (at your option) any later version. +# +# This program is distributed in the hope that it will be useful, +# but WITHOUT ANY WARRANTY; without even the implied warranty of +# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the +# GNU General Public License for more details. +# +# You should have received a copy of the GNU General Public License +# along with this program. If not, you can find it on the World Wide +# Web at http://www.gnu.org/copyleft/gpl.html, or write to the Free +# Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, +# MA 02110-1301, USA + +package Test::Lintian::Output::ColonSeparated; + +=head1 NAME + +Test::Lintian::Output::ColonSeparated -- routines to process colon-separated tags + +=head1 SYNOPSIS + + use Path::Tiny; + use Test::Lintian::Output::ColonSeparated qw(to_universal); + + my $ewi = path("path to an ColonSeparated tag file")->slurp_utf8; + my $universal = to_universal($ewi); + +=head1 DESCRIPTION + +Helper routines to deal with colon-separated tags and tag files + +=cut + +use v5.20; +use warnings; +use utf8; +use autodie; + +use Exporter qw(import); + +BEGIN { + our @EXPORT_OK = qw( + to_universal + ); +} + +use Carp; +use List::Util qw(all); +use Text::CSV; + +use Test::Lintian::Output::Universal qw(universal_string order); + +use constant EMPTY => q{}; +use constant NEWLINE => qq{\n}; + +=head1 FUNCTIONS + +=over 4 + +=item to_universal(STRING) + +Converts the colon-separated tag data contained in STRING to universal tags. +They are likewise delivered in a multi-line string. + +=cut + +sub to_universal { + my ($fullewi) = @_; + + my @unsorted; + + my @lines = split(NEWLINE, $fullewi); + chomp @lines; + + my $csv = Text::CSV->new( + { sep_char => ':', escape_char => '\\', quote_char => undef }); + + foreach my $line (@lines) { + + my $status = $csv->parse($line); + die "Cannot parse line $line: " . $csv->error_diag + unless $status; + + my @fields = $csv->fields; + + shift @fields; + + my ( + $code, $severity, $override, + $package, $version, $architecture, + $type,$name, $details + ) = @fields; + + croak "Cannot parse line $line" + unless all { length } + ($code, $severity, $package, $version,$architecture, $type, $name); + + my $converted = universal_string($package, $type, $name, $details); + push(@unsorted, $converted); + } + + my @sorted = reverse sort { order($a) cmp order($b) } @unsorted; + + my $universal = EMPTY; + $universal .= $_ . NEWLINE for @sorted; + + return $universal; +} + +=back + +=cut + +1; + +# Local Variables: +# indent-tabs-mode: nil +# cperl-indent-level: 4 +# End: +# vim: syntax=perl sw=4 sts=4 sr et diff -Nru lintian-2.93.0/lib/Test/Lintian/Output/FullEWI.pm lintian-2.89.0ubuntu1/lib/Test/Lintian/Output/FullEWI.pm --- lintian-2.93.0/lib/Test/Lintian/Output/FullEWI.pm 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/lib/Test/Lintian/Output/FullEWI.pm 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,115 @@ +# Copyright © 2019 Felix Lechner +# +# This program is free software; you can redistribute it and/or modify +# it under the terms of the GNU General Public License as published by +# the Free Software Foundation; either version 2 of the License, or +# (at your option) any later version. +# +# This program is distributed in the hope that it will be useful, +# but WITHOUT ANY WARRANTY; without even the implied warranty of +# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the +# GNU General Public License for more details. +# +# You should have received a copy of the GNU General Public License +# along with this program. If not, you can find it on the World Wide +# Web at http://www.gnu.org/copyleft/gpl.html, or write to the Free +# Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, +# MA 02110-1301, USA + +package Test::Lintian::Output::FullEWI; + +=head1 NAME + +Test::Lintian::Output::FullEWI -- routines to process C tags + +=head1 SYNOPSIS + + use Path::Tiny; + use Test::Lintian::Output::FullEWI qw(to_universal); + + my $ewi = path("path to an FullEWI tag file")->slurp_utf8; + my $universal = to_universal($ewi); + +=head1 DESCRIPTION + +Helper routines to deal with C tags and tag files + +=cut + +use v5.20; +use warnings; +use utf8; +use autodie; + +use Exporter qw(import); + +BEGIN { + our @EXPORT_OK = qw( + to_universal + ); +} + +use Carp; +use List::Util qw(all); + +use Test::Lintian::Output::Universal qw(universal_string order); + +use constant EMPTY => q{}; +use constant NEWLINE => qq{\n}; + +=head1 FUNCTIONS + +=over 4 + +=item to_universal(STRING) + +Converts the C tag data contained in STRING to universal tags. +They are likewise delivered in a multi-line string. + +=cut + +sub to_universal { + my ($fullewi) = @_; + + my @unsorted; + + my @lines = split(NEWLINE, $fullewi); + chomp @lines; + + foreach my $line (@lines) { + + # no tag in this line + next if $line =~ /^N: /; + + # look for fullewi line + my ($code, $package, $type, $version, $architecture, $name, $details) + = $line + =~ /^(.): (\S+) (\S+) \(([^)]+)\) \[([^]]+)\]: (\S+)(?: (.*))?$/; + + croak "Cannot parse line $line" + unless all { length } + ($code, $package, $type, $version, $architecture, $name); + + my $converted = universal_string($package, $type, $name, $details); + push(@unsorted, $converted); + } + + my @sorted = reverse sort { order($a) cmp order($b) } @unsorted; + + my $universal = EMPTY; + $universal .= $_ . NEWLINE for @sorted; + + return $universal; +} + +=back + +=cut + +1; + +# Local Variables: +# indent-tabs-mode: nil +# cperl-indent-level: 4 +# End: +# vim: syntax=perl sw=4 sts=4 sr et diff -Nru lintian-2.93.0/lib/Test/Lintian/Output/LetterQualifier.pm lintian-2.89.0ubuntu1/lib/Test/Lintian/Output/LetterQualifier.pm --- lintian-2.93.0/lib/Test/Lintian/Output/LetterQualifier.pm 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/lib/Test/Lintian/Output/LetterQualifier.pm 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,91 @@ +# Copyright © 2019 Felix Lechner +# +# This program is free software; you can redistribute it and/or modify +# it under the terms of the GNU General Public License as published by +# the Free Software Foundation; either version 2 of the License, or +# (at your option) any later version. +# +# This program is distributed in the hope that it will be useful, +# but WITHOUT ANY WARRANTY; without even the implied warranty of +# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the +# GNU General Public License for more details. +# +# You should have received a copy of the GNU General Public License +# along with this program. If not, you can find it on the World Wide +# Web at http://www.gnu.org/copyleft/gpl.html, or write to the Free +# Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, +# MA 02110-1301, USA + +package Test::Lintian::Output::LetterQualifier; + +=head1 NAME + +Test::Lintian::Output::LetterQualifier -- routines to process letter-qualifier tags + +=head1 SYNOPSIS + + use Path::Tiny; + use Test::Lintian::Output::LetterQualifier qw(to_universal); + + my $ewi = path("path to an LetterQualifier tag file")->slurp_utf8; + my $universal = to_universal($ewi); + +=head1 DESCRIPTION + +Helper routines to deal with letter-qualifier tags and tag files + +=cut + +use v5.20; +use warnings; +use utf8; +use autodie; + +use Exporter qw(import); + +BEGIN { + our @EXPORT_OK = qw( + to_universal + ); +} + +use Test::Lintian::Output::EWI; + +use constant NEWLINE => qq{\n}; + +=head1 FUNCTIONS + +=over 4 + +=item to_universal(STRING) + +Converts the letter-qualifier tag data contained in STRING to universal tags. +They are likewise delivered in a multi-line string. + +=cut + +sub to_universal { + my ($letterqualifier) = @_; + + my @lines = split(NEWLINE, $letterqualifier); + chomp @lines; + + s/^(.)\[..\](.*)$/$1$2/ for @lines; + + my $ewi; + $ewi .= $_ . NEWLINE for @lines; + + return Test::Lintian::Output::EWI::to_universal($ewi); +} + +=back + +=cut + +1; + +# Local Variables: +# indent-tabs-mode: nil +# cperl-indent-level: 4 +# End: +# vim: syntax=perl sw=4 sts=4 sr et diff -Nru lintian-2.93.0/lib/Test/Lintian/Output/XML.pm lintian-2.89.0ubuntu1/lib/Test/Lintian/Output/XML.pm --- lintian-2.93.0/lib/Test/Lintian/Output/XML.pm 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/lib/Test/Lintian/Output/XML.pm 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,125 @@ +# Copyright © 2019 Felix Lechner +# +# This program is free software; you can redistribute it and/or modify +# it under the terms of the GNU General Public License as published by +# the Free Software Foundation; either version 2 of the License, or +# (at your option) any later version. +# +# This program is distributed in the hope that it will be useful, +# but WITHOUT ANY WARRANTY; without even the implied warranty of +# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the +# GNU General Public License for more details. +# +# You should have received a copy of the GNU General Public License +# along with this program. If not, you can find it on the World Wide +# Web at http://www.gnu.org/copyleft/gpl.html, or write to the Free +# Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, +# MA 02110-1301, USA + +package Test::Lintian::Output::XML; + +=head1 NAME + +Test::Lintian::Output::XML -- routines to process C tags + +=head1 SYNOPSIS + + use Path::Tiny; + use Test::Lintian::Output::XML qw(to_universal); + + my $xml = path("path to an XML tag file")->slurp_utf8; + my $universal = to_universal($xml); + +=head1 DESCRIPTION + +Helper routines to deal with C tags and tag files + +=cut + +use v5.20; +use warnings; +use utf8; +use autodie; + +use Exporter qw(import); + +BEGIN { + our @EXPORT_OK = qw( + to_universal + ); +} + +use Carp; +use List::Util qw(all); +use XML::LibXML; + +use Test::Lintian::Output::Universal qw(universal_string order); + +use constant EMPTY => q{}; +use constant NEWLINE => qq{\n}; + +=head1 FUNCTIONS + +=over 4 + +=item to_universal(STRING) + +Converts the C tag data contained in STRING to universal tags. +They are likewise delivered in a multi-line string. + +=cut + +sub to_universal { + my ($xml) = @_; + + my @unsorted; + + my $string = '' . $xml . ''; + my $dom = XML::LibXML->load_xml(string => $string); + + my @packagenodes = $dom->findnodes('/lintian/package'); + croak 'No packages in XML' + unless scalar @packagenodes; + + foreach my $packagenode (@packagenodes) { + + my $package = $packagenode->getAttribute('name'); + my $type = $packagenode->getAttribute('type'); + + croak 'Cannot parse package node in XML' + unless all { length } ($package, $type); + + my @tagsnodes = $packagenode->findnodes('./tag'); + foreach my $tagnode (@tagsnodes) { + + my $severity = $tagnode->getAttribute('severity'); + my $name = $tagnode->getAttribute('name'); + my $details = $tagnode->to_literal; + + croak 'Cannot parse tag node in XML' + unless all { length } ($severity, $name); + + my $converted = universal_string($package, $type, $name, $details); + push(@unsorted, $converted); + } + } + + my @sorted = reverse sort { order($a) cmp order($b) } @unsorted; + + my $universal = EMPTY; + $universal .= $_ . NEWLINE for @sorted; + + return $universal; +} + +=back + +=cut + +1; + +# Local Variables: +# indent-tabs-mode: nil +# cperl-indent-level: 4 +# End: +# vim: syntax=perl sw=4 sts=4 sr et diff -Nru lintian-2.93.0/lib/Test/Lintian/Run.pm lintian-2.89.0ubuntu1/lib/Test/Lintian/Run.pm --- lintian-2.93.0/lib/Test/Lintian/Run.pm 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/lib/Test/Lintian/Run.pm 2020-08-10 09:59:45.000000000 +0000 @@ -299,16 +299,11 @@ my $okay = !(scalar @errors); - if ($testcase->exists('Todo')) { - - my $explanation = $testcase->unfolded_value('Todo'); - diag "TODO ($explanation)"; - + if($testcase->unfolded_value('Todo') eq 'yes') { TODO: { - local $TODO = $explanation; + local $TODO = 'Test marked as TODO.'; ok($okay, 'Lintian passes for test marked TODO.'); } - return; } diff -Nru lintian-2.93.0/lib/Test/Lintian.pm lintian-2.89.0ubuntu1/lib/Test/Lintian.pm --- lintian-2.93.0/lib/Test/Lintian.pm 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/lib/Test/Lintian.pm 2020-08-10 09:59:45.000000000 +0000 @@ -207,10 +207,10 @@ ); } - for my $tpara (@tagpara) { + foreach my $tpara (@tagpara) { my $tag = $tpara->{'Tag'}//''; my $severity = $tpara->{'Severity'}//''; - my $explanation = $tpara->{'Explanation'} // ''; + my $info = $tpara->{'Info'} // ''; my (@htmltags, %seen); $i++; @@ -229,7 +229,7 @@ 'Tag has valid severity') or $builder->diag("$cname: $tag severity: $severity\n"); - # Explanation + # Info my $mistakes = 0; my $handler = sub { my ($incorrect, $correct) = @_; @@ -239,48 +239,44 @@ }; # FIXME: There are a couple of known false-positives that # breaks the test. - # check_spelling($explanation, $handler); + # check_spelling($info, $handler); $builder->is_eq($mistakes, 0, "$content_type $cname: $tag has no spelling errors"); - $builder->ok( - $explanation !~ /(?:^| )(?:[Ww]e|I)\b/, - 'Tag explanation does not speak of "I", or "we"' - )or $builder->diag("$content_type $cname: $tag\n"); + $builder->ok($info !~ /(?:^| )(?:[Ww]e|I)\b/, + 'Tag info does not speak of "I", or "we"') + or $builder->diag("$content_type $cname: $tag\n"); $builder->ok( - $explanation !~ /(\S\w)\. [^ ]/ + $info !~ /(\S\w)\. [^ ]/ || $1 =~ '/^\.[ge]$/', # for 'e.g.'/'i.e.' - 'Tag explanation uses two spaces after a full stop' + 'Tag info uses two spaces after a full stop' ) or $builder->diag("$content_type $cname: $tag\n"); - $builder->ok($explanation !~ /(\S\w\. )/, - 'Tag explanation uses only two spaces after a full stop') + $builder->ok($info !~ /(\S\w\. )/, + 'Tag info uses only two spaces after a full stop') or $builder->diag("$content_type $cname: $tag ($1)\n"); - $builder->ok(valid_utf8($explanation), - 'Tag explanation must be written in UTF-8') + $builder->ok(valid_utf8($info),'Tag info must be written in UTF-8') or $builder->diag("$content_type $cname: $tag\n"); - # Check the tag explanation for unescaped <> or for unknown tags - # (which probably indicate the same thing). - while ( - $explanation=~ s,<([^\s>]+)(?:\s+href=\"[^\"]+\")?>.*?,,s) - { + # Check the tag info for unescaped <> or for unknown tags (which + # probably indicate the same thing). + while ($info =~ s,<([^\s>]+)(?:\s+href=\"[^\"]+\")?>.*?,,s) { push @htmltags, $1; } @htmltags = grep { !exists $known_html_tags{$_} && !$seen{$_}++ }@htmltags; $builder->is_eq(join(', ', @htmltags), - '', 'Tag explanation has no unknown html tags') + '', 'Tag info has no unknown html tags') or $builder->diag("$content_type $cname: $tag\n"); - $builder->ok($explanation !~ /[<>]/, - 'Tag explanation has no stray angle brackets') + $builder->ok($info !~ /[<>]/, + 'Tag info has no stray angle brackets') or $builder->diag("$content_type $cname: $tag\n"); - if ($tpara->{'See-Also'}) { - my @issues = _check_reference($tpara->{'See-Also'}); + if ($tpara->{'Ref'}) { + my @issues = _check_reference($tpara->{'Ref'}); my $text = join("\n\t", @issues); $builder->ok(!@issues, 'Proper references are used') or $builder->diag("$content_type $cname: $tag\n\t$text"); diff -Nru lintian-2.93.0/man/annotate-lintian-hints.pod lintian-2.89.0ubuntu1/man/annotate-lintian-hints.pod --- lintian-2.93.0/man/annotate-lintian-hints.pod 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/man/annotate-lintian-hints.pod 1970-01-01 00:00:00.000000000 +0000 @@ -1,112 +0,0 @@ -# Copyright © 2010 Niels Thykier -# Copyright © 2017 Chris Lamb -# Copyright © 2020 Felix Lechner -# - based on the work Richard Braakman and Christian -# Schwarz (copyrighted 1998). -# -# This manual page is free software. It is distributed under the -# terms of the GNU General Public License as published by the Free -# Software Foundation; either version 2 of the License, or (at your -# option) any later version. -# -# This manual page is distributed in the hope that it will be useful, -# but WITHOUT ANY WARRANTY; without even the implied warranty of -# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the -# GNU General Public License for more details. -# -# You should have received a copy of the GNU General Public License -# along with this manual page; if not, write to the Free Software -# Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 -# USA -# - -=head1 NAME - -annotate-lintian-hints - give detailed information about Lintian's error tags - -=head1 SYNOPSIS - -B [I...] - -=head1 DESCRIPTION - -The B command parses the EWI output of the -B command and gives verbose information about the listed -Lintian tags, or parses a Lintian override file and gives verbose -information about the tags included. - -If no log-file is specified on the command line, this command expects -its input on stdin. Thus, the output of B can either be piped -through B or a log file produced by B can be -processed with this command. - - (Note, though, that the B command has a command line option -B<-i> to display the same results as B, so you -normally do not need to pipe the output of B through this -command to see the extra information.) - -=head1 OPTIONS - -=over 4 - -=item B<-a>, B<--annotate> - -Read from standard input or any files specified on the command line -and search the input for lines formatted like Lintian override -entries. For each one that was found, display verbose information -about that tag. - -=item B<-h>, B<--help> - -Display usage information and exit. - -=item B<--include-dir> dir - -Use dir as an additional "Lintian root". The directory is expected -have a similar layout to the LINTIAN_BASE (if it exists), but does not -need to be a full self-contained root. - -Unlike B, B will I load any code from -these additional directories. - -This option may appear more than once; each time adding an additional -directory. - -=item B<--profile> prof - -Use the severities from the vendor profile prof when displaying tags. -If the profile name does not contain a slash, the default profile for -that vendor is chosen. - -If not specified, B loads the best profile for the -current vendor. - -Please Refer to the Lintian User Manual for the full documentation of -profiles. - -=item B<--user-dirs>, B<--no-user-dirs> - -By default, B will check I<$HOME> and I for files -supplied by the user or the local sysadmin (e.g. profiles). This -default can be disabled (and re-enabled) by using B<--no-user-dirs> -(and B<--user-dirs>, respectively). - -These option can appear multiple times, in which case the of them -to appear determines the result. - -=back - -=head1 SEE ALSO - -L - -=head1 AUTHORS - -Niels Thykier - -Richard Braakman - -Christian Schwarz - -=cut - diff -Nru lintian-2.93.0/man/explain-lintian-tags.pod lintian-2.89.0ubuntu1/man/explain-lintian-tags.pod --- lintian-2.93.0/man/explain-lintian-tags.pod 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/man/explain-lintian-tags.pod 1970-01-01 00:00:00.000000000 +0000 @@ -1,108 +0,0 @@ -# Copyright © 2010 Niels Thykier -# Copyright © 2017 Chris Lamb -# Copyright © 2020 Felix Lechner -# - based on the work Richard Braakman and Christian -# Schwarz (copyrighted 1998). -# -# This manual page is free software. It is distributed under the -# terms of the GNU General Public License as published by the Free -# Software Foundation; either version 2 of the License, or (at your -# option) any later version. -# -# This manual page is distributed in the hope that it will be useful, -# but WITHOUT ANY WARRANTY; without even the implied warranty of -# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the -# GNU General Public License for more details. -# -# You should have received a copy of the GNU General Public License -# along with this manual page; if not, write to the Free Software -# Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 -# USA -# - -=head1 NAME - -explain-lintian-tags - offer more information about Lintian's tags - -=head1 SYNOPSIS - -B B<--tags> I ... - -=head1 DESCRIPTION - -The B command explains the named tags given on -the command line. - -=head1 OPTIONS - -=over 4 - -=item B<-l>, B<--list-tags> - -List all tags Lintian knows about in sorted order. - -=item B<-h>, B<--help> - -Display usage information and exit. - -=item B<--include-dir> dir - -Use dir as an additional "Lintian root". The directory is expected -have a similar layout to the LINTIAN_BASE (if it exists), but does not -need to be a full self-contained root. - -Unlike B, B will I load any code from -these additional directories. - -This option may appear more than once; each time adding an additional -directory. - -=item B<--profile> prof - -Use the severities from the vendor profile prof when displaying tags. -If the profile name does not contain a slash, the default profile for -that vendor is chosen. - -If not specified, B loads the best profile for the -current vendor. - -Please Refer to the Lintian User Manual for the full documentation of -profiles. - -=item B<-t>, B<--tag>, B<--tags> - -This option has no effect. It exists for historical reasons. - -=item B<--user-dirs>, B<--no-user-dirs> - -By default, B will check I<$HOME> and I for files -supplied by the user or the local sysadmin (e.g. profiles). This -default can be disabled (and re-enabled) by using B<--no-user-dirs> -(and B<--user-dirs>, respectively). - -These option can appear multiple times, in which case the of them -to appear determines the result. - -=back - -=head1 EXIT STATUS - -If any of the tags specified were not found in the specified profile -(or in the default profile), this command returns with exit code 1. - -When all requested tags were found, it returns with exit code 0. - -=head1 SEE ALSO - -L - -=head1 AUTHORS - -Niels Thykier - -Richard Braakman - -Christian Schwarz - -=cut - diff -Nru lintian-2.93.0/man/lintian-info.pod lintian-2.89.0ubuntu1/man/lintian-info.pod --- lintian-2.93.0/man/lintian-info.pod 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/man/lintian-info.pod 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,132 @@ +# Copyright © 2010 Niels Thykier +# Copyright © 2017 Chris Lamb +# - based on the work Richard Braakman and Christian +# Schwarz (copyrighted 1998). +# +# This manual page is free software. It is distributed under the +# terms of the GNU General Public License as published by the Free +# Software Foundation; either version 2 of the License, or (at your +# option) any later version. +# +# This manual page is distributed in the hope that it will be useful, +# but WITHOUT ANY WARRANTY; without even the implied warranty of +# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the +# GNU General Public License for more details. +# +# You should have received a copy of the GNU General Public License +# along with this manual page; if not, write to the Free Software +# Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 +# USA +# + +=head1 NAME + +lintian-info - give detailed information about Lintian's error tags + +=head1 SYNOPSIS + +B [I...] + +B B<--tags> I ... + +=head1 DESCRIPTION + +The B command parses the output of the B +command and gives verbose information about the listed Lintian error +tags, parses a Lintian override file and gives verbose information +about the tags included, or (if given the B<-t> or B<--tags> option) +explains a given tag or tags. + +If no log-file is specified on the command line, this command expects +its input on stdin. Thus, the output of B can either be piped +through B or a log file produced by B can be +processed with this command. (Note, though, that the B +command has a command line option B<-i> to display the same results as +B, so you will not normally need to pipe the output of +B into this command.) + + +=head1 OPTIONS + +=over 4 + +=item B<-a>, B<--annotate> + +Read from standard input or any files specified on the command line +and search the input for lines formatted like Lintian override +entries. For each one that was found, display verbose information +about that tag. + +=item B<-l>, B<--list-tags> + +List all tags Lintian knows about in sorted order. + +=item B<-h>, B<--help> + +Display usage information and exit. + +=item B<--include-dir> dir + +Use dir as an additional "Lintian root". The directory is expected +have a similar layout to the LINTIAN_BASE (if it exists), but does not +need to be a full self-contained root. + +Unlike B, B will I load any code from +these additional directories. + +This option may appear more than once; each time adding an additional +directory. + +B: This option should be the very first if given. + +=item B<--profile> prof + +Use the severities from the vendor profile prof when displaying tags. +If the profile name does not contain a slash, the default profile for +that vendor is chosen. + +If not specified, B loads the best profile for the +current vendor. + +Please Refer to the Lintian User Manual for the full documentation of +profiles. + +=item B<-t>, B<--tag>, B<--tags> + +Rather than treating them as log file names, treat any command-line +options as tag names and display the descriptions of each tag. + +=item B<--user-dirs>, B<--no-user-dirs> + +By default, B will check I<$HOME> and I for files +supplied by the user or the local sysadmin (e.g. profiles). This +default can be disabled (and re-enabled) by using B<--no-user-dirs> +(and B<--user-dirs>, respectively). + +These option can appear multiple times, in which case the of them +to appear determines the result. + +B: This option should be the very first if given. + +=back + +=head1 EXIT STATUS + +If B<-t> or B<--tags> was given and one or more of the tags specified +were unknown, this command returns the exit code 1. Otherwise, it +always returns with exit code 0. + +=head1 SEE ALSO + +L + +=head1 AUTHORS + +Niels Thykier + +Richard Braakman + +Christian Schwarz + +=cut + diff -Nru lintian-2.93.0/man/lintian.pod lintian-2.89.0ubuntu1/man/lintian.pod --- lintian-2.93.0/man/lintian.pod 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/man/lintian.pod 1970-01-01 00:00:00.000000000 +0000 @@ -1,812 +0,0 @@ -# Copyright © 2010 Niels Thykier -# Copyright © 2017, 2019 Chris Lamb -# - based on the work Richard Braakman and Christian -# Schwarz (copyrighted 1998). -# -# This manual page is free software. It is distributed under the -# terms of the GNU General Public License as published by the Free -# Software Foundation; either version 2 of the License, or (at your -# option) any later version. -# -# This manual page is distributed in the hope that it will be useful, -# but WITHOUT ANY WARRANTY; without even the implied warranty of -# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the -# GNU General Public License for more details. -# -# You should have received a copy of the GNU General Public License -# along with this manual page; if not, write to the Free Software -# Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 -# USA -# - -=head1 NAME - -lintian - Static analysis tool for Debian packages - -=head1 SYNOPSIS - -B [I] [I] [I] ... - -=head1 DESCRIPTION - -Lintian dissects Debian packages and reports bugs and policy -violations. It contains automated checks for many aspects of Debian -policy as well as some checks for common errors. - -There are two ways to specify binary, udeb or source packages for -Lintian to process: by file name (the .deb file for a binary package -or the .dsc file for a source package), or by naming a I<.changes> -file. - -If you specify a I<.changes> file, Lintian will process all packages -listed in that file. This is convenient when checking a new package -before uploading it. - -If you specify packages to be checked or use the option -B<--packages-from-file>, the packages requested will be processed. -Otherwise, if I exists, it is parsed to determine -the name of the .changes file to look for in the parent directory. -See L for more information. - - -=head1 OPTIONS - -Actions of the lintian command: (Only one action can be specified per invocation) - -=over 4 - -=item B<-c>, B<--check> - -Run all checks over the specified packages. This is the default action. - -=item B<-C> chk1,chk2,..., B<--check-part> chk1,chk2,... - -Run only the specified checks. You can either specify the name of the -check script or the abbreviation. For details, see the L section -below. - -=item B<-F>, B<--ftp-master-rejects> - -Run only the checks that issue tags that result in automatic rejects -from the Debian upload queue. The list of such tags is refreshed with -each Lintian release, so may be slightly out of date if it has changed -recently. - -This is implemented via a profile and thus this option cannot be used -together with B<--profile>. - -=item B<-T> tag1,tag2,..., B<--tags> tag1,tag2,... - -Run only the checks that issue the requested tags. The tests for -other tags within the check scripts will be run but the tags will not -be issued. - -With this options all tags listed will be displayed regardless of the -display settings. - -=item B<--tags-from-file> filename - -Same functionality as B<--tags>, but read the list of tags from a -file. Blank lines and lines beginning with # are ignored. All other -lines are taken to be tag names or comma-separated lists of tag names -to (potentially) issue. - -With this options all tags listed will be displayed regardless of the -display settings. - -=item B<-X> chk1,chk2,..., B<--dont-check-part> chk1,chk2,... - -Run all but the specified checks. You can either specify the name -of the check script or the abbreviation. For details, see the -L section below. - -=back - -General options: - -=over 4 - -=item B<-h>, B<--help> - -Display usage information and exit. - -=item B<-q>, B<--quiet> - -Suppress all informational messages including override comments -(normally shown with B<--show-overrides>). - -This option is silently ignored if B<--debug> is given. Otherwise, if -both B<--verbose> and B<--quiet> is used, the last of these two options -take effect. - -This option overrides the B and the B variable in the -configuration file. In the configuration file, this option is enabled -by using B variable. The B and B variables may -not both appear in the config file. - -=item B<-v>, B<--verbose> - -Display verbose messages. - -If B<--debug> is used this option is always enabled. Otherwise, if -both B<--verbose> and B<--quiet> is used (and B<--debug> is not used), -the last of these two options take effect. - -This option overrides the B variable in the configuration file. -In the configuration file, this option is enabled by using B -variable. The B and B variables may not both appear -in the config file. - -=item B<-V>, B<--version> - -Display lintian version number and exit. - -=item B<--print-version> - -Print unadorned version number and exit. - -=back - -Behavior options for B. - -=over 4 - -=item B<--color> (never|always|auto|html) - -Whether to colorize tags in lintian output based on their visibility. -The default is "never", which never uses color. "always" will always -use color, "auto" will use color only if the output is going to a -terminal, and "html" will use HTML EspanE tags with a color style -attribute (instead of ANSI color escape sequences). - -This option overrides the B variable in the configuration file. - -=item B<--hyperlinks> (on|off) - -Shows text-based hyperlinks to tag descriptions on lintian.debian.org on -terminals that support it. The default is on for terminals that support -it, unless the user selected '--color never'. This currently only works -in GNOME Terminal. - -This option overrides the B variable in the configuration file. - -=item B<--default-display-level> - -Reset the current display level to the default. Basically, this -option behaves exactly like passing the following options to lintian: - -=over 4 - -B<-L> ">=warning" - -=back - -The primary use for this is to ensure that lintian's display level has -been reset to the built-in default values. Notably, this can be used -to override display settings earlier on the command-line or in the -lintian configuration file. - -Further changes to the display level can be done I this option. -Example: B<--default-display-level --display-info> gives you the -default display level plus informational ("I:") tags. - -=item B<--display-source> X - -Only display tags from the source X (e.g. the Policy Manual or the -Developer Reference). This option can be used multiple times to -add additional sources. Example sources are "policy" or "devref" -being the Policy Manual and the Developer Reference (respectively). - -The entire list of sources can be found in -I<$LINTIAN_BASE/data/output/manual-references> - -=item B<-E>, B<--display-experimental>, B<--no-display-experimental> - -Control whether to display experimental ("X:") tags. They are -normally suppressed. - -If a tag is marked experimental, this means that the code that -generates this message is not as well tested as the rest of Lintian, -and might still give surprising results. Feel free to ignore -Experimental messages that do not seem to make sense, though of course -bug reports are always welcome (particularly if they include fixes). - -These options overrides the B variable in the -configuration file. - -=item B<--fail-on> {error | warning | info | pedantic | experimental | override | none} - -Causes B to exit with a program status of 2 for the given -conditions. This option can be a comma-separated list, or it may be -specified multiple times. - -The default is B. Also, 'warning' does not imply 'error'. -Please specify both if you want both. - -=item B<-i>, B<--info> - -Print explanatory information about each problem discovered in -addition to the lintian error tags. To print a long tag description -without running lintian, see L. - -This option overrides B variable in the configuration file. - -=item B<-I>, B<--display-info> - -Display informational ("I:") tags as well. They are normally -suppressed. (This is equivalent to B<-L> ">=info"). - -This option overrides the B variable in the -configuration file. - -Note: B and B may not both appear in the -configuration file. - -=item B<-L> [+|-|=][>=|>|=|<|<=][S|C|S/C], B<--display-level> [+|-|=][>=|>|=|<|<=][S|C|S/C] - -Fine-grained selection of tags to be displayed. It is possible to add, -remove or set the levels to display, specifying a visibility (error, -warning, info, pedantic, or classification. The default settings are -equivalent to B<-L> ">=warning". - -The value consists of 3 parts, where two of them are optional. The -parts are: - -=over 4 - -=item modifier operator - -How to affect the current display level. Can be one of add to ("+"), -remove from ("-") or set to ("=") the display level(s) denoted by the -following selection. - -The default value is "=" (i.e. set the display level). - -=item set operator - -The visibility to be selected. The operator can be one of ">=", ">", -"=", "<" or "<=". As an example, this can be used to select all info -(and more serious) tags via ">=info". - -The default value is "=", which means "exactly" the given visibility. - -=back - -This option overrides the B variable in the -configuration file. The value of the B in -configuration file should be space separated entries in the same -format as passed via command-line. - -Note: B may not be used with B or B -in the configuration file. - -=item B<-o>, B<--no-override> - -Ignore all overrides provided by the package. This option will overrule -B<--show-overrides>. - -This option overrides the B variable in the configuration -file. - -=item B<--pedantic> - -Display pedantic ("P:") tags as well. They are normally suppressed. -(This is equivalent to B<-L> "+=pedantic"). - -Pedantic tags are Lintian at its most pickiest and include checks for -particular Debian packaging styles and checks that many people -disagree with. Expect false positives and Lintian tags that you don't -consider useful if you use this option. Adding overrides for pedantic -tags is probably not worth the effort. - -This option overrides the B variable in the configuration -file. - -Note: B and B may not both appear in the -configuration file. - -=item B<--profile> vendor[/prof] - -Use the profile from vendor (or the profile with that name). If the -profile name does not contain a slash, the default profile for than -vendor is chosen. - -As an example, if you are on Ubuntu and want to use Lintian's Debian -checks, you can use: - - --profile debian - -Likewise, on a Debian machine you can use this to request the Ubuntu -checks. - -If the token I<{VENDOR}> appears in the profile name, B will -substitute the token with a vendor name to find the profile. -B uses L to determine the best vendor to use -(the closer to the current vendor, the better). This is mostly useful -for people implementing their own checks on top of Lintian. - -If not specified, the default value is I<{VENDOR}/main>. - -Please Refer to the Lintian User Manual for the full documentation of -profiles. - -=item B<--show-overrides>, B<--hide-overrides> - -Controls whether tags that have been overridden should be shown. - -The B<--show-overrides> differs from B<--no-overrides> in that shown overridden -tags will still be marked as overridden (using an "O" code). - -If the overridden tags are shown, the related override comments will -also be displayed (unless --quiet is used). Please refer to the Lintian -User Manual for the documentation on how lintian relates comments to a -given override. - - -These options override the B variable in the -configuration file. - -=item B<--suppress-tags> tag1,tag2,... - -Suppress the listed tags. They will not be reported if they occur and -will not affect the exit status of Lintian. This option can be given -multiple times and can be mixed with B<--suppress-tags-from-file>. - -This option can be used together with B<--dont-check-part> ("Not those -checks nor these tags") and B<--check-part> ("Only those checks, but -not these tags (from those checks)") to further reduce the selection of -tags. - -When used with B<--tags>, this option is mostly ignored. - -=item B<--suppress-tags-from-file> file - -Suppress all tags listed in the given file. Blank lines and lines -beginning with # are ignored. All other lines are taken to be tag -names or comma-separated lists of tag names to suppress. The -suppressed tags will not be reported if they occur and will not affect -the exit status of Lintian. - -Tags parsed from the file will be handled as if they had been given to -the B<--suppress-tags> option (e.g. ignored if B<--tags> is used). - -=item B<--tag-display-limit>[=X] - -By default, lintian limits itself to emitting at most 4 instances of each -tag per processable when STDOUT is a TTY. This option specified that limit. -See also B<--no-tag-display-limit>. - -=item B<--no-tag-display-limit> - -By default, lintian limits itself to emitting at most 4 instances of each -tag per processable when STDOUT is a TTY. This option disables that limit. - -When STDOUT is not a TTY, lintian has no limit. See also -B<--tag-display-limit>. - -=back - -Configuration options: - -=over 4 - -=item B<--cfg> configfile - -Read the configuration from configfile rather than the default -locations. This option overrides the B environment -variable. - -=item B<--no-cfg> - -Do not read any configuration file. This option overrides the -B<--cfg> above. - -=item B<--ignore-lintian-env> - -Ignore all environment variables starting with I. - -This option is mostly useful for applications running B for -checking packages and do not want the invoking user to affect the -result (by setting LINTIAN_PROFILE etc.). - -Note it does I cause B to ignore the entire environment -like I or I. The latter can affect the default -profile (or "{VENDOR}" token for B<--profile>). - -Should usually be combined with B<--no-user-dirs> (or unsetting $HOME -and all I variables). - -=item B<--include-dir> dir - -Use dir as an additional "LINTIAN_BASE". The directory is expected -have a similar layout to the LINTIAN_BASE (if it exists), but does not -need to be a full self-contained root. - -B will check this directory for (additional) profiles, data -files, support libraries and checks. The latter two imply that -Lintian may attempt to I from this directory. - -This option may appear more than once; each time adding an additional -directory. Directories are searched in the order they appear on the -command line. - -The additional directories will be checked I the user -directories (though see B<--no-user-dirs>) and I the core -LINTIAN_BASE. - -B: This option should be the very first if given. - -=item B<-j> X, B<--jobs>=X - -Set the limit for how many jobs Lintian will run in parallel. This -option overrides the B variable in the configuration file. - -By default Lintian will use I to determine a reasonable default -(or 2, if the nproc fails). - -=item B<--user-dirs>, B<--no-user-dirs> - -By default, B will check I<$HOME> and I for files -supplied by the user or the local sysadmin (e.g. config files and -profiles). This default can be disabled (and re-enabled) by using -B<--no-user-dirs> (and B<--user-dirs>, respectively). - -These options will I affect the inclusion of LINTIAN_BASE, which -is always included. - -These option can appear multiple times, in which case the last of them -to appear determines the result. - -Note that if the intention is only to disable the user's I<$HOME>, -then unsetting I<$HOME> and I may suffice. Alternatively, -I can be "re-added" by using I<--include-dir> (caveat: -I will be ignored by this). - -If the intention is to avoid (unintentional) side-effects from the -calling user, then this option could be combined with -B<--ignore-lintian-env>. - -If for some reason B<--no-user-dirs> cannot be used, then consider -unsetting I<$HOME> and all the I<$XDG_*> variables (not just the -I<$XDG_*_HOME> ones). - -B: This option should be the very first if given. - -=back - -Developer/Special usage options: - -=over 4 - -=item B<--allow-root> - -Override lintian's warning when it is run with superuser privileges. - -=item B<--keep-lab> - -By default, temporary labs will be removed after lintian is finished. -Specifying this options will leave the lab behind, which might be -useful for debugging purposes. You can find out where the temporary -lab is located by running lintian with the B<--verbose> option. - -=item B<--packages-from-file> X - -The line is read as the path to a file to process (all whitespace is -included!). - -If X is "-", Lintian will read the packages from STDIN. - -=item B<--perf-debug> - -Enable performance related debug logging. - -The data logged and the format used is subject to change with every -release. - -Note that some of the information may also be available (possibly in -a different format) with the B<--debug> option. - -=item B<--perf-output> OUTPUT - -Write performance related debug information to the specified file or -file descriptor. If OUTPUT starts with a '&' or '+', Lintian will -handle OUTPUT specially. Otherwise, Lintian will open the file -denoted by OUTPUT for writing (truncating if it exists, creating it -if it does not exist). - -If the first character of OUTPUT is a & and the rest of argument is a -number N, then lintian attempts to write it to the file descriptor -with the number N. Said file descriptor must be open for writing. -E.g I<&2> makes Lintian write the performance logging to STDERR. - -If the first character of OUTPUT is a +, Lintian will append to the -file rather than truncating it. In this case, the file name is OUTPUT -with initial "+" character removed. E.g. I<+my-file> makes Lintian -append to I - -If Lintian should write the output to a file starting with a literal -'&' or '+', then simply prefix it with "./" (e.g. "+my-file" becomes -"./+my-file"). - -If this option omitted, Lintian will default to using STDOUT. - -=back - -=head1 FILES - -Lintian looks for its configuration file in the following locations, -in this order: - -=over 4 - -=item * The argument given to B<--cfg> - -=item * I<$LINTIAN_CFG> - -=item * I<$XDG_CONFIG_HOME/lintian/lintianrc> - -=item * I - -Where XDG_DIR is a directory listed in I<$XDG_CONFIG_DIRS> (or -I if I<$XDG_CONFIG_DIRS> is unset). - -=item * I<$HOME/.lintianrc> - -Please consider using the XDG based variant above (usually, in -I<~/.config>). - -=item * I - -=back - -Lintian uses the following directories: - -=over 4 - -=item I - -Lintian defaults to creating a temporary lab directory in I. To -change the directory used, set the TMPDIR environment variable to a -suitable directory. TMPDIR can be set in the configuration file. - -=item I - -Scripts that check aspects of a package. - -=item I - -Scripts that collect information about a package and store it for use -by the check scripts. - -=item I - -Supporting data used by Lintian checks and for output formatting. - -=item I - -Utility scripts used by the other lintian scripts. - -=back - -For binary packages, Lintian looks for overrides in a file named -IpackageE> inside the binary -package, where IpackageE> is the name of the binary -package. For source packages, Lintian looks for overrides in -I and then in -I if the first file is not found. -The first path is preferred. See the Lintian User's Manual for the -syntax of overrides. - -=head1 CONFIGURATION FILE - -The configuration file can be used to specify default values for some -options. The general format is: - - option = value - -All whitespace adjacent to the "=" sign as well as leading and -trailing whitespace is ignored. However whitespace within the -value is respected, as demonstrated by this example: - - # Parsed as "opt1" with value "val1" - opt1 = val1 - # Parsed as "opt2" with value "val2.1 val2.2 val2.3" - opt2 = val2.1 val2.2 val2.3 - -Unless otherwise specified, no option may appear more than once. -Lintian will ignore empty lines or lines starting with the -B<#>-character. - -Generally options will be the long form of the command-line option -without the leading dashes. There some exceptions (such as ---profile), where Lintian uses the same name as the environment -variable. - -Lintian only allows a subset of the options specified in the -configuration file; please refer to the individual options in -L. - -In the configuration file, all options listed must have a value, even -if they do not accept a value on command line (e.g. --pedantic). The -values "yes", "y", "1", or "true" will enable such an option and "no", -"n", "0" or "false" will disable it. Prior to the 2.5.2 release, -these values were case sensitive. - -For other options, they generally take the same values as they do on -the command line. Though some options allow a slightly different -format (e.g. --display-level). These exceptions are explained for the -relevant options in L. - -Beyond command line options, it is also allowed to specify the -environment variable "TMPDIR" in the configuration file. - -A sample configuration file could look like: - - # Sample configuration file for lintian - # - # Set the default profile (--profile) - LINTIAN_PROFILE = debian - - # Set the default TMPDIR for lintian to /var/tmp/lintian - # - useful if /tmp is tmpfs with "limited" size. - TMPDIR = /var/tmp/lintian/ - - # Show info (I:) tags by default (--display-info) - # NB: this cannot be used with display-level - display-info=yes - - # Ignore all overrides (--no-override) - # NB: called "override" in the config file - # and has inverted value! - override = no - - # Automatically determine if color should be used - color = auto - -=head1 EXIT STATUS - -=over 4 - -=item B<0> - -Normal operation. - -=item B<1> - -Lintian run-time error. An error message is sent to stderr. - -=item B<2> - -Detected a condition specified via the B<--fail-on> option. This can -be used to trigger a non-zero exit value in case of policy violations. - -=back - -=head1 CHECKING LAST BUILD - -When run in an unpacked package dir (with no package selection -arguments), Lintian will use I to determine the -source and version of the package. Lintian will then attempt to find -a matching I<.changes> file for this source and version combination. - -Lintian will (in order) search the following directories: - -=over 4 - -=item .. - -Used by dpkg-buildpackage(1). - -=item ../build-area - -Used by svn-buildpackage(1). - -=item /var/cache/pbuilder/result - -Used by pbuilder(1) and cowbuilder(1). - -=back - -In each directory, Lintian will attempt to find a I<.changes> file -using the following values as architecture (in order): - -=over 4 - -=item I<$DEB_BUILD_ARCH> (or I) - -The environment variable DEB_BUILD_ARCH (if not set, "dpkg ---print-architecture" will be used instead) - -=item I<$DEB_HOST_ARCH> - -The environment variable DEB_HOST_ARCH. - -=item I - -If dpkg(1) appears to support multi-arch, then any architecture listed -by "dpkg --print-foreign-architectures" will be used (in the order -returned by dpkg). - -=item I - -Pseudo architecture used by mergechanges(1). - -=item I - -Used when building architecture indep packages only (e.g. -dpkg-buildpackage -A). - -=item I - -Used for "source only" builds (e.g. dpkg-buildpackage -S). - -=back - -If a I<.changes> file matches any combination above exists, Lintian -will process the first match as if you had passed it per command line. -If no I<.changes> file can be found, Lintian will print a list of attempted -locations on STDERR and exit 0. - -=head1 EXAMPLES - -=over 4 - -=item B<$ lintian foo.changes> - -Check the changes file itself and any (binary, udeb or source) package -listed in it. - -=item B<$ lintian foo.deb> - -Check binary package foo given by foo.deb. - -=item B<$ lintian foo.dsc> - -Check source package foo given by foo.dsc. - -=item B<$ lintian foo.dsc -L +info> - -Check source package foo given by foo.dsc, including info tags. - -=item B<$ lintian -i foo.changes> - -Check the changes file and, if listed, the source and binary package -of the upload. The output will contain detailed information about the -reported tags. - -=item B<$ lintian> - -Assuming I exists, look for a changes file for the -source in the parent dir. Otherwise, print usage information and -exit. - -=back - -=head1 BUGS - -Lintian does not have any locking mechanisms yet. (Running several -Lintian processes on the same laboratory simultaneously is likely to fail -or corrupt the laboratory.) - -If you discover any other bugs in lintian, please contact the authors. - -=head1 SEE ALSO - -L, Lintian User Manual -(/usr/share/doc/lintian/lintian.html) - -Packaging tools: L, L, -L. - -=head1 AUTHORS - -Niels Thykier - -Richard Braakman - -Christian Schwarz - -Please use the email address for -Lintian related comments. - -=cut diff -Nru lintian-2.93.0/man/lintian.pod.in lintian-2.89.0ubuntu1/man/lintian.pod.in --- lintian-2.93.0/man/lintian.pod.in 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/man/lintian.pod.in 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,822 @@ +# Copyright © 2010 Niels Thykier +# Copyright © 2017, 2019 Chris Lamb +# - based on the work Richard Braakman and Christian +# Schwarz (copyrighted 1998). +# +# This manual page is free software. It is distributed under the +# terms of the GNU General Public License as published by the Free +# Software Foundation; either version 2 of the License, or (at your +# option) any later version. +# +# This manual page is distributed in the hope that it will be useful, +# but WITHOUT ANY WARRANTY; without even the implied warranty of +# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the +# GNU General Public License for more details. +# +# You should have received a copy of the GNU General Public License +# along with this manual page; if not, write to the Free Software +# Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 +# USA +# + +=head1 NAME + +lintian - Static analysis tool for Debian packages + +=head1 SYNOPSIS + +B [I] [I] [I] ... + +=head1 DESCRIPTION + +Lintian dissects Debian packages and reports bugs and policy +violations. It contains automated checks for many aspects of Debian +policy as well as some checks for common errors. + +There are two ways to specify binary, udeb or source packages for +Lintian to process: by file name (the .deb file for a binary package +or the .dsc file for a source package), or by naming a I<.changes> +file. + +If you specify a I<.changes> file, Lintian will process all packages +listed in that file. This is convenient when checking a new package +before uploading it. + +If you specify packages to be checked or use the option +B<--packages-from-file>, the packages requested will be processed. +Otherwise, if I exists, it is parsed to determine +the name of the .changes file to look for in the parent directory. +See L for more information. + + +=head1 OPTIONS + +Actions of the lintian command: (Only one action can be specified per invocation) + +=over 4 + +=item B<-c>, B<--check> + +Run all checks over the specified packages. This is the default action. + +=item B<-C> chk1,chk2,..., B<--check-part> chk1,chk2,... + +Run only the specified checks. You can either specify the name of the +check script or the abbreviation. For details, see the L section +below. + +=item B<-F>, B<--ftp-master-rejects> + +Run only the checks that issue tags that result in automatic rejects +from the Debian upload queue. The list of such tags is refreshed with +each Lintian release, so may be slightly out of date if it has changed +recently. + +This is implemented via a profile and thus this option cannot be used +together with B<--profile>. + +=item B<-T> tag1,tag2,..., B<--tags> tag1,tag2,... + +Run only the checks that issue the requested tags. The tests for +other tags within the check scripts will be run but the tags will not +be issued. + +With this options all tags listed will be displayed regardless of the +display settings. + +=item B<--tags-from-file> filename + +Same functionality as B<--tags>, but read the list of tags from a +file. Blank lines and lines beginning with # are ignored. All other +lines are taken to be tag names or comma-separated lists of tag names +to (potentially) issue. + +With this options all tags listed will be displayed regardless of the +display settings. + +=item B<-X> chk1,chk2,..., B<--dont-check-part> chk1,chk2,... + +Run all but the specified checks. You can either specify the name +of the check script or the abbreviation. For details, see the +L section below. + +=back + +General options: + +=over 4 + +=item B<-h>, B<--help> + +Display usage information and exit. + +=item B<-q>, B<--quiet> + +Suppress all informational messages including override comments +(normally shown with B<--show-overrides>). + +This option is silently ignored if B<--debug> is given. Otherwise, if +both B<--verbose> and B<--quiet> is used, the last of these two options +take effect. + +This option overrides the B and the B variable in the +configuration file. In the configuration file, this option is enabled +by using B variable. The B and B variables may +not both appear in the config file. + +=item B<-v>, B<--verbose> + +Display verbose messages. + +If B<--debug> is used this option is always enabled. Otherwise, if +both B<--verbose> and B<--quiet> is used (and B<--debug> is not used), +the last of these two options take effect. + +This option overrides the B variable in the configuration file. +In the configuration file, this option is enabled by using B +variable. The B and B variables may not both appear +in the config file. + +=item B<-V>, B<--version> + +Display lintian version number and exit. + +=item B<--print-version> + +Print unadorned version number and exit. + +=back + +Behavior options for B. + +=over 4 + +=item B<--color> (never|always|auto|html) + +Whether to colorize tags in lintian output based on their visibility. +The default is "never", which never uses color. "always" will always +use color, "auto" will use color only if the output is going to a +terminal, and "html" will use HTML EspanE tags with a color style +attribute (instead of ANSI color escape sequences). + +This option overrides the B variable in the configuration file. + +=item B<--hyperlinks> (on|off) + +Shows text-based hyperlinks to tag descriptions on lintian.debian.org on +terminals that support it. The default is on for terminals that support +it, unless the user selected '--color never'. This currently only works +in GNOME Terminal. + +This option overrides the B variable in the configuration file. + +=item B<--default-display-level> + +Reset the current display level to the default. Basically, this +option behaves exactly like passing the following options to lintian: + +=over 4 + +B<-L> ">=warning" + +=back + +The primary use for this is to ensure that lintian's display level has +been reset to the built-in default values. Notably, this can be used +to override display settings earlier on the command-line or in the +lintian configuration file. + +Further changes to the display level can be done I this option. +Example: B<--default-display-level --display-info> gives you the +default display level plus informational ("I:") tags. + +=item B<--display-source> X + +Only display tags from the source X (e.g. the Policy Manual or the +Developer Reference). This option can be used multiple times to +add additional sources. Example sources are "policy" or "devref" +being the Policy Manual and the Developer Reference (respectively). + +The entire list of sources can be found in +I<$LINTIAN_BASE/data/output/manual-references> + +=item B<-E>, B<--display-experimental>, B<--no-display-experimental> + +Control whether to display experimental ("X:") tags. They are +normally suppressed. + +If a tag is marked experimental, this means that the code that +generates this message is not as well tested as the rest of Lintian, +and might still give surprising results. Feel free to ignore +Experimental messages that do not seem to make sense, though of course +bug reports are always welcome (particularly if they include fixes). + +These options overrides the B variable in the +configuration file. + +=item B<--fail-on> {error | warning | info | pedantic | experimental | override | none} + +Causes B to exit with a program status of 2 for the given +conditions. This option can be a comma-separated list, or it may be +specified multiple times. + +The default is B. Also, 'warning' does not imply 'error'. +Please specify both if you want both. + +=item B<-i>, B<--info> + +Print explanatory information about each problem discovered in +addition to the lintian error tags. To print a long tag description +without running lintian, see L. + +This option overrides B variable in the configuration file. + +=item B<-I>, B<--display-info> + +Display informational ("I:") tags as well. They are normally +suppressed. (This is equivalent to B<-L> ">=info"). + +This option overrides the B variable in the +configuration file. + +Note: B and B may not both appear in the +configuration file. + +=item B<-L> [+|-|=][>=|>|=|<|<=][S|C|S/C], B<--display-level> [+|-|=][>=|>|=|<|<=][S|C|S/C] + +Fine-grained selection of tags to be displayed. It is possible to add, +remove or set the levels to display, specifying a visibility (error, +warning, info, pedantic, or classification. The default settings are +equivalent to B<-L> ">=warning". + +The value consists of 3 parts, where two of them are optional. The +parts are: + +=over 4 + +=item modifier operator + +How to affect the current display level. Can be one of add to ("+"), +remove from ("-") or set to ("=") the display level(s) denoted by the +following selection. + +The default value is "=" (i.e. set the display level). + +=item set operator + +The visibility to be selected. The operator can be one of ">=", ">", +"=", "<" or "<=". As an example, this can be used to select all info +(and more serious) tags via ">=info". + +The default value is "=", which means "exactly" the given visibility. + +=back + +This option overrides the B variable in the +configuration file. The value of the B in +configuration file should be space separated entries in the same +format as passed via command-line. + +Note: B may not be used with B or B +in the configuration file. + +=item B<-o>, B<--no-override> + +Ignore all overrides provided by the package. This option will overrule +B<--show-overrides>. + +This option overrides the B variable in the configuration +file. + +=item B<--pedantic> + +Display pedantic ("P:") tags as well. They are normally suppressed. +(This is equivalent to B<-L> "+=pedantic"). + +Pedantic tags are Lintian at its most pickiest and include checks for +particular Debian packaging styles and checks that many people +disagree with. Expect false positives and Lintian tags that you don't +consider useful if you use this option. Adding overrides for pedantic +tags is probably not worth the effort. + +This option overrides the B variable in the configuration +file. + +Note: B and B may not both appear in the +configuration file. + +=item B<--profile> vendor[/prof] + +Use the profile from vendor (or the profile with that name). If the +profile name does not contain a slash, the default profile for than +vendor is chosen. + +As an example, if you are on Ubuntu and want to use Lintian's Debian +checks, you can use: + + --profile debian + +Likewise, on a Debian machine you can use this to request the Ubuntu +checks. + +If the token I<{VENDOR}> appears in the profile name, B will +substitute the token with a vendor name to find the profile. +B uses L to determine the best vendor to use +(the closer to the current vendor, the better). This is mostly useful +for people implementing their own checks on top of Lintian. + +If not specified, the default value is I<{VENDOR}/main>. + +Please Refer to the Lintian User Manual for the full documentation of +profiles. + +=item B<--show-overrides>, B<--hide-overrides> + +Controls whether tags that have been overridden should be shown. + +The B<--show-overrides> differs from B<--no-overrides> in that shown overridden +tags will still be marked as overridden (using an "O" code). + +If the overridden tags are shown, the related override comments will +also be displayed (unless --quiet is used). Please refer to the Lintian +User Manual for the documentation on how lintian relates comments to a +given override. + + +These options override the B variable in the +configuration file. + +=item B<--suppress-tags> tag1,tag2,... + +Suppress the listed tags. They will not be reported if they occur and +will not affect the exit status of Lintian. This option can be given +multiple times and can be mixed with B<--suppress-tags-from-file>. + +This option can be used together with B<--dont-check-part> ("Not those +checks nor these tags") and B<--check-part> ("Only those checks, but +not these tags (from those checks)") to further reduce the selection of +tags. + +When used with B<--tags>, this option is mostly ignored. + +=item B<--suppress-tags-from-file> file + +Suppress all tags listed in the given file. Blank lines and lines +beginning with # are ignored. All other lines are taken to be tag +names or comma-separated lists of tag names to suppress. The +suppressed tags will not be reported if they occur and will not affect +the exit status of Lintian. + +Tags parsed from the file will be handled as if they had been given to +the B<--suppress-tags> option (e.g. ignored if B<--tags> is used). + +=item B<--tag-display-limit>[=X] + +By default, lintian limits itself to emitting at most 4 instances of each +tag per processable when STDOUT is a TTY. This option specified that limit. +See also B<--no-tag-display-limit>. + +=item B<--no-tag-display-limit> + +By default, lintian limits itself to emitting at most 4 instances of each +tag per processable when STDOUT is a TTY. This option disables that limit. + +When STDOUT is not a TTY, lintian has no limit. See also +B<--tag-display-limit>. + +=back + +Configuration options: + +=over 4 + +=item B<--cfg> configfile + +Read the configuration from configfile rather than the default +locations. This option overrides the B environment +variable. + +=item B<--no-cfg> + +Do not read any configuration file. This option overrides the +B<--cfg> above. + +=item B<--ignore-lintian-env> + +Ignore all environment variables starting with I. + +This option is mostly useful for applications running B for +checking packages and do not want the invoking user to affect the +result (by setting LINTIAN_PROFILE etc.). + +Note it does I cause B to ignore the entire environment +like I or I. The latter can affect the default +profile (or "{VENDOR}" token for B<--profile>). + +Should usually be combined with B<--no-user-dirs> (or unsetting $HOME +and all I variables). + +=item B<--include-dir> dir + +Use dir as an additional "LINTIAN_BASE". The directory is expected +have a similar layout to the LINTIAN_BASE (if it exists), but does not +need to be a full self-contained root. + +B will check this directory for (additional) profiles, data +files, support libraries and checks. The latter two imply that +Lintian may attempt to I from this directory. + +This option may appear more than once; each time adding an additional +directory. Directories are searched in the order they appear on the +command line. + +The additional directories will be checked I the user +directories (though see B<--no-user-dirs>) and I the core +LINTIAN_BASE. + +B: This option should be the very first if given. + +=item B<-j> X, B<--jobs>=X + +Set the limit for how many jobs Lintian will run in parallel. This +option overrides the B variable in the configuration file. + +By default Lintian will use I to determine a reasonable default +(or 2, if the nproc fails). + +=item B<--user-dirs>, B<--no-user-dirs> + +By default, B will check I<$HOME> and I for files +supplied by the user or the local sysadmin (e.g. config files and +profiles). This default can be disabled (and re-enabled) by using +B<--no-user-dirs> (and B<--user-dirs>, respectively). + +These options will I affect the inclusion of LINTIAN_BASE, which +is always included. + +These option can appear multiple times, in which case the last of them +to appear determines the result. + +Note that if the intention is only to disable the user's I<$HOME>, +then unsetting I<$HOME> and I may suffice. Alternatively, +I can be "re-added" by using I<--include-dir> (caveat: +I will be ignored by this). + +If the intention is to avoid (unintentional) side-effects from the +calling user, then this option could be combined with +B<--ignore-lintian-env>. + +If for some reason B<--no-user-dirs> cannot be used, then consider +unsetting I<$HOME> and all the I<$XDG_*> variables (not just the +I<$XDG_*_HOME> ones). + +B: This option should be the very first if given. + +=back + +Developer/Special usage options: + +=over 4 + +=item B<--allow-root> + +Override lintian's warning when it is run with superuser privileges. + +=item B<--keep-lab> + +By default, temporary labs will be removed after lintian is finished. +Specifying this options will leave the lab behind, which might be +useful for debugging purposes. You can find out where the temporary +lab is located by running lintian with the B<--verbose> option. + +=item B<--packages-from-file> X + +The line is read as the path to a file to process (all whitespace is +included!). + +If X is "-", Lintian will read the packages from STDIN. + +=item B<--perf-debug> + +Enable performance related debug logging. + +The data logged and the format used is subject to change with every +release. + +Note that some of the information may also be available (possibly in +a different format) with the B<--debug> option. + +=item B<--perf-output> OUTPUT + +Write performance related debug information to the specified file or +file descriptor. If OUTPUT starts with a '&' or '+', Lintian will +handle OUTPUT specially. Otherwise, Lintian will open the file +denoted by OUTPUT for writing (truncating if it exists, creating it +if it does not exist). + +If the first character of OUTPUT is a & and the rest of argument is a +number N, then lintian attempts to write it to the file descriptor +with the number N. Said file descriptor must be open for writing. +E.g I<&2> makes Lintian write the performance logging to STDERR. + +If the first character of OUTPUT is a +, Lintian will append to the +file rather than truncating it. In this case, the file name is OUTPUT +with initial "+" character removed. E.g. I<+my-file> makes Lintian +append to I + +If Lintian should write the output to a file starting with a literal +'&' or '+', then simply prefix it with "./" (e.g. "+my-file" becomes +"./+my-file"). + +If this option omitted, Lintian will default to using STDOUT. + +=back + +=head1 CHECKS + +@CHECKS@ + +=head1 COLLECTION + +@COLLECTION@ + +=head1 FILES + +Lintian looks for its configuration file in the following locations: + +=over 4 + +=item * The argument given to B<--cfg> + +=item * I<$LINTIAN_CFG> + +=item * I<$XDG_CONFIG_HOME/lintian/lintianrc> + +=item * I<$HOME/.lintianrc> + +Deprecated in Lintian/2.5.12 and newer (use the XDG based variant +above) + +=item * I + +Where XDG_DIR is a directories listed in I<$XDG_CONFIG_DIRS> (or +I if I<$XDG_CONFIG_DIRS> is unset). + +=item * I + +Deprecated in Lintian/2.5.12 and newer (use the XDG based variant +above) + +=back + +Lintian uses the following directories: + +=over 4 + +=item I + +Lintian defaults to creating a temporary lab directory in I. To +change the directory used, set the TMPDIR environment variable to a +suitable directory. TMPDIR can be set in the configuration file. + +=item I + +Scripts that check aspects of a package. + +=item I + +Scripts that collect information about a package and store it for use +by the check scripts. + +=item I + +Supporting data used by Lintian checks and for output formatting. + +=item I + +Utility scripts used by the other lintian scripts. + +=back + +For binary packages, Lintian looks for overrides in a file named +IpackageE> inside the binary +package, where IpackageE> is the name of the binary +package. For source packages, Lintian looks for overrides in +I and then in +I if the first file is not found. +The first path is preferred. See the Lintian User's Manual for the +syntax of overrides. + +=head1 CONFIGURATION FILE + +The configuration file can be used to specify default values for some +options. The general format is: + + option = value + +All whitespace adjacent to the "=" sign as well as leading and +trailing whitespace is ignored. However whitespace within the +value is respected, as demonstrated by this example: + + # Parsed as "opt1" with value "val1" + opt1 = val1 + # Parsed as "opt2" with value "val2.1 val2.2 val2.3" + opt2 = val2.1 val2.2 val2.3 + +Unless otherwise specified, no option may appear more than once. +Lintian will ignore empty lines or lines starting with the +B<#>-character. + +Generally options will be the long form of the command-line option +without the leading dashes. There some exceptions (such as +--profile), where Lintian uses the same name as the environment +variable. + +Lintian only allows a subset of the options specified in the +configuration file; please refer to the individual options in +L. + +In the configuration file, all options listed must have a value, even +if they do not accept a value on command line (e.g. --pedantic). The +values "yes", "y", "1", or "true" will enable such an option and "no", +"n", "0" or "false" will disable it. Prior to the 2.5.2 release, +these values were case sensitive. + +For other options, they generally take the same values as they do on +the command line. Though some options allow a slightly different +format (e.g. --display-level). These exceptions are explained for the +relevant options in L. + +Beyond command line options, it is also allowed to specify the +environment variable "TMPDIR" in the configuration file. + +A sample configuration file could look like: + + # Sample configuration file for lintian + # + # Set the default profile (--profile) + LINTIAN_PROFILE = debian + + # Set the default TMPDIR for lintian to /var/tmp/lintian + # - useful if /tmp is tmpfs with "limited" size. + TMPDIR = /var/tmp/lintian/ + + # Show info (I:) tags by default (--display-info) + # NB: this cannot be used with display-level + display-info=yes + + # Ignore all overrides (--no-override) + # NB: called "override" in the config file + # and has inverted value! + override = no + + # Automatically determine if color should be used + color = auto + +=head1 EXIT STATUS + +=over 4 + +=item B<0> + +Normal operation. + +=item B<1> + +Lintian run-time error. An error message is sent to stderr. + +=item B<2> + +Detected a condition specified via the B<--fail-on> option. This can +be used to trigger a non-zero exit value in case of policy violations. + +=back + +=head1 CHECKING LAST BUILD + +When run in an unpacked package dir (with no package selection +arguments), Lintian will use I to determine the +source and version of the package. Lintian will then attempt to find +a matching I<.changes> file for this source and version combination. + +Lintian will (in order) search the following directories: + +=over 4 + +=item .. + +Used by dpkg-buildpackage(1). + +=item ../build-area + +Used by svn-buildpackage(1). + +=item /var/cache/pbuilder/result + +Used by pbuilder(1) and cowbuilder(1). + +=back + +In each directory, Lintian will attempt to find a I<.changes> file +using the following values as architecture (in order): + +=over 4 + +=item I<$DEB_BUILD_ARCH> (or I) + +The environment variable DEB_BUILD_ARCH (if not set, "dpkg +--print-architecture" will be used instead) + +=item I<$DEB_HOST_ARCH> + +The environment variable DEB_HOST_ARCH. + +=item I + +If dpkg(1) appears to support multi-arch, then any architecture listed +by "dpkg --print-foreign-architectures" will be used (in the order +returned by dpkg). + +=item I + +Pseudo architecture used by mergechanges(1). + +=item I + +Used when building architecture indep packages only (e.g. +dpkg-buildpackage -A). + +=item I + +Used for "source only" builds (e.g. dpkg-buildpackage -S). + +=back + +If a I<.changes> file matches any combination above exists, Lintian +will process the first match as if you had passed it per command line. +If no I<.changes> file can be found, Lintian will print a list of attempted +locations on STDERR and exit 0. + +=head1 EXAMPLES + +=over 4 + +=item B<$ lintian foo.changes> + +Check the changes file itself and any (binary, udeb or source) package +listed in it. + +=item B<$ lintian foo.deb> + +Check binary package foo given by foo.deb. + +=item B<$ lintian foo.dsc> + +Check source package foo given by foo.dsc. + +=item B<$ lintian foo.dsc -L +info> + +Check source package foo given by foo.dsc, including info tags. + +=item B<$ lintian -i foo.changes> + +Check the changes file and, if listed, the source and binary package +of the upload. The output will contain detailed information about the +reported tags. + +=item B<$ lintian> + +Assuming I exists, look for a changes file for the +source in the parent dir. Otherwise, print usage information and +exit. + +=back + +=head1 BUGS + +Lintian does not have any locking mechanisms yet. (Running several +Lintian processes on the same laboratory simultaneously is likely to fail +or corrupt the laboratory.) + +If you discover any other bugs in lintian, please contact the authors. + +=head1 SEE ALSO + +L, Lintian User Manual +(/usr/share/doc/lintian/lintian.html) + +Packaging tools: L, L, +L. + +=head1 AUTHORS + +Niels Thykier + +Richard Braakman + +Christian Schwarz + +Please use the email address for +Lintian related comments. + +=cut diff -Nru lintian-2.93.0/private/build-test-packages lintian-2.89.0ubuntu1/private/build-test-packages --- lintian-2.93.0/private/build-test-packages 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/private/build-test-packages 1970-01-01 00:00:00.000000000 +0000 @@ -1,471 +0,0 @@ -#!/usr/bin/perl - -# Copyright © 1998 Richard Braakman -# Copyright © 2008 Frank Lichtenheld -# Copyright © 2008, 2009 Russ Allbery -# Copyright © 2014 Niels Thykier -# Copyright © 2020 Felix Lechner -# -# This program is free software; you can redistribute it and/or modify -# it under the terms of the GNU General Public License as published by -# the Free Software Foundation; either version 2 of the License, or -# (at your option) any later version. -# -# This program is distributed in the hope that it will be useful, -# but WITHOUT ANY WARRANTY; without even the implied warranty of -# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the -# GNU General Public License for more details. -# -# You should have received a copy of the GNU General Public License -# along with this program. If not, you can find it on the World Wide -# Web at http://www.gnu.org/copyleft/gpl.html, or write to the Free -# Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, -# MA 02110-1301, USA. - -# The harness for Lintian's test suite. For detailed information on -# the test suite layout and naming conventions, see t/tests/README. -# For more information about running tests, see -# doc/tutorial/Lintian/Tutorial/TestSuite.pod - -use v5.20; -use warnings; -use utf8; -use autodie; - -# use Lintian modules that belong to this program -use FindBin; -use lib "$FindBin::RealBin/../lib"; - -use Capture::Tiny qw(capture_merged); -use Cwd qw(realpath); -use File::Copy; -use File::Find::Rule; -use File::stat; -use Getopt::Long; -use IO::Async::Function; -use IO::Async::Loop; -use List::Compare; -use Path::Tiny; -use Time::Duration; -use Time::Moment; -use Time::Piece; -use Try::Tiny; - -use Lintian::IO::Async qw(safe_qx); - -use Test::Lintian::Build qw(build_subject); -use Test::Lintian::ConfigFile qw(read_config); -use Test::Lintian::Helper - qw(rfc822date cache_dpkg_architecture_values get_latest_policy get_recommended_debhelper_version); -use Test::Lintian::Hooks qw(sed_hook sort_lines calibrate); -use Test::Lintian::Prepare qw(prepare); - -use constant SPACE => q{ }; -use constant SLASH => q{/}; -use constant INDENT => q{ }; -use constant NEWLINE => qq{\n}; -use constant TAB => qq{\t}; -use constant EMPTY => q{}; -use constant YES => q{yes}; -use constant NO => q{no}; - -my $processing_start = Time::Moment->from_string(gmtime->datetime . 'Z'); - -# whitelist the environment we permit to avoid things that mess up -# tests, like CFLAGS, DH_OPTIONS, DH_COMPAT, DEB_HOST_ARCH -# TODO: MAKEFLAGS - some of the tests don't cope too well with it -my %PRESERVE_ENV = map { $_ => 1 } qw( - NO_PKG_MANGLE - PATH - TMPDIR - CCACHE_DIR -); - -my @disallowed = grep { !exists $PRESERVE_ENV{$_} } keys %ENV; - -delete $ENV{$_} for @disallowed; - -# Standard pipeline installs ccache; causes write permission errors on Salsa -# https://salsa.debian.org/salsa-ci-team/pipeline/-/issues/164 -$ENV{CCACHE_DISABLE} = 1; - -# Ubuntu auto-builders run pkg-mangle which messes up test packages -$ENV{NO_PKG_MANGLE} //= 'true'; - -$ENV{LINTIAN_BASE} = realpath("$FindBin::RealBin/..") - // die 'Cannot resolve LINTIAN_BASE'; - -# options -my $debug; -my $dump_logs = 1; -my $force_rebuild; -my $numjobs = -1; -my $outpath; -my $verbose = 0; - -Getopt::Long::Configure('bundling'); -unless ( - Getopt::Long::GetOptions( - 'B|force-rebuild' => \$force_rebuild, - 'd|debug+' => \$debug, - 'j|jobs:i' => \$numjobs, - 'L|dump-logs!' => \$dump_logs, - 'v|verbose' => \$verbose, - 'w|work-dir:s' => \$outpath, - 'h|help' => sub {usage(); exit;}, - ) -) { - usage(); - die; -} - -# check number of arguments -die('Please use -h for usage information.') - if @ARGV > 1; - -# get arguments -my ($testset) = @ARGV; - -# default test set -$testset ||= 't'; - -# check test set directory -die "Cannot find testset directory $testset" - unless -d $testset; - -# make sure testset is an absolute path -$testset = path($testset)->absolute->stringify; - -# calculate a default test work directory if none given -$outpath ||= path($testset)->parent->stringify . '/debian/test-out'; - -# create test work directory unless it exists -path($outpath)->mkpath - unless -e $outpath; - -# make sure test work path is a directory -die "Test work directory $outpath is not a directory" - unless -d $outpath; - -# make sure outpath is absolute -$outpath = path($outpath)->relative->stringify; - -say EMPTY; - -# tie verbosity to debug -$verbose = 1 + $debug if $debug; - -# can be 0 without value ("-j"), and -1 if option was not specified at all -$numjobs = default_parallel() if $numjobs <= 0; -say "Running up to $numjobs tests concurrently" - if $numjobs > 1 && $verbose >= 2; - -$ENV{'DUMP_LOGS'} = $dump_logs//NO ? YES : NO; - -# Disable translation support in dpkg as it is a considerable -# unnecessary overhead. -$ENV{'DPKG_NLS'} = 0; - -my $helperpath = "$testset/../bin"; -if (-d $helperpath) { - my $helpers = path($helperpath)->absolute->stringify - // die("Cannot resolve $helperpath: $!"); - $ENV{'PATH'} = "$helpers:$ENV{'PATH'}"; -} - -# get architecture -cache_dpkg_architecture_values(); -say "Host architecture is $ENV{'DEB_HOST_ARCH'}."; - -# get latest policy version and date -($ENV{'POLICY_VERSION'}, $ENV{'POLICY_EPOCH'}) = get_latest_policy(); -say "Latest policy version is $ENV{'POLICY_VERSION'} from " - . rfc822date($ENV{'POLICY_EPOCH'}); - -# get current debhelper compat level; do not name DH_COMPAT; causes conflict -$ENV{'DEFAULT_DEBHELPER_COMPAT'} = get_recommended_debhelper_version(); -say -"Using compat level $ENV{'DEFAULT_DEBHELPER_COMPAT'} as a default for packages built with debhelper."; - -say EMPTY; - -# print environment -my @vars = sort keys %ENV; -say 'Environment:' if @vars; -for my $var (@vars) { say INDENT . "$var=$ENV{$var}" } - -say EMPTY; - -my $status = 0; - -# find spec paths -my @descfiles - = sort File::Find::Rule->file()->name('fill-values')->in("$testset/recipes"); - -my @specpaths = map { path($_)->parent->absolute->stringify } @descfiles; - -# prepare output directories -say 'Preparing the sources for '. scalar @specpaths. ' test packages.' - if @specpaths; - -my @prepqueue = map { path($_)->relative->stringify } @specpaths; - -# for filled templates -my $sourceroot = "$outpath/package-sources"; - -# for built test packages -my $buildroot = "$outpath/packages"; - -my @relative - = map { path($_)->parent->relative("$testset/recipes") } @specpaths; -my @sourcepaths = map {$_->absolute($sourceroot)->stringify } @relative; -my @buildpaths = map {$_->absolute($buildroot)->stringify } @relative; - -# remove obsolete package sources -my @foundsources = map { path($_)->parent->absolute->stringify; } - File::Find::Rule->file->name('fill-values')->in($sourceroot); -my $sourcelc = List::Compare->new('--unsorted', \@foundsources, \@sourcepaths); -my @obsoletesources = $sourcelc->get_Lonly; -path($_)->remove_tree for @obsoletesources; - -# remove obsolete built packages -my @foundpackages = map { path($_)->parent->absolute->stringify; } - File::Find::Rule->file->name('source-files.sha1sums')->in($buildroot); -my $packagelc= List::Compare->new('--unsorted', \@foundpackages, \@buildpaths); -my @obsoletepackages = $packagelc->get_Lonly; -path($_)->remove_tree for @obsoletepackages; - -# remove empty directories -for my $folder (@obsoletesources, @obsoletepackages) { - my $candidate = path($folder)->parent; - while ($candidate->exists && !$candidate->children) { - rmdir $candidate->stringify; - $candidate = $candidate->parent; - } -} - -$ENV{PERL_PATH_TINY_NO_FLOCK} =1; - -my $prepare = IO::Async::Function->new( - code => sub { - my ($specpath) = @_; - - # label process - $0 = "Lintian prepare test: $specpath"; - - # calculate destination - my $relative = path($specpath)->parent->relative("$testset/recipes"); - my $sourcepath = $relative->absolute($sourceroot)->stringify; - my $buildpath = $relative->absolute($buildroot)->relative->stringify; - - my $error; - - # capture output - my $log = capture_merged { - - try { - - # remove destination - path($sourcepath)->remove_tree - if -e $sourcepath; - - # prepare - prepare($specpath, $sourcepath, $testset, $force_rebuild); - - }catch { - # catch any error - $error = $_; - }; - }; - - # save log; - my $logfile = "$sourcepath.log"; - path($logfile)->spew_utf8($log) if $log; - - # print something if there was an error - die(($log // EMPTY) . "Preparation failed for $specpath: $error") - if $error; - - return $specpath; - }, - max_workers => $numjobs, - max_worker_calls => 1, -); - -my $loop = IO::Async::Loop->new; -$loop->add($prepare); - -$SIG{INT} = sub { $prepare->stop; die "Caught a sigint $!" }; -my @preptasks = map {$prepare->call(args => [$_])} sort @prepqueue; - -my $allprepared = Future->wait_all(@preptasks); - -$loop->await($allprepared); - -my @failedprep = $allprepared->failed_futures; -if (@failedprep) { - say EMPTY; - say 'Failed preparation tasks:'; - say NEWLINE . $_->failure for @failedprep; - exit 1; -} else { - say 'Package sources are ready.'; -} - -say EMPTY; - -my $build = IO::Async::Function->new( - code => sub { - my ($specpath, $position, $total) = @_; - - # set a predictable locale - $ENV{'LC_ALL'} = 'C'; - - # many tests create files via debian/rules - umask(022); - - # get destination - my $relative = path($specpath)->parent->relative("$testset/recipes"); - my $sourcepath = $relative->absolute($sourceroot)->relative->stringify; - my $buildpath = $relative->absolute($buildroot)->relative->stringify; - - my $sha1sums - = qx{cd $sourcepath; find . -type f -print0 | sort -z | xargs -0 sha1sum}; - - my $checksum_path = "$buildpath/source-files.sha1sums"; - if (-r $checksum_path) { - my $previous = path($checksum_path)->slurp; - - # only rebuild if needed - return - if $sha1sums eq $previous; - } - - $0 = "Lintian build test: $specpath [$position/$total]"; - say "Building in $buildpath [$position/$total]"; - - path($buildpath)->remove_tree - if -e $buildpath; - path($buildpath)->mkpath; - - # read dynamic file names - my $runfiles = "$sourcepath/files"; - my $files = read_config($runfiles); - - my $error; - - my $log = capture_merged { - - try { - # call runner - build_subject($sourcepath, $buildpath); - }catch { - # catch any error - $error = $_; - }; - }; - - # delete old runner log - my $betterlogpath = $buildpath . SLASH . $files->unfolded_value('Log'); - unlink $betterlogpath if -f $betterlogpath; - - # move the early log for directory preparation to position of runner log - my $earlylogpath = "$sourcepath.log"; - move($earlylogpath, $betterlogpath) if -f $earlylogpath; - - # append runner log to population log - path($betterlogpath)->append_utf8($log) if length $log; - - # add error if there was one - path($betterlogpath)->append_utf8($error) if length $error; - - path($checksum_path)->spew($sha1sums) - unless length $error; - - # print log and die on error - die(($log // EMPTY) . "Builder died for $buildpath: $error") - if length $error; - - return $specpath; - }, - max_workers => $numjobs, - max_worker_calls => 1, -); - -$loop->add($build); - -$SIG{INT} = sub { $build->stop; die "Caught a sigint $!" }; - -my $counter; -my @buildtasks= map {$build->call(args => [$_, ++$counter, scalar @specpaths])} - sort @specpaths; - -my $allbuilt = Future->wait_all(@buildtasks); - -$loop->await($allbuilt); - -my @failedbuilds = $allbuilt->failed_futures; -if (@failedbuilds) { - say EMPTY; - say 'Failed build tasks:'; - say NEWLINE . $_->failure for @failedbuilds; - exit 1; -} else { - say 'All test packages are up to date.'; -} - -say EMPTY; - -my $processing_end = Time::Moment->from_string(gmtime->datetime . 'Z'); -my $duration = duration($processing_start->delta_seconds($processing_end)); -say "Building the test packages took $duration."; - -say EMPTY; - -exit 0; - -# program is done - -=item default_parallel - -=cut - -# Return the default number of parallelization to be used -sub default_parallel { - # check cpuinfo for the number of cores... - my $cpus = safe_qx('nproc'); - if ($cpus =~ m/^\d+$/) { - # Running up to twice the number of cores usually gets the most out - # of the CPUs and disks but it might be too aggressive to be the - # default for -j. Only use +1 then. - return $cpus + 1; - } - - # No decent number of jobs? Just use 2 as a default - return 2; -} - -sub usage { - print <<"END"; -Usage: $0 [options] [-j []] [] - - -d Display additional debugging information - --dump-logs Print build log to STDOUT, if a build fails. - -j [] Run up to jobs in parallel. - If -j is passed without specifying , the number - of jobs started is +1. - -v Be more verbose - --help, -h Print this help and exit - - The optional 3rd parameter causes runtests to only run tests that match - the particular selection. This parameter can be a list of selectors: - what:[,] -END - return; -} - -# Local Variables: -# indent-tabs-mode: nil -# cperl-indent-level: 4 -# End: -# vim: syntax=perl sw=4 sts=4 sr et diff -Nru lintian-2.93.0/private/build-test-packages-if-needed lintian-2.89.0ubuntu1/private/build-test-packages-if-needed --- lintian-2.93.0/private/build-test-packages-if-needed 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/private/build-test-packages-if-needed 1970-01-01 00:00:00.000000000 +0000 @@ -1,95 +0,0 @@ -#!/bin/sh -# -# Copyright © 2019 Chris Lamb /dev/null | \ - grep MD5Sum: | cut -d' ' -f2 | cut -d_ -f1-2; - dpkg -l | awk '{ print $2 "_" $3 }' - ) | sort -} - -CHECKSUM="$(Checksum_input | sha1sum | cut -d ' ' -f1)" -CACHE_FILENAME="${CACHE_DIR}/${PIPELINE}-${CHECKSUM}.tar.xz" - -echo "Cache filename: ${CACHE_FILENAME}" - -# get some debug output -apt-cache --quiet policy -apt-cache --quiet policy debhelper - -# get prequisites early, otherwise tar fails for lack of xz-utils -env DEBIAN_FRONTEND=noninteractive apt-get --quiet --yes --option dir::cache::archives="${CACHE_DIR}" --option Debug::pkgProblemResolver=yes build-dep . - -mkdir -p .cache - -echo "I: Showing artifacts in .cache" >&2 -ls -al .cache >&2 - -echo "I: Looking for ${CACHE_FILENAME}" >&2 - -if [ -f "${CACHE_FILENAME}" ] -then - echo "I: Extracting ${CACHE_FILENAME}" >&2 - rm -rf debian/test-out/packages - tar xfJ "${CACHE_FILENAME}" -fi - -private/build-test-packages - -echo "I: Removing obsolete test package artifacts from .cache" >&2 -find .cache \ - -maxdepth 1 \ - -type f \ - -regextype posix-egrep \ - -regex "^\.cache/${PIPELINE}-[[:xdigit:]]{40}\.tar\.xz\$" \ - -print \ - -delete - -echo "I: Removing old-style artifacts (no pipeline in name) from .cache" >&2 -find .cache \ - -maxdepth 1 \ - -type f \ - -regextype posix-egrep \ - -regex '^\.cache/[[:xdigit:]]{40}\.tar\.xz$' \ - -print \ - -delete - -echo "I: Creating ${CACHE_FILENAME}" >&2 -mkdir -p "$(dirname "${CACHE_FILENAME}")" -tar cfJ "${CACHE_FILENAME}" debian/test-out/packages - -cp -v "${CACHE_FILENAME}" test-packages.tar.xz - -echo "I: Showing artifacts in .cache" >&2 -ls -al .cache >&2 diff -Nru lintian-2.93.0/private/generate-html-docs lintian-2.89.0ubuntu1/private/generate-html-docs --- lintian-2.93.0/private/generate-html-docs 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/private/generate-html-docs 2020-08-10 09:59:45.000000000 +0000 @@ -61,14 +61,29 @@ $dist = $1 if $line =~ m{\A Distribution: \s*+ (\S++) \s* \Z}xsm; } close($fd); - if ((not defined($dist) or $dist eq 'UNRELEASED') and -d '.git') { - - delete $ENV{'GITDIR'}; - # For unreleased versions, git describe is probably a better # choice when available. - my $guess = qx{git describe}; + my $guess; + require IO::Async::Loop; + require IO::Async::Process; + delete $ENV{'GITDIR'}; + + my $loop = IO::Async::Loop->new; + my $future = $loop->new_future; + my $process = IO::Async::Process->new( + command => ['git', 'describe'], + stdout => { into => \$guess }, + on_finish => sub { + my ($self, $exitcode) = @_; + my $status = ($exitcode >> 8); + + $future->done('Done with git describe'); + return; + }); + + $loop->add($process); + $loop->await($future); chomp $guess; $version = $guess @@ -91,9 +106,3 @@ sub version_tag_comment { return q{}; } - -# Local Variables: -# indent-tabs-mode: nil -# cperl-indent-level: 4 -# End: -# vim: syntax=perl sw=4 sts=4 sr et diff -Nru lintian-2.93.0/private/generate-lintian-pod lintian-2.89.0ubuntu1/private/generate-lintian-pod --- lintian-2.93.0/private/generate-lintian-pod 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/private/generate-lintian-pod 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,103 @@ +#!/usr/bin/perl + +use v5.20; +use warnings; +use utf8; +use autodie; + +# Find the lib directory of lintian-root (defaulting to ./lib/) +BEGIN { + $ENV{LINTIAN_BASE} //= '.'; +} +use lib $ENV{LINTIAN_BASE} . '/lib/'; + +use Lintian::Deb822::Parser qw(read_dpkg_control); + +my @keywords = (); + +foreach my $kw (qw(conffiles shlibs Standards-Version)){ + push @keywords, [qr/$kw/, "B<$kw>"]; +} + +open(my $file, '<', 'man/lintian.pod.in'); + +while(my $line = <$file>){ + chomp($line); + if($line eq '@CHECKS@'){ + extract_data('checks', 'check-script'); + } else { + print "$line\n"; + } +} +close($file); + +sub pretty_print { + my $text = shift; + my $inex = 0; + $text =~ s@\n\s\.\n\s@\n\n\n@og; + $text =~ s@\n\s@\n@og; + $text =~ s/\&([^;]+)\;/E<$1>/og; # do > -> E + $text =~ s/(\S+\(\d+\))/L<$1>/og; # link to manpages + foreach my $line (split(m/\n/o, $text)) { + if ($line =~ m/^ /o){ + if(!$inex){ + # Start of an example. + $inex = 1; + # Give an extra line break. + $line = "\n$line"; + } + # Example line + print "$line\n"; + next; + } elsif ($inex) { + # First line after an example. + $inex = 0; + $line = "\n\n$line"; + } + # Normal line + # Replace simple html tags + $line =~ s@\([^<]*)\@I<$1>@iog; + $line =~ s@\([^<]*)\@B<$1>@iog; + $line =~ s@\([^<]*)\@I<$1>@iog; + # Underline paths + $line =~ s@(\S*/(?:[^/ \t]*[^/ \t.,:;]/?)*)@I<$1>@og; + # Policy Manual + $line =~ s@Policy Manual@B@og; + foreach my $kw (@keywords){ + my ($s,$r) = @$kw; + $line =~ s|\b\Q$s\E\b|$r|; + } + print "$line\n"; + } + print "\n\n"; + return; +} + +sub extract_data { + my ($folder, $fname) = @_; + print "=over 4\n\n"; + foreach my $file (glob("$folder/*.desc")) { + my ($header, @ignore) = read_dpkg_control($file); + my $name = $header->{$fname}; + my $desc; + + next + if $name eq 'lintian'; + + $desc = $header->{'Manpage'}; + next + unless defined $desc; + + print "=item B<$name>\n\n"; + + pretty_print($desc); + } + print "=back\n\n"; + return; +} + +# Local Variables: +# indent-tabs-mode: nil +# cperl-indent-level: 4 +# End: +# vim: syntax=perl sw=4 sts=4 sr et diff -Nru lintian-2.93.0/private/generate-profiles lintian-2.89.0ubuntu1/private/generate-profiles --- lintian-2.93.0/private/generate-profiles 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/private/generate-profiles 1970-01-01 00:00:00.000000000 +0000 @@ -1,188 +0,0 @@ -#!/usr/bin/perl - -# Generates profiles for the Debian vendor -# - Remember to add new profiles to d/rules under profiles - -use v5.20; -use warnings; -use utf8; -use autodie; - -# use Lintian modules that belong to this program -use FindBin; -use lib "$FindBin::RealBin/../lib"; - -use Cwd qw(realpath); -use File::Find::Rule; -use List::Compare; -use List::Util qw(uniq); -use LWP::Simple; -use Path::Tiny; -use YAML::XS; - -use Lintian::Deb822::File; - -use constant EMPTY => q{}; -use constant SPACE => q{ }; -use constant COMMA => q{,}; -use constant HYPHEN => q{-}; -use constant INDENT => q{ }; -use constant NEWLINE => qq{\n}; - -$ENV{LINTIAN_BASE} = realpath("$FindBin::RealBin/..") - // die 'Cannot resolve LINTIAN_BASE'; - -# generate main profile -my $checkdir = "$ENV{LINTIAN_BASE}/checks"; -my @modulepaths = File::Find::Rule->file->name('*.pm')->in($checkdir); - -my @allchecks; -for my $modulepath (@modulepaths) { - my $relative = path($modulepath)->relative($checkdir)->stringify; - my ($name) = ($relative =~ qr/^(.*)\.pm$/); - - push(@allchecks, $name); -} - -# add check for tags issued by internal infrastructure -push(@allchecks, 'lintian'); - -generate_profile( - 'debian', 'main', - { - 'Enable-Tags-From-Check' => \@allchecks, - }); - -# generate profile for FTP Master auto-reject -my $auto_reject_url = 'https://ftp-master.debian.org/static/lintian.tags'; -my $contents = get($auto_reject_url); -die "Couldn't get file from $auto_reject_url" - unless defined $contents; - -my $yaml = Load($contents); -die "Couldn't parse output from $auto_reject_url" - unless defined $yaml; - -my $base = $yaml->{lintian}; -die "Couldn't parse document base for $auto_reject_url" - unless defined $base; - -my @want_fatal = uniq @{ $base->{fatal} // [] }; -my @want_nonfatal = uniq @{ $base->{nonfatal} // [] }; - -# find all tags known to Lintian -my @known_tags; -my %new_name; -my $tagroot = "$ENV{LINTIAN_BASE}/tags"; -my @descfiles = File::Find::Rule->file()->name('*.desc')->in($tagroot); -for my $tagpath (@descfiles) { - - my $deb822 = Lintian::Deb822::File->new; - my @sections = $deb822->read_file($tagpath); - die "Tag in $tagpath does not have exactly one paragraph" - unless scalar @sections == 1; - - my $fields = $sections[0]; - - my $name = $fields->value('Tag'); - push(@known_tags, $name); - - my @renamed_from = $fields->trimmed_list('Renamed-From'); - - my @taken = grep { exists $new_name{$_} } @renamed_from; - - say "Warning: Ignoring $_ as an alias for $new_name{$_} in favor of $name." - for @taken; - - $new_name{$_} = $name for @renamed_from; -} - -my $old_lc - = List::Compare->new([@want_fatal, @want_nonfatal], [keys %new_name]); -my @old_names = $old_lc->get_intersection; -say 'FTP Master uses old tag names for auto-rejection:' - if @old_names; -say INDENT . "- $_ => $new_name{$_}" for @old_names; - -# replace old names -@want_fatal = uniq map { $new_name{$_} // $_ } @want_fatal; -@want_nonfatal = uniq map { $new_name{$_} // $_ } @want_nonfatal; - -my $fatal_lc = List::Compare->new(\@want_fatal, \@known_tags); -my @unknown_fatal = $fatal_lc->get_Lonly; -my @fatal = $fatal_lc->get_intersection; - -my $nonfatal_lc = List::Compare->new(\@want_nonfatal, \@known_tags); -my @unknown_nonfatal = $nonfatal_lc->get_Lonly; -my @nonfatal = $nonfatal_lc->get_intersection; - -my @unknown = (@unknown_fatal, @unknown_nonfatal); -say 'Warning, disregarding unknown tags for profile ftp-master-auto-reject:' - if @unknown; -say INDENT . HYPHEN . SPACE . $_ for @unknown; - -say 'Found ' - . scalar @fatal - . ' fatal and ' - . scalar @nonfatal - . ' non-fatal tags for profile ftp-master-auto-reject.'; - -generate_profile( - 'debian', - 'ftp-master-auto-reject', - { - # "lintian" is enabled by default, so we explicitly disable it. - 'Disable-Tags-From-Check' => ['lintian'], - 'Enable-Tags' => [@fatal, @nonfatal], - }, - { - 'Tags' => \@fatal, - 'Overridable' => ['no'], - }); - -exit 0; - -sub generate_profile { - my ($vendor, $name, @paragraphs) = @_; - - my $text =<mkpath - unless -d $folder; - - path("$folder/$name.profile")->spew($text); - - return; -} - -sub write_paragraph { - my ($paragraph) = @_; - - my $text = EMPTY; - - foreach my $field (sort keys %{$paragraph}) { - $text .= "$field:" . NEWLINE; - - my @values = sort @{$paragraph->{$field}}; - my $separator = (scalar @values > 1 ? COMMA : EMPTY); - - $text .= SPACE . $_ . $separator . NEWLINE for @values; - } - - $text .= NEWLINE - if length $text; - - return $text; -} - -# Local Variables: -# indent-tabs-mode: nil -# cperl-indent-level: 4 -# End: -# vim: syntax=perl sw=4 sts=4 sr et diff -Nru lintian-2.93.0/private/generate-profiles.pl lintian-2.89.0ubuntu1/private/generate-profiles.pl --- lintian-2.93.0/private/generate-profiles.pl 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/private/generate-profiles.pl 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,185 @@ +#!/usr/bin/perl + +# Generates profiles for the Debian vendor +# - Remember to add new profiles to d/rules under profiles + +use v5.20; +use warnings; +use utf8; +use autodie; + +BEGIN { + $ENV{'LINTIAN_BASE'} //= q{.}; +} + +use File::Find::Rule; +use List::Compare; +use List::Util qw(uniq); +use LWP::Simple; +use Path::Tiny; +use YAML::XS; + +use lib "$ENV{LINTIAN_BASE}/lib"; + +use Lintian::Deb822::Parser qw(read_dpkg_control); + +use constant EMPTY => q{}; +use constant SPACE => q{ }; +use constant COMMA => q{,}; +use constant HYPHEN => q{-}; +use constant INDENT => q{ }; +use constant NEWLINE => qq{\n}; + +# generate main profile +my $checkdir = "$ENV{LINTIAN_BASE}/checks"; +my @modulepaths = File::Find::Rule->file->name('*.pm')->in($checkdir); + +my @allchecks; +for my $modulepath (@modulepaths) { + my $relative = path($modulepath)->relative($checkdir)->stringify; + my ($name) = ($relative =~ qr/^(.*)\.pm$/); + + push(@allchecks, $name); +} + +# add check for tags issued by internal infrastructure +push(@allchecks, 'lintian'); + +generate_profile( + 'debian', 'main', + { + 'Enable-Tags-From-Check' => \@allchecks, + }); + +# generate profile for FTP Master auto-reject +my $auto_reject_url = 'https://ftp-master.debian.org/static/lintian.tags'; +my $contents = get($auto_reject_url); +die "Couldn't get file from $auto_reject_url" + unless defined $contents; + +my $yaml = Load($contents); +die "Couldn't parse output from $auto_reject_url" + unless defined $yaml; + +my $base = $yaml->{lintian}; +die "Couldn't parse document base for $auto_reject_url" + unless defined $base; + +my @want_fatal = uniq @{ $base->{fatal} // [] }; +my @want_nonfatal = uniq @{ $base->{nonfatal} // [] }; + +# find all tags known to Lintian +my @known_tags; +my %new_name; +my $tagroot = "$ENV{LINTIAN_BASE}/tags"; +my @descfiles = File::Find::Rule->file()->name('*.desc')->in($tagroot); +for my $tagpath (@descfiles) { + my @paragraphs = read_dpkg_control($tagpath); + die "Tag in $tagpath does not have exactly one paragraph" + unless scalar @paragraphs == 1; + + my %fields = %{ $paragraphs[0] }; + + my $name = $fields{Tag}; + push(@known_tags, $fields{Tag}); + + my @renamed_from= grep { length } + grep { s/^\s*|\s*$//g } split(/,/, $fields{'Renamed-From'} // EMPTY); + + my @taken = grep { exists $new_name{$_} } @renamed_from; + + say "Warning: Ignoring $_ as an alias for $new_name{$_} in favor of $name." + for @taken; + + $new_name{$_} = $name for @renamed_from; +} + +my $old_lc + = List::Compare->new([@want_fatal, @want_nonfatal], [keys %new_name]); +my @old_names = $old_lc->get_intersection; +say 'FTP Master uses old tag names for auto-rejection:' + if @old_names; +say INDENT . "- $_ => $new_name{$_}" for @old_names; + +# replace old names +@want_fatal = uniq map { $new_name{$_} // $_ } @want_fatal; +@want_nonfatal = uniq map { $new_name{$_} // $_ } @want_nonfatal; + +my $fatal_lc = List::Compare->new(\@want_fatal, \@known_tags); +my @unknown_fatal = $fatal_lc->get_Lonly; +my @fatal = $fatal_lc->get_intersection; + +my $nonfatal_lc = List::Compare->new(\@want_nonfatal, \@known_tags); +my @unknown_nonfatal = $nonfatal_lc->get_Lonly; +my @nonfatal = $nonfatal_lc->get_intersection; + +my @unknown = (@unknown_fatal, @unknown_nonfatal); +say 'Warning, disregarding unknown tags for profile ftp-master-auto-reject:' + if @unknown; +say INDENT . HYPHEN . SPACE . $_ for @unknown; + +say 'Found ' + . scalar @fatal + . ' fatal and ' + . scalar @nonfatal + . ' non-fatal tags for profile ftp-master-auto-reject.'; + +generate_profile( + 'debian', + 'ftp-master-auto-reject', + { + # "lintian" is enabled by default, so we explicitly disable it. + 'Disable-Tags-From-Check' => ['lintian'], + 'Enable-Tags' => [@fatal, @nonfatal], + }, + { + 'Tags' => \@fatal, + 'Overridable' => ['no'], + }); + +exit 0; + +sub generate_profile { + my ($vendor, $name, @paragraphs) = @_; + + my $text =<mkpath + unless -d $folder; + + path("$folder/$name.profile")->spew($text); + + return; +} + +sub write_paragraph { + my ($paragraph) = @_; + + my $text = EMPTY; + + foreach my $field (sort keys %{$paragraph}) { + $text .= "$field:" . NEWLINE; + + my @values = sort @{$paragraph->{$field}}; + my $separator = (scalar @values > 1 ? COMMA : EMPTY); + + $text .= SPACE . $_ . $separator . NEWLINE for @values; + } + + $text .= NEWLINE + if length $text; + + return $text; +} + +# Local Variables: +# indent-tabs-mode: nil +# cperl-indent-level: 4 +# End: +# vim: syntax=perl sw=4 sts=4 sr et diff -Nru lintian-2.93.0/private/generate-tag-summary lintian-2.89.0ubuntu1/private/generate-tag-summary --- lintian-2.93.0/private/generate-tag-summary 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/private/generate-tag-summary 2020-08-10 09:59:45.000000000 +0000 @@ -7,13 +7,15 @@ use utf8; use autodie; -# use Lintian modules that belong to this program -use FindBin; -use lib "$FindBin::RealBin/../lib"; - use Getopt::Long; -use Lintian::IPC::Run3 qw(safe_qx); +BEGIN { + $ENV{'LINTIAN_BASE'} //= '.'; +} + +use lib "$ENV{'LINTIAN_BASE'}/lib/"; + +use Lintian::IO::Async qw(safe_qx); my (%added, %removed, %opt); @@ -41,7 +43,7 @@ print "Assuming commit range to be: ${commit_range}\n"; } -open(my $fd, '-|', 'git', 'diff', $commit_range, '--', 'tags/*/*.tag'); +open(my $fd, '-|', 'git', 'diff', $commit_range, '--', 'tags/*/*.desc'); while (my $line = <$fd>) { chomp($line); next unless $line =~ m{ \A ([\+-]) Tag: \s*+ ([^ ]++) \s*+ \Z}xsm; diff -Nru lintian-2.93.0/private/gitlab-ci-pipeline lintian-2.89.0ubuntu1/private/gitlab-ci-pipeline --- lintian-2.93.0/private/gitlab-ci-pipeline 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/private/gitlab-ci-pipeline 1970-01-01 00:00:00.000000000 +0000 @@ -1,96 +0,0 @@ -#!/bin/bash -# ^^^ bash provides 'time', and is also the standard in .gitlab-ci.yml -# -# Copyright © 2019 Chris Lamb -# Copyright © 2020 Felix Lechner -# -# This program is free software; you can redistribute it and/or modify -# it under the terms of the GNU General Public License as published by -# the Free Software Foundation; either version 2 of the License, or -# (at your option) any later version. -# -# This program is distributed in the hope that it will be useful, -# but WITHOUT ANY WARRANTY; without even the implied warranty of -# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the -# GNU General Public License for more details. -# -# You should have received a copy of the GNU General Public License -# along with this program. If not, you can find it on the World Wide -# Web at http://www.gnu.org/copyleft/gpl.html, or write to the Free -# Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, -# MA 02110-1301, USA. - -set -eux - -CACHE_DIR="${1}" -PIPELINE="${2}" - -Checksum_input () { - # Local files that, if changed, should result in a rebuild of the test - # packages. - find \ - private/build-test-packages \ - lib/Test/ \ - -type f -print0 | sort -z | xargs -0 sha1sum - - # Rebuild if any build-dependency or installed package changes - ( - apt-get --quiet --yes --print-uris build-dep . 2>/dev/null | \ - grep MD5Sum: | cut -d' ' -f2 | cut -d_ -f1-2; - dpkg -l | awk '{ print $2 "_" $3 }' - ) | sort -} - -# for apt and friends -export DEBIAN_FRONTEND="noninteractive" - -# update package info -apt-get --quiet update - -if [ "${PIPELINE}" == "stable" ] ; then - - # get the release code name - source /etc/os-release - - # ignore status when backports repo is not set up, i.e. unstable or new releases - apt-get --quiet --yes --target-release "${VERSION_CODENAME}-backports" --option dir::cache::archives="${CACHE_DIR}" install debhelper || true - -fi - -# get prequisites early, otherwise tar fails for lack of xz-utils -apt-get --quiet --yes --option dir::cache::archives="${CACHE_DIR}" --option Debug::pkgProblemResolver=yes build-dep . - -mkdir -p "${CACHE_DIR}" -echo "I: Showing artifacts in ${CACHE_DIR}" >&2 -ls -al "${CACHE_DIR}" >&2 - -CHECKSUM="$(Checksum_input | sha1sum | cut -d ' ' -f1)" -CACHE_FILENAME="${CACHE_DIR}/${PIPELINE}-${CHECKSUM}.tar.xz" -echo "I: Looking for ${CACHE_FILENAME}" >&2 - -if [ -f "${CACHE_FILENAME}" ] -then - echo "I: Extracting ${CACHE_FILENAME}" >&2 - rm -rf debian/test-out/packages - tar xfJ "${CACHE_FILENAME}" -fi - -time private/build-test-packages - -echo "I: Removing obsolete test package artifacts for ${PIPELINE} pipeline from ${CACHE_DIR}" >&2 -find "${CACHE_DIR}" \ - -maxdepth 1 \ - -type f \ - -regextype posix-egrep \ - -regex "^${CACHE_DIR}/${PIPELINE}-[[:xdigit:]]{40}\.tar\.xz\$" \ - -print \ - -delete - -echo "I: Creating ${CACHE_FILENAME}" >&2 -mkdir -p "$(dirname "${CACHE_FILENAME}")" -tar cfJ "${CACHE_FILENAME}" debian/test-out/packages - -echo "I: Showing artifacts in ${CACHE_DIR}" >&2 -ls -al "${CACHE_DIR}" >&2 - -time private/runtests diff -Nru lintian-2.93.0/private/refresh-archs lintian-2.89.0ubuntu1/private/refresh-archs --- lintian-2.93.0/private/refresh-archs 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/private/refresh-archs 2020-08-10 09:59:45.000000000 +0000 @@ -1,5 +1,6 @@ #!/usr/bin/perl +#################### # Copyright © 2012 Niels Thykier # - Based on a shell script by Raphael Geissert # @@ -15,21 +16,24 @@ # # You should have received a copy of the GNU General Public License # along with this file. If not, see . +#################### use v5.20; use warnings; use utf8; use autodie; -# use Lintian modules that belong to this program -use FindBin; -use lib "$FindBin::RealBin/../lib"; - use File::Temp qw(tempfile); use POSIX qw (strftime); +BEGIN { + $ENV{'LINTIAN_BASE'} //= '.'; +} + +use lib "$ENV{'LINTIAN_BASE'}/lib/"; + use Lintian::Deb822::Parser qw(parse_dpkg_control_string); -use Lintian::IPC::Run3 qw(safe_qx); +use Lintian::IO::Async qw(safe_qx); my $datapath = shift; my %hardening = ( diff -Nru lintian-2.93.0/private/refresh-debhelper-data lintian-2.89.0ubuntu1/private/refresh-debhelper-data --- lintian-2.93.0/private/refresh-debhelper-data 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/private/refresh-debhelper-data 2020-08-10 09:59:45.000000000 +0000 @@ -1,5 +1,6 @@ #!/bin/sh +#################### # Copyright © 2008 by Raphael Geissert # Copyright © 2017-2018 Chris Lamb # @@ -15,6 +16,7 @@ # # You should have received a copy of the GNU General Public License # along with this file. If not, see . +#################### set -e diff -Nru lintian-2.93.0/private/refresh-ftp-master-tags lintian-2.89.0ubuntu1/private/refresh-ftp-master-tags --- lintian-2.93.0/private/refresh-ftp-master-tags 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/private/refresh-ftp-master-tags 2020-08-10 09:59:45.000000000 +0000 @@ -27,11 +27,20 @@ # Not a B-D and script is compile tested... require LWP::Simple; LWP::Simple->import(qw(get)); - use POSIX qw(strftime); use List::MoreUtils qw(uniq); +BEGIN { + my $LINTIAN_BASE = $ENV{'LINTIAN_BASE'}; + if (not $LINTIAN_BASE) { + require Cwd; + $ENV{'LINTIAN_BASE'} = $LINTIAN_BASE = Cwd::cwd(); + } else { + chdir($LINTIAN_BASE); + } +} + our $YAML_URL = 'https://ftp-master.debian.org/static/lintian.tags'; # Retrieve the YAML file that determines which ftp-master tags warrant a diff -Nru lintian-2.93.0/private/refresh-insserv-data lintian-2.89.0ubuntu1/private/refresh-insserv-data --- lintian-2.93.0/private/refresh-insserv-data 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/private/refresh-insserv-data 2020-08-10 09:59:45.000000000 +0000 @@ -1,5 +1,6 @@ #!/bin/sh +#################### # Copyright © 2008, 2010 by Raphael Geissert # Copyright © 2017 Chris Lamb # @@ -15,6 +16,7 @@ # # You should have received a copy of the GNU General Public License # along with this file. If not, see . +#################### set -eu diff -Nru lintian-2.93.0/private/refresh-locale-codes lintian-2.89.0ubuntu1/private/refresh-locale-codes --- lintian-2.93.0/private/refresh-locale-codes 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/private/refresh-locale-codes 2020-08-10 09:59:45.000000000 +0000 @@ -24,12 +24,17 @@ use utf8; use autodie; -# use Lintian modules that belong to this program -use FindBin; -use lib "$FindBin::RealBin/../lib"; - use POSIX qw(strftime); +BEGIN { + # determine LINTIAN_BASE + my $LINTIAN_BASE = $ENV{'LINTIAN_BASE'} || '.'; + $ENV{'LINTIAN_BASE'} = $LINTIAN_BASE + unless exists $ENV{'LINTIAN_BASE'}; +} + +use lib "$ENV{'LINTIAN_BASE'}/lib"; + use Lintian::Util qw(locate_executable); my ($DATADIR) = @ARGV; diff -Nru lintian-2.93.0/private/refresh-manual-refs lintian-2.89.0ubuntu1/private/refresh-manual-refs --- lintian-2.93.0/private/refresh-manual-refs 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/private/refresh-manual-refs 2020-08-10 09:59:45.000000000 +0000 @@ -20,9 +20,11 @@ # Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, # MA 02110-1301, USA. -# You need copies of all the relevant manuals installed in the standard -# places locally (packages debian-policy, developers-reference, doc-base, -# python, lintian, menu, java-policy and vim-doc). +# Should be run from the top level of the Lintian source tree or with +# LINTIAN_BASE set appropriately. You need copies of all the relevant manuals +# installed in the standard places locally (packages debian-policy, +# developers-reference, doc-base, python, lintian, menu, java-policy and +# vim-doc). use v5.20; use warnings; @@ -30,14 +32,22 @@ use autodie; use open qw(:std :encoding(UTF-8)); -# use Lintian modules that belong to this program -use FindBin; -use lib "$FindBin::RealBin/../lib"; - use File::Basename; use List::MoreUtils qw(none); use POSIX qw(strftime); +BEGIN { + my $LINTIAN_BASE = $ENV{'LINTIAN_BASE'}; + if (not $LINTIAN_BASE) { + require Cwd; + $ENV{'LINTIAN_BASE'} = $LINTIAN_BASE = Cwd::cwd(); + } else { + chdir($LINTIAN_BASE); + } +} + +my $LINTIAN_BASE = $ENV{'LINTIAN_BASE'}; + # For each manual, we need: # * Location of the manual index on the local filesystem # * Base URL for the eventual target of the reference (or empty string if no diff -Nru lintian-2.93.0/private/runtests lintian-2.89.0ubuntu1/private/runtests --- lintian-2.93.0/private/runtests 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/private/runtests 1970-01-01 00:00:00.000000000 +0000 @@ -1,668 +0,0 @@ -#!/usr/bin/perl - -# Copyright © 1998 Richard Braakman -# Copyright © 2008 Frank Lichtenheld -# Copyright © 2008, 2009 Russ Allbery -# Copyright © 2014 Niels Thykier -# Copyright © 2020 Felix Lechner -# -# This program is free software; you can redistribute it and/or modify -# it under the terms of the GNU General Public License as published by -# the Free Software Foundation; either version 2 of the License, or -# (at your option) any later version. -# -# This program is distributed in the hope that it will be useful, -# but WITHOUT ANY WARRANTY; without even the implied warranty of -# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the -# GNU General Public License for more details. -# -# You should have received a copy of the GNU General Public License -# along with this program. If not, you can find it on the World Wide -# Web at http://www.gnu.org/copyleft/gpl.html, or write to the Free -# Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, -# MA 02110-1301, USA. - -# The harness for Lintian's test suite. For detailed information on -# the test suite layout and naming conventions, see t/tests/README. -# For more information about running tests, see -# doc/tutorial/Lintian/Tutorial/TestSuite.pod -# - -use v5.20; -use warnings; -use utf8; -use autodie; - -# use Lintian modules that belong to this program -use FindBin; -use lib "$FindBin::RealBin/../lib"; - -use Capture::Tiny qw(capture_merged); -use Cwd qw(realpath); -use File::Basename; -use File::Path qw(make_path); -use File::Spec::Functions qw(abs2rel rel2abs splitpath splitdir); -use File::stat; -use Getopt::Long; -use List::MoreUtils qw(any uniq); -use List::Util qw(max); -use IO::Async::Function; -use IO::Async::Loop; -use Path::Tiny; -use TAP::Formatter::Console; -use TAP::Formatter::File; -use TAP::Harness; -use TAP::Parser::Aggregator; -use Term::ANSIColor; -use Time::Duration; -use Time::Moment; -use Time::Piece; -use Try::Tiny; - -use Lintian::IO::Async qw(safe_qx); - -use Test::Lintian::ConfigFile qw(read_config); -use Test::Lintian::Filter - qw(find_selected_scripts find_selected_lintian_testpaths); -use Test::Lintian::Helper - qw(rfc822date cache_dpkg_architecture_values get_latest_policy get_recommended_debhelper_version); -use Test::Lintian::Prepare qw(filleval); -use Test::Lintian::Run qw(logged_runner); -use Test::ScriptAge qw(perl_modification_epoch our_modification_epoch); - -use constant SPACE => q{ }; -use constant INDENT => q{ }; -use constant NEWLINE => qq{\n}; -use constant EMPTY => q{}; -use constant YES => q{yes}; -use constant NO => q{no}; - -# display output immediately -STDOUT->autoflush; - -my $processing_start = Time::Moment->from_string(gmtime->datetime . 'Z'); - -# whitelist the environment we permit to avoid things that mess up -# tests, like CFLAGS, DH_OPTIONS, DH_COMPAT, DEB_HOST_ARCH -my %PRESERVE_ENV = map { $_ => 1 } qw( - LINTIAN_TEST_INSTALLED - PATH - TMPDIR -); - -my @disallowed = grep { !exists $PRESERVE_ENV{$_} } keys %ENV; - -delete $ENV{$_} for @disallowed; - -if (($ENV{LINTIAN_TEST_INSTALLED} // 'no') eq 'yes') { - - $ENV{LINTIAN_UNDER_TEST} = realpath('/usr/bin/lintian') - // die 'Lintian is not installed'; - -} else { - $ENV{LINTIAN_UNDER_TEST} = realpath($FindBin::RealBin . '/../bin/lintian'); -} - -$ENV{LINTIAN_BASE} - = realpath(dirname(dirname($ENV{LINTIAN_UNDER_TEST}))) - // die 'Cannot resolve LINTIAN_BASE'; - -# options -my $coverage; -my $debug; -my $dump_logs = 1; -my $numjobs = -1; -my $keep_going; -my $onlyrun; -my $outpath; -my $unattended; -my $verbose = 0; - -Getopt::Long::Configure('bundling'); -unless ( - Getopt::Long::GetOptions( - 'c|coverage:s' => \$coverage, - 'd|debug+' => \$debug, - 'j|jobs:i' => \$numjobs, - 'k|keep-going' => \$keep_going, - 'L|dump-logs!' => \$dump_logs, - 'o|onlyrun:s' => \$onlyrun, - 'u|unattended' => \$unattended, - 'v|verbose' => \$verbose, - 'w|work-dir:s' => \$outpath, - 'h|help' => sub {usage(); exit;}, - ) -) { - usage(); - die; -} - -# check number of arguments -die('Please use -h for usage information.') - if @ARGV > 1; - -# get arguments -my ($testset) = @ARGV; - -# default test set -$testset ||= 't'; - -# check test set directory -die "Cannot find testset directory $testset" - unless -d $testset; - -# make sure testset is an absolute path -$testset = rel2abs($testset); - -# calculate a default test work directory if none given -$outpath ||= dirname($testset) . '/debian/test-out'; - -# create test work directory unless it exists -make_path($outpath) - unless -e $outpath; - -# make sure test work path is a directory -die "Test work directory $outpath is not a directory" - unless -d $outpath; - -# make sure outpath is absolute -$outpath = rel2abs($outpath); - -my $ACTIVE_JOBS = 0; - -my $output_is_tty = -t STDOUT; - -# get lintian modification date -my @lintianparts - = ('checks', 'commands', 'data','bin', 'profiles', 'vendors', 'lib/Lintian'); -my @lintianfiles - = map { File::Find::Rule->file->in("$ENV{'LINTIAN_BASE'}/$_") }@lintianparts; -push(@lintianfiles, Cwd::realpath($ENV{'LINTIAN_UNDER_TEST'})); -$ENV{'LINTIAN_EPOCH'} - = max(map { -e $_ ? stat($_)->mtime : time } @lintianfiles); -say 'Lintian modified on '. rfc822date($ENV{'LINTIAN_EPOCH'}); - -my $error; -my $string = capture_merged { - my @command = ($ENV{'LINTIAN_UNDER_TEST'}, '--version'); - system(@command) == 0 - or $error = "system @command failed: $?"; -}; -die $string . $error - if length $error; - -chomp $string; -my ($version) = $string =~ qr/^\S+\s+v(.+)$/; -die 'Cannot get Lintian version' unless length $version; -say "Version under test is $version."; - -say EMPTY; - -# set environment for coverage -if (defined $coverage) { - # Only collect coverage for stuff that D::NYTProf and - # Test::Pod::Coverage cannot do for us. This makes cover use less - # RAM in the other end. - my @criteria = qw(statement branch condition path subroutine); - my $args= '-MDevel::Cover=-silent,1,+ignore,^(.*/)?t/scripts/.+'; - $args .= ',+ignore,/usr/bin/.*,+ignore,(.*/)?Dpkg'; - $args .= ',-coverage,' . join(',-coverage,', @criteria); - $args .= ',' . $coverage if $coverage ne ''; - $ENV{'LINTIAN_COVERAGE'} = $args; - - $ENV{'HARNESS_PERL_SWITCHES'} //= EMPTY; - $ENV{'HARNESS_PERL_SWITCHES'} .= SPACE . $args; -} - -# Devel::Cover + one cover_db + multiple processes is a recipe -# for corruptions. Force $numjobs to 1 if we are running under -# coverage. -$numjobs = 1 if exists $ENV{'LINTIAN_COVERAGE'}; - -# tie verbosity to debug -$verbose = 1 + $debug if $debug; - -# can be 0 without value ("-j"), and -1 if option was not specified at all -$numjobs = default_parallel() if $numjobs <= 0; -say "Running up to $numjobs tests concurrently" - if $numjobs > 1 && $verbose >= 2; - -$ENV{'DUMP_LOGS'} = $dump_logs//NO ? YES : NO; - -# Disable translation support in dpkg as it is a considerable -# unnecessary overhead. -$ENV{'DPKG_NLS'} = 0; - -my $helperpath = "$testset/../private"; -if (-d $helperpath) { - my $helpers = rel2abs($helperpath)// die("Cannot resolve $helperpath: $!"); - $ENV{'PATH'} = "$helpers:$ENV{'PATH'}"; -} - -# get architecture -cache_dpkg_architecture_values(); -say "Host architecture is $ENV{'DEB_HOST_ARCH'}."; - -# get latest policy version and date -($ENV{'POLICY_VERSION'}, $ENV{'POLICY_EPOCH'}) = get_latest_policy(); -say "Latest policy version is $ENV{'POLICY_VERSION'} from " - . rfc822date($ENV{'POLICY_EPOCH'}); - -# get current debhelper compat level; do not name DH_COMPAT; causes conflict -$ENV{'DEFAULT_DEBHELPER_COMPAT'} = get_recommended_debhelper_version(); -say -"Using compat level $ENV{'DEFAULT_DEBHELPER_COMPAT'} as a default for packages built with debhelper."; - -# get harness date, including templates, skeletons and whitelists -my @harnessparts - = ('bin', 't/runners', 't/templates', 't/skeletons', 't/whitelists'); -my @harnessfiles - = map { File::Find::Rule->file->in("$ENV{'LINTIAN_BASE'}/$_") }@harnessparts; -my $harness_files_epoch - = max(map { -e $_ ? stat($_)->mtime : time } @harnessfiles); -$ENV{'HARNESS_EPOCH'} - = max(our_modification_epoch, perl_modification_epoch, $harness_files_epoch); -say 'Harness modified on '. rfc822date($ENV{'HARNESS_EPOCH'}); - -say EMPTY; - -# print environment -my @vars = sort keys %ENV; -say 'Environment:' if @vars; -for my $var (@vars) { say INDENT . "$var=$ENV{$var}" } - -say EMPTY; - -my $status = 0; - -my $formatter = TAP::Formatter::File->new({ - errors => 1, - jobs => $numjobs, -}); -$formatter = TAP::Formatter::Console->new({ - errors => 1, - jobs => $numjobs, - color => 1, - }) if -t STDOUT; - -my $harness = TAP::Harness->new({ - formatter => $formatter, - jobs => $numjobs, - lib => ["$ENV{'LINTIAN_BASE'}/lib"], -}); - -my $aggregator = TAP::Parser::Aggregator->new; -$aggregator->start; - -my @runscripts; -my $scriptpath = "$testset/scripts"; - -# add selected scripts -push(@runscripts, find_selected_scripts($scriptpath, $onlyrun)); - -# always add internal harness tests -my @requiredscripts; -@requiredscripts - = sort File::Find::Rule->file()->name('*.t')->in("$scriptpath/harness") - unless length $onlyrun; -push(@runscripts, @requiredscripts); - -# remove any duplicates -@runscripts = uniq @runscripts; - -# make all paths relative -@runscripts = map { abs2rel($_) } @runscripts; - -say 'Running selected and required Perl test scripts.'; -say EMPTY; - -# run scripts through harness -$harness->aggregate_tests($aggregator, sort @runscripts); - -unless (!@runscripts || $aggregator->all_passed || $keep_going) { - $aggregator->stop; - $formatter->summary($aggregator); - exit 1; -} - -say EMPTY; - -# find test paths -my @testpaths = find_selected_lintian_testpaths($testset, $onlyrun); - -# for built test packages -my $buildroot = "$outpath/packages"; - -# for built test packages -my $evalroot = "$outpath/eval"; - -# prepare test -my $filleval = IO::Async::Function->new( - code => sub { - my ($specpath) = @_; - - # label process - $0 = "Lintian prepare test: $specpath"; - - # calculate destination - my $relative = path($specpath)->relative("$testset/recipes"); - my $buildpath = $relative->absolute($buildroot)->stringify; - my $evalpath = $relative->absolute($evalroot)->relative->stringify; - - my $error; - - # capture output - my $log = capture_merged { - - try { - - # remove destination - path($evalpath)->remove_tree - if -e $evalpath; - - path($evalpath)->mkpath; - - # prepare - filleval("$specpath/eval", $evalpath, $testset); - - my $traversal = Cwd::realpath("$buildpath/subject"); - - if (length $traversal) { - die "Cannot link to subject in $buildpath" - if system("cd $evalpath; ln -s $traversal subject"); - } - - }catch { - # catch any error - $error = $_; - }; - }; - - # save log; - my $logfile = "$evalpath/log"; - path($logfile)->spew_utf8($log) if $log; - - # print something if there was an error - die(($log // EMPTY) . "Preparation failed for $specpath: $error") - if $error; - - return $specpath; - }, - max_workers => $numjobs, - max_worker_calls => 1, -); - -my $loop = IO::Async::Loop->new; -$loop->add($filleval); - -$SIG{INT} = sub { $filleval->stop; die "Caught a sigint $!" }; -my @filltasks = map {$filleval->call(args => [$_])} sort @testpaths; - -my $allfilled = Future->wait_all(@filltasks); - -$loop->await($allfilled); - -# remap paths from testset to outpath to get work directories -my @workpaths - = map { rel2abs(abs2rel($_, "$testset/recipes"), "$outpath/eval") } - @testpaths; - -# if ($platforms ne 'any') { -# my @wildcards = split(SPACE, $platforms); -# my @matches= map { -# qx{dpkg-architecture -a $ENV{'DEB_HOST_ARCH'} -i $_; echo -n \$?} -# } @wildcards; -# unless (any { $_ == 0 } @matches) { -# say 'Architecture mismatch'; -# return; -# } -# } - -# make all paths relative to current directory -@workpaths = map { path($_)->relative } @workpaths; - -# add the scripts in generated tests to be run -my @workscripts; -for my $path (@workpaths) { - - my @runners = File::Find::Rule->file->name('*.t')->in($path); - - die "No runner in $path" - unless scalar @runners; - die "More than one runner in $path" - if scalar @runners > 1; - - push(@workscripts, @runners); -} - -# run scripts through harness -$harness->aggregate_tests($aggregator, sort @workscripts); - -$aggregator->stop; -$formatter->summary($aggregator); - -say EMPTY; - -my $processing_end = Time::Moment->from_string(gmtime->datetime . 'Z'); -my $duration = duration($processing_start->delta_seconds($processing_end)); -say "The test suite ran for $duration."; - -$status = 1 - unless $aggregator->all_passed; - -if (-t STDOUT && !$unattended) { - my @failed = $aggregator->failed; - say 'Offering to re-calibrate the tags expected in tests that failed.' - if @failed; - - my $accept_all; - - for my $scriptpath (@failed) { - my $workpath = dirname($scriptpath); - - my $descpath = "$workpath/desc"; - my $testcase = read_config($descpath); - - my $relative = abs2rel($workpath, $evalroot); - my $testpath = abs2rel(rel2abs($relative, "$testset/recipes")); - - say EMPTY; - say 'Failed test: ' . colored($testpath, 'bold white on_blue'); - - my $match_strategy = $testcase->unfolded_value('Match-Strategy'); - - if ($match_strategy eq 'tags') { - - my $diffpath = "$workpath/tagdiff"; - next - unless -r $diffpath; - - my $diff = path($diffpath)->slurp; - print $diff; - - } elsif ($match_strategy eq 'literal') { - - my $actualpath = "$workpath/literal.actual.parsed"; - next - unless -r $actualpath; - my @command - = ('diff', '-uN', "$testpath/eval/literal", $actualpath); - say join(SPACE, @command); - system(@command); - - } else { - say -"Do not know how to fix tests using matching strategy $match_strategy."; - next; - } - - unless ($accept_all) { - - print -'>>> Fix test (y), accept all (a), do not fix (n), quit (q/default)? '; - - my $decision = ; - chomp $decision; - - last - if $decision eq 'q' || $decision eq EMPTY; - - next - unless $decision eq 'y' || $decision eq 'a'; - - $accept_all = 1 - if $decision eq 'a'; - } - - if ($match_strategy eq 'tags') { - - # create tags if needed; helps when writing new tests - my $tagspath = "$testpath/eval/tags"; - path($tagspath)->touch - unless -e $tagspath; - - my $diffpath = "$workpath/tagdiff"; - next - unless -r $diffpath; - - my @adjustargs = ($diffpath, $tagspath); - unshift(@adjustargs, '-i') - unless $accept_all; - - die "Cannot run tagadjust for $testpath" - if system('tagadjust', @adjustargs); - - # also copy the new tags to workpath; no need to rebuild - die "Cannot copy updated tags to $workpath" - if system('cp', $tagspath, "$workpath/tags"); - - } elsif ($match_strategy eq 'literal') { - - my $actualpath = "$workpath/literal.actual.parsed"; - next - unless -r $actualpath; - - die "Cannot copy to accept literal output for $testpath" - if system('cp', $actualpath, "$testpath/eval/literal"); - - } - } - - say NEWLINE . 'Accepted all remaining tag changes.' - if $accept_all; - -} else { - my @crashed = $aggregator->parse_errors; - - say 'Showing full logs for tests with parse errors.' - if @crashed; - - for my $absolutepath (@crashed) { - my $scriptpath = abs2rel($absolutepath); - my $workpath = dirname($scriptpath); - - say EMPTY; - say "Log for test $scriptpath:"; - - my $logpath = "$workpath/log"; - my $log = path($logpath)->slurp; - print $log; - } -} - -# give a hint if not enough tests were run -unless (scalar @runscripts - scalar @requiredscripts + scalar @workscripts - || $onlyrun eq 'minimal:') { - quick_hint($onlyrun); - exit 1; -} - -say EMPTY; - -exit $status; - -# program is done - -=item default_parallel - -=cut - -# Return the default number of parallelization to be used -sub default_parallel { - # check cpuinfo for the number of cores... - my $cpus = safe_qx('nproc'); - if ($cpus =~ m/^\d+$/) { - # Running up to twice the number of cores usually gets the most out - # of the CPUs and disks but it might be too aggressive to be the - # default for -j. Only use +1 then. - return $cpus + 1; - } - - # No decent number of jobs? Just use 2 as a default - return 2; -} - -sub usage { - print <<"END"; -Usage: $0 [options] [-j []] - - --onlyrun Select only some tests for a quick check - --coverage Run Lintian under Devel::Cover (Warning: painfully slow) - -d Display additional debugging information - --dump-logs Print build log to STDOUT, if a build fails. - -j [] Run up to jobs in parallel. - If -j is passed without specifying , the number - of jobs started is +1. - -k Do not stop after one failed test - -v Be more verbose - --help, -h Print this help and exit - - The option --onlyrun causes runtests to only run tests that match - the particular selection. This parameter can be a list of selectors: - what:[,] - - * test: - - Run the named test. Please note that testnames may not be - unique, so it may run more than one test. - * script:( || ) - - Run the named code quality script or all in the named directory. - E.g. "01-critic" will run all tests in "t/scripts/01-critic/". - * check: - - Run all tests related to the given check. - * suite: - - Run all tests in the named suite. - * tag: - - Run any test that lists in "Test-For" or - "Test-Against". - -Test artifacts are cached in --work-dir [default: debian/test-out] and -will generally be reused to save time. To recreate the test packages, -run 'private/build-test-packages'. -END - return; -} - -sub quick_hint { - my ($selection) = @_; - print <<"END"; - -No tests were selected by your filter: - - $selection - -To select your tests, please use an appropriate argument with a -selector like: - - 'suite:', 'test:', 'check:', 'tag:', or 'script:' - -You can also use 'minimal:', which runs only the tests that cannot -be turned off, such as the internal tests for the harness. -END - return; -} - -# Local Variables: -# indent-tabs-mode: nil -# cperl-indent-level: 4 -# End: -# vim: syntax=perl sw=4 sts=4 sr et diff -Nru lintian-2.93.0/private/split-desc lintian-2.89.0ubuntu1/private/split-desc --- lintian-2.93.0/private/split-desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/private/split-desc 1970-01-01 00:00:00.000000000 +0000 @@ -1,108 +0,0 @@ -#!/usr/bin/perl - -use v5.20; -use warnings; -use utf8; - -use List::MoreUtils qw(any); -use Path::Tiny; - -use constant EMPTY => q{}; - -die 'Please specify exactly one argument' - unless @ARGV == 1; - -my $path = $ARGV[0]; - -#print "Splitting $path\n"; - -my $contents = path($path)->slurp; - -#print $contents; - -my @testlabels = qw( - Check - Default-Lintian-Options - Lintian-Command-Line - Match-Strategy - Options - Output-Format - Profile - References - Test-Against - Test-Architectures - Test-Conflicts - Test-Depends - Todo -); - -my $build = EMPTY; -my $eval = EMPTY; -my $comments = EMPTY; - -while ($contents =~ s/\n(\#[^\n]*\n)/\n/) { - $comments .= $1; -} - -while ($contents =~ s/^([^:]+\:[^\n]*\n(?: [^\n]+\n)*)//) { - - my $field = $1; - - my ($label) = ($field =~ /^([^:]+)\:/); - # print "Found $label\n"; - - if ($label eq 'Testname') { - $eval .= $field; - $build .= $field; - next; - } - - if (any {/^$label$/} @testlabels) { - $eval .= $field; - - } else { - $build .= $field; - } -} - -die 'Unknown data at the end' - if length $contents; - -path($path)->remove; - -my $parent = path($path)->parent->stringify; - -my $temppath = $parent . ' (new)'; -path($parent)->move($temppath); -path($parent)->mkpath; - -my $buildpath = path($parent)->child('build-spec')->stringify; -my $evalpath = path($parent)->child('eval')->stringify; - -path($parent)->mkpath; -path($temppath)->move($buildpath); -path($evalpath)->mkpath; - -my $fillvalues = path($buildpath)->child('fill-values')->stringify; -my $desc = path($evalpath)->child('desc'); - -path($fillvalues)->spew($build); -path($desc)->spew($eval); - -path($fillvalues)->append($comments); -path($desc)->append($comments); - -my @move - = qw(tags literal skip post-test test-calibration tag-list suppress lintian-include-dir); - -for my $transfer (@move) { - - my $sourcepath = path($buildpath)->child($transfer)->stringify; - my $destpath = path($evalpath)->child($transfer)->stringify; - - path($sourcepath)->move($destpath) - if -e $sourcepath; -} - -#print "Build:\n$build\n"; -#print "Eval:\n$eval\n"; diff -Nru lintian-2.93.0/private/tagadjust lintian-2.89.0ubuntu1/private/tagadjust --- lintian-2.93.0/private/tagadjust 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/private/tagadjust 1970-01-01 00:00:00.000000000 +0000 @@ -1,152 +0,0 @@ -#!/usr/bin/perl - -# Copyright © 2019 Felix Lechner -# -# This program is free software; you can redistribute it and/or modify -# it under the terms of the GNU General Public License as published by -# the Free Software Foundation; either version 2 of the License, or -# (at your option) any later version. -# -# This program is distributed in the hope that it will be useful, -# but WITHOUT ANY WARRANTY; without even the implied warranty of -# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the -# GNU General Public License for more details. -# -# You should have received a copy of the GNU General Public License -# along with this program. If not, you can find it on the World Wide -# Web at http://www.gnu.org/copyleft/gpl.html, or write to the Free -# Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, -# MA 02110-1301, USA. - -# The harness for Lintian's test suite. For detailed information on -# the test suite layout and naming conventions, see t/tests/README. -# For more information about running tests, see -# doc/tutorial/Lintian/Tutorial/TestSuite.pod -# - -use v5.20; -use warnings; -use utf8; -use autodie; - -# use Lintian modules that belong to this program -use FindBin; -use lib "$FindBin::RealBin/../lib"; - -use Cwd; -use Capture::Tiny qw(capture_merged); -use Getopt::Long; -use List::Util qw(all); -use Path::Tiny; -use Term::ANSIColor; - -use Test::Lintian::Output::Universal qw(parse_line order); - -use constant EMPTY => q{}; -use constant SPACE => q{ }; -use constant COLON => q{:}; -use constant LPARENS => q{(}; -use constant RPARENS => q{)}; -use constant NEWLINE => qq{\n}; - -# options -my $interactive; - -Getopt::Long::Configure; -unless ( - Getopt::Long::GetOptions( - 'i|interactive' => \$interactive, - 'help|h' => sub {usage(); exit;}, - ) -) { - usage(); - die; -} - -# check arguments and options -die "Please use -h for usage information.\n" - if scalar @ARGV != 2; - -# get arguments -my ($diffpath, $tagspath) = @ARGV; - -my @difflines = path($diffpath)->lines_utf8; -chomp @difflines; - -my @tagslines = path($tagspath)->lines_utf8; -chomp @tagslines; - -my $changed; - -foreach my $line (@difflines) { - my ($sign, $stripped) = $line =~ qr/^([+-])(.*)$/; - - die "$diffpath is not a tagdiff file" - unless length $sign && defined $stripped; - - if ($interactive) { - - my $command; - my $color; - - if ($sign eq '+') { - $command = 'Add'; - $color = 'bold bright_white on_green'; - } else { - $command = 'Remove'; - $color = 'bold bright_white on_red'; - } - - my $colored = $stripped; - $colored = colored($stripped, $color) - if -t STDOUT; - print "$colored - $command (y/n/q)? "; - - my $decision = ; - chomp $decision; - exit if $decision eq 'q'; - next unless $decision eq 'y'; - } - - if ($sign eq '+') { - # say "Adding: $stripped"; - push(@tagslines, $stripped); - } else { - # say "Removing: $stripped"; - # remove the first match only - my $found = 0; - @tagslines = grep {$_ ne $stripped || $found++} @tagslines; - } - - $changed = 1; -} - -exit unless $changed; - -# also sort output into preferred order -my $joined = EMPTY; -$joined .= $_ . NEWLINE - for reverse sort { order($a) cmp order($b) } @tagslines; -path($tagspath)->spew_utf8($joined); - -exit; - -sub usage { - print <<"END"; -Usage: $0 -i - - --interactive, -i Apply interactively - - Applies to so that the new file represents the - changes. Please use tagdiff to create the file with the changes. - - The tags are then sorted in the order preferred for universal tags. -END - return; -} - -# Local Variables: -# indent-tabs-mode: nil -# cperl-indent-level: 4 -# End: -# vim: syntax=perl sw=4 sts=4 sr et diff -Nru lintian-2.93.0/private/tagdiff lintian-2.89.0ubuntu1/private/tagdiff --- lintian-2.93.0/private/tagdiff 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/private/tagdiff 1970-01-01 00:00:00.000000000 +0000 @@ -1,122 +0,0 @@ -#!/usr/bin/perl - -# Copyright © 2019 Felix Lechner -# -# This program is free software; you can redistribute it and/or modify -# it under the terms of the GNU General Public License as published by -# the Free Software Foundation; either version 2 of the License, or -# (at your option) any later version. -# -# This program is distributed in the hope that it will be useful, -# but WITHOUT ANY WARRANTY; without even the implied warranty of -# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the -# GNU General Public License for more details. -# -# You should have received a copy of the GNU General Public License -# along with this program. If not, you can find it on the World Wide -# Web at http://www.gnu.org/copyleft/gpl.html, or write to the Free -# Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, -# MA 02110-1301, USA. - -# The harness for Lintian's test suite. For detailed information on -# the test suite layout and naming conventions, see t/tests/README. -# For more information about running tests, see -# doc/tutorial/Lintian/Tutorial/TestSuite.pod -# - -use v5.20; -use warnings; -use utf8; -use autodie; - -# use Lintian modules that belong to this program -use FindBin; -use lib "$FindBin::RealBin/../lib"; - -use Getopt::Long; -use List::Util qw(all); -use Path::Tiny; -use Term::ANSIColor qw(:constants); -use Text::Diff; - -use Test::Lintian::Output::Universal qw(order); - -use constant EMPTY => q{}; -use constant SPACE => q{ }; -use constant NEWLINE => qq{\n}; - -no warnings 'redefine'; - -sub Text::Diff::Unified::file_header { return EMPTY; } -sub Text::Diff::Unified::hunk_header { return EMPTY; } - -# options -Getopt::Long::Configure; -unless ( - Getopt::Long::GetOptions( - 'help|h' => sub {usage(); exit;}, - ) -) { - usage(); - die; -} - -# check arguments and options -die "Please use -h for usage information.\n" - if scalar @ARGV != 2; - -# get arguments -my ($expectedpath, $actualpath) = @ARGV; - -my @expected - = reverse sort { order($a) cmp order($b) } (path($expectedpath)->lines_utf8); -my @actual - = reverse sort { order($a) cmp order($b) }(path($actualpath)->lines_utf8); - -my $diff = diff(\@expected, \@actual, { CONTEXT => 0 }); - -my @lines = split(NEWLINE, $diff); -chomp @lines; - -# sort before applying color -@lines = reverse sort @lines; - -# apply color when on a terminal -if (-t STDOUT) { - - my $green = GREEN; - my $red = RED; - my $reset = RESET; - - s/^(\+.*)$/$green$1$reset/ for @lines; - s/^(\-.*)$/$red$1$reset/ for @lines; -} - -print $_ . NEWLINE for @lines; - -exit; - -sub usage { - print <<"END"; -Usage: $0 - - Print differences between the tag information in the two files. The files - must in a CSV format delimited by '|'. The easiest way to obtain such a - file is to use tagextract. - - The output is sorted lexigraphically in reverse order. If the arguments - are reversed, the new output can also be generated from the old one by - reversing the signs and sorting again in reverse order (under LC_ALL=C). - It only works with uncolored output. - - Returns with a zero exit code under normal conditions, even when the tags - do not match. -END - return; -} - -# Local Variables: -# indent-tabs-mode: nil -# cperl-indent-level: 4 -# End: -# vim: syntax=perl sw=4 sts=4 sr et diff -Nru lintian-2.93.0/private/tagextract lintian-2.89.0ubuntu1/private/tagextract --- lintian-2.93.0/private/tagextract 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/private/tagextract 1970-01-01 00:00:00.000000000 +0000 @@ -1,110 +0,0 @@ -#!/usr/bin/perl - -# Copyright © 2019 Felix Lechner -# -# This program is free software; you can redistribute it and/or modify -# it under the terms of the GNU General Public License as published by -# the Free Software Foundation; either version 2 of the License, or -# (at your option) any later version. -# -# This program is distributed in the hope that it will be useful, -# but WITHOUT ANY WARRANTY; without even the implied warranty of -# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the -# GNU General Public License for more details. -# -# You should have received a copy of the GNU General Public License -# along with this program. If not, you can find it on the World Wide -# Web at http://www.gnu.org/copyleft/gpl.html, or write to the Free -# Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, -# MA 02110-1301, USA. - -# The harness for Lintian's test suite. For detailed information on -# the test suite layout and naming conventions, see t/tests/README. -# For more information about running tests, see -# doc/tutorial/Lintian/Tutorial/TestSuite.pod -# - -use v5.20; -use warnings; -use utf8; -use autodie; - -# use Lintian modules that belong to this program -use FindBin; -use lib "$FindBin::RealBin/../lib"; - -use Getopt::Long; -use List::Util qw(all); -use Path::Tiny; - -use Test::Lintian::Output::EWI; - -# options -my $format; - -Getopt::Long::Configure; -unless ( - Getopt::Long::GetOptions( - 'f|format=s' => \$format, - 'help|h' => sub {usage(); exit;}, - ) -) { - usage(); - die; -} - -# check arguments and options -die "Please use -h for usage information.\n" - if scalar @ARGV < 1 || scalar @ARGV > 2; - -# get arguments -my ($inpath, $outpath) = @ARGV; - -die "File $inpath does not exist.\n" - unless -f $inpath; - -my $text = path($inpath)->slurp_utf8; -my $converted = to_universal($format, $text); - -if (defined $outpath) { - path($outpath)->spew_utf8($converted); -}else { - print $converted; -} - -exit; - -sub to_universal { - my ($format, $text) = @_; - - if ($format eq 'EWI') { - return Test::Lintian::Output::EWI::to_universal($text); - } - - die "Unknown format: $format\n"; -} - -sub usage { - print <<"END"; -Usage: $0 -f - - --format, -f Format of Lintian output file - - Extracts tag information from a variety of Lintian output formats. The - output format is a simplified EWI format without letter code. Other - notable differences are that the binary package type is always displayed. - - The tags are sorted in a reverse order, but with the package type pulled - to the front. That way package types are grouped. Source packages are at - the top. - - Prints to stdout when no is given. -END - return; -} - -# Local Variables: -# indent-tabs-mode: nil -# cperl-indent-level: 4 -# End: -# vim: syntax=perl sw=4 sts=4 sr et diff -Nru lintian-2.93.0/private/tagsort lintian-2.89.0ubuntu1/private/tagsort --- lintian-2.93.0/private/tagsort 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/private/tagsort 1970-01-01 00:00:00.000000000 +0000 @@ -1,92 +0,0 @@ -#!/usr/bin/perl - -# Copyright © 2019 Felix Lechner -# -# This program is free software; you can redistribute it and/or modify -# it under the terms of the GNU General Public License as published by -# the Free Software Foundation; either version 2 of the License, or -# (at your option) any later version. -# -# This program is distributed in the hope that it will be useful, -# but WITHOUT ANY WARRANTY; without even the implied warranty of -# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the -# GNU General Public License for more details. -# -# You should have received a copy of the GNU General Public License -# along with this program. If not, you can find it on the World Wide -# Web at http://www.gnu.org/copyleft/gpl.html, or write to the Free -# Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, -# MA 02110-1301, USA. - -# The harness for Lintian's test suite. For detailed information on -# the test suite layout and naming conventions, see t/tests/README. -# For more information about running tests, see -# doc/tutorial/Lintian/Tutorial/TestSuite.pod -# - -use v5.20; -use warnings; -use utf8; -use autodie; - -# use Lintian modules that belong to this program -use FindBin; -use lib "$FindBin::RealBin/../lib"; - -use Cwd; -use Getopt::Long; -use List::Util qw(all); -use Path::Tiny; -use Term::ANSIColor; - -use Test::Lintian::Output::Universal qw(parse_line order); - -use constant EMPTY => q{}; -use constant SPACE => q{ }; -use constant COLON => q{:}; -use constant LPARENS => q{(}; -use constant RPARENS => q{)}; -use constant NEWLINE => qq{\n}; - -Getopt::Long::Configure; -unless ( - Getopt::Long::GetOptions( - 'help|h' => sub {usage(); exit;}, - ) -) { - usage(); - die; -} - -# check arguments and options -die "Please use -h for usage information.\n" - if scalar @ARGV != 1; - -# get arguments -my ($tagspath) = @ARGV; - -my @tagslines = path($tagspath)->lines_utf8; -chomp @tagslines; - -my $joined = EMPTY; -$joined .= $_ . NEWLINE - for reverse sort { order($a) cmp order($b) } @tagslines; - -path($tagspath)->spew_utf8($joined); - -exit; - -sub usage { - print <<"END"; -Usage: $0 - - Sorts tagfile in the order preferred for universal tags. -END - return; -} - -# Local Variables: -# indent-tabs-mode: nil -# cperl-indent-level: 4 -# End: -# vim: syntax=perl sw=4 sts=4 sr et diff -Nru lintian-2.93.0/private/tag-stats lintian-2.89.0ubuntu1/private/tag-stats --- lintian-2.93.0/private/tag-stats 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/private/tag-stats 2020-08-10 09:59:45.000000000 +0000 @@ -13,18 +13,22 @@ use utf8; use autodie qw(opendir closedir); -# use Lintian modules that belong to this program -use FindBin; -use lib "$FindBin::RealBin/../lib"; +BEGIN { + my $LINTIAN_BASE = $ENV{'LINTIAN_BASE'}; + if (not $LINTIAN_BASE) { + require Cwd; + $ENV{'LINTIAN_BASE'} = $LINTIAN_BASE = Cwd::cwd(); + } else { + chdir $LINTIAN_BASE or die "Cannot chdir to $LINTIAN_BASE: $!\n"; + } +} -use Cwd qw(realpath); +my $LINTIAN_BASE = $ENV{'LINTIAN_BASE'}; +use lib "$ENV{'LINTIAN_BASE'}/lib"; use Lintian::Deb822::Parser qw(read_dpkg_control); use Lintian::Tag::Info; -$ENV{LINTIAN_BASE} = realpath("$FindBin::RealBin/..") - // die 'Cannot resolve LINTIAN_BASE'; - my @severities = reverse qw(pedantic info warning error); my @types = qw(E W I P); @@ -35,11 +39,11 @@ my $verbose = $ARGV[0] ? ($ARGV[0] =~ s/v/v/g) : 0; -opendir(my $checkdir, "$ENV{LINTIAN_BASE}/checks"); +opendir(my $checkdir, "$LINTIAN_BASE/checks"); for my $check (readdir($checkdir)) { next unless $check =~ /\.desc$/; - my @tags = read_dpkg_control("$ENV{LINTIAN_BASE}/checks/$check"); + my @tags = read_dpkg_control("$LINTIAN_BASE/checks/$check"); my $desc = $tags[0]; shift(@tags); diff -Nru lintian-2.93.0/private/update-coverage lintian-2.89.0ubuntu1/private/update-coverage --- lintian-2.93.0/private/update-coverage 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/private/update-coverage 2020-08-10 09:59:45.000000000 +0000 @@ -6,30 +6,38 @@ # by the old test suite against the list of all documented tags and generate # output suitable for tags-never-seen that lists the untested tags. Updates # t/COVERAGE. +# +# Should be run from the top level of the Lintian source tree or with +# LINTIAN_BASE set appropriately. use v5.20; use warnings; use utf8; use autodie; -# use Lintian modules that belong to this program -use FindBin; -use lib "$FindBin::RealBin/../lib"; - -use Cwd qw(realpath); use POSIX qw(strftime); -use Lintian::Deb822::Parser qw(read_dpkg_control); +BEGIN { + my $LINTIAN_BASE = $ENV{'LINTIAN_BASE'}; + if (not $LINTIAN_BASE) { + require Cwd; + $ENV{'LINTIAN_BASE'} = $LINTIAN_BASE = Cwd::cwd(); + } else { + chdir($LINTIAN_BASE); + } +} -$ENV{LINTIAN_BASE} = realpath("$FindBin::RealBin/..") - // die 'Cannot resolve LINTIAN_BASE'; +my $LINTIAN_BASE = $ENV{'LINTIAN_BASE'}; + +use lib "$ENV{'LINTIAN_BASE'}/lib"; +use Lintian::Deb822::Parser qw(read_dpkg_control); # Check that we're being run from the right place (although the above probably # died if we weren't). -unless (-f 'private/runtests') { +unless (-f 'bin/runtests') { warn "update-coverage source be run from the top level of the Lintian\n"; warn "source tree.\n\n"; - die "Cannot find private/runtests -- run from the right directory?\n"; + die "Cannot find bin/runtests -- run from the right directory?\n"; } # Gather a list of all tags. diff -Nru lintian-2.93.0/t/defaults/desc lintian-2.89.0ubuntu1/t/defaults/desc --- lintian-2.93.0/t/defaults/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/defaults/desc 2020-08-10 09:59:45.000000000 +0000 @@ -5,5 +5,6 @@ Output-Format: universal Skeleton: testing Match-Strategy: tags -Default-Lintian-Options: --pedantic --display-info --display-experimental --display-level +classification --show-overrides --check-part [% $check %] +Default-Lintian-Options: --pedantic --display-info --display-experimental --display-level +classification --check-part [% $check %] +Todo: no Test-Architectures: any diff -Nru lintian-2.93.0/t/recipes/checks/cruft/cruft-ancient-libtool/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/cruft/cruft-ancient-libtool/eval/desc --- lintian-2.93.0/t/recipes/checks/cruft/cruft-ancient-libtool/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/cruft/cruft-ancient-libtool/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -1,3 +1,3 @@ Testname: cruft-ancient-libtool -See-Also: Debian Bug#293296 +References: Debian Bug#293296 Check: cruft diff -Nru lintian-2.93.0/t/recipes/checks/cruft/cruft-ancient-libtool-2/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/cruft/cruft-ancient-libtool-2/eval/desc --- lintian-2.93.0/t/recipes/checks/cruft/cruft-ancient-libtool-2/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/cruft/cruft-ancient-libtool-2/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -1,3 +1,3 @@ Testname: cruft-ancient-libtool-2 -See-Also: Debian Bug#293296 +References: Debian Bug#293296 Check: cruft diff -Nru lintian-2.93.0/t/recipes/checks/cruft/cruft-current-libtool/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/cruft/cruft-current-libtool/eval/desc --- lintian-2.93.0/t/recipes/checks/cruft/cruft-current-libtool/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/cruft/cruft-current-libtool/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -1,4 +1,4 @@ Testname: cruft-current-libtool Test-Against: ancient-libtool -See-Also: Debian Bug#293296 +References: Debian Bug#293296 Check: cruft diff -Nru lintian-2.93.0/t/recipes/checks/cruft/cruft-empty-diff/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/cruft/cruft-empty-diff/eval/desc --- lintian-2.93.0/t/recipes/checks/cruft/cruft-empty-diff/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/cruft/cruft-empty-diff/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -1,3 +1,3 @@ Testname: cruft-empty-diff -See-Also: Debian Bug#498668 +References: Debian Bug#498668 Check: cruft diff -Nru lintian-2.93.0/t/recipes/checks/cruft/cruft-general-diff/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/cruft/cruft-general-diff/eval/desc --- lintian-2.93.0/t/recipes/checks/cruft/cruft-general-diff/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/cruft/cruft-general-diff/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -1,3 +1,3 @@ Testname: cruft-general-diff -See-Also: Debian Bug#598251 +References: Debian Bug#598251 Check: cruft diff -Nru lintian-2.93.0/t/recipes/checks/cruft/cruft-general-quilt/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/cruft/cruft-general-quilt/eval/desc --- lintian-2.93.0/t/recipes/checks/cruft/cruft-general-quilt/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/cruft/cruft-general-quilt/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -1,3 +1,3 @@ Testname: cruft-general-quilt -See-Also: Debian Bug#598251 +References: Debian Bug#598251 Check: cruft diff -Nru lintian-2.93.0/t/recipes/checks/cruft/cruft-general-upstream/build-spec/pre-upstream lintian-2.89.0ubuntu1/t/recipes/checks/cruft/cruft-general-upstream/build-spec/pre-upstream --- lintian-2.93.0/t/recipes/checks/cruft/cruft-general-upstream/build-spec/pre-upstream 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/cruft/cruft-general-upstream/build-spec/pre-upstream 2020-08-10 09:59:45.000000000 +0000 @@ -47,8 +47,8 @@ echo '' > "${dir}/fake.py" echo 'import fake' > "${dir}/main.py" unset PYTHONDONTWRITEBYTECODE -PYTHONPATH="${dir}" python3 "${dir}/main.py" > /dev/null -PYTHONPATH="${dir}" python3 -O "${dir}/main.py" > /dev/null +PYTHONPATH="${dir}" python2 "${dir}/main.py" > /dev/null +PYTHONPATH="${dir}" python2 -O "${dir}/main.py" > /dev/null rm -f "${dir}"/main.py* zip -q "${dir}/fake.jar" "${dir}/fake.min.js" diff -Nru lintian-2.93.0/t/recipes/checks/cruft/cruft-general-upstream/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/cruft/cruft-general-upstream/eval/desc --- lintian-2.93.0/t/recipes/checks/cruft/cruft-general-upstream/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/cruft/cruft-general-upstream/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -1,5 +1,2 @@ Testname: cruft-general-upstream Check: cruft -Todo: In unstable, file(1) cannot detect files byte-compiled by Python3. (Bug#950516) -# also update the version number below when Bug#950516 was fixed -Test-Depends: file (>= 1:5.38) diff -Nru lintian-2.93.0/t/recipes/checks/cruft/cruft-general-upstream/eval/tags lintian-2.89.0ubuntu1/t/recipes/checks/cruft/cruft-general-upstream/eval/tags --- lintian-2.93.0/t/recipes/checks/cruft/cruft-general-upstream/eval/tags 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/cruft/cruft-general-upstream/eval/tags 2020-08-10 09:59:45.000000000 +0000 @@ -7,8 +7,8 @@ cruft-general-upstream (source): source-contains-svk-commit-file svk-commit444.tmp cruft-general-upstream (source): source-contains-prebuilt-windows-binary fake-win32-bin.exe cruft-general-upstream (source): source-contains-prebuilt-silverlight-object fakesilverlight.XAC -cruft-general-upstream (source): source-contains-prebuilt-python-object __pycache__/fake.cpython-38.pyc -cruft-general-upstream (source): source-contains-prebuilt-python-object __pycache__/fake.cpython-38.opt-1.pyc +cruft-general-upstream (source): source-contains-prebuilt-python-object fake.pyo +cruft-general-upstream (source): source-contains-prebuilt-python-object fake.pyc cruft-general-upstream (source): source-contains-prebuilt-ms-help-file fake-help-file.chm cruft-general-upstream (source): source-contains-prebuilt-javascript-object fake.min.js cruft-general-upstream (source): source-contains-prebuilt-flash-project fakeflasourced.fla diff -Nru lintian-2.93.0/t/recipes/checks/cruft/cruft-updated-libtool/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/cruft/cruft-updated-libtool/eval/desc --- lintian-2.93.0/t/recipes/checks/cruft/cruft-updated-libtool/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/cruft/cruft-updated-libtool/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -1,4 +1,4 @@ Testname: cruft-updated-libtool Test-Against: ancient-libtool -See-Also: Debian Bug#534134 +References: Debian Bug#534134 Check: cruft diff -Nru lintian-2.93.0/t/recipes/checks/cruft/min-js-with-sources/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/cruft/min-js-with-sources/eval/desc --- lintian-2.93.0/t/recipes/checks/cruft/min-js-with-sources/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/cruft/min-js-with-sources/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -1,3 +1,3 @@ Testname: min-js-with-sources Check: cruft -See-Also: Bug#962583 +References: Bug#962583 diff -Nru lintian-2.93.0/t/recipes/checks/debhelper/debhelper-brace-expansion/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/debhelper/debhelper-brace-expansion/eval/desc --- lintian-2.93.0/t/recipes/checks/debhelper/debhelper-brace-expansion/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/debhelper/debhelper-brace-expansion/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -1,3 +1,3 @@ Testname: debhelper-brace-expansion -See-Also: Debian Bug#480939 +References: Debian Bug#480939 Check: debhelper diff -Nru lintian-2.93.0/t/recipes/checks/debhelper/debhelper-no-depends/build-spec/debian/rules lintian-2.89.0ubuntu1/t/recipes/checks/debhelper/debhelper-no-depends/build-spec/debian/rules --- lintian-2.93.0/t/recipes/checks/debhelper/debhelper-no-depends/build-spec/debian/rules 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/debhelper/debhelper-no-depends/build-spec/debian/rules 2020-08-10 09:59:45.000000000 +0000 @@ -12,8 +12,8 @@ -dh_dpatch_patch # We don't warn about commands inside make conditionals, so none of these # get any warnings. -ifeq "$(USE_DH_PYTHON3)" "y" - dh_python3 +ifeq "$(USE_DH_PYTHON2)" "y" + dh_python2 else ifeq "$(USE_PYSUPPORT)" "y" dh_pysupport diff -Nru lintian-2.93.0/t/recipes/checks/debhelper/debhelper-override-typos/build-spec/debian/rules lintian-2.89.0ubuntu1/t/recipes/checks/debhelper/debhelper-override-typos/build-spec/debian/rules --- lintian-2.93.0/t/recipes/checks/debhelper/debhelper-override-typos/build-spec/debian/rules 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/debhelper/debhelper-override-typos/build-spec/debian/rules 2020-08-10 09:59:45.000000000 +0000 @@ -9,8 +9,8 @@ override_dh_installcrons: override_dh_install_examples: override_dh_install_changelogs : # Extra space -override_dh_perls override_dh_python3 : # Bad then good -override_dh_python3 override_dh_perls : # Good then bad +override_dh_perls override_dh_python2 : # Bad then good +override_dh_python2 override_dh_perls : # Good then bad override_dh_instakk override_dh_install_examples : # Both broken, with space foo override_dh_installdebs bar override_dh_installxmlcatalog: # combining regular and overrides @@ -34,10 +34,10 @@ override_dh_install: # prefix_override_dh_gconfs: override_dh_will_never_exist: -override_dh_python3 override_dh_perl : +override_dh_python2 override_dh_perl : override_dh_auto_configure-% override_dh_auto_install-%: foo override_dh_installdeb bar override_dh_installxmlcatalogs: # combining regular and overrides -override_dh_install: $(PY3VERS:%=install-python%) +override_dh_install: $(PY3VERS:%=install-python%) $(PY2VERS:%=install-python%) # override_dh_instal: would be a typo, but in a comment it doesn't matter execute_after_dh_install: execute_before_dh_install: diff -Nru lintian-2.93.0/t/recipes/checks/debhelper/legacy-libbaz/eval/tags lintian-2.89.0ubuntu1/t/recipes/checks/debhelper/legacy-libbaz/eval/tags --- lintian-2.93.0/t/recipes/checks/debhelper/legacy-libbaz/eval/tags 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/debhelper/legacy-libbaz/eval/tags 2020-08-10 09:59:45.000000000 +0000 @@ -1,9 +1,5 @@ libbaz (source): uses-debhelper-compat-file libbaz (source): package-needs-versioned-debhelper-build-depends 13 -libbaz (source): maintainer-script-lacks-debhelper-token debian/lib.prerm -libbaz (source): maintainer-script-lacks-debhelper-token debian/lib.postinst -libbaz (source): maintainer-script-lacks-debhelper-token debian/dev.prerm -libbaz (source): maintainer-script-lacks-debhelper-token debian/dev.postinst libbaz (source): debian-build-system debhelper libbaz (source): debhelper-compat-level 13 libbaz (source): debhelper-but-no-misc-depends libbaz2-dev diff -Nru lintian-2.93.0/t/recipes/checks/debhelper/oeverride-typo/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/debhelper/oeverride-typo/eval/desc --- lintian-2.93.0/t/recipes/checks/debhelper/oeverride-typo/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/debhelper/oeverride-typo/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -1,3 +1,3 @@ Testname: oeverride-typo Check: debhelper -See-Also: Bug#963765 +References: Bug#963765 diff -Nru lintian-2.93.0/t/recipes/checks/debian/changelog/changelog-file-become-native/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/debian/changelog/changelog-file-become-native/eval/desc --- lintian-2.93.0/t/recipes/checks/debian/changelog/changelog-file-become-native/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/debian/changelog/changelog-file-become-native/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -1,3 +1,3 @@ Testname: changelog-file-become-native -See-Also: Debian Bug #504070 +References: Debian Bug #504070 Check: debian/changelog diff -Nru lintian-2.93.0/t/recipes/checks/debian/changelog/changelog-file-strange-date/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/debian/changelog/changelog-file-strange-date/eval/desc --- lintian-2.93.0/t/recipes/checks/debian/changelog/changelog-file-strange-date/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/debian/changelog/changelog-file-strange-date/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -1,3 +1,3 @@ Testname: changelog-file-strange-date -See-Also: Debian Bug#794674 +References: Debian Bug#794674 Check: debian/changelog diff -Nru lintian-2.93.0/t/recipes/checks/debian/changelog/changelog-file-unreleased/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/debian/changelog/changelog-file-unreleased/eval/desc --- lintian-2.93.0/t/recipes/checks/debian/changelog/changelog-file-unreleased/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/debian/changelog/changelog-file-unreleased/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -2,5 +2,5 @@ Test-Against: latest-debian-changelog-entry-without-new-date unreleased-changelog-distribution -See-Also: Debian Bug#560149 +References: Debian Bug#560149 Check: debian/changelog diff -Nru lintian-2.93.0/t/recipes/checks/debian/changelog/changelog-file-unreleased-signed-changes/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/debian/changelog/changelog-file-unreleased-signed-changes/eval/desc --- lintian-2.93.0/t/recipes/checks/debian/changelog/changelog-file-unreleased-signed-changes/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/debian/changelog/changelog-file-unreleased-signed-changes/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -1,3 +1,3 @@ Testname: changelog-file-unreleased-signed-changes -See-Also: #873520 +References: #873520 Check: debian/changelog diff -Nru lintian-2.93.0/t/recipes/checks/debian/changelog/missing-explicit-entry-fp-unrel/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/debian/changelog/missing-explicit-entry-fp-unrel/eval/desc --- lintian-2.93.0/t/recipes/checks/debian/changelog/missing-explicit-entry-fp-unrel/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/debian/changelog/missing-explicit-entry-fp-unrel/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -2,4 +2,4 @@ Test-Against: changelog-file-missing-explicit-entry Check: debian/changelog -See-Also: Debian Bug #942411 +References: Debian Bug #942411 diff -Nru lintian-2.93.0/t/recipes/checks/debian/changelog/nmu-local-changelog/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/debian/changelog/nmu-local-changelog/eval/desc --- lintian-2.93.0/t/recipes/checks/debian/changelog/nmu-local-changelog/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/debian/changelog/nmu-local-changelog/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -1,4 +1,4 @@ Testname: nmu-local-changelog Test-Against: malformed-debian-changelog-version -See-Also: Debian Bug#501523 +References: Debian Bug#501523 Check: debian/changelog diff -Nru lintian-2.93.0/t/recipes/checks/debian/changelog/nmu-local-version/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/debian/changelog/nmu-local-version/eval/desc --- lintian-2.93.0/t/recipes/checks/debian/changelog/nmu-local-version/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/debian/changelog/nmu-local-version/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -1,4 +1,4 @@ Testname: nmu-local-version Test-Against: malformed-debian-changelog-version -See-Also: Debian Bug#501523 +References: Debian Bug#501523 Check: debian/changelog diff -Nru lintian-2.93.0/t/recipes/checks/debian/control/control-file-general/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/debian/control/control-file-general/eval/desc --- lintian-2.93.0/t/recipes/checks/debian/control/control-file-general/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/debian/control/control-file-general/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -1,5 +1,5 @@ Testname: control-file-general -See-Also: Debian Bug#30020, Debian Bug#409099, Debian Bug#516706, +References: Debian Bug#30020, Debian Bug#409099, Debian Bug#516706, Debian Bug#533202, Debian Bug#557971, Debian Bug#573399, Debian Bug#580494, Debian Bug#657110 Check: debian/control diff -Nru lintian-2.93.0/t/recipes/checks/debian/control/control-file-hardcoded-libc/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/debian/control/control-file-hardcoded-libc/eval/desc --- lintian-2.93.0/t/recipes/checks/debian/control/control-file-hardcoded-libc/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/debian/control/control-file-hardcoded-libc/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -1,3 +1,3 @@ Testname: control-file-hardcoded-libc -See-Also: Debian Bug#512196 +References: Debian Bug#512196 Check: debian/control diff -Nru lintian-2.93.0/t/recipes/checks/debian/control/fields-build-profiles-general/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/debian/control/fields-build-profiles-general/eval/desc --- lintian-2.93.0/t/recipes/checks/debian/control/fields-build-profiles-general/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/debian/control/fields-build-profiles-general/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -1,3 +1,3 @@ Testname: fields-build-profiles-general -See-Also: Debian Bug#540594, Debian Bug#551793 +References: Debian Bug#540594, Debian Bug#551793 Check: debian/control diff -Nru lintian-2.93.0/t/recipes/checks/debian/copyright/dep5/conjunction-vs-alone/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/debian/copyright/dep5/conjunction-vs-alone/eval/desc --- lintian-2.93.0/t/recipes/checks/debian/copyright/dep5/conjunction-vs-alone/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/debian/copyright/dep5/conjunction-vs-alone/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -2,4 +2,4 @@ Check: debian/copyright/dep5 Test-Against: dep5-copyright-license-name-not-unique -See-Also: Bug#801182 +References: Bug#801182 diff -Nru lintian-2.93.0/t/recipes/checks/debian/copyright/dep5/file-does-not-exist/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/debian/copyright/dep5/file-does-not-exist/eval/desc --- lintian-2.93.0/t/recipes/checks/debian/copyright/dep5/file-does-not-exist/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/debian/copyright/dep5/file-does-not-exist/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -1,3 +1,3 @@ Testname: file-does-not-exist Check: debian/copyright/dep5 -See-Also: Bug#888001 +References: Bug#888001 diff -Nru lintian-2.93.0/t/recipes/checks/debian/copyright/dep5/patch-empties-directory/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/debian/copyright/dep5/patch-empties-directory/eval/desc --- lintian-2.93.0/t/recipes/checks/debian/copyright/dep5/patch-empties-directory/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/debian/copyright/dep5/patch-empties-directory/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -3,4 +3,4 @@ Test-Against: wildcard-matches-nothing-in-dep5-copyright unused-file-paragraph-in-dep5-copyright -See-Also: Bug#844274 +References: Bug#844274 diff -Nru lintian-2.93.0/t/recipes/checks/debian/copyright/dep5/redundant-wildcard/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/debian/copyright/dep5/redundant-wildcard/eval/desc --- lintian-2.93.0/t/recipes/checks/debian/copyright/dep5/redundant-wildcard/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/debian/copyright/dep5/redundant-wildcard/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -1,3 +1,3 @@ Testname: redundant-wildcard Check: debian/copyright/dep5 -See-Also: Bug#905747 +References: Bug#905747 diff -Nru lintian-2.93.0/t/recipes/checks/debian/copyright/dep5/reused-wildcard/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/debian/copyright/dep5/reused-wildcard/eval/desc --- lintian-2.93.0/t/recipes/checks/debian/copyright/dep5/reused-wildcard/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/debian/copyright/dep5/reused-wildcard/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -1,3 +1,3 @@ Testname: reused-wildcard Check: debian/copyright/dep5 -See-Also: Bug#905747 +References: Bug#905747 diff -Nru lintian-2.93.0/t/recipes/checks/debian/copyright/dep5/reuse-identifier-in-files/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/debian/copyright/dep5/reuse-identifier-in-files/eval/desc --- lintian-2.93.0/t/recipes/checks/debian/copyright/dep5/reuse-identifier-in-files/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/debian/copyright/dep5/reuse-identifier-in-files/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -2,4 +2,4 @@ Check: debian/copyright/dep5 Test-Against: dep5-copyright-license-name-not-unique -See-Also: Bug#779676 +References: Bug#779676 diff -Nru lintian-2.93.0/t/recipes/checks/debian/copyright/dep5/wildcard-out-of-order/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/debian/copyright/dep5/wildcard-out-of-order/eval/desc --- lintian-2.93.0/t/recipes/checks/debian/copyright/dep5/wildcard-out-of-order/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/debian/copyright/dep5/wildcard-out-of-order/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -1,3 +1,3 @@ Testname: wildcard-out-of-order Check: debian/copyright/dep5 -See-Also: Bug#905747 +References: Bug#905747 diff -Nru lintian-2.93.0/t/recipes/checks/debian/desktop-entries/desktop-file/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/debian/desktop-entries/desktop-file/eval/desc --- lintian-2.93.0/t/recipes/checks/debian/desktop-entries/desktop-file/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/debian/desktop-entries/desktop-file/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -1,3 +1,3 @@ Testname: desktop-file Check: debian/desktop-entries -See-Also: social contract item 2, devref 3.1.4, policy 4.3, Bug#755161 +References: social contract item 2, devref 3.1.4, policy 4.3, Bug#755161 diff -Nru lintian-2.93.0/t/recipes/checks/debian/filenames/duplicate-news-files/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/debian/filenames/duplicate-news-files/eval/desc --- lintian-2.93.0/t/recipes/checks/debian/filenames/duplicate-news-files/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/debian/filenames/duplicate-news-files/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -1,3 +1,3 @@ Testname: duplicate-news-files -See-Also: #429510, #946126 +References: #429510, #946126 Check: debian/filenames diff -Nru lintian-2.93.0/t/recipes/checks/debian/filenames/news-has-debian-extension/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/debian/filenames/news-has-debian-extension/eval/desc --- lintian-2.93.0/t/recipes/checks/debian/filenames/news-has-debian-extension/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/debian/filenames/news-has-debian-extension/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -1,3 +1,3 @@ Testname: news-has-debian-extension -See-Also: #429510, #946126, #946041 +References: #429510, #946126, #946041 Check: debian/filenames diff -Nru lintian-2.93.0/t/recipes/checks/debian/lintian-overrides/comments/absolutely-misspelled/eval/tags lintian-2.89.0ubuntu1/t/recipes/checks/debian/lintian-overrides/comments/absolutely-misspelled/eval/tags --- lintian-2.93.0/t/recipes/checks/debian/lintian-overrides/comments/absolutely-misspelled/eval/tags 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/debian/lintian-overrides/comments/absolutely-misspelled/eval/tags 2020-08-10 09:59:45.000000000 +0000 @@ -1 +1 @@ -absolutely-misspelled (binary): spelling-in-override-comment cute-field (line 5) absolutly absolutely +absolutely-misspelled (binary): spelling-in-override-comment cute-field (line 6) absolutly absolutely diff -Nru lintian-2.93.0/t/recipes/checks/debian/lintian-overrides/comments/lowercase-sql/eval/tags lintian-2.89.0ubuntu1/t/recipes/checks/debian/lintian-overrides/comments/lowercase-sql/eval/tags --- lintian-2.93.0/t/recipes/checks/debian/lintian-overrides/comments/lowercase-sql/eval/tags 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/debian/lintian-overrides/comments/lowercase-sql/eval/tags 2020-08-10 09:59:45.000000000 +0000 @@ -1 +1 @@ -lowercase-sql (binary): capitalization-in-override-comment cute-field (line 5) postgresql PostgreSQL +lowercase-sql (binary): capitalization-in-override-comment cute-field (line 6) postgresql PostgreSQL diff -Nru lintian-2.93.0/t/recipes/checks/debian/manual-pages/manpage-in-1/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/debian/manual-pages/manpage-in-1/eval/desc --- lintian-2.93.0/t/recipes/checks/debian/manual-pages/manpage-in-1/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/debian/manual-pages/manpage-in-1/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -1,3 +1,3 @@ Testname: manpage-in-1 Check: debian/manual-pages -See-Also: social contract item 2, devref 3.1.4, policy 4.3, Bug#755161 +References: social contract item 2, devref 3.1.4, policy 4.3, Bug#755161 diff -Nru lintian-2.93.0/t/recipes/checks/debian/not-installed/triplet-in-library-path/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/debian/not-installed/triplet-in-library-path/eval/desc --- lintian-2.93.0/t/recipes/checks/debian/not-installed/triplet-in-library-path/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/debian/not-installed/triplet-in-library-path/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -1,3 +1,3 @@ Testname: triplet-in-library-path Check: debian/not-installed -See-Also: Debian Bug#961973 +References: Debian Bug#961973 diff -Nru lintian-2.93.0/t/recipes/checks/debian/patches/dep3/applied-upstream/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/debian/patches/dep3/applied-upstream/eval/desc --- lintian-2.93.0/t/recipes/checks/debian/patches/dep3/applied-upstream/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/debian/patches/dep3/applied-upstream/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -2,4 +2,4 @@ Check: debian/patches/dep3 Test-Against: patch-not-forwarded-upstream -See-Also: Bug#965119 +References: Bug#965119 diff -Nru lintian-2.93.0/t/recipes/checks/debian/patches/dep3/empty-forwarded-no-bug/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/debian/patches/dep3/empty-forwarded-no-bug/eval/desc --- lintian-2.93.0/t/recipes/checks/debian/patches/dep3/empty-forwarded-no-bug/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/debian/patches/dep3/empty-forwarded-no-bug/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -1,3 +1,3 @@ Testname: empty-forwarded-no-bug Check: debian/patches/dep3 -See-Also: Bug#755153 +References: Bug#755153 diff -Nru lintian-2.93.0/t/recipes/checks/debian/patches/dep3/forwarded-no/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/debian/patches/dep3/forwarded-no/eval/desc --- lintian-2.93.0/t/recipes/checks/debian/patches/dep3/forwarded-no/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/debian/patches/dep3/forwarded-no/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -1,3 +1,3 @@ Testname: forwarded-no Check: debian/patches/dep3 -See-Also: Bug#755153 +References: Bug#755153 diff -Nru lintian-2.93.0/t/recipes/checks/debian/patches/dep3/forwarded-not-needed/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/debian/patches/dep3/forwarded-not-needed/eval/desc --- lintian-2.93.0/t/recipes/checks/debian/patches/dep3/forwarded-not-needed/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/debian/patches/dep3/forwarded-not-needed/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -2,4 +2,4 @@ Check: debian/patches/dep3 Test-Against: patch-not-forwarded-upstream -See-Also: Bug#755153 +References: Bug#755153 diff -Nru lintian-2.93.0/t/recipes/checks/debian/patches/dep3/origin-upstream/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/debian/patches/dep3/origin-upstream/eval/desc --- lintian-2.93.0/t/recipes/checks/debian/patches/dep3/origin-upstream/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/debian/patches/dep3/origin-upstream/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -2,4 +2,4 @@ Check: debian/patches/dep3 Test-Against: patch-not-forwarded-upstream -See-Also: Bug#966140 +References: Bug#966140 diff -Nru lintian-2.93.0/t/recipes/checks/debian/patches/dep3/pseudo-header/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/debian/patches/dep3/pseudo-header/eval/desc --- lintian-2.93.0/t/recipes/checks/debian/patches/dep3/pseudo-header/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/debian/patches/dep3/pseudo-header/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -2,4 +2,4 @@ Check: debian/patches/dep3 Test-Against: patch-not-forwarded-upstream -See-Also: Bug#966024 +References: Bug#966024 diff -Nru lintian-2.93.0/t/recipes/checks/debian/patches/patch-systems-empty-series/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/debian/patches/patch-systems-empty-series/eval/desc --- lintian-2.93.0/t/recipes/checks/debian/patches/patch-systems-empty-series/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/debian/patches/patch-systems-empty-series/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -1,3 +1,3 @@ Testname: patch-systems-empty-series -See-Also: Debian Bug #525005 +References: Debian Bug #525005 Check: debian/patches diff -Nru lintian-2.93.0/t/recipes/checks/debian/patches/patch-systems-no-readme-source/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/debian/patches/patch-systems-no-readme-source/eval/desc --- lintian-2.93.0/t/recipes/checks/debian/patches/patch-systems-no-readme-source/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/debian/patches/patch-systems-no-readme-source/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -1,3 +1,3 @@ Testname: patch-systems-no-readme-source -See-Also: Debian Bug #537969 +References: Debian Bug #537969 Check: debian/patches diff -Nru lintian-2.93.0/t/recipes/checks/debian/patches/patch-systems-quilt-description/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/debian/patches/patch-systems-quilt-description/eval/desc --- lintian-2.93.0/t/recipes/checks/debian/patches/patch-systems-quilt-description/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/debian/patches/patch-systems-quilt-description/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -1,3 +1,3 @@ Testname: patch-systems-quilt-description -See-Also: Debian Bug #498892 +References: Debian Bug #498892 Check: debian/patches diff -Nru lintian-2.93.0/t/recipes/checks/debian/patches/quilt/patch-systems-empty-series/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/debian/patches/quilt/patch-systems-empty-series/eval/desc --- lintian-2.93.0/t/recipes/checks/debian/patches/quilt/patch-systems-empty-series/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/debian/patches/quilt/patch-systems-empty-series/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -1,4 +1,4 @@ Testname: patch-systems-empty-series Test-Against: quilt-build-dep-but-no-series-file -See-Also: Debian Bug #525005 +References: Debian Bug #525005 Check: debian/patches/quilt diff -Nru lintian-2.93.0/t/recipes/checks/debian/patches/quilt/patch-systems-quilt-description/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/debian/patches/quilt/patch-systems-quilt-description/eval/desc --- lintian-2.93.0/t/recipes/checks/debian/patches/quilt/patch-systems-quilt-description/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/debian/patches/quilt/patch-systems-quilt-description/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -1,3 +1,3 @@ Testname: patch-systems-quilt-description -See-Also: Debian Bug #498892 +References: Debian Bug #498892 Check: debian/patches/quilt diff -Nru lintian-2.93.0/t/recipes/checks/debian/readme/debian-readme-general/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/debian/readme/debian-readme-general/eval/desc --- lintian-2.93.0/t/recipes/checks/debian/readme/debian-readme-general/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/debian/readme/debian-readme-general/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -1,3 +1,3 @@ Testname: debian-readme-general -See-Also: Debian Bug#556456 +References: Debian Bug#556456 Check: debian/readme diff -Nru lintian-2.93.0/t/recipes/checks/debian/rules/debhelper-no-depends/build-spec/debian/rules lintian-2.89.0ubuntu1/t/recipes/checks/debian/rules/debhelper-no-depends/build-spec/debian/rules --- lintian-2.93.0/t/recipes/checks/debian/rules/debhelper-no-depends/build-spec/debian/rules 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/debian/rules/debhelper-no-depends/build-spec/debian/rules 2020-08-10 09:59:45.000000000 +0000 @@ -12,8 +12,8 @@ -dh_dpatch_patch # We don't warn about commands inside make conditionals, so none of these # get any warnings. -ifeq "$(USE_DH_PYTHON3)" "y" - dh_python3 +ifeq "$(USE_DH_PYTHON2)" "y" + dh_python2 else ifeq "$(USE_PYSUPPORT)" "y" dh_pysupport diff -Nru lintian-2.93.0/t/recipes/checks/debian/rules/dh-sequencer/curly-braces/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/debian/rules/dh-sequencer/curly-braces/eval/desc --- lintian-2.93.0/t/recipes/checks/debian/rules/dh-sequencer/curly-braces/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/debian/rules/dh-sequencer/curly-braces/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -2,4 +2,4 @@ Check: debian/rules/dh-sequencer Test-Against: no-dh-sequencer -See-Also: Debian Bug#947115 +References: Debian Bug#947115 diff -Nru lintian-2.93.0/t/recipes/checks/debian/rules/dh-sequencer/dependency/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/debian/rules/dh-sequencer/dependency/eval/desc --- lintian-2.93.0/t/recipes/checks/debian/rules/dh-sequencer/dependency/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/debian/rules/dh-sequencer/dependency/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -2,4 +2,4 @@ Check: debian/rules/dh-sequencer Test-Against: no-dh-sequencer -See-Also: #968108 +References: #968108 diff -Nru lintian-2.93.0/t/recipes/checks/debian/rules/dh-sequencer/double-quotes/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/debian/rules/dh-sequencer/double-quotes/eval/desc --- lintian-2.93.0/t/recipes/checks/debian/rules/dh-sequencer/double-quotes/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/debian/rules/dh-sequencer/double-quotes/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -2,4 +2,4 @@ Check: debian/rules/dh-sequencer Test-Against: no-dh-sequencer -See-Also: https://salsa.debian.org/lintian/lintian/merge_requests/288 +References: https://salsa.debian.org/lintian/lintian/merge_requests/288 diff -Nru lintian-2.93.0/t/recipes/checks/debian/rules/dh-sequencer/explicit-targets/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/debian/rules/dh-sequencer/explicit-targets/eval/desc --- lintian-2.93.0/t/recipes/checks/debian/rules/dh-sequencer/explicit-targets/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/debian/rules/dh-sequencer/explicit-targets/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -2,4 +2,4 @@ Check: debian/rules/dh-sequencer Test-Against: no-dh-sequencer -See-Also: Debian Bug#930679 +References: Debian Bug#930679 diff -Nru lintian-2.93.0/t/recipes/checks/debian/rules/dh-sequencer/no-dh-sequencer/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/debian/rules/dh-sequencer/no-dh-sequencer/eval/desc --- lintian-2.93.0/t/recipes/checks/debian/rules/dh-sequencer/no-dh-sequencer/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/debian/rules/dh-sequencer/no-dh-sequencer/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -1,3 +1,3 @@ Testname: no-dh-sequencer Check: debian/rules/dh-sequencer -See-Also: Debian Bug#930679 +References: Debian Bug#930679 diff -Nru lintian-2.93.0/t/recipes/checks/debian/rules/dh-sequencer/parentheses/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/debian/rules/dh-sequencer/parentheses/eval/desc --- lintian-2.93.0/t/recipes/checks/debian/rules/dh-sequencer/parentheses/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/debian/rules/dh-sequencer/parentheses/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -2,4 +2,4 @@ Check: debian/rules/dh-sequencer Test-Against: no-dh-sequencer -See-Also: Debian Bug#947115 +References: Debian Bug#947115 diff -Nru lintian-2.93.0/t/recipes/checks/debian/rules/dh-sequencer/single-quotes/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/debian/rules/dh-sequencer/single-quotes/eval/desc --- lintian-2.93.0/t/recipes/checks/debian/rules/dh-sequencer/single-quotes/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/debian/rules/dh-sequencer/single-quotes/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -2,4 +2,4 @@ Check: debian/rules/dh-sequencer Test-Against: no-dh-sequencer -See-Also: https://salsa.debian.org/lintian/lintian/merge_requests/288 +References: https://salsa.debian.org/lintian/lintian/merge_requests/288 diff -Nru lintian-2.93.0/t/recipes/checks/debian/rules/dh-sequencer/with-comments/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/debian/rules/dh-sequencer/with-comments/eval/desc --- lintian-2.93.0/t/recipes/checks/debian/rules/dh-sequencer/with-comments/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/debian/rules/dh-sequencer/with-comments/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -2,4 +2,4 @@ Check: debian/rules/dh-sequencer Test-Against: no-dh-sequencer -See-Also: Debian Bug#960485 +References: Debian Bug#960485 diff -Nru lintian-2.93.0/t/recipes/checks/debian/rules/permissions-775/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/debian/rules/permissions-775/eval/desc --- lintian-2.93.0/t/recipes/checks/debian/rules/permissions-775/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/debian/rules/permissions-775/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -1,4 +1,4 @@ Testname: permissions-775 Check: debian/rules Test-Against: debian-rules-not-executable -See-Also: Bug#945869, Bug#945869 +References: Bug#945869, Bug#945869 diff -Nru lintian-2.93.0/t/recipes/checks/debian/rules/rules-build-dep-pattern/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/debian/rules/rules-build-dep-pattern/eval/desc --- lintian-2.93.0/t/recipes/checks/debian/rules/rules-build-dep-pattern/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/debian/rules/rules-build-dep-pattern/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -1,3 +1,3 @@ Testname: rules-build-dep-pattern -See-Also: Bug#536405 +References: Bug#536405 Check: debian/rules diff -Nru lintian-2.93.0/t/recipes/checks/debian/rules/rules-dh-unused-target/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/debian/rules/rules-dh-unused-target/eval/desc --- lintian-2.93.0/t/recipes/checks/debian/rules/rules-dh-unused-target/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/debian/rules/rules-dh-unused-target/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -1,4 +1,4 @@ Testname: rules-dh-unused-target Test-Against: binary-arch-rules-but-pkg-is-arch-indep -See-Also: <20080806175819.GV11882@mail-vs.djpig.de> +References: <20080806175819.GV11882@mail-vs.djpig.de> Check: debian/rules diff -Nru lintian-2.93.0/t/recipes/checks/debian/rules/rules-dh-unused-target-nonempty/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/debian/rules/rules-dh-unused-target-nonempty/eval/desc --- lintian-2.93.0/t/recipes/checks/debian/rules/rules-dh-unused-target-nonempty/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/debian/rules/rules-dh-unused-target-nonempty/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -1,3 +1,3 @@ Testname: rules-dh-unused-target-nonempty -See-Also: <20080806175819.GV11882@mail-vs.djpig.de> +References: <20080806175819.GV11882@mail-vs.djpig.de> Check: debian/rules diff -Nru lintian-2.93.0/t/recipes/checks/debian/rules/rules-ignore-define/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/debian/rules/rules-ignore-define/eval/desc --- lintian-2.93.0/t/recipes/checks/debian/rules/rules-ignore-define/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/debian/rules/rules-ignore-define/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -1,4 +1,4 @@ Testname: rules-ignore-define Test-Against: binary-arch-rules-but-pkg-is-arch-indep -See-Also: Debian Bug#510869 +References: Debian Bug#510869 Check: debian/rules diff -Nru lintian-2.93.0/t/recipes/checks/debian/rules/rules-missing-targets-with-includes/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/debian/rules/rules-missing-targets-with-includes/eval/desc --- lintian-2.93.0/t/recipes/checks/debian/rules/rules-missing-targets-with-includes/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/debian/rules/rules-missing-targets-with-includes/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -1,4 +1,4 @@ Testname: rules-missing-targets-with-includes Test-Against: debian-rules-missing-required-target -See-Also: Debian Bug#607281 +References: Debian Bug#607281 Check: debian/rules diff -Nru lintian-2.93.0/t/recipes/checks/debian/watch/bug-950250-original/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/debian/watch/bug-950250-original/eval/desc --- lintian-2.93.0/t/recipes/checks/debian/watch/bug-950250-original/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/debian/watch/bug-950250-original/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -1,3 +1,3 @@ Testname: bug-950250-original Check: debian/watch -See-Also: Bug#950250 +Reference: Bug#950250 diff -Nru lintian-2.93.0/t/recipes/checks/debian/watch/bug-950250-reordered/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/debian/watch/bug-950250-reordered/eval/desc --- lintian-2.93.0/t/recipes/checks/debian/watch/bug-950250-reordered/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/debian/watch/bug-950250-reordered/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -1,3 +1,3 @@ Testname: bug-950250-reordered Check: debian/watch -See-Also: Bug#950250 +Reference: Bug#950250 diff -Nru lintian-2.93.0/t/recipes/checks/debian/watch/bug-950277/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/debian/watch/bug-950277/eval/desc --- lintian-2.93.0/t/recipes/checks/debian/watch/bug-950277/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/debian/watch/bug-950277/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -1,3 +1,3 @@ Testname: bug-950277 Check: debian/watch -See-Also: Bug#950277 +References: Bug#950277 diff -Nru lintian-2.93.0/t/recipes/checks/debian/watch/comments-only/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/debian/watch/comments-only/eval/desc --- lintian-2.93.0/t/recipes/checks/debian/watch/comments-only/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/debian/watch/comments-only/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -2,4 +2,4 @@ Check: debian/watch Test-Against: debian-watch-file-missing-version -See-Also: Bug#965385 +References: Bug#965385 diff -Nru lintian-2.93.0/t/recipes/checks/debian/watch/watch-file-general/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/debian/watch/watch-file-general/eval/desc --- lintian-2.93.0/t/recipes/checks/debian/watch/watch-file-general/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/debian/watch/watch-file-general/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -1,3 +1,3 @@ Testname: watch-file-general -See-Also: Debian Bug#510398 +References: Debian Bug#510398 Check: debian/watch diff -Nru lintian-2.93.0/t/recipes/checks/debian/watch/watch-file-pgpmode-next/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/debian/watch/watch-file-pgpmode-next/eval/desc --- lintian-2.93.0/t/recipes/checks/debian/watch/watch-file-pgpmode-next/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/debian/watch/watch-file-pgpmode-next/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -1,4 +1,4 @@ Testname: watch-file-pgpmode-next Test-Against: debian-watch-does-not-check-gpg-signature -See-Also: #841000 +References: #841000 Check: debian/watch diff -Nru lintian-2.93.0/t/recipes/checks/debian/watch/watch-file-pgpmode-none/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/debian/watch/watch-file-pgpmode-none/eval/desc --- lintian-2.93.0/t/recipes/checks/debian/watch/watch-file-pgpmode-none/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/debian/watch/watch-file-pgpmode-none/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -1,4 +1,4 @@ Testname: watch-file-pgpmode-none Test-Against: debian-watch-file-pubkey-file-is-missing -See-Also: #841000 +References: #841000 Check: debian/watch diff -Nru lintian-2.93.0/t/recipes/checks/documentation/files-python-general/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/documentation/files-python-general/eval/desc --- lintian-2.93.0/t/recipes/checks/documentation/files-python-general/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/documentation/files-python-general/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -1,3 +1,3 @@ Testname: files-python-general -See-Also: Debian Bug#608810, Debian Bug#756005 +References: Debian Bug#608810, Debian Bug#756005 Check: documentation diff -Nru lintian-2.93.0/t/recipes/checks/documentation/files-uses-dpkg-database-directly/eval/tags lintian-2.89.0ubuntu1/t/recipes/checks/documentation/files-uses-dpkg-database-directly/eval/tags --- lintian-2.93.0/t/recipes/checks/documentation/files-uses-dpkg-database-directly/eval/tags 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/documentation/files-uses-dpkg-database-directly/eval/tags 2020-08-10 09:59:45.000000000 +0000 @@ -1,2 +1 @@ -files-uses-dpkg-database-directly (binary): package-contains-documentation-outside-usr-share-doc var/lib/test/misc.txt files-uses-dpkg-database-directly (binary): package-contains-documentation-outside-usr-share-doc var/lib/test/README diff -Nru lintian-2.93.0/t/recipes/checks/documentation/files-zero-byte-doc/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/documentation/files-zero-byte-doc/eval/desc --- lintian-2.93.0/t/recipes/checks/documentation/files-zero-byte-doc/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/documentation/files-zero-byte-doc/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -1,3 +1,3 @@ Testname: files-zero-byte-doc -See-Also: Debian Bug#507273 +References: Debian Bug#507273 Check: documentation diff -Nru lintian-2.93.0/t/recipes/checks/documentation/legacy-filenames/eval/tags lintian-2.89.0ubuntu1/t/recipes/checks/documentation/legacy-filenames/eval/tags --- lintian-2.93.0/t/recipes/checks/documentation/legacy-filenames/eval/tags 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/documentation/legacy-filenames/eval/tags 2020-08-10 09:59:45.000000000 +0000 @@ -6,4 +6,3 @@ filenames (binary): package-contains-documentation-outside-usr-share-doc usr/share/pixmaps/license.txt filenames (binary): package-contains-documentation-outside-usr-share-doc usr/share/menu/README filenames (binary): package-contains-documentation-outside-usr-share-doc usr/lib/menu/README -filenames (binary): package-contains-documentation-outside-usr-share-doc usr/lib/ma-dir/perl/version/foo/.hg_archival.txt diff -Nru lintian-2.93.0/t/recipes/checks/documentation/manual/acute-accent/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/documentation/manual/acute-accent/eval/desc --- lintian-2.93.0/t/recipes/checks/documentation/manual/acute-accent/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/documentation/manual/acute-accent/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -1,3 +1,3 @@ Testname: acute-accent Check: documentation/manual -See-Also: Bug#554897, Bug#507673 +References: Bug#554897, Bug#507673 diff -Nru lintian-2.93.0/t/recipes/checks/documentation/manual/combined-manpage/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/documentation/manual/combined-manpage/eval/desc --- lintian-2.93.0/t/recipes/checks/documentation/manual/combined-manpage/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/documentation/manual/combined-manpage/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -2,5 +2,5 @@ Check: documentation/manual Test-Against: wrong-manual-section -See-Also: +References: Bug#962601 diff -Nru lintian-2.93.0/t/recipes/checks/documentation/manual/manpages-general/eval/tags lintian-2.89.0ubuntu1/t/recipes/checks/documentation/manual/manpages-general/eval/tags --- lintian-2.93.0/t/recipes/checks/documentation/manual/manpages-general/eval/tags 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/documentation/manual/manpages-general/eval/tags 2020-08-10 09:59:45.000000000 +0000 @@ -16,9 +16,7 @@ manpages-general (binary): manual-page-from-template usr/share/man/man1/program.1.gz manpages-general (binary): manual-page-for-system-command usr/sbin/usr-sbin-binary manpages-general (binary): groff-message usr/share/man/man3/included.3.gz 6: warning: macro 'zY' not defined -manpages-general (binary): groff-message usr/share/man/man3/include.3.gz man3/included.3:8: error: end of file while ignoring input lines manpages-general (binary): groff-message usr/share/man/man3/include.3.gz man3/included.3:6: warning: macro 'zY' not defined -manpages-general (binary): groff-message usr/share/man/man3/include.3.gz man3/included.3:13: warning: macro '--' not defined manpages-general (binary): groff-message usr/share/man/man1/test.1P.gz 14: warning: macro 'dep' not defined (possibly missing space after 'de') manpages-general (binary): empty-manual-page usr/share/man/man6/usr-games-binary.6.gz manpages-general (binary): empty-manual-page usr/share/man/man1/usr-sbin-binary.1.gz diff -Nru lintian-2.93.0/t/recipes/checks/documentation/manual/scripts-ocamlrun/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/documentation/manual/scripts-ocamlrun/eval/desc --- lintian-2.93.0/t/recipes/checks/documentation/manual/scripts-ocamlrun/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/documentation/manual/scripts-ocamlrun/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -1,3 +1,3 @@ Testname: scripts-ocamlrun -See-Also: Debian Bug#495431 +References: Debian Bug#495431 Check: documentation/manual diff -Nru lintian-2.93.0/t/recipes/checks/documentation/texinfo/infofiles-general/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/documentation/texinfo/infofiles-general/eval/desc --- lintian-2.93.0/t/recipes/checks/documentation/texinfo/infofiles-general/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/documentation/texinfo/infofiles-general/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -1,3 +1,3 @@ Testname: infofiles-general -See-Also: Bug#534640 +References: Bug#534640 Check: documentation/texinfo diff -Nru lintian-2.93.0/t/recipes/checks/fields/description/squeezed-comma/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/fields/description/squeezed-comma/eval/desc --- lintian-2.93.0/t/recipes/checks/fields/description/squeezed-comma/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/fields/description/squeezed-comma/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -1,3 +1,3 @@ Testname: squeezed-comma Check: fields/description -See-Also: Bug#591665, Bug#591664 +References: Bug#591665, Bug#591664 diff -Nru lintian-2.93.0/t/recipes/checks/fields/distribution/distribution-multiple-bad/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/fields/distribution/distribution-multiple-bad/eval/desc --- lintian-2.93.0/t/recipes/checks/fields/distribution/distribution-multiple-bad/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/fields/distribution/distribution-multiple-bad/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -1,3 +1,3 @@ Testname: distribution-multiple-bad -See-Also: Debian Bug#514853 +References: Debian Bug#514853 Check: fields/distribution diff -Nru lintian-2.93.0/t/recipes/checks/fields/distribution/distribution-ubuntu-native/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/fields/distribution/distribution-ubuntu-native/eval/desc --- lintian-2.93.0/t/recipes/checks/fields/distribution/distribution-ubuntu-native/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/fields/distribution/distribution-ubuntu-native/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -1,5 +1,5 @@ Testname: distribution-ubuntu-native Test-Against: bad-distribution-in-changes-file Profile: ubuntu/main -See-Also: Debian Bug#507740 +References: Debian Bug#507740 Check: fields/distribution diff -Nru lintian-2.93.0/t/recipes/checks/fields/distribution/nmu-ubuntu-native/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/fields/distribution/nmu-ubuntu-native/eval/desc --- lintian-2.93.0/t/recipes/checks/fields/distribution/nmu-ubuntu-native/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/fields/distribution/nmu-ubuntu-native/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -1,5 +1,5 @@ Testname: nmu-ubuntu-native Profile: ubuntu/main Test-Against: bad-distribution-in-changes-file -See-Also: Debian Bug #507740 +References: Debian Bug #507740 Check: fields/distribution diff -Nru lintian-2.93.0/t/recipes/checks/fields/length/depends-field-too-long/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/fields/length/depends-field-too-long/eval/desc --- lintian-2.93.0/t/recipes/checks/fields/length/depends-field-too-long/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/fields/length/depends-field-too-long/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -1,3 +1,3 @@ Testname: depends-field-too-long -See-Also: Debian Bug#942493 +References: Debian Bug#942493 Check: fields/length diff -Nru lintian-2.93.0/t/recipes/checks/fields/length/provides-field-too-long/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/fields/length/provides-field-too-long/eval/desc --- lintian-2.93.0/t/recipes/checks/fields/length/provides-field-too-long/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/fields/length/provides-field-too-long/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -1,3 +1,3 @@ Testname: provides-field-too-long -See-Also: Debian Bug#942493 +References: Debian Bug#942493 Check: fields/length diff -Nru lintian-2.93.0/t/recipes/checks/fields/mail-address/distribution-multiple-bad/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/fields/mail-address/distribution-multiple-bad/eval/desc --- lintian-2.93.0/t/recipes/checks/fields/mail-address/distribution-multiple-bad/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/fields/mail-address/distribution-multiple-bad/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -1,3 +1,3 @@ Testname: distribution-multiple-bad -See-Also: Debian Bug#514853 +References: Debian Bug#514853 Check: fields/mail-address diff -Nru lintian-2.93.0/t/recipes/checks/fields/mail-address/java-team-fp/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/fields/mail-address/java-team-fp/eval/desc --- lintian-2.93.0/t/recipes/checks/fields/mail-address/java-team-fp/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/fields/mail-address/java-team-fp/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -1,3 +1,3 @@ Testname: java-team-fp Check: fields/mail-address -See-Also: Bug#962448 +References: Bug#962448 diff -Nru lintian-2.93.0/t/recipes/checks/fields/mail-address/missing-closing-bracket/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/fields/mail-address/missing-closing-bracket/eval/desc --- lintian-2.93.0/t/recipes/checks/fields/mail-address/missing-closing-bracket/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/fields/mail-address/missing-closing-bracket/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -2,4 +2,4 @@ Check: fields/mail-address Test-Against: malformed-contact -See-Also: Bug#965335 +References: Bug#965335 diff -Nru lintian-2.93.0/t/recipes/checks/fields/mail-address/right-to-left-override/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/fields/mail-address/right-to-left-override/eval/desc --- lintian-2.93.0/t/recipes/checks/fields/mail-address/right-to-left-override/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/fields/mail-address/right-to-left-override/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -1,3 +1,3 @@ Testname: right-to-left-override Check: fields/mail-address -See-Also: Bug#962277 +Reference: Bug#962277 diff -Nru lintian-2.93.0/t/recipes/checks/fields/mail-address/watch-file-pgpmode-next/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/fields/mail-address/watch-file-pgpmode-next/eval/desc --- lintian-2.93.0/t/recipes/checks/fields/mail-address/watch-file-pgpmode-next/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/fields/mail-address/watch-file-pgpmode-next/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -1,3 +1,3 @@ Testname: watch-file-pgpmode-next -See-Also: #841000 +References: #841000 Check: fields/mail-address diff -Nru lintian-2.93.0/t/recipes/checks/fields/maintainer/java-team-fp/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/fields/maintainer/java-team-fp/eval/desc --- lintian-2.93.0/t/recipes/checks/fields/maintainer/java-team-fp/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/fields/maintainer/java-team-fp/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -1,3 +1,3 @@ Testname: java-team-fp Check: fields/maintainer -See-Also: Bug#962448 +References: Bug#962448 diff -Nru lintian-2.93.0/t/recipes/checks/fields/maintainer/ubuntu-maintainer-different/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/fields/maintainer/ubuntu-maintainer-different/eval/desc --- lintian-2.93.0/t/recipes/checks/fields/maintainer/ubuntu-maintainer-different/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/fields/maintainer/ubuntu-maintainer-different/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -1,5 +1,5 @@ Testname: ubuntu-maintainer-different Check: fields/maintainer Test-Against: inconsistent-maintainer -See-Also: Ubuntu Bug#1862787, +References: Ubuntu Bug#1862787, https://wiki.ubuntu.com/DebianMaintainerField diff -Nru lintian-2.93.0/t/recipes/checks/fields/multi-line/multiple-lines-in-maintainer-field/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/fields/multi-line/multiple-lines-in-maintainer-field/eval/desc --- lintian-2.93.0/t/recipes/checks/fields/multi-line/multiple-lines-in-maintainer-field/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/fields/multi-line/multiple-lines-in-maintainer-field/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -1,3 +1,3 @@ Testname: multiple-lines-in-maintainer-field -See-Also: Policy 5.6 & 7.1 +References: Policy 5.6 & 7.1 Check: fields/multi-line diff -Nru lintian-2.93.0/t/recipes/checks/fields/package-relations/fields-build-depends-general/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/fields/package-relations/fields-build-depends-general/eval/desc --- lintian-2.93.0/t/recipes/checks/fields/package-relations/fields-build-depends-general/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/fields/package-relations/fields-build-depends-general/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -1,3 +1,3 @@ Testname: fields-build-depends-general -See-Also: Debian Bug#540594, Debian Bug#551793 +References: Debian Bug#540594, Debian Bug#551793 Check: fields/package-relations diff -Nru lintian-2.93.0/t/recipes/checks/fields/package-relations/fields-build-profiles-general/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/fields/package-relations/fields-build-profiles-general/eval/desc --- lintian-2.93.0/t/recipes/checks/fields/package-relations/fields-build-profiles-general/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/fields/package-relations/fields-build-profiles-general/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -1,3 +1,3 @@ Testname: fields-build-profiles-general -See-Also: Debian Bug#540594, Debian Bug#551793 +References: Debian Bug#540594, Debian Bug#551793 Check: fields/package-relations diff -Nru lintian-2.93.0/t/recipes/checks/fields/package-type/explicit-type-deb/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/fields/package-type/explicit-type-deb/eval/desc --- lintian-2.93.0/t/recipes/checks/fields/package-type/explicit-type-deb/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/fields/package-type/explicit-type-deb/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -1,3 +1,3 @@ Testname: explicit-type-deb Check: fields/package-type -See-Also: Policy 5.6.28, Debian Bug#951513, Debian Bug#953857 +Reference: Policy 5.6.28, Debian Bug#951513, Debian Bug#953857 diff -Nru lintian-2.93.0/t/recipes/checks/fields/recommended/control-file-general/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/fields/recommended/control-file-general/eval/desc --- lintian-2.93.0/t/recipes/checks/fields/recommended/control-file-general/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/fields/recommended/control-file-general/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -1,5 +1,5 @@ Testname: control-file-general -See-Also: Debian Bug#30020, Debian Bug#409099, Debian Bug#516706, +References: Debian Bug#30020, Debian Bug#409099, Debian Bug#516706, Debian Bug#533202, Debian Bug#557971, Debian Bug#573399, Debian Bug#580494, Debian Bug#657110 Check: fields/recommended diff -Nru lintian-2.93.0/t/recipes/checks/fields/style/go-import-path/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/fields/style/go-import-path/eval/desc --- lintian-2.93.0/t/recipes/checks/fields/style/go-import-path/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/fields/style/go-import-path/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -2,4 +2,4 @@ Check: fields/style Test-Against: cute-field -See-Also: Bug#965966 +References: Bug#965966 diff -Nru lintian-2.93.0/t/recipes/checks/fields/terminal-control/colorful/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/fields/terminal-control/colorful/eval/desc --- lintian-2.93.0/t/recipes/checks/fields/terminal-control/colorful/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/fields/terminal-control/colorful/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -1,3 +1,3 @@ Testname: colorful Check: fields/terminal-control -See-Also: Bug#962277 +Reference: Bug#962277 diff -Nru lintian-2.93.0/t/recipes/checks/files/compressed/gz/timestamp-in-gzip/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/files/compressed/gz/timestamp-in-gzip/eval/desc --- lintian-2.93.0/t/recipes/checks/files/compressed/gz/timestamp-in-gzip/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/files/compressed/gz/timestamp-in-gzip/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -1,3 +1,3 @@ Testname: timestamp-in-gzip Check: files/compressed/gz -See-Also: Bug#762105 +Reference: Bug#762105 diff -Nru lintian-2.93.0/t/recipes/checks/files/contents/scripts-maintainer-general/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/files/contents/scripts-maintainer-general/eval/desc --- lintian-2.93.0/t/recipes/checks/files/contents/scripts-maintainer-general/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/files/contents/scripts-maintainer-general/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -1,4 +1,4 @@ Testname: scripts-maintainer-general Profile: ubuntu/main -See-Also: Debian Bug#532984 +References: Debian Bug#532984 Check: files/contents diff -Nru lintian-2.93.0/t/recipes/checks/files/hierarchy/links/leaving-architecture/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/files/hierarchy/links/leaving-architecture/eval/desc --- lintian-2.93.0/t/recipes/checks/files/hierarchy/links/leaving-architecture/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/files/hierarchy/links/leaving-architecture/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -1,3 +1,3 @@ Testname: leaving-architecture Check: files/hierarchy/links -See-Also: Bug#243158, Bug#964073 +References: Bug#243158, Bug#964073 diff -Nru lintian-2.93.0/t/recipes/checks/files/hierarchy/links/up-inside-architecture/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/files/hierarchy/links/up-inside-architecture/eval/desc --- lintian-2.93.0/t/recipes/checks/files/hierarchy/links/up-inside-architecture/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/files/hierarchy/links/up-inside-architecture/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -2,4 +2,4 @@ Check: files/hierarchy/links Test-Against: breakout-link -See-Also: Bug#243158, Bug#964073 +References: Bug#243158, Bug#964073 diff -Nru lintian-2.93.0/t/recipes/checks/files/hierarchy/links/usr-lib-to-opt/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/files/hierarchy/links/usr-lib-to-opt/eval/desc --- lintian-2.93.0/t/recipes/checks/files/hierarchy/links/usr-lib-to-opt/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/files/hierarchy/links/usr-lib-to-opt/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -1,3 +1,3 @@ Testname: usr-lib-to-opt Check: files/hierarchy/links -See-Also: Bug#964073 +References: Bug#964073 diff -Nru lintian-2.93.0/t/recipes/checks/files/hierarchy/path-segments/share-doc-share/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/files/hierarchy/path-segments/share-doc-share/eval/desc --- lintian-2.93.0/t/recipes/checks/files/hierarchy/path-segments/share-doc-share/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/files/hierarchy/path-segments/share-doc-share/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -1,3 +1,3 @@ Testname: share-doc-share Check: files/hierarchy/path-segments -See-Also: Bug#950052, Bug#950027 +References: Bug#950052, Bug#950027 diff -Nru lintian-2.93.0/t/recipes/checks/files/hierarchy/path-segments/share-doc-share/eval/tags lintian-2.89.0ubuntu1/t/recipes/checks/files/hierarchy/path-segments/share-doc-share/eval/tags --- lintian-2.93.0/t/recipes/checks/files/hierarchy/path-segments/share-doc-share/eval/tags 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/files/hierarchy/path-segments/share-doc-share/eval/tags 2020-08-10 09:59:45.000000000 +0000 @@ -1 +1 @@ -share-doc-share (binary): repeated-path-segment share usr/share/doc/share/ +share-doc-share (binary): repeated-path-segment share usr/share/doc/share/worth-sharing.txt diff -Nru lintian-2.93.0/t/recipes/checks/files/symbolic-links/dev-null-fp/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/files/symbolic-links/dev-null-fp/eval/desc --- lintian-2.93.0/t/recipes/checks/files/symbolic-links/dev-null-fp/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/files/symbolic-links/dev-null-fp/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -2,4 +2,4 @@ Check: files/symbolic-links Test-Against: absolute-symbolic-link-target-in-source -See-Also: Bug#964111, Bug#964234 +References: Bug#964111, Bug#964234 diff -Nru lintian-2.93.0/t/recipes/checks/fonts/opentype/use-restricted/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/fonts/opentype/use-restricted/eval/desc --- lintian-2.93.0/t/recipes/checks/fonts/opentype/use-restricted/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/fonts/opentype/use-restricted/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -1,3 +1,3 @@ Testname: use-restricted Check: fonts/opentype -See-Also: Debian Bug#635068 +References: Debian Bug#635068 diff -Nru lintian-2.93.0/t/recipes/checks/fonts/truetype/use-restricted/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/fonts/truetype/use-restricted/eval/desc --- lintian-2.93.0/t/recipes/checks/fonts/truetype/use-restricted/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/fonts/truetype/use-restricted/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -1,3 +1,3 @@ Testname: use-restricted Check: fonts/truetype -See-Also: Debian Bug#635068 +References: Debian Bug#635068 diff -Nru lintian-2.93.0/t/recipes/checks/languages/fortran/gfortran/missing-prerequisite-for-module/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/languages/fortran/gfortran/missing-prerequisite-for-module/eval/desc --- lintian-2.93.0/t/recipes/checks/languages/fortran/gfortran/missing-prerequisite-for-module/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/languages/fortran/gfortran/missing-prerequisite-for-module/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -1,5 +1,5 @@ Testname: missing-prerequisite-for-module Check: languages/fortran/gfortran -See-Also: Debian Bug #796352, +References: Debian Bug #796352, Debian Bug #714730, https://salsa.debian.org/science-team/dh-fortran-mod/blob/debian/master/dh_fortran_mod.in diff -Nru lintian-2.93.0/t/recipes/checks/languages/fortran/gfortran/no-module-version/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/languages/fortran/gfortran/no-module-version/eval/desc --- lintian-2.93.0/t/recipes/checks/languages/fortran/gfortran/no-module-version/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/languages/fortran/gfortran/no-module-version/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -1,5 +1,5 @@ Testname: no-module-version Check: languages/fortran/gfortran -See-Also: Debian Bug #796352, +References: Debian Bug #796352, Debian Bug #714730, https://salsa.debian.org/science-team/dh-fortran-mod/blob/debian/master/dh_fortran_mod.in diff -Nru lintian-2.93.0/t/recipes/checks/languages/javascript/embedded/files-embedded/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/languages/javascript/embedded/files-embedded/eval/desc --- lintian-2.93.0/t/recipes/checks/languages/javascript/embedded/files-embedded/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/languages/javascript/embedded/files-embedded/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -1,3 +1,3 @@ Testname: files-embedded -See-Also: +References: Check: languages/javascript/embedded diff -Nru lintian-2.93.0/t/recipes/checks/languages/perl/yapp/yapp-parser/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/languages/perl/yapp/yapp-parser/eval/desc --- lintian-2.93.0/t/recipes/checks/languages/perl/yapp/yapp-parser/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/languages/perl/yapp/yapp-parser/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -1,3 +1,3 @@ Testname: yapp-parser Check: languages/perl/yapp -See-Also: #921080 +Reference: #921080 diff -Nru lintian-2.93.0/t/recipes/checks/languages/php/embedded/files-embedded/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/languages/php/embedded/files-embedded/eval/desc --- lintian-2.93.0/t/recipes/checks/languages/php/embedded/files-embedded/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/languages/php/embedded/files-embedded/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -1,3 +1,3 @@ Testname: files-embedded -See-Also: +References: Check: languages/php/embedded diff -Nru lintian-2.93.0/t/recipes/checks/languages/python/feedparser/files-embedded/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/languages/python/feedparser/files-embedded/eval/desc --- lintian-2.93.0/t/recipes/checks/languages/python/feedparser/files-embedded/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/languages/python/feedparser/files-embedded/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -1,3 +1,3 @@ Testname: files-embedded -See-Also: +References: Check: languages/python/feedparser diff -Nru lintian-2.93.0/t/recipes/checks/languages/python/files-python-general/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/languages/python/files-python-general/eval/desc --- lintian-2.93.0/t/recipes/checks/languages/python/files-python-general/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/languages/python/files-python-general/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -1,3 +1,3 @@ Testname: files-python-general -See-Also: Debian Bug#608810, Debian Bug#756005 +References: Debian Bug#608810, Debian Bug#756005 Check: languages/python diff -Nru lintian-2.93.0/t/recipes/checks/languages/python/python-build-depends-on-sphinx-unrel/build-spec/debian/control.in lintian-2.89.0ubuntu1/t/recipes/checks/languages/python/python-build-depends-on-sphinx-unrel/build-spec/debian/control.in --- lintian-2.93.0/t/recipes/checks/languages/python/python-build-depends-on-sphinx-unrel/build-spec/debian/control.in 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/languages/python/python-build-depends-on-sphinx-unrel/build-spec/debian/control.in 2020-08-10 09:59:45.000000000 +0000 @@ -3,12 +3,21 @@ Section: python Maintainer: [% $author %] Standards-Version: [% $standards_version %] -Build-Depends: [% $build_depends %], python3-sphinx +Build-Depends: [% $build_depends %], python-sphinx, python3-sphinx Rules-Requires-Root: no +Package: python-[% $source %] +Architecture: all +Depends: ${misc:Depends}, python2.7 +Description: Test package + This is a test package designed to exercise some feature or tag of + Lintian. It is part of the Lintian test suite and may do very odd + things. It should not be installed like a regular package. It may + be an empty package. + Package: python3-[% $source %] Architecture: all -Depends: ${misc:Depends}, ${python3::Depends} +Depends: ${misc:Depends}, python3 Description: Test package (Python 3) This is a test package designed to exercise some feature or tag of Lintian. It is part of the Lintian test suite and may do very odd diff -Nru lintian-2.93.0/t/recipes/checks/languages/python/scripts/python-script-uses-unversioned-python-in-shebang/build-spec/debian/control.in lintian-2.89.0ubuntu1/t/recipes/checks/languages/python/scripts/python-script-uses-unversioned-python-in-shebang/build-spec/debian/control.in --- lintian-2.93.0/t/recipes/checks/languages/python/scripts/python-script-uses-unversioned-python-in-shebang/build-spec/debian/control.in 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/languages/python/scripts/python-script-uses-unversioned-python-in-shebang/build-spec/debian/control.in 2020-08-10 09:59:45.000000000 +0000 @@ -8,7 +8,7 @@ Package: prog-[% $source %] Architecture: [% $package_architecture %] -Depends: ${misc:Depends}, ${python3:Depends} +Depends: ${misc:Depends}, python, python2.7 Description: Package with Python script with bad shebang This is a test package designed to exercise some feature or tag of Lintian. It is part of the Lintian test suite and may do very odd diff -Nru lintian-2.93.0/t/recipes/checks/languages/python/scripts/python-script-uses-unversioned-python-in-shebang/build-spec/debian/script-good1 lintian-2.89.0ubuntu1/t/recipes/checks/languages/python/scripts/python-script-uses-unversioned-python-in-shebang/build-spec/debian/script-good1 --- lintian-2.93.0/t/recipes/checks/languages/python/scripts/python-script-uses-unversioned-python-in-shebang/build-spec/debian/script-good1 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/languages/python/scripts/python-script-uses-unversioned-python-in-shebang/build-spec/debian/script-good1 2020-08-10 09:59:45.000000000 +0000 @@ -1 +1 @@ -#!/usr/bin/env python3 +#!/usr/bin/env python2 diff -Nru lintian-2.93.0/t/recipes/checks/languages/python/scripts/python-script-uses-unversioned-python-in-shebang/build-spec/debian/script-good2 lintian-2.89.0ubuntu1/t/recipes/checks/languages/python/scripts/python-script-uses-unversioned-python-in-shebang/build-spec/debian/script-good2 --- lintian-2.93.0/t/recipes/checks/languages/python/scripts/python-script-uses-unversioned-python-in-shebang/build-spec/debian/script-good2 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/languages/python/scripts/python-script-uses-unversioned-python-in-shebang/build-spec/debian/script-good2 2020-08-10 09:59:45.000000000 +0000 @@ -1 +1 @@ -#!/usr/bin/python3 +#!/usr/bin/python2.7 diff -Nru lintian-2.93.0/t/recipes/checks/languages/r/site-library/lacks-depends-on-r-api/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/languages/r/site-library/lacks-depends-on-r-api/eval/desc --- lintian-2.93.0/t/recipes/checks/languages/r/site-library/lacks-depends-on-r-api/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/languages/r/site-library/lacks-depends-on-r-api/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -1,4 +1,4 @@ Testname: lacks-depends-on-r-api Check: languages/r/site-library -See-Also: +Reference: https://wiki.debian.org/Teams/r-pkg-team diff -Nru lintian-2.93.0/t/recipes/checks/lintian/override-context-mismatch/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/lintian/override-context-mismatch/eval/desc --- lintian-2.93.0/t/recipes/checks/lintian/override-context-mismatch/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/lintian/override-context-mismatch/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -1,3 +1,3 @@ Testname: override-context-mismatch Check: lintian -Default-Lintian-Options: --pedantic --display-info --display-experimental --display-level +classification --show-overrides --check-part fields/style,lintian +Default-Lintian-Options: --pedantic --display-info --display-experimental --display-level +classification --check-part fields/style,lintian diff -Nru lintian-2.93.0/t/recipes/checks/lintian/override-not-used/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/lintian/override-not-used/eval/desc --- lintian-2.93.0/t/recipes/checks/lintian/override-not-used/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/lintian/override-not-used/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -1,3 +1,3 @@ Testname: override-not-used Check: lintian -Default-Lintian-Options: --pedantic --display-info --display-experimental --display-level +classification --show-overrides --check-part fields/style,lintian +Default-Lintian-Options: --pedantic --display-info --display-experimental --display-level +classification --check-part fields/style,lintian diff -Nru lintian-2.93.0/t/recipes/checks/maintainer-scripts/generated/scripts-control-interpreters/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/maintainer-scripts/generated/scripts-control-interpreters/eval/desc --- lintian-2.93.0/t/recipes/checks/maintainer-scripts/generated/scripts-control-interpreters/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/maintainer-scripts/generated/scripts-control-interpreters/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -1,3 +1,3 @@ Testname: scripts-control-interpreters -See-Also: Debian Bug#508307 +References: Debian Bug#508307 Check: maintainer-scripts/generated diff -Nru lintian-2.93.0/t/recipes/checks/maintainer-scripts/generated/scripts-maintainer-general/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/maintainer-scripts/generated/scripts-maintainer-general/eval/desc --- lintian-2.93.0/t/recipes/checks/maintainer-scripts/generated/scripts-maintainer-general/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/maintainer-scripts/generated/scripts-maintainer-general/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -1,4 +1,4 @@ Testname: scripts-maintainer-general Profile: ubuntu/main -See-Also: Debian Bug#532984 +References: Debian Bug#532984 Check: maintainer-scripts/generated diff -Nru lintian-2.93.0/t/recipes/checks/menu-format/menu-format-desktop-general/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/menu-format/menu-format-desktop-general/eval/desc --- lintian-2.93.0/t/recipes/checks/menu-format/menu-format-desktop-general/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/menu-format/menu-format-desktop-general/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -1,3 +1,3 @@ Testname: menu-format-desktop-general -See-Also: Debian Bug#537737 +References: Debian Bug#537737 Check: menu-format diff -Nru lintian-2.93.0/t/recipes/checks/menu-format/menu-format-desktop-mimetype/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/menu-format/menu-format-desktop-mimetype/eval/desc --- lintian-2.93.0/t/recipes/checks/menu-format/menu-format-desktop-mimetype/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/menu-format/menu-format-desktop-mimetype/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -1,3 +1,3 @@ Testname: menu-format-desktop-mimetype -See-Also: Debian Bug#488832, Debian Bug#525133, #757383, #760677 +References: Debian Bug#488832, Debian Bug#525133, #757383, #760677 Check: menu-format diff -Nru lintian-2.93.0/t/recipes/checks/menus/menus-doc-base-general/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/menus/menus-doc-base-general/eval/desc --- lintian-2.93.0/t/recipes/checks/menus/menus-doc-base-general/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/menus/menus-doc-base-general/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -1,4 +1,4 @@ Testname: menus-doc-base-general Test-Against: doc-base-unknown-section -See-Also: Debian Bug#495836 +References: Debian Bug#495836 Check: menus diff -Nru lintian-2.93.0/t/recipes/checks/nmu/nmu-case-insensitive/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/nmu/nmu-case-insensitive/eval/desc --- lintian-2.93.0/t/recipes/checks/nmu/nmu-case-insensitive/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/nmu/nmu-case-insensitive/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -2,5 +2,5 @@ Test-Against: no-nmu-in-changelog source-nmu-has-incorrect-version-number -See-Also: Debian Bug#486795 +References: Debian Bug#486795 Check: nmu diff -Nru lintian-2.93.0/t/recipes/checks/nmu/nmu-local-changelog/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/nmu/nmu-local-changelog/eval/desc --- lintian-2.93.0/t/recipes/checks/nmu/nmu-local-changelog/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/nmu/nmu-local-changelog/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -2,5 +2,5 @@ Test-Against: no-nmu-in-changelog source-nmu-has-incorrect-version-number -See-Also: Debian Bug#501523 +References: Debian Bug#501523 Check: nmu diff -Nru lintian-2.93.0/t/recipes/checks/nmu/nmu-local-version/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/nmu/nmu-local-version/eval/desc --- lintian-2.93.0/t/recipes/checks/nmu/nmu-local-version/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/nmu/nmu-local-version/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -2,5 +2,5 @@ Test-Against: no-nmu-in-changelog source-nmu-has-incorrect-version-number -See-Also: Debian Bug#501523 +References: Debian Bug#501523 Check: nmu diff -Nru lintian-2.93.0/t/recipes/checks/nmu/nmu-ubuntu-native/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/nmu/nmu-ubuntu-native/eval/desc --- lintian-2.93.0/t/recipes/checks/nmu/nmu-ubuntu-native/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/nmu/nmu-ubuntu-native/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -1,5 +1,5 @@ Testname: nmu-ubuntu-native Profile: ubuntu/main Test-Against: no-nmu-in-changelog -See-Also: Debian Bug #507740 +References: Debian Bug #507740 Check: nmu diff -Nru lintian-2.93.0/t/recipes/checks/scripts/bash-completion-with-hashbang/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/scripts/bash-completion-with-hashbang/eval/desc --- lintian-2.93.0/t/recipes/checks/scripts/bash-completion-with-hashbang/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/scripts/bash-completion-with-hashbang/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -1,3 +1,3 @@ Testname: bash-completion-with-hashbang Check: scripts -See-Also: https://salsa.debian.org/lintian/lintian/-/merge_requests/292#note_139494 +References: https://salsa.debian.org/lintian/lintian/-/merge_requests/292#note_139494 diff -Nru lintian-2.93.0/t/recipes/checks/scripts/legacy-scripts/build-spec/debian/rules lintian-2.89.0ubuntu1/t/recipes/checks/scripts/legacy-scripts/build-spec/debian/rules --- lintian-2.93.0/t/recipes/checks/scripts/legacy-scripts/build-spec/debian/rules 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/scripts/legacy-scripts/build-spec/debian/rules 2020-08-10 09:59:45.000000000 +0000 @@ -29,12 +29,12 @@ install -m 755 fish-foo $(tmp)/etc/fish.d/ install -m 755 jruby-broken $(tmp)/usr/bin/ install -m 755 pyfoo $(tmp)/usr/bin/ - install -m 755 py3.Xfoo $(tmp)/usr/bin/ + install -m 755 py2.Xfoo $(tmp)/usr/bin/ # This uses "env" and should trigger script-in-usr-share-doc - install -m 755 py3.Xfoo $(tmp)/usr/share/doc/scripts/ - install -m 755 py3foo $(tmp)/usr/bin/ + install -m 755 py2.Xfoo $(tmp)/usr/share/doc/scripts/ + install -m 755 py2foo $(tmp)/usr/bin/ # This uses "env" and should trigger script-in-usr-share-doc - install -m 755 py3foo $(tmp)/usr/share/doc/scripts/ + install -m 755 py2foo $(tmp)/usr/share/doc/scripts/ install -m 755 perlfoo $(tmp)/usr/bin/ install -m 755 rubyfoo $(tmp)/usr/bin/ # This doesn't use "env" but should also trigger script-in-usr-share-doc diff -Nru lintian-2.93.0/t/recipes/checks/scripts/legacy-scripts/build-spec/orig/py2foo lintian-2.89.0ubuntu1/t/recipes/checks/scripts/legacy-scripts/build-spec/orig/py2foo --- lintian-2.93.0/t/recipes/checks/scripts/legacy-scripts/build-spec/orig/py2foo 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/scripts/legacy-scripts/build-spec/orig/py2foo 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,4 @@ +#! /usr/bin/env python2 + +if __name__ == '__main__': + print 'Hi there' diff -Nru lintian-2.93.0/t/recipes/checks/scripts/legacy-scripts/build-spec/orig/py2.Xfoo lintian-2.89.0ubuntu1/t/recipes/checks/scripts/legacy-scripts/build-spec/orig/py2.Xfoo --- lintian-2.93.0/t/recipes/checks/scripts/legacy-scripts/build-spec/orig/py2.Xfoo 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/scripts/legacy-scripts/build-spec/orig/py2.Xfoo 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,4 @@ +#! /usr/bin/env python2.2 + +if __name__ == '__main__': + print 'Hi there' diff -Nru lintian-2.93.0/t/recipes/checks/scripts/legacy-scripts/build-spec/orig/py3foo lintian-2.89.0ubuntu1/t/recipes/checks/scripts/legacy-scripts/build-spec/orig/py3foo --- lintian-2.93.0/t/recipes/checks/scripts/legacy-scripts/build-spec/orig/py3foo 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/scripts/legacy-scripts/build-spec/orig/py3foo 1970-01-01 00:00:00.000000000 +0000 @@ -1,4 +0,0 @@ -#! /usr/bin/env python3 - -if __name__ == '__main__': - print 'Hi there' diff -Nru lintian-2.93.0/t/recipes/checks/scripts/legacy-scripts/build-spec/orig/py3.Xfoo lintian-2.89.0ubuntu1/t/recipes/checks/scripts/legacy-scripts/build-spec/orig/py3.Xfoo --- lintian-2.93.0/t/recipes/checks/scripts/legacy-scripts/build-spec/orig/py3.Xfoo 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/scripts/legacy-scripts/build-spec/orig/py3.Xfoo 1970-01-01 00:00:00.000000000 +0000 @@ -1,4 +0,0 @@ -#! /usr/bin/env python3.7 - -if __name__ == '__main__': - print 'Hi there' diff -Nru lintian-2.93.0/t/recipes/checks/scripts/legacy-scripts/eval/tags lintian-2.89.0ubuntu1/t/recipes/checks/scripts/legacy-scripts/eval/tags --- lintian-2.93.0/t/recipes/checks/scripts/legacy-scripts/eval/tags 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/scripts/legacy-scripts/eval/tags 2020-08-10 09:59:45.000000000 +0000 @@ -5,14 +5,14 @@ scripts (binary): script-without-interpreter control/prerm scripts (binary): script-uses-bin-env usr/bin/envfoo scripts (binary): python-script-but-no-python-dep usr/bin/pyfoo #!python -scripts (binary): python-script-but-no-python-dep usr/bin/py3.Xfoo #!python3.7 +scripts (binary): python-script-but-no-python-dep usr/bin/py2.Xfoo #!python2.2 scripts (binary): php-script-with-unusual-interpreter usr/share/scripts/php7.0foo /usr/bin/php7.0 scripts (binary): php-script-with-unusual-interpreter usr/share/scripts/php7.0envfoo php7.0 scripts (binary): php-script-but-no-php-cli-dep usr/share/scripts/phpfoo #!/usr/bin/php scripts (binary): php-script-but-no-php-cli-dep usr/share/scripts/phpenvfoo #!php scripts (binary): php-script-but-no-php-cli-dep usr/share/scripts/php7.0foo #!/usr/bin/php7.0 scripts (binary): php-script-but-no-php-cli-dep usr/share/scripts/php7.0envfoo #!php7.0 -scripts (binary): missing-dep-for-interpreter python3 => python3:any | python3-minimal:any (usr/bin/py3foo) #!python3 +scripts (binary): missing-dep-for-interpreter python2 => python:any | python-minimal:any | python2:any | python2-minimal:any (usr/bin/py2foo) #!python2 scripts (binary): missing-dep-for-interpreter lefty => graphviz (usr/bin/lefty-foo) #!/usr/local/bin/lefty scripts (binary): missing-dep-for-interpreter jruby => jruby | jruby1.0 | jruby1.1 | jruby1.2 (usr/bin/jruby-broken) #!/usr/bin/jruby scripts (binary): maintainer-script-without-set-e postrm diff -Nru lintian-2.93.0/t/recipes/checks/scripts/scripts-calls-init-script/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/scripts/scripts-calls-init-script/eval/desc --- lintian-2.93.0/t/recipes/checks/scripts/scripts-calls-init-script/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/scripts/scripts-calls-init-script/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -1,3 +1,3 @@ Testname: scripts-calls-init-script -See-Also: Debian Bug#381485 +References: Debian Bug#381485 Check: scripts diff -Nru lintian-2.93.0/t/recipes/checks/scripts/scripts-control-interpreters/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/scripts/scripts-control-interpreters/eval/desc --- lintian-2.93.0/t/recipes/checks/scripts/scripts-control-interpreters/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/scripts/scripts-control-interpreters/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -1,3 +1,3 @@ Testname: scripts-control-interpreters -See-Also: Debian Bug#508307 +References: Debian Bug#508307 Check: scripts diff -Nru lintian-2.93.0/t/recipes/checks/scripts/scripts-interpreters/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/scripts/scripts-interpreters/eval/desc --- lintian-2.93.0/t/recipes/checks/scripts/scripts-interpreters/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/scripts/scripts-interpreters/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -1,3 +1,3 @@ Testname: scripts-interpreters -See-Also: Debian Bug#543873 +References: Debian Bug#543873 Check: scripts diff -Nru lintian-2.93.0/t/recipes/checks/scripts/scripts-maintainer-general/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/scripts/scripts-maintainer-general/eval/desc --- lintian-2.93.0/t/recipes/checks/scripts/scripts-maintainer-general/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/scripts/scripts-maintainer-general/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -1,4 +1,4 @@ Testname: scripts-maintainer-general Profile: ubuntu/main -See-Also: Debian Bug#532984 +References: Debian Bug#532984 Check: scripts diff -Nru lintian-2.93.0/t/recipes/checks/scripts/scripts-ocamlrun/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/scripts/scripts-ocamlrun/eval/desc --- lintian-2.93.0/t/recipes/checks/scripts/scripts-ocamlrun/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/scripts/scripts-ocamlrun/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -1,4 +1,4 @@ Testname: scripts-ocamlrun Test-Against: missing-dep-for-interpreter -See-Also: Debian Bug#495431 +References: Debian Bug#495431 Check: scripts diff -Nru lintian-2.93.0/t/recipes/checks/shared-libs/shared-libs-unversioned/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/shared-libs/shared-libs-unversioned/eval/desc --- lintian-2.93.0/t/recipes/checks/shared-libs/shared-libs-unversioned/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/shared-libs/shared-libs-unversioned/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -1,5 +1,5 @@ Testname: shared-libs-unversioned Test-Against: ships-undeclared-shared-library -See-Also: Debian Bug#506673 +References: Debian Bug#506673 Check: shared-libs diff -Nru lintian-2.93.0/t/recipes/checks/upstream-signature/doubly-armored-signature/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/upstream-signature/doubly-armored-signature/eval/desc --- lintian-2.93.0/t/recipes/checks/upstream-signature/doubly-armored-signature/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/upstream-signature/doubly-armored-signature/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -1,3 +1,3 @@ Testname: doubly-armored-signature Check: upstream-signature -See-Also: Debian #929436, https://lists.debian.org/debian-devel/2019/04/msg00459.html +Reference: Debian #929436, https://lists.debian.org/debian-devel/2019/04/msg00459.html diff -Nru lintian-2.93.0/t/recipes/checks/upstream-signature/explicit-armor-header/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/upstream-signature/explicit-armor-header/eval/desc --- lintian-2.93.0/t/recipes/checks/upstream-signature/explicit-armor-header/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/upstream-signature/explicit-armor-header/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -1,3 +1,3 @@ Testname: explicit-armor-header Check: upstream-signature -See-Also: Debian #929436, https://lists.debian.org/debian-devel/2019/04/msg00459.html +Reference: Debian #929436, https://lists.debian.org/debian-devel/2019/04/msg00459.html diff -Nru lintian-2.93.0/t/recipes/checks/upstream-signature/repeated-signature/eval/desc lintian-2.89.0ubuntu1/t/recipes/checks/upstream-signature/repeated-signature/eval/desc --- lintian-2.93.0/t/recipes/checks/upstream-signature/repeated-signature/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/checks/upstream-signature/repeated-signature/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -1,3 +1,3 @@ Testname: repeated-signature Check: upstream-signature -See-Also: Debian #929436, https://lists.debian.org/debian-devel/2019/04/msg00459.html +Reference: Debian #929436, https://lists.debian.org/debian-devel/2019/04/msg00459.html diff -Nru lintian-2.93.0/t/recipes/lintian-features/html-output/eval/post-test lintian-2.89.0ubuntu1/t/recipes/lintian-features/html-output/eval/post-test --- lintian-2.93.0/t/recipes/lintian-features/html-output/eval/post-test 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/lintian-features/html-output/eval/post-test 2020-08-10 09:59:45.000000000 +0000 @@ -1,3 +1,4 @@ /Produced by Lintian version/ d /The run started/ d +s/(lintian\.debian\.org\/)[^/]*\//\1/ s/_[[:alnum:]]+\.(changes|buildinfo)/\.\1/ diff -Nru lintian-2.93.0/t/recipes/lintian-features/lintian-color-html/build-spec/debian/docs lintian-2.89.0ubuntu1/t/recipes/lintian-features/lintian-color-html/build-spec/debian/docs --- lintian-2.93.0/t/recipes/lintian-features/lintian-color-html/build-spec/debian/docs 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/lintian-features/lintian-color-html/build-spec/debian/docs 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1 @@ +foo.xml diff -Nru lintian-2.93.0/t/recipes/lintian-features/lintian-color-html/build-spec/fill-values lintian-2.89.0ubuntu1/t/recipes/lintian-features/lintian-color-html/build-spec/fill-values --- lintian-2.93.0/t/recipes/lintian-features/lintian-color-html/build-spec/fill-values 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/lintian-features/lintian-color-html/build-spec/fill-values 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,3 @@ +Testname: lintian-color-html +Skeleton: upload-non-native +Description: Test Lintian --color=html output escaping diff -Nru lintian-2.93.0/t/recipes/lintian-features/lintian-color-html/build-spec/orig/foo.xml lintian-2.89.0ubuntu1/t/recipes/lintian-features/lintian-color-html/build-spec/orig/foo.xml --- lintian-2.93.0/t/recipes/lintian-features/lintian-color-html/build-spec/orig/foo.xml 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/lintian-features/lintian-color-html/build-spec/orig/foo.xml 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1 @@ + diff -Nru lintian-2.93.0/t/recipes/lintian-features/lintian-color-html/eval/desc lintian-2.89.0ubuntu1/t/recipes/lintian-features/lintian-color-html/eval/desc --- lintian-2.93.0/t/recipes/lintian-features/lintian-color-html/eval/desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/lintian-features/lintian-color-html/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,5 @@ +Testname: lintian-color-html +Options: --color=html --show-overrides +Match-Strategy: literal +Output-Format: EWI +Default-Lintian-Options: --pedantic --display-info --display-experimental diff -Nru lintian-2.93.0/t/recipes/lintian-features/lintian-color-html/eval/literal lintian-2.89.0ubuntu1/t/recipes/lintian-features/lintian-color-html/eval/literal --- lintian-2.93.0/t/recipes/lintian-features/lintian-color-html/eval/literal 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/lintian-features/lintian-color-html/eval/literal 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,4 @@ +W: lintian-color-html: privacy-breach-generic usr/share/doc/lintian-color-html/foo.xml [<img src="http://1984.ow/bigbrotheriswatchingyou.png" />] (http://1984.ow/bigbrotheriswatchingyou.png) +I: lintian-color-html source: upstream-metadata-missing-bug-tracking +I: lintian-color-html source: upstream-metadata-missing-repository +X: lintian-color-html source: debian-watch-does-not-check-gpg-signature diff -Nru lintian-2.93.0/t/recipes/lintian-features/lintian-output-colons/build-spec/debian/control.in lintian-2.89.0ubuntu1/t/recipes/lintian-features/lintian-output-colons/build-spec/debian/control.in --- lintian-2.93.0/t/recipes/lintian-features/lintian-output-colons/build-spec/debian/control.in 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/lintian-features/lintian-output-colons/build-spec/debian/control.in 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,20 @@ +Source: [% $source %] +Priority: optional +Section: [% $section %] +Maintainer: [% $author %] +Standards-Version: [% $standards_version %] +Build-Depends: [% $build_depends %] +Rules-Requires-Root: no + +Package: [% $source %] +Architecture: [% $package_architecture %] +Depends: ${misc:Depends}, libssl0.9.8 (>= 0abcd) +Essential:yes +Section: [% $section %] +Description: [% $description %]. + This is a test package designed to exercise some feature or tag of + Lintian. It is part of the Lintian test suite and may do very odd + things. It should not be installed like a regular package. It may + be an empty package. + . + The homepage is http://www.example.com/. diff -Nru lintian-2.93.0/t/recipes/lintian-features/lintian-output-colons/build-spec/debian/dirs lintian-2.89.0ubuntu1/t/recipes/lintian-features/lintian-output-colons/build-spec/debian/dirs --- lintian-2.93.0/t/recipes/lintian-features/lintian-output-colons/build-spec/debian/dirs 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/lintian-features/lintian-output-colons/build-spec/debian/dirs 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,2 @@ +usr/local/share/lintian +var/lock/lintian diff -Nru lintian-2.93.0/t/recipes/lintian-features/lintian-output-colons/build-spec/debian/examples lintian-2.89.0ubuntu1/t/recipes/lintian-features/lintian-output-colons/build-spec/debian/examples --- lintian-2.93.0/t/recipes/lintian-features/lintian-output-colons/build-spec/debian/examples 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/lintian-features/lintian-output-colons/build-spec/debian/examples 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1 @@ +example diff -Nru lintian-2.93.0/t/recipes/lintian-features/lintian-output-colons/build-spec/debian/install lintian-2.89.0ubuntu1/t/recipes/lintian-features/lintian-output-colons/build-spec/debian/install --- lintian-2.93.0/t/recipes/lintian-features/lintian-output-colons/build-spec/debian/install 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/lintian-features/lintian-output-colons/build-spec/debian/install 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,2 @@ +script usr/bin +script.desktop usr/share/applications diff -Nru lintian-2.93.0/t/recipes/lintian-features/lintian-output-colons/build-spec/debian/rules lintian-2.89.0ubuntu1/t/recipes/lintian-features/lintian-output-colons/build-spec/debian/rules --- lintian-2.93.0/t/recipes/lintian-features/lintian-output-colons/build-spec/debian/rules 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/lintian-features/lintian-output-colons/build-spec/debian/rules 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,5 @@ +#!/usr/bin/make -f +%: + dh $@ + +override_dh_usrlocal: diff -Nru lintian-2.93.0/t/recipes/lintian-features/lintian-output-colons/build-spec/debian/source.lintian-overrides lintian-2.89.0ubuntu1/t/recipes/lintian-features/lintian-output-colons/build-spec/debian/source.lintian-overrides --- lintian-2.93.0/t/recipes/lintian-features/lintian-output-colons/build-spec/debian/source.lintian-overrides 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/lintian-features/lintian-output-colons/build-spec/debian/source.lintian-overrides 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1 @@ +lintian-output-colons source: dfsg-version-misspelled 1.0* diff -Nru lintian-2.93.0/t/recipes/lintian-features/lintian-output-colons/build-spec/diff/Changes lintian-2.89.0ubuntu1/t/recipes/lintian-features/lintian-output-colons/build-spec/diff/Changes --- lintian-2.93.0/t/recipes/lintian-features/lintian-output-colons/build-spec/diff/Changes 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/lintian-features/lintian-output-colons/build-spec/diff/Changes 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1 @@ +This is unlike any other dummy changelog. diff -Nru lintian-2.93.0/t/recipes/lintian-features/lintian-output-colons/build-spec/fill-values lintian-2.89.0ubuntu1/t/recipes/lintian-features/lintian-output-colons/build-spec/fill-values --- lintian-2.93.0/t/recipes/lintian-features/lintian-output-colons/build-spec/fill-values 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/lintian-features/lintian-output-colons/build-spec/fill-values 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,5 @@ +Testname: lintian-output-colons +Skeleton: upload-non-native +Version: 1.0+dsfg-1.1 +Package-Architecture: all +Description: Test Lintian colon-separated output format diff -Nru lintian-2.93.0/t/recipes/lintian-features/lintian-output-colons/build-spec/orig/example lintian-2.89.0ubuntu1/t/recipes/lintian-features/lintian-output-colons/build-spec/orig/example --- lintian-2.93.0/t/recipes/lintian-features/lintian-output-colons/build-spec/orig/example 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/lintian-features/lintian-output-colons/build-spec/orig/example 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,2 @@ +#!/usr/bin/foo +echo This is some example. diff -Nru lintian-2.93.0/t/recipes/lintian-features/lintian-output-colons/build-spec/orig/script lintian-2.89.0ubuntu1/t/recipes/lintian-features/lintian-output-colons/build-spec/orig/script --- lintian-2.93.0/t/recipes/lintian-features/lintian-output-colons/build-spec/orig/script 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/lintian-features/lintian-output-colons/build-spec/orig/script 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,3 @@ +#!/bin/sh +. /usr/share/debconf/confmodule +echo 'Hello world' diff -Nru lintian-2.93.0/t/recipes/lintian-features/lintian-output-colons/build-spec/orig/script.desktop lintian-2.89.0ubuntu1/t/recipes/lintian-features/lintian-output-colons/build-spec/orig/script.desktop --- lintian-2.93.0/t/recipes/lintian-features/lintian-output-colons/build-spec/orig/script.desktop 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/lintian-features/lintian-output-colons/build-spec/orig/script.desktop 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +[Desktop Entry] +Name=script +Type=Application +Comment=Incorrectly limited to particular environments +Categories=Development; +Exec=script +OnlyShowIn=GNOME;KDE; +Icon=foo +Keywords=Lintian diff -Nru lintian-2.93.0/t/recipes/lintian-features/lintian-output-colons/eval/desc lintian-2.89.0ubuntu1/t/recipes/lintian-features/lintian-output-colons/eval/desc --- lintian-2.93.0/t/recipes/lintian-features/lintian-output-colons/eval/desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/lintian-features/lintian-output-colons/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,5 @@ +Testname: lintian-output-colons +Options: --show-overrides +Output-Format: colons +Match-Strategy: literal +Default-Lintian-Options: --pedantic --display-info --display-experimental diff -Nru lintian-2.93.0/t/recipes/lintian-features/lintian-output-colons/eval/literal lintian-2.89.0ubuntu1/t/recipes/lintian-features/lintian-output-colons/eval/literal --- lintian-2.93.0/t/recipes/lintian-features/lintian-output-colons/eval/literal 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/lintian-features/lintian-output-colons/eval/literal 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,24 @@ +tag:E:error::lintian-output-colons:1.0+dsfg-1.1:all:binary:dir-in-usr-local:usr/local/share/: +tag:E:error::lintian-output-colons:1.0+dsfg-1.1:all:binary:dir-in-usr-local:usr/local/share/lintian/: +tag:E:error::lintian-output-colons:1.0+dsfg-1.1:all:binary:dir-or-file-in-var-lock:var/lock/lintian/: +tag:E:error::lintian-output-colons:1.0+dsfg-1.1:all:binary:new-essential-package:: +tag:E:error::lintian-output-colons:1.0+dsfg-1.1:all:binary:possible-gpl-code-linked-with-openssl:: +tag:W:warning::lintian-output-colons:1.0+dsfg-1.1:source:source:changelog-file-missing-explicit-entry:0.0.1-1 -> 1.0+dsfg-1 (missing) -> 1.0+dsfg-1.1: +tag:W:warning::lintian-output-colons:1.0+dsfg-1.1:source:source:format-3.0-but-debian-changes-patch:: +tag:W:warning::lintian-output-colons:1.0+dsfg-1.1:source:source:maintainer-upload-has-incorrect-version-number:1.0+dsfg-1.1: +tag:W:warning::lintian-output-colons:1.0+dsfg-1.1:all:binary:no-manual-page:usr/bin/script: +tag:I:info::lintian-output-colons:1.0+dsfg-1.1:source:source:binary-control-field-duplicates-source:field "Section" in package lintian-output-colons: +tag:I:info::lintian-output-colons:1.0+dsfg-1.1:all:binary:description-possibly-contains-homepage:http\://www.example.com/.: +tag:I:info::lintian-output-colons:1.0+dsfg-1.1:all:binary:desktop-entry-limited-to-environments:usr/share/applications/script.desktop: +tag:I:info::lintian-output-colons:1.0+dsfg-1.1:all:binary:package-contains-empty-directory:usr/local/share/lintian/: +tag:I:info::lintian-output-colons:1.0+dsfg-1.1:source:source:patch-not-forwarded-upstream:debian/patches/debian-changes-1.0+dsfg-1.1: +tag:I:info::lintian-output-colons:1.0+dsfg-1.1:source:source:quilt-patch-using-template-description:debian-changes-1.0+dsfg-1.1: +tag:I:info::lintian-output-colons:1.0+dsfg-1.1:all:binary:synopsis-is-a-sentence:"Test Lintian colon-separated output format.": +tag:I:info::lintian-output-colons:1.0+dsfg-1.1:source:source:upstream-metadata-missing-bug-tracking:: +tag:I:info::lintian-output-colons:1.0+dsfg-1.1:source:source:upstream-metadata-missing-repository:: +tag:P:pedantic::lintian-output-colons:1.0+dsfg-1.1:source:source:debian-control-has-unusual-field-spacing:line 12: +tag:P:pedantic:X:lintian-output-colons:1.0+dsfg-1.1:source:source:debian-watch-does-not-check-gpg-signature:: +tag:P:pedantic::lintian-output-colons:1.0+dsfg-1.1:all:binary:example-unusual-interpreter:usr/share/doc/lintian-output-colons/examples/example #!/usr/bin/foo: +tag:P:pedantic::lintian-output-colons:1.0+dsfg-1.1:source:source:no-homepage-field:: +tag:P:pedantic::lintian-output-colons:1.0+dsfg-1.1:source:source:old-source-override-location:: +tag:W:warning:O:lintian-output-colons:1.0+dsfg-1.1:source:source:dfsg-version-misspelled:1.0+dsfg-1.1:dfsg-version-misspelled 1.0* diff -Nru lintian-2.93.0/t/recipes/lintian-features/lintian-output-fullewi/build-spec/debian/control.in lintian-2.89.0ubuntu1/t/recipes/lintian-features/lintian-output-fullewi/build-spec/debian/control.in --- lintian-2.93.0/t/recipes/lintian-features/lintian-output-fullewi/build-spec/debian/control.in 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/lintian-features/lintian-output-fullewi/build-spec/debian/control.in 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,20 @@ +Source: [% $source %] +Priority: optional +Section: [% $section %] +Maintainer: [% $author %] +Standards-Version: [% $standards_version %] +Build-Depends: [% $build_depends %] +Rules-Requires-Root: no + +Package: [% $source %] +Architecture: [% $package_architecture %] +Depends: ${misc:Depends}, libssl0.9.8 (>= 0abcd) +Essential:yes +Section: [% $section %] +Description: [% $description %]. + This is a test package designed to exercise some feature or tag of + Lintian. It is part of the Lintian test suite and may do very odd + things. It should not be installed like a regular package. It may + be an empty package. + . + The homepage is http://www.example.com/. diff -Nru lintian-2.93.0/t/recipes/lintian-features/lintian-output-fullewi/build-spec/debian/dirs lintian-2.89.0ubuntu1/t/recipes/lintian-features/lintian-output-fullewi/build-spec/debian/dirs --- lintian-2.93.0/t/recipes/lintian-features/lintian-output-fullewi/build-spec/debian/dirs 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/lintian-features/lintian-output-fullewi/build-spec/debian/dirs 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,2 @@ +usr/local/share/lintian +var/lock/lintian diff -Nru lintian-2.93.0/t/recipes/lintian-features/lintian-output-fullewi/build-spec/debian/examples lintian-2.89.0ubuntu1/t/recipes/lintian-features/lintian-output-fullewi/build-spec/debian/examples --- lintian-2.93.0/t/recipes/lintian-features/lintian-output-fullewi/build-spec/debian/examples 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/lintian-features/lintian-output-fullewi/build-spec/debian/examples 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1 @@ +example diff -Nru lintian-2.93.0/t/recipes/lintian-features/lintian-output-fullewi/build-spec/debian/install lintian-2.89.0ubuntu1/t/recipes/lintian-features/lintian-output-fullewi/build-spec/debian/install --- lintian-2.93.0/t/recipes/lintian-features/lintian-output-fullewi/build-spec/debian/install 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/lintian-features/lintian-output-fullewi/build-spec/debian/install 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,2 @@ +script usr/bin +script.desktop usr/share/applications diff -Nru lintian-2.93.0/t/recipes/lintian-features/lintian-output-fullewi/build-spec/debian/rules lintian-2.89.0ubuntu1/t/recipes/lintian-features/lintian-output-fullewi/build-spec/debian/rules --- lintian-2.93.0/t/recipes/lintian-features/lintian-output-fullewi/build-spec/debian/rules 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/lintian-features/lintian-output-fullewi/build-spec/debian/rules 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,5 @@ +#!/usr/bin/make -f +%: + dh $@ + +override_dh_usrlocal: diff -Nru lintian-2.93.0/t/recipes/lintian-features/lintian-output-fullewi/build-spec/debian/source.lintian-overrides lintian-2.89.0ubuntu1/t/recipes/lintian-features/lintian-output-fullewi/build-spec/debian/source.lintian-overrides --- lintian-2.93.0/t/recipes/lintian-features/lintian-output-fullewi/build-spec/debian/source.lintian-overrides 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/lintian-features/lintian-output-fullewi/build-spec/debian/source.lintian-overrides 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1 @@ +lintian-output-colons source: dfsg-version-misspelled 1.0* diff -Nru lintian-2.93.0/t/recipes/lintian-features/lintian-output-fullewi/build-spec/diff/Changes lintian-2.89.0ubuntu1/t/recipes/lintian-features/lintian-output-fullewi/build-spec/diff/Changes --- lintian-2.93.0/t/recipes/lintian-features/lintian-output-fullewi/build-spec/diff/Changes 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/lintian-features/lintian-output-fullewi/build-spec/diff/Changes 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1 @@ +This is unlike any other dummy changelog. diff -Nru lintian-2.93.0/t/recipes/lintian-features/lintian-output-fullewi/build-spec/fill-values lintian-2.89.0ubuntu1/t/recipes/lintian-features/lintian-output-fullewi/build-spec/fill-values --- lintian-2.93.0/t/recipes/lintian-features/lintian-output-fullewi/build-spec/fill-values 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/lintian-features/lintian-output-fullewi/build-spec/fill-values 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,5 @@ +Testname: lintian-output-fullewi +Skeleton: upload-non-native +Version: 1.0+dsfg-1.1 +Package-Architecture: all +Description: Test Lintian's 'fullewi' output format diff -Nru lintian-2.93.0/t/recipes/lintian-features/lintian-output-fullewi/build-spec/orig/example lintian-2.89.0ubuntu1/t/recipes/lintian-features/lintian-output-fullewi/build-spec/orig/example --- lintian-2.93.0/t/recipes/lintian-features/lintian-output-fullewi/build-spec/orig/example 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/lintian-features/lintian-output-fullewi/build-spec/orig/example 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,2 @@ +#!/usr/bin/foo +echo This is some example. diff -Nru lintian-2.93.0/t/recipes/lintian-features/lintian-output-fullewi/build-spec/orig/script lintian-2.89.0ubuntu1/t/recipes/lintian-features/lintian-output-fullewi/build-spec/orig/script --- lintian-2.93.0/t/recipes/lintian-features/lintian-output-fullewi/build-spec/orig/script 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/lintian-features/lintian-output-fullewi/build-spec/orig/script 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,3 @@ +#!/bin/sh +. /usr/share/debconf/confmodule +echo 'Hello world' diff -Nru lintian-2.93.0/t/recipes/lintian-features/lintian-output-fullewi/build-spec/orig/script.desktop lintian-2.89.0ubuntu1/t/recipes/lintian-features/lintian-output-fullewi/build-spec/orig/script.desktop --- lintian-2.93.0/t/recipes/lintian-features/lintian-output-fullewi/build-spec/orig/script.desktop 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/lintian-features/lintian-output-fullewi/build-spec/orig/script.desktop 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +[Desktop Entry] +Name=script +Type=Application +Comment=Incorrectly limited to particular environments +Categories=Development; +Exec=script +OnlyShowIn=GNOME;KDE; +Icon=foo +Keywords=Lintian diff -Nru lintian-2.93.0/t/recipes/lintian-features/lintian-output-fullewi/eval/desc lintian-2.89.0ubuntu1/t/recipes/lintian-features/lintian-output-fullewi/eval/desc --- lintian-2.93.0/t/recipes/lintian-features/lintian-output-fullewi/eval/desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/lintian-features/lintian-output-fullewi/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,5 @@ +Testname: lintian-output-fullewi +Options: --show-overrides +Output-Format: fullewi +Match-Strategy: literal +Default-Lintian-Options: --pedantic --display-info --display-experimental diff -Nru lintian-2.93.0/t/recipes/lintian-features/lintian-output-fullewi/eval/literal lintian-2.89.0ubuntu1/t/recipes/lintian-features/lintian-output-fullewi/eval/literal --- lintian-2.93.0/t/recipes/lintian-features/lintian-output-fullewi/eval/literal 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/lintian-features/lintian-output-fullewi/eval/literal 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,24 @@ +E: lintian-output-fullewi binary (1.0+dsfg-1.1) [all]: dir-in-usr-local usr/local/share/ +E: lintian-output-fullewi binary (1.0+dsfg-1.1) [all]: dir-in-usr-local usr/local/share/lintian/ +E: lintian-output-fullewi binary (1.0+dsfg-1.1) [all]: dir-or-file-in-var-lock var/lock/lintian/ +E: lintian-output-fullewi binary (1.0+dsfg-1.1) [all]: new-essential-package +E: lintian-output-fullewi binary (1.0+dsfg-1.1) [all]: possible-gpl-code-linked-with-openssl +W: lintian-output-fullewi source (1.0+dsfg-1.1) [source]: changelog-file-missing-explicit-entry 0.0.1-1 -> 1.0+dsfg-1 (missing) -> 1.0+dsfg-1.1 +W: lintian-output-fullewi source (1.0+dsfg-1.1) [source]: dfsg-version-misspelled 1.0+dsfg-1.1 +W: lintian-output-fullewi source (1.0+dsfg-1.1) [source]: format-3.0-but-debian-changes-patch +W: lintian-output-fullewi source (1.0+dsfg-1.1) [source]: maintainer-upload-has-incorrect-version-number 1.0+dsfg-1.1 +W: lintian-output-fullewi binary (1.0+dsfg-1.1) [all]: no-manual-page usr/bin/script +I: lintian-output-fullewi source (1.0+dsfg-1.1) [source]: binary-control-field-duplicates-source field "Section" in package lintian-output-fullewi +I: lintian-output-fullewi binary (1.0+dsfg-1.1) [all]: description-possibly-contains-homepage http://www.example.com/. +I: lintian-output-fullewi binary (1.0+dsfg-1.1) [all]: desktop-entry-limited-to-environments usr/share/applications/script.desktop +I: lintian-output-fullewi binary (1.0+dsfg-1.1) [all]: package-contains-empty-directory usr/local/share/lintian/ +I: lintian-output-fullewi source (1.0+dsfg-1.1) [source]: patch-not-forwarded-upstream debian/patches/debian-changes-1.0+dsfg-1.1 +I: lintian-output-fullewi source (1.0+dsfg-1.1) [source]: quilt-patch-using-template-description debian-changes-1.0+dsfg-1.1 +I: lintian-output-fullewi binary (1.0+dsfg-1.1) [all]: synopsis-is-a-sentence "Test Lintian's 'fullewi' output format." +I: lintian-output-fullewi source (1.0+dsfg-1.1) [source]: upstream-metadata-missing-bug-tracking +I: lintian-output-fullewi source (1.0+dsfg-1.1) [source]: upstream-metadata-missing-repository +P: lintian-output-fullewi source (1.0+dsfg-1.1) [source]: debian-control-has-unusual-field-spacing line 12 +X: lintian-output-fullewi source (1.0+dsfg-1.1) [source]: debian-watch-does-not-check-gpg-signature +P: lintian-output-fullewi binary (1.0+dsfg-1.1) [all]: example-unusual-interpreter usr/share/doc/lintian-output-fullewi/examples/example #!/usr/bin/foo +P: lintian-output-fullewi source (1.0+dsfg-1.1) [source]: no-homepage-field +P: lintian-output-fullewi source (1.0+dsfg-1.1) [source]: old-source-override-location diff -Nru lintian-2.93.0/t/recipes/lintian-features/lintian-output-letter/build-spec/debian/control.in lintian-2.89.0ubuntu1/t/recipes/lintian-features/lintian-output-letter/build-spec/debian/control.in --- lintian-2.93.0/t/recipes/lintian-features/lintian-output-letter/build-spec/debian/control.in 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/lintian-features/lintian-output-letter/build-spec/debian/control.in 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,20 @@ +Source: [% $source %] +Priority: optional +Section: [% $section %] +Maintainer: [% $author %] +Standards-Version: [% $standards_version %] +Build-Depends: [% $build_depends %] +Rules-Requires-Root: no + +Package: [% $source %] +Architecture: [% $package_architecture %] +Depends: ${misc:Depends}, libssl0.9.8 (>= 0abcd) +Essential:yes +Section: [% $section %] +Description: [% $description %]. + This is a test package designed to exercise some feature or tag of + Lintian. It is part of the Lintian test suite and may do very odd + things. It should not be installed like a regular package. It may + be an empty package. + . + The homepage is http://www.example.com/. diff -Nru lintian-2.93.0/t/recipes/lintian-features/lintian-output-letter/build-spec/debian/dirs lintian-2.89.0ubuntu1/t/recipes/lintian-features/lintian-output-letter/build-spec/debian/dirs --- lintian-2.93.0/t/recipes/lintian-features/lintian-output-letter/build-spec/debian/dirs 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/lintian-features/lintian-output-letter/build-spec/debian/dirs 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,2 @@ +usr/local/share/lintian +var/lock/lintian diff -Nru lintian-2.93.0/t/recipes/lintian-features/lintian-output-letter/build-spec/debian/examples lintian-2.89.0ubuntu1/t/recipes/lintian-features/lintian-output-letter/build-spec/debian/examples --- lintian-2.93.0/t/recipes/lintian-features/lintian-output-letter/build-spec/debian/examples 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/lintian-features/lintian-output-letter/build-spec/debian/examples 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1 @@ +example diff -Nru lintian-2.93.0/t/recipes/lintian-features/lintian-output-letter/build-spec/debian/install lintian-2.89.0ubuntu1/t/recipes/lintian-features/lintian-output-letter/build-spec/debian/install --- lintian-2.93.0/t/recipes/lintian-features/lintian-output-letter/build-spec/debian/install 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/lintian-features/lintian-output-letter/build-spec/debian/install 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,2 @@ +script usr/bin +script.desktop usr/share/applications diff -Nru lintian-2.93.0/t/recipes/lintian-features/lintian-output-letter/build-spec/debian/rules lintian-2.89.0ubuntu1/t/recipes/lintian-features/lintian-output-letter/build-spec/debian/rules --- lintian-2.93.0/t/recipes/lintian-features/lintian-output-letter/build-spec/debian/rules 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/lintian-features/lintian-output-letter/build-spec/debian/rules 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,5 @@ +#!/usr/bin/make -f +%: + dh $@ + +override_dh_usrlocal: diff -Nru lintian-2.93.0/t/recipes/lintian-features/lintian-output-letter/build-spec/debian/source.lintian-overrides lintian-2.89.0ubuntu1/t/recipes/lintian-features/lintian-output-letter/build-spec/debian/source.lintian-overrides --- lintian-2.93.0/t/recipes/lintian-features/lintian-output-letter/build-spec/debian/source.lintian-overrides 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/lintian-features/lintian-output-letter/build-spec/debian/source.lintian-overrides 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1 @@ +lintian-output-letter source: dfsg-version-misspelled 1.0* diff -Nru lintian-2.93.0/t/recipes/lintian-features/lintian-output-letter/build-spec/diff/Changes lintian-2.89.0ubuntu1/t/recipes/lintian-features/lintian-output-letter/build-spec/diff/Changes --- lintian-2.93.0/t/recipes/lintian-features/lintian-output-letter/build-spec/diff/Changes 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/lintian-features/lintian-output-letter/build-spec/diff/Changes 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1 @@ +This is unlike any other dummy changelog. diff -Nru lintian-2.93.0/t/recipes/lintian-features/lintian-output-letter/build-spec/fill-values lintian-2.89.0ubuntu1/t/recipes/lintian-features/lintian-output-letter/build-spec/fill-values --- lintian-2.93.0/t/recipes/lintian-features/lintian-output-letter/build-spec/fill-values 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/lintian-features/lintian-output-letter/build-spec/fill-values 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,4 @@ +Testname: lintian-output-letter +Skeleton: upload-non-native +Version: 1.0+dsfg-1.1 +Description: Test Lintian letter qualifier output format diff -Nru lintian-2.93.0/t/recipes/lintian-features/lintian-output-letter/build-spec/orig/example lintian-2.89.0ubuntu1/t/recipes/lintian-features/lintian-output-letter/build-spec/orig/example --- lintian-2.93.0/t/recipes/lintian-features/lintian-output-letter/build-spec/orig/example 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/lintian-features/lintian-output-letter/build-spec/orig/example 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,2 @@ +#!/usr/bin/foo +echo This is some example. diff -Nru lintian-2.93.0/t/recipes/lintian-features/lintian-output-letter/build-spec/orig/script lintian-2.89.0ubuntu1/t/recipes/lintian-features/lintian-output-letter/build-spec/orig/script --- lintian-2.93.0/t/recipes/lintian-features/lintian-output-letter/build-spec/orig/script 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/lintian-features/lintian-output-letter/build-spec/orig/script 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,3 @@ +#!/bin/sh +. /usr/share/debconf/confmodule +echo 'Hello world' diff -Nru lintian-2.93.0/t/recipes/lintian-features/lintian-output-letter/build-spec/orig/script.desktop lintian-2.89.0ubuntu1/t/recipes/lintian-features/lintian-output-letter/build-spec/orig/script.desktop --- lintian-2.93.0/t/recipes/lintian-features/lintian-output-letter/build-spec/orig/script.desktop 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/lintian-features/lintian-output-letter/build-spec/orig/script.desktop 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +[Desktop Entry] +Name=script +Type=Application +Comment=Incorrectly limited to particular environments +Categories=Development; +Exec=script +OnlyShowIn=GNOME;KDE; +Icon=foo +Keywords=Lintian diff -Nru lintian-2.93.0/t/recipes/lintian-features/lintian-output-letter/eval/desc lintian-2.89.0ubuntu1/t/recipes/lintian-features/lintian-output-letter/eval/desc --- lintian-2.93.0/t/recipes/lintian-features/lintian-output-letter/eval/desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/lintian-features/lintian-output-letter/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,5 @@ +Testname: lintian-output-letter +Options: --show-overrides +Output-Format: letterqualifier +Match-Strategy: literal +Default-Lintian-Options: --pedantic --display-info --display-experimental diff -Nru lintian-2.93.0/t/recipes/lintian-features/lintian-output-letter/eval/literal lintian-2.89.0ubuntu1/t/recipes/lintian-features/lintian-output-letter/eval/literal --- lintian-2.93.0/t/recipes/lintian-features/lintian-output-letter/eval/literal 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/lintian-features/lintian-output-letter/eval/literal 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,24 @@ +E[E]: lintian-output-letter: dir-in-usr-local usr/local/share/ +E[E]: lintian-output-letter: dir-in-usr-local usr/local/share/lintian/ +E[E]: lintian-output-letter: dir-or-file-in-var-lock var/lock/lintian/ +E[E]: lintian-output-letter: new-essential-package +E[E]: lintian-output-letter: possible-gpl-code-linked-with-openssl +W[W]: lintian-output-letter source: changelog-file-missing-explicit-entry 0.0.1-1 -> 1.0+dsfg-1 (missing) -> 1.0+dsfg-1.1 +W[W]: lintian-output-letter source: format-3.0-but-debian-changes-patch +W[W]: lintian-output-letter source: maintainer-upload-has-incorrect-version-number 1.0+dsfg-1.1 +W[W]: lintian-output-letter: no-manual-page usr/bin/script +I[I]: lintian-output-letter source: binary-control-field-duplicates-source field "Section" in package lintian-output-letter +I[I]: lintian-output-letter: description-possibly-contains-homepage http://www.example.com/. +I[I]: lintian-output-letter: desktop-entry-limited-to-environments usr/share/applications/script.desktop +I[I]: lintian-output-letter: package-contains-empty-directory usr/local/share/lintian/ +I[I]: lintian-output-letter source: patch-not-forwarded-upstream debian/patches/debian-changes-1.0+dsfg-1.1 +I[I]: lintian-output-letter source: quilt-patch-using-template-description debian-changes-1.0+dsfg-1.1 +I[I]: lintian-output-letter: synopsis-is-a-sentence "Test Lintian letter qualifier output format." +I[I]: lintian-output-letter source: upstream-metadata-missing-bug-tracking +I[I]: lintian-output-letter source: upstream-metadata-missing-repository +P[P]: lintian-output-letter source: debian-control-has-unusual-field-spacing line 12 +X[P]: lintian-output-letter source: debian-watch-does-not-check-gpg-signature +P[P]: lintian-output-letter: example-unusual-interpreter usr/share/doc/lintian-output-letter/examples/example #!/usr/bin/foo +P[P]: lintian-output-letter source: no-homepage-field +P[P]: lintian-output-letter source: old-source-override-location +O[W]: lintian-output-letter source: dfsg-version-misspelled 1.0+dsfg-1.1 diff -Nru lintian-2.93.0/t/recipes/lintian-features/lintian-output-xml/build-spec/debian/control.in lintian-2.89.0ubuntu1/t/recipes/lintian-features/lintian-output-xml/build-spec/debian/control.in --- lintian-2.93.0/t/recipes/lintian-features/lintian-output-xml/build-spec/debian/control.in 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/lintian-features/lintian-output-xml/build-spec/debian/control.in 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,20 @@ +Source: [% $source %] +Priority: optional +Section: [% $section %] +Maintainer: [% $author %] +Standards-Version: [% $standards_version %] +Build-Depends: [% $build_depends %] +Rules-Requires-Root: no + +Package: [% $source %] +Architecture: [% $package_architecture %] +Depends: ${misc:Depends}, libssl0.9.8 (>= 0abcd) +Essential:yes +Section: [% $section %] +Description: [% $description %]. + This is a test package designed to exercise some feature or tag of + Lintian. It is part of the Lintian test suite and may do very odd + things. It should not be installed like a regular package. It may + be an empty package. + . + The homepage is http://www.example.com/. diff -Nru lintian-2.93.0/t/recipes/lintian-features/lintian-output-xml/build-spec/debian/dirs lintian-2.89.0ubuntu1/t/recipes/lintian-features/lintian-output-xml/build-spec/debian/dirs --- lintian-2.93.0/t/recipes/lintian-features/lintian-output-xml/build-spec/debian/dirs 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/lintian-features/lintian-output-xml/build-spec/debian/dirs 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,2 @@ +usr/local/share/lintian +var/lock/lintian diff -Nru lintian-2.93.0/t/recipes/lintian-features/lintian-output-xml/build-spec/debian/examples lintian-2.89.0ubuntu1/t/recipes/lintian-features/lintian-output-xml/build-spec/debian/examples --- lintian-2.93.0/t/recipes/lintian-features/lintian-output-xml/build-spec/debian/examples 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/lintian-features/lintian-output-xml/build-spec/debian/examples 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1 @@ +example diff -Nru lintian-2.93.0/t/recipes/lintian-features/lintian-output-xml/build-spec/debian/install lintian-2.89.0ubuntu1/t/recipes/lintian-features/lintian-output-xml/build-spec/debian/install --- lintian-2.93.0/t/recipes/lintian-features/lintian-output-xml/build-spec/debian/install 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/lintian-features/lintian-output-xml/build-spec/debian/install 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,2 @@ +script usr/bin +script.desktop usr/share/applications diff -Nru lintian-2.93.0/t/recipes/lintian-features/lintian-output-xml/build-spec/debian/rules lintian-2.89.0ubuntu1/t/recipes/lintian-features/lintian-output-xml/build-spec/debian/rules --- lintian-2.93.0/t/recipes/lintian-features/lintian-output-xml/build-spec/debian/rules 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/lintian-features/lintian-output-xml/build-spec/debian/rules 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,5 @@ +#!/usr/bin/make -f +%: + dh $@ + +override_dh_usrlocal: diff -Nru lintian-2.93.0/t/recipes/lintian-features/lintian-output-xml/build-spec/debian/source.lintian-overrides lintian-2.89.0ubuntu1/t/recipes/lintian-features/lintian-output-xml/build-spec/debian/source.lintian-overrides --- lintian-2.93.0/t/recipes/lintian-features/lintian-output-xml/build-spec/debian/source.lintian-overrides 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/lintian-features/lintian-output-xml/build-spec/debian/source.lintian-overrides 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1 @@ +lintian-output-xml source: dfsg-version-misspelled 1.0* diff -Nru lintian-2.93.0/t/recipes/lintian-features/lintian-output-xml/build-spec/diff/Changes lintian-2.89.0ubuntu1/t/recipes/lintian-features/lintian-output-xml/build-spec/diff/Changes --- lintian-2.93.0/t/recipes/lintian-features/lintian-output-xml/build-spec/diff/Changes 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/lintian-features/lintian-output-xml/build-spec/diff/Changes 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1 @@ +This is unlike any other dummy changelog. diff -Nru lintian-2.93.0/t/recipes/lintian-features/lintian-output-xml/build-spec/fill-values lintian-2.89.0ubuntu1/t/recipes/lintian-features/lintian-output-xml/build-spec/fill-values --- lintian-2.93.0/t/recipes/lintian-features/lintian-output-xml/build-spec/fill-values 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/lintian-features/lintian-output-xml/build-spec/fill-values 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,5 @@ +Testname: lintian-output-xml +Skeleton: upload-non-native +Version: 1.0+dsfg-1.1 +Package-Architecture: all +Description: Test Lintian XML output format diff -Nru lintian-2.93.0/t/recipes/lintian-features/lintian-output-xml/build-spec/orig/example lintian-2.89.0ubuntu1/t/recipes/lintian-features/lintian-output-xml/build-spec/orig/example --- lintian-2.93.0/t/recipes/lintian-features/lintian-output-xml/build-spec/orig/example 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/lintian-features/lintian-output-xml/build-spec/orig/example 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,2 @@ +#!/usr/bin/foo +echo This is some example. diff -Nru lintian-2.93.0/t/recipes/lintian-features/lintian-output-xml/build-spec/orig/script lintian-2.89.0ubuntu1/t/recipes/lintian-features/lintian-output-xml/build-spec/orig/script --- lintian-2.93.0/t/recipes/lintian-features/lintian-output-xml/build-spec/orig/script 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/lintian-features/lintian-output-xml/build-spec/orig/script 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,3 @@ +#!/bin/sh +. /usr/share/debconf/confmodule +echo 'Hello world' diff -Nru lintian-2.93.0/t/recipes/lintian-features/lintian-output-xml/build-spec/orig/script.desktop lintian-2.89.0ubuntu1/t/recipes/lintian-features/lintian-output-xml/build-spec/orig/script.desktop --- lintian-2.93.0/t/recipes/lintian-features/lintian-output-xml/build-spec/orig/script.desktop 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/lintian-features/lintian-output-xml/build-spec/orig/script.desktop 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +[Desktop Entry] +Name=script +Type=Application +Comment=Incorrectly limited to particular environments +Categories=Development; +Exec=script +OnlyShowIn=GNOME;KDE; +Icon=foo +Keywords=Lintian diff -Nru lintian-2.93.0/t/recipes/lintian-features/lintian-output-xml/eval/desc lintian-2.89.0ubuntu1/t/recipes/lintian-features/lintian-output-xml/eval/desc --- lintian-2.93.0/t/recipes/lintian-features/lintian-output-xml/eval/desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/lintian-features/lintian-output-xml/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,5 @@ +Testname: lintian-output-xml +Options: --show-overrides +Output-Format: xml +Match-Strategy: literal +Default-Lintian-Options: --pedantic --display-info --display-experimental diff -Nru lintian-2.93.0/t/recipes/lintian-features/lintian-output-xml/eval/literal lintian-2.89.0ubuntu1/t/recipes/lintian-features/lintian-output-xml/eval/literal --- lintian-2.93.0/t/recipes/lintian-features/lintian-output-xml/eval/literal 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/lintian-features/lintian-output-xml/eval/literal 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,125 @@ + + + + VERSION + + + lintian-output-xml + 1.0+dsfg-1.1 + TIMESTAMP + + + + + changelog-file-missing-explicit-entry + 0.0.1-1 -> 1.0+dsfg-1 (missing) -> 1.0+dsfg-1.1 + + + format-3.0-but-debian-changes-patch + + + maintainer-upload-has-incorrect-version-number + 1.0+dsfg-1.1 + + + binary-control-field-duplicates-source + field "Section" in package lintian-output-xml + + + patch-not-forwarded-upstream + debian/patches/debian-changes-1.0+dsfg-1.1 + + + quilt-patch-using-template-description + debian-changes-1.0+dsfg-1.1 + + + upstream-metadata-missing-bug-tracking + + + upstream-metadata-missing-repository + + + debian-control-has-unusual-field-spacing + line 12 + + + debian-watch-does-not-check-gpg-signature + yes + + + no-homepage-field + + + old-source-override-location + + + dfsg-version-misspelled + 1.0+dsfg-1.1 + + maintainer + + + + + + + + + + + + + lintian-output-xml + all + deb + + + dir-in-usr-local + usr/local/share/ + + + dir-in-usr-local + usr/local/share/lintian/ + + + dir-or-file-in-var-lock + var/lock/lintian/ + + + new-essential-package + + + possible-gpl-code-linked-with-openssl + + + no-manual-page + usr/bin/script + + + description-possibly-contains-homepage + http://www.example.com/. + + + desktop-entry-limited-to-environments + usr/share/applications/script.desktop + + + package-contains-empty-directory + usr/local/share/lintian/ + + + synopsis-is-a-sentence + "Test Lintian XML output format." + + + example-unusual-interpreter + usr/share/doc/lintian-output-xml/examples/example #!/usr/bin/foo + + + + + + + + diff -Nru lintian-2.93.0/t/recipes/lintian-features/lintian-output-xml/eval/post-test lintian-2.89.0ubuntu1/t/recipes/lintian-features/lintian-output-xml/eval/post-test --- lintian-2.93.0/t/recipes/lintian-features/lintian-output-xml/eval/post-test 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/lintian-features/lintian-output-xml/eval/post-test 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,2 @@ +s/\S+<\/lintian-version>/VERSION<\/lintian-version>/ +s/\S+<\/run-start>/TIMESTAMP<\/run-start>/ diff -Nru lintian-2.93.0/t/recipes/runner-features/runtests-todo/eval/desc lintian-2.89.0ubuntu1/t/recipes/runner-features/runtests-todo/eval/desc --- lintian-2.93.0/t/recipes/runner-features/runtests-todo/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/runner-features/runtests-todo/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -1,5 +1,5 @@ Testname: runtests-todo -Todo: This tests the Todo feature in the runner. +Todo: yes Match-Strategy: literal Output-Format: EWI Default-Lintian-Options: --pedantic --display-info --display-experimental diff -Nru lintian-2.93.0/t/recipes/tracking/generic-dh-make-2008/eval/desc lintian-2.89.0ubuntu1/t/recipes/tracking/generic-dh-make-2008/eval/desc --- lintian-2.93.0/t/recipes/tracking/generic-dh-make-2008/eval/desc 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/recipes/tracking/generic-dh-make-2008/eval/desc 2020-08-10 09:59:45.000000000 +0000 @@ -1,3 +1,3 @@ Testname: generic-dh-make-2008 -See-Also: Debian Bug#497347 +References: Debian Bug#497347 Default-Lintian-Options: --pedantic --display-info --display-experimental diff -Nru lintian-2.93.0/t/scripts/harness/desc-fields.t lintian-2.89.0ubuntu1/t/scripts/harness/desc-fields.t --- lintian-2.93.0/t/scripts/harness/desc-fields.t 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/scripts/harness/desc-fields.t 2020-08-10 09:59:45.000000000 +0000 @@ -46,10 +46,10 @@ my @descpaths = File::Find::Rule->file()->name('desc')->in('t/recipes'); # mandatory fields -my @mandatory = qw(Testname); +my @mandatory = qw(); # disallowed fields -my @disallowed = qw(Test-For Checks References Reference Ref); +my @disallowed = qw(test_for checks); # tests per desc my $perfile = 6 + scalar @mandatory + scalar @disallowed; diff -Nru lintian-2.93.0/t/scripts/harness/tagextract.t lintian-2.89.0ubuntu1/t/scripts/harness/tagextract.t --- lintian-2.93.0/t/scripts/harness/tagextract.t 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/scripts/harness/tagextract.t 2020-08-10 09:59:45.000000000 +0000 @@ -46,7 +46,7 @@ EOSTR # test plan -plan tests => 1; +plan tests => 5; # EWI input my $ewi =<<'EOSTR'; @@ -71,6 +71,107 @@ 'Tags extracted from EWI format matched.' ); +# fullewi input +my $fullewi =<<'EOSTR'; +E: changelog-file-general source (1:1.0-1) [source]: latest-debian-changelog-entry-without-new-date +W: changelog-file-general binary (1:1.0-1) [all]: changelog-not-compressed-with-max-compression changelog.Debian.gz +W: changelog-file-general binary (1:1.0-1) [all]: debian-changelog-file-contains-obsolete-user-emacs-settings +E: changelog-file-general binary (1:1.0-1) [all]: debian-changelog-file-contains-invalid-email-address unknown@unknown +E: changelog-file-general binary (1:1.0-1) [all]: latest-changelog-entry-without-new-date +W: changelog-file-general binary (1:1.0-1) [all]: latest-debian-changelog-entry-reuses-existing-version 1:1.0-1 == 1.0-1 (last used: Fri, 01 Feb 2019 12:27:45 -0800) +E: changelog-file-general binary (1:1.0-1) [all]: epoch-changed-but-upstream-version-did-not-go-backwards 1.0 >= 1.0 +E: changelog-file-general binary (1:1.0-1) [all]: possible-missing-colon-in-closes Closes #555555 +W: changelog-file-general binary (1:1.0-1) [all]: changelog-references-temp-security-identifier TEMP-1234567-abcdef +X: changelog-file-general binary (1:1.0-1) [all]: bad-intended-distribution intended to experimental but uploaded to unstable +W: changelog-file-general binary (1:1.0-1) [all]: misspelled-closes-bug #666666 +W: changelog-file-general binary (1:1.0-1) [all]: improbable-bug-number-in-closes 1234 +W: changelog-file-general binary (1:1.0-1) [all]: debian-changelog-line-too-long line 8 +W: changelog-file-general binary (1:1.0-1) [all]: debian-changelog-line-too-long line 15 +EOSTR + +ok( + tagextract('fullewi', $fullewi) eq $expected, + 'Tags extracted from full format matched.' +); + +# letterqualifier input +my $letterqualifier =<<'EOSTR'; +E[I!]: changelog-file-general source: latest-debian-changelog-entry-without-new-date +W[N!]: changelog-file-general: changelog-not-compressed-with-max-compression changelog.Debian.gz +W[N!]: changelog-file-general: debian-changelog-file-contains-obsolete-user-emacs-settings +E[I!]: changelog-file-general: debian-changelog-file-contains-invalid-email-address unknown@unknown +E[I!]: changelog-file-general: latest-changelog-entry-without-new-date +W[N!]: changelog-file-general: latest-debian-changelog-entry-reuses-existing-version 1:1.0-1 == 1.0-1 (last used: Fri, 01 Feb 2019 12:27:45 -0800) +E[S ]: changelog-file-general: epoch-changed-but-upstream-version-did-not-go-backwards 1.0 >= 1.0 +E[I ]: changelog-file-general: possible-missing-colon-in-closes Closes #555555 +W[N!]: changelog-file-general: changelog-references-temp-security-identifier TEMP-1234567-abcdef +X[N?]: changelog-file-general: bad-intended-distribution intended to experimental but uploaded to unstable +W[N!]: changelog-file-general: misspelled-closes-bug #666666 +W[N ]: changelog-file-general: improbable-bug-number-in-closes 1234 +W[N!]: changelog-file-general: debian-changelog-line-too-long line 8 +W[N!]: changelog-file-general: debian-changelog-line-too-long line 15 +EOSTR + +ok( + tagextract('letterqualifier', $letterqualifier) eq $expected, + 'Tags extracted from letterqualifier format matched.' +); + +# xml input +my $xml =<<'EOSTR'; + + + + + + + + +changelog.Debian.gz + +unknown@unknown + +1:1.0-1 == 1.0-1 (last used: Fri, 01 Feb 2019 12:27:45 -0800) +1.0 >= 1.0 +Closes #555555 +TEMP-1234567-abcdef +intended to experimental but uploaded to unstable +#666666 +1234 +line 8 +line 15 + +EOSTR + +ok( + tagextract('xml', $xml) eq $expected, + 'Tags extracted from xml format matched.' +); + +# colons input +my $colons =<<'EOSTR'; +tag:E:important::changelog-file-general:1\:1.0-1:source:source:latest-debian-changelog-entry-without-new-date:: +tag:W:normal::changelog-file-general:1\:1.0-1:all:binary:changelog-not-compressed-with-max-compression:changelog.Debian.gz: +tag:W:normal::changelog-file-general:1\:1.0-1:all:binary:debian-changelog-file-contains-obsolete-user-emacs-settings:: +tag:E:important::changelog-file-general:1\:1.0-1:all:binary:debian-changelog-file-contains-invalid-email-address:unknown@unknown: +tag:E:important::changelog-file-general:1\:1.0-1:all:binary:latest-changelog-entry-without-new-date:: +tag:W:normal::changelog-file-general:1\:1.0-1:all:binary:latest-debian-changelog-entry-reuses-existing-version:1\:1.0-1 == 1.0-1 (last used\: Fri, 01 Feb 2019 12\:27\:45 -0800): +tag:E:serious::changelog-file-general:1\:1.0-1:all:binary:epoch-changed-but-upstream-version-did-not-go-backwards:1.0 >= 1.0: +tag:E:important::changelog-file-general:1\:1.0-1:all:binary:possible-missing-colon-in-closes:Closes #555555: +tag:W:normal::changelog-file-general:1\:1.0-1:all:binary:changelog-references-temp-security-identifier:TEMP-1234567-abcdef: +tag:I:normal:X:changelog-file-general:1\:1.0-1:all:binary:bad-intended-distribution:intended to experimental but uploaded to unstable: +tag:W:normal::changelog-file-general:1\:1.0-1:all:binary:misspelled-closes-bug:#666666: +tag:W:normal::changelog-file-general:1\:1.0-1:all:binary:improbable-bug-number-in-closes:1234: +tag:W:normal::changelog-file-general:1\:1.0-1:all:binary:debian-changelog-line-too-long:line 8: +tag:W:normal::changelog-file-general:1\:1.0-1:all:binary:debian-changelog-line-too-long:line 15: +EOSTR + +ok( + tagextract('colons', $colons) eq $expected, + 'Tags extracted from colons format matched.' +); + exit; sub tagextract { diff -Nru lintian-2.93.0/t/scripts/pod.t lintian-2.89.0ubuntu1/t/scripts/pod.t --- lintian-2.93.0/t/scripts/pod.t 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/scripts/pod.t 2020-08-10 09:59:45.000000000 +0000 @@ -13,13 +13,8 @@ my $dir = $ENV{'LINTIAN_BASE'} // '.'; -my @POD_FILES = all_pod_files( - "$dir/lib", - "$dir/doc/tutorial", - "$dir/man/lintian.pod", - "$dir/man/annotate-lintian-hints.pod", - "$dir/man/explain-lintian-tags.pod", -); +my @POD_FILES = all_pod_files("$dir/lib", "$dir/doc/tutorial"); +push(@POD_FILES, map { "$dir/man/$_" } 'lintian-info.pod', 'lintian.pod.in'); all_pod_files_ok(@POD_FILES); diff -Nru lintian-2.93.0/t/scripts/profiles-coverage.t lintian-2.89.0ubuntu1/t/scripts/profiles-coverage.t --- lintian-2.93.0/t/scripts/profiles-coverage.t 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/scripts/profiles-coverage.t 2020-08-10 09:59:45.000000000 +0000 @@ -37,7 +37,7 @@ my %TAGS; # find all tags -my @tagpaths = File::Find::Rule->file->name('*.tag')->in("$root/tags"); +my @tagpaths = File::Find::Rule->file->name('*.desc')->in("$root/tags"); for my $desc (@tagpaths) { my @sections = read_dpkg_control($desc); BAIL_OUT("$desc does not have exactly one paragraph") diff -Nru lintian-2.93.0/t/scripts/tags/desc-fields.t lintian-2.89.0ubuntu1/t/scripts/tags/desc-fields.t --- lintian-2.93.0/t/scripts/tags/desc-fields.t 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/scripts/tags/desc-fields.t 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,133 @@ +#!/usr/bin/perl + +# Copyright © 2019 Felix Lechner +# +# This program is free software; you can redistribute it and/or modify +# it under the terms of the GNU General Public License as published by +# the Free Software Foundation; either version 2 of the License, or +# (at your option) any later version. +# +# This program is distributed in the hope that it will be useful, +# but WITHOUT ANY WARRANTY; without even the implied warranty of +# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the +# GNU General Public License for more details. +# +# You should have received a copy of the GNU General Public License +# along with this program. If not, you can find it on the World Wide +# Web at http://www.gnu.org/copyleft/gpl.html, or write to the Free +# Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, +# MA 02110-1301, USA. + +# The harness for Lintian's test suite. For detailed information on +# the test suite layout and naming conventions, see t/tests/README. +# For more information about running tests, see +# doc/tutorial/Lintian/Tutorial/TestSuite.pod +# + +use strict; +use warnings; +use autodie; +use v5.10; + +use File::Find::Rule; +use List::Util qw(all); +use Path::Tiny; +use Test::More; + +use lib "$ENV{'LINTIAN_BASE'}/lib"; + +use Lintian::Deb822::File; +use Lintian::Profile; + +use constant SPACE => q{ }; + +my @descpaths = sort File::Find::Rule->file()->name('*.desc')->in('tags'); + +diag scalar @descpaths . ' known tags.'; + +# mandatory fields +my @mandatory = qw(Tag Severity Check Info); + +# disallowed fields +my @disallowed = qw(Reference References); + +# tests per desc +my $perfile = 7 + scalar @mandatory + scalar @disallowed; + +# set the testing plan +plan tests => $perfile * scalar @descpaths; + +my $profile = Lintian::Profile->new; +$profile->load(undef, [$ENV{LINTIAN_BASE}]); + +for my $descpath (@descpaths) { + + # test for duplicate fields + my %count; + + my @lines = path($descpath)->lines; + for my $line (@lines) { + my ($field) = $line =~ qr/^(\S+):/; + $count{$field} += 1 + if defined $field; + } + + ok( + (all { $count{$_} == 1 } keys %count), + "No duplicate fields in $descpath" + ); + + my $deb822 = Lintian::Deb822::File->new; + + my @sections = $deb822->read_file($descpath); + is(scalar @sections, 1, "Tag in $descpath has exactly one section"); + + my $fields = $sections[0] // {}; + + # tag has a name + my $tagname = $fields->value('Tag'); + BAIL_OUT("Tag described in $descpath has no name") + unless length $tagname; + + # tagfile is named $tagname.desc + is(path($descpath)->basename, + "$tagname.desc", "Tagfile for $tagname is named $tagname.desc"); + + # mandatory fields + ok($fields->exists($_), "Field $_ exists in $descpath")for @mandatory; + + # disallowed fields + ok(!$fields->exists($_), "Field $_ does not exist in $descpath") + for @disallowed; + + my $checkname = $fields->value('Check'); + + # tag is associated with a check + ok(length $checkname, "Tag $tagname is associated with a check"); + + ok($profile->get_checkinfo($checkname), + "Tag $tagname is associated with a valid check"); + + if ($fields->value('Name-Spaced') eq 'yes') { + # encapsulating directory is name of check + my $subdir = path($descpath)->parent->relative('tags'); + is($subdir, $checkname, + "Tag $tagname is in directory named '$checkname'"); + + } else { + # encapsulating directory is first letter of tag's name + my $parentdir = path($descpath)->parent->basename; + my $firstletter = lc(substr($tagname, 0, 1)); + is($parentdir, $firstletter, + "Tag $tagname is in directory named '$firstletter'"); + } + + ok($fields->value('Renamed-From') !~ m{,}, + "Old tag names for $tagname are not separated by commas"); +} + +# Local Variables: +# indent-tabs-mode: nil +# cperl-indent-level: 4 +# End: +# vim: syntax=perl sw=4 sts=4 sr et diff -Nru lintian-2.93.0/t/scripts/tags/fields.t lintian-2.89.0ubuntu1/t/scripts/tags/fields.t --- lintian-2.93.0/t/scripts/tags/fields.t 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/t/scripts/tags/fields.t 1970-01-01 00:00:00.000000000 +0000 @@ -1,166 +0,0 @@ -#!/usr/bin/perl - -# Copyright © 2019-2020 Felix Lechner -# -# This program is free software; you can redistribute it and/or modify -# it under the terms of the GNU General Public License as published by -# the Free Software Foundation; either version 2 of the License, or -# (at your option) any later version. -# -# This program is distributed in the hope that it will be useful, -# but WITHOUT ANY WARRANTY; without even the implied warranty of -# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the -# GNU General Public License for more details. -# -# You should have received a copy of the GNU General Public License -# along with this program. If not, you can find it on the World Wide -# Web at http://www.gnu.org/copyleft/gpl.html, or write to the Free -# Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, -# MA 02110-1301, USA. - -# The harness for Lintian's test suite. For detailed information on -# the test suite layout and naming conventions, see t/tests/README. -# For more information about running tests, see -# doc/tutorial/Lintian/Tutorial/TestSuite.pod -# - -use v5.20; -use warnings; -use utf8; -use autodie; - -use File::Find::Rule; -use IPC::Run3; -use List::Util qw(all); -use Path::Tiny; -use Test::More; - -use lib "$ENV{'LINTIAN_BASE'}/lib"; - -use Lintian::Deb822::File; -use Lintian::Output::HTML; -use Lintian::Profile; - -use constant EMPTY => q{}; -use constant SPACE => q{ }; -use constant SLASH => q{/}; - -my @tagpaths = sort File::Find::Rule->file()->name('*.tag')->in('tags'); - -diag scalar @tagpaths . ' known tags.'; - -# mandatory fields -my @mandatory = qw(Tag Severity Check Explanation); - -# disallowed fields -my @disallowed = qw(Reference References Ref Info Certainty); - -# tests per desc -my $perfile = 8 + scalar @mandatory + scalar @disallowed; - -# set the testing plan -plan tests => $perfile * scalar @tagpaths; - -my $profile = Lintian::Profile->new; -$profile->load(undef, [$ENV{LINTIAN_BASE}]); - -for my $tagpath (@tagpaths) { - - # test for duplicate fields - my %count; - - my @lines = path($tagpath)->lines; - for my $line (@lines) { - my ($field) = $line =~ qr/^(\S+):/; - $count{$field} += 1 - if defined $field; - } - - ok((all { $count{$_} == 1 } keys %count), - "No duplicate fields in $tagpath"); - - my $deb822 = Lintian::Deb822::File->new; - - my @sections = $deb822->read_file($tagpath); - is(scalar @sections, 1, "Tag in $tagpath has exactly one section"); - - my $fields = $sections[0] // {}; - - # tag has a name - my $tagname = $fields->value('Tag'); - BAIL_OUT("Tag described in $tagpath has no name") - unless length $tagname; - - # tagfile is named $tagname.tag - is(path($tagpath)->basename, - "$tagname.tag", "Tagfile for $tagname is named $tagname.tag"); - - my $checkname = $fields->value('Check'); - - # tag is associated with a check - ok(length $checkname, "Tag $tagname is associated with a check"); - - if ($fields->value('Name-Spaced') eq 'yes') { - - $tagname = $checkname . SLASH . $tagname; - - # encapsulating directory is name of check - my $subdir = path($tagpath)->parent->relative('tags'); - is($subdir, $checkname, - "Tag $tagname is in directory named '$checkname'"); - - } else { - # encapsulating directory is first letter of tag's name - my $parentdir = path($tagpath)->parent->basename; - my $firstletter = lc(substr($tagname, 0, 1)); - is($parentdir, $firstletter, - "Tag $tagname is in directory named '$firstletter'"); - } - - # mandatory fields - ok($fields->exists($_), "Field $_ exists in $tagpath")for @mandatory; - - # disallowed fields - ok(!$fields->exists($_), "Field $_ does not exist in $tagpath") - for @disallowed; - - ok($profile->get_checkinfo($checkname), - "Tag $tagname is associated with a valid check"); - - ok($fields->value('Renamed-From') !~ m{,}, - "Old tag names for $tagname are not separated by commas"); - - my $html_output = Lintian::Output::HTML->new; - - my $taginfo = $profile->get_taginfo($tagname); - BAIL_OUT("Tag $tagname was not loaded via profile") - unless defined $taginfo; - - my $html_description; - open(my $fh, '>:encoding(UTF-8)', \$html_description); - select $fh; - - print "$tagname"; - $html_output->tag_description($taginfo); - say ''; - - select *STDOUT; - close $fh; - - print $html_description; - - my $tidy_out; - my $tidy_err; - - my @tidy_command = qw(tidy -quiet); - run3(\@tidy_command, \$html_description, \$tidy_out, \$tidy_err); - - is($tidy_err, EMPTY, - "No warnings from HTML Tidy for tag description in $tagname"); -} - -# Local Variables: -# indent-tabs-mode: nil -# cperl-indent-level: 4 -# End: -# vim: syntax=perl sw=4 sts=4 sr et diff -Nru lintian-2.93.0/tags/a/absolute-symbolic-link-target-in-source.desc lintian-2.89.0ubuntu1/tags/a/absolute-symbolic-link-target-in-source.desc --- lintian-2.93.0/tags/a/absolute-symbolic-link-target-in-source.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/a/absolute-symbolic-link-target-in-source.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,11 @@ +Tag: absolute-symbolic-link-target-in-source +Severity: warning +Check: files/symbolic-links +Info: This symlink in a patched source tree points to an absolute target. It + happens sometimes when people point toward /dev/null, but that can and should + be done in the installation package instead. It is no problem there. The + source package is considered unanchored and should not contain any absolute + file references. + . + Please remove the symbolic link from the source package or point it to a + a location inside the patched source tree. diff -Nru lintian-2.93.0/tags/a/absolute-symbolic-link-target-in-source.tag lintian-2.89.0ubuntu1/tags/a/absolute-symbolic-link-target-in-source.tag --- lintian-2.93.0/tags/a/absolute-symbolic-link-target-in-source.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/a/absolute-symbolic-link-target-in-source.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,11 +0,0 @@ -Tag: absolute-symbolic-link-target-in-source -Severity: warning -Check: files/symbolic-links -Explanation: This symlink in a patched source tree points to an absolute target. It - happens sometimes when people point toward /dev/null, but that can and should - be done in the installation package instead. It is no problem there. The - source package is considered unanchored and should not contain any absolute - file references. - . - Please remove the symbolic link from the source package or point it to a - a location inside the patched source tree. diff -Nru lintian-2.93.0/tags/a/absolute-symlink-in-top-level-folder.desc lintian-2.89.0ubuntu1/tags/a/absolute-symlink-in-top-level-folder.desc --- lintian-2.93.0/tags/a/absolute-symlink-in-top-level-folder.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/a/absolute-symlink-in-top-level-folder.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,12 @@ +Tag: absolute-symlink-in-top-level-folder +Severity: warning +Check: files/symbolic-links +Renamed-From: symlink-should-be-relative +Info: Symlinks to files which are in the same top-level directory should be + relative according to policy. (In other words, a link in /usr to another + file in /usr should be relative, while a link in /usr to a file in /etc + should be absolute.) + . + If you use debhelper, running dh_link after creating the package structure + will fix this problem for you. +Ref: policy 10.5 diff -Nru lintian-2.93.0/tags/a/absolute-symlink-in-top-level-folder.tag lintian-2.89.0ubuntu1/tags/a/absolute-symlink-in-top-level-folder.tag --- lintian-2.93.0/tags/a/absolute-symlink-in-top-level-folder.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/a/absolute-symlink-in-top-level-folder.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,12 +0,0 @@ -Tag: absolute-symlink-in-top-level-folder -Severity: warning -Check: files/symbolic-links -Renamed-From: symlink-should-be-relative -Explanation: Symlinks to files which are in the same top-level directory should be - relative according to policy. (In other words, a link in /usr to another - file in /usr should be relative, while a link in /usr to a file in /etc - should be absolute.) - . - If you use debhelper, running dh_link after creating the package structure - will fix this problem for you. -See-Also: policy 10.5 diff -Nru lintian-2.93.0/tags/a/acute-accent-in-manual-page.desc lintian-2.89.0ubuntu1/tags/a/acute-accent-in-manual-page.desc --- lintian-2.93.0/tags/a/acute-accent-in-manual-page.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/a/acute-accent-in-manual-page.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,12 @@ +Tag: acute-accent-in-manual-page +Severity: info +Check: documentation/manual +Renamed-From: acute-accent-in-manpage +Info: This manual page uses the \' groff sequence. Usually, the + intent to generate an apostrophe, but that sequence actually + renders as a an acute accent. + . + For an apostrophe or a single closing quote, use plain '. + For single opening quote, i.e. a straight downward line ' + like the one used in shell commands, use \(aq. +Ref: Bug#554897, Bug#507673 diff -Nru lintian-2.93.0/tags/a/acute-accent-in-manual-page.tag lintian-2.89.0ubuntu1/tags/a/acute-accent-in-manual-page.tag --- lintian-2.93.0/tags/a/acute-accent-in-manual-page.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/a/acute-accent-in-manual-page.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,12 +0,0 @@ -Tag: acute-accent-in-manual-page -Severity: info -Check: documentation/manual -Renamed-From: acute-accent-in-manpage -Explanation: This manual page uses the \' groff sequence. Usually, the - intent to generate an apostrophe, but that sequence actually - renders as an acute accent. - . - For an apostrophe or a single closing quote, use plain '. - For single opening quote, i.e. a straight downward line ' - like the one used in shell commands, use '\(aq'. -See-Also: Bug#554897, Bug#507673 diff -Nru lintian-2.93.0/tags/a/adduser-with-home-var-run.desc lintian-2.89.0ubuntu1/tags/a/adduser-with-home-var-run.desc --- lintian-2.93.0/tags/a/adduser-with-home-var-run.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/a/adduser-with-home-var-run.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: adduser-with-home-var-run +Severity: warning +Check: maintainer-scripts/adduser +Info: {pre,post}inst script calls adduser --home /var/run, should be /run. + Examples of such packages include pesign, pulseaudio and openssh-server + (#760422, fixed). +Ref: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760422 diff -Nru lintian-2.93.0/tags/a/adduser-with-home-var-run.tag lintian-2.89.0ubuntu1/tags/a/adduser-with-home-var-run.tag --- lintian-2.93.0/tags/a/adduser-with-home-var-run.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/a/adduser-with-home-var-run.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: adduser-with-home-var-run -Severity: warning -Check: maintainer-scripts/adduser -Explanation: {pre,post}inst script calls adduser --home /var/run, should be /run. - Examples for such packages include pesign, pulseaudio and openssh-server. -See-Also: Bug#760422 diff -Nru lintian-2.93.0/tags/a/alternates-not-allowed.desc lintian-2.89.0ubuntu1/tags/a/alternates-not-allowed.desc --- lintian-2.93.0/tags/a/alternates-not-allowed.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/a/alternates-not-allowed.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: alternates-not-allowed +Severity: error +Check: fields/package-relations +Info: Only the "Depends", "Recommends", "Suggests" and "Pre-Depends" + fields may specify alternate dependencies using the "|" symbol. +Ref: policy 7.1 diff -Nru lintian-2.93.0/tags/a/alternates-not-allowed.tag lintian-2.89.0ubuntu1/tags/a/alternates-not-allowed.tag --- lintian-2.93.0/tags/a/alternates-not-allowed.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/a/alternates-not-allowed.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: alternates-not-allowed -Severity: error -Check: fields/package-relations -Explanation: Only the "Depends", "Recommends", "Suggests" and "Pre-Depends" - fields may specify alternate dependencies using the "|" symbol. -See-Also: policy 7.1 diff -Nru lintian-2.93.0/tags/a/alternatively-build-depends-on-python-sphinx-and-python3-sphinx.desc lintian-2.89.0ubuntu1/tags/a/alternatively-build-depends-on-python-sphinx-and-python3-sphinx.desc --- lintian-2.93.0/tags/a/alternatively-build-depends-on-python-sphinx-and-python3-sphinx.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/a/alternatively-build-depends-on-python-sphinx-and-python3-sphinx.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,12 @@ +Tag: alternatively-build-depends-on-python-sphinx-and-python3-sphinx +Severity: warning +Check: languages/python +Info: This package alternatively Build-Depends on the Python 2 or Python 3 + version of the Sphinx documentation generator. + . + The 2.x series of Python is due for deprecation and will not be maintained + by upstream past 2020 and will likely be dropped after the release of + Debian "buster". + . + Please replace the alternative with a single build dependency on + python3-sphinx. diff -Nru lintian-2.93.0/tags/a/alternatively-build-depends-on-python-sphinx-and-python3-sphinx.tag lintian-2.89.0ubuntu1/tags/a/alternatively-build-depends-on-python-sphinx-and-python3-sphinx.tag --- lintian-2.93.0/tags/a/alternatively-build-depends-on-python-sphinx-and-python3-sphinx.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/a/alternatively-build-depends-on-python-sphinx-and-python3-sphinx.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,12 +0,0 @@ -Tag: alternatively-build-depends-on-python-sphinx-and-python3-sphinx -Severity: warning -Check: languages/python -Explanation: This package alternatively Build-Depends on the Python 2 or Python 3 - version of the Sphinx documentation generator. - . - The 2.x series of Python is due for deprecation and will not be maintained - by upstream past 2020 and will likely be dropped after the release of - Debian "buster". - . - Please replace the alternative with a single build dependency on - python3-sphinx. diff -Nru lintian-2.93.0/tags/a/ambiguous-paragraph-in-dep5-copyright.desc lintian-2.89.0ubuntu1/tags/a/ambiguous-paragraph-in-dep5-copyright.desc --- lintian-2.93.0/tags/a/ambiguous-paragraph-in-dep5-copyright.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/a/ambiguous-paragraph-in-dep5-copyright.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,20 @@ +Tag: ambiguous-paragraph-in-dep5-copyright +Severity: warning +Certainty: possible +Check: debian/copyright/dep5 +Ref: #652380, https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ +Info: The paragraph has a "License" and a "Copyright" field, but no + "Files" field. Technically, this is a valid paragraph per the DEP 5 + specification. However, it is mostly likely a mistake. + . + If it is a stand-alone license paragraph, the "Copyright" + field is not needed and should be removed. On the other hand, if it + is a files paragraph, it is missing the "Files" field. + . + Please note that while the "Files" field was optional in some cases + in some of the earlier draft versions, it is mandatory in all + files paragraphs in the current specification. + . + Lintian will attempt to guess what you intended and continue based on + its guess. If the guess is wrong, you may see spurious tags related + to this paragraph. diff -Nru lintian-2.93.0/tags/a/ambiguous-paragraph-in-dep5-copyright.tag lintian-2.89.0ubuntu1/tags/a/ambiguous-paragraph-in-dep5-copyright.tag --- lintian-2.93.0/tags/a/ambiguous-paragraph-in-dep5-copyright.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/a/ambiguous-paragraph-in-dep5-copyright.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,19 +0,0 @@ -Tag: ambiguous-paragraph-in-dep5-copyright -Severity: warning -Check: debian/copyright/dep5 -See-Also: Bug#652380, https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ -Explanation: The paragraph has a "License" and a "Copyright" field, but no - "Files" field. Technically, this is a valid paragraph per the DEP 5 - specification. However, it is mostly likely a mistake. - . - If it is a stand-alone license paragraph, the "Copyright" - field is not needed and should be removed. On the other hand, if it - is a files paragraph, it is missing the "Files" field. - . - Please note that while the "Files" field was optional in some cases - in some of the earlier draft versions, it is mandatory in *all* - files paragraphs in the current specification. - . - Lintian will attempt to guess what you intended and continue based on - its guess. If the guess is wrong, you may see spurious tags related - to this paragraph. diff -Nru lintian-2.93.0/tags/a/ancient-libtool.desc lintian-2.89.0ubuntu1/tags/a/ancient-libtool.desc --- lintian-2.93.0/tags/a/ancient-libtool.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/a/ancient-libtool.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,25 @@ +Tag: ancient-libtool +Severity: warning +Certainty: possible +Check: cruft +Info: The referenced file seems to be from a libtool version older than + 1.5.2-2. This might lead to build errors on some newer architectures not + known to this libtool. + . + Please ask your upstream maintainer to re-libtoolize the package or do it + yourself if there is no active upstream. You will also need to run + Autoconf to regenerate the configure script. Usually it is best to do + this during the build by depending on autoconf, libtool, and automake if + it is used, and then running: + . + autoreconf -i --force + . + before running configure. Depending on how old the package is, this may + require additional modifications to configure.ac or + configure.in or other work. If you do this during the build, + determine which files it will add or update and be sure to remove those + files in the clean target. + . + If you have fixed architecture-specific issues with minimal patches, + rather than updating libtool, and verified that it builds correctly, + please override this tag. Lintian will not be able to verify that. diff -Nru lintian-2.93.0/tags/a/ancient-libtool.tag lintian-2.89.0ubuntu1/tags/a/ancient-libtool.tag --- lintian-2.93.0/tags/a/ancient-libtool.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/a/ancient-libtool.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,24 +0,0 @@ -Tag: ancient-libtool -Severity: warning -Check: cruft -Explanation: The referenced file seems to be from a libtool version older than - 1.5.2-2. This might lead to build errors on some newer architectures not - known to this libtool. - . - Please ask your upstream maintainer to re-libtoolize the package or do it - yourself if there is no active upstream. You will also need to run - Autoconf to regenerate the configure script. Usually it is best to do - this during the build by depending on autoconf, libtool, and automake if - it is used, and then running: - . - autoreconf -i --force - . - before running configure. Depending on how old the package is, this may - require additional modifications to configure.ac or - configure.in or other work. If you do this during the build, - determine which files it will add or update and be sure to remove those - files in the clean target. - . - If you have fixed architecture-specific issues with minimal patches, - rather than updating libtool, and verified that it builds correctly, - please override this tag. Lintian will not be able to verify that. diff -Nru lintian-2.93.0/tags/a/ancient-python-version-field.desc lintian-2.89.0ubuntu1/tags/a/ancient-python-version-field.desc --- lintian-2.93.0/tags/a/ancient-python-version-field.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/a/ancient-python-version-field.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,14 @@ +Tag: ancient-python-version-field +Severity: warning +Check: languages/python +Ref: python-policy 3.4 +Info: The specified Python-Version or Python3-Version field is used to + specify the version(s) of Python the package supports. However, the + associated Python version is satisfied by the current "oldstable" + distribution of Debian and is therefore unnecessary. + . + Please remove or update the reference. If removing, please also check + for the use of py3versions -r in debian/rules, and + debian/tests/. Without an operative Python3-Version + field py3versions will fall back to all supported versions + which may not be appropriate. diff -Nru lintian-2.93.0/tags/a/ancient-python-version-field.tag lintian-2.89.0ubuntu1/tags/a/ancient-python-version-field.tag --- lintian-2.93.0/tags/a/ancient-python-version-field.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/a/ancient-python-version-field.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,14 +0,0 @@ -Tag: ancient-python-version-field -Severity: warning -Check: languages/python -See-Also: python-policy 3.4 -Explanation: The specified Python-Version or Python3-Version field is used to - specify the version(s) of Python the package supports. However, the - associated Python version is satisfied by the current "oldstable" - distribution of Debian and is therefore unnecessary. - . - Please remove or update the reference. If removing, please also check - for the use of py3versions -r in debian/rules, and - debian/tests/. Without an operative Python3-Version - field py3versions will fall back to all supported versions - which may not be appropriate. diff -Nru lintian-2.93.0/tags/a/ancient-standards-version.desc lintian-2.89.0ubuntu1/tags/a/ancient-standards-version.desc --- lintian-2.93.0/tags/a/ancient-standards-version.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/a/ancient-standards-version.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,16 @@ +Tag: ancient-standards-version +Severity: warning +Check: fields/standards-version +Ref: https://www.debian.org/doc/debian-policy/upgrading-checklist.html +Info: The source package refers to a Standards-Version that has been + obsolete for more than two years. Please update your package to latest + Policy and set this control field appropriately. + . + If the package is already compliant with the current standards, you don't + have to re-upload the package just to adjust the Standards-Version + control field. However, please remember to update this field next time + you upload the package. + . + See /usr/share/doc/debian-policy/upgrading-checklist.txt.gz in + the debian-policy package for a summary of changes in newer versions of + Policy. diff -Nru lintian-2.93.0/tags/a/ancient-standards-version.tag lintian-2.89.0ubuntu1/tags/a/ancient-standards-version.tag --- lintian-2.93.0/tags/a/ancient-standards-version.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/a/ancient-standards-version.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,16 +0,0 @@ -Tag: ancient-standards-version -Severity: warning -Check: fields/standards-version -See-Also: https://www.debian.org/doc/debian-policy/upgrading-checklist.html -Explanation: The source package refers to a Standards-Version that has been - obsolete for more than two years. Please update your package to latest - Policy and set this control field appropriately. - . - If the package is already compliant with the current standards, you don't - have to re-upload the package just to adjust the Standards-Version - control field. However, please remember to update this field next time - you upload the package. - . - See /usr/share/doc/debian-policy/upgrading-checklist.txt.gz in - the debian-policy package for a summary of changes in newer versions of - Policy. diff -Nru lintian-2.93.0/tags/a/ansi-escape.desc lintian-2.89.0ubuntu1/tags/a/ansi-escape.desc --- lintian-2.93.0/tags/a/ansi-escape.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/a/ansi-escape.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,4 @@ +Tag: ansi-escape +Severity: warning +Check: fields/terminal-control +Info: A control field contains an ANSI terminal escape code. diff -Nru lintian-2.93.0/tags/a/ansi-escape.tag lintian-2.89.0ubuntu1/tags/a/ansi-escape.tag --- lintian-2.93.0/tags/a/ansi-escape.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/a/ansi-escape.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,4 +0,0 @@ -Tag: ansi-escape -Severity: warning -Check: fields/terminal-control -Explanation: A control field contains an ANSI terminal escape code. diff -Nru lintian-2.93.0/tags/a/apache2-configuration-files-need-conf-suffix.desc lintian-2.89.0ubuntu1/tags/a/apache2-configuration-files-need-conf-suffix.desc --- lintian-2.93.0/tags/a/apache2-configuration-files-need-conf-suffix.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/a/apache2-configuration-files-need-conf-suffix.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: apache2-configuration-files-need-conf-suffix +Severity: error +Check: apache2 +Info: The package is installing an Apache2 configuration but that file does not + end with a '.conf' suffix. Starting with Apache2 2.4 all configuration + files except module '.load' files need that suffix or are ignored otherwise. diff -Nru lintian-2.93.0/tags/a/apache2-configuration-files-need-conf-suffix.tag lintian-2.89.0ubuntu1/tags/a/apache2-configuration-files-need-conf-suffix.tag --- lintian-2.93.0/tags/a/apache2-configuration-files-need-conf-suffix.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/a/apache2-configuration-files-need-conf-suffix.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: apache2-configuration-files-need-conf-suffix -Severity: error -Check: apache2 -Explanation: The package is installing an Apache2 configuration but that file does not - end with a '.conf' suffix. Starting with Apache2 2.4 all configuration - files except module '.load' files need that suffix or are ignored otherwise. diff -Nru lintian-2.93.0/tags/a/apache2-deprecated-auth-config.desc lintian-2.89.0ubuntu1/tags/a/apache2-deprecated-auth-config.desc --- lintian-2.93.0/tags/a/apache2-deprecated-auth-config.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/a/apache2-deprecated-auth-config.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,15 @@ +Tag: apache2-deprecated-auth-config +Severity: warning +Check: apache2 +Info: The package is using some of the deprecated authentication configuration + directives Order, Satisfy, Allow, Deny, <Limit> or <LimitExcept> + . + These do not integrate well with the new authorization scheme of Apache + 2.4 and, in the case of <Limit> and <LimitExcept> have confusing + semantics. The configuration directives should be replaced with a suitable + combination of <RequireAll>, <RequireAny>, Require all, Require local, + Require ip, and Require method. + . + Alternatively, the offending lines can be wrapped between + <IfModule !mod_authz_core.c> ... </IfModule> or + <IfVersion < 2.3> ... </IfVersion> directives. diff -Nru lintian-2.93.0/tags/a/apache2-deprecated-auth-config.tag lintian-2.89.0ubuntu1/tags/a/apache2-deprecated-auth-config.tag --- lintian-2.93.0/tags/a/apache2-deprecated-auth-config.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/a/apache2-deprecated-auth-config.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,15 +0,0 @@ -Tag: apache2-deprecated-auth-config -Severity: warning -Check: apache2 -Explanation: The package is using some of the deprecated authentication configuration - directives Order, Satisfy, Allow, Deny, <Limit> or <LimitExcept> - . - These do not integrate well with the new authorization scheme of Apache - 2.4 and, in the case of <Limit> and <LimitExcept> have confusing - semantics. The configuration directives should be replaced with a suitable - combination of <RequireAll>, <RequireAny>, Require all, Require local, - Require ip, and Require method. - . - Alternatively, the offending lines can be wrapped between - <IfModule !mod_authz_core.c> ... </IfModule> or - <IfVersion < 2.3> ... </IfVersion> directives. diff -Nru lintian-2.93.0/tags/a/apache2-module-does-not-depend-on-apache2-api.desc lintian-2.89.0ubuntu1/tags/a/apache2-module-does-not-depend-on-apache2-api.desc --- lintian-2.93.0/tags/a/apache2-module-does-not-depend-on-apache2-api.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/a/apache2-module-does-not-depend-on-apache2-api.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: apache2-module-does-not-depend-on-apache2-api +Severity: error +Check: apache2 +Info: The package is an Apache2 HTTPD server module but does not declare a + strong binary relation against the Apache2 server binary it links against. Modules + must depend on the apache2-api-YYYYMMNN package provided as a virtual + package by apache2-bin. diff -Nru lintian-2.93.0/tags/a/apache2-module-does-not-depend-on-apache2-api.tag lintian-2.89.0ubuntu1/tags/a/apache2-module-does-not-depend-on-apache2-api.tag --- lintian-2.93.0/tags/a/apache2-module-does-not-depend-on-apache2-api.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/a/apache2-module-does-not-depend-on-apache2-api.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: apache2-module-does-not-depend-on-apache2-api -Severity: error -Check: apache2 -Explanation: The package is an Apache2 HTTPD server module but does not declare a - strong binary relation against the Apache2 server binary it links against. Modules - must depend on the apache2-api-YYYYMMNN package provided as a virtual - package by apache2-bin. diff -Nru lintian-2.93.0/tags/a/apache2-module-does-not-ship-load-file.desc lintian-2.89.0ubuntu1/tags/a/apache2-module-does-not-ship-load-file.desc --- lintian-2.93.0/tags/a/apache2-module-does-not-ship-load-file.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/a/apache2-module-does-not-ship-load-file.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: apache2-module-does-not-ship-load-file +Severity: error +Check: apache2 +Info: The package is an Apache2 HTTPD server module but does not ship a + ".load" file or it was installed under an unexpected name. The load + files in "/etc/apache2/mods-available" are required to interact with + the server package to enable and disable the module and must match the module + name without "mod_ prefix, e.g. mod_foo must ship a load file + named "foo.load". diff -Nru lintian-2.93.0/tags/a/apache2-module-does-not-ship-load-file.tag lintian-2.89.0ubuntu1/tags/a/apache2-module-does-not-ship-load-file.tag --- lintian-2.93.0/tags/a/apache2-module-does-not-ship-load-file.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/a/apache2-module-does-not-ship-load-file.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: apache2-module-does-not-ship-load-file -Severity: error -Check: apache2 -Explanation: The package is an Apache2 HTTPD server module but does not ship a - ".load" file or it was installed under an unexpected name. The load - files in "/etc/apache2/mods-available" are required to interact with - the server package to enable and disable the module and must match the module - name without "mod_ prefix, e.g. mod_foo must ship a load file - named "foo.load". diff -Nru lintian-2.93.0/tags/a/apache2-reverse-dependency-calls-invoke-rc.d.desc lintian-2.89.0ubuntu1/tags/a/apache2-reverse-dependency-calls-invoke-rc.d.desc --- lintian-2.93.0/tags/a/apache2-reverse-dependency-calls-invoke-rc.d.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/a/apache2-reverse-dependency-calls-invoke-rc.d.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: apache2-reverse-dependency-calls-invoke-rc.d +Severity: warning +Check: apache2 +Info: The package is invoking apache2's init script in its maintainer script + albeit it shouldn't do so. Reverse dependencies installing apache2 + configuration pieces should not restart the web server unconditionally in + maintainer scripts. Instead they should be using apache2-maintscript-helper + which correctly obeys local policies. diff -Nru lintian-2.93.0/tags/a/apache2-reverse-dependency-calls-invoke-rc.d.tag lintian-2.89.0ubuntu1/tags/a/apache2-reverse-dependency-calls-invoke-rc.d.tag --- lintian-2.93.0/tags/a/apache2-reverse-dependency-calls-invoke-rc.d.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/a/apache2-reverse-dependency-calls-invoke-rc.d.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: apache2-reverse-dependency-calls-invoke-rc.d -Severity: warning -Check: apache2 -Explanation: The package is invoking apache2's init script in its maintainer script - albeit it shouldn't do so. Reverse dependencies installing apache2 - configuration pieces should not restart the web server unconditionally in - maintainer scripts. Instead they should be using apache2-maintscript-helper - which correctly obeys local policies. diff -Nru lintian-2.93.0/tags/a/apache2-reverse-dependency-calls-wrapper-script.desc lintian-2.89.0ubuntu1/tags/a/apache2-reverse-dependency-calls-wrapper-script.desc --- lintian-2.93.0/tags/a/apache2-reverse-dependency-calls-wrapper-script.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/a/apache2-reverse-dependency-calls-wrapper-script.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: apache2-reverse-dependency-calls-wrapper-script +Severity: warning +Check: apache2 +Info: The package is calling an Apache2 configuration wrapper script (e.g. + a2enmod, a2enconf, a2enconf, ...). Maintainer + scripts should not be calling these scripts directly. To achieve a uniform and + consolidated behavior these scripts should be invoked indirectly by using + apache2-maintscript-helper. diff -Nru lintian-2.93.0/tags/a/apache2-reverse-dependency-calls-wrapper-script.tag lintian-2.89.0ubuntu1/tags/a/apache2-reverse-dependency-calls-wrapper-script.tag --- lintian-2.93.0/tags/a/apache2-reverse-dependency-calls-wrapper-script.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/a/apache2-reverse-dependency-calls-wrapper-script.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: apache2-reverse-dependency-calls-wrapper-script -Severity: warning -Check: apache2 -Explanation: The package is calling an Apache2 configuration wrapper script (e.g. - a2enmod, a2enconf, a2enconf, ...). Maintainer - scripts should not be calling these scripts directly. To achieve a uniform and - consolidated behavior these scripts should be invoked indirectly by using - apache2-maintscript-helper. diff -Nru lintian-2.93.0/tags/a/apache2-reverse-dependency-ships-file-in-not-allowed-directory.desc lintian-2.89.0ubuntu1/tags/a/apache2-reverse-dependency-ships-file-in-not-allowed-directory.desc --- lintian-2.93.0/tags/a/apache2-reverse-dependency-ships-file-in-not-allowed-directory.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/a/apache2-reverse-dependency-ships-file-in-not-allowed-directory.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: apache2-reverse-dependency-ships-file-in-not-allowed-directory +Severity: error +Check: apache2 +Info: The package installs a piece of Apache2 configuration to + /etc/apache2/{sites,mods,conf}-enabled. This is not allowed. Instead + the respective /etc/apache2/{sites,mods,conf}-available counterparts + must be used. diff -Nru lintian-2.93.0/tags/a/apache2-reverse-dependency-ships-file-in-not-allowed-directory.tag lintian-2.89.0ubuntu1/tags/a/apache2-reverse-dependency-ships-file-in-not-allowed-directory.tag --- lintian-2.93.0/tags/a/apache2-reverse-dependency-ships-file-in-not-allowed-directory.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/a/apache2-reverse-dependency-ships-file-in-not-allowed-directory.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: apache2-reverse-dependency-ships-file-in-not-allowed-directory -Severity: error -Check: apache2 -Explanation: The package installs a piece of Apache2 configuration to - /etc/apache2/{sites,mods,conf}-enabled. This is not allowed. Instead - the respective /etc/apache2/{sites,mods,conf}-available counterparts - must be used. diff -Nru lintian-2.93.0/tags/a/apache2-reverse-dependency-uses-obsolete-directory.desc lintian-2.89.0ubuntu1/tags/a/apache2-reverse-dependency-uses-obsolete-directory.desc --- lintian-2.93.0/tags/a/apache2-reverse-dependency-uses-obsolete-directory.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/a/apache2-reverse-dependency-uses-obsolete-directory.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: apache2-reverse-dependency-uses-obsolete-directory +Severity: warning +Check: apache2 +Info: The package is installing a file into the obsolete + /etc/apache2/conf.d/ directory. This file is not read by the Apache2 + 2.4 web server anymore. Instead /etc/apache2/conf-available/ should be + used. diff -Nru lintian-2.93.0/tags/a/apache2-reverse-dependency-uses-obsolete-directory.tag lintian-2.89.0ubuntu1/tags/a/apache2-reverse-dependency-uses-obsolete-directory.tag --- lintian-2.93.0/tags/a/apache2-reverse-dependency-uses-obsolete-directory.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/a/apache2-reverse-dependency-uses-obsolete-directory.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: apache2-reverse-dependency-uses-obsolete-directory -Severity: warning -Check: apache2 -Explanation: The package is installing a file into the obsolete - /etc/apache2/conf.d/ directory. This file is not read by the Apache2 - 2.4 web server anymore. Instead /etc/apache2/conf-available/ should be - used. diff -Nru lintian-2.93.0/tags/a/apache2-unparsable-dependency.desc lintian-2.89.0ubuntu1/tags/a/apache2-unparsable-dependency.desc --- lintian-2.93.0/tags/a/apache2-unparsable-dependency.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/a/apache2-unparsable-dependency.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: apache2-unparsable-dependency +Severity: warning +Check: apache2 +Info: The package is declaring a module dependency within an Apache + configuration file which does not meet the requirements. Dependencies must be + declared without paths, leading "mod_" prefix and without file + extension. diff -Nru lintian-2.93.0/tags/a/apache2-unparsable-dependency.tag lintian-2.89.0ubuntu1/tags/a/apache2-unparsable-dependency.tag --- lintian-2.93.0/tags/a/apache2-unparsable-dependency.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/a/apache2-unparsable-dependency.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: apache2-unparsable-dependency -Severity: warning -Check: apache2 -Explanation: The package is declaring a module dependency within an Apache - configuration file which does not meet the requirements. Dependencies must be - declared without paths, leading "mod_" prefix and without file - extension. diff -Nru lintian-2.93.0/tags/a/apache2-unsupported-dependency.desc lintian-2.89.0ubuntu1/tags/a/apache2-unsupported-dependency.desc --- lintian-2.93.0/tags/a/apache2-unsupported-dependency.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/a/apache2-unsupported-dependency.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: apache2-unsupported-dependency +Severity: warning +Check: apache2 +Info: The package is declaring a module dependency within an Apache + configuration file which is not supported there. Dependencies are supported in + module '.load' files, and web application '.conf' files, + conflicts in '.load files only. diff -Nru lintian-2.93.0/tags/a/apache2-unsupported-dependency.tag lintian-2.89.0ubuntu1/tags/a/apache2-unsupported-dependency.tag --- lintian-2.93.0/tags/a/apache2-unsupported-dependency.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/a/apache2-unsupported-dependency.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: apache2-unsupported-dependency -Severity: warning -Check: apache2 -Explanation: The package is declaring a module dependency within an Apache - configuration file which is not supported there. Dependencies are supported in - module '.load' files, and web application '.conf' files, - conflicts in '.load files only. diff -Nru lintian-2.93.0/tags/a/apparently-corrupted-elf-binary.desc lintian-2.89.0ubuntu1/tags/a/apparently-corrupted-elf-binary.desc --- lintian-2.93.0/tags/a/apparently-corrupted-elf-binary.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/a/apparently-corrupted-elf-binary.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: apparently-corrupted-elf-binary +Severity: warning +Certainty: possible +Check: binaries +Info: This appears to be an ELF file but readelf cannot parse it. + . + This may be a mistake or a corrupted file, you may need to + install binutils-multiarch on the system running Lintian so that + non-native binaries are handled correctly, or it may be a + misidentification of a file as ELF that actually isn't. diff -Nru lintian-2.93.0/tags/a/apparently-corrupted-elf-binary.tag lintian-2.89.0ubuntu1/tags/a/apparently-corrupted-elf-binary.tag --- lintian-2.93.0/tags/a/apparently-corrupted-elf-binary.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/a/apparently-corrupted-elf-binary.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: apparently-corrupted-elf-binary -Severity: warning -Check: binaries -Explanation: This appears to be an ELF file but readelf cannot parse it. - . - This may be a mistake or a corrupted file, you may need to - install binutils-multiarch on the system running Lintian so that - non-native binaries are handled correctly, or it may be a - misidentification of a file as ELF that actually isn't. diff -Nru lintian-2.93.0/tags/a/application-in-library-section.desc lintian-2.89.0ubuntu1/tags/a/application-in-library-section.desc --- lintian-2.93.0/tags/a/application-in-library-section.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/a/application-in-library-section.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,16 @@ +Tag: application-in-library-section +Severity: info +Certainty: wild-guess +Check: application-not-library +Experimental: yes +Info: This package contains a binary in $PATH but is in a section just + thought for libraries. It likely should be in another section like + e.g. utils, text, devel, misc, etc., but not in e.g. perl, ruby or + python. + . + People tend to skip these package sections when looking for + applications in the package list and hence wouldn't notice this + package. + . + In case the program in $PATH is only a helper tool and the package is + primarily a library, please add a Lintian override for this tag. diff -Nru lintian-2.93.0/tags/a/application-in-library-section.tag lintian-2.89.0ubuntu1/tags/a/application-in-library-section.tag --- lintian-2.93.0/tags/a/application-in-library-section.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/a/application-in-library-section.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,15 +0,0 @@ -Tag: application-in-library-section -Severity: info -Check: application-not-library -Experimental: yes -Explanation: This package contains a binary in $PATH but is in a section just - thought for libraries. It likely should be in another section like - e.g. utils, text, devel, misc, etc., but not in e.g. perl, ruby or - python. - . - People tend to skip these package sections when looking for - applications in the package list and hence wouldn't notice this - package. - . - In case the program in $PATH is only a helper tool and the package is - primarily a library, please add a Lintian override for this tag. diff -Nru lintian-2.93.0/tags/a/appstream-metadata-in-legacy-location.desc lintian-2.89.0ubuntu1/tags/a/appstream-metadata-in-legacy-location.desc --- lintian-2.93.0/tags/a/appstream-metadata-in-legacy-location.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/a/appstream-metadata-in-legacy-location.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: appstream-metadata-in-legacy-location +Severity: warning +Check: appstream-metadata +Ref: https://wiki.debian.org/AppStream/Guidelines +Info: AppStream metadata file was found in /usr/share/appdata/. The + AppStream XML files should be placed in /usr/share/metainfo/. diff -Nru lintian-2.93.0/tags/a/appstream-metadata-in-legacy-location.tag lintian-2.89.0ubuntu1/tags/a/appstream-metadata-in-legacy-location.tag --- lintian-2.93.0/tags/a/appstream-metadata-in-legacy-location.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/a/appstream-metadata-in-legacy-location.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: appstream-metadata-in-legacy-location -Severity: warning -Check: appstream-metadata -See-Also: https://wiki.debian.org/AppStream/Guidelines -Explanation: AppStream metadata file was found in /usr/share/appdata/. The - AppStream XML files should be placed in /usr/share/metainfo/. diff -Nru lintian-2.93.0/tags/a/appstream-metadata-invalid.desc lintian-2.89.0ubuntu1/tags/a/appstream-metadata-invalid.desc --- lintian-2.93.0/tags/a/appstream-metadata-invalid.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/a/appstream-metadata-invalid.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: appstream-metadata-invalid +Severity: error +Check: appstream-metadata +Ref: https://wiki.debian.org/AppStream/Guidelines +Info: The specified AppStream metadata file does not consist of + valid XML. diff -Nru lintian-2.93.0/tags/a/appstream-metadata-invalid.tag lintian-2.89.0ubuntu1/tags/a/appstream-metadata-invalid.tag --- lintian-2.93.0/tags/a/appstream-metadata-invalid.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/a/appstream-metadata-invalid.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: appstream-metadata-invalid -Severity: error -Check: appstream-metadata -See-Also: https://wiki.debian.org/AppStream/Guidelines -Explanation: The specified AppStream metadata file does not consist of - valid XML. diff -Nru lintian-2.93.0/tags/a/appstream-metadata-legacy-format.desc lintian-2.89.0ubuntu1/tags/a/appstream-metadata-legacy-format.desc --- lintian-2.93.0/tags/a/appstream-metadata-legacy-format.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/a/appstream-metadata-legacy-format.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: appstream-metadata-legacy-format +Severity: error +Check: appstream-metadata +Ref: https://wiki.debian.org/AppStream/Guidelines, + https://www.freedesktop.org/software/appstream/docs/chap-Metadata.html#sect-Metadata-GenericComponent +Info: AppStream metadata with obsolete <application> root node found. + This indicate a legacy format. The metadata should follow the format + the new outlined on the freedesktop.org homepage. + . + It is possible to validate the format using 'appstreamcli validate'. diff -Nru lintian-2.93.0/tags/a/appstream-metadata-legacy-format.tag lintian-2.89.0ubuntu1/tags/a/appstream-metadata-legacy-format.tag --- lintian-2.93.0/tags/a/appstream-metadata-legacy-format.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/a/appstream-metadata-legacy-format.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,10 +0,0 @@ -Tag: appstream-metadata-legacy-format -Severity: error -Check: appstream-metadata -See-Also: https://wiki.debian.org/AppStream/Guidelines, - https://www.freedesktop.org/software/appstream/docs/chap-Metadata.html#sect-Metadata-GenericComponent -Explanation: AppStream metadata with obsolete <application> root node found. - This indicate a legacy format. The metadata should follow the format - the new outlined on the freedesktop.org homepage. - . - It is possible to validate the format using 'appstreamcli validate'. diff -Nru lintian-2.93.0/tags/a/appstream-metadata-malformed-modalias-provide.desc lintian-2.89.0ubuntu1/tags/a/appstream-metadata-malformed-modalias-provide.desc --- lintian-2.93.0/tags/a/appstream-metadata-malformed-modalias-provide.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/a/appstream-metadata-malformed-modalias-provide.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: appstream-metadata-malformed-modalias-provide +Severity: warning +Check: appstream-metadata +Ref: https://wiki.debian.org/AppStream/Guidelines +Info: The modalias matching rule in the AppStream metadata file is + malformed. Hexadecimal numbers in vendor and product IDs must be + upper case. diff -Nru lintian-2.93.0/tags/a/appstream-metadata-malformed-modalias-provide.tag lintian-2.89.0ubuntu1/tags/a/appstream-metadata-malformed-modalias-provide.tag --- lintian-2.93.0/tags/a/appstream-metadata-malformed-modalias-provide.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/a/appstream-metadata-malformed-modalias-provide.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: appstream-metadata-malformed-modalias-provide -Severity: warning -Check: appstream-metadata -See-Also: https://wiki.debian.org/AppStream/Guidelines -Explanation: The modalias matching rule in the AppStream metadata file is - malformed. Hexadecimal numbers in vendor and product IDs must be - upper case. diff -Nru lintian-2.93.0/tags/a/appstream-metadata-missing-modalias-provide.desc lintian-2.89.0ubuntu1/tags/a/appstream-metadata-missing-modalias-provide.desc --- lintian-2.93.0/tags/a/appstream-metadata-missing-modalias-provide.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/a/appstream-metadata-missing-modalias-provide.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: appstream-metadata-missing-modalias-provide +Severity: warning +Check: appstream-metadata +Ref: https://wiki.debian.org/AppStream/Guidelines +Info: This package contain a udev rule for providing device access to + the console user (using the uaccess udev TAG) or to members of the + plugdev file group without announcing the hardware support using + AppStream. diff -Nru lintian-2.93.0/tags/a/appstream-metadata-missing-modalias-provide.tag lintian-2.89.0ubuntu1/tags/a/appstream-metadata-missing-modalias-provide.tag --- lintian-2.93.0/tags/a/appstream-metadata-missing-modalias-provide.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/a/appstream-metadata-missing-modalias-provide.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: appstream-metadata-missing-modalias-provide -Severity: warning -Check: appstream-metadata -See-Also: https://wiki.debian.org/AppStream/Guidelines -Explanation: This package contain a udev rule for providing device access to - the console user (using the uaccess udev TAG) or to members of the - plugdev file group without announcing the hardware support using - AppStream. diff -Nru lintian-2.93.0/tags/a/arch-dependent-file-in-usr-share.desc lintian-2.89.0ubuntu1/tags/a/arch-dependent-file-in-usr-share.desc --- lintian-2.93.0/tags/a/arch-dependent-file-in-usr-share.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/a/arch-dependent-file-in-usr-share.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: arch-dependent-file-in-usr-share +Severity: error +Check: binaries +Ref: fhs usrsharearchitectureindependentdata +Info: This package installs an ELF binary in the /usr/share + hierarchy, which is reserved for architecture-independent files. diff -Nru lintian-2.93.0/tags/a/arch-dependent-file-in-usr-share.tag lintian-2.89.0ubuntu1/tags/a/arch-dependent-file-in-usr-share.tag --- lintian-2.93.0/tags/a/arch-dependent-file-in-usr-share.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/a/arch-dependent-file-in-usr-share.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: arch-dependent-file-in-usr-share -Severity: error -Check: binaries -See-Also: fhs usrsharearchitectureindependentdata -Explanation: This package installs an ELF binary in the /usr/share - hierarchy, which is reserved for architecture-independent files. diff -Nru lintian-2.93.0/tags/a/arch-dependent-file-not-in-arch-specific-directory.desc lintian-2.89.0ubuntu1/tags/a/arch-dependent-file-not-in-arch-specific-directory.desc --- lintian-2.93.0/tags/a/arch-dependent-file-not-in-arch-specific-directory.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/a/arch-dependent-file-not-in-arch-specific-directory.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: arch-dependent-file-not-in-arch-specific-directory +Severity: error +Certainty: possible +Check: binaries +Ref: https://wiki.ubuntu.com/MultiarchSpec +Info: This package is Multi-Arch "same", but it installs an ELF binary in the + directory that is not architecture-specific. diff -Nru lintian-2.93.0/tags/a/arch-dependent-file-not-in-arch-specific-directory.tag lintian-2.89.0ubuntu1/tags/a/arch-dependent-file-not-in-arch-specific-directory.tag --- lintian-2.93.0/tags/a/arch-dependent-file-not-in-arch-specific-directory.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/a/arch-dependent-file-not-in-arch-specific-directory.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: arch-dependent-file-not-in-arch-specific-directory -Severity: error -Check: binaries -See-Also: https://wiki.ubuntu.com/MultiarchSpec -Explanation: This package is Multi-Arch "same", but it installs an ELF binary in the - directory that is not architecture-specific. diff -Nru lintian-2.93.0/tags/a/arch-dep-package-has-big-usr-share.desc lintian-2.89.0ubuntu1/tags/a/arch-dep-package-has-big-usr-share.desc --- lintian-2.93.0/tags/a/arch-dep-package-has-big-usr-share.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/a/arch-dep-package-has-big-usr-share.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,13 @@ +Tag: arch-dep-package-has-big-usr-share +Severity: info +Check: huge-usr-share +Info: The package has a significant amount of architecture-independent + data (over 4MB, or over 2MB and more than 50% of the package) in + /usr/share but is an architecture-dependent package. This is + wasteful of mirror space and bandwidth since it means distributing + multiple copies of this data, one for each architecture. + . + If the data in /usr/share is not architecture-independent, this + is a Policy violation that should be fixed by moving the data elsewhere + (usually /usr/lib). +Ref: devref 6.7.5 diff -Nru lintian-2.93.0/tags/a/arch-dep-package-has-big-usr-share.tag lintian-2.89.0ubuntu1/tags/a/arch-dep-package-has-big-usr-share.tag --- lintian-2.93.0/tags/a/arch-dep-package-has-big-usr-share.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/a/arch-dep-package-has-big-usr-share.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,13 +0,0 @@ -Tag: arch-dep-package-has-big-usr-share -Severity: info -Check: huge-usr-share -Explanation: The package has a significant amount of architecture-independent - data (over 4MB, or over 2MB and more than 50% of the package) in - /usr/share but is an architecture-dependent package. This is - wasteful of mirror space and bandwidth since it means distributing - multiple copies of this data, one for each architecture. - . - If the data in /usr/share is not architecture-independent, this - is a Policy violation that should be fixed by moving the data elsewhere - (usually /usr/lib). -See-Also: devref 6.7.5 diff -Nru lintian-2.93.0/tags/a/arch-independent-package-contains-binary-or-object.desc lintian-2.89.0ubuntu1/tags/a/arch-independent-package-contains-binary-or-object.desc --- lintian-2.93.0/tags/a/arch-independent-package-contains-binary-or-object.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/a/arch-independent-package-contains-binary-or-object.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: arch-independent-package-contains-binary-or-object +Severity: error +Certainty: possible +Check: binaries +Info: The package contains a binary or object file but is tagged + Architecture: all. + . + If this package contains binaries or objects for cross-compiling or + binary blobs for other purposes independent of the host architecture + (such as BIOS updates or firmware), please add a Lintian override. diff -Nru lintian-2.93.0/tags/a/arch-independent-package-contains-binary-or-object.tag lintian-2.89.0ubuntu1/tags/a/arch-independent-package-contains-binary-or-object.tag --- lintian-2.93.0/tags/a/arch-independent-package-contains-binary-or-object.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/a/arch-independent-package-contains-binary-or-object.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: arch-independent-package-contains-binary-or-object -Severity: error -Check: binaries -Explanation: The package contains a binary or object file but is tagged - Architecture: all. - . - If this package contains binaries or objects for cross-compiling or - binary blobs for other purposes independent of the host architecture - (such as BIOS updates or firmware), please add a Lintian override. diff -Nru lintian-2.93.0/tags/a/arch-wildcard-in-binary-package.desc lintian-2.89.0ubuntu1/tags/a/arch-wildcard-in-binary-package.desc --- lintian-2.93.0/tags/a/arch-wildcard-in-binary-package.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/a/arch-wildcard-in-binary-package.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: arch-wildcard-in-binary-package +Severity: error +Check: fields/architecture +Info: Architecture wildcards, including the special architecture value + "any", do not make sense in a binary package. A binary package must + either be architecture-independent or built for a specific architecture. +Ref: policy 5.6.8 diff -Nru lintian-2.93.0/tags/a/arch-wildcard-in-binary-package.tag lintian-2.89.0ubuntu1/tags/a/arch-wildcard-in-binary-package.tag --- lintian-2.93.0/tags/a/arch-wildcard-in-binary-package.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/a/arch-wildcard-in-binary-package.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: arch-wildcard-in-binary-package -Severity: error -Check: fields/architecture -Explanation: Architecture wildcards, including the special architecture value - "any", do not make sense in a binary package. A binary package must - either be architecture-independent or built for a specific architecture. -See-Also: policy 5.6.8 diff -Nru lintian-2.93.0/tags/a/aspell-package-not-arch-all.desc lintian-2.89.0ubuntu1/tags/a/aspell-package-not-arch-all.desc --- lintian-2.93.0/tags/a/aspell-package-not-arch-all.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/a/aspell-package-not-arch-all.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: aspell-package-not-arch-all +Severity: warning +Check: fields/architecture +Info: This package appears to be an aspell dictionary package, but it is + not Architecture: all. The binary hashes should be built at install-time + by calling aspell-autobuildhash, so the contents of the package should be + architecture-independent. +Ref: aspell-autobuildhash(8) diff -Nru lintian-2.93.0/tags/a/aspell-package-not-arch-all.tag lintian-2.89.0ubuntu1/tags/a/aspell-package-not-arch-all.tag --- lintian-2.93.0/tags/a/aspell-package-not-arch-all.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/a/aspell-package-not-arch-all.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: aspell-package-not-arch-all -Severity: warning -Check: fields/architecture -Explanation: This package appears to be an aspell dictionary package, but it is - not Architecture: all. The binary hashes should be built at install-time - by calling aspell-autobuildhash, so the contents of the package should be - architecture-independent. -See-Also: aspell-autobuildhash(8) diff -Nru lintian-2.93.0/tags/a/autotools-pkg-config-macro-not-cross-compilation-safe.desc lintian-2.89.0ubuntu1/tags/a/autotools-pkg-config-macro-not-cross-compilation-safe.desc --- lintian-2.93.0/tags/a/autotools-pkg-config-macro-not-cross-compilation-safe.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/a/autotools-pkg-config-macro-not-cross-compilation-safe.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,11 @@ +Tag: autotools-pkg-config-macro-not-cross-compilation-safe +Severity: warning +Certainty: possible +Check: cruft +Info: The package appears to use AC_PATH_PROG to discover the + location of pkg-config(1). This macro fails to select the correct + version to support cross-compilation. + . + A better way would be to use the PKG_PROG_PKG_CONFIG macro from + pkg.m4 and then using the $PKG_CONFIG shell variable. +Ref: #884798 diff -Nru lintian-2.93.0/tags/a/autotools-pkg-config-macro-not-cross-compilation-safe.tag lintian-2.89.0ubuntu1/tags/a/autotools-pkg-config-macro-not-cross-compilation-safe.tag --- lintian-2.93.0/tags/a/autotools-pkg-config-macro-not-cross-compilation-safe.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/a/autotools-pkg-config-macro-not-cross-compilation-safe.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,10 +0,0 @@ -Tag: autotools-pkg-config-macro-not-cross-compilation-safe -Severity: warning -Check: cruft -Explanation: The package appears to use AC_PATH_PROG to discover the - location of pkg-config(1). This macro fails to select the correct - version to support cross-compilation. - . - A better way would be to use the PKG_PROG_PKG_CONFIG macro from - pkg.m4 and then using the $PKG_CONFIG shell variable. -See-Also: Bug#884798 diff -Nru lintian-2.93.0/tags/b/backports-changes-missing.desc lintian-2.89.0ubuntu1/tags/b/backports-changes-missing.desc --- lintian-2.93.0/tags/b/backports-changes-missing.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/backports-changes-missing.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: backports-changes-missing +Severity: info +Certainty: possible +Check: fields/distribution +Info: The changes file only has changelog entries from a single version. It + is recommended for backports to include all changes since (old)stable or + the previous backport. This can be done by adding the '-v' option to the + build with the appropriate version. +Ref: http://backports.debian.org/Contribute/, #785084 diff -Nru lintian-2.93.0/tags/b/backports-changes-missing.tag lintian-2.89.0ubuntu1/tags/b/backports-changes-missing.tag --- lintian-2.93.0/tags/b/backports-changes-missing.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/backports-changes-missing.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: backports-changes-missing -Severity: info -Check: fields/distribution -Explanation: The changes file only has changelog entries from a single version. It - is recommended for backports to include all changes since (old)stable or - the previous backport. This can be done by adding the '-v' option to the - build with the appropriate version. -See-Also: http://backports.debian.org/Contribute/, Bug#785084 diff -Nru lintian-2.93.0/tags/b/backports-upload-has-incorrect-version-number.desc lintian-2.89.0ubuntu1/tags/b/backports-upload-has-incorrect-version-number.desc --- lintian-2.93.0/tags/b/backports-upload-has-incorrect-version-number.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/backports-upload-has-incorrect-version-number.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: backports-upload-has-incorrect-version-number +Severity: error +Check: fields/distribution +Info: The version number doesn't comply with the standard backport version + rules. It should end in ~bpoX+N, where X is the release version number of + the target distribution. +Ref: http://backports.debian.org/Contribute/ diff -Nru lintian-2.93.0/tags/b/backports-upload-has-incorrect-version-number.tag lintian-2.89.0ubuntu1/tags/b/backports-upload-has-incorrect-version-number.tag --- lintian-2.93.0/tags/b/backports-upload-has-incorrect-version-number.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/backports-upload-has-incorrect-version-number.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: backports-upload-has-incorrect-version-number -Severity: error -Check: fields/distribution -Explanation: The version number doesn't comply with the standard backport version - rules. It should end in ~bpoX+N, where X is the release version number of - the target distribution. -See-Also: http://backports.debian.org/Contribute/ diff -Nru lintian-2.93.0/tags/b/backup-file-in-package.desc lintian-2.89.0ubuntu1/tags/b/backup-file-in-package.desc --- lintian-2.93.0/tags/b/backup-file-in-package.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/backup-file-in-package.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: backup-file-in-package +Severity: warning +Check: files/unwanted +Info: There is a file in the package whose name matches the format emacs + or vim uses for backup and autosave files. It may have been installed by + accident. diff -Nru lintian-2.93.0/tags/b/backup-file-in-package.tag lintian-2.89.0ubuntu1/tags/b/backup-file-in-package.tag --- lintian-2.93.0/tags/b/backup-file-in-package.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/backup-file-in-package.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: backup-file-in-package -Severity: warning -Check: files/unwanted -Explanation: There is a file in the package whose name matches the format emacs - or vim uses for backup and autosave files. It may have been installed by - accident. diff -Nru lintian-2.93.0/tags/b/bad-distribution-in-changes-file.desc lintian-2.89.0ubuntu1/tags/b/bad-distribution-in-changes-file.desc --- lintian-2.93.0/tags/b/bad-distribution-in-changes-file.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/bad-distribution-in-changes-file.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,12 @@ +Tag: bad-distribution-in-changes-file +Severity: error +Check: fields/distribution +Info: You've specified an unknown target distribution for your upload in + the debian/changelog file. It is possible that you are uploading + for a different distribution than the one Lintian is checking for. In + that case, passing --profile $VENDOR may fix this warning. + . + Note that the distributions non-free and contrib are no + longer valid. You'll have to use distribution unstable and + Section: non-free/xxx or Section: contrib/xxx instead. +Ref: policy 5.6.14 diff -Nru lintian-2.93.0/tags/b/bad-distribution-in-changes-file.tag lintian-2.89.0ubuntu1/tags/b/bad-distribution-in-changes-file.tag --- lintian-2.93.0/tags/b/bad-distribution-in-changes-file.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/bad-distribution-in-changes-file.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,12 +0,0 @@ -Tag: bad-distribution-in-changes-file -Severity: error -Check: fields/distribution -Explanation: You've specified an unknown target distribution for your upload in - the debian/changelog file. It is possible that you are uploading - for a different distribution than the one Lintian is checking for. In - that case, passing --profile $VENDOR may fix this warning. - . - Note that the distributions non-free and contrib are no - longer valid. You'll have to use distribution unstable and - Section: non-free/xxx or Section: contrib/xxx instead. -See-Also: policy 5.6.14 diff -Nru lintian-2.93.0/tags/b/bad-exception-format-in-dep5-copyright.desc lintian-2.89.0ubuntu1/tags/b/bad-exception-format-in-dep5-copyright.desc --- lintian-2.93.0/tags/b/bad-exception-format-in-dep5-copyright.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/bad-exception-format-in-dep5-copyright.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: bad-exception-format-in-dep5-copyright +Severity: warning +Check: debian/copyright/dep5 +Ref: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ +Info: The “License” field contains a short name with a bad exception + format. According to specification format of exception is: + shortlicencename with exceptionname exception. + . + If more than one exception applies to a single license, + an arbitrary short name must be used instead. diff -Nru lintian-2.93.0/tags/b/bad-exception-format-in-dep5-copyright.tag lintian-2.89.0ubuntu1/tags/b/bad-exception-format-in-dep5-copyright.tag --- lintian-2.93.0/tags/b/bad-exception-format-in-dep5-copyright.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/bad-exception-format-in-dep5-copyright.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,10 +0,0 @@ -Tag: bad-exception-format-in-dep5-copyright -Severity: warning -Check: debian/copyright/dep5 -See-Also: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ -Explanation: The “License” field contains a short name with a bad exception - format. According to specification format of exception is: - shortlicencename with exceptionname exception. - . - If more than one exception applies to a single license, - an arbitrary short name must be used instead. diff -Nru lintian-2.93.0/tags/b/bad-homepage.desc lintian-2.89.0ubuntu1/tags/b/bad-homepage.desc --- lintian-2.93.0/tags/b/bad-homepage.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/bad-homepage.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: bad-homepage +Severity: warning +Check: fields/homepage +Info: The "Homepage:" field in this package's control file does not + contain a valid absolute URL. Most probably you forgot to specify + the scheme (e.g. http). + . + This tag is also triggered if the scheme is not known by Lintian. diff -Nru lintian-2.93.0/tags/b/bad-homepage.tag lintian-2.89.0ubuntu1/tags/b/bad-homepage.tag --- lintian-2.93.0/tags/b/bad-homepage.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/bad-homepage.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: bad-homepage -Severity: warning -Check: fields/homepage -Explanation: The "Homepage:" field in this package's control file does not - contain a valid absolute URL. Most probably you forgot to specify - the scheme (e.g. http). - . - This tag is also triggered if the scheme is not known by Lintian. diff -Nru lintian-2.93.0/tags/b/bad-intended-distribution.desc lintian-2.89.0ubuntu1/tags/b/bad-intended-distribution.desc --- lintian-2.93.0/tags/b/bad-intended-distribution.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/bad-intended-distribution.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: bad-intended-distribution +Severity: info +Certainty: wild-guess +Check: debian/changelog +Experimental: yes +Info: The last changelog entry implies this version is not for release. + Instead it should specify the distribution it is to be uploaded to. diff -Nru lintian-2.93.0/tags/b/bad-intended-distribution.tag lintian-2.89.0ubuntu1/tags/b/bad-intended-distribution.tag --- lintian-2.93.0/tags/b/bad-intended-distribution.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/bad-intended-distribution.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: bad-intended-distribution -Severity: info -Check: debian/changelog -Experimental: yes -Explanation: The last changelog entry implies this version is not for release. - Instead it should specify the distribution it is to be uploaded to. diff -Nru lintian-2.93.0/tags/b/bad-jar-name.desc lintian-2.89.0ubuntu1/tags/b/bad-jar-name.desc --- lintian-2.93.0/tags/b/bad-jar-name.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/bad-jar-name.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: bad-jar-name +Severity: warning +Check: languages/java +Info: The package ships the specified "public" Jar file under + /usr/share/java/, but the name does not correspond to Java policy + guidelines. This can cause tools in the Debian Java toolchain to fail. +Ref: java-policy 2.4 diff -Nru lintian-2.93.0/tags/b/bad-jar-name.tag lintian-2.89.0ubuntu1/tags/b/bad-jar-name.tag --- lintian-2.93.0/tags/b/bad-jar-name.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/bad-jar-name.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: bad-jar-name -Severity: warning -Check: languages/java -Explanation: The package ships the specified "public" Jar file under - /usr/share/java/, but the name does not correspond to Java policy - guidelines. This can cause tools in the Debian Java toolchain to fail. -See-Also: java-policy 2.4 diff -Nru lintian-2.93.0/tags/b/bad-menu-file-name.desc lintian-2.89.0ubuntu1/tags/b/bad-menu-file-name.desc --- lintian-2.93.0/tags/b/bad-menu-file-name.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/bad-menu-file-name.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: bad-menu-file-name +Severity: error +Check: menus +Info: The package installs a file /usr/lib/menu/menu, which is + already in use by the menu package itself. The menu file should + be named after the package that installs it. diff -Nru lintian-2.93.0/tags/b/bad-menu-file-name.tag lintian-2.89.0ubuntu1/tags/b/bad-menu-file-name.tag --- lintian-2.93.0/tags/b/bad-menu-file-name.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/bad-menu-file-name.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: bad-menu-file-name -Severity: error -Check: menus -Explanation: The package installs a file /usr/lib/menu/menu, which is - already in use by the menu package itself. The menu file should - be named after the package that installs it. diff -Nru lintian-2.93.0/tags/b/bad-menu-item.desc lintian-2.89.0ubuntu1/tags/b/bad-menu-item.desc --- lintian-2.93.0/tags/b/bad-menu-item.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/bad-menu-item.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,5 @@ +Tag: bad-menu-item +Severity: error +Check: fields/installer-menu-item +Info: The field Installer-Menu-Item should only contain positive integer + values. diff -Nru lintian-2.93.0/tags/b/bad-menu-item.tag lintian-2.89.0ubuntu1/tags/b/bad-menu-item.tag --- lintian-2.93.0/tags/b/bad-menu-item.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/bad-menu-item.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,5 +0,0 @@ -Tag: bad-menu-item -Severity: error -Check: fields/installer-menu-item -Explanation: The field Installer-Menu-Item should only contain positive integer - values. diff -Nru lintian-2.93.0/tags/b/bad-owner-for-doc-file.desc lintian-2.89.0ubuntu1/tags/b/bad-owner-for-doc-file.desc --- lintian-2.93.0/tags/b/bad-owner-for-doc-file.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/bad-owner-for-doc-file.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,4 @@ +Tag: bad-owner-for-doc-file +Severity: error +Check: documentation +Info: Documentation files should be owned by root/root. diff -Nru lintian-2.93.0/tags/b/bad-owner-for-doc-file.tag lintian-2.89.0ubuntu1/tags/b/bad-owner-for-doc-file.tag --- lintian-2.93.0/tags/b/bad-owner-for-doc-file.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/bad-owner-for-doc-file.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,4 +0,0 @@ -Tag: bad-owner-for-doc-file -Severity: error -Check: documentation -Explanation: Documentation files should be owned by root/root. diff -Nru lintian-2.93.0/tags/b/bad-package-name.desc lintian-2.89.0ubuntu1/tags/b/bad-package-name.desc --- lintian-2.93.0/tags/b/bad-package-name.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/bad-package-name.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: bad-package-name +Severity: error +Check: fields/package +Info: A package name should be at least two characters long, must consist + of the alphanumerics and "+" "-" and ".", and must start with an + alphanumeric character. +Ref: policy 5.6.7 diff -Nru lintian-2.93.0/tags/b/bad-package-name.tag lintian-2.89.0ubuntu1/tags/b/bad-package-name.tag --- lintian-2.93.0/tags/b/bad-package-name.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/bad-package-name.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: bad-package-name -Severity: error -Check: fields/package -Explanation: A package name should be at least two characters long, must consist - of the alphanumerics and "+" "-" and ".", and must start with an - alphanumeric character. -See-Also: policy 5.6.7 diff -Nru lintian-2.93.0/tags/b/bad-perm-for-file-in-etc-sudoers.d.desc lintian-2.89.0ubuntu1/tags/b/bad-perm-for-file-in-etc-sudoers.d.desc --- lintian-2.93.0/tags/b/bad-perm-for-file-in-etc-sudoers.d.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/bad-perm-for-file-in-etc-sudoers.d.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: bad-perm-for-file-in-etc-sudoers.d +Severity: error +Check: files/permissions +Info: Files in /etc/sudoers.d/ must be 0440 or sudo will refuse to + parse them. +Ref: #588831, #576527 diff -Nru lintian-2.93.0/tags/b/bad-perm-for-file-in-etc-sudoers.d.tag lintian-2.89.0ubuntu1/tags/b/bad-perm-for-file-in-etc-sudoers.d.tag --- lintian-2.93.0/tags/b/bad-perm-for-file-in-etc-sudoers.d.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/bad-perm-for-file-in-etc-sudoers.d.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: bad-perm-for-file-in-etc-sudoers.d -Severity: error -Check: files/permissions -Explanation: Files in /etc/sudoers.d/ must be 0440 or sudo will refuse to - parse them. -See-Also: Bug#588831, Bug#576527 diff -Nru lintian-2.93.0/tags/b/bad-permissions-for-ali-file.desc lintian-2.89.0ubuntu1/tags/b/bad-permissions-for-ali-file.desc --- lintian-2.93.0/tags/b/bad-permissions-for-ali-file.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/bad-permissions-for-ali-file.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,12 @@ +Tag: bad-permissions-for-ali-file +Severity: warning +Check: files/permissions +Ref: policy 8.4 +Info: Ada Library Information (*.ali) files are required to be read-only + (mode 0444) by GNAT. + . + If at least one user can write the *.ali file, GNAT considers whether + or not to recompile the corresponding source file. Such recompilation + would fail because normal users don't have write permission on the + files. Moreover, such recompilation would defeat the purpose of + library packages, which provide *.a and *.so libraries to link against). diff -Nru lintian-2.93.0/tags/b/bad-permissions-for-ali-file.tag lintian-2.89.0ubuntu1/tags/b/bad-permissions-for-ali-file.tag --- lintian-2.93.0/tags/b/bad-permissions-for-ali-file.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/bad-permissions-for-ali-file.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,12 +0,0 @@ -Tag: bad-permissions-for-ali-file -Severity: warning -Check: files/permissions -See-Also: policy 8.4 -Explanation: Ada Library Information (*.ali) files are required to be read-only - (mode 0444) by GNAT. - . - If at least one user can write the *.ali file, GNAT considers whether - or not to recompile the corresponding source file. Such recompilation - would fail because normal users don't have write permission on the - files. Moreover, such recompilation would defeat the purpose of - library packages, which provide *.a and *.so libraries to link against). diff -Nru lintian-2.93.0/tags/b/bad-permissions-for-etc-cron.d-script.desc lintian-2.89.0ubuntu1/tags/b/bad-permissions-for-etc-cron.d-script.desc --- lintian-2.93.0/tags/b/bad-permissions-for-etc-cron.d-script.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/bad-permissions-for-etc-cron.d-script.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,5 @@ +Tag: bad-permissions-for-etc-cron.d-script +Severity: error +Check: cron +Info: Files in /etc/cron.d are configuration files for cron and not + scripts. Thus, they should not be marked executable. diff -Nru lintian-2.93.0/tags/b/bad-permissions-for-etc-cron.d-script.tag lintian-2.89.0ubuntu1/tags/b/bad-permissions-for-etc-cron.d-script.tag --- lintian-2.93.0/tags/b/bad-permissions-for-etc-cron.d-script.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/bad-permissions-for-etc-cron.d-script.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,5 +0,0 @@ -Tag: bad-permissions-for-etc-cron.d-script -Severity: error -Check: cron -Explanation: Files in /etc/cron.d are configuration files for cron and not - scripts. Thus, they should not be marked executable. diff -Nru lintian-2.93.0/tags/b/bad-permissions-for-etc-emacs-script.desc lintian-2.89.0ubuntu1/tags/b/bad-permissions-for-etc-emacs-script.desc --- lintian-2.93.0/tags/b/bad-permissions-for-etc-emacs-script.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/bad-permissions-for-etc-emacs-script.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,5 @@ +Tag: bad-permissions-for-etc-emacs-script +Severity: error +Check: emacs +Info: Files in the /etc/emacs* directories should not be marked + executable. diff -Nru lintian-2.93.0/tags/b/bad-permissions-for-etc-emacs-script.tag lintian-2.89.0ubuntu1/tags/b/bad-permissions-for-etc-emacs-script.tag --- lintian-2.93.0/tags/b/bad-permissions-for-etc-emacs-script.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/bad-permissions-for-etc-emacs-script.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,5 +0,0 @@ -Tag: bad-permissions-for-etc-emacs-script -Severity: error -Check: emacs -Explanation: Files in the /etc/emacs* directories should not be marked - executable. diff -Nru lintian-2.93.0/tags/b/bad-provided-package-name.desc lintian-2.89.0ubuntu1/tags/b/bad-provided-package-name.desc --- lintian-2.93.0/tags/b/bad-provided-package-name.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/bad-provided-package-name.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: bad-provided-package-name +Severity: error +Check: fields/package-relations +Info: A package name should be at least two characters long, must consist + of the alphanumerics (lowercase characters only) and "+" "-" and ".", and + must start with an alphanumeric character. +Ref: policy 5.6.7 diff -Nru lintian-2.93.0/tags/b/bad-provided-package-name.tag lintian-2.89.0ubuntu1/tags/b/bad-provided-package-name.tag --- lintian-2.93.0/tags/b/bad-provided-package-name.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/bad-provided-package-name.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: bad-provided-package-name -Severity: error -Check: fields/package-relations -Explanation: A package name should be at least two characters long, must consist - of the alphanumerics (lowercase characters only) and "+" "-" and ".", and - must start with an alphanumeric character. -See-Also: policy 5.6.7 diff -Nru lintian-2.93.0/tags/b/bad-relation.desc lintian-2.89.0ubuntu1/tags/b/bad-relation.desc --- lintian-2.93.0/tags/b/bad-relation.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/bad-relation.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: bad-relation +Severity: error +Check: fields/package-relations +Info: The package declares a relationship that could not be parsed according + to the rules given in the Policy Manual. +Ref: policy 7.1 diff -Nru lintian-2.93.0/tags/b/bad-relation.tag lintian-2.89.0ubuntu1/tags/b/bad-relation.tag --- lintian-2.93.0/tags/b/bad-relation.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/bad-relation.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: bad-relation -Severity: error -Check: fields/package-relations -Explanation: The package declares a relationship that could not be parsed according - to the rules given in the Policy Manual. -See-Also: policy 7.1 diff -Nru lintian-2.93.0/tags/b/bad-section-in-changes-file.desc lintian-2.89.0ubuntu1/tags/b/bad-section-in-changes-file.desc --- lintian-2.93.0/tags/b/bad-section-in-changes-file.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/bad-section-in-changes-file.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: bad-section-in-changes-file +Severity: error +Check: changes-file +Info: The sections non-free and contrib are no longer + valid. Please use section non-free/xxx or + contrib/xxx instead. +Ref: policy 2.4 diff -Nru lintian-2.93.0/tags/b/bad-section-in-changes-file.tag lintian-2.89.0ubuntu1/tags/b/bad-section-in-changes-file.tag --- lintian-2.93.0/tags/b/bad-section-in-changes-file.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/bad-section-in-changes-file.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: bad-section-in-changes-file -Severity: error -Check: changes-file -Explanation: The sections non-free and contrib are no longer - valid. Please use section non-free/xxx or - contrib/xxx instead. -See-Also: policy 2.4 diff -Nru lintian-2.93.0/tags/b/bad-so-link-within-manual-page.desc lintian-2.89.0ubuntu1/tags/b/bad-so-link-within-manual-page.desc --- lintian-2.93.0/tags/b/bad-so-link-within-manual-page.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/bad-so-link-within-manual-page.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: bad-so-link-within-manual-page +Severity: error +Check: documentation/manual +Info: Manual files that use the .so links to include other pages should + only point to a path relative to the top-level manual hierarchy, e.g. + . + .so man3/boo.1.gz diff -Nru lintian-2.93.0/tags/b/bad-so-link-within-manual-page.tag lintian-2.89.0ubuntu1/tags/b/bad-so-link-within-manual-page.tag --- lintian-2.93.0/tags/b/bad-so-link-within-manual-page.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/bad-so-link-within-manual-page.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: bad-so-link-within-manual-page -Severity: error -Check: documentation/manual -Explanation: Manual files that use the .so links to include other pages should - only point to a path relative to the top-level manual hierarchy, e.g. - . - .so man3/boo.1.gz diff -Nru lintian-2.93.0/tags/b/bad-test-in-menu-item.desc lintian-2.89.0ubuntu1/tags/b/bad-test-in-menu-item.desc --- lintian-2.93.0/tags/b/bad-test-in-menu-item.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/bad-test-in-menu-item.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: bad-test-in-menu-item +Severity: error +Check: menu-format +Info: The menu file contains an item that does not start with the text + "?package(somepackage):". All menu file lines must test for the existence + of a package in this way. +Ref: menu 3.2 diff -Nru lintian-2.93.0/tags/b/bad-test-in-menu-item.tag lintian-2.89.0ubuntu1/tags/b/bad-test-in-menu-item.tag --- lintian-2.93.0/tags/b/bad-test-in-menu-item.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/bad-test-in-menu-item.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: bad-test-in-menu-item -Severity: error -Check: menu-format -Explanation: The menu file contains an item that does not start with the text - "?package(somepackage):". All menu file lines must test for the existence - of a package in this way. -See-Also: menu 3.2 diff -Nru lintian-2.93.0/tags/b/bad-urgency-in-changes-file.desc lintian-2.89.0ubuntu1/tags/b/bad-urgency-in-changes-file.desc --- lintian-2.93.0/tags/b/bad-urgency-in-changes-file.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/bad-urgency-in-changes-file.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: bad-urgency-in-changes-file +Severity: error +Check: fields/urgency +Info: The keyword value of the "Urgency" field in the .changes file is not + one of the allowed values of low, medium, high, critical, and emergency + (case-insensitive). This value normally taken from the first line of the + most recent entry in debian/changelog, which is probably where + the error is. +Ref: policy 5.6.17 diff -Nru lintian-2.93.0/tags/b/bad-urgency-in-changes-file.tag lintian-2.89.0ubuntu1/tags/b/bad-urgency-in-changes-file.tag --- lintian-2.93.0/tags/b/bad-urgency-in-changes-file.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/bad-urgency-in-changes-file.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: bad-urgency-in-changes-file -Severity: error -Check: fields/urgency -Explanation: The keyword value of the "Urgency" field in the .changes file is not - one of the allowed values of low, medium, high, critical, and emergency - (case-insensitive). This value normally taken from the first line of the - most recent entry in debian/changelog, which is probably where - the error is. -See-Also: policy 5.6.17 diff -Nru lintian-2.93.0/tags/b/bad-version-in-relation.desc lintian-2.89.0ubuntu1/tags/b/bad-version-in-relation.desc --- lintian-2.93.0/tags/b/bad-version-in-relation.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/bad-version-in-relation.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: bad-version-in-relation +Ref: policy 5.6.12 +Severity: error +Check: fields/package-relations +Info: The version number used in this relationship does not match the + defined format of a version number. diff -Nru lintian-2.93.0/tags/b/bad-version-in-relation.tag lintian-2.89.0ubuntu1/tags/b/bad-version-in-relation.tag --- lintian-2.93.0/tags/b/bad-version-in-relation.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/bad-version-in-relation.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: bad-version-in-relation -See-Also: policy 5.6.12 -Severity: error -Check: fields/package-relations -Explanation: The version number used in this relationship does not match the - defined format of a version number. diff -Nru lintian-2.93.0/tags/b/bad-version-number.desc lintian-2.89.0ubuntu1/tags/b/bad-version-number.desc --- lintian-2.93.0/tags/b/bad-version-number.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/bad-version-number.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,5 @@ +Tag: bad-version-number +Severity: error +Check: fields/version +Info: The version number fails one of the syntactic requirements of dpkg. +Ref: policy 5.6.12 diff -Nru lintian-2.93.0/tags/b/bad-version-number.tag lintian-2.89.0ubuntu1/tags/b/bad-version-number.tag --- lintian-2.93.0/tags/b/bad-version-number.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/bad-version-number.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,5 +0,0 @@ -Tag: bad-version-number -Severity: error -Check: fields/version -Explanation: The version number fails one of the syntactic requirements of dpkg. -See-Also: policy 5.6.12 diff -Nru lintian-2.93.0/tags/b/bad-whatis-entry.desc lintian-2.89.0ubuntu1/tags/b/bad-whatis-entry.desc --- lintian-2.93.0/tags/b/bad-whatis-entry.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/bad-whatis-entry.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,18 @@ +Tag: bad-whatis-entry +Severity: warning +Check: documentation/manual +Renamed-From: manpage-has-bad-whatis-entry +Info: A manual page should start with a NAME section, which + lists the program name and a brief description. The NAME + section is used to generate a database that can be queried by commands + like apropos and whatis. You are seeing this tag + because lexgrog was unable to parse the NAME section. + . + Manual pages for multiple programs, functions, or files should list each + separated by a comma and a space, followed by \- and a common + description. + . + Listed items may not contain any spaces. A manual page for a two-level + command such as fs listacl must look like fs_listacl + so the list is read correctly. +Ref: lexgrog(1), groff_man(7), groff_mdoc(7) diff -Nru lintian-2.93.0/tags/b/bad-whatis-entry.tag lintian-2.89.0ubuntu1/tags/b/bad-whatis-entry.tag --- lintian-2.93.0/tags/b/bad-whatis-entry.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/bad-whatis-entry.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,18 +0,0 @@ -Tag: bad-whatis-entry -Severity: warning -Check: documentation/manual -Renamed-From: manpage-has-bad-whatis-entry -Explanation: A manual page should start with a NAME section, which - lists the program name and a brief description. The NAME - section is used to generate a database that can be queried by commands - like apropos and whatis. You are seeing this tag - because lexgrog was unable to parse the NAME section. - . - Manual pages for multiple programs, functions, or files should list each - separated by a comma and a space, followed by \- and a common - description. - . - Listed items may not contain any spaces. A manual page for a two-level - command such as fs listacl must look like fs_listacl - so the list is read correctly. -See-Also: lexgrog(1), groff_man(7), groff_mdoc(7) diff -Nru lintian-2.93.0/tags/b/bash-completion-with-hashbang.desc lintian-2.89.0ubuntu1/tags/b/bash-completion-with-hashbang.desc --- lintian-2.93.0/tags/b/bash-completion-with-hashbang.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/bash-completion-with-hashbang.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: bash-completion-with-hashbang +Severity: warning +Check: scripts +Info: This file starts with the #! sequence that marks interpreted scripts, + but it is a bash completion script that is merely intended to be sourced. + . + Please remove the line with hashbang, including any designated interpreter. +Ref: https://salsa.debian.org/lintian/lintian/-/merge_requests/292#note_139494 diff -Nru lintian-2.93.0/tags/b/bash-completion-with-hashbang.tag lintian-2.89.0ubuntu1/tags/b/bash-completion-with-hashbang.tag --- lintian-2.93.0/tags/b/bash-completion-with-hashbang.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/bash-completion-with-hashbang.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: bash-completion-with-hashbang -Severity: warning -Check: scripts -Explanation: This file starts with the #! sequence that marks interpreted scripts, - but it is a bash completion script that is merely intended to be sourced. - . - Please remove the line with hashbang, including any designated interpreter. -See-Also: https://salsa.debian.org/lintian/lintian/-/merge_requests/292#note_139494 diff -Nru lintian-2.93.0/tags/b/binaries-have-file-conflict.desc lintian-2.89.0ubuntu1/tags/b/binaries-have-file-conflict.desc --- lintian-2.93.0/tags/b/binaries-have-file-conflict.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/binaries-have-file-conflict.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,11 @@ +Tag: binaries-have-file-conflict +Severity: warning +Certainty: possible +Check: group-checks +Experimental: no +Info: The binaries appears to have overlapping files without proper + conflicts relation. + . + Note the check is completely based on the file index for the + packages. Possible known false-positives include dpkg-diverts in + maintainer scripts. diff -Nru lintian-2.93.0/tags/b/binaries-have-file-conflict.tag lintian-2.89.0ubuntu1/tags/b/binaries-have-file-conflict.tag --- lintian-2.93.0/tags/b/binaries-have-file-conflict.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/binaries-have-file-conflict.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,10 +0,0 @@ -Tag: binaries-have-file-conflict -Severity: warning -Check: group-checks -Experimental: no -Explanation: The binaries appears to have overlapping files without proper - conflicts relation. - . - Note the check is completely based on the file index for the - packages. Possible known false-positives include dpkg-diverts in - maintainer scripts. diff -Nru lintian-2.93.0/tags/b/binary-arch-rules-but-pkg-is-arch-indep.desc lintian-2.89.0ubuntu1/tags/b/binary-arch-rules-but-pkg-is-arch-indep.desc --- lintian-2.93.0/tags/b/binary-arch-rules-but-pkg-is-arch-indep.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/binary-arch-rules-but-pkg-is-arch-indep.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: binary-arch-rules-but-pkg-is-arch-indep +Severity: warning +Check: debian/rules +Info: It looks like you try to run code in the binary-arch target of + debian/rules, even though your package is architecture- + independent. diff -Nru lintian-2.93.0/tags/b/binary-arch-rules-but-pkg-is-arch-indep.tag lintian-2.89.0ubuntu1/tags/b/binary-arch-rules-but-pkg-is-arch-indep.tag --- lintian-2.93.0/tags/b/binary-arch-rules-but-pkg-is-arch-indep.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/binary-arch-rules-but-pkg-is-arch-indep.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: binary-arch-rules-but-pkg-is-arch-indep -Severity: warning -Check: debian/rules -Explanation: It looks like you try to run code in the binary-arch target of - debian/rules, even though your package is architecture- - independent. diff -Nru lintian-2.93.0/tags/b/binary-compiled-with-profiling-enabled.desc lintian-2.89.0ubuntu1/tags/b/binary-compiled-with-profiling-enabled.desc --- lintian-2.93.0/tags/b/binary-compiled-with-profiling-enabled.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/binary-compiled-with-profiling-enabled.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,5 @@ +Tag: binary-compiled-with-profiling-enabled +Severity: warning +Check: binaries +Info: While profiling is useful for testing and debugging purposes, enabling + it causes a program to leave gmon.out files whenever a user runs it. diff -Nru lintian-2.93.0/tags/b/binary-compiled-with-profiling-enabled.tag lintian-2.89.0ubuntu1/tags/b/binary-compiled-with-profiling-enabled.tag --- lintian-2.93.0/tags/b/binary-compiled-with-profiling-enabled.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/binary-compiled-with-profiling-enabled.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,5 +0,0 @@ -Tag: binary-compiled-with-profiling-enabled -Severity: warning -Check: binaries -Explanation: While profiling is useful for testing and debugging purposes, enabling - it causes a program to leave gmon.out files whenever a user runs it. diff -Nru lintian-2.93.0/tags/b/binary-control-field-duplicates-source.desc lintian-2.89.0ubuntu1/tags/b/binary-control-field-duplicates-source.desc --- lintian-2.93.0/tags/b/binary-control-field-duplicates-source.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/binary-control-field-duplicates-source.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: binary-control-field-duplicates-source +Severity: info +Check: debian/control +Info: In debian/control, this field for a binary package + duplicates the value inherited from the source package paragraph. This + doesn't hurt anything, but you may want to take advantage of the + inheritance and set the value in only one place. It prevents missing + duplicate places that need to be fixed if the value ever changes. diff -Nru lintian-2.93.0/tags/b/binary-control-field-duplicates-source.tag lintian-2.89.0ubuntu1/tags/b/binary-control-field-duplicates-source.tag --- lintian-2.93.0/tags/b/binary-control-field-duplicates-source.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/binary-control-field-duplicates-source.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: binary-control-field-duplicates-source -Severity: info -Check: debian/control -Explanation: In debian/control, this field for a binary package - duplicates the value inherited from the source package paragraph. This - doesn't hurt anything, but you may want to take advantage of the - inheritance and set the value in only one place. It prevents missing - duplicate places that need to be fixed if the value ever changes. diff -Nru lintian-2.93.0/tags/b/binary-file-built-without-LFS-support.desc lintian-2.89.0ubuntu1/tags/b/binary-file-built-without-LFS-support.desc --- lintian-2.93.0/tags/b/binary-file-built-without-LFS-support.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/binary-file-built-without-LFS-support.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,39 @@ +Tag: binary-file-built-without-LFS-support +Severity: info +Certainty: possible +Check: binaries +Experimental: yes +Info: The listed ELF binary appears to be (partially) built without + "Large File Support" (LFS). If so, it may not be able to handle large + files or files with large metadata values (ex: inode numbers) correctly. + . + To support large files, code review might be needed to make sure that + those files are not slurped into memory or mmap(2)ed, and that correct + 64-bit data types are used (ex: off_t instead of ssize_t), etc. Once + that has been done ensure _FILE_OFFSET_BITS is defined and + set to 64 before any system headers are included (note that on systems + were the ABI has LFS enabled by default, setting _FILE_OFFSET_BITS + to 64 will be a no-op, and as such optional). This can be done by using + the AC_SYS_LARGEFILE macro with autoconf which will set any + macro required to enable LFS when necessary, or by enabling the + lfs feature from the future dpkg-buildflags feature + area which sets the CPPFLAGS variable (since dpkg-dev 1.19.0). + Note though, that getconf LFS_CFLAGS must not be used, + as it does not support cross-building. Using + _FILE_OFFSET_BITS should require no system function renames (eg. + from open(2) to open64(2)), and if this tag is still emitted, the most + probable cause is because the macro is not seen by the system code being + compiled. + . + Take into account that even if this tag is not emitted, that does not + mean the binary is LFS-safe (ie. no OOM conditions, file truncation + or overwrite will happen). + . + Also note that enabling LFS on a shared library is not always safe as + it might break ABI in case some of the exported types change size, in + those cases a SOVERSION bump might be required. Or alternatively, on + systems with an ABI without LFS, defining _LARGEFILE64_SOURCE + and exporting both 32 and 64-bit variants of the interfaces can avoid + the SOVERSION bump, at the cost of more complex maintenance. +Ref: http://www.unix.org/version2/whatsnew/lfs20mar.html, + https://www.gnu.org/software/libc/manual/html_node/Feature-Test-Macros.html diff -Nru lintian-2.93.0/tags/b/binary-file-built-without-LFS-support.tag lintian-2.89.0ubuntu1/tags/b/binary-file-built-without-LFS-support.tag --- lintian-2.93.0/tags/b/binary-file-built-without-LFS-support.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/binary-file-built-without-LFS-support.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,38 +0,0 @@ -Tag: binary-file-built-without-LFS-support -Severity: info -Check: binaries -Experimental: yes -Explanation: The listed ELF binary appears to be (partially) built without - "Large File Support" (LFS). If so, it may not be able to handle large - files or files with large metadata values (ex: inode numbers) correctly. - . - To support large files, code review might be needed to make sure that - those files are not slurped into memory or mmap(2)ed, and that correct - 64-bit data types are used (ex: off_t instead of ssize_t), etc. Once - that has been done ensure _FILE_OFFSET_BITS is defined and - set to 64 before any system headers are included (note that on systems - were the ABI has LFS enabled by default, setting _FILE_OFFSET_BITS - to 64 will be a no-op, and as such optional). This can be done by using - the AC_SYS_LARGEFILE macro with autoconf which will set any - macro required to enable LFS when necessary, or by enabling the - lfs feature from the future dpkg-buildflags feature - area which sets the CPPFLAGS variable (since dpkg-dev 1.19.0). - Note though, that getconf LFS_CFLAGS must not be used, - as it does not support cross-building. Using - _FILE_OFFSET_BITS should require no system function renames (eg. - from open(2) to open64(2)), and if this tag is still emitted, the most - probable cause is because the macro is not seen by the system code being - compiled. - . - Take into account that even if this tag is not emitted, that does not - mean the binary is LFS-safe (ie. no OOM conditions, file truncation - or overwrite will happen). - . - Also note that enabling LFS on a shared library is not always safe as - it might break ABI in case some of the exported types change size, in - those cases a SOVERSION bump might be required. Or alternatively, on - systems with an ABI without LFS, defining _LARGEFILE64_SOURCE - and exporting both 32 and 64-bit variants of the interfaces can avoid - the SOVERSION bump, at the cost of more complex maintenance. -See-Also: http://www.unix.org/version2/whatsnew/lfs20mar.html, - https://www.gnu.org/software/libc/manual/html_node/Feature-Test-Macros.html diff -Nru lintian-2.93.0/tags/b/binary-from-other-architecture.desc lintian-2.89.0ubuntu1/tags/b/binary-from-other-architecture.desc --- lintian-2.93.0/tags/b/binary-from-other-architecture.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/binary-from-other-architecture.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: binary-from-other-architecture +Severity: error +Certainty: possible +Check: binaries +Info: This ELF binary appears to have been built for an architecture other + than the one of the binary package being tested. This may occur when a + pre-built binary is shipped in the package or when an attempt to + cross-compile didn't work. diff -Nru lintian-2.93.0/tags/b/binary-from-other-architecture.tag lintian-2.89.0ubuntu1/tags/b/binary-from-other-architecture.tag --- lintian-2.93.0/tags/b/binary-from-other-architecture.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/binary-from-other-architecture.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: binary-from-other-architecture -Severity: error -Check: binaries -Explanation: This ELF binary appears to have been built for an architecture other - than the one of the binary package being tested. This may occur when a - pre-built binary is shipped in the package or when an attempt to - cross-compile didn't work. diff -Nru lintian-2.93.0/tags/b/binary-has-unneeded-section.desc lintian-2.89.0ubuntu1/tags/b/binary-has-unneeded-section.desc --- lintian-2.93.0/tags/b/binary-has-unneeded-section.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/binary-has-unneeded-section.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,11 @@ +Tag: binary-has-unneeded-section +Severity: info +Check: binaries +Info: The binary or shared library is stripped, but still contains a + section that is not useful. You should call strip with + --remove-section=.comment --remove-section=.note to remove the + .note and .comment sections. + . + dh_strip will do this automatically for you, but + install -s will not because it calls strip without any + arguments. diff -Nru lintian-2.93.0/tags/b/binary-has-unneeded-section.tag lintian-2.89.0ubuntu1/tags/b/binary-has-unneeded-section.tag --- lintian-2.93.0/tags/b/binary-has-unneeded-section.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/binary-has-unneeded-section.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,11 +0,0 @@ -Tag: binary-has-unneeded-section -Severity: info -Check: binaries -Explanation: The binary or shared library is stripped, but still contains a - section that is not useful. You should call strip with - --remove-section=.comment --remove-section=.note to remove the - .note and .comment sections. - . - dh_strip will do this automatically for you, but - install -s will not because it calls strip without any - arguments. diff -Nru lintian-2.93.0/tags/b/binary-in-etc.desc lintian-2.89.0ubuntu1/tags/b/binary-in-etc.desc --- lintian-2.93.0/tags/b/binary-in-etc.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/binary-in-etc.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: binary-in-etc +Severity: error +Check: binaries +Ref: fhs etchostspecificsystemconfiguration +Info: This package installs an ELF binary in /etc. The + Filesystem Hierarchy Standard forbids this. diff -Nru lintian-2.93.0/tags/b/binary-in-etc.tag lintian-2.89.0ubuntu1/tags/b/binary-in-etc.tag --- lintian-2.93.0/tags/b/binary-in-etc.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/binary-in-etc.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: binary-in-etc -Severity: error -Check: binaries -See-Also: fhs etchostspecificsystemconfiguration -Explanation: This package installs an ELF binary in /etc. The - Filesystem Hierarchy Standard forbids this. diff -Nru lintian-2.93.0/tags/b/binary-nmu-debian-revision-in-source.desc lintian-2.89.0ubuntu1/tags/b/binary-nmu-debian-revision-in-source.desc --- lintian-2.93.0/tags/b/binary-nmu-debian-revision-in-source.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/binary-nmu-debian-revision-in-source.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: binary-nmu-debian-revision-in-source +Severity: warning +Check: fields/version +Ref: devref 5.10.2.1 +Info: The version number of your source package ends in +b and a number or + has a Debian revision containing three parts. These version numbers are + used by binary NMUs and should not be used as the source version. (The + +b form is the current standard; the three-part version number now + obsolete.) diff -Nru lintian-2.93.0/tags/b/binary-nmu-debian-revision-in-source.tag lintian-2.89.0ubuntu1/tags/b/binary-nmu-debian-revision-in-source.tag --- lintian-2.93.0/tags/b/binary-nmu-debian-revision-in-source.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/binary-nmu-debian-revision-in-source.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: binary-nmu-debian-revision-in-source -Severity: warning -Check: fields/version -See-Also: devref 5.10.2.1 -Explanation: The version number of your source package ends in +b and a number or - has a Debian revision containing three parts. These version numbers are - used by binary NMUs and should not be used as the source version. (The - +b form is the current standard; the three-part version number now - obsolete.) diff -Nru lintian-2.93.0/tags/b/binary-package-depends-on-toolchain-package.desc lintian-2.89.0ubuntu1/tags/b/binary-package-depends-on-toolchain-package.desc --- lintian-2.93.0/tags/b/binary-package-depends-on-toolchain-package.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/binary-package-depends-on-toolchain-package.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: binary-package-depends-on-toolchain-package +Severity: warning +Certainty: possible +Check: fields/package-relations +Info: This package specifies a binary dependency on a "toolchain" package + such as debhelper or cdbs. This is likely to be a mistake; these + packages are typically specified as build-dependencies instead. + . + If the package intentionally requires such a dependency, please add a + Lintian override with a justifying remark. diff -Nru lintian-2.93.0/tags/b/binary-package-depends-on-toolchain-package.tag lintian-2.89.0ubuntu1/tags/b/binary-package-depends-on-toolchain-package.tag --- lintian-2.93.0/tags/b/binary-package-depends-on-toolchain-package.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/binary-package-depends-on-toolchain-package.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: binary-package-depends-on-toolchain-package -Severity: warning -Check: fields/package-relations -Explanation: This package specifies a binary dependency on a "toolchain" package - such as debhelper or cdbs. This is likely to be a mistake; these - packages are typically specified as build-dependencies instead. - . - If the package intentionally requires such a dependency, please add a - Lintian override with a justifying remark. diff -Nru lintian-2.93.0/tags/b/binary-with-bad-dynamic-table.desc lintian-2.89.0ubuntu1/tags/b/binary-with-bad-dynamic-table.desc --- lintian-2.93.0/tags/b/binary-with-bad-dynamic-table.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/binary-with-bad-dynamic-table.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,11 @@ +Tag: binary-with-bad-dynamic-table +Severity: error +Certainty: possible +Check: binaries +Info: This appears to be an ELF file. According to readelf, the + program headers suggests it should have a dynamic section, but + readelf cannot find it. + . + If it is meant to be external debugging symbols for another file, + it should be installed under /usr/lib/debug. Otherwise, this + could be a corrupt ELF file. diff -Nru lintian-2.93.0/tags/b/binary-with-bad-dynamic-table.tag lintian-2.89.0ubuntu1/tags/b/binary-with-bad-dynamic-table.tag --- lintian-2.93.0/tags/b/binary-with-bad-dynamic-table.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/binary-with-bad-dynamic-table.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,10 +0,0 @@ -Tag: binary-with-bad-dynamic-table -Severity: error -Check: binaries -Explanation: This appears to be an ELF file. According to readelf, the - program headers suggests it should have a dynamic section, but - readelf cannot find it. - . - If it is meant to be external debugging symbols for another file, - it should be installed under /usr/lib/debug. Otherwise, this - could be a corrupt ELF file. diff -Nru lintian-2.93.0/tags/b/bin-sbin-mismatch.desc lintian-2.89.0ubuntu1/tags/b/bin-sbin-mismatch.desc --- lintian-2.93.0/tags/b/bin-sbin-mismatch.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/bin-sbin-mismatch.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,18 @@ +Tag: bin-sbin-mismatch +Severity: info +Certainty: possible +Check: files/contents +Experimental: yes +Info: The package installs a binary under /usr/sbin or + /sbin but the specified file or maintainer script appears to + incorrectly reference it under /usr/bin or /bin. + . + This is likely due to the maintainer identifying that the package + requires root privileges or similar and thus installing the files to + the sbin variant, but the package has not been comprehensively + or completely updated to match. + . + For ELF files, mismatches could be related to the SHF_MERGE + option to ld. The option saves space by providing different + start indices into the same static location in object files. + Unfortunately, the sub-string information is lost in that process. diff -Nru lintian-2.93.0/tags/b/bin-sbin-mismatch.tag lintian-2.89.0ubuntu1/tags/b/bin-sbin-mismatch.tag --- lintian-2.93.0/tags/b/bin-sbin-mismatch.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/bin-sbin-mismatch.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,17 +0,0 @@ -Tag: bin-sbin-mismatch -Severity: info -Check: files/contents -Experimental: yes -Explanation: The package installs a binary under /usr/sbin or - /sbin but the specified file or maintainer script appears to - incorrectly reference it under /usr/bin or /bin. - . - This is likely due to the maintainer identifying that the package - requires root privileges or similar and thus installing the files to - the sbin variant, but the package has not been comprehensively - or completely updated to match. - . - For ELF files, mismatches could be related to the SHF_MERGE - option to ld. The option saves space by providing different - start indices into the same static location in object files. - Unfortunately, the sub-string information is lost in that process. diff -Nru lintian-2.93.0/tags/b/bogus-mail-host.desc lintian-2.89.0ubuntu1/tags/b/bogus-mail-host.desc --- lintian-2.93.0/tags/b/bogus-mail-host.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/bogus-mail-host.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,12 @@ +Tag: bogus-mail-host +Severity: error +Check: fields/mail-address +Renamed-From: + maintainer-address-is-on-localhost + uploader-address-is-on-localhost + changed-by-address-is-on-localhost +Info: The host part of the named contact address is not known or not + globally routables, such as localhost(.localdomain). +Ref: policy 5.6.2, + policy 5.6.3, + policy 5.6.4 diff -Nru lintian-2.93.0/tags/b/bogus-mail-host-in-debian-changelog.desc lintian-2.89.0ubuntu1/tags/b/bogus-mail-host-in-debian-changelog.desc --- lintian-2.93.0/tags/b/bogus-mail-host-in-debian-changelog.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/bogus-mail-host-in-debian-changelog.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: bogus-mail-host-in-debian-changelog +Severity: error +Check: debian/changelog +Renamed-From: debian-changelog-file-contains-invalid-email-address +Info: The changelog file contains an invalid email address: the domain + needs at least one dot. This looks like a mistake. diff -Nru lintian-2.93.0/tags/b/bogus-mail-host-in-debian-changelog.tag lintian-2.89.0ubuntu1/tags/b/bogus-mail-host-in-debian-changelog.tag --- lintian-2.93.0/tags/b/bogus-mail-host-in-debian-changelog.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/bogus-mail-host-in-debian-changelog.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: bogus-mail-host-in-debian-changelog -Severity: error -Check: debian/changelog -Renamed-From: debian-changelog-file-contains-invalid-email-address -Explanation: The changelog file contains an invalid email address: the domain - needs at least one dot. This looks like a mistake. diff -Nru lintian-2.93.0/tags/b/bogus-mail-host.tag lintian-2.89.0ubuntu1/tags/b/bogus-mail-host.tag --- lintian-2.93.0/tags/b/bogus-mail-host.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/bogus-mail-host.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,12 +0,0 @@ -Tag: bogus-mail-host -Severity: error -Check: fields/mail-address -Renamed-From: - maintainer-address-is-on-localhost - uploader-address-is-on-localhost - changed-by-address-is-on-localhost -Explanation: The host part of the named contact address is not known or not - globally routables, such as localhost(.localdomain). -See-Also: policy 5.6.2, - policy 5.6.3, - policy 5.6.4 diff -Nru lintian-2.93.0/tags/b/boilerplate-copyright-format-uri.desc lintian-2.89.0ubuntu1/tags/b/boilerplate-copyright-format-uri.desc --- lintian-2.93.0/tags/b/boilerplate-copyright-format-uri.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/boilerplate-copyright-format-uri.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: boilerplate-copyright-format-uri +Severity: warning +Certainty: possible +Check: debian/copyright/dep5 +Info: Format URI of the machine-readable copyright file contains + VERSIONED_FORMAT_URL or REVISION string. Please replace it + with an actual URI or an actual revision number respectively. diff -Nru lintian-2.93.0/tags/b/boilerplate-copyright-format-uri.tag lintian-2.89.0ubuntu1/tags/b/boilerplate-copyright-format-uri.tag --- lintian-2.93.0/tags/b/boilerplate-copyright-format-uri.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/boilerplate-copyright-format-uri.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: boilerplate-copyright-format-uri -Severity: warning -Check: debian/copyright/dep5 -Explanation: Format URI of the machine-readable copyright file contains - VERSIONED_FORMAT_URL or REVISION string. Please replace it - with an actual URI or an actual revision number respectively. diff -Nru lintian-2.93.0/tags/b/boolean-template-has-bogus-default.desc lintian-2.89.0ubuntu1/tags/b/boolean-template-has-bogus-default.desc --- lintian-2.93.0/tags/b/boolean-template-has-bogus-default.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/boolean-template-has-bogus-default.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: boolean-template-has-bogus-default +Severity: error +Check: debian/debconf +Info: The "boolean" type in a debconf template, can have only two values: true + and false. The default has been set to something different. +Ref: debconf-spec 3.1, debconf-devel(7) diff -Nru lintian-2.93.0/tags/b/boolean-template-has-bogus-default.tag lintian-2.89.0ubuntu1/tags/b/boolean-template-has-bogus-default.tag --- lintian-2.93.0/tags/b/boolean-template-has-bogus-default.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/boolean-template-has-bogus-default.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: boolean-template-has-bogus-default -Severity: error -Check: debian/debconf -Explanation: The "boolean" type in a debconf template, can have only two values: true - and false. The default has been set to something different. -See-Also: debconf-spec 3.1, debconf-devel(7) diff -Nru lintian-2.93.0/tags/b/brace-expansion-in-debhelper-config-file.desc lintian-2.89.0ubuntu1/tags/b/brace-expansion-in-debhelper-config-file.desc --- lintian-2.93.0/tags/b/brace-expansion-in-debhelper-config-file.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/brace-expansion-in-debhelper-config-file.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: brace-expansion-in-debhelper-config-file +Severity: warning +Certainty: possible +Check: debhelper +Info: This debhelper config file appears to use shell brace expansion + (such as {foo,bar}) to specify files. This happens to work due + to an accident of implementation but is not a supported feature. Only + ?, *, and [...] are supported. +Ref: debhelper(1) diff -Nru lintian-2.93.0/tags/b/brace-expansion-in-debhelper-config-file.tag lintian-2.89.0ubuntu1/tags/b/brace-expansion-in-debhelper-config-file.tag --- lintian-2.93.0/tags/b/brace-expansion-in-debhelper-config-file.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/brace-expansion-in-debhelper-config-file.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: brace-expansion-in-debhelper-config-file -Severity: warning -Check: debhelper -Explanation: This debhelper config file appears to use shell brace expansion - (such as {foo,bar}) to specify files. This happens to work due - to an accident of implementation but is not a supported feature. Only - ?, *, and [...] are supported. -See-Also: debhelper(1) diff -Nru lintian-2.93.0/tags/b/breakout-link.desc lintian-2.89.0ubuntu1/tags/b/breakout-link.desc --- lintian-2.93.0/tags/b/breakout-link.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/breakout-link.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,16 @@ +Tag: breakout-link +Severity: warning +Check: files/hierarchy/links +Info: The named link is in /usr/lib and points to higher + location in the file system, or traverses through one. + . + At least for /usr/lib, it is usally an error and may + confuse some tools. + . + To escape this check, links in /usr/lib must point to targets + in the same directory or a subdirectory thereof. + . + Lateral connections to the same level in /usr/lib are not allowed + if they traverse through a higher directory, because in a typical + multi-lib layout that might point to another architecture. +Ref: Bug#243158 diff -Nru lintian-2.93.0/tags/b/breakout-link.tag lintian-2.89.0ubuntu1/tags/b/breakout-link.tag --- lintian-2.93.0/tags/b/breakout-link.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/breakout-link.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,16 +0,0 @@ -Tag: breakout-link -Severity: warning -Check: files/hierarchy/links -Explanation: The named link is in /usr/lib and points to higher - location in the file system, or traverses through one. - . - At least for /usr/lib, it is usually an error and may - confuse some tools. - . - To escape this check, links in /usr/lib must point to targets - in the same directory or a subdirectory thereof. - . - Lateral connections to the same level in /usr/lib are not allowed - if they traverse through a higher directory, because in a typical - multi-lib layout that might point to another architecture. -See-Also: Bug#243158 diff -Nru lintian-2.93.0/tags/b/breaks-without-version.desc lintian-2.89.0ubuntu1/tags/b/breaks-without-version.desc --- lintian-2.93.0/tags/b/breaks-without-version.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/breaks-without-version.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,14 @@ +Tag: breaks-without-version +Severity: warning +Certainty: possible +Check: fields/package-relations +Ref: policy 7.3, policy 7.4, #605744 +Info: This package declares a Breaks relationship with another package + that has no version number. Normally, Breaks should be used to indicate + an incompatibility with a specific version of another package, or with + all versions predating a fix. If the two packages can never be installed + at the same time, Conflicts should normally be used instead. + . + Note this tag can also be issued if a package has been split into two + completely new ones. In this case, this package is missing a Replaces + on the old package. diff -Nru lintian-2.93.0/tags/b/breaks-without-version.tag lintian-2.89.0ubuntu1/tags/b/breaks-without-version.tag --- lintian-2.93.0/tags/b/breaks-without-version.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/breaks-without-version.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,13 +0,0 @@ -Tag: breaks-without-version -Severity: warning -Check: fields/package-relations -See-Also: policy 7.3, policy 7.4, Bug#605744 -Explanation: This package declares a Breaks relationship with another package - that has no version number. Normally, Breaks should be used to indicate - an incompatibility with a specific version of another package, or with - all versions predating a fix. If the two packages can never be installed - at the same time, Conflicts should normally be used instead. - . - Note this tag can also be issued if a package has been split into two - completely new ones. In this case, this package is missing a Replaces - on the old package. diff -Nru lintian-2.93.0/tags/b/broken-bz2.desc lintian-2.89.0ubuntu1/tags/b/broken-bz2.desc --- lintian-2.93.0/tags/b/broken-bz2.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/broken-bz2.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: broken-bz2 +Severity: warning +Check: files/compressed/bz2 +Info: The given file ends with .bz2, which normally indicates it + was compressed with bzip2. However, it doesn't seem to be an + bz2-compressed file. diff -Nru lintian-2.93.0/tags/b/broken-bz2.tag lintian-2.89.0ubuntu1/tags/b/broken-bz2.tag --- lintian-2.93.0/tags/b/broken-bz2.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/broken-bz2.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: broken-bz2 -Severity: warning -Check: files/compressed/bz2 -Explanation: The given file ends with .bz2, which normally indicates it - was compressed with bzip2. However, it doesn't seem to be an - bz2-compressed file. diff -Nru lintian-2.93.0/tags/b/broken-gz.desc lintian-2.89.0ubuntu1/tags/b/broken-gz.desc --- lintian-2.93.0/tags/b/broken-gz.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/broken-gz.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: broken-gz +Severity: warning +Check: files/compressed/gz +Info: The given file ends with .gz, which normally indicates it + was compressed with gzip. However, it doesn't seem to be a + gzip-compressed file. diff -Nru lintian-2.93.0/tags/b/broken-gz.tag lintian-2.89.0ubuntu1/tags/b/broken-gz.tag --- lintian-2.93.0/tags/b/broken-gz.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/broken-gz.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: broken-gz -Severity: warning -Check: files/compressed/gz -Explanation: The given file ends with .gz, which normally indicates it - was compressed with gzip. However, it doesn't seem to be a - gzip-compressed file. diff -Nru lintian-2.93.0/tags/b/broken-link-to-undocumented.desc lintian-2.89.0ubuntu1/tags/b/broken-link-to-undocumented.desc --- lintian-2.93.0/tags/b/broken-link-to-undocumented.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/broken-link-to-undocumented.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: broken-link-to-undocumented +Severity: error +Check: documentation/manual +Renamed-From: bad-link-to-undocumented-manpage +Info: The symbolic link should reference + "../man[237]/undocumented.[237].gz" for manual pages in + /usr/share/man. diff -Nru lintian-2.93.0/tags/b/broken-link-to-undocumented.tag lintian-2.89.0ubuntu1/tags/b/broken-link-to-undocumented.tag --- lintian-2.93.0/tags/b/broken-link-to-undocumented.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/broken-link-to-undocumented.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: broken-link-to-undocumented -Severity: error -Check: documentation/manual -Renamed-From: bad-link-to-undocumented-manpage -Explanation: The symbolic link should reference - "../man[237]/undocumented.[237].gz" for manual pages in - /usr/share/man. diff -Nru lintian-2.93.0/tags/b/broken-lz.desc lintian-2.89.0ubuntu1/tags/b/broken-lz.desc --- lintian-2.93.0/tags/b/broken-lz.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/broken-lz.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: broken-lz +Severity: warning +Check: files/compressed/lz +Info: The given file ends with .lz, which normally indicates it + was compressed with lz. However, it doesn't seem to be an + lz-compressed file. diff -Nru lintian-2.93.0/tags/b/broken-lzma.desc lintian-2.89.0ubuntu1/tags/b/broken-lzma.desc --- lintian-2.93.0/tags/b/broken-lzma.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/broken-lzma.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: broken-lzma +Severity: warning +Check: files/compressed/lzma +Info: The given file ends with .lzma, which normally indicates it + was compressed with lzma. However, it doesn't seem to be an + lzma-compressed file. diff -Nru lintian-2.93.0/tags/b/broken-lzma.tag lintian-2.89.0ubuntu1/tags/b/broken-lzma.tag --- lintian-2.93.0/tags/b/broken-lzma.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/broken-lzma.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: broken-lzma -Severity: warning -Check: files/compressed/lzma -Explanation: The given file ends with .lzma, which normally indicates it - was compressed with lzma. However, it doesn't seem to be an - lzma-compressed file. diff -Nru lintian-2.93.0/tags/b/broken-lzo.desc lintian-2.89.0ubuntu1/tags/b/broken-lzo.desc --- lintian-2.93.0/tags/b/broken-lzo.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/broken-lzo.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: broken-lzo +Severity: warning +Check: files/compressed/lzo +Info: The given file ends with .lzo, which normally indicates it + was compressed with lzop. However, it doesn't seem to be an + lz-compressed file. diff -Nru lintian-2.93.0/tags/b/broken-lzo.tag lintian-2.89.0ubuntu1/tags/b/broken-lzo.tag --- lintian-2.93.0/tags/b/broken-lzo.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/broken-lzo.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: broken-lzo -Severity: warning -Check: files/compressed/lzo -Explanation: The given file ends with .lzo, which normally indicates it - was compressed with lzop. However, it doesn't seem to be an - lz-compressed file. diff -Nru lintian-2.93.0/tags/b/broken-lz.tag lintian-2.89.0ubuntu1/tags/b/broken-lz.tag --- lintian-2.93.0/tags/b/broken-lz.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/broken-lz.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: broken-lz -Severity: warning -Check: files/compressed/lz -Explanation: The given file ends with .lz, which normally indicates it - was compressed with lz. However, it doesn't seem to be an - lz-compressed file. diff -Nru lintian-2.93.0/tags/b/broken-xz.desc lintian-2.89.0ubuntu1/tags/b/broken-xz.desc --- lintian-2.93.0/tags/b/broken-xz.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/broken-xz.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: broken-xz +Severity: warning +Check: files/compressed/xz +Info: The given file ends with .xz, which normally indicates it + is compressed with xz. However, it doesn't seem to be an + xz-compressed file. diff -Nru lintian-2.93.0/tags/b/broken-xz.tag lintian-2.89.0ubuntu1/tags/b/broken-xz.tag --- lintian-2.93.0/tags/b/broken-xz.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/broken-xz.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: broken-xz -Severity: warning -Check: files/compressed/xz -Explanation: The given file ends with .xz, which normally indicates it - is compressed with xz. However, it doesn't seem to be an - xz-compressed file. diff -Nru lintian-2.93.0/tags/b/broken-zip.desc lintian-2.89.0ubuntu1/tags/b/broken-zip.desc --- lintian-2.93.0/tags/b/broken-zip.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/broken-zip.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: broken-zip +Severity: warning +Check: files/compressed/zip +Info: The given file ends with .zip, which normally indicates it + was compressed with zip. However, it doesn't seem to be a + zip-compressed file. diff -Nru lintian-2.93.0/tags/b/broken-zip.tag lintian-2.89.0ubuntu1/tags/b/broken-zip.tag --- lintian-2.93.0/tags/b/broken-zip.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/broken-zip.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: broken-zip -Severity: warning -Check: files/compressed/zip -Explanation: The given file ends with .zip, which normally indicates it - was compressed with zip. However, it doesn't seem to be a - zip-compressed file. diff -Nru lintian-2.93.0/tags/b/bugs-field-does-not-refer-to-debian-infrastructure.desc lintian-2.89.0ubuntu1/tags/b/bugs-field-does-not-refer-to-debian-infrastructure.desc --- lintian-2.93.0/tags/b/bugs-field-does-not-refer-to-debian-infrastructure.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/bugs-field-does-not-refer-to-debian-infrastructure.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: bugs-field-does-not-refer-to-debian-infrastructure +Severity: warning +Certainty: possible +Check: fields/bugs +Info: The debian/control file contains a Bugs field that does + not refer to Debian infrastructure. This is recognized by the string + ".debian.org". + . + This is likely to make reportbug(1) unable to report bugs. +Ref: #740944 diff -Nru lintian-2.93.0/tags/b/bugs-field-does-not-refer-to-debian-infrastructure.tag lintian-2.89.0ubuntu1/tags/b/bugs-field-does-not-refer-to-debian-infrastructure.tag --- lintian-2.93.0/tags/b/bugs-field-does-not-refer-to-debian-infrastructure.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/bugs-field-does-not-refer-to-debian-infrastructure.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: bugs-field-does-not-refer-to-debian-infrastructure -Severity: warning -Check: fields/bugs -Explanation: The debian/control file contains a Bugs field that does - not refer to Debian infrastructure. This is recognized by the string - ".debian.org". - . - This is likely to make reportbug(1) unable to report bugs. -See-Also: Bug#740944 diff -Nru lintian-2.93.0/tags/b/build-conflicts-with-build-dependency.desc lintian-2.89.0ubuntu1/tags/b/build-conflicts-with-build-dependency.desc --- lintian-2.93.0/tags/b/build-conflicts-with-build-dependency.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/build-conflicts-with-build-dependency.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: build-conflicts-with-build-dependency +Severity: error +Check: fields/package-relations +Ref: policy 7.7 +Info: The package build-conflicts with a package that it also + build-depends on. diff -Nru lintian-2.93.0/tags/b/build-conflicts-with-build-dependency.tag lintian-2.89.0ubuntu1/tags/b/build-conflicts-with-build-dependency.tag --- lintian-2.93.0/tags/b/build-conflicts-with-build-dependency.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/build-conflicts-with-build-dependency.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: build-conflicts-with-build-dependency -Severity: error -Check: fields/package-relations -See-Also: policy 7.7 -Explanation: The package build-conflicts with a package that it also - build-depends on. diff -Nru lintian-2.93.0/tags/b/build-depends-arch-without-arch-dependent-binary.desc lintian-2.89.0ubuntu1/tags/b/build-depends-arch-without-arch-dependent-binary.desc --- lintian-2.93.0/tags/b/build-depends-arch-without-arch-dependent-binary.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/build-depends-arch-without-arch-dependent-binary.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,5 @@ +Tag: build-depends-arch-without-arch-dependent-binary +Severity: error +Check: fields/package-relations +Info: The control file specifies source relations for architecture-dependent + packages, but no architecture-dependent packages are built. diff -Nru lintian-2.93.0/tags/b/build-depends-arch-without-arch-dependent-binary.tag lintian-2.89.0ubuntu1/tags/b/build-depends-arch-without-arch-dependent-binary.tag --- lintian-2.93.0/tags/b/build-depends-arch-without-arch-dependent-binary.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/build-depends-arch-without-arch-dependent-binary.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,5 +0,0 @@ -Tag: build-depends-arch-without-arch-dependent-binary -Severity: error -Check: fields/package-relations -Explanation: The control file specifies source relations for architecture-dependent - packages, but no architecture-dependent packages are built. diff -Nru lintian-2.93.0/tags/b/build-depends-indep-without-arch-indep.desc lintian-2.89.0ubuntu1/tags/b/build-depends-indep-without-arch-indep.desc --- lintian-2.93.0/tags/b/build-depends-indep-without-arch-indep.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/build-depends-indep-without-arch-indep.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: build-depends-indep-without-arch-indep +Severity: error +Check: fields/package-relations +Ref: policy 7.7 +Info: The control file specifies source relations for architecture-independent + packages, but no architecture-independent packages are built. diff -Nru lintian-2.93.0/tags/b/build-depends-indep-without-arch-indep.tag lintian-2.89.0ubuntu1/tags/b/build-depends-indep-without-arch-indep.tag --- lintian-2.93.0/tags/b/build-depends-indep-without-arch-indep.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/build-depends-indep-without-arch-indep.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: build-depends-indep-without-arch-indep -Severity: error -Check: fields/package-relations -See-Also: policy 7.7 -Explanation: The control file specifies source relations for architecture-independent - packages, but no architecture-independent packages are built. diff -Nru lintian-2.93.0/tags/b/build-depends-on-1-revision.desc lintian-2.89.0ubuntu1/tags/b/build-depends-on-1-revision.desc --- lintian-2.93.0/tags/b/build-depends-on-1-revision.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/build-depends-on-1-revision.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,11 @@ +Tag: build-depends-on-1-revision +Severity: warning +Certainty: possible +Check: fields/package-relations +Info: The package declares a build dependency on a version of a package + with a -1 Debian revision such as "libfoo (>= 1.2-1)". Such a + dependency will not be satisfied by a backport of libfoo 1.2-1 and + therefore makes backporting unnecessarily difficult. Normally, the -1 + version is unneeded and a dependency such as "libfoo (>= 1.2)" would + be sufficient. If there was an earlier -0.X version of libfoo that would + not satisfy the dependency, use "libfoo (>= 1.2-1~)" instead. diff -Nru lintian-2.93.0/tags/b/build-depends-on-1-revision.tag lintian-2.89.0ubuntu1/tags/b/build-depends-on-1-revision.tag --- lintian-2.93.0/tags/b/build-depends-on-1-revision.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/build-depends-on-1-revision.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,10 +0,0 @@ -Tag: build-depends-on-1-revision -Severity: warning -Check: fields/package-relations -Explanation: The package declares a build dependency on a version of a package - with a -1 Debian revision such as "libfoo (>= 1.2-1)". Such a - dependency will not be satisfied by a backport of libfoo 1.2-1 and - therefore makes backporting unnecessarily difficult. Normally, the -1 - version is unneeded and a dependency such as "libfoo (>= 1.2)" would - be sufficient. If there was an earlier -0.X version of libfoo that would - not satisfy the dependency, use "libfoo (>= 1.2-1~)" instead. diff -Nru lintian-2.93.0/tags/b/build-depends-on-an-obsolete-java-package.desc lintian-2.89.0ubuntu1/tags/b/build-depends-on-an-obsolete-java-package.desc --- lintian-2.93.0/tags/b/build-depends-on-an-obsolete-java-package.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/build-depends-on-an-obsolete-java-package.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: build-depends-on-an-obsolete-java-package +Severity: warning +Check: fields/package-relations +Ref: java-policy 2.2 +Info: The package build-depends on an obsolete Java dependency. + It should build-depend on default-jdk instead. diff -Nru lintian-2.93.0/tags/b/build-depends-on-an-obsolete-java-package.tag lintian-2.89.0ubuntu1/tags/b/build-depends-on-an-obsolete-java-package.tag --- lintian-2.93.0/tags/b/build-depends-on-an-obsolete-java-package.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/build-depends-on-an-obsolete-java-package.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: build-depends-on-an-obsolete-java-package -Severity: warning -Check: fields/package-relations -See-Also: java-policy 2.2 -Explanation: The package build-depends on an obsolete Java dependency. - It should build-depend on default-jdk instead. diff -Nru lintian-2.93.0/tags/b/build-depends-on-build-essential.desc lintian-2.89.0ubuntu1/tags/b/build-depends-on-build-essential.desc --- lintian-2.93.0/tags/b/build-depends-on-build-essential.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/build-depends-on-build-essential.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: build-depends-on-build-essential +Info: You depend on the build-essential package, which is only a + metapackage depending on build tools that have to be installed in all + build environments. +Severity: error +Check: fields/package-relations +Ref: policy 7.7 diff -Nru lintian-2.93.0/tags/b/build-depends-on-build-essential-package-without-using-version.desc lintian-2.89.0ubuntu1/tags/b/build-depends-on-build-essential-package-without-using-version.desc --- lintian-2.93.0/tags/b/build-depends-on-build-essential-package-without-using-version.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/build-depends-on-build-essential-package-without-using-version.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,13 @@ +Tag: build-depends-on-build-essential-package-without-using-version +Severity: error +Check: fields/package-relations +Ref: policy 4.2 +Info: The package declares a build-depends on a build essential package + without using a versioned depends. Packages do not have to depend on any + package included in build-essential. It is the responsibility of anyone + building packages to have all build-essential packages installed. The + only reason for an explicit dependency on a package included in + build-essential is if a particular version of that package is required, + in which case the dependency should include the version. +Renamed-From: + depends-on-build-essential-package-without-using-version diff -Nru lintian-2.93.0/tags/b/build-depends-on-build-essential-package-without-using-version.tag lintian-2.89.0ubuntu1/tags/b/build-depends-on-build-essential-package-without-using-version.tag --- lintian-2.93.0/tags/b/build-depends-on-build-essential-package-without-using-version.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/build-depends-on-build-essential-package-without-using-version.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,13 +0,0 @@ -Tag: build-depends-on-build-essential-package-without-using-version -Severity: error -Check: fields/package-relations -See-Also: policy 4.2 -Explanation: The package declares a build-depends on a build essential package - without using a versioned depends. Packages do not have to depend on any - package included in build-essential. It is the responsibility of anyone - building packages to have all build-essential packages installed. The - only reason for an explicit dependency on a package included in - build-essential is if a particular version of that package is required, - in which case the dependency should include the version. -Renamed-From: - depends-on-build-essential-package-without-using-version diff -Nru lintian-2.93.0/tags/b/build-depends-on-build-essential.tag lintian-2.89.0ubuntu1/tags/b/build-depends-on-build-essential.tag --- lintian-2.93.0/tags/b/build-depends-on-build-essential.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/build-depends-on-build-essential.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: build-depends-on-build-essential -Explanation: You depend on the build-essential package, which is only a - metapackage depending on build tools that have to be installed in all - build environments. -Severity: error -Check: fields/package-relations -See-Also: policy 7.7 diff -Nru lintian-2.93.0/tags/b/build-depends-on-essential-package-without-using-version.desc lintian-2.89.0ubuntu1/tags/b/build-depends-on-essential-package-without-using-version.desc --- lintian-2.93.0/tags/b/build-depends-on-essential-package-without-using-version.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/build-depends-on-essential-package-without-using-version.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: build-depends-on-essential-package-without-using-version +Severity: error +Check: fields/package-relations +Ref: policy 4.2 +Info: The package declares a build-depends on an essential package, e.g. dpkg, + without using a versioned depends. Packages do not need to build-depend on + essential packages; essential means that they will always be present. + The only reason to list an explicit dependency on an essential package + is if you need a particular version of that package, in which case the + version should be given in the dependency. diff -Nru lintian-2.93.0/tags/b/build-depends-on-essential-package-without-using-version.tag lintian-2.89.0ubuntu1/tags/b/build-depends-on-essential-package-without-using-version.tag --- lintian-2.93.0/tags/b/build-depends-on-essential-package-without-using-version.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/build-depends-on-essential-package-without-using-version.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,10 +0,0 @@ -Tag: build-depends-on-essential-package-without-using-version -Severity: error -Check: fields/package-relations -See-Also: policy 4.2 -Explanation: The package declares a build-depends on an essential package, e.g. dpkg, - without using a versioned depends. Packages do not need to build-depend on - essential packages; essential means that they will always be present. - The only reason to list an explicit dependency on an essential package - is if you need a particular version of that package, in which case the - version should be given in the dependency. diff -Nru lintian-2.93.0/tags/b/build-depends-on-metapackage.desc lintian-2.89.0ubuntu1/tags/b/build-depends-on-metapackage.desc --- lintian-2.93.0/tags/b/build-depends-on-metapackage.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/build-depends-on-metapackage.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: build-depends-on-metapackage +Severity: error +Check: fields/package-relations +Info: Packages must not build-depend on metapackages. + . + Metapackages such as xorg, xorg-dev, x-window-system, + x-window-system-dev and x-window-system-core exist only for the + benefit of users and should not be used in package build + dependencies. +Ref: https://wiki.debian.org/Lintian/Tags/depends-on-metapackage diff -Nru lintian-2.93.0/tags/b/build-depends-on-metapackage.tag lintian-2.89.0ubuntu1/tags/b/build-depends-on-metapackage.tag --- lintian-2.93.0/tags/b/build-depends-on-metapackage.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/build-depends-on-metapackage.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,10 +0,0 @@ -Tag: build-depends-on-metapackage -Severity: error -Check: fields/package-relations -Explanation: Packages must not build-depend on metapackages. - . - Metapackages such as xorg, xorg-dev, x-window-system, - x-window-system-dev and x-window-system-core exist only for the - benefit of users and should not be used in package build - dependencies. -See-Also: https://wiki.debian.org/Lintian/Tags/depends-on-metapackage diff -Nru lintian-2.93.0/tags/b/build-depends-on-non-build-package.desc lintian-2.89.0ubuntu1/tags/b/build-depends-on-non-build-package.desc --- lintian-2.93.0/tags/b/build-depends-on-non-build-package.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/build-depends-on-non-build-package.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: build-depends-on-non-build-package +Severity: error +Check: fields/package-relations +Info: The package declares a build dependency on a package that is not + appropriate for build dependencies, usually because it's only for + interactive use or cannot be correctly installed in a build environment. + See the description or documentation of the package for more + information. diff -Nru lintian-2.93.0/tags/b/build-depends-on-non-build-package.tag lintian-2.89.0ubuntu1/tags/b/build-depends-on-non-build-package.tag --- lintian-2.93.0/tags/b/build-depends-on-non-build-package.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/build-depends-on-non-build-package.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: build-depends-on-non-build-package -Severity: error -Check: fields/package-relations -Explanation: The package declares a build dependency on a package that is not - appropriate for build dependencies, usually because it's only for - interactive use or cannot be correctly installed in a build environment. - See the description or documentation of the package for more - information. diff -Nru lintian-2.93.0/tags/b/build-depends-on-obsolete-package.desc lintian-2.89.0ubuntu1/tags/b/build-depends-on-obsolete-package.desc --- lintian-2.93.0/tags/b/build-depends-on-obsolete-package.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/build-depends-on-obsolete-package.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: build-depends-on-obsolete-package +Severity: warning +Certainty: possible +Check: fields/package-relations +Info: The package build-depends on a package that has been superseded. + If the superseded package is part of an ORed group, it should not be + the first package in the group. diff -Nru lintian-2.93.0/tags/b/build-depends-on-obsolete-package.tag lintian-2.89.0ubuntu1/tags/b/build-depends-on-obsolete-package.tag --- lintian-2.93.0/tags/b/build-depends-on-obsolete-package.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/build-depends-on-obsolete-package.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: build-depends-on-obsolete-package -Severity: warning -Check: fields/package-relations -Explanation: The package build-depends on a package that has been superseded. - If the superseded package is part of an ORed group, it should not be - the first package in the group. diff -Nru lintian-2.93.0/tags/b/build-depends-on-python-dev-with-no-arch-any.desc lintian-2.89.0ubuntu1/tags/b/build-depends-on-python-dev-with-no-arch-any.desc --- lintian-2.93.0/tags/b/build-depends-on-python-dev-with-no-arch-any.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/build-depends-on-python-dev-with-no-arch-any.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,14 @@ +Tag: build-depends-on-python-dev-with-no-arch-any +Severity: info +Certainty: possible +Check: fields/package-relations +Info: The given package appears to have a Python development package + (python-dev, python-all-dev or pythonX.Y-dev) listed in its Build-Depends + or Build-Depends-Indep fields, but only "Architecture: all" packages are + built by this source package. Python applications and modules do not + usually require those dev packages, so you should consider removing them + in favour of python, python-all or pythonX.Y. + . + If you are building a Python extension instead, you should have + development packages listed in Build-Depends, but normally there should + be at least one Architecture: any package. diff -Nru lintian-2.93.0/tags/b/build-depends-on-python-dev-with-no-arch-any.tag lintian-2.89.0ubuntu1/tags/b/build-depends-on-python-dev-with-no-arch-any.tag --- lintian-2.93.0/tags/b/build-depends-on-python-dev-with-no-arch-any.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/build-depends-on-python-dev-with-no-arch-any.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,13 +0,0 @@ -Tag: build-depends-on-python-dev-with-no-arch-any -Severity: info -Check: fields/package-relations -Explanation: The given package appears to have a Python development package - (python-dev, python-all-dev or pythonX.Y-dev) listed in its Build-Depends - or Build-Depends-Indep fields, but only "Architecture: all" packages are - built by this source package. Python applications and modules do not - usually require those dev packages, so you should consider removing them - in favour of python, python-all or pythonX.Y. - . - If you are building a Python extension instead, you should have - development packages listed in Build-Depends, but normally there should - be at least one Architecture: any package. diff -Nru lintian-2.93.0/tags/b/build-depends-on-python-sphinx-only.desc lintian-2.89.0ubuntu1/tags/b/build-depends-on-python-sphinx-only.desc --- lintian-2.93.0/tags/b/build-depends-on-python-sphinx-only.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/build-depends-on-python-sphinx-only.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,13 @@ +Tag: build-depends-on-python-sphinx-only +Severity: warning +Check: languages/python +Info: This package Build-Depends on the Python 2.x version of the Sphinx + documentation generator. + . + The 2.x series of Python is due for deprecation and will not be maintained + by upstream past 2020 and will likely be dropped after the release of + Debian "buster". + . + Some Python modules may need to depend on both python-sphinx and + python3-sphinx but please consider moving to only Build-Depending on + the python3-sphinx package instead. diff -Nru lintian-2.93.0/tags/b/build-depends-on-python-sphinx-only.tag lintian-2.89.0ubuntu1/tags/b/build-depends-on-python-sphinx-only.tag --- lintian-2.93.0/tags/b/build-depends-on-python-sphinx-only.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/build-depends-on-python-sphinx-only.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,13 +0,0 @@ -Tag: build-depends-on-python-sphinx-only -Severity: warning -Check: languages/python -Explanation: This package Build-Depends on the Python 2.x version of the Sphinx - documentation generator. - . - The 2.x series of Python is due for deprecation and will not be maintained - by upstream past 2020 and will likely be dropped after the release of - Debian "buster". - . - Some Python modules may need to depend on both python-sphinx and - python3-sphinx but please consider moving to only Build-Depending on - the python3-sphinx package instead. diff -Nru lintian-2.93.0/tags/b/build-depends-on-specific-java-doc-package.desc lintian-2.89.0ubuntu1/tags/b/build-depends-on-specific-java-doc-package.desc --- lintian-2.93.0/tags/b/build-depends-on-specific-java-doc-package.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/build-depends-on-specific-java-doc-package.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: build-depends-on-specific-java-doc-package +Severity: warning +Check: fields/package-relations +Info: The given package declares a build dependency on either openjdk- + X-doc or classpath-doc instead of using default-jdk-doc. default-jdk-doc + provides a symlink to the API via /usr/share/default-jdk-doc/api. diff -Nru lintian-2.93.0/tags/b/build-depends-on-specific-java-doc-package.tag lintian-2.89.0ubuntu1/tags/b/build-depends-on-specific-java-doc-package.tag --- lintian-2.93.0/tags/b/build-depends-on-specific-java-doc-package.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/build-depends-on-specific-java-doc-package.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: build-depends-on-specific-java-doc-package -Severity: warning -Check: fields/package-relations -Explanation: The given package declares a build dependency on either openjdk- - X-doc or classpath-doc instead of using default-jdk-doc. default-jdk-doc - provides a symlink to the API via /usr/share/default-jdk-doc/api. diff -Nru lintian-2.93.0/tags/b/build-depends-on-versioned-berkeley-db.desc lintian-2.89.0ubuntu1/tags/b/build-depends-on-versioned-berkeley-db.desc --- lintian-2.93.0/tags/b/build-depends-on-versioned-berkeley-db.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/build-depends-on-versioned-berkeley-db.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,26 @@ +Tag: build-depends-on-versioned-berkeley-db +Severity: warning +Certainty: possible +Check: fields/package-relations +Info: The package build-depends on a versioned development package of + Berkeley DB (libdbX.Y-dev) instead of versionless package + (libdb-dev). Unfortunately this prevents binNMUs when default + Berkeley DB version changes. + . + Unless the package absolutely have to depend on specific Berkeley DB + version, it should build-depends on libdb-dev. For more information + on the upgrade process, please see the references. + . + The package can usually be made Berkeley DB version agnostic by the + following steps: + . + 1. note the version of Berkeley DB used to compile the package on build time + 2. on first install copy the used version to active version + 3. on upgrades compare the versions and if they differ do the upgrade procedure + . + If you are unsure you can contact Berkeley DB maintainer, who would be + glad to help. + . + Should the package have a legitimate reason for using the versioned development + package, please add an override. +Ref: http://docs.oracle.com/cd/E17076_02/html/upgrading/upgrade_process.html diff -Nru lintian-2.93.0/tags/b/build-depends-on-versioned-berkeley-db.tag lintian-2.89.0ubuntu1/tags/b/build-depends-on-versioned-berkeley-db.tag --- lintian-2.93.0/tags/b/build-depends-on-versioned-berkeley-db.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/build-depends-on-versioned-berkeley-db.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,25 +0,0 @@ -Tag: build-depends-on-versioned-berkeley-db -Severity: warning -Check: fields/package-relations -Explanation: The package build-depends on a versioned development package of - Berkeley DB (libdbX.Y-dev) instead of versionless package - (libdb-dev). Unfortunately this prevents binNMUs when default - Berkeley DB version changes. - . - Unless the package absolutely have to depend on specific Berkeley DB - version, it should build-depends on libdb-dev. For more information - on the upgrade process, please see the references. - . - The package can usually be made Berkeley DB version agnostic by the - following steps: - . - 1. note the version of Berkeley DB used to compile the package on build time - 2. on first install copy the used version to active version - 3. on upgrades compare the versions and if they differ do the upgrade procedure - . - If you are unsure you can contact Berkeley DB maintainer, who would be - glad to help. - . - Should the package have a legitimate reason for using the versioned development - package, please add an override. -See-Also: http://docs.oracle.com/cd/E17076_02/html/upgrading/upgrade_process.html diff -Nru lintian-2.93.0/tags/b/build-info-in-binary-control-file-section.desc lintian-2.89.0ubuntu1/tags/b/build-info-in-binary-control-file-section.desc --- lintian-2.93.0/tags/b/build-info-in-binary-control-file-section.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/build-info-in-binary-control-file-section.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: build-info-in-binary-control-file-section +Severity: error +Check: debian/control +Ref: policy 5.2 +Info: The control file has a Build-Depends, Build-Depends-Indep, + Build-Conflicts, or Build-Conflicts-Indep field in a binary + section. These specify source package relationships, and should be in + the source section of the control file. diff -Nru lintian-2.93.0/tags/b/build-info-in-binary-control-file-section.tag lintian-2.89.0ubuntu1/tags/b/build-info-in-binary-control-file-section.tag --- lintian-2.93.0/tags/b/build-info-in-binary-control-file-section.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/build-info-in-binary-control-file-section.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: build-info-in-binary-control-file-section -Severity: error -Check: debian/control -See-Also: policy 5.2 -Explanation: The control file has a Build-Depends, Build-Depends-Indep, - Build-Conflicts, or Build-Conflicts-Indep field in a binary - section. These specify source package relationships, and should be in - the source section of the control file. diff -Nru lintian-2.93.0/tags/b/build-path-in-manual.desc lintian-2.89.0ubuntu1/tags/b/build-path-in-manual.desc --- lintian-2.93.0/tags/b/build-path-in-manual.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/build-path-in-manual.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: build-path-in-manual +Severity: error +Check: documentation/manual +Renamed-From: manpage-named-after-build-path +Info: The manual page appears to be named after its build path and + not after its content. + . + Please check your debian/rules or upstream Makefile. diff -Nru lintian-2.93.0/tags/b/build-path-in-manual.tag lintian-2.89.0ubuntu1/tags/b/build-path-in-manual.tag --- lintian-2.93.0/tags/b/build-path-in-manual.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/build-path-in-manual.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: build-path-in-manual -Severity: error -Check: documentation/manual -Renamed-From: manpage-named-after-build-path -Explanation: The manual page appears to be named after its build path and - not after its content. - . - Please check your debian/rules or upstream Makefile. diff -Nru lintian-2.93.0/tags/b/built-using-field-on-arch-all-package.desc lintian-2.89.0ubuntu1/tags/b/built-using-field-on-arch-all-package.desc --- lintian-2.93.0/tags/b/built-using-field-on-arch-all-package.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/built-using-field-on-arch-all-package.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: built-using-field-on-arch-all-package +Severity: info +Check: debian/control +Info: This package builds a binary arch:all package which incorrectly + specifies a Built-Using control field. + . + Built-Using only applies to architecture-specific packages. + . + Please remove the Built-Using line from your package + definition. diff -Nru lintian-2.93.0/tags/b/built-using-field-on-arch-all-package.tag lintian-2.89.0ubuntu1/tags/b/built-using-field-on-arch-all-package.tag --- lintian-2.93.0/tags/b/built-using-field-on-arch-all-package.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/b/built-using-field-on-arch-all-package.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,10 +0,0 @@ -Tag: built-using-field-on-arch-all-package -Severity: info -Check: debian/control -Explanation: This package builds a binary arch:all package which incorrectly - specifies a Built-Using control field. - . - Built-Using only applies to architecture-specific packages. - . - Please remove the Built-Using line from your package - definition. diff -Nru lintian-2.93.0/tags/c/cannot-check-whether-usr-share-doc-symlink-points-to-foreign-package.desc lintian-2.89.0ubuntu1/tags/c/cannot-check-whether-usr-share-doc-symlink-points-to-foreign-package.desc --- lintian-2.93.0/tags/c/cannot-check-whether-usr-share-doc-symlink-points-to-foreign-package.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/cannot-check-whether-usr-share-doc-symlink-points-to-foreign-package.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,11 @@ +Tag: cannot-check-whether-usr-share-doc-symlink-points-to-foreign-package +Severity: info +Certainty: possible +Check: debian/copyright +Info: There is a symlink /usr/share/doc/pkg1 -> pkg2 + in your package. This means that pkg1 and pkg2 must + both come from the same source package. Lintian cannot check this right now + however. + . + Please reprocess this binary together with its source package to avoid + this tag. diff -Nru lintian-2.93.0/tags/c/cannot-check-whether-usr-share-doc-symlink-points-to-foreign-package.tag lintian-2.89.0ubuntu1/tags/c/cannot-check-whether-usr-share-doc-symlink-points-to-foreign-package.tag --- lintian-2.93.0/tags/c/cannot-check-whether-usr-share-doc-symlink-points-to-foreign-package.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/cannot-check-whether-usr-share-doc-symlink-points-to-foreign-package.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,10 +0,0 @@ -Tag: cannot-check-whether-usr-share-doc-symlink-points-to-foreign-package -Severity: info -Check: debian/copyright -Explanation: There is a symlink /usr/share/doc/*pkg1* -> *pkg2* - in your package. This means that *pkg1* and *pkg2* must - both come from the same source package. Lintian cannot check this right now - however. - . - Please reprocess this binary together with its source package to avoid - this tag. diff -Nru lintian-2.93.0/tags/c/capitalization-error-in-description.desc lintian-2.89.0ubuntu1/tags/c/capitalization-error-in-description.desc --- lintian-2.93.0/tags/c/capitalization-error-in-description.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/capitalization-error-in-description.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,13 @@ +Tag: capitalization-error-in-description +Severity: info +Certainty: wild-guess +Check: fields/description +Info: Lintian found a possible capitalization error in the package + description. Lintian has a list of common capitalization errors, + primarily of upstream projects, that it looks for. It does not have a + dictionary like a spelling checker does. + . + This is a particularly picky check of capitalization in package + descriptions, since they're very visible to end users, but it will have + false positives for project names used in a context where they should be + lowercase, such as package names or executable names. diff -Nru lintian-2.93.0/tags/c/capitalization-error-in-description-synopsis.desc lintian-2.89.0ubuntu1/tags/c/capitalization-error-in-description-synopsis.desc --- lintian-2.93.0/tags/c/capitalization-error-in-description-synopsis.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/capitalization-error-in-description-synopsis.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: capitalization-error-in-description-synopsis +Severity: info +Certainty: wild-guess +Check: fields/description +Info: Lintian found a possible capitalization error in the package + synopsis. Lintian has a list of common capitalization errors, + primarily of upstream projects, that it looks for. It does not have a + dictionary like a spelling checker does. diff -Nru lintian-2.93.0/tags/c/capitalization-error-in-description-synopsis.tag lintian-2.89.0ubuntu1/tags/c/capitalization-error-in-description-synopsis.tag --- lintian-2.93.0/tags/c/capitalization-error-in-description-synopsis.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/capitalization-error-in-description-synopsis.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: capitalization-error-in-description-synopsis -Severity: info -Check: fields/description -Explanation: Lintian found a possible capitalization error in the package - synopsis. Lintian has a list of common capitalization errors, - primarily of upstream projects, that it looks for. It does not have a - dictionary like a spelling checker does. diff -Nru lintian-2.93.0/tags/c/capitalization-error-in-description.tag lintian-2.89.0ubuntu1/tags/c/capitalization-error-in-description.tag --- lintian-2.93.0/tags/c/capitalization-error-in-description.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/capitalization-error-in-description.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,12 +0,0 @@ -Tag: capitalization-error-in-description -Severity: info -Check: fields/description -Explanation: Lintian found a possible capitalization error in the package - description. Lintian has a list of common capitalization errors, - primarily of upstream projects, that it looks for. It does not have a - dictionary like a spelling checker does. - . - This is a particularly picky check of capitalization in package - descriptions, since they're very visible to end users, but it will have - false positives for project names used in a context where they should be - lowercase, such as package names or executable names. diff -Nru lintian-2.93.0/tags/c/capitalization-in-override-comment.desc lintian-2.89.0ubuntu1/tags/c/capitalization-in-override-comment.desc --- lintian-2.93.0/tags/c/capitalization-in-override-comment.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/capitalization-in-override-comment.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: capitalization-in-override-comment +Severity: info +Check: debian/lintian-overrides/comments +Info: The comment attached to a Lintian override probably contains + a capitalization error. + . + Lintian looks for common capitalization errors. It does not have a + dictionary. diff -Nru lintian-2.93.0/tags/c/capitalization-in-override-comment.tag lintian-2.89.0ubuntu1/tags/c/capitalization-in-override-comment.tag --- lintian-2.93.0/tags/c/capitalization-in-override-comment.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/capitalization-in-override-comment.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: capitalization-in-override-comment -Severity: pedantic -Check: debian/lintian-overrides/comments -Explanation: The comment attached to a Lintian override probably contains - a capitalization error. - . - Lintian looks for common capitalization errors. It does not have a - dictionary. diff -Nru lintian-2.93.0/tags/c/carriage-return-line-feed.desc lintian-2.89.0ubuntu1/tags/c/carriage-return-line-feed.desc --- lintian-2.93.0/tags/c/carriage-return-line-feed.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/carriage-return-line-feed.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,13 @@ +Tag: carriage-return-line-feed +Severity: error +Check: debian/line-separators +Renamed-From: control-file-with-CRLF-EOLs +Info: The given control file uses CRLF as line terminator + instead of the traditional UNIX LF terminator. Since some + tools were only designed with the UNIX end-of-line terminators in mind, + it is possible that they misbehave or lead to unexpected results. + . + Running the following command against the given file removes any + CR character in the file: + . + sed -i 's/\r//g' path/to/file diff -Nru lintian-2.93.0/tags/c/carriage-return-line-feed.tag lintian-2.89.0ubuntu1/tags/c/carriage-return-line-feed.tag --- lintian-2.93.0/tags/c/carriage-return-line-feed.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/carriage-return-line-feed.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,13 +0,0 @@ -Tag: carriage-return-line-feed -Severity: error -Check: debian/line-separators -Renamed-From: control-file-with-CRLF-EOLs -Explanation: The given control file uses CRLF as line terminator - instead of the traditional UNIX LF terminator. Since some - tools were only designed with the UNIX end-of-line terminators in mind, - it is possible that they misbehave or lead to unexpected results. - . - Running the following command against the given file removes any - CR character in the file: - . - sed -i 's/\r//g' path/to/file diff -Nru lintian-2.93.0/tags/c/changed-by-invalid-for-derivative.desc lintian-2.89.0ubuntu1/tags/c/changed-by-invalid-for-derivative.desc --- lintian-2.93.0/tags/c/changed-by-invalid-for-derivative.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/changed-by-invalid-for-derivative.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: changed-by-invalid-for-derivative +Severity: error +Check: fields/changed-by +Info: The Changed-By field does not match the required format for this + Debian derivative. + . + Derivative distributions of Debian may enforce additional restrictions + on such fields. diff -Nru lintian-2.93.0/tags/c/changed-by-invalid-for-derivative.tag lintian-2.89.0ubuntu1/tags/c/changed-by-invalid-for-derivative.tag --- lintian-2.93.0/tags/c/changed-by-invalid-for-derivative.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/changed-by-invalid-for-derivative.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: changed-by-invalid-for-derivative -Severity: error -Check: fields/changed-by -Explanation: The Changed-By field does not match the required format for this - Debian derivative. - . - Derivative distributions of Debian may enforce additional restrictions - on such fields. diff -Nru lintian-2.93.0/tags/c/changelog-distribution-does-not-match-changes-file.desc lintian-2.89.0ubuntu1/tags/c/changelog-distribution-does-not-match-changes-file.desc --- lintian-2.93.0/tags/c/changelog-distribution-does-not-match-changes-file.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/changelog-distribution-does-not-match-changes-file.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,12 @@ +Tag: changelog-distribution-does-not-match-changes-file +Severity: warning +Certainty: possible +Check: debian/changelog +Info: The target distribution in the most recent entry in this package's + debian/changelog file does not match the target in the generated + .changes file. + . + This may indicate a mistake in setting the distribution, an accidental + upload to unstable of a package intended for experimental, or a mistake + in invoking sbuild(1). +Ref: #906155, sbuild(1) diff -Nru lintian-2.93.0/tags/c/changelog-distribution-does-not-match-changes-file.tag lintian-2.89.0ubuntu1/tags/c/changelog-distribution-does-not-match-changes-file.tag --- lintian-2.93.0/tags/c/changelog-distribution-does-not-match-changes-file.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/changelog-distribution-does-not-match-changes-file.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,11 +0,0 @@ -Tag: changelog-distribution-does-not-match-changes-file -Severity: warning -Check: debian/changelog -Explanation: The target distribution in the most recent entry in this package's - debian/changelog file does not match the target in the generated - .changes file. - . - This may indicate a mistake in setting the distribution, an accidental - upload to unstable of a package intended for experimental, or a mistake - in invoking sbuild(1). -See-Also: Bug#906155, sbuild(1) diff -Nru lintian-2.93.0/tags/c/changelog-empty-entry.desc lintian-2.89.0ubuntu1/tags/c/changelog-empty-entry.desc --- lintian-2.93.0/tags/c/changelog-empty-entry.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/changelog-empty-entry.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: changelog-empty-entry +Severity: error +Check: debian/changelog +Info: The last changelog entry is empty. Please add a description or use + an UNRELEASED version. +Ref: policy 4.4 diff -Nru lintian-2.93.0/tags/c/changelog-empty-entry.tag lintian-2.89.0ubuntu1/tags/c/changelog-empty-entry.tag --- lintian-2.93.0/tags/c/changelog-empty-entry.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/changelog-empty-entry.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: changelog-empty-entry -Severity: error -Check: debian/changelog -Explanation: The last changelog entry is empty. Please add a description or use - an UNRELEASED version. -See-Also: policy 4.4 diff -Nru lintian-2.93.0/tags/c/changelog-file-missing-explicit-entry.desc lintian-2.89.0ubuntu1/tags/c/changelog-file-missing-explicit-entry.desc --- lintian-2.93.0/tags/c/changelog-file-missing-explicit-entry.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/changelog-file-missing-explicit-entry.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,11 @@ +Tag: changelog-file-missing-explicit-entry +Severity: warning +Check: debian/changelog +Info: The latest changelog file for this package specifies a version in + the form of 1.2-3+deb8u1, 1.2-3+nmu4 (or similar) but this does not + follow from a corresponding 1.2-3 changelog stanza. + . + This suggests that changes were merged into a single entry. This is + suboptimal as it makes it more difficult for users to determine which + upload fixed a particular bug. +Ref: devref 5.8.5.4, devref 5.11.2, devref 5.14.3, #916877 diff -Nru lintian-2.93.0/tags/c/changelog-file-missing-explicit-entry.tag lintian-2.89.0ubuntu1/tags/c/changelog-file-missing-explicit-entry.tag --- lintian-2.93.0/tags/c/changelog-file-missing-explicit-entry.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/changelog-file-missing-explicit-entry.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,11 +0,0 @@ -Tag: changelog-file-missing-explicit-entry -Severity: warning -Check: debian/changelog -Explanation: The latest changelog file for this package specifies a version in - the form of 1.2-3+deb8u1, 1.2-3+nmu4 (or similar) but this does not - follow from a corresponding 1.2-3 changelog stanza. - . - This suggests that changes were merged into a single entry. This is - suboptimal as it makes it more difficult for users to determine which - upload fixed a particular bug. -See-Also: devref 5.8.5.4, devref 5.11.2, devref 5.14.3, Bug#916877 diff -Nru lintian-2.93.0/tags/c/changelog-file-not-compressed.desc lintian-2.89.0ubuntu1/tags/c/changelog-file-not-compressed.desc --- lintian-2.93.0/tags/c/changelog-file-not-compressed.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/changelog-file-not-compressed.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: changelog-file-not-compressed +Severity: error +Check: debian/changelog +Info: Changelog files should be compressed using "gzip -9". Even if they + start out small, they will become large with time. +Ref: policy 12.7 diff -Nru lintian-2.93.0/tags/c/changelog-file-not-compressed.tag lintian-2.89.0ubuntu1/tags/c/changelog-file-not-compressed.tag --- lintian-2.93.0/tags/c/changelog-file-not-compressed.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/changelog-file-not-compressed.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: changelog-file-not-compressed -Severity: error -Check: debian/changelog -Explanation: Changelog files should be compressed using "gzip -9". Even if they - start out small, they will become large with time. -See-Also: policy 12.7 diff -Nru lintian-2.93.0/tags/c/changelog-is-dh_make-template.desc lintian-2.89.0ubuntu1/tags/c/changelog-is-dh_make-template.desc --- lintian-2.93.0/tags/c/changelog-is-dh_make-template.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/changelog-is-dh_make-template.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: changelog-is-dh_make-template +Severity: error +Check: debian/changelog +Info: The changelog file has an instruction left by dh_make, which has + not been removed. Example: + . + * Initial release (Closes: #nnnn) <nnnn is the bug number of your ITP> + . + The "<... is the bug number ...>" part has not been removed from the + changelog. diff -Nru lintian-2.93.0/tags/c/changelog-is-dh_make-template.tag lintian-2.89.0ubuntu1/tags/c/changelog-is-dh_make-template.tag --- lintian-2.93.0/tags/c/changelog-is-dh_make-template.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/changelog-is-dh_make-template.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,10 +0,0 @@ -Tag: changelog-is-dh_make-template -Severity: error -Check: debian/changelog -Explanation: The changelog file has an instruction left by dh_make, which has - not been removed. Example: - . - - Initial release (Closes: #nnnn) <nnnn is the bug number of your ITP> - . - The "<... is the bug number ...>" part has not been removed from the - changelog. diff -Nru lintian-2.93.0/tags/c/changelog-is-symlink.desc lintian-2.89.0ubuntu1/tags/c/changelog-is-symlink.desc --- lintian-2.93.0/tags/c/changelog-is-symlink.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/changelog-is-symlink.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,11 @@ +Tag: changelog-is-symlink +Severity: warning +Check: nmu +Info: The file debian/changelog is a symlink instead of a regular + file. This is unnecessary and makes package checking and manipulation + more difficult. If the changelog should be available in the source + package under multiple names, make debian/changelog the real + file and the other names symlinks to it. + . + This problem may have prevented Lintian from performing other checks, + leading to undetected changelog errors. diff -Nru lintian-2.93.0/tags/c/changelog-is-symlink.tag lintian-2.89.0ubuntu1/tags/c/changelog-is-symlink.tag --- lintian-2.93.0/tags/c/changelog-is-symlink.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/changelog-is-symlink.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,11 +0,0 @@ -Tag: changelog-is-symlink -Severity: warning -Check: nmu -Explanation: The file debian/changelog is a symlink instead of a regular - file. This is unnecessary and makes package checking and manipulation - more difficult. If the changelog should be available in the source - package under multiple names, make debian/changelog the real - file and the other names symlinks to it. - . - This problem may have prevented Lintian from performing other checks, - leading to undetected changelog errors. diff -Nru lintian-2.93.0/tags/c/changelog-news-debian-mismatch.desc lintian-2.89.0ubuntu1/tags/c/changelog-news-debian-mismatch.desc --- lintian-2.93.0/tags/c/changelog-news-debian-mismatch.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/changelog-news-debian-mismatch.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: changelog-news-debian-mismatch +Severity: warning +Certainty: possible +Check: debian/changelog +Info: The latest entries in the Debian changelog file and NEWS.Debian file + are for the same version but the given field doesn't match. The + changelog information is canonical and the NEWS.Debian information is + ignored, but it may be confusing to users to have them be different. diff -Nru lintian-2.93.0/tags/c/changelog-news-debian-mismatch.tag lintian-2.89.0ubuntu1/tags/c/changelog-news-debian-mismatch.tag --- lintian-2.93.0/tags/c/changelog-news-debian-mismatch.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/changelog-news-debian-mismatch.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: changelog-news-debian-mismatch -Severity: warning -Check: debian/changelog -Explanation: The latest entries in the Debian changelog file and NEWS.Debian file - are for the same version but the given field doesn't match. The - changelog information is canonical and the NEWS.Debian information is - ignored, but it may be confusing to users to have them be different. diff -Nru lintian-2.93.0/tags/c/changelog-not-compressed-with-max-compression.desc lintian-2.89.0ubuntu1/tags/c/changelog-not-compressed-with-max-compression.desc --- lintian-2.93.0/tags/c/changelog-not-compressed-with-max-compression.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/changelog-not-compressed-with-max-compression.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: changelog-not-compressed-with-max-compression +Severity: warning +Check: debian/changelog +Info: Changelog files should be compressed using "gzip -9"; i.e., using + the maximum compression level via the -9 option to gzip. +Ref: policy 12.7 diff -Nru lintian-2.93.0/tags/c/changelog-not-compressed-with-max-compression.tag lintian-2.89.0ubuntu1/tags/c/changelog-not-compressed-with-max-compression.tag --- lintian-2.93.0/tags/c/changelog-not-compressed-with-max-compression.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/changelog-not-compressed-with-max-compression.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: changelog-not-compressed-with-max-compression -Severity: warning -Check: debian/changelog -Explanation: Changelog files should be compressed using "gzip -9"; i.e., using - the maximum compression level via the -9 option to gzip. -See-Also: policy 12.7 diff -Nru lintian-2.93.0/tags/c/changelog-references-temp-security-identifier.desc lintian-2.89.0ubuntu1/tags/c/changelog-references-temp-security-identifier.desc --- lintian-2.93.0/tags/c/changelog-references-temp-security-identifier.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/changelog-references-temp-security-identifier.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,15 @@ +Tag: changelog-references-temp-security-identifier +Severity: warning +Check: debian/changelog +Info: The changelog entry references a temporary security identifier, + like "TEMP-0000000-2FC21E". + . + The TEMP identifier will disappear in the future once a proper CVE + identifier has been assigned. Therefore it is useless as an + external reference. Even worse, the identifier is not stable and + may change even before a CVE is allocated. + . + If a CVE has been allocated, please use that instead. Otherwise, + please replace the TEMP identifier with a short description of the + issue. +Ref: #787929, #807892 diff -Nru lintian-2.93.0/tags/c/changelog-references-temp-security-identifier.tag lintian-2.89.0ubuntu1/tags/c/changelog-references-temp-security-identifier.tag --- lintian-2.93.0/tags/c/changelog-references-temp-security-identifier.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/changelog-references-temp-security-identifier.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,15 +0,0 @@ -Tag: changelog-references-temp-security-identifier -Severity: warning -Check: debian/changelog -Explanation: The changelog entry references a temporary security identifier, - like "TEMP-0000000-2FC21E". - . - The TEMP identifier will disappear in the future once a proper CVE - identifier has been assigned. Therefore it is useless as an - external reference. Even worse, the identifier is not stable and - may change even before a CVE is allocated. - . - If a CVE has been allocated, please use that instead. Otherwise, - please replace the TEMP identifier with a short description of the - issue. -See-Also: Bug#787929, Bug#807892 diff -Nru lintian-2.93.0/tags/c/checksum-count-mismatch-in-changes-file.desc lintian-2.89.0ubuntu1/tags/c/checksum-count-mismatch-in-changes-file.desc --- lintian-2.93.0/tags/c/checksum-count-mismatch-in-changes-file.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/checksum-count-mismatch-in-changes-file.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: checksum-count-mismatch-in-changes-file +Severity: error +Check: changes-file +Info: The number of checksums .changes file for the + specified algorithm does not match the number of files. +Ref: policy 5.6.21, policy 5.6.24 diff -Nru lintian-2.93.0/tags/c/checksum-count-mismatch-in-changes-file.tag lintian-2.89.0ubuntu1/tags/c/checksum-count-mismatch-in-changes-file.tag --- lintian-2.93.0/tags/c/checksum-count-mismatch-in-changes-file.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/checksum-count-mismatch-in-changes-file.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: checksum-count-mismatch-in-changes-file -Severity: error -Check: changes-file -Explanation: The number of checksums .changes file for the - specified algorithm does not match the number of files. -See-Also: policy 5.6.21, policy 5.6.24 diff -Nru lintian-2.93.0/tags/c/checksum-mismatch-in-changes-file.desc lintian-2.89.0ubuntu1/tags/c/checksum-mismatch-in-changes-file.desc --- lintian-2.93.0/tags/c/checksum-mismatch-in-changes-file.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/checksum-mismatch-in-changes-file.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: checksum-mismatch-in-changes-file +Severity: error +Check: changes-file +Info: The actual checksum does not match what's listed in the + .changes file. +Ref: policy 5.6.21, policy 5.6.24 diff -Nru lintian-2.93.0/tags/c/checksum-mismatch-in-changes-file.tag lintian-2.89.0ubuntu1/tags/c/checksum-mismatch-in-changes-file.tag --- lintian-2.93.0/tags/c/checksum-mismatch-in-changes-file.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/checksum-mismatch-in-changes-file.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: checksum-mismatch-in-changes-file -Severity: error -Check: changes-file -Explanation: The actual checksum does not match what's listed in the - .changes file. -See-Also: policy 5.6.21, policy 5.6.24 diff -Nru lintian-2.93.0/tags/c/classpath-contains-relative-path.desc lintian-2.89.0ubuntu1/tags/c/classpath-contains-relative-path.desc --- lintian-2.93.0/tags/c/classpath-contains-relative-path.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/classpath-contains-relative-path.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,16 @@ +Tag: classpath-contains-relative-path +Severity: warning +Certainty: possible +Check: languages/java +Info: The classpath listed in the jar file refers to a potential + missing jar file. This could be the remnants of a build-time + classpath that are not relevant for a JAR bundled in a Debian + package. + . + Alternatively, the classpath may be correct, but the package is + lacking a jar file or a symlink to it. + . + Note, Lintian assumes that all (relative) classpaths pointing to + /usr/share/java/ (but not subdirs thereof) are satisfied by + dependencies as long as there is at least one strong libX-java + dependency. diff -Nru lintian-2.93.0/tags/c/classpath-contains-relative-path.tag lintian-2.89.0ubuntu1/tags/c/classpath-contains-relative-path.tag --- lintian-2.93.0/tags/c/classpath-contains-relative-path.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/classpath-contains-relative-path.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,15 +0,0 @@ -Tag: classpath-contains-relative-path -Severity: warning -Check: languages/java -Explanation: The classpath listed in the jar file refers to a potential - missing jar file. This could be the remnants of a build-time - classpath that are not relevant for a JAR bundled in a Debian - package. - . - Alternatively, the classpath may be correct, but the package is - lacking a jar file or a symlink to it. - . - Note, Lintian assumes that all (relative) classpaths pointing to - /usr/share/java/ (but not subdirs thereof) are satisfied by - dependencies as long as there is at least one strong libX-java - dependency. diff -Nru lintian-2.93.0/tags/c/codeless-jar.desc lintian-2.89.0ubuntu1/tags/c/codeless-jar.desc --- lintian-2.93.0/tags/c/codeless-jar.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/codeless-jar.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,5 @@ +Tag: codeless-jar +Severity: warning +Check: languages/java +Info: The jar file contains a manifest but no code. This probably indicates + that something went wrong at build-time. diff -Nru lintian-2.93.0/tags/c/codeless-jar.tag lintian-2.89.0ubuntu1/tags/c/codeless-jar.tag --- lintian-2.93.0/tags/c/codeless-jar.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/codeless-jar.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,5 +0,0 @@ -Tag: codeless-jar -Severity: warning -Check: languages/java -Explanation: The jar file contains a manifest but no code. This probably indicates - that something went wrong at build-time. diff -Nru lintian-2.93.0/tags/c/co-maintained-package-with-no-vcs-fields.desc lintian-2.89.0ubuntu1/tags/c/co-maintained-package-with-no-vcs-fields.desc --- lintian-2.93.0/tags/c/co-maintained-package-with-no-vcs-fields.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/co-maintained-package-with-no-vcs-fields.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,11 @@ +Tag: co-maintained-package-with-no-vcs-fields +Severity: pedantic +Certainty: possible +Check: fields/vcs +Info: Based on the content of the maintainer and uploader fields this + package is co-maintained but there are no Vcs-* fields. + . + It is recommended that shared maintenance of packages are co-ordinated + via a revision control system. +Renamed-From: + co-maintained-package-with-no-vcs-headers diff -Nru lintian-2.93.0/tags/c/co-maintained-package-with-no-vcs-fields.tag lintian-2.89.0ubuntu1/tags/c/co-maintained-package-with-no-vcs-fields.tag --- lintian-2.93.0/tags/c/co-maintained-package-with-no-vcs-fields.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/co-maintained-package-with-no-vcs-fields.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,10 +0,0 @@ -Tag: co-maintained-package-with-no-vcs-fields -Severity: pedantic -Check: fields/vcs -Explanation: Based on the content of the maintainer and uploader fields this - package is co-maintained but there are no Vcs-* fields. - . - It is recommended that shared maintenance of packages are co-ordinated - via a revision control system. -Renamed-From: - co-maintained-package-with-no-vcs-headers diff -Nru lintian-2.93.0/tags/c/command-in-menu-file-and-desktop-file.desc lintian-2.89.0ubuntu1/tags/c/command-in-menu-file-and-desktop-file.desc --- lintian-2.93.0/tags/c/command-in-menu-file-and-desktop-file.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/command-in-menu-file-and-desktop-file.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: command-in-menu-file-and-desktop-file +Severity: warning +Certainty: possible +Check: menu-format +Info: The command is listed both in a menu file and a desktop file + . + Per the tech-ctte decision on #741573, this is now prohibited. + . + Please remove the menu file from the package. +Ref: policy 9.6, https://lists.debian.org/debian-devel-announce/2015/09/msg00000.html diff -Nru lintian-2.93.0/tags/c/command-in-menu-file-and-desktop-file.tag lintian-2.89.0ubuntu1/tags/c/command-in-menu-file-and-desktop-file.tag --- lintian-2.93.0/tags/c/command-in-menu-file-and-desktop-file.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/command-in-menu-file-and-desktop-file.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: command-in-menu-file-and-desktop-file -Severity: warning -Check: menu-format -Explanation: The command is listed both in a menu file and a desktop file - . - Per the tech-ctte decision on Bug#741573, this is now prohibited. - . - Please remove the menu file from the package. -See-Also: policy 9.6, https://lists.debian.org/debian-devel-announce/2015/09/msg00000.html diff -Nru lintian-2.93.0/tags/c/command-with-path-in-maintainer-script.desc lintian-2.89.0ubuntu1/tags/c/command-with-path-in-maintainer-script.desc --- lintian-2.93.0/tags/c/command-with-path-in-maintainer-script.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/command-with-path-in-maintainer-script.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,18 @@ +Tag: command-with-path-in-maintainer-script +Severity: warning +Check: scripts +Info: The indicated program run in a maintainer script has a prepended + path. Programs called from maintainer scripts normally should not have a + path prepended. dpkg ensures that the PATH is set to a reasonable value, + and prepending a path may prevent the local administrator from using a + replacement version of a command for some local reason. + . + If the path is used to test a program for existence, please use if + which $program > /dev/null; then …. + . + If you intend to override this tag, please make sure that you are in + control of the installation path of the according program and that + you won't forget to change this maintainer script, too, if you ever + move that program around. +Ref: policy 6.1, devref 6.4, #769845, #807695, + https://lists.debian.org/debian-devel/2014/11/msg00044.html diff -Nru lintian-2.93.0/tags/c/command-with-path-in-maintainer-script.tag lintian-2.89.0ubuntu1/tags/c/command-with-path-in-maintainer-script.tag --- lintian-2.93.0/tags/c/command-with-path-in-maintainer-script.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/command-with-path-in-maintainer-script.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,18 +0,0 @@ -Tag: command-with-path-in-maintainer-script -Severity: warning -Check: scripts -Explanation: The indicated program run in a maintainer script has a prepended - path. Programs called from maintainer scripts normally should not have a - path prepended. dpkg ensures that the PATH is set to a reasonable value, - and prepending a path may prevent the local administrator from using a - replacement version of a command for some local reason. - . - If the path is used to test a program for existence, please use if - which $program > /dev/null; then …. - . - If you intend to override this tag, please make sure that you are in - control of the installation path of the according program and that - you won't forget to change this maintainer script, too, if you ever - move that program around. -See-Also: policy 6.1, devref 6.4, Bug#769845, Bug#807695, - https://lists.debian.org/debian-devel/2014/11/msg00044.html diff -Nru lintian-2.93.0/tags/c/comma-separated-files-in-dep5-copyright.desc lintian-2.89.0ubuntu1/tags/c/comma-separated-files-in-dep5-copyright.desc --- lintian-2.93.0/tags/c/comma-separated-files-in-dep5-copyright.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/comma-separated-files-in-dep5-copyright.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: comma-separated-files-in-dep5-copyright +Severity: warning +Certainty: possible +Check: debian/copyright/dep5 +Ref: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ +Info: A list of files in the machine-readable copyright format appears to be + separated by commas. The file list should be whitespace separated instead. + . + Please note this tag is only emitted once per checked copyright file. diff -Nru lintian-2.93.0/tags/c/comma-separated-files-in-dep5-copyright.tag lintian-2.89.0ubuntu1/tags/c/comma-separated-files-in-dep5-copyright.tag --- lintian-2.93.0/tags/c/comma-separated-files-in-dep5-copyright.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/comma-separated-files-in-dep5-copyright.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: comma-separated-files-in-dep5-copyright -Severity: warning -Check: debian/copyright/dep5 -See-Also: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ -Explanation: A list of files in the machine-readable copyright format appears to be - separated by commas. The file list should be whitespace separated instead. - . - Please note this tag is only emitted once per checked copyright file. diff -Nru lintian-2.93.0/tags/c/composer-package-without-pkg-php-tools-builddep.desc lintian-2.89.0ubuntu1/tags/c/composer-package-without-pkg-php-tools-builddep.desc --- lintian-2.93.0/tags/c/composer-package-without-pkg-php-tools-builddep.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/composer-package-without-pkg-php-tools-builddep.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: composer-package-without-pkg-php-tools-builddep +Severity: info +Certainty: possible +Check: languages/php/pear +Info: The package contains a composer.json file but doesn't build-depend on + pkg-php-tools. + . + pkg-php-tools is the recommended tool for building PHP Composer packages. For + more information, install it and read the included README.Composer. diff -Nru lintian-2.93.0/tags/c/composer-package-without-pkg-php-tools-builddep.tag lintian-2.89.0ubuntu1/tags/c/composer-package-without-pkg-php-tools-builddep.tag --- lintian-2.93.0/tags/c/composer-package-without-pkg-php-tools-builddep.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/composer-package-without-pkg-php-tools-builddep.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: composer-package-without-pkg-php-tools-builddep -Severity: info -Check: languages/php/pear -Explanation: The package contains a composer.json file but doesn't build-depend on - pkg-php-tools. - . - pkg-php-tools is the recommended tool for building PHP Composer packages. For - more information, install it and read the included README.Composer. diff -Nru lintian-2.93.0/tags/c/compressed-documentation.desc lintian-2.89.0ubuntu1/tags/c/compressed-documentation.desc --- lintian-2.93.0/tags/c/compressed-documentation.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/compressed-documentation.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,11 @@ +Tag: compressed-documentation +Severity: warning +Certainty: possible +Check: documentation +Renamed-From: file-should-not-be-compressed +Info: The following file should not be compressed. + . + This file should be excluded from compression during build time. + If using debhelper (<< 9.20140227), you may need to use the -X + option to dh_compress. Newer versions of debhelper handle this + correctly by default. diff -Nru lintian-2.93.0/tags/c/compressed-documentation.tag lintian-2.89.0ubuntu1/tags/c/compressed-documentation.tag --- lintian-2.93.0/tags/c/compressed-documentation.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/compressed-documentation.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,10 +0,0 @@ -Tag: compressed-documentation -Severity: warning -Check: documentation -Renamed-From: file-should-not-be-compressed -Explanation: The following file should not be compressed. - . - This file should be excluded from compression during build time. - If using debhelper (<< 9.20140227), you may need to use the -X - option to dh_compress. Newer versions of debhelper handle this - correctly by default. diff -Nru lintian-2.93.0/tags/c/compressed-duplicate.desc lintian-2.89.0ubuntu1/tags/c/compressed-duplicate.desc --- lintian-2.93.0/tags/c/compressed-duplicate.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/compressed-duplicate.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: compressed-duplicate +Severity: info +Certainty: possible +Check: files/compressed +Renamed-From: duplicated-compressed-file +Info: The given, apparently compressed, file is shipped in the package + in addition to another file with the same name without the + compression-method extension. Normally this indicates a mistake in the + installation process of the package. diff -Nru lintian-2.93.0/tags/c/compressed-duplicate.tag lintian-2.89.0ubuntu1/tags/c/compressed-duplicate.tag --- lintian-2.93.0/tags/c/compressed-duplicate.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/compressed-duplicate.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: compressed-duplicate -Severity: info -Check: files/compressed -Renamed-From: duplicated-compressed-file -Explanation: The given, apparently compressed, file is shipped in the package - in addition to another file with the same name without the - compression-method extension. Normally this indicates a mistake in the - installation process of the package. diff -Nru lintian-2.93.0/tags/c/compressed-symlink-with-wrong-ext.desc lintian-2.89.0ubuntu1/tags/c/compressed-symlink-with-wrong-ext.desc --- lintian-2.93.0/tags/c/compressed-symlink-with-wrong-ext.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/compressed-symlink-with-wrong-ext.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: compressed-symlink-with-wrong-ext +Severity: error +Check: files/symbolic-links +Info: The package installs a symbolic link pointing to a compressed file, + but the symbolic link does not use the same file extension than the + referenced file. In most cases, this can produce troubles when the + user or a program tries to access the file through the link. +Ref: policy 10.5 diff -Nru lintian-2.93.0/tags/c/compressed-symlink-with-wrong-ext.tag lintian-2.89.0ubuntu1/tags/c/compressed-symlink-with-wrong-ext.tag --- lintian-2.93.0/tags/c/compressed-symlink-with-wrong-ext.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/compressed-symlink-with-wrong-ext.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: compressed-symlink-with-wrong-ext -Severity: error -Check: files/symbolic-links -Explanation: The package installs a symbolic link pointing to a compressed file, - but the symbolic link does not use the same file extension than the - referenced file. In most cases, this can produce troubles when the - user or a program tries to access the file through the link. -See-Also: policy 10.5 diff -Nru lintian-2.93.0/tags/c/concatenated-upstream-signatures.desc lintian-2.89.0ubuntu1/tags/c/concatenated-upstream-signatures.desc --- lintian-2.93.0/tags/c/concatenated-upstream-signatures.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/concatenated-upstream-signatures.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: concatenated-upstream-signatures +Severity: warning +Check: upstream-signature +Info: The packaging includes a detached upstream signature file that contains + multiple concatenated signature blocks. That is likely an error. + . + Please include only one signature block in the indicated signature file. diff -Nru lintian-2.93.0/tags/c/concatenated-upstream-signatures.tag lintian-2.89.0ubuntu1/tags/c/concatenated-upstream-signatures.tag --- lintian-2.93.0/tags/c/concatenated-upstream-signatures.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/concatenated-upstream-signatures.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: concatenated-upstream-signatures -Severity: warning -Check: upstream-signature -Explanation: The packaging includes a detached upstream signature file that contains - multiple concatenated signature blocks. That is likely an error. - . - Please include only one signature block in the indicated signature file. diff -Nru lintian-2.93.0/tags/c/conffile-has-bad-file-type.desc lintian-2.89.0ubuntu1/tags/c/conffile-has-bad-file-type.desc --- lintian-2.93.0/tags/c/conffile-has-bad-file-type.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/conffile-has-bad-file-type.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: conffile-has-bad-file-type +Severity: error +Check: conffiles +Ref: #690051, #690910 +Info: The conffiles lists this path, which is not a file. This will + almost certainly not work. + . + Note that dpkg does not support symlinks being conffiles. diff -Nru lintian-2.93.0/tags/c/conffile-has-bad-file-type.tag lintian-2.89.0ubuntu1/tags/c/conffile-has-bad-file-type.tag --- lintian-2.93.0/tags/c/conffile-has-bad-file-type.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/conffile-has-bad-file-type.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: conffile-has-bad-file-type -Severity: error -Check: conffiles -See-Also: Bug#690051, Bug#690910 -Explanation: The conffiles lists this path, which is not a file. This will - almost certainly not work. - . - Note that dpkg does not support symlinks being conffiles. diff -Nru lintian-2.93.0/tags/c/conffile-is-not-in-package.desc lintian-2.89.0ubuntu1/tags/c/conffile-is-not-in-package.desc --- lintian-2.93.0/tags/c/conffile-is-not-in-package.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/conffile-is-not-in-package.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,11 @@ +Tag: conffile-is-not-in-package +Severity: error +Check: conffiles +Info: The conffiles control file lists this path, but the path does + not appear to exist in the package. Lintian may also emit this tag + when the file exists, but the canonical name is used in the + "conffiles" control file (e.g. if a parent segment are symlinks). + . + Note that dpkg and Lintian strips all whitespace from the right hand + side of each line. Thus it is not possible for a file ending with + trailing whitespace to be marked as a conffile. diff -Nru lintian-2.93.0/tags/c/conffile-is-not-in-package.tag lintian-2.89.0ubuntu1/tags/c/conffile-is-not-in-package.tag --- lintian-2.93.0/tags/c/conffile-is-not-in-package.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/conffile-is-not-in-package.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,11 +0,0 @@ -Tag: conffile-is-not-in-package -Severity: error -Check: conffiles -Explanation: The conffiles control file lists this path, but the path does - not appear to exist in the package. Lintian may also emit this tag - when the file exists, but the canonical name is used in the - "conffiles" control file (e.g. if a parent segment are symlinks). - . - Note that dpkg and Lintian strips all whitespace from the right hand - side of each line. Thus it is not possible for a file ending with - trailing whitespace to be marked as a conffile. diff -Nru lintian-2.93.0/tags/c/config-does-not-load-confmodule.desc lintian-2.89.0ubuntu1/tags/c/config-does-not-load-confmodule.desc --- lintian-2.93.0/tags/c/config-does-not-load-confmodule.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/config-does-not-load-confmodule.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,4 @@ +Tag: config-does-not-load-confmodule +Severity: warning +Check: debian/debconf +Info: The config script must load one of the debconf libraries. diff -Nru lintian-2.93.0/tags/c/config-does-not-load-confmodule.tag lintian-2.89.0ubuntu1/tags/c/config-does-not-load-confmodule.tag --- lintian-2.93.0/tags/c/config-does-not-load-confmodule.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/config-does-not-load-confmodule.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,4 +0,0 @@ -Tag: config-does-not-load-confmodule -Severity: warning -Check: debian/debconf -Explanation: The config script must load one of the debconf libraries. diff -Nru lintian-2.93.0/tags/c/config-file-reserved.desc lintian-2.89.0ubuntu1/tags/c/config-file-reserved.desc --- lintian-2.93.0/tags/c/config-file-reserved.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/config-file-reserved.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,5 @@ +Tag: config-file-reserved +Severity: error +Check: files/pam +Info: This file is reserved by a specific package. Please email the + maintainer of the package in question if you have questions. diff -Nru lintian-2.93.0/tags/c/config-file-reserved.tag lintian-2.89.0ubuntu1/tags/c/config-file-reserved.tag --- lintian-2.93.0/tags/c/config-file-reserved.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/config-file-reserved.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,5 +0,0 @@ -Tag: config-file-reserved -Severity: error -Check: files/pam -Explanation: This file is reserved by a specific package. Please email the - maintainer of the package in question if you have questions. diff -Nru lintian-2.93.0/tags/c/configure-generated-file-in-source.desc lintian-2.89.0ubuntu1/tags/c/configure-generated-file-in-source.desc --- lintian-2.93.0/tags/c/configure-generated-file-in-source.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/configure-generated-file-in-source.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,18 @@ +Tag: configure-generated-file-in-source +Severity: warning +Certainty: possible +Check: cruft +Info: Leaving config.cache/status causes autobuilders problems. + config.cache and config.status are produced by GNU autoconf's configure + scripts. If they are left in the source package, autobuilders may pick + up settings for the wrong architecture. + . + The clean rule in debian/rules should remove this file. This + should ideally be done by fixing the upstream build system to do it when + you run the appropriate cleaning command (and don't forget to forward the + fix to the upstream authors so it doesn't happen in the next release). If + that is already implemented, then make sure you are indeed cleaning it in + the clean rule. If all else fails, a simple rm -f should work. + . + Note that Lintian cannot reliably detect the removal in the clean rule, + so once you fix this, please ignore or override this warning. diff -Nru lintian-2.93.0/tags/c/configure-generated-file-in-source.tag lintian-2.89.0ubuntu1/tags/c/configure-generated-file-in-source.tag --- lintian-2.93.0/tags/c/configure-generated-file-in-source.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/configure-generated-file-in-source.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,17 +0,0 @@ -Tag: configure-generated-file-in-source -Severity: warning -Check: cruft -Explanation: Leaving config.cache/status causes autobuilders problems. - config.cache and config.status are produced by GNU autoconf's configure - scripts. If they are left in the source package, autobuilders may pick - up settings for the wrong architecture. - . - The clean rule in debian/rules should remove this file. This - should ideally be done by fixing the upstream build system to do it when - you run the appropriate cleaning command (and don't forget to forward the - fix to the upstream authors so it doesn't happen in the next release). If - that is already implemented, then make sure you are indeed cleaning it in - the clean rule. If all else fails, a simple rm -f should work. - . - Note that Lintian cannot reliably detect the removal in the clean rule, - so once you fix this, please ignore or override this warning. diff -Nru lintian-2.93.0/tags/c/conflicting-negation-in-source-relation.desc lintian-2.89.0ubuntu1/tags/c/conflicting-negation-in-source-relation.desc --- lintian-2.93.0/tags/c/conflicting-negation-in-source-relation.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/conflicting-negation-in-source-relation.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: conflicting-negation-in-source-relation +Severity: error +Check: fields/package-relations +Ref: policy 7.1 +Info: The architecture string in this source relation has some + negated architectures (prepended by !) and others that are not + negated. This is not permitted by Policy. Either all architectures must + be negated or none of them may be. diff -Nru lintian-2.93.0/tags/c/conflicting-negation-in-source-relation.tag lintian-2.89.0ubuntu1/tags/c/conflicting-negation-in-source-relation.tag --- lintian-2.93.0/tags/c/conflicting-negation-in-source-relation.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/conflicting-negation-in-source-relation.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: conflicting-negation-in-source-relation -Severity: error -Check: fields/package-relations -See-Also: policy 7.1 -Explanation: The architecture string in this source relation has some - negated architectures (prepended by !) and others that are not - negated. This is not permitted by Policy. Either all architectures must - be negated or none of them may be. diff -Nru lintian-2.93.0/tags/c/conflicts-with-dependency.desc lintian-2.89.0ubuntu1/tags/c/conflicts-with-dependency.desc --- lintian-2.93.0/tags/c/conflicts-with-dependency.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/conflicts-with-dependency.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: conflicts-with-dependency +Severity: error +Check: fields/package-relations +Ref: policy 7.4 +Info: The package seems to conflict with one of its dependencies, + recommendations, or suggestions by listing it in Conflicts or Breaks. diff -Nru lintian-2.93.0/tags/c/conflicts-with-dependency.tag lintian-2.89.0ubuntu1/tags/c/conflicts-with-dependency.tag --- lintian-2.93.0/tags/c/conflicts-with-dependency.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/conflicts-with-dependency.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: conflicts-with-dependency -Severity: error -Check: fields/package-relations -See-Also: policy 7.4 -Explanation: The package seems to conflict with one of its dependencies, - recommendations, or suggestions by listing it in Conflicts or Breaks. diff -Nru lintian-2.93.0/tags/c/conflicts-with-version.desc lintian-2.89.0ubuntu1/tags/c/conflicts-with-version.desc --- lintian-2.93.0/tags/c/conflicts-with-version.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/conflicts-with-version.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,12 @@ +Tag: conflicts-with-version +Severity: info +Certainty: wild-guess +Check: fields/package-relations +Ref: policy 7.4 +Info: An earlier-than version clause is normally an indication that Breaks + should be used instead of Conflicts. Breaks is a weaker requirement that + provides the package manager more leeway to find a valid upgrade path. + Conflicts should only be used if two packages can never be unpacked at + the same time, or for some situations involving virtual packages (where a + version clause is not appropriate). In particular, when moving files + between packages, use Breaks plus Replaces, not Conflicts plus Replaces. diff -Nru lintian-2.93.0/tags/c/conflicts-with-version.tag lintian-2.89.0ubuntu1/tags/c/conflicts-with-version.tag --- lintian-2.93.0/tags/c/conflicts-with-version.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/conflicts-with-version.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,11 +0,0 @@ -Tag: conflicts-with-version -Severity: info -Check: fields/package-relations -See-Also: policy 7.4 -Explanation: An earlier-than version clause is normally an indication that Breaks - should be used instead of Conflicts. Breaks is a weaker requirement that - provides the package manager more leeway to find a valid upgrade path. - Conflicts should only be used if two packages can never be unpacked at - the same time, or for some situations involving virtual packages (where a - version clause is not appropriate). In particular, when moving files - between packages, use Breaks plus Replaces, not Conflicts plus Replaces. diff -Nru lintian-2.93.0/tags/c/control-file-contains-dh_make-vcs-comment.desc lintian-2.89.0ubuntu1/tags/c/control-file-contains-dh_make-vcs-comment.desc --- lintian-2.93.0/tags/c/control-file-contains-dh_make-vcs-comment.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/control-file-contains-dh_make-vcs-comment.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: control-file-contains-dh_make-vcs-comment +Severity: warning +Check: debian/control +Info: The control file contains commented-out VCS-* lines, most + probably a result of dh_make. These URLs should either be valid and + uncommented, or removed. diff -Nru lintian-2.93.0/tags/c/control-file-contains-dh_make-vcs-comment.tag lintian-2.89.0ubuntu1/tags/c/control-file-contains-dh_make-vcs-comment.tag --- lintian-2.93.0/tags/c/control-file-contains-dh_make-vcs-comment.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/control-file-contains-dh_make-vcs-comment.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: control-file-contains-dh_make-vcs-comment -Severity: warning -Check: debian/control -Explanation: The control file contains commented-out VCS-* lines, most - probably a result of dh_make. These URLs should either be valid and - uncommented, or removed. diff -Nru lintian-2.93.0/tags/c/control-file-has-bad-owner.desc lintian-2.89.0ubuntu1/tags/c/control-file-has-bad-owner.desc --- lintian-2.93.0/tags/c/control-file-has-bad-owner.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/control-file-has-bad-owner.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,5 @@ +Tag: control-file-has-bad-owner +Severity: error +Check: control-files +Ref: policy 10.9 +Info: All control files should be owned by root/root. diff -Nru lintian-2.93.0/tags/c/control-file-has-bad-owner.tag lintian-2.89.0ubuntu1/tags/c/control-file-has-bad-owner.tag --- lintian-2.93.0/tags/c/control-file-has-bad-owner.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/control-file-has-bad-owner.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,5 +0,0 @@ -Tag: control-file-has-bad-owner -Severity: error -Check: control-files -See-Also: policy 10.9 -Explanation: All control files should be owned by root/root. diff -Nru lintian-2.93.0/tags/c/control-file-has-bad-permissions.desc lintian-2.89.0ubuntu1/tags/c/control-file-has-bad-permissions.desc --- lintian-2.93.0/tags/c/control-file-has-bad-permissions.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/control-file-has-bad-permissions.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: control-file-has-bad-permissions +Severity: error +Check: control-files +Ref: policy 10.9 +Info: The config, postinst, postrm, + preinst, and prerm control files should use mode 0755; + all other control files should use 0644. diff -Nru lintian-2.93.0/tags/c/control-file-has-bad-permissions.tag lintian-2.89.0ubuntu1/tags/c/control-file-has-bad-permissions.tag --- lintian-2.93.0/tags/c/control-file-has-bad-permissions.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/control-file-has-bad-permissions.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: control-file-has-bad-permissions -Severity: error -Check: control-files -See-Also: policy 10.9 -Explanation: The config, postinst, postrm, - preinst, and prerm control files should use mode 0755; - all other control files should use 0644. diff -Nru lintian-2.93.0/tags/c/control-file-is-empty.desc lintian-2.89.0ubuntu1/tags/c/control-file-is-empty.desc --- lintian-2.93.0/tags/c/control-file-is-empty.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/control-file-is-empty.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: control-file-is-empty +Severity: warning +Certainty: possible +Check: control-files +Info: The package contains an empty control file, which is most probably + an error. diff -Nru lintian-2.93.0/tags/c/control-file-is-empty.tag lintian-2.89.0ubuntu1/tags/c/control-file-is-empty.tag --- lintian-2.93.0/tags/c/control-file-is-empty.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/control-file-is-empty.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,5 +0,0 @@ -Tag: control-file-is-empty -Severity: warning -Check: control-files -Explanation: The package contains an empty control file, which is most probably - an error. diff -Nru lintian-2.93.0/tags/c/control-file-is-not-a-file.desc lintian-2.89.0ubuntu1/tags/c/control-file-is-not-a-file.desc --- lintian-2.93.0/tags/c/control-file-is-not-a-file.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/control-file-is-not-a-file.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,4 @@ +Tag: control-file-is-not-a-file +Severity: error +Check: control-files +Info: The package contains a control file that is not a regular file. diff -Nru lintian-2.93.0/tags/c/control-file-is-not-a-file.tag lintian-2.89.0ubuntu1/tags/c/control-file-is-not-a-file.tag --- lintian-2.93.0/tags/c/control-file-is-not-a-file.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/control-file-is-not-a-file.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,4 +0,0 @@ -Tag: control-file-is-not-a-file -Severity: error -Check: control-files -Explanation: The package contains a control file that is not a regular file. diff -Nru lintian-2.93.0/tags/c/control-interpreter-in-usr-local.desc lintian-2.89.0ubuntu1/tags/c/control-interpreter-in-usr-local.desc --- lintian-2.93.0/tags/c/control-interpreter-in-usr-local.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/control-interpreter-in-usr-local.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: control-interpreter-in-usr-local +Severity: error +Check: scripts +Info: A control script for this package references an interpreter in a + directory in /usr/local. Control scripts must use interpreters + provided by Debian packages, and Debian packages do not install anything + in /usr/local. diff -Nru lintian-2.93.0/tags/c/control-interpreter-in-usr-local.tag lintian-2.89.0ubuntu1/tags/c/control-interpreter-in-usr-local.tag --- lintian-2.93.0/tags/c/control-interpreter-in-usr-local.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/control-interpreter-in-usr-local.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: control-interpreter-in-usr-local -Severity: error -Check: scripts -Explanation: A control script for this package references an interpreter in a - directory in /usr/local. Control scripts must use interpreters - provided by Debian packages, and Debian packages do not install anything - in /usr/local. diff -Nru lintian-2.93.0/tags/c/control-interpreter-without-depends.desc lintian-2.89.0ubuntu1/tags/c/control-interpreter-without-depends.desc --- lintian-2.93.0/tags/c/control-interpreter-without-depends.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/control-interpreter-without-depends.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: control-interpreter-without-depends +Severity: error +Certainty: possible +Check: scripts +Info: The package contains a maintainer script that uses an unusual and + non-essential interpreter but does not declare a dependency on the + package that provides this interpreter. +Ref: policy 7.2 diff -Nru lintian-2.93.0/tags/c/control-interpreter-without-depends.tag lintian-2.89.0ubuntu1/tags/c/control-interpreter-without-depends.tag --- lintian-2.93.0/tags/c/control-interpreter-without-depends.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/control-interpreter-without-depends.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: control-interpreter-without-depends -Severity: error -Check: scripts -Explanation: The package contains a maintainer script that uses an unusual and - non-essential interpreter but does not declare a dependency on the - package that provides this interpreter. -See-Also: policy 7.2 diff -Nru lintian-2.93.0/tags/c/control-tarball-compression-format.desc lintian-2.89.0ubuntu1/tags/c/control-tarball-compression-format.desc --- lintian-2.93.0/tags/c/control-tarball-compression-format.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/control-tarball-compression-format.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,4 @@ +Tag: control-tarball-compression-format +Severity: classification +Check: deb-format +Info: This is the compressor format used for the control.tar tarball. diff -Nru lintian-2.93.0/tags/c/control-tarball-compression-format.tag lintian-2.89.0ubuntu1/tags/c/control-tarball-compression-format.tag --- lintian-2.93.0/tags/c/control-tarball-compression-format.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/control-tarball-compression-format.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,4 +0,0 @@ -Tag: control-tarball-compression-format -Severity: classification -Check: deb-format -Explanation: This is the compressor format used for the control.tar tarball. diff -Nru lintian-2.93.0/tags/c/copyright-contains-automatically-extracted-boilerplate.desc lintian-2.89.0ubuntu1/tags/c/copyright-contains-automatically-extracted-boilerplate.desc --- lintian-2.93.0/tags/c/copyright-contains-automatically-extracted-boilerplate.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/copyright-contains-automatically-extracted-boilerplate.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: copyright-contains-automatically-extracted-boilerplate +Severity: warning +Check: debian/copyright +Ref: policy 12.5 +Info: The string "This copyright info was automatically extracted" + appears in the copyright file, which indicates that you either didn't + check the whole source to find additional copyright/license, or that + you didn't remove that paragraph after having done so. diff -Nru lintian-2.93.0/tags/c/copyright-contains-automatically-extracted-boilerplate.tag lintian-2.89.0ubuntu1/tags/c/copyright-contains-automatically-extracted-boilerplate.tag --- lintian-2.93.0/tags/c/copyright-contains-automatically-extracted-boilerplate.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/copyright-contains-automatically-extracted-boilerplate.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: copyright-contains-automatically-extracted-boilerplate -Severity: warning -Check: debian/copyright -See-Also: policy 12.5 -Explanation: The string "This copyright info was automatically extracted" - appears in the copyright file, which indicates that you either didn't - check the whole source to find additional copyright/license, or that - you didn't remove that paragraph after having done so. diff -Nru lintian-2.93.0/tags/c/copyright-contains-dh_make-todo-boilerplate.desc lintian-2.89.0ubuntu1/tags/c/copyright-contains-dh_make-todo-boilerplate.desc --- lintian-2.93.0/tags/c/copyright-contains-dh_make-todo-boilerplate.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/copyright-contains-dh_make-todo-boilerplate.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: copyright-contains-dh_make-todo-boilerplate +Severity: error +Certainty: possible +Check: debian/copyright +Ref: policy 12.5 +Info: The string "Please also look if..." appears in the copyright + file, which indicates that you either didn't check the whole source + to find additional copyright/license, or that you didn't remove that + paragraph after having done so. diff -Nru lintian-2.93.0/tags/c/copyright-contains-dh_make-todo-boilerplate.tag lintian-2.89.0ubuntu1/tags/c/copyright-contains-dh_make-todo-boilerplate.tag --- lintian-2.93.0/tags/c/copyright-contains-dh_make-todo-boilerplate.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/copyright-contains-dh_make-todo-boilerplate.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: copyright-contains-dh_make-todo-boilerplate -Severity: error -Check: debian/copyright -See-Also: policy 12.5 -Explanation: The string "Please also look if..." appears in the copyright - file, which indicates that you either didn't check the whole source - to find additional copyright/license, or that you didn't remove that - paragraph after having done so. diff -Nru lintian-2.93.0/tags/c/copyright-does-not-refer-to-common-license-file.desc lintian-2.89.0ubuntu1/tags/c/copyright-does-not-refer-to-common-license-file.desc --- lintian-2.93.0/tags/c/copyright-does-not-refer-to-common-license-file.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/copyright-does-not-refer-to-common-license-file.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: copyright-does-not-refer-to-common-license-file +Severity: warning +Check: debian/copyright +Info: If your package uses any one of the licenses in + /usr/share/common-licenses, the copyright file should refer to + files therein. +Ref: policy 12.5 diff -Nru lintian-2.93.0/tags/c/copyright-does-not-refer-to-common-license-file.tag lintian-2.89.0ubuntu1/tags/c/copyright-does-not-refer-to-common-license-file.tag --- lintian-2.93.0/tags/c/copyright-does-not-refer-to-common-license-file.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/copyright-does-not-refer-to-common-license-file.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: copyright-does-not-refer-to-common-license-file -Severity: warning -Check: debian/copyright -Explanation: If your package uses any one of the licenses in - /usr/share/common-licenses, the copyright file should refer to - files therein. -See-Also: policy 12.5 diff -Nru lintian-2.93.0/tags/c/copyright-excludes-files-in-native-package.desc lintian-2.89.0ubuntu1/tags/c/copyright-excludes-files-in-native-package.desc --- lintian-2.93.0/tags/c/copyright-excludes-files-in-native-package.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/copyright-excludes-files-in-native-package.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: copyright-excludes-files-in-native-package +Severity: error +Check: debian/copyright/dep5 +Info: The Debian copyright notes excluded files with the Excluded-Files field, + but the package is native. + . + Native packages cannot be repackaged. Please remove the field from + debian/copyright or make the package non-native. diff -Nru lintian-2.93.0/tags/c/copyright-excludes-files-in-native-package.tag lintian-2.89.0ubuntu1/tags/c/copyright-excludes-files-in-native-package.tag --- lintian-2.93.0/tags/c/copyright-excludes-files-in-native-package.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/copyright-excludes-files-in-native-package.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: copyright-excludes-files-in-native-package -Severity: error -Check: debian/copyright/dep5 -Explanation: The Debian copyright notes excluded files with the Excluded-Files field, - but the package is native. - . - Native packages cannot be repackaged. Please remove the field from - debian/copyright or make the package non-native. diff -Nru lintian-2.93.0/tags/c/copyright-file-compressed.desc lintian-2.89.0ubuntu1/tags/c/copyright-file-compressed.desc --- lintian-2.93.0/tags/c/copyright-file-compressed.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/copyright-file-compressed.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: copyright-file-compressed +Severity: error +Check: debian/copyright +Info: The copyright file /usr/share/doc/pkg/copyright must not be + compressed. +Ref: policy 12.5 diff -Nru lintian-2.93.0/tags/c/copyright-file-compressed.tag lintian-2.89.0ubuntu1/tags/c/copyright-file-compressed.tag --- lintian-2.93.0/tags/c/copyright-file-compressed.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/copyright-file-compressed.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: copyright-file-compressed -Severity: error -Check: debian/copyright -Explanation: The copyright file /usr/share/doc/*pkg*/copyright must not be - compressed. -See-Also: policy 12.5 diff -Nru lintian-2.93.0/tags/c/copyright-file-contains-full-apache-2-license.desc lintian-2.89.0ubuntu1/tags/c/copyright-file-contains-full-apache-2-license.desc --- lintian-2.93.0/tags/c/copyright-file-contains-full-apache-2-license.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/copyright-file-contains-full-apache-2-license.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: copyright-file-contains-full-apache-2-license +Severity: error +Check: debian/copyright +Info: The copyright file /usr/share/doc/pkg/copyright contains the + complete text of the Apache 2.0 license. It should refer to the file + /usr/share/common-licenses/Apache-2.0 instead. +Ref: policy 12.5 diff -Nru lintian-2.93.0/tags/c/copyright-file-contains-full-apache-2-license.tag lintian-2.89.0ubuntu1/tags/c/copyright-file-contains-full-apache-2-license.tag --- lintian-2.93.0/tags/c/copyright-file-contains-full-apache-2-license.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/copyright-file-contains-full-apache-2-license.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: copyright-file-contains-full-apache-2-license -Severity: error -Check: debian/copyright -Explanation: The copyright file /usr/share/doc/*pkg*/copyright contains the - complete text of the Apache 2.0 license. It should refer to the file - /usr/share/common-licenses/Apache-2.0 instead. -See-Also: policy 12.5 diff -Nru lintian-2.93.0/tags/c/copyright-file-contains-full-gfdl-license.desc lintian-2.89.0ubuntu1/tags/c/copyright-file-contains-full-gfdl-license.desc --- lintian-2.93.0/tags/c/copyright-file-contains-full-gfdl-license.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/copyright-file-contains-full-gfdl-license.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: copyright-file-contains-full-gfdl-license +Severity: error +Check: debian/copyright +Info: The copyright file /usr/share/doc/pkg/copyright contains the + complete text of the GFDL v1.2. It should refer to the file + /usr/share/common-licenses/GFDL-1.2 instead. +Ref: policy 12.5 diff -Nru lintian-2.93.0/tags/c/copyright-file-contains-full-gfdl-license.tag lintian-2.89.0ubuntu1/tags/c/copyright-file-contains-full-gfdl-license.tag --- lintian-2.93.0/tags/c/copyright-file-contains-full-gfdl-license.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/copyright-file-contains-full-gfdl-license.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: copyright-file-contains-full-gfdl-license -Severity: error -Check: debian/copyright -Explanation: The copyright file /usr/share/doc/*pkg*/copyright contains the - complete text of the GFDL v1.2. It should refer to the file - /usr/share/common-licenses/GFDL-1.2 instead. -See-Also: policy 12.5 diff -Nru lintian-2.93.0/tags/c/copyright-file-contains-full-gpl-license.desc lintian-2.89.0ubuntu1/tags/c/copyright-file-contains-full-gpl-license.desc --- lintian-2.93.0/tags/c/copyright-file-contains-full-gpl-license.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/copyright-file-contains-full-gpl-license.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: copyright-file-contains-full-gpl-license +Severity: error +Check: debian/copyright +Info: The copyright file /usr/share/doc/pkg/copyright contains the + complete text of the GPL v1, v2, or v3. It should refer to the file + /usr/share/common-licenses/GPL-1, GPL-2, or + GPL-3 instead. +Ref: policy 12.5 diff -Nru lintian-2.93.0/tags/c/copyright-file-contains-full-gpl-license.tag lintian-2.89.0ubuntu1/tags/c/copyright-file-contains-full-gpl-license.tag --- lintian-2.93.0/tags/c/copyright-file-contains-full-gpl-license.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/copyright-file-contains-full-gpl-license.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: copyright-file-contains-full-gpl-license -Severity: error -Check: debian/copyright -Explanation: The copyright file /usr/share/doc/*pkg*/copyright contains the - complete text of the GPL v1, v2, or v3. It should refer to the file - /usr/share/common-licenses/GPL-1, GPL-2, or - GPL-3 instead. -See-Also: policy 12.5 diff -Nru lintian-2.93.0/tags/c/copyright-file-is-symlink.desc lintian-2.89.0ubuntu1/tags/c/copyright-file-is-symlink.desc --- lintian-2.93.0/tags/c/copyright-file-is-symlink.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/copyright-file-is-symlink.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: copyright-file-is-symlink +Severity: error +Check: debian/copyright +Info: The copyright file /usr/share/doc/pkg/copyright must not be a + symbolic link. +Ref: policy 12.5 diff -Nru lintian-2.93.0/tags/c/copyright-file-is-symlink.tag lintian-2.89.0ubuntu1/tags/c/copyright-file-is-symlink.tag --- lintian-2.93.0/tags/c/copyright-file-is-symlink.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/copyright-file-is-symlink.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: copyright-file-is-symlink -Severity: error -Check: debian/copyright -Explanation: The copyright file /usr/share/doc/*pkg*/copyright must not be a - symbolic link. -See-Also: policy 12.5 diff -Nru lintian-2.93.0/tags/c/copyright-file-lacks-pointer-to-perl-license.desc lintian-2.89.0ubuntu1/tags/c/copyright-file-lacks-pointer-to-perl-license.desc --- lintian-2.93.0/tags/c/copyright-file-lacks-pointer-to-perl-license.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/copyright-file-lacks-pointer-to-perl-license.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: copyright-file-lacks-pointer-to-perl-license +Severity: error +Certainty: possible +Check: debian/copyright +Ref: policy 12.5 +Info: If your package is released under the same terms as Perl itself, + it should refer to the Artistic and GPL license files in the + /usr/share/common-licenses directory. diff -Nru lintian-2.93.0/tags/c/copyright-file-lacks-pointer-to-perl-license.tag lintian-2.89.0ubuntu1/tags/c/copyright-file-lacks-pointer-to-perl-license.tag --- lintian-2.93.0/tags/c/copyright-file-lacks-pointer-to-perl-license.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/copyright-file-lacks-pointer-to-perl-license.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: copyright-file-lacks-pointer-to-perl-license -Severity: error -Check: debian/copyright -See-Also: policy 12.5 -Explanation: If your package is released under the same terms as Perl itself, - it should refer to the Artistic and GPL license files in the - /usr/share/common-licenses directory. diff -Nru lintian-2.93.0/tags/c/copyright-has-crs.desc lintian-2.89.0ubuntu1/tags/c/copyright-has-crs.desc --- lintian-2.93.0/tags/c/copyright-has-crs.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/copyright-has-crs.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: copyright-has-crs +Severity: pedantic +Check: debian/copyright +Info: The copyright file has lines ending in CRLF instead of just LF. + . + Running the following command against the given file removes any + CR character in the file: + . + sed -i 's/\r//g' path/to/file diff -Nru lintian-2.93.0/tags/c/copyright-has-crs.tag lintian-2.89.0ubuntu1/tags/c/copyright-has-crs.tag --- lintian-2.93.0/tags/c/copyright-has-crs.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/copyright-has-crs.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: copyright-has-crs -Severity: pedantic -Check: debian/copyright -Explanation: The copyright file has lines ending in CRLF instead of just LF. - . - Running the following command against the given file removes any - CR character in the file: - . - sed -i 's/\r//g' path/to/file diff -Nru lintian-2.93.0/tags/c/copyright-has-url-from-dh_make-boilerplate.desc lintian-2.89.0ubuntu1/tags/c/copyright-has-url-from-dh_make-boilerplate.desc --- lintian-2.93.0/tags/c/copyright-has-url-from-dh_make-boilerplate.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/copyright-has-url-from-dh_make-boilerplate.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: copyright-has-url-from-dh_make-boilerplate +Severity: warning +Check: debian/copyright +Ref: policy 12.5 +Info: There is "url://example.com" in your copyright file. This was most + likely a remnant from the dh_make template. + . + Make sure you include the real location where you obtained the + upstream sources (if any). diff -Nru lintian-2.93.0/tags/c/copyright-has-url-from-dh_make-boilerplate.tag lintian-2.89.0ubuntu1/tags/c/copyright-has-url-from-dh_make-boilerplate.tag --- lintian-2.93.0/tags/c/copyright-has-url-from-dh_make-boilerplate.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/copyright-has-url-from-dh_make-boilerplate.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: copyright-has-url-from-dh_make-boilerplate -Severity: warning -Check: debian/copyright -See-Also: policy 12.5 -Explanation: There is "url://example.com" in your copyright file. This was most - likely a remnant from the dh_make template. - . - Make sure you include the real location where you obtained the - upstream sources (if any). diff -Nru lintian-2.93.0/tags/c/copyright-not-using-common-license-for-apache2.desc lintian-2.89.0ubuntu1/tags/c/copyright-not-using-common-license-for-apache2.desc --- lintian-2.93.0/tags/c/copyright-not-using-common-license-for-apache2.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/copyright-not-using-common-license-for-apache2.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,13 @@ +Tag: copyright-not-using-common-license-for-apache2 +Severity: error +Certainty: possible +Check: debian/copyright +Renamed-From: copyright-should-refer-to-common-license-file-for-apache-2 +Ref: policy 12.5 +Info: The strings "Apache License, Version" or "Apache-2" appear in the + copyright file for this package, but the copyright file does not + reference /usr/share/common-licenses as the location of the + Apache-2 on Debian systems. + . + If the copyright file must mention the Apache-2 for reasons other than + stating the license of the package, please add a Lintian override. diff -Nru lintian-2.93.0/tags/c/copyright-not-using-common-license-for-apache2.tag lintian-2.89.0ubuntu1/tags/c/copyright-not-using-common-license-for-apache2.tag --- lintian-2.93.0/tags/c/copyright-not-using-common-license-for-apache2.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/copyright-not-using-common-license-for-apache2.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,12 +0,0 @@ -Tag: copyright-not-using-common-license-for-apache2 -Severity: error -Check: debian/copyright -Renamed-From: copyright-should-refer-to-common-license-file-for-apache-2 -See-Also: policy 12.5 -Explanation: The strings "Apache License, Version" or "Apache-2" appear in the - copyright file for this package, but the copyright file does not - reference /usr/share/common-licenses as the location of the - Apache-2 on Debian systems. - . - If the copyright file must mention the Apache-2 for reasons other than - stating the license of the package, please add a Lintian override. diff -Nru lintian-2.93.0/tags/c/copyright-not-using-common-license-for-gfdl.desc lintian-2.89.0ubuntu1/tags/c/copyright-not-using-common-license-for-gfdl.desc --- lintian-2.93.0/tags/c/copyright-not-using-common-license-for-gfdl.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/copyright-not-using-common-license-for-gfdl.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,13 @@ +Tag: copyright-not-using-common-license-for-gfdl +Severity: error +Certainty: possible +Check: debian/copyright +Renamed-From: copyright-should-refer-to-common-license-file-for-gfdl +Ref: policy 12.5 +Info: The strings "GNU Free Documentation License" or "GFDL" appear in the + copyright file for this package, but the copyright file does not + reference /usr/share/common-licenses as the location of the GFDL + on Debian systems. + . + If the copyright file must mention the GFDL for reasons other than stating + the license of the package, please add a Lintian override. diff -Nru lintian-2.93.0/tags/c/copyright-not-using-common-license-for-gfdl.tag lintian-2.89.0ubuntu1/tags/c/copyright-not-using-common-license-for-gfdl.tag --- lintian-2.93.0/tags/c/copyright-not-using-common-license-for-gfdl.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/copyright-not-using-common-license-for-gfdl.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,12 +0,0 @@ -Tag: copyright-not-using-common-license-for-gfdl -Severity: error -Check: debian/copyright -Renamed-From: copyright-should-refer-to-common-license-file-for-gfdl -See-Also: policy 12.5 -Explanation: The strings "GNU Free Documentation License" or "GFDL" appear in the - copyright file for this package, but the copyright file does not - reference /usr/share/common-licenses as the location of the GFDL - on Debian systems. - . - If the copyright file must mention the GFDL for reasons other than stating - the license of the package, please add a Lintian override. diff -Nru lintian-2.93.0/tags/c/copyright-not-using-common-license-for-gpl.desc lintian-2.89.0ubuntu1/tags/c/copyright-not-using-common-license-for-gpl.desc --- lintian-2.93.0/tags/c/copyright-not-using-common-license-for-gpl.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/copyright-not-using-common-license-for-gpl.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,13 @@ +Tag: copyright-not-using-common-license-for-gpl +Severity: error +Certainty: possible +Check: debian/copyright +Renamed-From: copyright-should-refer-to-common-license-file-for-gpl +Ref: policy 12.5 +Info: The strings "GNU General Public License" or "GPL" appear in the + copyright file for this package, but the copyright file does not + reference /usr/share/common-licenses as the location of the GPL + on Debian systems. + . + If the copyright file must mention the GPL for reasons other than stating + the license of the package, please add a Lintian override. diff -Nru lintian-2.93.0/tags/c/copyright-not-using-common-license-for-gpl.tag lintian-2.89.0ubuntu1/tags/c/copyright-not-using-common-license-for-gpl.tag --- lintian-2.93.0/tags/c/copyright-not-using-common-license-for-gpl.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/copyright-not-using-common-license-for-gpl.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,12 +0,0 @@ -Tag: copyright-not-using-common-license-for-gpl -Severity: error -Check: debian/copyright -Renamed-From: copyright-should-refer-to-common-license-file-for-gpl -See-Also: policy 12.5 -Explanation: The strings "GNU General Public License" or "GPL" appear in the - copyright file for this package, but the copyright file does not - reference /usr/share/common-licenses as the location of the GPL - on Debian systems. - . - If the copyright file must mention the GPL for reasons other than stating - the license of the package, please add a Lintian override. diff -Nru lintian-2.93.0/tags/c/copyright-not-using-common-license-for-lgpl.desc lintian-2.89.0ubuntu1/tags/c/copyright-not-using-common-license-for-lgpl.desc --- lintian-2.93.0/tags/c/copyright-not-using-common-license-for-lgpl.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/copyright-not-using-common-license-for-lgpl.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,14 @@ +Tag: copyright-not-using-common-license-for-lgpl +Severity: error +Certainty: possible +Check: debian/copyright +Renamed-From: copyright-should-refer-to-common-license-file-for-lgpl +Ref: policy 12.5 +Info: The strings "GNU Lesser General Public License", "GNU Library + General Public License", or "LGPL" appear in the copyright file for this + package, but the copyright file does not reference + /usr/share/common-licenses as the location of the LGPL on Debian + systems. + . + If the copyright file must mention the LGPL for reasons other than stating + the license of the package, please add a Lintian override. diff -Nru lintian-2.93.0/tags/c/copyright-not-using-common-license-for-lgpl.tag lintian-2.89.0ubuntu1/tags/c/copyright-not-using-common-license-for-lgpl.tag --- lintian-2.93.0/tags/c/copyright-not-using-common-license-for-lgpl.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/copyright-not-using-common-license-for-lgpl.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,13 +0,0 @@ -Tag: copyright-not-using-common-license-for-lgpl -Severity: error -Check: debian/copyright -Renamed-From: copyright-should-refer-to-common-license-file-for-lgpl -See-Also: policy 12.5 -Explanation: The strings "GNU Lesser General Public License", "GNU Library - General Public License", or "LGPL" appear in the copyright file for this - package, but the copyright file does not reference - /usr/share/common-licenses as the location of the LGPL on Debian - systems. - . - If the copyright file must mention the LGPL for reasons other than stating - the license of the package, please add a Lintian override. diff -Nru lintian-2.93.0/tags/c/copyright-refers-to-compressed-license.desc lintian-2.89.0ubuntu1/tags/c/copyright-refers-to-compressed-license.desc --- lintian-2.93.0/tags/c/copyright-refers-to-compressed-license.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/copyright-refers-to-compressed-license.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: copyright-refers-to-compressed-license +Severity: error +Check: debian/copyright +Info: The /usr/share/doc/pkg/copyright file refers to a standard license + /usr/share/common-licenses/{GPL,LGPL,Artistic,BSD}.gz as a compressed + file. Please update the reference (the licenses are installed + uncompressed). diff -Nru lintian-2.93.0/tags/c/copyright-refers-to-compressed-license.tag lintian-2.89.0ubuntu1/tags/c/copyright-refers-to-compressed-license.tag --- lintian-2.93.0/tags/c/copyright-refers-to-compressed-license.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/copyright-refers-to-compressed-license.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: copyright-refers-to-compressed-license -Severity: error -Check: debian/copyright -Explanation: The /usr/share/doc/*pkg*/copyright file refers to a standard license - /usr/share/common-licenses/{GPL,LGPL,Artistic,BSD}.gz as a compressed - file. Please update the reference (the licenses are installed - uncompressed). diff -Nru lintian-2.93.0/tags/c/copyright-refers-to-deprecated-bsd-license-file.desc lintian-2.89.0ubuntu1/tags/c/copyright-refers-to-deprecated-bsd-license-file.desc --- lintian-2.93.0/tags/c/copyright-refers-to-deprecated-bsd-license-file.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/copyright-refers-to-deprecated-bsd-license-file.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,13 @@ +Tag: copyright-refers-to-deprecated-bsd-license-file +Severity: warning +Check: debian/copyright +Ref: policy 12.5 +Info: The copyright file refers to + /usr/share/common-licenses/BSD. Due to the brevity of this + license, the specificity of this copy to code whose copyright is held by + the Regents of the University of California, and the frequency of minor + wording changes in the license, its text should be included in the + copyright file directly rather than referencing this file. + . + This file may be removed from a future version of base-files if + references to it drop sufficiently. diff -Nru lintian-2.93.0/tags/c/copyright-refers-to-deprecated-bsd-license-file.tag lintian-2.89.0ubuntu1/tags/c/copyright-refers-to-deprecated-bsd-license-file.tag --- lintian-2.93.0/tags/c/copyright-refers-to-deprecated-bsd-license-file.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/copyright-refers-to-deprecated-bsd-license-file.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,13 +0,0 @@ -Tag: copyright-refers-to-deprecated-bsd-license-file -Severity: warning -Check: debian/copyright -See-Also: policy 12.5 -Explanation: The copyright file refers to - /usr/share/common-licenses/BSD. Due to the brevity of this - license, the specificity of this copy to code whose copyright is held by - the Regents of the University of California, and the frequency of minor - wording changes in the license, its text should be included in the - copyright file directly rather than referencing this file. - . - This file may be removed from a future version of base-files if - references to it drop sufficiently. diff -Nru lintian-2.93.0/tags/c/copyright-refers-to-incorrect-directory.desc lintian-2.89.0ubuntu1/tags/c/copyright-refers-to-incorrect-directory.desc --- lintian-2.93.0/tags/c/copyright-refers-to-incorrect-directory.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/copyright-refers-to-incorrect-directory.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: copyright-refers-to-incorrect-directory +Severity: error +Check: debian/copyright +Ref: policy 12.5 +Info: In the directory name /usr/share/common-licenses, licenses is spelled + with an "s", not as licences with a "c". diff -Nru lintian-2.93.0/tags/c/copyright-refers-to-incorrect-directory.tag lintian-2.89.0ubuntu1/tags/c/copyright-refers-to-incorrect-directory.tag --- lintian-2.93.0/tags/c/copyright-refers-to-incorrect-directory.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/copyright-refers-to-incorrect-directory.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: copyright-refers-to-incorrect-directory -Severity: error -Check: debian/copyright -See-Also: policy 12.5 -Explanation: In the directory name /usr/share/common-licenses, licenses is spelled - with an "s", not as licences with a "c". diff -Nru lintian-2.93.0/tags/c/copyright-refers-to-nonexistent-license-file.desc lintian-2.89.0ubuntu1/tags/c/copyright-refers-to-nonexistent-license-file.desc --- lintian-2.93.0/tags/c/copyright-refers-to-nonexistent-license-file.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/copyright-refers-to-nonexistent-license-file.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: copyright-refers-to-nonexistent-license-file +Severity: warning +Check: debian/copyright +Info: The copyright file refers to a license in + /usr/share/common-licenses that doesn't exist. Usually this is + a typo, such as accidentally omitting the - between the license + name and the version number. diff -Nru lintian-2.93.0/tags/c/copyright-refers-to-nonexistent-license-file.tag lintian-2.89.0ubuntu1/tags/c/copyright-refers-to-nonexistent-license-file.tag --- lintian-2.93.0/tags/c/copyright-refers-to-nonexistent-license-file.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/copyright-refers-to-nonexistent-license-file.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: copyright-refers-to-nonexistent-license-file -Severity: warning -Check: debian/copyright -Explanation: The copyright file refers to a license in - /usr/share/common-licenses that doesn't exist. Usually this is - a typo, such as accidentally omitting the - between the license - name and the version number. diff -Nru lintian-2.93.0/tags/c/copyright-refers-to-old-directory.desc lintian-2.89.0ubuntu1/tags/c/copyright-refers-to-old-directory.desc --- lintian-2.93.0/tags/c/copyright-refers-to-old-directory.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/copyright-refers-to-old-directory.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: copyright-refers-to-old-directory +Severity: error +Check: debian/copyright +Info: The common licenses (GPL, BSD, Artistic, etc) have been moved from + /usr/doc/copyright to /usr/share/common-licenses. + Copyright files should be updated. +Ref: policy 12.5 diff -Nru lintian-2.93.0/tags/c/copyright-refers-to-old-directory.tag lintian-2.89.0ubuntu1/tags/c/copyright-refers-to-old-directory.tag --- lintian-2.93.0/tags/c/copyright-refers-to-old-directory.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/copyright-refers-to-old-directory.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: copyright-refers-to-old-directory -Severity: error -Check: debian/copyright -Explanation: The common licenses (GPL, BSD, Artistic, etc) have been moved from - /usr/doc/copyright to /usr/share/common-licenses. - Copyright files should be updated. -See-Also: policy 12.5 diff -Nru lintian-2.93.0/tags/c/copyright-refers-to-symlink-license.desc lintian-2.89.0ubuntu1/tags/c/copyright-refers-to-symlink-license.desc --- lintian-2.93.0/tags/c/copyright-refers-to-symlink-license.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/copyright-refers-to-symlink-license.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,22 @@ +Tag: copyright-refers-to-symlink-license +Severity: pedantic +Certainty: possible +Check: debian/copyright +Info: The copyright file refers to the versionless symlink in + /usr/share/common-licenses for the full text of the GPL, LGPL, + or GFDL license. This symlink is updated to point to the latest version + of the license when a new one is released. The package appears to allow + relicensing under later versions of its license, so this is legally + consistent, but it implies that Debian will relicense the package under + later versions of those licenses as they're released. It is normally + better to point to the version of the license the package references in + its license statement. + . + For example, if the package says something like "you may redistribute it + and/or modify it under the terms of the GNU General Public License as + published by the Free Software Foundation; either version 2, or (at your + option) any later version", the debian/copyright file should + refer to /usr/share/common-licenses/GPL-2, not /GPL. + . + For packages released under the same terms as Perl, Perl references the + GPL version 1, so point to /usr/share/common-licenses/GPL-1. diff -Nru lintian-2.93.0/tags/c/copyright-refers-to-symlink-license.tag lintian-2.89.0ubuntu1/tags/c/copyright-refers-to-symlink-license.tag --- lintian-2.93.0/tags/c/copyright-refers-to-symlink-license.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/copyright-refers-to-symlink-license.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,21 +0,0 @@ -Tag: copyright-refers-to-symlink-license -Severity: pedantic -Check: debian/copyright -Explanation: The copyright file refers to the versionless symlink in - /usr/share/common-licenses for the full text of the GPL, LGPL, - or GFDL license. This symlink is updated to point to the latest version - of the license when a new one is released. The package appears to allow - relicensing under later versions of its license, so this is legally - consistent, but it implies that Debian will relicense the package under - later versions of those licenses as they're released. It is normally - better to point to the version of the license the package references in - its license statement. - . - For example, if the package says something like "you may redistribute it - and/or modify it under the terms of the GNU General Public License as - published by the Free Software Foundation; either version 2, or (at your - option) any later version", the debian/copyright file should - refer to /usr/share/common-licenses/GPL-2, not /GPL. - . - For packages released under the same terms as Perl, Perl references the - GPL version 1, so point to /usr/share/common-licenses/GPL-1. diff -Nru lintian-2.93.0/tags/c/copyright-refers-to-versionless-license-file.desc lintian-2.89.0ubuntu1/tags/c/copyright-refers-to-versionless-license-file.desc --- lintian-2.93.0/tags/c/copyright-refers-to-versionless-license-file.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/copyright-refers-to-versionless-license-file.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,18 @@ +Tag: copyright-refers-to-versionless-license-file +Severity: warning +Certainty: possible +Check: debian/copyright +Info: The copyright file refers to the versionless symlink in + /usr/share/common-licenses for the full text of the GPL, LGPL, + or GFDL license, but the package does not appear to allow distribution + under later versions of the license. This symlink will change with each + release of a new version of the license and may therefore point to a + different version than the package is released under. + debian/copyright should instead refers to the specific version + of the license that the package references. + . + For example, if the package says something like "you can redistribute it + and/or modify it under the terms of the GNU General Public License as + published by the Free Software Foundation; version 2 dated June, 1991," + the debian/copyright file should refer to + /usr/share/common-licenses/GPL-2, not /GPL. diff -Nru lintian-2.93.0/tags/c/copyright-refers-to-versionless-license-file.tag lintian-2.89.0ubuntu1/tags/c/copyright-refers-to-versionless-license-file.tag --- lintian-2.93.0/tags/c/copyright-refers-to-versionless-license-file.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/copyright-refers-to-versionless-license-file.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,17 +0,0 @@ -Tag: copyright-refers-to-versionless-license-file -Severity: warning -Check: debian/copyright -Explanation: The copyright file refers to the versionless symlink in - /usr/share/common-licenses for the full text of the GPL, LGPL, - or GFDL license, but the package does not appear to allow distribution - under later versions of the license. This symlink will change with each - release of a new version of the license and may therefore point to a - different version than the package is released under. - debian/copyright should instead refers to the specific version - of the license that the package references. - . - For example, if the package says something like "you can redistribute it - and/or modify it under the terms of the GNU General Public License as - published by the Free Software Foundation; version 2 dated June, 1991," - the debian/copyright file should refer to - /usr/share/common-licenses/GPL-2, not /GPL. diff -Nru lintian-2.93.0/tags/c/copyright-with-old-dh-make-debian-copyright.desc lintian-2.89.0ubuntu1/tags/c/copyright-with-old-dh-make-debian-copyright.desc --- lintian-2.93.0/tags/c/copyright-with-old-dh-make-debian-copyright.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/copyright-with-old-dh-make-debian-copyright.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,14 @@ +Tag: copyright-with-old-dh-make-debian-copyright +Severity: pedantic +Check: debian/copyright +Info: The copyright file contains the incomplete Debian packaging + copyright boilerplate from older versions of dh_make. + (C) alone is not considered a valid copyright notice in some + countries. The word Copyright or the © symbol should be used + instead or in addition to (C). + . + Copyright notices like this are, in any country that's a signatory to the + Berne Convention, not required to claim copyright on a work, but their + presence may allow claiming additional damages should a copyright case go + to court. If you provide a notice, you may as well provide one that's + legally recognized in a broader range of countries. diff -Nru lintian-2.93.0/tags/c/copyright-with-old-dh-make-debian-copyright.tag lintian-2.89.0ubuntu1/tags/c/copyright-with-old-dh-make-debian-copyright.tag --- lintian-2.93.0/tags/c/copyright-with-old-dh-make-debian-copyright.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/copyright-with-old-dh-make-debian-copyright.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,14 +0,0 @@ -Tag: copyright-with-old-dh-make-debian-copyright -Severity: pedantic -Check: debian/copyright -Explanation: The copyright file contains the incomplete Debian packaging - copyright boilerplate from older versions of dh_make. - (C) alone is not considered a valid copyright notice in some - countries. The word Copyright or the © symbol should be used - instead or in addition to (C). - . - Copyright notices like this are, in any country that's a signatory to the - Berne Convention, not required to claim copyright on a work, but their - presence may allow claiming additional damages should a copyright case go - to court. If you provide a notice, you may as well provide one that's - legally recognized in a broader range of countries. diff -Nru lintian-2.93.0/tags/c/copyright-without-copyright-notice.desc lintian-2.89.0ubuntu1/tags/c/copyright-without-copyright-notice.desc --- lintian-2.93.0/tags/c/copyright-without-copyright-notice.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/copyright-without-copyright-notice.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,22 @@ +Tag: copyright-without-copyright-notice +Severity: warning +Check: debian/copyright +Ref: https://ftp-master.debian.org/REJECT-FAQ.html +Info: The copyright file for this package does not appear to contain a + copyright notice. You should copy the copyright notice from the upstream + source (or add one of your own for a native package). A copyright notice + must consist of Copyright, Copr., or the Unicode symbol of C in a circle + followed by the years and the copyright holder. A copyright notice is + not required for a work to be copyrighted, but Debian requires the + copyright file include the authors and years of copyright, and including + a valid copyright notice is the best way to do that. Examples: + . + Copyright YYYY Firstname Lastname <address@example.com> + Copr. YYYY-YYYY Firstname Lastname <address@example.com> + © YYYY,YYYY Firstname Lastname <address@example.com> + . + If the package is in the public domain rather than copyrighted, be sure + to mention "public domain" in the copyright file. Please be aware that + this is very rare and not the same as a DFSG-free license. True public + domain software is generally limited to such special cases as a work + product of a United States government agency. diff -Nru lintian-2.93.0/tags/c/copyright-without-copyright-notice.tag lintian-2.89.0ubuntu1/tags/c/copyright-without-copyright-notice.tag --- lintian-2.93.0/tags/c/copyright-without-copyright-notice.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/copyright-without-copyright-notice.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,22 +0,0 @@ -Tag: copyright-without-copyright-notice -Severity: warning -Check: debian/copyright -See-Also: https://ftp-master.debian.org/REJECT-FAQ.html -Explanation: The copyright file for this package does not appear to contain a - copyright notice. You should copy the copyright notice from the upstream - source (or add one of your own for a native package). A copyright notice - must consist of Copyright, Copr., or the Unicode symbol of C in a circle - followed by the years and the copyright holder. A copyright notice is - not required for a work to be copyrighted, but Debian requires the - copyright file include the authors and years of copyright, and including - a valid copyright notice is the best way to do that. Examples: - . - Copyright YYYY Firstname Lastname <address@example.com> - Copr. YYYY-YYYY Firstname Lastname <address@example.com> - © YYYY,YYYY Firstname Lastname <address@example.com> - . - If the package is in the public domain rather than copyrighted, be sure - to mention "public domain" in the copyright file. Please be aware that - this is very rare and not the same as a DFSG-free license. True public - domain software is generally limited to such special cases as a work - product of a United States government agency. diff -Nru lintian-2.93.0/tags/c/country-in-manual.desc lintian-2.89.0ubuntu1/tags/c/country-in-manual.desc --- lintian-2.93.0/tags/c/country-in-manual.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/country-in-manual.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: country-in-manual +Severity: warning +Check: documentation/manual +Renamed-From: manpage-locale-dir-country-specific +Info: This package installs a manual page in a locale directory that + includes the country name. A country name should not be included in the + directory name unless it indicates a significant difference in the + language. The known cases where country names are appropriate are pt_BR + and zh_*. +Ref: policy 12.1 diff -Nru lintian-2.93.0/tags/c/country-in-manual.tag lintian-2.89.0ubuntu1/tags/c/country-in-manual.tag --- lintian-2.93.0/tags/c/country-in-manual.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/country-in-manual.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,10 +0,0 @@ -Tag: country-in-manual -Severity: warning -Check: documentation/manual -Renamed-From: manpage-locale-dir-country-specific -Explanation: This package installs a manual page in a locale directory that - includes the country name. A country name should not be included in the - directory name unless it indicates a significant difference in the - language. The known cases where country names are appropriate are pt_BR - and zh_*. -See-Also: policy 12.1 diff -Nru lintian-2.93.0/tags/c/csh-considered-harmful.desc lintian-2.89.0ubuntu1/tags/c/csh-considered-harmful.desc --- lintian-2.93.0/tags/c/csh-considered-harmful.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/csh-considered-harmful.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: csh-considered-harmful +Severity: warning +Check: scripts +Info: The Debian policy for scripts explicitly warns against using csh + and tcsh as scripting languages. +Ref: policy 10.4 diff -Nru lintian-2.93.0/tags/c/csh-considered-harmful.tag lintian-2.89.0ubuntu1/tags/c/csh-considered-harmful.tag --- lintian-2.93.0/tags/c/csh-considered-harmful.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/csh-considered-harmful.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: csh-considered-harmful -Severity: warning -Check: scripts -Explanation: The Debian policy for scripts explicitly warns against using csh - and tcsh as scripting languages. -See-Also: policy 10.4 diff -Nru lintian-2.93.0/tags/c/ctrl-script.desc lintian-2.89.0ubuntu1/tags/c/ctrl-script.desc --- lintian-2.93.0/tags/c/ctrl-script.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/ctrl-script.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: ctrl-script +Severity: classification +Check: control-files +Info: This package has one or more maintainer scripts (or other + executable control files). + . + This flags any control file with the executable bit set. diff -Nru lintian-2.93.0/tags/c/ctrl-script.tag lintian-2.89.0ubuntu1/tags/c/ctrl-script.tag --- lintian-2.93.0/tags/c/ctrl-script.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/ctrl-script.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: ctrl-script -Severity: classification -Check: control-files -Explanation: This package has one or more maintainer scripts (or other - executable control files). - . - This flags any control file with the executable bit set. diff -Nru lintian-2.93.0/tags/c/custom-compression-in-debian-rules.desc lintian-2.89.0ubuntu1/tags/c/custom-compression-in-debian-rules.desc --- lintian-2.93.0/tags/c/custom-compression-in-debian-rules.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/custom-compression-in-debian-rules.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,23 @@ +Tag: custom-compression-in-debian-rules +Severity: warning +Check: debian/rules +Renamed-From: debian-rules-should-not-use-custom-compression-settings +Info: This package calls dh_builddeb(1) to select a custom + compression level or algorithm in debian/rules. Please remove + the call and let dpkg-deb(1) select suitable defaults. + . + Custom compression settings are usually chosen for one of two + reasons: + . + Higher compression levels or more advanced algorithms shrink the + sizes of large files, but they can cause problems in the resource + constrained environments used in Debian's buildd infrastructure. + For example, higher than expected memory consumption may trigger + an FTBFS or a failure to install. + . + Lower compression levels or less advanced algorithms are sometimes + needed to support older Debian version. Unfortunately, they also + make it harder to change the defauls on an archive-wide basis. + . + Some legitimate use cases trigger this tag. Please override it. +Ref: Bug#829100, Bug#906614, Bug##909696, dpkg-deb(1) diff -Nru lintian-2.93.0/tags/c/custom-compression-in-debian-rules.tag lintian-2.89.0ubuntu1/tags/c/custom-compression-in-debian-rules.tag --- lintian-2.93.0/tags/c/custom-compression-in-debian-rules.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/custom-compression-in-debian-rules.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,23 +0,0 @@ -Tag: custom-compression-in-debian-rules -Severity: warning -Check: debian/rules -Renamed-From: debian-rules-should-not-use-custom-compression-settings -Explanation: This package calls dh_builddeb(1) to select a custom - compression level or algorithm in debian/rules. Please remove - the call and let dpkg-deb(1) select suitable defaults. - . - Custom compression settings are usually chosen for one of two - reasons: - . - Higher compression levels or more advanced algorithms shrink the - sizes of large files, but they can cause problems in the resource - constrained environments used in Debian's buildd infrastructure. - For example, higher than expected memory consumption may trigger - an FTBFS or a failure to install. - . - Lower compression levels or less advanced algorithms are sometimes - needed to support older Debian version. Unfortunately, they also - make it harder to change the defauls on an archive-wide basis. - . - Some legitimate use cases trigger this tag. Please override it. -See-Also: Bug#829100, Bug#906614, Bug#909696, dpkg-deb(1) diff -Nru lintian-2.93.0/tags/c/custom-compression-in-debian-source-options.desc lintian-2.89.0ubuntu1/tags/c/custom-compression-in-debian-source-options.desc --- lintian-2.93.0/tags/c/custom-compression-in-debian-source-options.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/custom-compression-in-debian-source-options.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,23 @@ +Tag: custom-compression-in-debian-source-options +Severity: warning +Check: debian/source-dir +Renamed-From: debian-source-options-has-custom-compression-settings +Info: This package selects a custom compression level or algorithm + in debian/source/options. Please remove the call and let + dpkg-deb(1) select suitable defaults. + . + Custom compression settings are usually chosen for one of two + reasons: + . + Higher compression levels or more advanced algorithms shrink the + sizes of large files, but they can cause problems in the resource + constrained environments used in Debian's buildd infrastructure. + For example, higher than expected memory consumption may trigger + an FTBFS or a failure to install. + . + Lower compression levels or less advanced algorithms are sometimes + needed to support older Debian version. Unfortunately, they also + make it harder to change the defauls on an archive-wide basis. + . + Some legitimate use cases trigger this tag. Please override it. +Ref: Bug#829100, Bug#906614, Bug##909696, dpkg-deb(1) diff -Nru lintian-2.93.0/tags/c/custom-compression-in-debian-source-options.tag lintian-2.89.0ubuntu1/tags/c/custom-compression-in-debian-source-options.tag --- lintian-2.93.0/tags/c/custom-compression-in-debian-source-options.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/custom-compression-in-debian-source-options.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,23 +0,0 @@ -Tag: custom-compression-in-debian-source-options -Severity: warning -Check: debian/source-dir -Renamed-From: debian-source-options-has-custom-compression-settings -Explanation: This package selects a custom compression level or algorithm - in debian/source/options. Please remove the call and let - dpkg-deb(1) select suitable defaults. - . - Custom compression settings are usually chosen for one of two - reasons: - . - Higher compression levels or more advanced algorithms shrink the - sizes of large files, but they can cause problems in the resource - constrained environments used in Debian's buildd infrastructure. - For example, higher than expected memory consumption may trigger - an FTBFS or a failure to install. - . - Lower compression levels or less advanced algorithms are sometimes - needed to support older Debian version. Unfortunately, they also - make it harder to change the defauls on an archive-wide basis. - . - Some legitimate use cases trigger this tag. Please override it. -See-Also: Bug#829100, Bug#906614, Bug#909696, dpkg-deb(1) diff -Nru lintian-2.93.0/tags/c/custom-library-search-path.desc lintian-2.89.0ubuntu1/tags/c/custom-library-search-path.desc --- lintian-2.93.0/tags/c/custom-library-search-path.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/custom-library-search-path.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,24 @@ +Tag: custom-library-search-path +Severity: error +Certainty: possible +Check: binaries +Renamed-From: binary-or-shlib-defines-rpath +Ref: https://wiki.debian.org/RpathIssue +Info: The binary or shared library sets RPATH or RUNPATH. This + overrides the normal library search path, possibly interfering with + local policy and causing problems for multilib, among other issues. + . + The only time a binary or shared library in a Debian package should + set RPATH or RUNPATH is if it is linked to private shared libraries + in the same package. In that case, place those private shared + libraries in /usr/lib/package. Libraries used by + binaries in other packages should be placed in /lib or + /usr/lib as appropriate, with a proper SONAME, in which case + RPATH/RUNPATH is unnecessary. + . + To fix this problem, look for link lines like: + gcc test.o -o test -Wl,--rpath,/usr/local/lib + or + gcc test.o -o test -R/usr/local/lib + and remove the -Wl,--rpath or -R argument. You can also + use the chrpath utility to remove the RPATH. diff -Nru lintian-2.93.0/tags/c/custom-library-search-path.tag lintian-2.89.0ubuntu1/tags/c/custom-library-search-path.tag --- lintian-2.93.0/tags/c/custom-library-search-path.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/custom-library-search-path.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,23 +0,0 @@ -Tag: custom-library-search-path -Severity: error -Check: binaries -Renamed-From: binary-or-shlib-defines-rpath -See-Also: https://wiki.debian.org/RpathIssue -Explanation: The binary or shared library sets RPATH or RUNPATH. This - overrides the normal library search path, possibly interfering with - local policy and causing problems for multilib, among other issues. - . - The only time a binary or shared library in a Debian package should - set RPATH or RUNPATH is if it is linked to private shared libraries - in the same package. In that case, place those private shared - libraries in /usr/lib/*package*. Libraries used by - binaries in other packages should be placed in /lib or - /usr/lib as appropriate, with a proper SONAME, in which case - RPATH/RUNPATH is unnecessary. - . - To fix this problem, look for link lines like: - gcc test.o -o test -Wl,--rpath,/usr/local/lib - or - gcc test.o -o test -R/usr/local/lib - and remove the -Wl,--rpath or -R argument. You can also - use the chrpath utility to remove the RPATH. diff -Nru lintian-2.93.0/tags/c/cute-field.desc lintian-2.89.0ubuntu1/tags/c/cute-field.desc --- lintian-2.93.0/tags/c/cute-field.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/cute-field.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: cute-field +Severity: pedantic +Check: fields/style +Info: The named field uses a free-style form of capitalization, which + is permitted by policy. The alternative offered is probably a more + common variant in the archive. +Ref: policy 5.1 diff -Nru lintian-2.93.0/tags/c/cute-field.tag lintian-2.89.0ubuntu1/tags/c/cute-field.tag --- lintian-2.93.0/tags/c/cute-field.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/c/cute-field.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: cute-field -Severity: pedantic -Check: fields/style -Explanation: The named field uses a free-style form of capitalization, which - is permitted by policy. The alternative offered is probably a more - common variant in the archive. -See-Also: policy 5.1 diff -Nru lintian-2.93.0/tags/continuous-integration/salsa/include.desc lintian-2.89.0ubuntu1/tags/continuous-integration/salsa/include.desc --- lintian-2.93.0/tags/continuous-integration/salsa/include.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/continuous-integration/salsa/include.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,5 @@ +Tag: include +Severity: classification +Check: continuous-integration/salsa +Name-Spaced: yes +Info: Include directive in a Salsa CI specification. diff -Nru lintian-2.93.0/tags/continuous-integration/salsa/include.tag lintian-2.89.0ubuntu1/tags/continuous-integration/salsa/include.tag --- lintian-2.93.0/tags/continuous-integration/salsa/include.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/continuous-integration/salsa/include.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,5 +0,0 @@ -Tag: include -Severity: classification -Check: continuous-integration/salsa -Name-Spaced: yes -Explanation: Include directive in a Salsa CI specification. diff -Nru lintian-2.93.0/tags/continuous-integration/salsa/specification.desc lintian-2.89.0ubuntu1/tags/continuous-integration/salsa/specification.desc --- lintian-2.93.0/tags/continuous-integration/salsa/specification.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/continuous-integration/salsa/specification.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,5 @@ +Tag: specification +Severity: classification +Check: continuous-integration/salsa +Name-Spaced: yes +Info: File name likely holding a Salsa CI specification. diff -Nru lintian-2.93.0/tags/continuous-integration/salsa/specification.tag lintian-2.89.0ubuntu1/tags/continuous-integration/salsa/specification.tag --- lintian-2.93.0/tags/continuous-integration/salsa/specification.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/continuous-integration/salsa/specification.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,5 +0,0 @@ -Tag: specification -Severity: classification -Check: continuous-integration/salsa -Name-Spaced: yes -Explanation: File name likely holding a Salsa CI specification. diff -Nru lintian-2.93.0/tags/d/data-tarball-compression-format.desc lintian-2.89.0ubuntu1/tags/d/data-tarball-compression-format.desc --- lintian-2.93.0/tags/d/data-tarball-compression-format.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/data-tarball-compression-format.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,4 @@ +Tag: data-tarball-compression-format +Severity: classification +Check: deb-format +Info: This is the compressor format used for the data.tar tarball. diff -Nru lintian-2.93.0/tags/d/data-tarball-compression-format.tag lintian-2.89.0ubuntu1/tags/d/data-tarball-compression-format.tag --- lintian-2.93.0/tags/d/data-tarball-compression-format.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/data-tarball-compression-format.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,4 +0,0 @@ -Tag: data-tarball-compression-format -Severity: classification -Check: deb-format -Explanation: This is the compressor format used for the data.tar tarball. diff -Nru lintian-2.93.0/tags/d/dbg-package-missing-depends.desc lintian-2.89.0ubuntu1/tags/d/dbg-package-missing-depends.desc --- lintian-2.93.0/tags/d/dbg-package-missing-depends.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/dbg-package-missing-depends.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,16 @@ +Tag: dbg-package-missing-depends +Severity: warning +Check: fields/package-relations +Info: The given binary package has a name of the form of "X-dbg", indicating it + contains detached debugging symbols for the package X. If so, it should + depend on the corresponding package, generally with (= ${binary:Version}) + since the debugging symbols are only useful with the binaries created by + the same build. + . + Note that the package being depended upon cannot be "Architecture: + all". + . + If this package provides debugging symbols for multiple other + packages, it should normally depend on all of those packages as + alternatives. In other words, pkga (= ${binary:Version}) | pkgb (= + ${binary:Version}) and so forth. diff -Nru lintian-2.93.0/tags/d/dbg-package-missing-depends.tag lintian-2.89.0ubuntu1/tags/d/dbg-package-missing-depends.tag --- lintian-2.93.0/tags/d/dbg-package-missing-depends.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/dbg-package-missing-depends.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,16 +0,0 @@ -Tag: dbg-package-missing-depends -Severity: warning -Check: fields/package-relations -Explanation: The given binary package has a name of the form of "X-dbg", indicating it - contains detached debugging symbols for the package X. If so, it should - depend on the corresponding package, generally with (= ${binary:Version}) - since the debugging symbols are only useful with the binaries created by - the same build. - . - Note that the package being depended upon cannot be "Architecture: - all". - . - If this package provides debugging symbols for multiple other - packages, it should normally depend on all of those packages as - alternatives. In other words, pkga (= ${binary:Version}) | pkgb (= - ${binary:Version}) and so forth. diff -Nru lintian-2.93.0/tags/d/dbus-policy-at-console.desc lintian-2.89.0ubuntu1/tags/d/dbus-policy-at-console.desc --- lintian-2.93.0/tags/d/dbus-policy-at-console.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/dbus-policy-at-console.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,25 @@ +Tag: dbus-policy-at-console +Severity: warning +Check: desktop/dbus +Info: The package contains D-Bus policy configuration that uses the + deprecated at_console condition to impose a different policy + for users who are "logged in at the console" according to + systemd-logind, ConsoleKit or similar APIs, such as: + . + <policy context="default"> + <deny send_destination="com.example.PowerManagementDaemon"/> + </policy> + <policy at_console="true"> + <allow send_destination="com.example.PowerManagementDaemon"/> + </policy> + . + The maintainers of D-Bus recommend that services should allow or deny + method calls according to broad categories that are not typically altered + by the system administrator (usually either "all users", or only root + and/or a specified system user). If finer-grained authorization + is required, the service should accept the method call message, then call + out to PolicyKit to decide whether to honor the request. PolicyKit can + use system-administrator-configurable policies to make that decision, + including distinguishing between users who are "at the console" and + those who are not. +Ref: https://bugs.freedesktop.org/show_bug.cgi?id=39611 diff -Nru lintian-2.93.0/tags/d/dbus-policy-at-console.tag lintian-2.89.0ubuntu1/tags/d/dbus-policy-at-console.tag --- lintian-2.93.0/tags/d/dbus-policy-at-console.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/dbus-policy-at-console.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,25 +0,0 @@ -Tag: dbus-policy-at-console -Severity: warning -Check: desktop/dbus -Explanation: The package contains D-Bus policy configuration that uses the - deprecated at_console condition to impose a different policy - for users who are "logged in at the console" according to - systemd-logind, ConsoleKit or similar APIs, such as: - . - <policy context="default"> - <deny send_destination="com.example.PowerManagementDaemon"/> - </policy> - <policy at_console="true"> - <allow send_destination="com.example.PowerManagementDaemon"/> - </policy> - . - The maintainers of D-Bus recommend that services should allow or deny - method calls according to broad categories that are not typically altered - by the system administrator (usually either "all users", or only root - and/or a specified system user). If finer-grained authorization - is required, the service should accept the method call message, then call - out to PolicyKit to decide whether to honor the request. PolicyKit can - use system-administrator-configurable policies to make that decision, - including distinguishing between users who are "at the console" and - those who are not. -See-Also: https://bugs.freedesktop.org/show_bug.cgi?id=39611 diff -Nru lintian-2.93.0/tags/d/dbus-policy-excessively-broad.desc lintian-2.89.0ubuntu1/tags/d/dbus-policy-excessively-broad.desc --- lintian-2.93.0/tags/d/dbus-policy-excessively-broad.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/dbus-policy-excessively-broad.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,30 @@ +Tag: dbus-policy-excessively-broad +Severity: error +Certainty: possible +Check: desktop/dbus +Info: The package contains D-Bus policy configuration that + matches broad classes of messages. This will cause strange side-effects, + is almost certainly unintended, and is a probable security flaw. + . + For instance, + . + <policy user="daemon"> + <allow send_type="method_call"/> + <allow send_destination="com.example.Bees"/> + </policy> + . + in any system bus policy file would allow the daemon user to send + any method call to any service, including method calls which are meant to + be restricted to root-only for security, such as + org.freedesktop.systemd1.Manager.StartTransientUnit. (In addition, + it allows that user to send any message to the com.example.Bees + service.) + . + The intended policy for that particular example was probably more like + . + <policy user="daemon"> + <allow send_type="method_call" send_destination="com.example.Bees"/> + </policy> + . + which correctly allows method calls to that particular service only. +Ref: http://www.openwall.com/lists/oss-security/2015/01/27/25 diff -Nru lintian-2.93.0/tags/d/dbus-policy-excessively-broad.tag lintian-2.89.0ubuntu1/tags/d/dbus-policy-excessively-broad.tag --- lintian-2.93.0/tags/d/dbus-policy-excessively-broad.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/dbus-policy-excessively-broad.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,29 +0,0 @@ -Tag: dbus-policy-excessively-broad -Severity: error -Check: desktop/dbus -Explanation: The package contains D-Bus policy configuration that - matches broad classes of messages. This will cause strange side-effects, - is almost certainly unintended, and is a probable security flaw. - . - For instance, - . - <policy user="daemon"> - <allow send_type="method_call"/> - <allow send_destination="com.example.Bees"/> - </policy> - . - in any system bus policy file would allow the daemon user to send - any method call to any service, including method calls which are meant to - be restricted to root-only for security, such as - org.freedesktop.systemd1.Manager.StartTransientUnit. (In addition, - it allows that user to send any message to the com.example.Bees - service.) - . - The intended policy for that particular example was probably more like - . - <policy user="daemon"> - <allow send_type="method_call" send_destination="com.example.Bees"/> - </policy> - . - which correctly allows method calls to that particular service only. -See-Also: http://www.openwall.com/lists/oss-security/2015/01/27/25 diff -Nru lintian-2.93.0/tags/d/dbus-policy-without-send-destination.desc lintian-2.89.0ubuntu1/tags/d/dbus-policy-without-send-destination.desc --- lintian-2.93.0/tags/d/dbus-policy-without-send-destination.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/dbus-policy-without-send-destination.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,35 @@ +Tag: dbus-policy-without-send-destination +Severity: warning +Check: desktop/dbus +Info: The package contains D-Bus policy configuration that uses + one of the send_* conditions, but does not specify a + send_destination, and is not specific to root. + . + Rules of the form + . + <allow send_interface="com.example.MyInterface"/> + . + allow messages with the given interface to be sent to any + service, not just the one installing the rule, which is rarely + what was intended. + . + Similarly, on the system bus, rules of the form + . + <deny send_interface="com.example.MyInterface"/> + . + are redundant with the system bus's default-deny policy, and have + unintended effects on other services. + . + This check ignores rules of the form + . + <policy user="root"> + <allow ... /> + </policy> + . + which are commonly used for the "agent" pattern seen in services like + BlueZ and NetworkManager: a root-privileged daemon calls out to + one or more per-user user interface agent processes with no specific + name, so send_destination is not easily applicable. + However, such rules should still be made as specific as possible to + avoid undesired side-effects. +Ref: https://bugs.freedesktop.org/show_bug.cgi?id=18961,http://lists.freedesktop.org/archives/dbus/2008-February/009401.html diff -Nru lintian-2.93.0/tags/d/dbus-policy-without-send-destination.tag lintian-2.89.0ubuntu1/tags/d/dbus-policy-without-send-destination.tag --- lintian-2.93.0/tags/d/dbus-policy-without-send-destination.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/dbus-policy-without-send-destination.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,35 +0,0 @@ -Tag: dbus-policy-without-send-destination -Severity: warning -Check: desktop/dbus -Explanation: The package contains D-Bus policy configuration that uses - one of the send_* conditions, but does not specify a - send_destination, and is not specific to root. - . - Rules of the form - . - <allow send_interface="com.example.MyInterface"/> - . - allow messages with the given interface to be sent to *any* - service, not just the one installing the rule, which is rarely - what was intended. - . - Similarly, on the system bus, rules of the form - . - <deny send_interface="com.example.MyInterface"/> - . - are redundant with the system bus's default-deny policy, and have - unintended effects on other services. - . - This check ignores rules of the form - . - <policy user="root"> - <allow ... /> - </policy> - . - which are commonly used for the "agent" pattern seen in services like - BlueZ and NetworkManager: a root-privileged daemon calls out to - one or more per-user user interface agent processes with no specific - name, so send_destination is not easily applicable. - However, such rules should still be made as specific as possible to - avoid undesired side-effects. -See-Also: https://bugs.freedesktop.org/show_bug.cgi?id=18961,http://lists.freedesktop.org/archives/dbus/2008-February/009401.html diff -Nru lintian-2.93.0/tags/d/dbus-session-service-wrong-name.desc lintian-2.89.0ubuntu1/tags/d/dbus-session-service-wrong-name.desc --- lintian-2.93.0/tags/d/dbus-session-service-wrong-name.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/dbus-session-service-wrong-name.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,14 @@ +Tag: dbus-session-service-wrong-name +Severity: info +Check: desktop/dbus +Info: The package contains a D-Bus session service whose filename + does not match the Name field found in the file. + This makes it possible that two non-conflicting packages could + provide the same service name with the same search-path priority + (i.e. in the same directory). dbus-daemon will arbitrarily choose + one of them, which is unlikely to be the desired result. + . + Best-practice is that if you implement a session service whose well-known + name is com.example.MyService1, and it should be + service-activatable, you should achieve that by packaging + /usr/share/dbus-1/services/com.example.MyService1.service. diff -Nru lintian-2.93.0/tags/d/dbus-session-service-wrong-name.tag lintian-2.89.0ubuntu1/tags/d/dbus-session-service-wrong-name.tag --- lintian-2.93.0/tags/d/dbus-session-service-wrong-name.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/dbus-session-service-wrong-name.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,14 +0,0 @@ -Tag: dbus-session-service-wrong-name -Severity: info -Check: desktop/dbus -Explanation: The package contains a D-Bus session service whose filename - does not match the Name field found in the file. - This makes it possible that two non-conflicting packages could - provide the same service name with the same search-path priority - (i.e. in the same directory). dbus-daemon will arbitrarily choose - one of them, which is unlikely to be the desired result. - . - Best-practice is that if you implement a session service whose well-known - name is com.example.MyService1, and it should be - service-activatable, you should achieve that by packaging - /usr/share/dbus-1/services/com.example.MyService1.service. diff -Nru lintian-2.93.0/tags/d/dbus-system-service-wrong-name.desc lintian-2.89.0ubuntu1/tags/d/dbus-system-service-wrong-name.desc --- lintian-2.93.0/tags/d/dbus-system-service-wrong-name.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/dbus-system-service-wrong-name.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,13 @@ +Tag: dbus-system-service-wrong-name +Severity: error +Check: desktop/dbus +Info: The package contains a D-Bus system service whose filename + does not match the Name field found in the file. + This will not work, because dbus-daemon-launch-helper specifically + looks for that filename, in order to keep system-level activation + secure and predictable. + . + If you implement a session service whose well-known name is + com.example.MyService1, and it should be service-activatable, + you must provide + /usr/share/dbus-1/system-services/com.example.MyService1.service. diff -Nru lintian-2.93.0/tags/d/dbus-system-service-wrong-name.tag lintian-2.89.0ubuntu1/tags/d/dbus-system-service-wrong-name.tag --- lintian-2.93.0/tags/d/dbus-system-service-wrong-name.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/dbus-system-service-wrong-name.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,13 +0,0 @@ -Tag: dbus-system-service-wrong-name -Severity: error -Check: desktop/dbus -Explanation: The package contains a D-Bus system service whose filename - does not match the Name field found in the file. - This will not work, because dbus-daemon-launch-helper specifically - looks for that filename, in order to keep system-level activation - secure and predictable. - . - If you implement a session service whose well-known name is - com.example.MyService1, and it should be service-activatable, - you must provide - /usr/share/dbus-1/system-services/com.example.MyService1.service. diff -Nru lintian-2.93.0/tags/d/debconf-config-not-executable.desc lintian-2.89.0ubuntu1/tags/d/debconf-config-not-executable.desc --- lintian-2.93.0/tags/d/debconf-config-not-executable.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debconf-config-not-executable.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,5 @@ +Tag: debconf-config-not-executable +Severity: error +Check: debian/debconf +Info: The debconf "config" script in the package control area must be + executable. diff -Nru lintian-2.93.0/tags/d/debconf-config-not-executable.tag lintian-2.89.0ubuntu1/tags/d/debconf-config-not-executable.tag --- lintian-2.93.0/tags/d/debconf-config-not-executable.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debconf-config-not-executable.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,5 +0,0 @@ -Tag: debconf-config-not-executable -Severity: error -Check: debian/debconf -Explanation: The debconf "config" script in the package control area must be - executable. diff -Nru lintian-2.93.0/tags/d/debconf-is-not-a-registry.desc lintian-2.89.0ubuntu1/tags/d/debconf-is-not-a-registry.desc --- lintian-2.93.0/tags/d/debconf-is-not-a-registry.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debconf-is-not-a-registry.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,18 @@ +Tag: debconf-is-not-a-registry +Severity: warning +Certainty: wild-guess +Check: debian/debconf +Info: In the Unix tradition, Debian packages should have human-readable and + human-editable configuration files. This package uses debconf commands + outside its maintainer scripts, which often indicates that it is taking + configuration information directly from the debconf database. Typically, + packages should use debconf-supplied information to generate + configuration files, and -- to avoid losing configuration information on + upgrades -- should parse these configuration files in the config + script if it is necessary to ask the user for changes. + . + Some standalone programs may legitimately use debconf to prompt the user + for questions. If you maintain a package containing such a program, + please install an override. Other exceptions to this check include + configuration scripts called from the package's post-installation script. +Ref: devref 6.5.1, debconf-devel(7) diff -Nru lintian-2.93.0/tags/d/debconf-is-not-a-registry.tag lintian-2.89.0ubuntu1/tags/d/debconf-is-not-a-registry.tag --- lintian-2.93.0/tags/d/debconf-is-not-a-registry.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debconf-is-not-a-registry.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,17 +0,0 @@ -Tag: debconf-is-not-a-registry -Severity: warning -Check: debian/debconf -Explanation: In the Unix tradition, Debian packages should have human-readable and - human-editable configuration files. This package uses debconf commands - outside its maintainer scripts, which often indicates that it is taking - configuration information directly from the debconf database. Typically, - packages should use debconf-supplied information to generate - configuration files, and -- to avoid losing configuration information on - upgrades -- should parse these configuration files in the config - script if it is necessary to ask the user for changes. - . - Some standalone programs may legitimately use debconf to prompt the user - for questions. If you maintain a package containing such a program, - please install an override. Other exceptions to this check include - configuration scripts called from the package's post-installation script. -See-Also: devref 6.5.1, debconf-devel(7) diff -Nru lintian-2.93.0/tags/d/debconf-translation-using-general-list.desc lintian-2.89.0ubuntu1/tags/d/debconf-translation-using-general-list.desc --- lintian-2.93.0/tags/d/debconf-translation-using-general-list.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debconf-translation-using-general-list.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,11 @@ +Tag: debconf-translation-using-general-list +Severity: warning +Check: debian/po-debconf +Info: This debconf translation is using the general debconf-i18n list as + the address in the Language-Team field. + . + The intended purpose of the Language-Team field is to be an additional + contact for new translation requests in addition to the previous + translator (as recorded in Last-Translator). The field should therefore + point to a mailing list dedicated to the language of this PO file, not + the general list for translation discussions. diff -Nru lintian-2.93.0/tags/d/debconf-translation-using-general-list.tag lintian-2.89.0ubuntu1/tags/d/debconf-translation-using-general-list.tag --- lintian-2.93.0/tags/d/debconf-translation-using-general-list.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debconf-translation-using-general-list.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,11 +0,0 @@ -Tag: debconf-translation-using-general-list -Severity: warning -Check: debian/po-debconf -Explanation: This debconf translation is using the general debconf-i18n list as - the address in the Language-Team field. - . - The intended purpose of the Language-Team field is to be an additional - contact for new translation requests in addition to the previous - translator (as recorded in Last-Translator). The field should therefore - point to a mailing list dedicated to the language of this PO file, not - the general list for translation discussions. diff -Nru lintian-2.93.0/tags/d/debhelper-autoscript-in-maintainer-scripts.desc lintian-2.89.0ubuntu1/tags/d/debhelper-autoscript-in-maintainer-scripts.desc --- lintian-2.93.0/tags/d/debhelper-autoscript-in-maintainer-scripts.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debhelper-autoscript-in-maintainer-scripts.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: debhelper-autoscript-in-maintainer-scripts +Severity: classification +Certainty: possible +Check: maintainer-scripts/generated +Info: The maintainer scripts of the package contain one or more + auto-generated shell snippets inserted by the listed debhelper tool. diff -Nru lintian-2.93.0/tags/d/debhelper-autoscript-in-maintainer-scripts.tag lintian-2.89.0ubuntu1/tags/d/debhelper-autoscript-in-maintainer-scripts.tag --- lintian-2.93.0/tags/d/debhelper-autoscript-in-maintainer-scripts.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debhelper-autoscript-in-maintainer-scripts.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,5 +0,0 @@ -Tag: debhelper-autoscript-in-maintainer-scripts -Severity: classification -Check: maintainer-scripts/generated -Explanation: The maintainer scripts of the package contain one or more - auto-generated shell snippets inserted by the listed debhelper tool. diff -Nru lintian-2.93.0/tags/d/debhelper-but-no-misc-depends.desc lintian-2.89.0ubuntu1/tags/d/debhelper-but-no-misc-depends.desc --- lintian-2.93.0/tags/d/debhelper-but-no-misc-depends.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debhelper-but-no-misc-depends.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,11 @@ +Tag: debhelper-but-no-misc-depends +Severity: warning +Certainty: possible +Check: debhelper +Ref: debhelper(7) +Info: The source package uses debhelper, but it does not include + ${misc:Depends} in the given binary package's debian/control entry. Any + debhelper command may add dependencies to ${misc:Depends} that are + required for the work that it does, so recommended best practice is to + always add ${misc:Depends} to the dependencies of each binary package if + debhelper is in use. diff -Nru lintian-2.93.0/tags/d/debhelper-but-no-misc-depends.tag lintian-2.89.0ubuntu1/tags/d/debhelper-but-no-misc-depends.tag --- lintian-2.93.0/tags/d/debhelper-but-no-misc-depends.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debhelper-but-no-misc-depends.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,10 +0,0 @@ -Tag: debhelper-but-no-misc-depends -Severity: warning -Check: debhelper -See-Also: debhelper(7) -Explanation: The source package uses debhelper, but it does not include - ${misc:Depends} in the given binary package's debian/control entry. Any - debhelper command may add dependencies to ${misc:Depends} that are - required for the work that it does, so recommended best practice is to - always add ${misc:Depends} to the dependencies of each binary package if - debhelper is in use. diff -Nru lintian-2.93.0/tags/d/debhelper-compat-file-contains-multiple-levels.desc lintian-2.89.0ubuntu1/tags/d/debhelper-compat-file-contains-multiple-levels.desc --- lintian-2.93.0/tags/d/debhelper-compat-file-contains-multiple-levels.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debhelper-compat-file-contains-multiple-levels.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,11 @@ +Tag: debhelper-compat-file-contains-multiple-levels +Severity: error +Check: debhelper +Ref: debhelper(7) +Info: The debian/compat file appears to contain multiple + compatibility levels. + . + This was likely due to the use of >> instead of > when + updating the level. + . + Please update the file to specify a single level. diff -Nru lintian-2.93.0/tags/d/debhelper-compat-file-contains-multiple-levels.tag lintian-2.89.0ubuntu1/tags/d/debhelper-compat-file-contains-multiple-levels.tag --- lintian-2.93.0/tags/d/debhelper-compat-file-contains-multiple-levels.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debhelper-compat-file-contains-multiple-levels.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,11 +0,0 @@ -Tag: debhelper-compat-file-contains-multiple-levels -Severity: error -Check: debhelper -See-Also: debhelper(7) -Explanation: The debian/compat file appears to contain multiple - compatibility levels. - . - This was likely due to the use of >> instead of > when - updating the level. - . - Please update the file to specify a single level. diff -Nru lintian-2.93.0/tags/d/debhelper-compat-file-is-empty.desc lintian-2.89.0ubuntu1/tags/d/debhelper-compat-file-is-empty.desc --- lintian-2.93.0/tags/d/debhelper-compat-file-is-empty.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debhelper-compat-file-is-empty.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: debhelper-compat-file-is-empty +Severity: error +Check: debhelper +Ref: debhelper(7) +Info: The source package has an empty debian/compat file. This is an error, + the compat level of debhelper should be in there. Note that only the first + line of the file is relevant. diff -Nru lintian-2.93.0/tags/d/debhelper-compat-file-is-empty.tag lintian-2.89.0ubuntu1/tags/d/debhelper-compat-file-is-empty.tag --- lintian-2.93.0/tags/d/debhelper-compat-file-is-empty.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debhelper-compat-file-is-empty.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: debhelper-compat-file-is-empty -Severity: error -Check: debhelper -See-Also: debhelper(7) -Explanation: The source package has an empty debian/compat file. This is an error, - the compat level of debhelper should be in there. Note that only the first - line of the file is relevant. diff -Nru lintian-2.93.0/tags/d/debhelper-compat-file-is-missing.desc lintian-2.89.0ubuntu1/tags/d/debhelper-compat-file-is-missing.desc --- lintian-2.93.0/tags/d/debhelper-compat-file-is-missing.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debhelper-compat-file-is-missing.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,14 @@ +Tag: debhelper-compat-file-is-missing +Severity: warning +Check: debhelper +Info: The package build-depends on debhelper but does not ship a compat + file. Packages not using an experimental or beta compatibility level + may alternatively Build-Depend on the debhelper-compat virtual package, + For example: + . + Build-Depends: debhelper-compat (= 13) + . + Please refer to the debhelper documentation on how to create the + compat file and the differences between each compat level. +Ref: https://lists.debian.org/debian-devel-changes/2012/01/msg01335.html, + debhelper(7) diff -Nru lintian-2.93.0/tags/d/debhelper-compat-file-is-missing.tag lintian-2.89.0ubuntu1/tags/d/debhelper-compat-file-is-missing.tag --- lintian-2.93.0/tags/d/debhelper-compat-file-is-missing.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debhelper-compat-file-is-missing.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,14 +0,0 @@ -Tag: debhelper-compat-file-is-missing -Severity: warning -Check: debhelper -Explanation: The package build-depends on debhelper but does not ship a compat - file. Packages not using an experimental or beta compatibility level - may alternatively Build-Depend on the debhelper-compat virtual package, - For example: - . - Build-Depends: debhelper-compat (= 13) - . - Please refer to the debhelper documentation on how to create the - compat file and the differences between each compat level. -See-Also: https://lists.debian.org/debian-devel-changes/2012/01/msg01335.html, - debhelper(7) diff -Nru lintian-2.93.0/tags/d/debhelper-compatibility-level-not-a-number.desc lintian-2.89.0ubuntu1/tags/d/debhelper-compatibility-level-not-a-number.desc --- lintian-2.93.0/tags/d/debhelper-compatibility-level-not-a-number.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debhelper-compatibility-level-not-a-number.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: debhelper-compatibility-level-not-a-number +Severity: error +Certainty: possible +Check: debhelper +Info: The debhelper compatibility level specified in debian/rules + is not a number. If you're using make functions or other more complex + methods to generate the compatibility level, write the output into + debian/compat instead of setting DH_COMPAT. The latter should + be available for a user to override temporarily. diff -Nru lintian-2.93.0/tags/d/debhelper-compatibility-level-not-a-number.tag lintian-2.89.0ubuntu1/tags/d/debhelper-compatibility-level-not-a-number.tag --- lintian-2.93.0/tags/d/debhelper-compatibility-level-not-a-number.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debhelper-compatibility-level-not-a-number.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: debhelper-compatibility-level-not-a-number -Severity: error -Check: debhelper -Explanation: The debhelper compatibility level specified in debian/rules - is not a number. If you're using make functions or other more complex - methods to generate the compatibility level, write the output into - debian/compat instead of setting DH_COMPAT. The latter should - be available for a user to override temporarily. diff -Nru lintian-2.93.0/tags/d/debhelper-compat-level.desc lintian-2.89.0ubuntu1/tags/d/debhelper-compat-level.desc --- lintian-2.93.0/tags/d/debhelper-compat-level.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debhelper-compat-level.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,4 @@ +Tag: debhelper-compat-level +Severity: classification +Check: debhelper +Info: This is the debhelper compat level used specified by this package. diff -Nru lintian-2.93.0/tags/d/debhelper-compat-level.tag lintian-2.89.0ubuntu1/tags/d/debhelper-compat-level.tag --- lintian-2.93.0/tags/d/debhelper-compat-level.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debhelper-compat-level.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,4 +0,0 @@ -Tag: debhelper-compat-level -Severity: classification -Check: debhelper -Explanation: This is the debhelper compat level used specified by this package. diff -Nru lintian-2.93.0/tags/d/debhelper-compat-not-a-number.desc lintian-2.89.0ubuntu1/tags/d/debhelper-compat-not-a-number.desc --- lintian-2.93.0/tags/d/debhelper-compat-not-a-number.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debhelper-compat-not-a-number.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: debhelper-compat-not-a-number +Severity: error +Check: debhelper +Ref: debhelper(7) +Info: The debhelper compatibility level specified in + debian/compat is not a number. diff -Nru lintian-2.93.0/tags/d/debhelper-compat-not-a-number.tag lintian-2.89.0ubuntu1/tags/d/debhelper-compat-not-a-number.tag --- lintian-2.93.0/tags/d/debhelper-compat-not-a-number.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debhelper-compat-not-a-number.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: debhelper-compat-not-a-number -Severity: error -Check: debhelper -See-Also: debhelper(7) -Explanation: The debhelper compatibility level specified in - debian/compat is not a number. diff -Nru lintian-2.93.0/tags/d/debhelper-compat-virtual-relation.desc lintian-2.89.0ubuntu1/tags/d/debhelper-compat-virtual-relation.desc --- lintian-2.93.0/tags/d/debhelper-compat-virtual-relation.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debhelper-compat-virtual-relation.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,5 @@ +Tag: debhelper-compat-virtual-relation +Severity: classification +Check: debhelper +Info: This package is using the debhelper-compat virtual + package as a build-dependency. diff -Nru lintian-2.93.0/tags/d/debhelper-compat-virtual-relation.tag lintian-2.89.0ubuntu1/tags/d/debhelper-compat-virtual-relation.tag --- lintian-2.93.0/tags/d/debhelper-compat-virtual-relation.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debhelper-compat-virtual-relation.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,5 +0,0 @@ -Tag: debhelper-compat-virtual-relation -Severity: classification -Check: debhelper -Explanation: This package is using the debhelper-compat virtual - package as a build-dependency. diff -Nru lintian-2.93.0/tags/d/debhelper-tools-from-autotools-dev-are-deprecated.desc lintian-2.89.0ubuntu1/tags/d/debhelper-tools-from-autotools-dev-are-deprecated.desc --- lintian-2.93.0/tags/d/debhelper-tools-from-autotools-dev-are-deprecated.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debhelper-tools-from-autotools-dev-are-deprecated.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,18 @@ +Tag: debhelper-tools-from-autotools-dev-are-deprecated +Severity: warning +Check: debhelper +Info: The debhelper tools from autotools-dev has been replaced by the tool + dh_update_autotools_config, which was available in + debhelper (>= 9.20160114) + . + The dh_update_autotools_config is run by default via the dh + command sequencer. If you are using dh, you can probably just remove + the uses of the tooling from autotools-dev without doing any further changes. + . + If you use the "classic" debhelper style, then please replace all + calls to dh_autotools-dev_updateconfig with + dh_update_autotools_config. The calls to + dh_autotools-dev_restoreconfig are replaced by + dh_clean, so they can most likely just be removed without + any further changes. +Ref: #878528 diff -Nru lintian-2.93.0/tags/d/debhelper-tools-from-autotools-dev-are-deprecated.tag lintian-2.89.0ubuntu1/tags/d/debhelper-tools-from-autotools-dev-are-deprecated.tag --- lintian-2.93.0/tags/d/debhelper-tools-from-autotools-dev-are-deprecated.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debhelper-tools-from-autotools-dev-are-deprecated.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,19 +0,0 @@ -Tag: debhelper-tools-from-autotools-dev-are-deprecated -Severity: warning -Check: debhelper -Explanation: The debhelper tools from autotools-dev has been replaced by the tool - dh_update_autotools_config, which was available in - debhelper (>= 9.20160114) - . - The dh_update_autotools_config is run - by default via the dh - command sequencer. If you are using dh, you can probably just remove - the uses of the tooling from autotools-dev without doing any further changes. - . - If you use the "classic" debhelper style, then please replace all - calls to dh_autotools-dev_updateconfig with - dh_update_autotools_config. The calls to - dh_autotools-dev_restoreconfig are replaced by - dh_clean, so they can most likely just be removed without - any further changes. -See-Also: Bug#878528 diff -Nru lintian-2.93.0/tags/d/debian-build-system.desc lintian-2.89.0ubuntu1/tags/d/debian-build-system.desc --- lintian-2.93.0/tags/d/debian-build-system.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-build-system.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,5 @@ +Tag: debian-build-system +Severity: classification +Check: debhelper +Info: This is the build system that Lintian believes the package is + using. diff -Nru lintian-2.93.0/tags/d/debian-build-system.tag lintian-2.89.0ubuntu1/tags/d/debian-build-system.tag --- lintian-2.93.0/tags/d/debian-build-system.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-build-system.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,5 +0,0 @@ -Tag: debian-build-system -Severity: classification -Check: debhelper -Explanation: This is the build system that Lintian believes the package is - using. diff -Nru lintian-2.93.0/tags/d/debian-changelog-file-contains-obsolete-user-emacs-settings.desc lintian-2.89.0ubuntu1/tags/d/debian-changelog-file-contains-obsolete-user-emacs-settings.desc --- lintian-2.93.0/tags/d/debian-changelog-file-contains-obsolete-user-emacs-settings.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-changelog-file-contains-obsolete-user-emacs-settings.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: debian-changelog-file-contains-obsolete-user-emacs-settings +Severity: warning +Check: debian/changelog +Info: The add-log-mailing-address variable is no longer honored in + debian-changelog-mode, and should not appear in packages' changelog + files. Instead, put something like this in your ~/.emacs: + . + (setq debian-changelog-mailing-address "userid@debian.org") diff -Nru lintian-2.93.0/tags/d/debian-changelog-file-contains-obsolete-user-emacs-settings.tag lintian-2.89.0ubuntu1/tags/d/debian-changelog-file-contains-obsolete-user-emacs-settings.tag --- lintian-2.93.0/tags/d/debian-changelog-file-contains-obsolete-user-emacs-settings.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-changelog-file-contains-obsolete-user-emacs-settings.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: debian-changelog-file-contains-obsolete-user-emacs-settings -Severity: warning -Check: debian/changelog -Explanation: The add-log-mailing-address variable is no longer honored in - debian-changelog-mode, and should not appear in packages' changelog - files. Instead, put something like this in your ~/.emacs: - . - (setq debian-changelog-mailing-address "userid@debian.org") diff -Nru lintian-2.93.0/tags/d/debian-changelog-file-is-a-symlink.desc lintian-2.89.0ubuntu1/tags/d/debian-changelog-file-is-a-symlink.desc --- lintian-2.93.0/tags/d/debian-changelog-file-is-a-symlink.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-changelog-file-is-a-symlink.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,13 @@ +Tag: debian-changelog-file-is-a-symlink +Severity: warning +Check: debian/changelog +Info: The Debian changelog file is a symlink to a file in a different + directory or not found in this package. Please don't do this. It makes + package checking and manipulation unnecessarily difficult. Because it was + a symlink, the Debian changelog file was not checked for other + problems. (Symlinks to another file in /usr/share/doc/pkg or a + subdirectory thereof are fine and should not trigger this warning.) + . + To refer to the changelog, copyright, and other documentation files of + another package that this one depends on, please symlink the entire + /usr/share/doc/pkg directory rather than individual files. diff -Nru lintian-2.93.0/tags/d/debian-changelog-file-is-a-symlink.tag lintian-2.89.0ubuntu1/tags/d/debian-changelog-file-is-a-symlink.tag --- lintian-2.93.0/tags/d/debian-changelog-file-is-a-symlink.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-changelog-file-is-a-symlink.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,13 +0,0 @@ -Tag: debian-changelog-file-is-a-symlink -Severity: warning -Check: debian/changelog -Explanation: The Debian changelog file is a symlink to a file in a different - directory or not found in this package. Please don't do this. It makes - package checking and manipulation unnecessarily difficult. Because it was - a symlink, the Debian changelog file was not checked for other - problems. (Symlinks to another file in /usr/share/doc/*pkg* or a - subdirectory thereof are fine and should not trigger this warning.) - . - To refer to the changelog, copyright, and other documentation files of - another package that this one depends on, please symlink the entire - /usr/share/doc/*pkg* directory rather than individual files. diff -Nru lintian-2.93.0/tags/d/debian-changelog-file-missing-or-wrong-name.desc lintian-2.89.0ubuntu1/tags/d/debian-changelog-file-missing-or-wrong-name.desc --- lintian-2.93.0/tags/d/debian-changelog-file-missing-or-wrong-name.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-changelog-file-missing-or-wrong-name.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,11 @@ +Tag: debian-changelog-file-missing-or-wrong-name +Severity: error +Check: debian/changelog +Info: Each Debian package (which provides a /usr/share/doc/pkg + directory) must install a Debian changelog file in + /usr/share/doc/pkg/changelog.Debian.gz + . + A common error is to name the Debian changelog like an upstream changelog + (/usr/share/doc/pkg/changelog.gz); therefore, Lintian will apply + further checks to such a file if it exists even after issuing this error. +Ref: policy 12.7 diff -Nru lintian-2.93.0/tags/d/debian-changelog-file-missing-or-wrong-name.tag lintian-2.89.0ubuntu1/tags/d/debian-changelog-file-missing-or-wrong-name.tag --- lintian-2.93.0/tags/d/debian-changelog-file-missing-or-wrong-name.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-changelog-file-missing-or-wrong-name.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,11 +0,0 @@ -Tag: debian-changelog-file-missing-or-wrong-name -Severity: error -Check: debian/changelog -Explanation: Each Debian package (which provides a /usr/share/doc/*pkg* - directory) must install a Debian changelog file in - /usr/share/doc/*pkg*/changelog.Debian.gz - . - A common error is to name the Debian changelog like an upstream changelog - (/usr/share/doc/*pkg*/changelog.gz); therefore, Lintian will apply - further checks to such a file if it exists even after issuing this error. -See-Also: policy 12.7 diff -Nru lintian-2.93.0/tags/d/debian-changelog-has-wrong-day-of-week.desc lintian-2.89.0ubuntu1/tags/d/debian-changelog-has-wrong-day-of-week.desc --- lintian-2.93.0/tags/d/debian-changelog-has-wrong-day-of-week.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-changelog-has-wrong-day-of-week.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,13 @@ +Tag: debian-changelog-has-wrong-day-of-week +Severity: warning +Check: debian/changelog +Info: The date in the changelog entry is not consistent with the actual + day of that week. Either the date is wrong or the day of week is wrong. + . + To avoid problems like this, consider using a tool like dch(1) or + date(1) to generate the date. Example: + . + $ date -R -ud '2013-11-05 23:59:59' + Tue, 05 Nov 2013 23:59:59 +0000 +Renamed-From: + debian-changelog-has-wrong-weekday diff -Nru lintian-2.93.0/tags/d/debian-changelog-has-wrong-day-of-week.tag lintian-2.89.0ubuntu1/tags/d/debian-changelog-has-wrong-day-of-week.tag --- lintian-2.93.0/tags/d/debian-changelog-has-wrong-day-of-week.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-changelog-has-wrong-day-of-week.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,13 +0,0 @@ -Tag: debian-changelog-has-wrong-day-of-week -Severity: warning -Check: debian/changelog -Explanation: The date in the changelog entry is not consistent with the actual - day of that week. Either the date is wrong or the day of week is wrong. - . - To avoid problems like this, consider using a tool like dch(1) or - date(1) to generate the date. Example: - . - $ date -R -ud '2013-11-05 23:59:59' - Tue, 05 Nov 2013 23:59:59 +0000 -Renamed-From: - debian-changelog-has-wrong-weekday diff -Nru lintian-2.93.0/tags/d/debian-changelog-line-too-long.desc lintian-2.89.0ubuntu1/tags/d/debian-changelog-line-too-long.desc --- lintian-2.93.0/tags/d/debian-changelog-line-too-long.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-changelog-line-too-long.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: debian-changelog-line-too-long +Severity: warning +Check: debian/changelog +Info: The given line of the latest changelog entry is over 80 columns. + Such changelog entries may look poor in terminal windows and mail + messages and be annoying to read. Please wrap changelog entries at 80 + columns or less where possible. diff -Nru lintian-2.93.0/tags/d/debian-changelog-line-too-long.tag lintian-2.89.0ubuntu1/tags/d/debian-changelog-line-too-long.tag --- lintian-2.93.0/tags/d/debian-changelog-line-too-long.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-changelog-line-too-long.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: debian-changelog-line-too-long -Severity: warning -Check: debian/changelog -Explanation: The given line of the latest changelog entry is over 80 columns. - Such changelog entries may look poor in terminal windows and mail - messages and be annoying to read. Please wrap changelog entries at 80 - columns or less where possible. diff -Nru lintian-2.93.0/tags/d/debian-changelog-line-too-short.desc lintian-2.89.0ubuntu1/tags/d/debian-changelog-line-too-short.desc --- lintian-2.93.0/tags/d/debian-changelog-line-too-short.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-changelog-line-too-short.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,22 @@ +Tag: debian-changelog-line-too-short +Severity: pedantic +Certainty: possible +Check: debian/changelog +Info: The given line of the latest changelog entry appears to contain a + very terse entry. + . + This can make it hard for others to understand the changelog entry. + Please keep in mind that: + . + * It is not uncommon that people read changelog entries that are more + than a decade old to understand why a change was made or why a + package works in a specific way. + * Many users will read the changelog via + apt-listchanges(1) + * The information in debian/changelog is permanent. + . + Examples for entries that are too short include "dh 11" or simply + "R³" - these could be expanded to, for example: + . + * Switch to debhelper compat 11. + * Set Rules-Requires-Root: no. diff -Nru lintian-2.93.0/tags/d/debian-changelog-line-too-short.tag lintian-2.89.0ubuntu1/tags/d/debian-changelog-line-too-short.tag --- lintian-2.93.0/tags/d/debian-changelog-line-too-short.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-changelog-line-too-short.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,21 +0,0 @@ -Tag: debian-changelog-line-too-short -Severity: pedantic -Check: debian/changelog -Explanation: The given line of the latest changelog entry appears to contain a - very terse entry. - . - This can make it hard for others to understand the changelog entry. - Please keep in mind that: - . - - It is not uncommon that people read changelog entries that are more - than a decade old to understand why a change was made or why a - package works in a specific way. - - Many users will read the changelog via - apt-listchanges(1) - - The information in debian/changelog is permanent. - . - Examples for entries that are too short include "dh 11" or simply - "R³" - these could be expanded to, for example: - . - - Switch to debhelper compat 11. - - Set Rules-Requires-Root: no. diff -Nru lintian-2.93.0/tags/d/debian-control-file-is-a-symlink.desc lintian-2.89.0ubuntu1/tags/d/debian-control-file-is-a-symlink.desc --- lintian-2.93.0/tags/d/debian-control-file-is-a-symlink.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-control-file-is-a-symlink.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: debian-control-file-is-a-symlink +Severity: warning +Check: debian/control +Info: The debian/control file is a symlink rather than a regular + file. Using symlinks for required source package files is unnecessary and + makes package checking and manipulation more difficult. If the control + file should be available in the source package under multiple names, make + debian/control the real file and the other names symlinks to it. diff -Nru lintian-2.93.0/tags/d/debian-control-file-is-a-symlink.tag lintian-2.89.0ubuntu1/tags/d/debian-control-file-is-a-symlink.tag --- lintian-2.93.0/tags/d/debian-control-file-is-a-symlink.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-control-file-is-a-symlink.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: debian-control-file-is-a-symlink -Severity: warning -Check: debian/control -Explanation: The debian/control file is a symlink rather than a regular - file. Using symlinks for required source package files is unnecessary and - makes package checking and manipulation more difficult. If the control - file should be available in the source package under multiple names, make - debian/control the real file and the other names symlinks to it. diff -Nru lintian-2.93.0/tags/d/debian-control-has-dbgsym-package.desc lintian-2.89.0ubuntu1/tags/d/debian-control-has-dbgsym-package.desc --- lintian-2.93.0/tags/d/debian-control-has-dbgsym-package.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-control-has-dbgsym-package.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: debian-control-has-dbgsym-package +Severity: error +Check: debian/control +Ref: #858117, https://wiki.debian.org/DebugPackage +Info: The debian/control file includes declaration of + normally autogenerated -dbgsym package. + . + You should delete this package from debian/control + and use autogeneration. diff -Nru lintian-2.93.0/tags/d/debian-control-has-dbgsym-package.tag lintian-2.89.0ubuntu1/tags/d/debian-control-has-dbgsym-package.tag --- lintian-2.93.0/tags/d/debian-control-has-dbgsym-package.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-control-has-dbgsym-package.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: debian-control-has-dbgsym-package -Severity: error -Check: debian/control -See-Also: Bug#858117, https://wiki.debian.org/DebugPackage -Explanation: The debian/control file includes declaration of - normally autogenerated -dbgsym package. - . - You should delete this package from debian/control - and use autogeneration. diff -Nru lintian-2.93.0/tags/d/debian-control-has-empty-field.desc lintian-2.89.0ubuntu1/tags/d/debian-control-has-empty-field.desc --- lintian-2.93.0/tags/d/debian-control-has-empty-field.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-control-has-empty-field.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: debian-control-has-empty-field +Severity: info +Check: debian/control +Info: The field on this line of debian/control is empty. Whilst + this is permitted in the syntax of Debian control files it is + unnecessary. diff -Nru lintian-2.93.0/tags/d/debian-control-has-empty-field.tag lintian-2.89.0ubuntu1/tags/d/debian-control-has-empty-field.tag --- lintian-2.93.0/tags/d/debian-control-has-empty-field.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-control-has-empty-field.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: debian-control-has-empty-field -Severity: info -Check: debian/control -Explanation: The field on this line of debian/control is empty. Whilst - this is permitted in the syntax of Debian control files it is - unnecessary. diff -Nru lintian-2.93.0/tags/d/debian-control-has-obsolete-dbg-package.desc lintian-2.89.0ubuntu1/tags/d/debian-control-has-obsolete-dbg-package.desc --- lintian-2.93.0/tags/d/debian-control-has-obsolete-dbg-package.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-control-has-obsolete-dbg-package.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,14 @@ +Tag: debian-control-has-obsolete-dbg-package +Severity: info +Certainty: possible +Check: debian/control +Ref: https://wiki.debian.org/AutomaticDebugPackages +Info: The debian/control file includes declaration of + -dbg package. + . + Debug package are now autogenerated avoiding waste of miror + space. + . + Please note that -dbg should be dropped from control file + and must not be transitioned to a dummy package depending + on -dbgsym. diff -Nru lintian-2.93.0/tags/d/debian-control-has-obsolete-dbg-package.tag lintian-2.89.0ubuntu1/tags/d/debian-control-has-obsolete-dbg-package.tag --- lintian-2.93.0/tags/d/debian-control-has-obsolete-dbg-package.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-control-has-obsolete-dbg-package.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,13 +0,0 @@ -Tag: debian-control-has-obsolete-dbg-package -Severity: info -Check: debian/control -See-Also: https://wiki.debian.org/AutomaticDebugPackages -Explanation: The debian/control file includes declaration of - -dbg package. - . - Debug package are now autogenerated avoiding waste of miror - space. - . - Please note that -dbg should be dropped from control file - and must not be transitioned to a dummy package depending - on -dbgsym. diff -Nru lintian-2.93.0/tags/d/debian-control-has-unusual-field-spacing.desc lintian-2.89.0ubuntu1/tags/d/debian-control-has-unusual-field-spacing.desc --- lintian-2.93.0/tags/d/debian-control-has-unusual-field-spacing.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-control-has-unusual-field-spacing.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: debian-control-has-unusual-field-spacing +Severity: pedantic +Check: debian/control +Ref: policy 5.1 +Info: The field on this line of debian/control has whitespace + other than a single space after the colon. This is explicitly permitted + in the syntax of Debian control files, but as Policy says, it is + conventional to put a single space after the colon. diff -Nru lintian-2.93.0/tags/d/debian-control-has-unusual-field-spacing.tag lintian-2.89.0ubuntu1/tags/d/debian-control-has-unusual-field-spacing.tag --- lintian-2.93.0/tags/d/debian-control-has-unusual-field-spacing.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-control-has-unusual-field-spacing.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: debian-control-has-unusual-field-spacing -Severity: pedantic -Check: debian/control -See-Also: policy 5.1 -Explanation: The field on this line of debian/control has whitespace - other than a single space after the colon. This is explicitly permitted - in the syntax of Debian control files, but as Policy says, it is - conventional to put a single space after the colon. diff -Nru lintian-2.93.0/tags/d/debian-control-repeats-field-name-in-value.desc lintian-2.89.0ubuntu1/tags/d/debian-control-repeats-field-name-in-value.desc --- lintian-2.93.0/tags/d/debian-control-repeats-field-name-in-value.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-control-repeats-field-name-in-value.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: debian-control-repeats-field-name-in-value +Severity: warning +Certainty: possible +Check: debian/control +Ref: policy 5.1 +Info: The field on this line of debian/control repeats + the field name in the value of the field. As an example: + . + Maintainer: Maintainer: Some Name <maintainer@mail.example.com> diff -Nru lintian-2.93.0/tags/d/debian-control-repeats-field-name-in-value.tag lintian-2.89.0ubuntu1/tags/d/debian-control-repeats-field-name-in-value.tag --- lintian-2.93.0/tags/d/debian-control-repeats-field-name-in-value.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-control-repeats-field-name-in-value.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: debian-control-repeats-field-name-in-value -Severity: warning -Check: debian/control -See-Also: policy 5.1 -Explanation: The field on this line of debian/control repeats - the field name in the value of the field. As an example: - . - Maintainer: Maintainer: Some Name <maintainer@mail.example.com> diff -Nru lintian-2.93.0/tags/d/debian-copyright-is-symlink.desc lintian-2.89.0ubuntu1/tags/d/debian-copyright-is-symlink.desc --- lintian-2.93.0/tags/d/debian-copyright-is-symlink.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-copyright-is-symlink.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: debian-copyright-is-symlink +Severity: warning +Check: debian/copyright +Info: The file debian/copyright is a symlink instead of a regular + file. This makes package checking and manipulation more difficult. + . + This problem may have prevented Lintian from performing other checks. diff -Nru lintian-2.93.0/tags/d/debian-copyright-is-symlink.tag lintian-2.89.0ubuntu1/tags/d/debian-copyright-is-symlink.tag --- lintian-2.93.0/tags/d/debian-copyright-is-symlink.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-copyright-is-symlink.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: debian-copyright-is-symlink -Severity: warning -Check: debian/copyright -Explanation: The file debian/copyright is a symlink instead of a regular - file. This makes package checking and manipulation more difficult. - . - This problem may have prevented Lintian from performing other checks. diff -Nru lintian-2.93.0/tags/d/debian-files-list-in-source.desc lintian-2.89.0ubuntu1/tags/d/debian-files-list-in-source.desc --- lintian-2.93.0/tags/d/debian-files-list-in-source.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-files-list-in-source.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: debian-files-list-in-source +Severity: error +Check: debian/files +Info: Leaving debian/files causes problems for the autobuilders, + since that file will likely include the list of .deb files for another + architecture, which will cause dpkg-buildpackage run by the buildd to fail. + . + The clean rule for the package should remove this file. +Ref: policy 4.12 diff -Nru lintian-2.93.0/tags/d/debian-files-list-in-source.tag lintian-2.89.0ubuntu1/tags/d/debian-files-list-in-source.tag --- lintian-2.93.0/tags/d/debian-files-list-in-source.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-files-list-in-source.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: debian-files-list-in-source -Severity: error -Check: debian/files -Explanation: Leaving debian/files causes problems for the autobuilders, - since that file will likely include the list of .deb files for another - architecture, which will cause dpkg-buildpackage run by the buildd to fail. - . - The clean rule for the package should remove this file. -See-Also: policy 4.12 diff -Nru lintian-2.93.0/tags/d/debian-news-entry-has-strange-distribution.desc lintian-2.89.0ubuntu1/tags/d/debian-news-entry-has-strange-distribution.desc --- lintian-2.93.0/tags/d/debian-news-entry-has-strange-distribution.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-news-entry-has-strange-distribution.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: debian-news-entry-has-strange-distribution +Severity: warning +Check: debian/changelog +Info: The latest entry in NEWS.Debian has an unusual distribution name. + This field is ignored by the archive software, so its value doesn't truly + matter, but it may be confusing to users reading the entry if the + distribution doesn't match the distribution for the same entry in the + Debian changelog file. diff -Nru lintian-2.93.0/tags/d/debian-news-entry-has-strange-distribution.tag lintian-2.89.0ubuntu1/tags/d/debian-news-entry-has-strange-distribution.tag --- lintian-2.93.0/tags/d/debian-news-entry-has-strange-distribution.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-news-entry-has-strange-distribution.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: debian-news-entry-has-strange-distribution -Severity: warning -Check: debian/changelog -Explanation: The latest entry in NEWS.Debian has an unusual distribution name. - This field is ignored by the archive software, so its value doesn't truly - matter, but it may be confusing to users reading the entry if the - distribution doesn't match the distribution for the same entry in the - Debian changelog file. diff -Nru lintian-2.93.0/tags/d/debian-news-entry-has-unknown-version.desc lintian-2.89.0ubuntu1/tags/d/debian-news-entry-has-unknown-version.desc --- lintian-2.93.0/tags/d/debian-news-entry-has-unknown-version.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-news-entry-has-unknown-version.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: debian-news-entry-has-unknown-version +Severity: warning +Certainty: possible +Check: debian/changelog +Info: The version number of the most recent NEWS.Debian entry + does not match any of the version numbers in the changelog file for this + package. This usually means the version in NEWS.Debian needs to + be updated to match a change to package version that happened after the + NEWS.Debian entry was written. diff -Nru lintian-2.93.0/tags/d/debian-news-entry-has-unknown-version.tag lintian-2.89.0ubuntu1/tags/d/debian-news-entry-has-unknown-version.tag --- lintian-2.93.0/tags/d/debian-news-entry-has-unknown-version.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-news-entry-has-unknown-version.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: debian-news-entry-has-unknown-version -Severity: warning -Check: debian/changelog -Explanation: The version number of the most recent NEWS.Debian entry - does not match any of the version numbers in the changelog file for this - package. This usually means the version in NEWS.Debian needs to - be updated to match a change to package version that happened after the - NEWS.Debian entry was written. diff -Nru lintian-2.93.0/tags/d/debian-news-entry-uses-asterisk.desc lintian-2.89.0ubuntu1/tags/d/debian-news-entry-uses-asterisk.desc --- lintian-2.93.0/tags/d/debian-news-entry-uses-asterisk.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-news-entry-uses-asterisk.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: debian-news-entry-uses-asterisk +Severity: info +Certainty: possible +Check: debian/changelog +Info: The latest entry in NEWS.Debian appears to use asterisks to present + changes in a bulleted list, similar to the normal changelog syntax. The + Debian Developer's Reference recommends using regular paragraphs in + NEWS.Debian rather than a bulleted list. +Ref: devref 6.3.4 diff -Nru lintian-2.93.0/tags/d/debian-news-entry-uses-asterisk.tag lintian-2.89.0ubuntu1/tags/d/debian-news-entry-uses-asterisk.tag --- lintian-2.93.0/tags/d/debian-news-entry-uses-asterisk.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-news-entry-uses-asterisk.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: debian-news-entry-uses-asterisk -Severity: info -Check: debian/changelog -Explanation: The latest entry in NEWS.Debian appears to use asterisks to present - changes in a bulleted list, similar to the normal changelog syntax. The - Debian Developer's Reference recommends using regular paragraphs in - NEWS.Debian rather than a bulleted list. -See-Also: devref 6.3.4 diff -Nru lintian-2.93.0/tags/d/debian-news-file-not-compressed.desc lintian-2.89.0ubuntu1/tags/d/debian-news-file-not-compressed.desc --- lintian-2.93.0/tags/d/debian-news-file-not-compressed.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-news-file-not-compressed.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: debian-news-file-not-compressed +Severity: warning +Check: debian/changelog +Info: NEWS.Debian files should be compressed using "gzip -9". The file + must always have the same name. +Ref: devref 6.3.4 diff -Nru lintian-2.93.0/tags/d/debian-news-file-not-compressed.tag lintian-2.89.0ubuntu1/tags/d/debian-news-file-not-compressed.tag --- lintian-2.93.0/tags/d/debian-news-file-not-compressed.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-news-file-not-compressed.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: debian-news-file-not-compressed -Severity: warning -Check: debian/changelog -Explanation: NEWS.Debian files should be compressed using "gzip -9". The file - must always have the same name. -See-Also: devref 6.3.4 diff -Nru lintian-2.93.0/tags/d/debian-pycompat-is-obsolete.desc lintian-2.89.0ubuntu1/tags/d/debian-pycompat-is-obsolete.desc --- lintian-2.93.0/tags/d/debian-pycompat-is-obsolete.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-pycompat-is-obsolete.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +# Imported from lintian4python (python/helpers) +Tag: debian-pycompat-is-obsolete +Severity: info +Check: languages/python/obsolete +Info: debian/pycompat is not used by any modern Python helper. It should be + safe to remove this file. diff -Nru lintian-2.93.0/tags/d/debian-pycompat-is-obsolete.tag lintian-2.89.0ubuntu1/tags/d/debian-pycompat-is-obsolete.tag --- lintian-2.93.0/tags/d/debian-pycompat-is-obsolete.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-pycompat-is-obsolete.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -# Imported from lintian4python (python/helpers) -Tag: debian-pycompat-is-obsolete -Severity: info -Check: languages/python/obsolete -Explanation: debian/pycompat is not used by any modern Python helper. It should be - safe to remove this file. diff -Nru lintian-2.93.0/tags/d/debian-pyversions-is-obsolete.desc lintian-2.89.0ubuntu1/tags/d/debian-pyversions-is-obsolete.desc --- lintian-2.93.0/tags/d/debian-pyversions-is-obsolete.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-pyversions-is-obsolete.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: debian-pyversions-is-obsolete +Severity: info +Check: languages/python/obsolete +Info: This package contains a debian/pyversions file. Since + dh_python2 it has been recommended to use the + X-Python3-Version field in debian/control instead. +Ref: https://wiki.debian.org/Python/TransitionToDHPython2, + https://www.debian.org/doc/packaging-manuals/python-policy/ch-module_packages.html#s-specifying_versions diff -Nru lintian-2.93.0/tags/d/debian-pyversions-is-obsolete.tag lintian-2.89.0ubuntu1/tags/d/debian-pyversions-is-obsolete.tag --- lintian-2.93.0/tags/d/debian-pyversions-is-obsolete.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-pyversions-is-obsolete.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: debian-pyversions-is-obsolete -Severity: info -Check: languages/python/obsolete -Explanation: This package contains a debian/pyversions file. Since - dh_python2 it has been recommended to use the - X-Python3-Version field in debian/control instead. -See-Also: https://wiki.debian.org/Python/TransitionToDHPython2, - https://www.debian.org/doc/packaging-manuals/python-policy/ch-module_packages.html#s-specifying_versions diff -Nru lintian-2.93.0/tags/d/debian-revision-is-zero.desc lintian-2.89.0ubuntu1/tags/d/debian-revision-is-zero.desc --- lintian-2.93.0/tags/d/debian-revision-is-zero.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-revision-is-zero.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: debian-revision-is-zero +Severity: error +Check: fields/version +Renamed-From: debian-revision-should-not-be-zero +Info: The Debian version part (the part after the -) should start with one, + not with zero. This is to ensure that a correctly-done Maintainer Upload will + always have a higher version number than a Non-Maintainer upload: a NMU could + have been prepared which introduces this upstream version with + Debian-revision -0.1 +Ref: devref 5.11.2 diff -Nru lintian-2.93.0/tags/d/debian-revision-is-zero.tag lintian-2.89.0ubuntu1/tags/d/debian-revision-is-zero.tag --- lintian-2.93.0/tags/d/debian-revision-is-zero.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-revision-is-zero.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,10 +0,0 @@ -Tag: debian-revision-is-zero -Severity: error -Check: fields/version -Renamed-From: debian-revision-should-not-be-zero -Explanation: The Debian version part (the part after the -) should start with one, - not with zero. This is to ensure that a correctly-done Maintainer Upload will - always have a higher version number than a Non-Maintainer upload: a NMU could - have been prepared which introduces this upstream version with - Debian-revision -0.1 -See-Also: devref 5.11.2 diff -Nru lintian-2.93.0/tags/d/debian-revision-not-well-formed.desc lintian-2.89.0ubuntu1/tags/d/debian-revision-not-well-formed.desc --- lintian-2.93.0/tags/d/debian-revision-not-well-formed.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-revision-not-well-formed.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: debian-revision-not-well-formed +Severity: warning +Check: fields/version +Info: The Debian version part (the part after the -) should consist of one + or two dot-separated parts: one for a regular maintainer release or two + for a source-NMU. +Ref: devref 5.11.2, policy 5.6.12 diff -Nru lintian-2.93.0/tags/d/debian-revision-not-well-formed.tag lintian-2.89.0ubuntu1/tags/d/debian-revision-not-well-formed.tag --- lintian-2.93.0/tags/d/debian-revision-not-well-formed.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-revision-not-well-formed.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: debian-revision-not-well-formed -Severity: warning -Check: fields/version -Explanation: The Debian version part (the part after the -) should consist of one - or two dot-separated parts: one for a regular maintainer release or two - for a source-NMU. -See-Also: devref 5.11.2, policy 5.6.12 diff -Nru lintian-2.93.0/tags/d/debian-rules-calls-debhelper-in-odd-order.desc lintian-2.89.0ubuntu1/tags/d/debian-rules-calls-debhelper-in-odd-order.desc --- lintian-2.93.0/tags/d/debian-rules-calls-debhelper-in-odd-order.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-rules-calls-debhelper-in-odd-order.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: debian-rules-calls-debhelper-in-odd-order +Severity: warning +Check: debian/rules +Info: One of the targets in the debian/rules file for this + package calls debhelper programs in an odd order. Normally, + dh_makeshlibs should be run before dh_shlibdeps or dh_installdeb, and + dh_shlibdeps should be run before dh_gencontrol. dh_builddeb should be + the last debhelper action when building the package, after any of the + other programs mentioned. Calling these programs in the wrong order may + cause incorrect or missing package files and metadata. diff -Nru lintian-2.93.0/tags/d/debian-rules-calls-debhelper-in-odd-order.tag lintian-2.89.0ubuntu1/tags/d/debian-rules-calls-debhelper-in-odd-order.tag --- lintian-2.93.0/tags/d/debian-rules-calls-debhelper-in-odd-order.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-rules-calls-debhelper-in-odd-order.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,10 +0,0 @@ -Tag: debian-rules-calls-debhelper-in-odd-order -Severity: warning -Check: debian/rules -Explanation: One of the targets in the debian/rules file for this - package calls debhelper programs in an odd order. Normally, - dh_makeshlibs should be run before dh_shlibdeps or dh_installdeb, and - dh_shlibdeps should be run before dh_gencontrol. dh_builddeb should be - the last debhelper action when building the package, after any of the - other programs mentioned. Calling these programs in the wrong order may - cause incorrect or missing package files and metadata. diff -Nru lintian-2.93.0/tags/d/debian-rules-calls-pwd.desc lintian-2.89.0ubuntu1/tags/d/debian-rules-calls-pwd.desc --- lintian-2.93.0/tags/d/debian-rules-calls-pwd.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-rules-calls-pwd.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,13 @@ +Tag: debian-rules-calls-pwd +Severity: warning +Check: debian/rules +Renamed-From: debian-rules-should-not-use-pwd +Info: The debian/rules file for this package appears to use the + variable $(PWD) to refer to the current directory. This variable is not + set by GNU make and therefore will have whatever value it has in the + environment, which may not be the actual current directory. Some ways of + building Debian packages (such as through sudo) will clear the PWD + environment variable. + . + Instead of $(PWD), use $(CURDIR), which is set by GNU make, ignores the + environment, and is guaranteed to always be set. diff -Nru lintian-2.93.0/tags/d/debian-rules-calls-pwd.tag lintian-2.89.0ubuntu1/tags/d/debian-rules-calls-pwd.tag --- lintian-2.93.0/tags/d/debian-rules-calls-pwd.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-rules-calls-pwd.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,13 +0,0 @@ -Tag: debian-rules-calls-pwd -Severity: warning -Check: debian/rules -Renamed-From: debian-rules-should-not-use-pwd -Explanation: The debian/rules file for this package appears to use the - variable $(PWD) to refer to the current directory. This variable is not - set by GNU make and therefore will have whatever value it has in the - environment, which may not be the actual current directory. Some ways of - building Debian packages (such as through sudo) will clear the PWD - environment variable. - . - Instead of $(PWD), use $(CURDIR), which is set by GNU make, ignores the - environment, and is guaranteed to always be set. diff -Nru lintian-2.93.0/tags/d/debian-rules-contains-unnecessary-get-orig-source-target.desc lintian-2.89.0ubuntu1/tags/d/debian-rules-contains-unnecessary-get-orig-source-target.desc --- lintian-2.93.0/tags/d/debian-rules-contains-unnecessary-get-orig-source-target.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-rules-contains-unnecessary-get-orig-source-target.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,16 @@ +Tag: debian-rules-contains-unnecessary-get-orig-source-target +Severity: info +Certainty: possible +Check: debian/rules +Info: This package's debian/rules file contains a + get-orig-source target that appears to be unnecessary. For + example, the package might simply contain a single call to uscan(1). + . + Such calls are not ideal; maintainers should be able to call uscan with + their own choice of options and they additionally encourage the + proliferation of boilerplate code across the archive. + . + Since Debian Policy 4.1.4, packages are encouraged to migrate to uscan + and a Files-Excluded header in the debian/copyright + file. +Ref: uscan(1) diff -Nru lintian-2.93.0/tags/d/debian-rules-contains-unnecessary-get-orig-source-target.tag lintian-2.89.0ubuntu1/tags/d/debian-rules-contains-unnecessary-get-orig-source-target.tag --- lintian-2.93.0/tags/d/debian-rules-contains-unnecessary-get-orig-source-target.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-rules-contains-unnecessary-get-orig-source-target.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,15 +0,0 @@ -Tag: debian-rules-contains-unnecessary-get-orig-source-target -Severity: info -Check: debian/rules -Explanation: This package's debian/rules file contains a - get-orig-source target that appears to be unnecessary. For - example, the package might simply contain a single call to uscan(1). - . - Such calls are not ideal; maintainers should be able to call uscan with - their own choice of options and they additionally encourage the - proliferation of boilerplate code across the archive. - . - Since Debian Policy 4.1.4, packages are encouraged to migrate to uscan - and a Files-Excluded header in the debian/copyright - file. -See-Also: uscan(1) diff -Nru lintian-2.93.0/tags/d/debian-rules-ignores-make-clean-error.desc lintian-2.89.0ubuntu1/tags/d/debian-rules-ignores-make-clean-error.desc --- lintian-2.93.0/tags/d/debian-rules-ignores-make-clean-error.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-rules-ignores-make-clean-error.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,19 @@ +Tag: debian-rules-ignores-make-clean-error +Severity: warning +Check: debian/rules +Info: A rule in the debian/rules file for this package calls the + package's clean or distclean target with a line like: + . + -$(MAKE) distclean + or + $(MAKE) -i distclean + . + The leading "-" or the option -i tells make to ignore all errors. + Normally this is done for packages using Autoconf since Makefile may not + exist. However, this line ignores all other error messages, not just + the missing Makefile error. It's better to use: + . + [ ! -f Makefile ] || $(MAKE) distclean + . + so that other error messages from the clean or distclean rule will still + be caught (or just remove the "-" if the package uses a static makefile). diff -Nru lintian-2.93.0/tags/d/debian-rules-ignores-make-clean-error.tag lintian-2.89.0ubuntu1/tags/d/debian-rules-ignores-make-clean-error.tag --- lintian-2.93.0/tags/d/debian-rules-ignores-make-clean-error.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-rules-ignores-make-clean-error.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,19 +0,0 @@ -Tag: debian-rules-ignores-make-clean-error -Severity: warning -Check: debian/rules -Explanation: A rule in the debian/rules file for this package calls the - package's clean or distclean target with a line like: - . - -$(MAKE) distclean - or - $(MAKE) -i distclean - . - The leading "-" or the option -i tells make to ignore all errors. - Normally this is done for packages using Autoconf since Makefile may not - exist. However, this line ignores all other error messages, not just - the missing Makefile error. It's better to use: - . - [ ! -f Makefile ] || $(MAKE) distclean - . - so that other error messages from the clean or distclean rule will still - be caught (or just remove the "-" if the package uses a static makefile). diff -Nru lintian-2.93.0/tags/d/debian-rules-is-dh_make-template.desc lintian-2.89.0ubuntu1/tags/d/debian-rules-is-dh_make-template.desc --- lintian-2.93.0/tags/d/debian-rules-is-dh_make-template.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-rules-is-dh_make-template.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: debian-rules-is-dh_make-template +Severity: error +Check: debian/rules +Info: The debian/rules file appears to be an unmodified or insufficiently + modified copy of the dh_make template. + . + Please double-check the rules file. diff -Nru lintian-2.93.0/tags/d/debian-rules-is-dh_make-template.tag lintian-2.89.0ubuntu1/tags/d/debian-rules-is-dh_make-template.tag --- lintian-2.93.0/tags/d/debian-rules-is-dh_make-template.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-rules-is-dh_make-template.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: debian-rules-is-dh_make-template -Severity: error -Check: debian/rules -Explanation: The debian/rules file appears to be an unmodified or insufficiently - modified copy of the dh_make template. - . - Please double-check the rules file. diff -Nru lintian-2.93.0/tags/d/debian-rules-is-symlink.desc lintian-2.89.0ubuntu1/tags/d/debian-rules-is-symlink.desc --- lintian-2.93.0/tags/d/debian-rules-is-symlink.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-rules-is-symlink.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,11 @@ +Tag: debian-rules-is-symlink +Severity: warning +Check: debian/rules +Info: The file debian/rules is a symlink instead of a regular + file. This is unnecessary and makes package checking and manipulation + more difficult. If the rules file should be available in the source + package under multiple names, make debian/rules the real + file and the other names symlinks to it. + . + This problem may have prevented Lintian from performing other checks, + leading to undetected changelog errors. diff -Nru lintian-2.93.0/tags/d/debian-rules-is-symlink.tag lintian-2.89.0ubuntu1/tags/d/debian-rules-is-symlink.tag --- lintian-2.93.0/tags/d/debian-rules-is-symlink.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-rules-is-symlink.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,11 +0,0 @@ -Tag: debian-rules-is-symlink -Severity: warning -Check: debian/rules -Explanation: The file debian/rules is a symlink instead of a regular - file. This is unnecessary and makes package checking and manipulation - more difficult. If the rules file should be available in the source - package under multiple names, make debian/rules the real - file and the other names symlinks to it. - . - This problem may have prevented Lintian from performing other checks, - leading to undetected changelog errors. diff -Nru lintian-2.93.0/tags/d/debian-rules-missing-recommended-target.desc lintian-2.89.0ubuntu1/tags/d/debian-rules-missing-recommended-target.desc --- lintian-2.93.0/tags/d/debian-rules-missing-recommended-target.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-rules-missing-recommended-target.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,24 @@ +Tag: debian-rules-missing-recommended-target +Severity: warning +Check: debian/rules +Ref: policy 4.9 +Info: The debian/rules file for this package does not provide + one of the recommended targets. All of build-arch and build-indep + should be provided, even if they don't do anything for this package. + If this package does not currently split building of architecture + dependent and independent packages, the following rules may be added + to fall back to the build target: + . + build-arch: build + build-indep: build + . + Note that the following form is recommended however: + . + build: build-arch build-indep + build-arch: build-stamp + build-indep: build-stamp + build-stamp: + build here + . + These targets will be required by policy in the future, so should be + added to prevent future breakage. diff -Nru lintian-2.93.0/tags/d/debian-rules-missing-recommended-target.tag lintian-2.89.0ubuntu1/tags/d/debian-rules-missing-recommended-target.tag --- lintian-2.93.0/tags/d/debian-rules-missing-recommended-target.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-rules-missing-recommended-target.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,24 +0,0 @@ -Tag: debian-rules-missing-recommended-target -Severity: warning -Check: debian/rules -See-Also: policy 4.9 -Explanation: The debian/rules file for this package does not provide - one of the recommended targets. All of build-arch and build-indep - should be provided, even if they don't do anything for this package. - If this package does not currently split building of architecture - dependent and independent packages, the following rules may be added - to fall back to the build target: - . - build-arch: build - build-indep: build - . - Note that the following form is recommended however: - . - build: build-arch build-indep - build-arch: build-stamp - build-indep: build-stamp - build-stamp: - build here - . - These targets will be required by policy in the future, so should be - added to prevent future breakage. diff -Nru lintian-2.93.0/tags/d/debian-rules-missing-required-target.desc lintian-2.89.0ubuntu1/tags/d/debian-rules-missing-required-target.desc --- lintian-2.93.0/tags/d/debian-rules-missing-required-target.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-rules-missing-required-target.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: debian-rules-missing-required-target +Severity: error +Check: debian/rules +Ref: policy 4.9 +Info: The debian/rules file for this package does not provide one + of the required targets. All of build, binary, binary-arch, + binary-indep, and clean must be provided, even if they don't do anything + for this package. diff -Nru lintian-2.93.0/tags/d/debian-rules-missing-required-target.tag lintian-2.89.0ubuntu1/tags/d/debian-rules-missing-required-target.tag --- lintian-2.93.0/tags/d/debian-rules-missing-required-target.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-rules-missing-required-target.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: debian-rules-missing-required-target -Severity: error -Check: debian/rules -See-Also: policy 4.9 -Explanation: The debian/rules file for this package does not provide one - of the required targets. All of build, binary, binary-arch, - binary-indep, and clean must be provided, even if they don't do anything - for this package. diff -Nru lintian-2.93.0/tags/d/debian-rules-not-a-makefile.desc lintian-2.89.0ubuntu1/tags/d/debian-rules-not-a-makefile.desc --- lintian-2.93.0/tags/d/debian-rules-not-a-makefile.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-rules-not-a-makefile.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: debian-rules-not-a-makefile +Severity: error +Check: debian/rules +Ref: policy 4.9 +Info: The debian/rules file for this package does not appear to + be a makefile or does not start with the required line. + debian/rules must be a valid makefile and must have + "#!/usr/bin/make -f" as its first line. diff -Nru lintian-2.93.0/tags/d/debian-rules-not-a-makefile.tag lintian-2.89.0ubuntu1/tags/d/debian-rules-not-a-makefile.tag --- lintian-2.93.0/tags/d/debian-rules-not-a-makefile.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-rules-not-a-makefile.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: debian-rules-not-a-makefile -Severity: error -Check: debian/rules -See-Also: policy 4.9 -Explanation: The debian/rules file for this package does not appear to - be a makefile or does not start with the required line. - debian/rules must be a valid makefile and must have - "#!/usr/bin/make -f" as its first line. diff -Nru lintian-2.93.0/tags/d/debian-rules-not-executable.desc lintian-2.89.0ubuntu1/tags/d/debian-rules-not-executable.desc --- lintian-2.93.0/tags/d/debian-rules-not-executable.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-rules-not-executable.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: debian-rules-not-executable +Severity: pedantic +Ref: policy 4.9 +Check: debian/rules +Info: The debian/rules file for this package does not appear to + be marked as executable and should be changed via chmod +x or + similar. diff -Nru lintian-2.93.0/tags/d/debian-rules-not-executable.tag lintian-2.89.0ubuntu1/tags/d/debian-rules-not-executable.tag --- lintian-2.93.0/tags/d/debian-rules-not-executable.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-rules-not-executable.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: debian-rules-not-executable -Severity: pedantic -See-Also: policy 4.9 -Check: debian/rules -Explanation: The debian/rules file for this package does not appear to - be marked as executable and should be changed via chmod +x or - similar. diff -Nru lintian-2.93.0/tags/d/debian-rules-parses-dpkg-parsechangelog.desc lintian-2.89.0ubuntu1/tags/d/debian-rules-parses-dpkg-parsechangelog.desc --- lintian-2.93.0/tags/d/debian-rules-parses-dpkg-parsechangelog.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-rules-parses-dpkg-parsechangelog.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,13 @@ +Tag: debian-rules-parses-dpkg-parsechangelog +Severity: info +Certainty: possible +Check: debian/rules +Info: The rules file appears to be parsing the output of dpkg-parsechangelog to + determine the current package version name, version, or timestamp, etc. + . + Since dpkg 1.16.1, this could be replaced by including the + /usr/share/dpkg/pkg-info.mk Makefile library and using the + DEB_{SOURCE,VERSION} or SOURCE_DATE_EPOCH variables. + . + Using this library is not only cleaner and more efficient, it handles many + corner-cases such as binNMUs, epoch versions, etc. diff -Nru lintian-2.93.0/tags/d/debian-rules-parses-dpkg-parsechangelog.tag lintian-2.89.0ubuntu1/tags/d/debian-rules-parses-dpkg-parsechangelog.tag --- lintian-2.93.0/tags/d/debian-rules-parses-dpkg-parsechangelog.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-rules-parses-dpkg-parsechangelog.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,12 +0,0 @@ -Tag: debian-rules-parses-dpkg-parsechangelog -Severity: info -Check: debian/rules -Explanation: The rules file appears to be parsing the output of dpkg-parsechangelog to - determine the current package version name, version, or timestamp, etc. - . - Since dpkg 1.16.1, this could be replaced by including the - /usr/share/dpkg/pkg-info.mk Makefile library and using the - DEB_{SOURCE,VERSION} or SOURCE_DATE_EPOCH variables. - . - Using this library is not only cleaner and more efficient, it handles many - corner-cases such as binNMUs, epoch versions, etc. diff -Nru lintian-2.93.0/tags/d/debian-rules-passes-version-info-to-dh_shlibdeps.desc lintian-2.89.0ubuntu1/tags/d/debian-rules-passes-version-info-to-dh_shlibdeps.desc --- lintian-2.93.0/tags/d/debian-rules-passes-version-info-to-dh_shlibdeps.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-rules-passes-version-info-to-dh_shlibdeps.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,11 @@ +Tag: debian-rules-passes-version-info-to-dh_shlibdeps +Severity: warning +Certainty: possible +Check: debian/rules +Info: The debian/rules file for this package has a call to + dh_shlibdeps(1) with the --version-info or + -V option. + . + However, this has no effect on dh_shlibdeps; you probably + wanted to pass this option to dh_makeshlibs(1) instead. +Ref: dh_shlibdeps(1), dh_makeshlibs(1) diff -Nru lintian-2.93.0/tags/d/debian-rules-passes-version-info-to-dh_shlibdeps.tag lintian-2.89.0ubuntu1/tags/d/debian-rules-passes-version-info-to-dh_shlibdeps.tag --- lintian-2.93.0/tags/d/debian-rules-passes-version-info-to-dh_shlibdeps.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-rules-passes-version-info-to-dh_shlibdeps.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,10 +0,0 @@ -Tag: debian-rules-passes-version-info-to-dh_shlibdeps -Severity: warning -Check: debian/rules -Explanation: The debian/rules file for this package has a call to - dh_shlibdeps(1) with the --version-info or - -V option. - . - However, this has no effect on dh_shlibdeps; you probably - wanted to pass this option to dh_makeshlibs(1) instead. -See-Also: dh_shlibdeps(1), dh_makeshlibs(1) diff -Nru lintian-2.93.0/tags/d/debian-rules-sets-DEB_BUILD_OPTIONS.desc lintian-2.89.0ubuntu1/tags/d/debian-rules-sets-DEB_BUILD_OPTIONS.desc --- lintian-2.93.0/tags/d/debian-rules-sets-DEB_BUILD_OPTIONS.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-rules-sets-DEB_BUILD_OPTIONS.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: debian-rules-sets-DEB_BUILD_OPTIONS +Severity: warning +Check: debian/rules +Ref: dpkg-buildflags(1) +Info: The debian/rules file sets the DEB_BUILD_OPTIONS variable, + which will override any user-specified build profile. + . + Please replace with DEB_BUILD_MAINT_OPTIONS. diff -Nru lintian-2.93.0/tags/d/debian-rules-sets-DEB_BUILD_OPTIONS.tag lintian-2.89.0ubuntu1/tags/d/debian-rules-sets-DEB_BUILD_OPTIONS.tag --- lintian-2.93.0/tags/d/debian-rules-sets-DEB_BUILD_OPTIONS.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-rules-sets-DEB_BUILD_OPTIONS.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: debian-rules-sets-DEB_BUILD_OPTIONS -Severity: warning -Check: debian/rules -See-Also: dpkg-buildflags(1) -Explanation: The debian/rules file sets the DEB_BUILD_OPTIONS variable, - which will override any user-specified build profile. - . - Please replace with DEB_BUILD_MAINT_OPTIONS. diff -Nru lintian-2.93.0/tags/d/debian-rules-sets-DH_COMPAT.desc lintian-2.89.0ubuntu1/tags/d/debian-rules-sets-DH_COMPAT.desc --- lintian-2.93.0/tags/d/debian-rules-sets-DH_COMPAT.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-rules-sets-DH_COMPAT.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: debian-rules-sets-DH_COMPAT +Severity: warning +Check: debian/rules +Ref: debhelper(7) +Info: As of debhelper version 4, the DH_COMPAT environment variable is + only to be used for temporarily overriding debian/compat. Any + line in debian/rules that sets it globally should be deleted and + a separate debian/compat file created if needed. diff -Nru lintian-2.93.0/tags/d/debian-rules-sets-DH_COMPAT.tag lintian-2.89.0ubuntu1/tags/d/debian-rules-sets-DH_COMPAT.tag --- lintian-2.93.0/tags/d/debian-rules-sets-DH_COMPAT.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-rules-sets-DH_COMPAT.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: debian-rules-sets-DH_COMPAT -Severity: warning -Check: debian/rules -See-Also: debhelper(7) -Explanation: As of debhelper version 4, the DH_COMPAT environment variable is - only to be used for temporarily overriding debian/compat. Any - line in debian/rules that sets it globally should be deleted and - a separate debian/compat file created if needed. diff -Nru lintian-2.93.0/tags/d/debian-rules-sets-dpkg-architecture-variable.desc lintian-2.89.0ubuntu1/tags/d/debian-rules-sets-dpkg-architecture-variable.desc --- lintian-2.93.0/tags/d/debian-rules-sets-dpkg-architecture-variable.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-rules-sets-dpkg-architecture-variable.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,16 @@ +Tag: debian-rules-sets-dpkg-architecture-variable +Severity: warning +Check: debian/rules +Ref: dpkg-architecture(1) +Info: The debian/rules file sets one or more + dpkg-architecture variables such as DEB_BUILD_ARCH. + . + These variables are pre-initialized in the environment when running under + dpkg-buildpackage - avoiding these assignments can reduce package + build time. + . + Please use: + . + include /usr/share/dpkg/architecture.mk + . + instead, or replace the assignment operator with ?=. diff -Nru lintian-2.93.0/tags/d/debian-rules-sets-dpkg-architecture-variable.tag lintian-2.89.0ubuntu1/tags/d/debian-rules-sets-dpkg-architecture-variable.tag --- lintian-2.93.0/tags/d/debian-rules-sets-dpkg-architecture-variable.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-rules-sets-dpkg-architecture-variable.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,16 +0,0 @@ -Tag: debian-rules-sets-dpkg-architecture-variable -Severity: warning -Check: debian/rules -See-Also: dpkg-architecture(1) -Explanation: The debian/rules file sets one or more - dpkg-architecture variables such as DEB_BUILD_ARCH. - . - These variables are pre-initialized in the environment when running under - dpkg-buildpackage - avoiding these assignments can reduce package - build time. - . - Please use: - . - include /usr/share/dpkg/architecture.mk - . - instead, or replace the assignment operator with ?=. diff -Nru lintian-2.93.0/tags/d/debian-rules-should-not-set-CFLAGS-from-noopt.desc lintian-2.89.0ubuntu1/tags/d/debian-rules-should-not-set-CFLAGS-from-noopt.desc --- lintian-2.93.0/tags/d/debian-rules-should-not-set-CFLAGS-from-noopt.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-rules-should-not-set-CFLAGS-from-noopt.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: debian-rules-should-not-set-CFLAGS-from-noopt +Severity: warning +Check: debian/rules +Ref: dpkg-buildflags(1) +Info: The debian/rules file for this package appears to set + CFLAGS if the value of DEB_BUILD_OPTIONS contains + noopt. + . + This has been obsoleted in favour of dpkg-buildflags. diff -Nru lintian-2.93.0/tags/d/debian-rules-should-not-set-CFLAGS-from-noopt.tag lintian-2.89.0ubuntu1/tags/d/debian-rules-should-not-set-CFLAGS-from-noopt.tag --- lintian-2.93.0/tags/d/debian-rules-should-not-set-CFLAGS-from-noopt.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-rules-should-not-set-CFLAGS-from-noopt.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: debian-rules-should-not-set-CFLAGS-from-noopt -Severity: warning -Check: debian/rules -See-Also: dpkg-buildflags(1) -Explanation: The debian/rules file for this package appears to set - CFLAGS if the value of DEB_BUILD_OPTIONS contains - noopt. - . - This has been obsoleted in favour of dpkg-buildflags. diff -Nru lintian-2.93.0/tags/d/debian-rules-should-not-use-DH_EXTRA_ADDONS.desc lintian-2.89.0ubuntu1/tags/d/debian-rules-should-not-use-DH_EXTRA_ADDONS.desc --- lintian-2.93.0/tags/d/debian-rules-should-not-use-DH_EXTRA_ADDONS.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-rules-should-not-use-DH_EXTRA_ADDONS.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: debian-rules-should-not-use-DH_EXTRA_ADDONS +Severity: warning +Check: debian/rules +Info: The DH_EXTRA_ADDONS variable is designed for local or downstream build + use and not for use in debian/rules + . + dh(1)'s --with should be used instead. diff -Nru lintian-2.93.0/tags/d/debian-rules-should-not-use-DH_EXTRA_ADDONS.tag lintian-2.89.0ubuntu1/tags/d/debian-rules-should-not-use-DH_EXTRA_ADDONS.tag --- lintian-2.93.0/tags/d/debian-rules-should-not-use-DH_EXTRA_ADDONS.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-rules-should-not-use-DH_EXTRA_ADDONS.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: debian-rules-should-not-use-DH_EXTRA_ADDONS -Severity: warning -Check: debian/rules -Explanation: The DH_EXTRA_ADDONS variable is designed for local or downstream build - use and not for use in debian/rules - . - dh(1)'s --with should be used instead. diff -Nru lintian-2.93.0/tags/d/debian-rules-should-not-use-sanitize-all-buildflag.desc lintian-2.89.0ubuntu1/tags/d/debian-rules-should-not-use-sanitize-all-buildflag.desc --- lintian-2.93.0/tags/d/debian-rules-should-not-use-sanitize-all-buildflag.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-rules-should-not-use-sanitize-all-buildflag.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,17 @@ +Tag: debian-rules-should-not-use-sanitize-all-buildflag +Severity: error +Check: debian/rules +Info: This package's debian/rules file contains a + DEB_BUILD_MAINT_OPTIONS assignment that enables the + sanitize=+all build flag. + . + This option instructs the compiler to enable options designed to + protect the binary against memory corruptions, memory leaks, use after + free, threading data races, and undefined behavior bugs. + . + However, this options should not be used for production Debian binaries + as they can reduce reliability for conformant code, reduce security or + even functionality. + . + Please remove the reference to sanitize=+all. +Ref: dpkg-buildflags(1), #895811 diff -Nru lintian-2.93.0/tags/d/debian-rules-should-not-use-sanitize-all-buildflag.tag lintian-2.89.0ubuntu1/tags/d/debian-rules-should-not-use-sanitize-all-buildflag.tag --- lintian-2.93.0/tags/d/debian-rules-should-not-use-sanitize-all-buildflag.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-rules-should-not-use-sanitize-all-buildflag.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,17 +0,0 @@ -Tag: debian-rules-should-not-use-sanitize-all-buildflag -Severity: error -Check: debian/rules -Explanation: This package's debian/rules file contains a - DEB_BUILD_MAINT_OPTIONS assignment that enables the - sanitize=+all build flag. - . - This option instructs the compiler to enable options designed to - protect the binary against memory corruptions, memory leaks, use after - free, threading data races, and undefined behavior bugs. - . - However, this options should not be used for production Debian binaries - as they can reduce reliability for conformant code, reduce security or - even functionality. - . - Please remove the reference to sanitize=+all. -See-Also: dpkg-buildflags(1), Bug#895811 diff -Nru lintian-2.93.0/tags/d/debian-rules-updates-control-automatically.desc lintian-2.89.0ubuntu1/tags/d/debian-rules-updates-control-automatically.desc --- lintian-2.93.0/tags/d/debian-rules-updates-control-automatically.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-rules-updates-control-automatically.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: debian-rules-updates-control-automatically +Severity: error +Certainty: possible +Check: debian/rules +Renamed-From: debian-rules-should-not-automatically-update-control +Info: DEB_AUTO_UPDATE_DEBIAN_CONTROL appears to be set to yes in + the debian/rules file. This activates a feature of CDBS which + may not be used in packages uploaded to the Debian archive. +Ref: https://ftp-master.debian.org/REJECT-FAQ.html diff -Nru lintian-2.93.0/tags/d/debian-rules-updates-control-automatically.tag lintian-2.89.0ubuntu1/tags/d/debian-rules-updates-control-automatically.tag --- lintian-2.93.0/tags/d/debian-rules-updates-control-automatically.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-rules-updates-control-automatically.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: debian-rules-updates-control-automatically -Severity: error -Check: debian/rules -Renamed-From: debian-rules-should-not-automatically-update-control -Explanation: DEB_AUTO_UPDATE_DEBIAN_CONTROL - appears to be set to yes in - the debian/rules file. This activates a feature of CDBS which - may not be used in packages uploaded to the Debian archive. -See-Also: https://ftp-master.debian.org/REJECT-FAQ.html diff -Nru lintian-2.93.0/tags/d/debian-rules-uses-as-needed-linker-flag.desc lintian-2.89.0ubuntu1/tags/d/debian-rules-uses-as-needed-linker-flag.desc --- lintian-2.93.0/tags/d/debian-rules-uses-as-needed-linker-flag.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-rules-uses-as-needed-linker-flag.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,15 @@ +Tag: debian-rules-uses-as-needed-linker-flag +Severity: pedantic +Experimental: yes +Check: debian/rules +Info: The debian/rules file for this package uses the + -Wl,--as-needed linker flag. + . + The bullseye toolchain defaults to linking with --as-needed and + therefore it should no longer be necessary to inject this into the + build process. + . + However, it is not safe to make this change if the package will target + the buster distribution such as via backports to the buster-bpo / + stable-bpo distribution or, during the bookworm cycle itself, the + oldstable-bpo distribution. diff -Nru lintian-2.93.0/tags/d/debian-rules-uses-as-needed-linker-flag.tag lintian-2.89.0ubuntu1/tags/d/debian-rules-uses-as-needed-linker-flag.tag --- lintian-2.93.0/tags/d/debian-rules-uses-as-needed-linker-flag.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-rules-uses-as-needed-linker-flag.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,15 +0,0 @@ -Tag: debian-rules-uses-as-needed-linker-flag -Severity: pedantic -Experimental: yes -Check: debian/rules -Explanation: The debian/rules file for this package uses the - -Wl,--as-needed linker flag. - . - The bullseye toolchain defaults to linking with --as-needed and - therefore it should no longer be necessary to inject this into the - build process. - . - However, it is not safe to make this change if the package will target - the buster distribution such as via backports to the buster-bpo / - stable-bpo distribution or, during the bookworm cycle itself, the - oldstable-bpo distribution. diff -Nru lintian-2.93.0/tags/d/debian-rules-uses-deb-build-opts.desc lintian-2.89.0ubuntu1/tags/d/debian-rules-uses-deb-build-opts.desc --- lintian-2.93.0/tags/d/debian-rules-uses-deb-build-opts.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-rules-uses-deb-build-opts.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: debian-rules-uses-deb-build-opts +Severity: warning +Check: debian/rules +Renamed-From: debian-rules-should-not-use-DEB_BUILD_OPTS +Info: The standard environment variable for build options is + DEB_BUILD_OPTIONS. Usually, referring to DEB_BUILD_OPTS is a mistake and + DEB_BUILD_OPTIONS was intended instead. diff -Nru lintian-2.93.0/tags/d/debian-rules-uses-deb-build-opts.tag lintian-2.89.0ubuntu1/tags/d/debian-rules-uses-deb-build-opts.tag --- lintian-2.93.0/tags/d/debian-rules-uses-deb-build-opts.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-rules-uses-deb-build-opts.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: debian-rules-uses-deb-build-opts -Severity: warning -Check: debian/rules -Renamed-From: debian-rules-should-not-use-DEB_BUILD_OPTS -Explanation: The standard environment variable for build options is - DEB_BUILD_OPTIONS. Usually, referring to DEB_BUILD_OPTS is a mistake and - DEB_BUILD_OPTIONS was intended instead. diff -Nru lintian-2.93.0/tags/d/debian-rules-uses-deprecated-makefile.desc lintian-2.89.0ubuntu1/tags/d/debian-rules-uses-deprecated-makefile.desc --- lintian-2.93.0/tags/d/debian-rules-uses-deprecated-makefile.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-rules-uses-deprecated-makefile.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: debian-rules-uses-deprecated-makefile +Severity: warning +Check: debian/rules +Info: The debian/rules file for this package appears to + include a Makefile that has been deprecated. Please refer to the + documentation of the providing package for a replacement (if any). diff -Nru lintian-2.93.0/tags/d/debian-rules-uses-deprecated-makefile.tag lintian-2.89.0ubuntu1/tags/d/debian-rules-uses-deprecated-makefile.tag --- lintian-2.93.0/tags/d/debian-rules-uses-deprecated-makefile.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-rules-uses-deprecated-makefile.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: debian-rules-uses-deprecated-makefile -Severity: warning -Check: debian/rules -Explanation: The debian/rules file for this package appears to - include a Makefile that has been deprecated. Please refer to the - documentation of the providing package for a replacement (if any). diff -Nru lintian-2.93.0/tags/d/debian-rules-uses-deprecated-systemd-override.desc lintian-2.89.0ubuntu1/tags/d/debian-rules-uses-deprecated-systemd-override.desc --- lintian-2.93.0/tags/d/debian-rules-uses-deprecated-systemd-override.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-rules-uses-deprecated-systemd-override.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,13 @@ +Tag: debian-rules-uses-deprecated-systemd-override +Severity: error +Check: debhelper +Info: The debian/rules file for this package has an + override_dh_systemd_enable or override_dh_systemd_start + target but the package uses debhelper compatibility level 11. + . + The dh_systemd_{enable,start} commands were deprecated in this + compat level and are no longer called. This is likely to cause your + package to not function as intended. + . + Please replace these with calls to dh_installsystemd. +Ref: debhelper(7) diff -Nru lintian-2.93.0/tags/d/debian-rules-uses-deprecated-systemd-override.tag lintian-2.89.0ubuntu1/tags/d/debian-rules-uses-deprecated-systemd-override.tag --- lintian-2.93.0/tags/d/debian-rules-uses-deprecated-systemd-override.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-rules-uses-deprecated-systemd-override.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,14 +0,0 @@ -Tag: debian-rules-uses-deprecated-systemd-override -Severity: error -Check: debhelper -Explanation: The debian/rules file for this package has an - override_dh_systemd_enable or - override_dh_systemd_start - target but the package uses debhelper compatibility level 11. - . - The dh_systemd_{enable,start} commands were deprecated in this - compat level and are no longer called. This is likely to cause your - package to not function as intended. - . - Please replace these with calls to dh_installsystemd. -See-Also: debhelper(7) diff -Nru lintian-2.93.0/tags/d/debian-rules-uses-installed-python-versions.desc lintian-2.89.0ubuntu1/tags/d/debian-rules-uses-installed-python-versions.desc --- lintian-2.93.0/tags/d/debian-rules-uses-installed-python-versions.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-rules-uses-installed-python-versions.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,17 @@ +Tag: debian-rules-uses-installed-python-versions +Severity: warning +Check: debian/rules +Info: The package appears to use py3versions -i to determine + the "installed" Python versions. + . + However, this can cause issues if a Python transition is in progress + as the -minimal variant of the previous version + (eg. python3.X-minimal) remains installed in many environments. + This variant then provides enough of an interpreter to count as being + "installed" but not enough for the tests themselves to succeed in most + cases. This then prevents the overall transition from taking place. + . + Please replace this will a call to all "supported" packages instead + (eg. py3versions -s and ensure python3-all is listed + in the build dependencies. +Ref: https://lists.debian.org/debian-devel/2020/03/msg00280.html diff -Nru lintian-2.93.0/tags/d/debian-rules-uses-installed-python-versions.tag lintian-2.89.0ubuntu1/tags/d/debian-rules-uses-installed-python-versions.tag --- lintian-2.93.0/tags/d/debian-rules-uses-installed-python-versions.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-rules-uses-installed-python-versions.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,17 +0,0 @@ -Tag: debian-rules-uses-installed-python-versions -Severity: warning -Check: debian/rules -Explanation: The package appears to use py3versions -i to determine - the "installed" Python versions. - . - However, this can cause issues if a Python transition is in progress - as the -minimal variant of the previous version - (eg. python3.X-minimal) remains installed in many environments. - This variant then provides enough of an interpreter to count as being - "installed" but not enough for the tests themselves to succeed in most - cases. This then prevents the overall transition from taking place. - . - Please replace this will a call to all "supported" packages instead - (eg. py3versions -s and ensure python3-all is listed - in the build dependencies. -See-Also: https://lists.debian.org/debian-devel/2020/03/msg00280.html diff -Nru lintian-2.93.0/tags/d/debian-rules-uses-special-shell-variable.desc lintian-2.89.0ubuntu1/tags/d/debian-rules-uses-special-shell-variable.desc --- lintian-2.93.0/tags/d/debian-rules-uses-special-shell-variable.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-rules-uses-special-shell-variable.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,16 @@ +Tag: debian-rules-uses-special-shell-variable +Severity: warning +Certainty: possible +Check: debian/rules +Renamed-From: debian-rules-should-not-use-underscore-variable +Ref: policy 4.9, https://stackoverflow.com/a/27628164 +Info: The rules file use the make variable $(_). + . + According to Policy 4.9, 'invoking either of make -f debian/rules + <...> or ./debian/rules + <args...>' must result in identical behavior'. + One way to inadvertently violate this policy is to use the $_ variable. + . + If the rules file uses $(dir $(_)) to discover the directory containing + the source package (presumably in order to implement the get-orig-source + target), please replace it by $(dir $(firstword $(MAKEFILE_LIST))). diff -Nru lintian-2.93.0/tags/d/debian-rules-uses-special-shell-variable.tag lintian-2.89.0ubuntu1/tags/d/debian-rules-uses-special-shell-variable.tag --- lintian-2.93.0/tags/d/debian-rules-uses-special-shell-variable.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-rules-uses-special-shell-variable.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,15 +0,0 @@ -Tag: debian-rules-uses-special-shell-variable -Severity: warning -Check: debian/rules -Renamed-From: debian-rules-should-not-use-underscore-variable -See-Also: policy 4.9, https://stackoverflow.com/a/27628164 -Explanation: The rules file use the make variable $(_). - . - According to Policy 4.9, 'invoking either of make -f debian/rules - <...> or ./debian/rules - <args...>' must result in identical behavior'. - One way to inadvertently violate this policy is to use the $_ variable. - . - If the rules file uses $(dir $(_)) to discover the directory containing - the source package (presumably in order to implement the get-orig-source - target), please replace it by $(dir $(firstword $(MAKEFILE_LIST))). diff -Nru lintian-2.93.0/tags/d/debian-rules-uses-supported-python-versions-without-python-all-build-depends.desc lintian-2.89.0ubuntu1/tags/d/debian-rules-uses-supported-python-versions-without-python-all-build-depends.desc --- lintian-2.93.0/tags/d/debian-rules-uses-supported-python-versions-without-python-all-build-depends.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-rules-uses-supported-python-versions-without-python-all-build-depends.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,12 @@ +Tag: debian-rules-uses-supported-python-versions-without-python-all-build-depends +Severity: warning +Check: debian/rules +Info: The package appears to use py3versions -s to determine + the "supported" Python versions without specifying python3-all + as a build-dependency. + . + With only the default version of Python installed, the package may + build and test successfully but subsequently fail at runtime when + another, non-default, Python version is present. + . + Please add python3-all as a build-dependency. diff -Nru lintian-2.93.0/tags/d/debian-rules-uses-supported-python-versions-without-python-all-build-depends.tag lintian-2.89.0ubuntu1/tags/d/debian-rules-uses-supported-python-versions-without-python-all-build-depends.tag --- lintian-2.93.0/tags/d/debian-rules-uses-supported-python-versions-without-python-all-build-depends.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-rules-uses-supported-python-versions-without-python-all-build-depends.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,12 +0,0 @@ -Tag: debian-rules-uses-supported-python-versions-without-python-all-build-depends -Severity: warning -Check: debian/rules -Explanation: The package appears to use py3versions -s to determine - the "supported" Python versions without specifying python3-all - as a build-dependency. - . - With only the default version of Python installed, the package may - build and test successfully but subsequently fail at runtime when - another, non-default, Python version is present. - . - Please add python3-all as a build-dependency. diff -Nru lintian-2.93.0/tags/d/debian-rules-uses-unnecessary-dh-argument.desc lintian-2.89.0ubuntu1/tags/d/debian-rules-uses-unnecessary-dh-argument.desc --- lintian-2.93.0/tags/d/debian-rules-uses-unnecessary-dh-argument.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-rules-uses-unnecessary-dh-argument.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: debian-rules-uses-unnecessary-dh-argument +Severity: warning +Check: debhelper +Info: The debian/rules file passes the specified argument to + dh $@ but it is enabled by default from this debhelper + compatibility level onwards. + . + Please remove the argument from the call to dh(1). +Ref: debhelper(7), dh(1) diff -Nru lintian-2.93.0/tags/d/debian-rules-uses-unnecessary-dh-argument.tag lintian-2.89.0ubuntu1/tags/d/debian-rules-uses-unnecessary-dh-argument.tag --- lintian-2.93.0/tags/d/debian-rules-uses-unnecessary-dh-argument.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-rules-uses-unnecessary-dh-argument.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: debian-rules-uses-unnecessary-dh-argument -Severity: warning -Check: debhelper -Explanation: The debian/rules file passes the specified argument to - dh $@ but it is enabled by default from this debhelper - compatibility level onwards. - . - Please remove the argument from the call to dh(1). -See-Also: debhelper(7), dh(1) diff -Nru lintian-2.93.0/tags/d/debian-rules-uses-wrong-environment-variable.desc lintian-2.89.0ubuntu1/tags/d/debian-rules-uses-wrong-environment-variable.desc --- lintian-2.93.0/tags/d/debian-rules-uses-wrong-environment-variable.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-rules-uses-wrong-environment-variable.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,14 @@ +Tag: debian-rules-uses-wrong-environment-variable +Severity: warning +Certainty: possible +Check: debian/rules +Renamed-From: debian-rules-should-not-use-or-modify-user-only-variable +Ref: #631786 +Info: The rules file appears to be reading or modifying a variable not + intended for use by package maintainers. + . + The special variables DEB_*FLAGS_{SET,APPEND} can be used by + users who want to re-compile Debian packages with special (or + non-standard) build flags. + . + Please use the DEB_*FLAGS_MAINT_{SET,APPEND} flags instead. diff -Nru lintian-2.93.0/tags/d/debian-rules-uses-wrong-environment-variable.tag lintian-2.89.0ubuntu1/tags/d/debian-rules-uses-wrong-environment-variable.tag --- lintian-2.93.0/tags/d/debian-rules-uses-wrong-environment-variable.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-rules-uses-wrong-environment-variable.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,13 +0,0 @@ -Tag: debian-rules-uses-wrong-environment-variable -Severity: warning -Check: debian/rules -Renamed-From: debian-rules-should-not-use-or-modify-user-only-variable -See-Also: Bug#631786 -Explanation: The rules file appears to be reading or modifying a variable not - intended for use by package maintainers. - . - The special variables DEB_*FLAGS_{SET,APPEND} can be used by - users who want to re-compile Debian packages with special (or - non-standard) build flags. - . - Please use the DEB_*FLAGS_MAINT_{SET,APPEND} flags instead. diff -Nru lintian-2.93.0/tags/d/debian-tests-control-and-control-autodep8.desc lintian-2.89.0ubuntu1/tags/d/debian-tests-control-and-control-autodep8.desc --- lintian-2.93.0/tags/d/debian-tests-control-and-control-autodep8.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-tests-control-and-control-autodep8.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: debian-tests-control-and-control-autodep8 +Severity: info +Check: testsuite +Info: This package has both a debian/tests/control and a + debian/tests/control.autodep8 file. Please merge the contents and + remove the latter one. diff -Nru lintian-2.93.0/tags/d/debian-tests-control-and-control-autodep8.tag lintian-2.89.0ubuntu1/tags/d/debian-tests-control-and-control-autodep8.tag --- lintian-2.93.0/tags/d/debian-tests-control-and-control-autodep8.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-tests-control-and-control-autodep8.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: debian-tests-control-and-control-autodep8 -Severity: info -Check: testsuite -Explanation: This package has both a debian/tests/control and a - debian/tests/control.autodep8 file. Please merge the contents and - remove the latter one. diff -Nru lintian-2.93.0/tags/d/debian-tests-control-autodep8-is-obsolete.desc lintian-2.89.0ubuntu1/tags/d/debian-tests-control-autodep8-is-obsolete.desc --- lintian-2.93.0/tags/d/debian-tests-control-autodep8-is-obsolete.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-tests-control-autodep8-is-obsolete.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,21 @@ +Tag: debian-tests-control-autodep8-is-obsolete +Severity: warning +Check: testsuite +Ref: autodep8(1) +Info: The specified autopkgtest control file is considered obsolete. + . + Before autodep8 version 0.17 and autopkgtest version 5.7 if a + maintainer wished to add tests to the set of tests generated + by autodep8 they provided those tests in a file named + debian/tests/control.autodep8. + . + It is now prefered to declare the additional tests in the regular + debian/tests/control file so that dpkg-source can + pick up the test dependencies. + . + When configured to run autodep8 tests, autopkgtest will run the + additional tests and the autodep8 tests when debian/control + has the proper Testsuite: autopkgtest-* in the source + headers. + . + Please merge the specified file into debian/tests/control. diff -Nru lintian-2.93.0/tags/d/debian-tests-control-autodep8-is-obsolete.tag lintian-2.89.0ubuntu1/tags/d/debian-tests-control-autodep8-is-obsolete.tag --- lintian-2.93.0/tags/d/debian-tests-control-autodep8-is-obsolete.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-tests-control-autodep8-is-obsolete.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,21 +0,0 @@ -Tag: debian-tests-control-autodep8-is-obsolete -Severity: warning -Check: testsuite -See-Also: autodep8(1) -Explanation: The specified autopkgtest control file is considered obsolete. - . - Before autodep8 version 0.17 and autopkgtest version 5.7 if a - maintainer wished to add tests to the set of tests generated - by autodep8 they provided those tests in a file named - debian/tests/control.autodep8. - . - It is now prefered to declare the additional tests in the regular - debian/tests/control file so that dpkg-source can - pick up the test dependencies. - . - When configured to run autodep8 tests, autopkgtest will run the - additional tests and the autodep8 tests when debian/control - has the proper Testsuite: autopkgtest-* in the source - headers. - . - Please merge the specified file into debian/tests/control. diff -Nru lintian-2.93.0/tags/d/debian-upstream-obsolete-path.desc lintian-2.89.0ubuntu1/tags/d/debian-upstream-obsolete-path.desc --- lintian-2.93.0/tags/d/debian-upstream-obsolete-path.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-upstream-obsolete-path.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,15 @@ +Tag: debian-upstream-obsolete-path +Severity: error +Check: cruft +Info: Upstream metadata is stored under an obsolete path. + . + Upstream MEtadata GAthered with YAml (UMEGAYA) is an effort to collect + meta-information about upstream projects from any source package + with a publicly accessible VCS via a file called + debian/upstream/metadata. + . + Older versions of this specification used + debian/upstream-metadata.yaml or debian/upstream + as meta-information storage file. + . + You should move any such file to debian/upstream/metadata. diff -Nru lintian-2.93.0/tags/d/debian-upstream-obsolete-path.tag lintian-2.89.0ubuntu1/tags/d/debian-upstream-obsolete-path.tag --- lintian-2.93.0/tags/d/debian-upstream-obsolete-path.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-upstream-obsolete-path.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,15 +0,0 @@ -Tag: debian-upstream-obsolete-path -Severity: error -Check: cruft -Explanation: Upstream metadata is stored under an obsolete path. - . - Upstream MEtadata GAthered with YAml (UMEGAYA) is an effort to collect - meta-information about upstream projects from any source package - with a publicly accessible VCS via a file called - debian/upstream/metadata. - . - Older versions of this specification used - debian/upstream-metadata.yaml or debian/upstream - as meta-information storage file. - . - You should move any such file to debian/upstream/metadata. diff -Nru lintian-2.93.0/tags/d/debian-watch-contains-dh_make-template.desc lintian-2.89.0ubuntu1/tags/d/debian-watch-contains-dh_make-template.desc --- lintian-2.93.0/tags/d/debian-watch-contains-dh_make-template.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-watch-contains-dh_make-template.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,5 @@ +Tag: debian-watch-contains-dh_make-template +Severity: info +Check: debian/watch +Info: The watch file contains a standard template included by dh_make. + Please remove them once you have implemented the watch file. diff -Nru lintian-2.93.0/tags/d/debian-watch-contains-dh_make-template.tag lintian-2.89.0ubuntu1/tags/d/debian-watch-contains-dh_make-template.tag --- lintian-2.93.0/tags/d/debian-watch-contains-dh_make-template.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-watch-contains-dh_make-template.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,5 +0,0 @@ -Tag: debian-watch-contains-dh_make-template -Severity: info -Check: debian/watch -Explanation: The watch file contains a standard template included by dh_make. - Please remove them once you have implemented the watch file. diff -Nru lintian-2.93.0/tags/d/debian-watch-could-verify-download.desc lintian-2.89.0ubuntu1/tags/d/debian-watch-could-verify-download.desc --- lintian-2.93.0/tags/d/debian-watch-could-verify-download.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-watch-could-verify-download.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: debian-watch-could-verify-download +Severity: warning +Check: debian/watch +Ref: uscan(1) +Info: One or more upstream signing keys are present in the Debian package + but are not being used. + . + Please enable the cryptographic verification of downloads with the + "pgpsigurlmangle" option in your watch file or remove the key. diff -Nru lintian-2.93.0/tags/d/debian-watch-could-verify-download.tag lintian-2.89.0ubuntu1/tags/d/debian-watch-could-verify-download.tag --- lintian-2.93.0/tags/d/debian-watch-could-verify-download.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-watch-could-verify-download.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: debian-watch-could-verify-download -Severity: warning -Check: debian/watch -See-Also: uscan(1) -Explanation: One or more upstream signing keys are present in the Debian package - but are not being used. - . - Please enable the cryptographic verification of downloads with the - "pgpsigurlmangle" option in your watch file or remove the key. diff -Nru lintian-2.93.0/tags/d/debian-watch-does-not-check-gpg-signature.desc lintian-2.89.0ubuntu1/tags/d/debian-watch-does-not-check-gpg-signature.desc --- lintian-2.93.0/tags/d/debian-watch-does-not-check-gpg-signature.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-watch-does-not-check-gpg-signature.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,20 @@ +Tag: debian-watch-does-not-check-gpg-signature +Severity: pedantic +Check: debian/watch +Experimental: yes +Ref: uscan(1) +Info: This watch file does not specify a means to verify the upstream + tarball using a cryptographic signature. + . + If upstream distributions provides such signatures, please use the + pgpsigurlmangle options in this watch file's opts= to + generate the URL of an upstream GPG signature. This signature is + automatically downloaded and verified against a keyring stored in + debian/upstream/signing-key.asc + . + Of course, not all upstreams provide such signatures but you could + request them as a way of verifying that no third party has modified the + code after its release (projects such as phpmyadmin, unrealircd, and + proftpd have suffered from this kind of attack). +Renamed-From: + debian-watch-may-check-gpg-signature diff -Nru lintian-2.93.0/tags/d/debian-watch-does-not-check-gpg-signature.tag lintian-2.89.0ubuntu1/tags/d/debian-watch-does-not-check-gpg-signature.tag --- lintian-2.93.0/tags/d/debian-watch-does-not-check-gpg-signature.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-watch-does-not-check-gpg-signature.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,20 +0,0 @@ -Tag: debian-watch-does-not-check-gpg-signature -Severity: pedantic -Check: debian/watch -Experimental: yes -See-Also: uscan(1) -Explanation: This watch file does not specify a means to verify the upstream - tarball using a cryptographic signature. - . - If upstream distributions provides such signatures, please use the - pgpsigurlmangle options in this watch file's opts= to - generate the URL of an upstream GPG signature. This signature is - automatically downloaded and verified against a keyring stored in - debian/upstream/signing-key.asc - . - Of course, not all upstreams provide such signatures but you could - request them as a way of verifying that no third party has modified the - code after its release (projects such as phpmyadmin, unrealircd, and - proftpd have suffered from this kind of attack). -Renamed-From: - debian-watch-may-check-gpg-signature diff -Nru lintian-2.93.0/tags/d/debian-watch-file-declares-multiple-versions.desc lintian-2.89.0ubuntu1/tags/d/debian-watch-file-declares-multiple-versions.desc --- lintian-2.93.0/tags/d/debian-watch-file-declares-multiple-versions.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-watch-file-declares-multiple-versions.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: debian-watch-file-declares-multiple-versions +Severity: warning +Check: debian/watch +Ref: uscan(1) +Info: The debian/watch file in this package contains multiple + lines starting with version=. There should be only one version + declaration in a watch file, on the first non-comment line of the file. diff -Nru lintian-2.93.0/tags/d/debian-watch-file-declares-multiple-versions.tag lintian-2.89.0ubuntu1/tags/d/debian-watch-file-declares-multiple-versions.tag --- lintian-2.93.0/tags/d/debian-watch-file-declares-multiple-versions.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-watch-file-declares-multiple-versions.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: debian-watch-file-declares-multiple-versions -Severity: warning -Check: debian/watch -See-Also: uscan(1) -Explanation: The debian/watch file in this package contains multiple - lines starting with version=. There should be only one version - declaration in a watch file, on the first non-comment line of the file. diff -Nru lintian-2.93.0/tags/d/debian-watch-file-in-native-package.desc lintian-2.89.0ubuntu1/tags/d/debian-watch-file-in-native-package.desc --- lintian-2.93.0/tags/d/debian-watch-file-in-native-package.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-watch-file-in-native-package.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: debian-watch-file-in-native-package +Severity: warning +Check: debian/watch +Ref: https://wiki.debian.org/DEHS +Info: The package ships a watch file although it is a Debian native + package. DEHS does not process watch files in native packages based on + the reasoning that native packages do not have upstreams to check for new + releases. diff -Nru lintian-2.93.0/tags/d/debian-watch-file-in-native-package.tag lintian-2.89.0ubuntu1/tags/d/debian-watch-file-in-native-package.tag --- lintian-2.93.0/tags/d/debian-watch-file-in-native-package.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-watch-file-in-native-package.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: debian-watch-file-in-native-package -Severity: warning -Check: debian/watch -See-Also: https://wiki.debian.org/DEHS -Explanation: The package ships a watch file although it is a Debian native - package. DEHS does not process watch files in native packages based on - the reasoning that native packages do not have upstreams to check for new - releases. diff -Nru lintian-2.93.0/tags/d/debian-watch-file-is-missing.desc lintian-2.89.0ubuntu1/tags/d/debian-watch-file-is-missing.desc --- lintian-2.93.0/tags/d/debian-watch-file-is-missing.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-watch-file-is-missing.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,16 @@ +Tag: debian-watch-file-is-missing +Severity: info +Check: debian/watch +Ref: policy 4.11, uscan(1) +Info: This source package is not Debian-native but it does not have a + debian/watch file. This file is used for automatic detection of + new upstream versions by the Debian External Health Status project and + other project infrastructure. If this package is maintained upstream, + please consider adding a debian/watch file to detect new + releases. + . + If the package is not maintained upstream or if upstream uses a + distribution mechanism that cannot be meaningfully monitored by uscan + and the Debian External Health Status project, please consider adding a + debian/watch file containing only comments documenting the + situation. diff -Nru lintian-2.93.0/tags/d/debian-watch-file-is-missing.tag lintian-2.89.0ubuntu1/tags/d/debian-watch-file-is-missing.tag --- lintian-2.93.0/tags/d/debian-watch-file-is-missing.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-watch-file-is-missing.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,16 +0,0 @@ -Tag: debian-watch-file-is-missing -Severity: info -Check: debian/watch -See-Also: policy 4.11, uscan(1) -Explanation: This source package is not Debian-native but it does not have a - debian/watch file. This file is used for automatic detection of - new upstream versions by the Debian External Health Status project and - other project infrastructure. If this package is maintained upstream, - please consider adding a debian/watch file to detect new - releases. - . - If the package is not maintained upstream or if upstream uses a - distribution mechanism that cannot be meaningfully monitored by uscan - and the Debian External Health Status project, please consider adding a - debian/watch file containing only comments documenting the - situation. diff -Nru lintian-2.93.0/tags/d/debian-watch-file-missing-version.desc lintian-2.89.0ubuntu1/tags/d/debian-watch-file-missing-version.desc --- lintian-2.93.0/tags/d/debian-watch-file-missing-version.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-watch-file-missing-version.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: debian-watch-file-missing-version +Severity: warning +Check: debian/watch +Ref: uscan(1) +Info: The debian/watch file in this package doesn't start a + version= line. The first non-comment line of + debian/watch should be a version= declaration. This + may mean that this is an old version one watch file that should be + updated to the current version. diff -Nru lintian-2.93.0/tags/d/debian-watch-file-missing-version.tag lintian-2.89.0ubuntu1/tags/d/debian-watch-file-missing-version.tag --- lintian-2.93.0/tags/d/debian-watch-file-missing-version.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-watch-file-missing-version.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: debian-watch-file-missing-version -Severity: warning -Check: debian/watch -See-Also: uscan(1) -Explanation: The debian/watch file in this package doesn't start a - version= line. The first non-comment line of - debian/watch should be a version= declaration. This - may mean that this is an old version one watch file that should be - updated to the current version. diff -Nru lintian-2.93.0/tags/d/debian-watch-file-pubkey-file-is-missing.desc lintian-2.89.0ubuntu1/tags/d/debian-watch-file-pubkey-file-is-missing.desc --- lintian-2.93.0/tags/d/debian-watch-file-pubkey-file-is-missing.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-watch-file-pubkey-file-is-missing.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: debian-watch-file-pubkey-file-is-missing +Severity: error +Check: debian/watch +Ref: uscan(1) +Info: This watch file verifies a cryptographic signature but + the upstream public key is missing. + . + Please add upstream public keys in either + debian/upstream/signing-key.asc or + debian/upstream/signing-key.pgp. diff -Nru lintian-2.93.0/tags/d/debian-watch-file-pubkey-file-is-missing.tag lintian-2.89.0ubuntu1/tags/d/debian-watch-file-pubkey-file-is-missing.tag --- lintian-2.93.0/tags/d/debian-watch-file-pubkey-file-is-missing.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-watch-file-pubkey-file-is-missing.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,10 +0,0 @@ -Tag: debian-watch-file-pubkey-file-is-missing -Severity: error -Check: debian/watch -See-Also: uscan(1) -Explanation: This watch file verifies a cryptographic signature but - the upstream public key is missing. - . - Please add upstream public keys in either - debian/upstream/signing-key.asc or - debian/upstream/signing-key.pgp. diff -Nru lintian-2.93.0/tags/d/debian-watch-file-specifies-old-upstream-version.desc lintian-2.89.0ubuntu1/tags/d/debian-watch-file-specifies-old-upstream-version.desc --- lintian-2.93.0/tags/d/debian-watch-file-specifies-old-upstream-version.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-watch-file-specifies-old-upstream-version.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: debian-watch-file-specifies-old-upstream-version +Severity: warning +Check: debian/watch +Info: The watch file specifies an upstream version number which matches + the upstream portion of an old debian/changelog entry, and the + current debian/changelog entry specifies a newer upstream + version. The version number in the watch file is very likely to be + incorrect and probably should be replaced with the current expected + upstream version. Otherwise, DEHS and similar projects will think the + package is out of date even when it may not be. diff -Nru lintian-2.93.0/tags/d/debian-watch-file-specifies-old-upstream-version.tag lintian-2.89.0ubuntu1/tags/d/debian-watch-file-specifies-old-upstream-version.tag --- lintian-2.93.0/tags/d/debian-watch-file-specifies-old-upstream-version.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-watch-file-specifies-old-upstream-version.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,10 +0,0 @@ -Tag: debian-watch-file-specifies-old-upstream-version -Severity: warning -Check: debian/watch -Explanation: The watch file specifies an upstream version number which matches - the upstream portion of an old debian/changelog entry, and the - current debian/changelog entry specifies a newer upstream - version. The version number in the watch file is very likely to be - incorrect and probably should be replaced with the current expected - upstream version. Otherwise, DEHS and similar projects will think the - package is out of date even when it may not be. diff -Nru lintian-2.93.0/tags/d/debian-watch-file-specifies-wrong-upstream-version.desc lintian-2.89.0ubuntu1/tags/d/debian-watch-file-specifies-wrong-upstream-version.desc --- lintian-2.93.0/tags/d/debian-watch-file-specifies-wrong-upstream-version.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-watch-file-specifies-wrong-upstream-version.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: debian-watch-file-specifies-wrong-upstream-version +Severity: warning +Check: debian/watch +Ref: uscan(1) +Info: The watch file specifies an upstream version which exactly matches + the version of a debian/changelog entry, this is not a + native package, and no version mangling is being done. The version + field in a watch file should specify the expected upstream version, not + the version of the Debian package. Any epochs and Debian revisions + should be removed first or mangled away. diff -Nru lintian-2.93.0/tags/d/debian-watch-file-specifies-wrong-upstream-version.tag lintian-2.89.0ubuntu1/tags/d/debian-watch-file-specifies-wrong-upstream-version.tag --- lintian-2.93.0/tags/d/debian-watch-file-specifies-wrong-upstream-version.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-watch-file-specifies-wrong-upstream-version.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,10 +0,0 @@ -Tag: debian-watch-file-specifies-wrong-upstream-version -Severity: warning -Check: debian/watch -See-Also: uscan(1) -Explanation: The watch file specifies an upstream version which exactly matches - the version of a debian/changelog entry, this is not a - native package, and no version mangling is being done. The version - field in a watch file should specify the expected upstream version, not - the version of the Debian package. Any epochs and Debian revisions - should be removed first or mangled away. diff -Nru lintian-2.93.0/tags/d/debian-watch-file-standard.desc lintian-2.89.0ubuntu1/tags/d/debian-watch-file-standard.desc --- lintian-2.93.0/tags/d/debian-watch-file-standard.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-watch-file-standard.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: debian-watch-file-standard +Severity: classification +Check: debian/watch +Ref: uscan(1) +Info: The watch file uses this version standard. The currently known + watch file versions are 2, 3 and 4. Version 1 means it was undeclared. diff -Nru lintian-2.93.0/tags/d/debian-watch-file-standard.tag lintian-2.89.0ubuntu1/tags/d/debian-watch-file-standard.tag --- lintian-2.93.0/tags/d/debian-watch-file-standard.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-watch-file-standard.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: debian-watch-file-standard -Severity: classification -Check: debian/watch -See-Also: uscan(1) -Explanation: The watch file uses this version standard. The currently known - watch file versions are 2, 3 and 4. Version 1 means it was undeclared. diff -Nru lintian-2.93.0/tags/d/debian-watch-file-unknown-version.desc lintian-2.89.0ubuntu1/tags/d/debian-watch-file-unknown-version.desc --- lintian-2.93.0/tags/d/debian-watch-file-unknown-version.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-watch-file-unknown-version.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: debian-watch-file-unknown-version +Severity: warning +Check: debian/watch +Ref: uscan(1) +Info: The version= line in the debian/watch file in this + package declares an unknown version. The currently known watch file + versions are 2, 3 and 4 diff -Nru lintian-2.93.0/tags/d/debian-watch-file-unknown-version.tag lintian-2.89.0ubuntu1/tags/d/debian-watch-file-unknown-version.tag --- lintian-2.93.0/tags/d/debian-watch-file-unknown-version.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-watch-file-unknown-version.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: debian-watch-file-unknown-version -Severity: warning -Check: debian/watch -See-Also: uscan(1) -Explanation: The version= line in the debian/watch file in this - package declares an unknown version. The currently known watch file - versions are 2, 3 and 4 diff -Nru lintian-2.93.0/tags/d/debian-watch-file-uses-deprecated-githubredir.desc lintian-2.89.0ubuntu1/tags/d/debian-watch-file-uses-deprecated-githubredir.desc --- lintian-2.93.0/tags/d/debian-watch-file-uses-deprecated-githubredir.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-watch-file-uses-deprecated-githubredir.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,12 @@ +Tag: debian-watch-file-uses-deprecated-githubredir +Severity: error +Check: debian/watch +Ref: https://lists.debian.org/debian-devel-announce/2014/10/msg00000.html +Info: The watch file specifies a githubredir.debian.net URL, which is deprecated + Instead, use direct links to the tags page: + . + version=3 + https://github.com/<user>/<project>/tags .*/(.*)\.tar\.gz + . + replacing <user> and <project> with the Github + username and project respectively. diff -Nru lintian-2.93.0/tags/d/debian-watch-file-uses-deprecated-githubredir.tag lintian-2.89.0ubuntu1/tags/d/debian-watch-file-uses-deprecated-githubredir.tag --- lintian-2.93.0/tags/d/debian-watch-file-uses-deprecated-githubredir.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-watch-file-uses-deprecated-githubredir.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,12 +0,0 @@ -Tag: debian-watch-file-uses-deprecated-githubredir -Severity: error -Check: debian/watch -See-Also: https://lists.debian.org/debian-devel-announce/2014/10/msg00000.html -Explanation: The watch file specifies a githubredir.debian.net URL, which is deprecated - Instead, use direct links to the tags page: - . - version=3 - https://github.com/<user>/<project>/tags .*/(.*)\.tar\.gz - . - replacing <user> and <project> with the Github - username and project respectively. diff -Nru lintian-2.93.0/tags/d/debian-watch-file-uses-deprecated-sf-redirector-method.desc lintian-2.89.0ubuntu1/tags/d/debian-watch-file-uses-deprecated-sf-redirector-method.desc --- lintian-2.93.0/tags/d/debian-watch-file-uses-deprecated-sf-redirector-method.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-watch-file-uses-deprecated-sf-redirector-method.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: debian-watch-file-uses-deprecated-sf-redirector-method +Severity: warning +Check: debian/watch +Info: The watch file seems to be passing arguments to the redirector + other than a path. Calling the SourceForge redirector with parameters like + project prevents uscan from generating working URIs to the files + and thus has been deprecated and is no longer supported by the redirector. diff -Nru lintian-2.93.0/tags/d/debian-watch-file-uses-deprecated-sf-redirector-method.tag lintian-2.89.0ubuntu1/tags/d/debian-watch-file-uses-deprecated-sf-redirector-method.tag --- lintian-2.93.0/tags/d/debian-watch-file-uses-deprecated-sf-redirector-method.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-watch-file-uses-deprecated-sf-redirector-method.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: debian-watch-file-uses-deprecated-sf-redirector-method -Severity: warning -Check: debian/watch -Explanation: The watch file seems to be passing arguments to the redirector - other than a path. Calling the SourceForge redirector with parameters like - project prevents uscan from generating working URIs to the files - and thus has been deprecated and is no longer supported by the redirector. diff -Nru lintian-2.93.0/tags/d/debian-watch-lacks-sourceforge-redirector.desc lintian-2.89.0ubuntu1/tags/d/debian-watch-lacks-sourceforge-redirector.desc --- lintian-2.93.0/tags/d/debian-watch-lacks-sourceforge-redirector.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-watch-lacks-sourceforge-redirector.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,16 @@ +Tag: debian-watch-lacks-sourceforge-redirector +Severity: warning +Check: debian/watch +Renamed-From: debian-watch-file-should-use-sf-redirector +Ref: uscan(1) +Info: The watch file specifies a SourceForge page or download server + directly. This is not recommended; SourceForge changes their download + servers and website periodically, requiring watch files to be modified + every time. Instead, use the qa.debian.org redirector by using the magic + URL: + . + http://sf.net/<project>/<tar-name>-(.+)\.tar\.gz + . + replacing <project> with the name of the SourceForge + project and <tar-name> with the name of the tarball + distributed within that project. Adjust the filename regex as necessary. diff -Nru lintian-2.93.0/tags/d/debian-watch-lacks-sourceforge-redirector.tag lintian-2.89.0ubuntu1/tags/d/debian-watch-lacks-sourceforge-redirector.tag --- lintian-2.93.0/tags/d/debian-watch-lacks-sourceforge-redirector.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-watch-lacks-sourceforge-redirector.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,16 +0,0 @@ -Tag: debian-watch-lacks-sourceforge-redirector -Severity: warning -Check: debian/watch -Renamed-From: debian-watch-file-should-use-sf-redirector -See-Also: uscan(1) -Explanation: The watch file specifies a SourceForge page or download server - directly. This is not recommended; SourceForge changes their download - servers and website periodically, requiring watch files to be modified - every time. Instead, use the qa.debian.org redirector by using the magic - URL: - . - http://sf.net/<project>/<tar-name>-(.+)\.tar\.gz - . - replacing <project> with the name of the SourceForge - project and <tar-name> with the name of the tarball - distributed within that project. Adjust the filename regex as necessary. diff -Nru lintian-2.93.0/tags/d/debian-watch-line-invalid.desc lintian-2.89.0ubuntu1/tags/d/debian-watch-line-invalid.desc --- lintian-2.93.0/tags/d/debian-watch-line-invalid.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-watch-line-invalid.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: debian-watch-line-invalid +Severity: warning +Check: debian/watch +Ref: uscan(1) +Info: The indicated line in the debian/watch file in this + package does not have a regnized format. diff -Nru lintian-2.93.0/tags/d/debian-watch-line-invalid.tag lintian-2.89.0ubuntu1/tags/d/debian-watch-line-invalid.tag --- lintian-2.93.0/tags/d/debian-watch-line-invalid.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-watch-line-invalid.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: debian-watch-line-invalid -Severity: warning -Check: debian/watch -See-Also: uscan(1) -Explanation: The indicated line in the debian/watch file in this - package does not have a regnized format. diff -Nru lintian-2.93.0/tags/d/debian-watch-mangles-debian-version-improperly.desc lintian-2.89.0ubuntu1/tags/d/debian-watch-mangles-debian-version-improperly.desc --- lintian-2.93.0/tags/d/debian-watch-mangles-debian-version-improperly.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-watch-mangles-debian-version-improperly.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,12 @@ +Tag: debian-watch-mangles-debian-version-improperly +Severity: info +Check: debian/watch +Renamed-From: debian-watch-file-should-dversionmangle-not-uversionmangle +Ref: https://wiki.debian.org/DEHS +Info: The version of this package contains dfsg, ds, + or debian, but a misleading upstream version mangling occurs in + the debian/watch file. Since the dfsg string is not + part of the upstream version and its addition is Debian-specific, the + debian/watch file should use the dversionmangle option to + remove, instead of adding in uversionmangle, the dfsg before + comparing version numbers. diff -Nru lintian-2.93.0/tags/d/debian-watch-mangles-debian-version-improperly.tag lintian-2.89.0ubuntu1/tags/d/debian-watch-mangles-debian-version-improperly.tag --- lintian-2.93.0/tags/d/debian-watch-mangles-debian-version-improperly.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-watch-mangles-debian-version-improperly.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,12 +0,0 @@ -Tag: debian-watch-mangles-debian-version-improperly -Severity: info -Check: debian/watch -Renamed-From: debian-watch-file-should-dversionmangle-not-uversionmangle -See-Also: https://wiki.debian.org/DEHS -Explanation: The version of this package contains dfsg, ds, - or debian, but a misleading upstream version mangling occurs in - the debian/watch file. Since the dfsg string is not - part of the upstream version and its addition is Debian-specific, the - debian/watch file should use the dversionmangle option to - remove, instead of adding in uversionmangle, the dfsg before - comparing version numbers. diff -Nru lintian-2.93.0/tags/d/debian-watch-mangles-upstream-version-improperly.desc lintian-2.89.0ubuntu1/tags/d/debian-watch-mangles-upstream-version-improperly.desc --- lintian-2.93.0/tags/d/debian-watch-mangles-upstream-version-improperly.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-watch-mangles-upstream-version-improperly.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: debian-watch-mangles-upstream-version-improperly +Severity: info +Check: debian/watch +Renamed-From: debian-watch-file-should-uversionmangle-not-dversionmangle +Ref: https://wiki.debian.org/DEHS +Info: The version of this package contains alpha, beta, + or rc, but a misleading Debian version mangling occurs in + the debian/watch file. You should use the uversionmangle + option instead of dversionmangle so that the prerelease is sorted by + uscan before a possible future final release. diff -Nru lintian-2.93.0/tags/d/debian-watch-mangles-upstream-version-improperly.tag lintian-2.89.0ubuntu1/tags/d/debian-watch-mangles-upstream-version-improperly.tag --- lintian-2.93.0/tags/d/debian-watch-mangles-upstream-version-improperly.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-watch-mangles-upstream-version-improperly.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,10 +0,0 @@ -Tag: debian-watch-mangles-upstream-version-improperly -Severity: info -Check: debian/watch -Renamed-From: debian-watch-file-should-uversionmangle-not-dversionmangle -See-Also: https://wiki.debian.org/DEHS -Explanation: The version of this package contains alpha, beta, - or rc, but a misleading Debian version mangling occurs in - the debian/watch file. You should use the uversionmangle - option instead of dversionmangle so that the prerelease is sorted by - uscan before a possible future final release. diff -Nru lintian-2.93.0/tags/d/debian-watch-not-mangling-version.desc lintian-2.89.0ubuntu1/tags/d/debian-watch-not-mangling-version.desc --- lintian-2.93.0/tags/d/debian-watch-not-mangling-version.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-watch-not-mangling-version.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,13 @@ +Tag: debian-watch-not-mangling-version +Severity: warning +Check: debian/watch +Renamed-From: debian-watch-file-should-mangle-version +Ref: uscan(1), https://wiki.debian.org/DEHS +Info: The version of this package contains dfsg, ds, + or debian, which normally indicates that the upstream source + has been repackaged to comply with the Debian Free Software Guidelines + (or similar reason), but there is no version mangling in the + debian/watch file. Since the dfsg string is not + part of the upstream version, the debian/watch file should + use the dversionmangle option to remove the dfsg before + version number comparison. diff -Nru lintian-2.93.0/tags/d/debian-watch-not-mangling-version.tag lintian-2.89.0ubuntu1/tags/d/debian-watch-not-mangling-version.tag --- lintian-2.93.0/tags/d/debian-watch-not-mangling-version.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-watch-not-mangling-version.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,13 +0,0 @@ -Tag: debian-watch-not-mangling-version -Severity: warning -Check: debian/watch -Renamed-From: debian-watch-file-should-mangle-version -See-Also: uscan(1), https://wiki.debian.org/DEHS -Explanation: The version of this package contains dfsg, ds, - or debian, which normally indicates that the upstream source - has been repackaged to comply with the Debian Free Software Guidelines - (or similar reason), but there is no version mangling in the - debian/watch file. Since the dfsg string is not - part of the upstream version, the debian/watch file should - use the dversionmangle option to remove the dfsg before - version number comparison. diff -Nru lintian-2.93.0/tags/d/debian-watch-upstream-component.desc lintian-2.89.0ubuntu1/tags/d/debian-watch-upstream-component.desc --- lintian-2.93.0/tags/d/debian-watch-upstream-component.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-watch-upstream-component.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,5 @@ +Tag: debian-watch-upstream-component +Severity: classification +Check: debian/watch +Ref: uscan(1) +Info: Component embedded in debian/watch diff -Nru lintian-2.93.0/tags/d/debian-watch-upstream-component.tag lintian-2.89.0ubuntu1/tags/d/debian-watch-upstream-component.tag --- lintian-2.93.0/tags/d/debian-watch-upstream-component.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-watch-upstream-component.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,5 +0,0 @@ -Tag: debian-watch-upstream-component -Severity: classification -Check: debian/watch -See-Also: uscan(1) -Explanation: Component embedded in debian/watch diff -Nru lintian-2.93.0/tags/d/debian-watch-uses-insecure-uri.desc lintian-2.89.0ubuntu1/tags/d/debian-watch-uses-insecure-uri.desc --- lintian-2.93.0/tags/d/debian-watch-uses-insecure-uri.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-watch-uses-insecure-uri.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: debian-watch-uses-insecure-uri +Severity: info +Check: debian/watch +Info: The watch file uses an unencrypted transport protocol for the + URI such as http:// or ftp://. It is recommended to use a secure + transport such as HTTPS for anonymous read-only access. + . + Upstream may already provide a HTTPS variant of the URI. If not, + please contact them and ask them to consider adding one. diff -Nru lintian-2.93.0/tags/d/debian-watch-uses-insecure-uri.tag lintian-2.89.0ubuntu1/tags/d/debian-watch-uses-insecure-uri.tag --- lintian-2.93.0/tags/d/debian-watch-uses-insecure-uri.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debian-watch-uses-insecure-uri.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: debian-watch-uses-insecure-uri -Severity: info -Check: debian/watch -Explanation: The watch file uses an unencrypted transport protocol for the - URI such as http:// or ftp://. It is recommended to use a secure - transport such as HTTPS for anonymous read-only access. - . - Upstream may already provide a HTTPS variant of the URI. If not, - please contact them and ask them to consider adding one. diff -Nru lintian-2.93.0/tags/d/debug-file-with-no-debug-symbols.desc lintian-2.89.0ubuntu1/tags/d/debug-file-with-no-debug-symbols.desc --- lintian-2.93.0/tags/d/debug-file-with-no-debug-symbols.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debug-file-with-no-debug-symbols.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,13 @@ +Tag: debug-file-with-no-debug-symbols +Severity: warning +Certainty: possible +Check: binaries +Ref: #668437 +Info: The binary is installed as a detached "debug symbols" ELF file, + but it does not appear to have debug information associated with it. + . + A common cause is not passing -g to GCC when compiling. + . + Implementation detail: Lintian checks for the ".debug_line" and the + ".debug_str" sections. If either of these are present, the binary + is assumed to contain debug information. diff -Nru lintian-2.93.0/tags/d/debug-file-with-no-debug-symbols.tag lintian-2.89.0ubuntu1/tags/d/debug-file-with-no-debug-symbols.tag --- lintian-2.93.0/tags/d/debug-file-with-no-debug-symbols.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debug-file-with-no-debug-symbols.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,12 +0,0 @@ -Tag: debug-file-with-no-debug-symbols -Severity: warning -Check: binaries -See-Also: Bug#668437 -Explanation: The binary is installed as a detached "debug symbols" ELF file, - but it does not appear to have debug information associated with it. - . - A common cause is not passing -g to GCC when compiling. - . - Implementation detail: Lintian checks for the ".debug_line" and the - ".debug_str" sections. If either of these are present, the binary - is assumed to contain debug information. diff -Nru lintian-2.93.0/tags/d/debug-package-for-multi-arch-same-pkg-not-coinstallable.desc lintian-2.89.0ubuntu1/tags/d/debug-package-for-multi-arch-same-pkg-not-coinstallable.desc --- lintian-2.93.0/tags/d/debug-package-for-multi-arch-same-pkg-not-coinstallable.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debug-package-for-multi-arch-same-pkg-not-coinstallable.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,20 @@ +Tag: debug-package-for-multi-arch-same-pkg-not-coinstallable +Severity: info +Certainty: possible +Check: group-checks +Info: The debug package appear to be containing debug symbols for a + "Multi-Arch: same" package, but the debug package itself is not + "Multi-Arch: same". If so, it is not possible to have the debug + symbols for all architecture variants of the binaries available + at the same time. + . + Making a debug package co-installable with itself is very trivial, + when installing the debug symbols beneath: + /usr/lib/debug/.build-id/<XX>/<rest-id>.debug + . + dh_strip does this in debhelper compat 9. Otherwise, the expected + location of the debug symbols of a given ELF binary can be determined + by using: + . + readelf -n <binary-elf> | \ + perl -ne 'print if s,^\s*Build ID:\s*(\S\S)(\S+),/usr/lib/debug/.build-id/$1/$2.debug,' diff -Nru lintian-2.93.0/tags/d/debug-package-for-multi-arch-same-pkg-not-coinstallable.tag lintian-2.89.0ubuntu1/tags/d/debug-package-for-multi-arch-same-pkg-not-coinstallable.tag --- lintian-2.93.0/tags/d/debug-package-for-multi-arch-same-pkg-not-coinstallable.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debug-package-for-multi-arch-same-pkg-not-coinstallable.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,19 +0,0 @@ -Tag: debug-package-for-multi-arch-same-pkg-not-coinstallable -Severity: info -Check: group-checks -Explanation: The debug package appear to be containing debug symbols for a - "Multi-Arch: same" package, but the debug package itself is not - "Multi-Arch: same". If so, it is not possible to have the debug - symbols for all architecture variants of the binaries available - at the same time. - . - Making a debug package co-installable with itself is very trivial, - when installing the debug symbols beneath: - /usr/lib/debug/.build-id/<XX>/<rest-id>.debug - . - dh_strip does this in debhelper compat 9. Otherwise, the expected - location of the debug symbols of a given ELF binary can be determined - by using: - . - readelf -n <binary-elf> | \ - perl -ne 'print if s,^\s*Build ID:\s*(\S\S)(\S+),/usr/lib/debug/.build-id/$1/$2.debug,' diff -Nru lintian-2.93.0/tags/d/debug-suffix-not-dbg.desc lintian-2.89.0ubuntu1/tags/d/debug-suffix-not-dbg.desc --- lintian-2.93.0/tags/d/debug-suffix-not-dbg.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debug-suffix-not-dbg.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: debug-suffix-not-dbg +Severity: warning +Check: files/debug +Renamed-From: debug-package-should-be-named-dbg +Info: This package provides at least one file in /usr/lib/debug, + which is intended for detached debugging symbols, but the package name + does not end in "-dbg". Detached debugging symbols should be put into a + separate package, Priority: extra, with a package name ending in "-dbg". +Ref: devref 6.7.9 diff -Nru lintian-2.93.0/tags/d/debug-suffix-not-dbg.tag lintian-2.89.0ubuntu1/tags/d/debug-suffix-not-dbg.tag --- lintian-2.93.0/tags/d/debug-suffix-not-dbg.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debug-suffix-not-dbg.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: debug-suffix-not-dbg -Severity: warning -Check: files/debug -Renamed-From: debug-package-should-be-named-dbg -Explanation: This package provides at least one file in /usr/lib/debug, - which is intended for detached debugging symbols, but the package name - does not end in "-dbg". Detached debugging symbols should be put into a - separate package, Priority: extra, with a package name ending in "-dbg". -See-Also: devref 6.7.9 diff -Nru lintian-2.93.0/tags/d/debug-symbol-migration-possibly-complete.desc lintian-2.89.0ubuntu1/tags/d/debug-symbol-migration-possibly-complete.desc --- lintian-2.93.0/tags/d/debug-symbol-migration-possibly-complete.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debug-symbol-migration-possibly-complete.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,19 @@ +Tag: debug-symbol-migration-possibly-complete +Severity: pedantic +Certainty: possible +Check: debian/rules +Info: The debian/rules file for this package has a call to + dh_strip(1) with the specified --dbgsym-migration or + --ddeb-migration argument. + . + Such arguments are used to migrate packages to use automatic debug + symbols, which first became available in December 2015. + . + If this command was added to the debian/rules that was + included in the current stable release of Debian then it can possibly + be removed. + . + However, if the command was added later (and/or the package was not + included in stretch) please wait until it has been included in a stable + release before removing it. +Ref: dh_strip(1), https://wiki.debian.org/AutomaticDebugPackages diff -Nru lintian-2.93.0/tags/d/debug-symbol-migration-possibly-complete.tag lintian-2.89.0ubuntu1/tags/d/debug-symbol-migration-possibly-complete.tag --- lintian-2.93.0/tags/d/debug-symbol-migration-possibly-complete.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debug-symbol-migration-possibly-complete.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,18 +0,0 @@ -Tag: debug-symbol-migration-possibly-complete -Severity: pedantic -Check: debian/rules -Explanation: The debian/rules file for this package has a call to - dh_strip(1) with the specified --dbgsym-migration or - --ddeb-migration argument. - . - Such arguments are used to migrate packages to use automatic debug - symbols, which first became available in December 2015. - . - If this command was added to the debian/rules that was - included in the current stable release of Debian then it can possibly - be removed. - . - However, if the command was added later (and/or the package was not - included in stretch) please wait until it has been included in a stable - release before removing it. -See-Also: dh_strip(1), https://wiki.debian.org/AutomaticDebugPackages diff -Nru lintian-2.93.0/tags/d/debug-symbols-directly-in-usr-lib-debug.desc lintian-2.89.0ubuntu1/tags/d/debug-symbols-directly-in-usr-lib-debug.desc --- lintian-2.93.0/tags/d/debug-symbols-directly-in-usr-lib-debug.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debug-symbols-directly-in-usr-lib-debug.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,11 @@ +Tag: debug-symbols-directly-in-usr-lib-debug +Severity: error +Check: binaries +Info: The given debugging symbols-only object is installed directly in + /usr/lib/debug, although it should be installed in a + subdirectory. For example, debug symbols of a binary in + /usr/bin should be placed in /usr/lib/debug/usr/bin. + gdb, when looking for debugging symbols, prepends /usr/lib/debug + to whatever path it finds in the .gnu_debuglink section, which when using + dh_strip(1) is either the path to your binary/library or a build-id based + path. diff -Nru lintian-2.93.0/tags/d/debug-symbols-directly-in-usr-lib-debug.tag lintian-2.89.0ubuntu1/tags/d/debug-symbols-directly-in-usr-lib-debug.tag --- lintian-2.93.0/tags/d/debug-symbols-directly-in-usr-lib-debug.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debug-symbols-directly-in-usr-lib-debug.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,11 +0,0 @@ -Tag: debug-symbols-directly-in-usr-lib-debug -Severity: error -Check: binaries -Explanation: The given debugging symbols-only object is installed directly in - /usr/lib/debug, although it should be installed in a - subdirectory. For example, debug symbols of a binary in - /usr/bin should be placed in /usr/lib/debug/usr/bin. - gdb, when looking for debugging symbols, prepends /usr/lib/debug - to whatever path it finds in the .gnu_debuglink section, which when using - dh_strip(1) is either the path to your binary/library or a build-id based - path. diff -Nru lintian-2.93.0/tags/d/debug-symbols-not-detached.desc lintian-2.89.0ubuntu1/tags/d/debug-symbols-not-detached.desc --- lintian-2.93.0/tags/d/debug-symbols-not-detached.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debug-symbols-not-detached.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,18 @@ +Tag: debug-symbols-not-detached +Severity: warning +Check: binaries +Renamed-From: debug-file-should-use-detached-symbols +Ref: devref 6.7.9 +Info: This file is in a location generally used for detached debugging + symbols, but it appears to contain a complete copy of the executable or + library instead of only the debugging symbols. Files in subdirectories + of /usr/lib/debug mirroring the main file system should contain + only debugging information generated by objcopy + --only-keep-debug. Binaries or shared objects built with extra + debugging should be installed directly in /usr/lib/debug or in + subdirectories corresponding to the package, not in the directories that + mirror the main file system. + . + If you are using dh_strip with the --dbg-package flag, don't also install + the library in /usr/lib/debug. dh_strip does all the work for + you. diff -Nru lintian-2.93.0/tags/d/debug-symbols-not-detached.tag lintian-2.89.0ubuntu1/tags/d/debug-symbols-not-detached.tag --- lintian-2.93.0/tags/d/debug-symbols-not-detached.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/debug-symbols-not-detached.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,18 +0,0 @@ -Tag: debug-symbols-not-detached -Severity: warning -Check: binaries -Renamed-From: debug-file-should-use-detached-symbols -See-Also: devref 6.7.9 -Explanation: This file is in a location generally used for detached debugging - symbols, but it appears to contain a complete copy of the executable or - library instead of only the debugging symbols. Files in subdirectories - of /usr/lib/debug mirroring the main file system should contain - only debugging information generated by objcopy - --only-keep-debug. Binaries or shared objects built with extra - debugging should be installed directly in /usr/lib/debug or in - subdirectories corresponding to the package, not in the directories that - mirror the main file system. - . - If you are using dh_strip with the --dbg-package flag, don't also install - the library in /usr/lib/debug. dh_strip does all the work for - you. diff -Nru lintian-2.93.0/tags/d/declares-possibly-conflicting-debhelper-compat-versions.desc lintian-2.89.0ubuntu1/tags/d/declares-possibly-conflicting-debhelper-compat-versions.desc --- lintian-2.93.0/tags/d/declares-possibly-conflicting-debhelper-compat-versions.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/declares-possibly-conflicting-debhelper-compat-versions.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: declares-possibly-conflicting-debhelper-compat-versions +Severity: error +Check: debhelper +Ref: debhelper(7) +Info: The source package declares the debhelper compatibility version + both in the debian/compat file and in the debian/rules + file. If these ever get out of synchronisation, the package may not build + as expected. diff -Nru lintian-2.93.0/tags/d/declares-possibly-conflicting-debhelper-compat-versions.tag lintian-2.89.0ubuntu1/tags/d/declares-possibly-conflicting-debhelper-compat-versions.tag --- lintian-2.93.0/tags/d/declares-possibly-conflicting-debhelper-compat-versions.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/declares-possibly-conflicting-debhelper-compat-versions.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: declares-possibly-conflicting-debhelper-compat-versions -Severity: error -Check: debhelper -See-Also: debhelper(7) -Explanation: The source package declares the debhelper compatibility version - both in the debian/compat file and in the debian/rules - file. If these ever get out of synchronisation, the package may not build - as expected. diff -Nru lintian-2.93.0/tags/d/default-mta-dependency-does-not-specify-mail-transport-agent.desc lintian-2.89.0ubuntu1/tags/d/default-mta-dependency-does-not-specify-mail-transport-agent.desc --- lintian-2.93.0/tags/d/default-mta-dependency-does-not-specify-mail-transport-agent.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/default-mta-dependency-does-not-specify-mail-transport-agent.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,12 @@ +Tag: default-mta-dependency-does-not-specify-mail-transport-agent +Severity: warning +Check: fields/package-relations +Info: This package has a relationship with the default-mta virtual + package but does not specify the mail-transport-agent as an + alternative. + . + default-mta and mail-transport-agent should only ever be in a set of + alternatives together, with default-mta listed first. + . + Please add a "or" dependency on mail-transport-agent after + default-mta. diff -Nru lintian-2.93.0/tags/d/default-mta-dependency-does-not-specify-mail-transport-agent.tag lintian-2.89.0ubuntu1/tags/d/default-mta-dependency-does-not-specify-mail-transport-agent.tag --- lintian-2.93.0/tags/d/default-mta-dependency-does-not-specify-mail-transport-agent.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/default-mta-dependency-does-not-specify-mail-transport-agent.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,12 +0,0 @@ -Tag: default-mta-dependency-does-not-specify-mail-transport-agent -Severity: warning -Check: fields/package-relations -Explanation: This package has a relationship with the default-mta virtual - package but does not specify the mail-transport-agent as an - alternative. - . - default-mta and mail-transport-agent should only ever be in a set of - alternatives together, with default-mta listed first. - . - Please add a "or" dependency on mail-transport-agent after - default-mta. diff -Nru lintian-2.93.0/tags/d/default-mta-dependency-not-listed-first.desc lintian-2.89.0ubuntu1/tags/d/default-mta-dependency-not-listed-first.desc --- lintian-2.93.0/tags/d/default-mta-dependency-not-listed-first.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/default-mta-dependency-not-listed-first.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,13 @@ +Tag: default-mta-dependency-not-listed-first +Severity: warning +Check: fields/package-relations +Info: This package has a relationship with the mail-transport-agent + or default-mta packages but does not specify the default-mta as an + first option. + . + default-mta and mail-transport-agent should only ever be in a set of + alternatives together, with default-mta listed in the primary + position. + . + Please rearrange the dependencies such that default-mta is listed + first. diff -Nru lintian-2.93.0/tags/d/default-mta-dependency-not-listed-first.tag lintian-2.89.0ubuntu1/tags/d/default-mta-dependency-not-listed-first.tag --- lintian-2.93.0/tags/d/default-mta-dependency-not-listed-first.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/default-mta-dependency-not-listed-first.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,13 +0,0 @@ -Tag: default-mta-dependency-not-listed-first -Severity: warning -Check: fields/package-relations -Explanation: This package has a relationship with the mail-transport-agent - or default-mta packages but does not specify the default-mta as an - first option. - . - default-mta and mail-transport-agent should only ever be in a set of - alternatives together, with default-mta listed in the primary - position. - . - Please rearrange the dependencies such that default-mta is listed - first. diff -Nru lintian-2.93.0/tags/d/dep5-copyright-license-name-not-unique.desc lintian-2.89.0ubuntu1/tags/d/dep5-copyright-license-name-not-unique.desc --- lintian-2.93.0/tags/d/dep5-copyright-license-name-not-unique.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/dep5-copyright-license-name-not-unique.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,27 @@ +Tag: dep5-copyright-license-name-not-unique +Severity: warning +Certainty: possible +Check: debian/copyright/dep5 +Ref: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ +Info: This paragraph defines an already defined license. + . + According to the specification, short license names are required to be + unique within a single copyright file. + . + This tag could be raised by something like this: + . + Files: filea ... + Copyright: 2009, ... + License: LGPL-2.1 + This program is free software; + ... + . + Files: fileb ... + Copyright: 2009, ... + License: LGPL-2.1 + This program is free software; + ... + . + In this case, you redefine LGPL-2.1 license. You should use + a stand-alone paragraph or merge the two files (using a single + paragraph). diff -Nru lintian-2.93.0/tags/d/dep5-copyright-license-name-not-unique.tag lintian-2.89.0ubuntu1/tags/d/dep5-copyright-license-name-not-unique.tag --- lintian-2.93.0/tags/d/dep5-copyright-license-name-not-unique.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/dep5-copyright-license-name-not-unique.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,26 +0,0 @@ -Tag: dep5-copyright-license-name-not-unique -Severity: warning -Check: debian/copyright/dep5 -See-Also: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ -Explanation: This paragraph defines an already defined license. - . - According to the specification, short license names are required to be - unique within a single copyright file. - . - This tag could be raised by something like this: - . - Files: filea ... - Copyright: 2009, ... - License: LGPL-2.1 - This program is free software; - ... - . - Files: fileb ... - Copyright: 2009, ... - License: LGPL-2.1 - This program is free software; - ... - . - In this case, you redefine LGPL-2.1 license. You should use - a stand-alone paragraph or merge the two files (using a single - paragraph). diff -Nru lintian-2.93.0/tags/d/dep5-file-paragraph-references-header-paragraph.desc lintian-2.89.0ubuntu1/tags/d/dep5-file-paragraph-references-header-paragraph.desc --- lintian-2.93.0/tags/d/dep5-file-paragraph-references-header-paragraph.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/dep5-file-paragraph-references-header-paragraph.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,12 @@ +Tag: dep5-file-paragraph-references-header-paragraph +Severity: warning +Certainty: possible +Check: debian/copyright/dep5 +Ref: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ +Info: The Files paragraph uses a reference to a license which is + only defined in the Header paragraph. The copyright specification + requires that the Files paragraph either contains the full license + itself or references a "stand-alone" License paragraph, and not the + Header paragraph. +Renamed-From: + dep5-file-paragraph-reference-header-paragraph diff -Nru lintian-2.93.0/tags/d/dep5-file-paragraph-references-header-paragraph.tag lintian-2.89.0ubuntu1/tags/d/dep5-file-paragraph-references-header-paragraph.tag --- lintian-2.93.0/tags/d/dep5-file-paragraph-references-header-paragraph.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/dep5-file-paragraph-references-header-paragraph.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,11 +0,0 @@ -Tag: dep5-file-paragraph-references-header-paragraph -Severity: warning -Check: debian/copyright/dep5 -See-Also: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ -Explanation: The Files paragraph uses a reference to a license which is - only defined in the Header paragraph. The copyright specification - requires that the Files paragraph either contains the full license - itself or references a "stand-alone" License paragraph, and not the - Header paragraph. -Renamed-From: - dep5-file-paragraph-reference-header-paragraph diff -Nru lintian-2.93.0/tags/d/dependency-is-not-multi-archified.desc lintian-2.89.0ubuntu1/tags/d/dependency-is-not-multi-archified.desc --- lintian-2.93.0/tags/d/dependency-is-not-multi-archified.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/dependency-is-not-multi-archified.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: dependency-is-not-multi-archified +Severity: warning +Certainty: possible +Check: group-checks +Info: The package is Multi-Arch "same", but it depends on a package that + is neither Multi-Arch "same" nor "foreign". +Ref: https://wiki.ubuntu.com/MultiarchSpec diff -Nru lintian-2.93.0/tags/d/dependency-is-not-multi-archified.tag lintian-2.89.0ubuntu1/tags/d/dependency-is-not-multi-archified.tag --- lintian-2.93.0/tags/d/dependency-is-not-multi-archified.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/dependency-is-not-multi-archified.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: dependency-is-not-multi-archified -Severity: warning -Check: group-checks -Explanation: The package is Multi-Arch "same", but it depends on a package that - is neither Multi-Arch "same" nor "foreign". -See-Also: https://wiki.ubuntu.com/MultiarchSpec diff -Nru lintian-2.93.0/tags/d/dependency-on-python-version-marked-for-end-of-life.desc lintian-2.89.0ubuntu1/tags/d/dependency-on-python-version-marked-for-end-of-life.desc --- lintian-2.93.0/tags/d/dependency-on-python-version-marked-for-end-of-life.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/dependency-on-python-version-marked-for-end-of-life.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,17 @@ +Tag: dependency-on-python-version-marked-for-end-of-life +Severity: pedantic +Check: languages/python +Experimental: yes +Ref: https://wiki.debian.org/Python/Python3Port, +https://www.python.org/dev/peps/pep-0373/, #897213 +Info: The package specifies a dependency on Python 2.x which is due for + deprecation and will not be maintained upstream past 2020 and will + likely be dropped after the release of Debian "buster". + . + You should not make any changes to your package based on this presence + of this tag. + . + However, please override this tag with a suitably-commented override if + it is known that this package will not be migrated to Python 3.x for one + reason or another. This is so that developers may ignore the package + when looking for software that needs to be ported. diff -Nru lintian-2.93.0/tags/d/dependency-on-python-version-marked-for-end-of-life.tag lintian-2.89.0ubuntu1/tags/d/dependency-on-python-version-marked-for-end-of-life.tag --- lintian-2.93.0/tags/d/dependency-on-python-version-marked-for-end-of-life.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/dependency-on-python-version-marked-for-end-of-life.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,17 +0,0 @@ -Tag: dependency-on-python-version-marked-for-end-of-life -Severity: pedantic -Check: languages/python -Experimental: yes -See-Also: https://wiki.debian.org/Python/Python3Port, -https://www.python.org/dev/peps/pep-0373/, Bug#897213 -Explanation: The package specifies a dependency on Python 2.x which is due for - deprecation and will not be maintained upstream past 2020 and will - likely be dropped after the release of Debian "buster". - . - You should not make any changes to your package based on this presence - of this tag. - . - However, please override this tag with a suitably-commented override if - it is known that this package will not be migrated to Python 3.x for one - reason or another. This is so that developers may ignore the package - when looking for software that needs to be ported. diff -Nru lintian-2.93.0/tags/d/depends-exclusively-on-makedev.desc lintian-2.89.0ubuntu1/tags/d/depends-exclusively-on-makedev.desc --- lintian-2.93.0/tags/d/depends-exclusively-on-makedev.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/depends-exclusively-on-makedev.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: depends-exclusively-on-makedev +Severity: warning +Check: fields/package-relations +Info: This package depends on makedev without a udev alternative. This + probably means that it doesn't have udev rules and relies on makedev to + create devices, which won't work if udev is installed and running. + Alternatively, it may mean that there are udev rules, but udev was not + added as an alternative to the makedev dependency. diff -Nru lintian-2.93.0/tags/d/depends-exclusively-on-makedev.tag lintian-2.89.0ubuntu1/tags/d/depends-exclusively-on-makedev.tag --- lintian-2.93.0/tags/d/depends-exclusively-on-makedev.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/depends-exclusively-on-makedev.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: depends-exclusively-on-makedev -Severity: warning -Check: fields/package-relations -Explanation: This package depends on makedev without a udev alternative. This - probably means that it doesn't have udev rules and relies on makedev to - create devices, which won't work if udev is installed and running. - Alternatively, it may mean that there are udev rules, but udev was not - added as an alternative to the makedev dependency. diff -Nru lintian-2.93.0/tags/d/depends-on-essential-package-without-using-version.desc lintian-2.89.0ubuntu1/tags/d/depends-on-essential-package-without-using-version.desc --- lintian-2.93.0/tags/d/depends-on-essential-package-without-using-version.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/depends-on-essential-package-without-using-version.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: depends-on-essential-package-without-using-version +Severity: error +Check: fields/package-relations +Ref: policy 3.5 +Info: The package declares a depends on an essential package, e.g. dpkg, + without using a versioned depends. Packages do not need to depend on + essential packages; essential means that they will always be present. + The only reason to list an explicit dependency on an essential package + is if you need a particular version of that package, in which case the + version should be given in the dependency. diff -Nru lintian-2.93.0/tags/d/depends-on-essential-package-without-using-version.tag lintian-2.89.0ubuntu1/tags/d/depends-on-essential-package-without-using-version.tag --- lintian-2.93.0/tags/d/depends-on-essential-package-without-using-version.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/depends-on-essential-package-without-using-version.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,10 +0,0 @@ -Tag: depends-on-essential-package-without-using-version -Severity: error -Check: fields/package-relations -See-Also: policy 3.5 -Explanation: The package declares a depends on an essential package, e.g. dpkg, - without using a versioned depends. Packages do not need to depend on - essential packages; essential means that they will always be present. - The only reason to list an explicit dependency on an essential package - is if you need a particular version of that package, in which case the - version should be given in the dependency. diff -Nru lintian-2.93.0/tags/d/depends-on-libdb1-compat.desc lintian-2.89.0ubuntu1/tags/d/depends-on-libdb1-compat.desc --- lintian-2.93.0/tags/d/depends-on-libdb1-compat.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/depends-on-libdb1-compat.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: depends-on-libdb1-compat +Severity: error +Check: fields/package-relations +Info: The package seems to declare a relation on libdb1-compat. + This library exists for compatibility with applications built against + glibc 2.0 or 2.1. There is intentionally no corresponding development + package. Do not link new applications against this library! diff -Nru lintian-2.93.0/tags/d/depends-on-libdb1-compat.tag lintian-2.89.0ubuntu1/tags/d/depends-on-libdb1-compat.tag --- lintian-2.93.0/tags/d/depends-on-libdb1-compat.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/depends-on-libdb1-compat.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: depends-on-libdb1-compat -Severity: error -Check: fields/package-relations -Explanation: The package seems to declare a relation on libdb1-compat. - This library exists for compatibility with applications built against - glibc 2.0 or 2.1. There is intentionally no corresponding development - package. Do not link new applications against this library! diff -Nru lintian-2.93.0/tags/d/depends-on-metapackage.desc lintian-2.89.0ubuntu1/tags/d/depends-on-metapackage.desc --- lintian-2.93.0/tags/d/depends-on-metapackage.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/depends-on-metapackage.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: depends-on-metapackage +Severity: error +Certainty: possible +Check: fields/package-relations +Info: This package is one of the packages that Lintian believes is a + metapackage: a package that exists for the convenience of users or + installers to install a set of related packages. Packages that are not + themselves metapackages must not depend on metapackages, since this may + prevent the user from removing portions of the package set they don't + need. diff -Nru lintian-2.93.0/tags/d/depends-on-metapackage.tag lintian-2.89.0ubuntu1/tags/d/depends-on-metapackage.tag --- lintian-2.93.0/tags/d/depends-on-metapackage.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/depends-on-metapackage.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: depends-on-metapackage -Severity: error -Check: fields/package-relations -Explanation: This package is one of the packages that Lintian believes is a - metapackage: a package that exists for the convenience of users or - installers to install a set of related packages. Packages that are not - themselves metapackages must not depend on metapackages, since this may - prevent the user from removing portions of the package set they don't - need. diff -Nru lintian-2.93.0/tags/d/depends-on-misc-pre-depends.desc lintian-2.89.0ubuntu1/tags/d/depends-on-misc-pre-depends.desc --- lintian-2.93.0/tags/d/depends-on-misc-pre-depends.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/depends-on-misc-pre-depends.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: depends-on-misc-pre-depends +Severity: warning +Certainty: possible +Check: debian/control +Info: This package has a Depends field that contains the + ${misc:Pre-Depends} substitution variable. This should be in + the Pre-Depends field instead. diff -Nru lintian-2.93.0/tags/d/depends-on-misc-pre-depends.tag lintian-2.89.0ubuntu1/tags/d/depends-on-misc-pre-depends.tag --- lintian-2.93.0/tags/d/depends-on-misc-pre-depends.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/depends-on-misc-pre-depends.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: depends-on-misc-pre-depends -Severity: warning -Check: debian/control -Explanation: This package has a Depends field that contains the - ${misc:Pre-Depends} substitution variable. This should be in - the Pre-Depends field instead. diff -Nru lintian-2.93.0/tags/d/depends-on-obsolete-package.desc lintian-2.89.0ubuntu1/tags/d/depends-on-obsolete-package.desc --- lintian-2.93.0/tags/d/depends-on-obsolete-package.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/depends-on-obsolete-package.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: depends-on-obsolete-package +Severity: error +Certainty: possible +Check: fields/package-relations +Info: The package depends on a package that has been superseded. + If the superseded package is part of an ORed group, it should not be + the first package in the group. diff -Nru lintian-2.93.0/tags/d/depends-on-obsolete-package.tag lintian-2.89.0ubuntu1/tags/d/depends-on-obsolete-package.tag --- lintian-2.93.0/tags/d/depends-on-obsolete-package.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/depends-on-obsolete-package.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: depends-on-obsolete-package -Severity: error -Check: fields/package-relations -Explanation: The package depends on a package that has been superseded. - If the superseded package is part of an ORed group, it should not be - the first package in the group. diff -Nru lintian-2.93.0/tags/d/depends-on-old-emacs.desc lintian-2.89.0ubuntu1/tags/d/depends-on-old-emacs.desc --- lintian-2.93.0/tags/d/depends-on-old-emacs.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/depends-on-old-emacs.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,12 @@ +Tag: depends-on-old-emacs +Severity: warning +Certainty: possible +Check: fields/package-relations +Info: The package lists an old version of Emacs as its first dependency. + It should probably be updated to support the current version of Emacs + in the archive and then list that version first in the list of Emacs + flavors it supports. + . + If the package intentionally only supports older versions of Emacs (if, + for example, it was included with later versions of Emacs), add a Lintian + override. diff -Nru lintian-2.93.0/tags/d/depends-on-old-emacs.tag lintian-2.89.0ubuntu1/tags/d/depends-on-old-emacs.tag --- lintian-2.93.0/tags/d/depends-on-old-emacs.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/depends-on-old-emacs.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,11 +0,0 @@ -Tag: depends-on-old-emacs -Severity: warning -Check: fields/package-relations -Explanation: The package lists an old version of Emacs as its first dependency. - It should probably be updated to support the current version of Emacs - in the archive and then list that version first in the list of Emacs - flavors it supports. - . - If the package intentionally only supports older versions of Emacs (if, - for example, it was included with later versions of Emacs), add a Lintian - override. diff -Nru lintian-2.93.0/tags/d/depends-on-packaging-dev.desc lintian-2.89.0ubuntu1/tags/d/depends-on-packaging-dev.desc --- lintian-2.93.0/tags/d/depends-on-packaging-dev.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/depends-on-packaging-dev.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,5 @@ +Tag: depends-on-packaging-dev +Info: You depend/recommend/build-depend on packaging-dev, which is + only a metapackage to install common packages needed for packaging. +Severity: warning +Check: fields/package-relations diff -Nru lintian-2.93.0/tags/d/depends-on-packaging-dev.tag lintian-2.89.0ubuntu1/tags/d/depends-on-packaging-dev.tag --- lintian-2.93.0/tags/d/depends-on-packaging-dev.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/depends-on-packaging-dev.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,5 +0,0 @@ -Tag: depends-on-packaging-dev -Explanation: You depend/recommend/build-depend on packaging-dev, which is - only a metapackage to install common packages needed for packaging. -Severity: warning -Check: fields/package-relations diff -Nru lintian-2.93.0/tags/d/depends-on-python2-and-python3.desc lintian-2.89.0ubuntu1/tags/d/depends-on-python2-and-python3.desc --- lintian-2.93.0/tags/d/depends-on-python2-and-python3.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/depends-on-python2-and-python3.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: depends-on-python2-and-python3 +Severity: info +Certainty: possible +Check: languages/python +Info: The specified package has a relation to both the Python 2 and + Python 3 interpreters. It may be that the package has only been + partially migrated to Python 3 from Python 2.x. + . + Please check the contents and/or dependencies of this package. diff -Nru lintian-2.93.0/tags/d/depends-on-python2-and-python3.tag lintian-2.89.0ubuntu1/tags/d/depends-on-python2-and-python3.tag --- lintian-2.93.0/tags/d/depends-on-python2-and-python3.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/depends-on-python2-and-python3.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: depends-on-python2-and-python3 -Severity: info -Check: languages/python -Explanation: The specified package has a relation to both the Python 2 and - Python 3 interpreters. It may be that the package has only been - partially migrated to Python 3 from Python 2.x. - . - Please check the contents and/or dependencies of this package. diff -Nru lintian-2.93.0/tags/d/depends-on-python-minimal.desc lintian-2.89.0ubuntu1/tags/d/depends-on-python-minimal.desc --- lintian-2.93.0/tags/d/depends-on-python-minimal.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/depends-on-python-minimal.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: depends-on-python-minimal +Severity: error +Check: fields/package-relations +Info: The python-minimal package (and versioned variants thereof) exists + only to possibly become an Essential package. Depending on it is always + an error since it should never be installed without python. If it + becomes Essential, there is no need to depend on it, and until then, + packages that require Python must depend on python. diff -Nru lintian-2.93.0/tags/d/depends-on-python-minimal.tag lintian-2.89.0ubuntu1/tags/d/depends-on-python-minimal.tag --- lintian-2.93.0/tags/d/depends-on-python-minimal.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/depends-on-python-minimal.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: depends-on-python-minimal -Severity: error -Check: fields/package-relations -Explanation: The python-minimal package (and versioned variants thereof) exists - only to possibly become an Essential package. Depending on it is always - an error since it should never be installed without python. If it - becomes Essential, there is no need to depend on it, and until then, - packages that require Python must depend on python. diff -Nru lintian-2.93.0/tags/d/depends-on-specific-java-doc-package.desc lintian-2.89.0ubuntu1/tags/d/depends-on-specific-java-doc-package.desc --- lintian-2.93.0/tags/d/depends-on-specific-java-doc-package.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/depends-on-specific-java-doc-package.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: depends-on-specific-java-doc-package +Severity: warning +Check: fields/package-relations +Info: The package should use default-jdk-doc instead of classpath-doc + or openjdk-X-doc to ease transitions when the providing doc package + is replaced (e.g. openjdk-6-doc being replaced by openjdk-7-doc). diff -Nru lintian-2.93.0/tags/d/depends-on-specific-java-doc-package.tag lintian-2.89.0ubuntu1/tags/d/depends-on-specific-java-doc-package.tag --- lintian-2.93.0/tags/d/depends-on-specific-java-doc-package.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/depends-on-specific-java-doc-package.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: depends-on-specific-java-doc-package -Severity: warning -Check: fields/package-relations -Explanation: The package should use default-jdk-doc instead of classpath-doc - or openjdk-X-doc to ease transitions when the providing doc package - is replaced (e.g. openjdk-6-doc being replaced by openjdk-7-doc). diff -Nru lintian-2.93.0/tags/d/deprecated-configure-filename.desc lintian-2.89.0ubuntu1/tags/d/deprecated-configure-filename.desc --- lintian-2.93.0/tags/d/deprecated-configure-filename.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/deprecated-configure-filename.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: deprecated-configure-filename +Severity: info +Check: build-systems/automake +Info: The use of 'configure.in' with automake is deprecated and will + not be supported in future versions of automake. Please consider + (helping upstream) migrating to 'configure.ac' instead. +Ref: https://lists.gnu.org/archive/html/automake/2013-05/msg00049.html +Experimental: yes diff -Nru lintian-2.93.0/tags/d/deprecated-configure-filename.tag lintian-2.89.0ubuntu1/tags/d/deprecated-configure-filename.tag --- lintian-2.93.0/tags/d/deprecated-configure-filename.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/deprecated-configure-filename.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: deprecated-configure-filename -Severity: info -Check: build-systems/automake -Explanation: The use of 'configure.in' with automake is deprecated and will - not be supported in future versions of automake. Please consider - (helping upstream) migrating to 'configure.ac' instead. -See-Also: https://lists.gnu.org/archive/html/automake/2013-05/msg00049.html -Experimental: yes diff -Nru lintian-2.93.0/tags/d/description-contains-dh-make-perl-template.desc lintian-2.89.0ubuntu1/tags/d/description-contains-dh-make-perl-template.desc --- lintian-2.93.0/tags/d/description-contains-dh-make-perl-template.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/description-contains-dh-make-perl-template.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: description-contains-dh-make-perl-template +Severity: warning +Check: fields/description +Info: The extended description contains the statement that it was + automagically extracted by dh-make-perl. Please check the description + for correctness and usefulness and remove the dh-make-perl statement + to signal that you have done so. diff -Nru lintian-2.93.0/tags/d/description-contains-dh-make-perl-template.tag lintian-2.89.0ubuntu1/tags/d/description-contains-dh-make-perl-template.tag --- lintian-2.93.0/tags/d/description-contains-dh-make-perl-template.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/description-contains-dh-make-perl-template.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: description-contains-dh-make-perl-template -Severity: warning -Check: fields/description -Explanation: The extended description contains the statement that it was - automagically extracted by dh-make-perl. Please check the description - for correctness and usefulness and remove the dh-make-perl statement - to signal that you have done so. diff -Nru lintian-2.93.0/tags/d/description-contains-homepage.desc lintian-2.89.0ubuntu1/tags/d/description-contains-homepage.desc --- lintian-2.93.0/tags/d/description-contains-homepage.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/description-contains-homepage.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: description-contains-homepage +Severity: warning +Check: fields/description +Info: The extended description contains a "Homepage" pseudo-field + following the old Developer's Reference recommendation. As of 1.14.6, + dpkg now supports Homepage as a regular field in + debian/control. This pseudo-field should be moved from the + extended description to the fields for the relevant source or binary + packages. diff -Nru lintian-2.93.0/tags/d/description-contains-homepage.tag lintian-2.89.0ubuntu1/tags/d/description-contains-homepage.tag --- lintian-2.93.0/tags/d/description-contains-homepage.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/description-contains-homepage.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: description-contains-homepage -Severity: warning -Check: fields/description -Explanation: The extended description contains a "Homepage" pseudo-field - following the old Developer's Reference recommendation. As of 1.14.6, - dpkg now supports Homepage as a regular field in - debian/control. This pseudo-field should be moved from the - extended description to the fields for the relevant source or binary - packages. diff -Nru lintian-2.93.0/tags/d/description-contains-invalid-control-statement.desc lintian-2.89.0ubuntu1/tags/d/description-contains-invalid-control-statement.desc --- lintian-2.93.0/tags/d/description-contains-invalid-control-statement.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/description-contains-invalid-control-statement.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,13 @@ +Tag: description-contains-invalid-control-statement +Severity: error +Check: fields/description +Info: The description contains an invalid control statement. + . + A control statement is a line starting with a dot (.). The only + control statement is defined by the policy is a single dot denoting + an empty line. + . + The "empty-line" control statement does not permit any characters + following it on the same line. Therefore, the line must consist + entirely of a space followed by a dot. +Ref: policy 5.6.13 diff -Nru lintian-2.93.0/tags/d/description-contains-invalid-control-statement.tag lintian-2.89.0ubuntu1/tags/d/description-contains-invalid-control-statement.tag --- lintian-2.93.0/tags/d/description-contains-invalid-control-statement.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/description-contains-invalid-control-statement.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,13 +0,0 @@ -Tag: description-contains-invalid-control-statement -Severity: error -Check: fields/description -Explanation: The description contains an invalid control statement. - . - A control statement is a line starting with a dot (.). The only - control statement is defined by the policy is a single dot denoting - an empty line. - . - The "empty-line" control statement does not permit any characters - following it on the same line. Therefore, the line must consist - entirely of a space followed by a dot. -See-Also: policy 5.6.13 diff -Nru lintian-2.93.0/tags/d/description-contains-tabs.desc lintian-2.89.0ubuntu1/tags/d/description-contains-tabs.desc --- lintian-2.93.0/tags/d/description-contains-tabs.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/description-contains-tabs.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,5 @@ +Tag: description-contains-tabs +Severity: error +Check: fields/description +Info: The package "Description:" must not contain tab characters. +Ref: policy 5.6.13 diff -Nru lintian-2.93.0/tags/d/description-contains-tabs.tag lintian-2.89.0ubuntu1/tags/d/description-contains-tabs.tag --- lintian-2.93.0/tags/d/description-contains-tabs.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/description-contains-tabs.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,5 +0,0 @@ -Tag: description-contains-tabs -Severity: error -Check: fields/description -Explanation: The package "Description:" must not contain tab characters. -See-Also: policy 5.6.13 diff -Nru lintian-2.93.0/tags/d/description-is-debmake-template.desc lintian-2.89.0ubuntu1/tags/d/description-is-debmake-template.desc --- lintian-2.93.0/tags/d/description-is-debmake-template.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/description-is-debmake-template.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,5 @@ +Tag: description-is-debmake-template +Severity: error +Check: fields/description +Info: The synopsis or the extended description just says "Missing", + which is a template provided by debmake. diff -Nru lintian-2.93.0/tags/d/description-is-debmake-template.tag lintian-2.89.0ubuntu1/tags/d/description-is-debmake-template.tag --- lintian-2.93.0/tags/d/description-is-debmake-template.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/description-is-debmake-template.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,5 +0,0 @@ -Tag: description-is-debmake-template -Severity: error -Check: fields/description -Explanation: The synopsis or the extended description just says "Missing", - which is a template provided by debmake. diff -Nru lintian-2.93.0/tags/d/description-is-dh_make-template.desc lintian-2.89.0ubuntu1/tags/d/description-is-dh_make-template.desc --- lintian-2.93.0/tags/d/description-is-dh_make-template.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/description-is-dh_make-template.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,5 @@ +Tag: description-is-dh_make-template +Severity: error +Check: fields/description +Info: The synopsis or the extended description has not been changed + from the template provided by dh_make. diff -Nru lintian-2.93.0/tags/d/description-is-dh_make-template.tag lintian-2.89.0ubuntu1/tags/d/description-is-dh_make-template.tag --- lintian-2.93.0/tags/d/description-is-dh_make-template.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/description-is-dh_make-template.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,5 +0,0 @@ -Tag: description-is-dh_make-template -Severity: error -Check: fields/description -Explanation: The synopsis or the extended description has not been changed - from the template provided by dh_make. diff -Nru lintian-2.93.0/tags/d/description-is-pkg-name.desc lintian-2.89.0ubuntu1/tags/d/description-is-pkg-name.desc --- lintian-2.93.0/tags/d/description-is-pkg-name.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/description-is-pkg-name.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: description-is-pkg-name +Severity: error +Check: fields/description +Ref: devref 6.2.2 +Info: The description is the same as the package name. + A better description should be provided for the user. diff -Nru lintian-2.93.0/tags/d/description-is-pkg-name.tag lintian-2.89.0ubuntu1/tags/d/description-is-pkg-name.tag --- lintian-2.93.0/tags/d/description-is-pkg-name.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/description-is-pkg-name.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: description-is-pkg-name -Severity: error -Check: fields/description -See-Also: devref 6.2.2 -Explanation: The description is the same as the package name. - A better description should be provided for the user. diff -Nru lintian-2.93.0/tags/d/description-mentions-planned-features.desc lintian-2.89.0ubuntu1/tags/d/description-mentions-planned-features.desc --- lintian-2.93.0/tags/d/description-mentions-planned-features.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/description-mentions-planned-features.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,12 @@ +Tag: description-mentions-planned-features +Severity: info +Certainty: wild-guess +Check: fields/description +Info: This package appears to mention planned or upcoming features of + the software. + . + Package descriptions should not mention features that are not yet implemented + as they waste the time of people searching for particular keywords. They are + also liable to become outdated quickly. + . + Please remove such statements from the package description. diff -Nru lintian-2.93.0/tags/d/description-mentions-planned-features.tag lintian-2.89.0ubuntu1/tags/d/description-mentions-planned-features.tag --- lintian-2.93.0/tags/d/description-mentions-planned-features.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/description-mentions-planned-features.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,11 +0,0 @@ -Tag: description-mentions-planned-features -Severity: info -Check: fields/description -Explanation: This package appears to mention planned or upcoming features of - the software. - . - Package descriptions should not mention features that are not yet implemented - as they waste the time of people searching for particular keywords. They are - also liable to become outdated quickly. - . - Please remove such statements from the package description. diff -Nru lintian-2.93.0/tags/d/description-possibly-contains-homepage.desc lintian-2.89.0ubuntu1/tags/d/description-possibly-contains-homepage.desc --- lintian-2.93.0/tags/d/description-possibly-contains-homepage.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/description-possibly-contains-homepage.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: description-possibly-contains-homepage +Severity: info +Certainty: wild-guess +Check: fields/description +Info: This package has no Homepage field but has a URL in the description + and wording that might indicate this is the package Homepage. If it is, + add a Homepage control field containing it rather than mentioning it in + the package description. diff -Nru lintian-2.93.0/tags/d/description-possibly-contains-homepage.tag lintian-2.89.0ubuntu1/tags/d/description-possibly-contains-homepage.tag --- lintian-2.93.0/tags/d/description-possibly-contains-homepage.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/description-possibly-contains-homepage.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: description-possibly-contains-homepage -Severity: info -Check: fields/description -Explanation: This package has no Homepage field but has a URL in the description - and wording that might indicate this is the package Homepage. If it is, - add a Homepage control field containing it rather than mentioning it in - the package description. diff -Nru lintian-2.93.0/tags/d/description-starts-with-leading-spaces.desc lintian-2.89.0ubuntu1/tags/d/description-starts-with-leading-spaces.desc --- lintian-2.93.0/tags/d/description-starts-with-leading-spaces.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/description-starts-with-leading-spaces.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: description-starts-with-leading-spaces +Severity: warning +Certainty: possible +Check: fields/description +Info: The package's extended "Description:" paragraph starts with more than + one leading space. Usually, leading spaces are used to switch "verbatim + display" on (i.e., lines are not wrapped) so this might be a bug in the + package. diff -Nru lintian-2.93.0/tags/d/description-starts-with-leading-spaces.tag lintian-2.89.0ubuntu1/tags/d/description-starts-with-leading-spaces.tag --- lintian-2.93.0/tags/d/description-starts-with-leading-spaces.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/description-starts-with-leading-spaces.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: description-starts-with-leading-spaces -Severity: warning -Check: fields/description -Explanation: The package's extended "Description:" paragraph starts with more than - one leading space. Usually, leading spaces are used to switch "verbatim - display" on (i.e., lines are not wrapped) so this might be a bug in the - package. diff -Nru lintian-2.93.0/tags/d/description-starts-with-package-name.desc lintian-2.89.0ubuntu1/tags/d/description-starts-with-package-name.desc --- lintian-2.93.0/tags/d/description-starts-with-package-name.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/description-starts-with-package-name.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: description-starts-with-package-name +Severity: error +Check: fields/description +Info: The first line of the "Description:" should not start with the + package name. For example, the package foo should not + have a description like this: "foo is a program that...". +Ref: policy 3.4.1 diff -Nru lintian-2.93.0/tags/d/description-starts-with-package-name.tag lintian-2.89.0ubuntu1/tags/d/description-starts-with-package-name.tag --- lintian-2.93.0/tags/d/description-starts-with-package-name.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/description-starts-with-package-name.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: description-starts-with-package-name -Severity: error -Check: fields/description -Explanation: The first line of the "Description:" should not start with the - package name. For example, the package foo should not - have a description like this: "foo is a program that...". -See-Also: policy 3.4.1 diff -Nru lintian-2.93.0/tags/d/description-synopsis-is-duplicated.desc lintian-2.89.0ubuntu1/tags/d/description-synopsis-is-duplicated.desc --- lintian-2.93.0/tags/d/description-synopsis-is-duplicated.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/description-synopsis-is-duplicated.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: description-synopsis-is-duplicated +Severity: error +Check: fields/description +Info: The first line of the extended Description: should not repeat the + synopsis exactly. This indicates that either the synopsis is badly formed + or that the extended description has been wrongly copied and pasted. +Ref: policy 3.4.2 diff -Nru lintian-2.93.0/tags/d/description-synopsis-is-duplicated.tag lintian-2.89.0ubuntu1/tags/d/description-synopsis-is-duplicated.tag --- lintian-2.93.0/tags/d/description-synopsis-is-duplicated.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/description-synopsis-is-duplicated.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: description-synopsis-is-duplicated -Severity: error -Check: fields/description -Explanation: The first line of the extended Description: should not repeat the - synopsis exactly. This indicates that either the synopsis is badly formed - or that the extended description has been wrongly copied and pasted. -See-Also: policy 3.4.2 diff -Nru lintian-2.93.0/tags/d/description-synopsis-is-empty.desc lintian-2.89.0ubuntu1/tags/d/description-synopsis-is-empty.desc --- lintian-2.93.0/tags/d/description-synopsis-is-empty.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/description-synopsis-is-empty.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,5 @@ +Tag: description-synopsis-is-empty +Severity: error +Check: fields/description +Info: The first line in the "Description:" is empty. +Ref: policy 3.4 diff -Nru lintian-2.93.0/tags/d/description-synopsis-is-empty.tag lintian-2.89.0ubuntu1/tags/d/description-synopsis-is-empty.tag --- lintian-2.93.0/tags/d/description-synopsis-is-empty.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/description-synopsis-is-empty.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,5 +0,0 @@ -Tag: description-synopsis-is-empty -Severity: error -Check: fields/description -Explanation: The first line in the "Description:" is empty. -See-Also: policy 3.4 diff -Nru lintian-2.93.0/tags/d/description-synopsis-starts-with-article.desc lintian-2.89.0ubuntu1/tags/d/description-synopsis-starts-with-article.desc --- lintian-2.93.0/tags/d/description-synopsis-starts-with-article.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/description-synopsis-starts-with-article.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: description-synopsis-starts-with-article +Severity: warning +Check: fields/description +Info: The first line of the "Description:" should omit any initial indefinite + or definite article: "a", "an", or "the". A good heuristic is that it should + be possible to substitute the package name and synopsis + into this formula: + . + The package name provides {a,an,the,some} synopsis. +Ref: devref 6.2.2 diff -Nru lintian-2.93.0/tags/d/description-synopsis-starts-with-article.tag lintian-2.89.0ubuntu1/tags/d/description-synopsis-starts-with-article.tag --- lintian-2.93.0/tags/d/description-synopsis-starts-with-article.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/description-synopsis-starts-with-article.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,10 +0,0 @@ -Tag: description-synopsis-starts-with-article -Severity: warning -Check: fields/description -Explanation: The first line of the "Description:" should omit any initial indefinite - or definite article: "a", "an", or "the". A good heuristic is that it should - be possible to substitute the package name and synopsis - into this formula: - . - The package name provides {a,an,the,some} synopsis. -See-Also: devref 6.2.2 diff -Nru lintian-2.93.0/tags/d/description-too-short.desc lintian-2.89.0ubuntu1/tags/d/description-too-short.desc --- lintian-2.93.0/tags/d/description-too-short.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/description-too-short.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: description-too-short +Severity: error +Check: fields/description +Ref: devref 6.2.2 +Info: The description contains only a single word. It is likely that the + description won't be very clear for the user. diff -Nru lintian-2.93.0/tags/d/description-too-short.tag lintian-2.89.0ubuntu1/tags/d/description-too-short.tag --- lintian-2.93.0/tags/d/description-too-short.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/description-too-short.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: description-too-short -Severity: error -Check: fields/description -See-Also: devref 6.2.2 -Explanation: The description contains only a single word. It is likely that the - description won't be very clear for the user. diff -Nru lintian-2.93.0/tags/d/desktop-command-not-in-package.desc lintian-2.89.0ubuntu1/tags/d/desktop-command-not-in-package.desc --- lintian-2.93.0/tags/d/desktop-command-not-in-package.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/desktop-command-not-in-package.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: desktop-command-not-in-package +Severity: warning +Certainty: possible +Check: menu-format +Info: The desktop entry specifies a command that is not available in the + package. In most cases, this is a typo or a forgotten update of the + desktop file after the install location of the binary was changed. A + desktop file for a command should be included in the same package as that + command. diff -Nru lintian-2.93.0/tags/d/desktop-command-not-in-package.tag lintian-2.89.0ubuntu1/tags/d/desktop-command-not-in-package.tag --- lintian-2.93.0/tags/d/desktop-command-not-in-package.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/desktop-command-not-in-package.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: desktop-command-not-in-package -Severity: warning -Check: menu-format -Explanation: The desktop entry specifies a command that is not available in the - package. In most cases, this is a typo or a forgotten update of the - desktop file after the install location of the binary was changed. A - desktop file for a command should be included in the same package as that - command. diff -Nru lintian-2.93.0/tags/d/desktop-contains-deprecated-key.desc lintian-2.89.0ubuntu1/tags/d/desktop-contains-deprecated-key.desc --- lintian-2.93.0/tags/d/desktop-contains-deprecated-key.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/desktop-contains-deprecated-key.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: desktop-contains-deprecated-key +Severity: warning +Check: menu-format +Info: The key on this line of the desktop entry has been deprecated in the + FreeDesktop specification. If the key is "KDE Desktop Entry", the right + fix is normally changing it to "Desktop Entry". + . + The desktop-file-validate tool in the desktop-file-utils package is + useful for checking the syntax of desktop entries. +Ref: https://specifications.freedesktop.org/desktop-entry-spec/latest/apc.html diff -Nru lintian-2.93.0/tags/d/desktop-contains-deprecated-key.tag lintian-2.89.0ubuntu1/tags/d/desktop-contains-deprecated-key.tag --- lintian-2.93.0/tags/d/desktop-contains-deprecated-key.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/desktop-contains-deprecated-key.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,10 +0,0 @@ -Tag: desktop-contains-deprecated-key -Severity: warning -Check: menu-format -Explanation: The key on this line of the desktop entry has been deprecated in the - FreeDesktop specification. If the key is "KDE Desktop Entry", the right - fix is normally changing it to "Desktop Entry". - . - The desktop-file-validate tool in the desktop-file-utils package is - useful for checking the syntax of desktop entries. -See-Also: https://specifications.freedesktop.org/desktop-entry-spec/latest/apc.html diff -Nru lintian-2.93.0/tags/d/desktop-entry-contains-deprecated-key.desc lintian-2.89.0ubuntu1/tags/d/desktop-entry-contains-deprecated-key.desc --- lintian-2.93.0/tags/d/desktop-entry-contains-deprecated-key.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/desktop-entry-contains-deprecated-key.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: desktop-entry-contains-deprecated-key +Severity: warning +Check: menu-format +Info: The key on this line of the desktop entry has been deprecated in the + FreeDesktop specification. + . + The desktop-file-validate tool in the desktop-file-utils package is + useful for checking the syntax of desktop entries. +Ref: https://specifications.freedesktop.org/desktop-entry-spec/latest/apc.html diff -Nru lintian-2.93.0/tags/d/desktop-entry-contains-deprecated-key.tag lintian-2.89.0ubuntu1/tags/d/desktop-entry-contains-deprecated-key.tag --- lintian-2.93.0/tags/d/desktop-entry-contains-deprecated-key.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/desktop-entry-contains-deprecated-key.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: desktop-entry-contains-deprecated-key -Severity: warning -Check: menu-format -Explanation: The key on this line of the desktop entry has been deprecated in the - FreeDesktop specification. - . - The desktop-file-validate tool in the desktop-file-utils package is - useful for checking the syntax of desktop entries. -See-Also: https://specifications.freedesktop.org/desktop-entry-spec/latest/apc.html diff -Nru lintian-2.93.0/tags/d/desktop-entry-contains-encoding-key.desc lintian-2.89.0ubuntu1/tags/d/desktop-entry-contains-encoding-key.desc --- lintian-2.93.0/tags/d/desktop-entry-contains-encoding-key.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/desktop-entry-contains-encoding-key.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,11 @@ +Tag: desktop-entry-contains-encoding-key +Severity: info +Check: menu-format +Info: The Encoding key is now deprecated by the FreeDesktop standard and + all strings are required to be encoded in UTF-8. This desktop entry + explicitly specifies an Encoding of UTF-8, which is harmless but no + longer necessary. + . + The desktop-file-validate tool in the desktop-file-utils package is + useful for checking the syntax of desktop entries. +Ref: https://specifications.freedesktop.org/desktop-entry-spec/latest/apc.html diff -Nru lintian-2.93.0/tags/d/desktop-entry-contains-encoding-key.tag lintian-2.89.0ubuntu1/tags/d/desktop-entry-contains-encoding-key.tag --- lintian-2.93.0/tags/d/desktop-entry-contains-encoding-key.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/desktop-entry-contains-encoding-key.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,11 +0,0 @@ -Tag: desktop-entry-contains-encoding-key -Severity: info -Check: menu-format -Explanation: The Encoding key is now deprecated by the FreeDesktop standard and - all strings are required to be encoded in UTF-8. This desktop entry - explicitly specifies an Encoding of UTF-8, which is harmless but no - longer necessary. - . - The desktop-file-validate tool in the desktop-file-utils package is - useful for checking the syntax of desktop entries. -See-Also: https://specifications.freedesktop.org/desktop-entry-spec/latest/apc.html diff -Nru lintian-2.93.0/tags/d/desktop-entry-contains-unknown-key.desc lintian-2.89.0ubuntu1/tags/d/desktop-entry-contains-unknown-key.desc --- lintian-2.93.0/tags/d/desktop-entry-contains-unknown-key.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/desktop-entry-contains-unknown-key.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,11 @@ +Tag: desktop-entry-contains-unknown-key +Severity: warning +Check: menu-format +Info: The key on this line of the desktop entry is not one of the standard + keys defined in the FreeDesktop specification, not one of the legacy KDE + keywords, and one that does not begin with X-. It's most likely + that the key was misspelled. + . + The desktop-file-validate tool in the desktop-file-utils package is + useful for checking the syntax of desktop entries. +Ref: https://specifications.freedesktop.org/desktop-entry-spec/latest/ar01s06.html diff -Nru lintian-2.93.0/tags/d/desktop-entry-contains-unknown-key.tag lintian-2.89.0ubuntu1/tags/d/desktop-entry-contains-unknown-key.tag --- lintian-2.93.0/tags/d/desktop-entry-contains-unknown-key.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/desktop-entry-contains-unknown-key.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,11 +0,0 @@ -Tag: desktop-entry-contains-unknown-key -Severity: warning -Check: menu-format -Explanation: The key on this line of the desktop entry is not one of the standard - keys defined in the FreeDesktop specification, not one of the legacy KDE - keywords, and one that does not begin with X-. It's most likely - that the key was misspelled. - . - The desktop-file-validate tool in the desktop-file-utils package is - useful for checking the syntax of desktop entries. -See-Also: https://specifications.freedesktop.org/desktop-entry-spec/latest/ar01s06.html diff -Nru lintian-2.93.0/tags/d/desktop-entry-file-has-crs.desc lintian-2.89.0ubuntu1/tags/d/desktop-entry-file-has-crs.desc --- lintian-2.93.0/tags/d/desktop-entry-file-has-crs.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/desktop-entry-file-has-crs.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,12 @@ +Tag: desktop-entry-file-has-crs +Severity: warning +Check: menu-format +Info: The desktop entry file has lines ending in CRLF instead of just LF. + The Desktop Entry Specification is explicit that lines should end with + only LF. The CR may be taken by some software as part of the field. + . + Running the following command against the given file removes any + CR character in the file: + . + sed -i 's/\r//g' path/to/file +Ref: https://specifications.freedesktop.org/desktop-entry-spec/latest/ar01s03.html diff -Nru lintian-2.93.0/tags/d/desktop-entry-file-has-crs.tag lintian-2.89.0ubuntu1/tags/d/desktop-entry-file-has-crs.tag --- lintian-2.93.0/tags/d/desktop-entry-file-has-crs.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/desktop-entry-file-has-crs.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,12 +0,0 @@ -Tag: desktop-entry-file-has-crs -Severity: warning -Check: menu-format -Explanation: The desktop entry file has lines ending in CRLF instead of just LF. - The Desktop Entry Specification is explicit that lines should end with - only LF. The CR may be taken by some software as part of the field. - . - Running the following command against the given file removes any - CR character in the file: - . - sed -i 's/\r//g' path/to/file -See-Also: https://specifications.freedesktop.org/desktop-entry-spec/latest/ar01s03.html diff -Nru lintian-2.93.0/tags/d/desktop-entry-invalid-category.desc lintian-2.89.0ubuntu1/tags/d/desktop-entry-invalid-category.desc --- lintian-2.93.0/tags/d/desktop-entry-invalid-category.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/desktop-entry-invalid-category.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,12 @@ +Tag: desktop-entry-invalid-category +Severity: warning +Check: menu-format +Info: This desktop entry lists a category that is not one of the + registered Main or Additional Categories in the FreeDesktop + specification. Note that case is significant and whitespace is only + allowed immediately before and after the equal sign in the Category key, + not elsewhere in the field. + . + The desktop-file-validate tool in the desktop-file-utils package is + useful for checking the syntax of desktop entries. +Ref: https://specifications.freedesktop.org/menu-spec/latest/apa.html diff -Nru lintian-2.93.0/tags/d/desktop-entry-invalid-category.tag lintian-2.89.0ubuntu1/tags/d/desktop-entry-invalid-category.tag --- lintian-2.93.0/tags/d/desktop-entry-invalid-category.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/desktop-entry-invalid-category.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,12 +0,0 @@ -Tag: desktop-entry-invalid-category -Severity: warning -Check: menu-format -Explanation: This desktop entry lists a category that is not one of the - registered Main or Additional Categories in the FreeDesktop - specification. Note that case is significant and whitespace is only - allowed immediately before and after the equal sign in the Category key, - not elsewhere in the field. - . - The desktop-file-validate tool in the desktop-file-utils package is - useful for checking the syntax of desktop entries. -See-Also: https://specifications.freedesktop.org/menu-spec/latest/apa.html diff -Nru lintian-2.93.0/tags/d/desktop-entry-lacks-icon-entry.desc lintian-2.89.0ubuntu1/tags/d/desktop-entry-lacks-icon-entry.desc --- lintian-2.93.0/tags/d/desktop-entry-lacks-icon-entry.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/desktop-entry-lacks-icon-entry.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,15 @@ +Tag: desktop-entry-lacks-icon-entry +Severity: info +Check: menu-format +Info: This .desktop file does not contain an "Icon" entry. + . + "Icon" is the name of the file (without the extension) of the icon displayed + by this .desktop file. The icon is searched in the different icon themes. + If the name is an absolute path, the given file will be used. + The icon should be unique enough to help the user to recognise the application. + . + The desktop-file-validate tool in the desktop-file-utils package is + useful for checking the syntax of desktop entries. +Ref: https://specifications.freedesktop.org/desktop-entry-spec/latest/ar01s06.html, + https://specifications.freedesktop.org/icon-theme-spec/icon-theme-spec-latest.html, + #854132 diff -Nru lintian-2.93.0/tags/d/desktop-entry-lacks-icon-entry.tag lintian-2.89.0ubuntu1/tags/d/desktop-entry-lacks-icon-entry.tag --- lintian-2.93.0/tags/d/desktop-entry-lacks-icon-entry.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/desktop-entry-lacks-icon-entry.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,15 +0,0 @@ -Tag: desktop-entry-lacks-icon-entry -Severity: info -Check: menu-format -Explanation: This .desktop file does not contain an "Icon" entry. - . - "Icon" is the name of the file (without the extension) of the icon displayed - by this .desktop file. The icon is searched in the different icon themes. - If the name is an absolute path, the given file will be used. - The icon should be unique enough to help the user to recognise the application. - . - The desktop-file-validate tool in the desktop-file-utils package is - useful for checking the syntax of desktop entries. -See-Also: https://specifications.freedesktop.org/desktop-entry-spec/latest/ar01s06.html, - https://specifications.freedesktop.org/icon-theme-spec/icon-theme-spec-latest.html, - Bug#854132 diff -Nru lintian-2.93.0/tags/d/desktop-entry-lacks-keywords-entry.desc lintian-2.89.0ubuntu1/tags/d/desktop-entry-lacks-keywords-entry.desc --- lintian-2.93.0/tags/d/desktop-entry-lacks-keywords-entry.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/desktop-entry-lacks-keywords-entry.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,15 @@ +Tag: desktop-entry-lacks-keywords-entry +Severity: info +Check: menu-format +Info: This .desktop file does either not contain a "Keywords" entry or it does + not contain any keywords not already present in the "Name" or + "GenericName" entries. + . + .desktop files are organized in key/value pairs (similar to .ini files). + "Keywords" is the name of the entry/key in the .desktop file containing + keywords relevant for this .desktop file. + . + The desktop-file-validate tool in the desktop-file-utils package is + useful for checking the syntax of desktop entries. +Ref: https://specifications.freedesktop.org/desktop-entry-spec/latest/ar01s06.html, + #693918, https://wiki.gnome.org/Initiatives/GnomeGoals/DesktopFileKeywords diff -Nru lintian-2.93.0/tags/d/desktop-entry-lacks-keywords-entry.tag lintian-2.89.0ubuntu1/tags/d/desktop-entry-lacks-keywords-entry.tag --- lintian-2.93.0/tags/d/desktop-entry-lacks-keywords-entry.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/desktop-entry-lacks-keywords-entry.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,15 +0,0 @@ -Tag: desktop-entry-lacks-keywords-entry -Severity: info -Check: menu-format -Explanation: This .desktop file does either not contain a "Keywords" entry or it does - not contain any keywords not already present in the "Name" or - "GenericName" entries. - . - .desktop files are organized in key/value pairs (similar to .ini files). - "Keywords" is the name of the entry/key in the .desktop file containing - keywords relevant for this .desktop file. - . - The desktop-file-validate tool in the desktop-file-utils package is - useful for checking the syntax of desktop entries. -See-Also: https://specifications.freedesktop.org/desktop-entry-spec/latest/ar01s06.html, - Bug#693918, https://wiki.gnome.org/Initiatives/GnomeGoals/DesktopFileKeywords diff -Nru lintian-2.93.0/tags/d/desktop-entry-lacks-main-category.desc lintian-2.89.0ubuntu1/tags/d/desktop-entry-lacks-main-category.desc --- lintian-2.93.0/tags/d/desktop-entry-lacks-main-category.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/desktop-entry-lacks-main-category.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: desktop-entry-lacks-main-category +Severity: warning +Check: menu-format +Info: The categories for this desktop entry do not contain any Main + Categories, only Additional Categories. Additional Categories should + only be used on conjunction with one or more Main Categories. + . + The desktop-file-validate tool in the desktop-file-utils package is + useful for checking the syntax of desktop entries. +Ref: https://specifications.freedesktop.org/menu-spec/latest/apa.html diff -Nru lintian-2.93.0/tags/d/desktop-entry-lacks-main-category.tag lintian-2.89.0ubuntu1/tags/d/desktop-entry-lacks-main-category.tag --- lintian-2.93.0/tags/d/desktop-entry-lacks-main-category.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/desktop-entry-lacks-main-category.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,10 +0,0 @@ -Tag: desktop-entry-lacks-main-category -Severity: warning -Check: menu-format -Explanation: The categories for this desktop entry do not contain any Main - Categories, only Additional Categories. Additional Categories should - only be used on conjunction with one or more Main Categories. - . - The desktop-file-validate tool in the desktop-file-utils package is - useful for checking the syntax of desktop entries. -See-Also: https://specifications.freedesktop.org/menu-spec/latest/apa.html diff -Nru lintian-2.93.0/tags/d/desktop-entry-limited-to-environments.desc lintian-2.89.0ubuntu1/tags/d/desktop-entry-limited-to-environments.desc --- lintian-2.93.0/tags/d/desktop-entry-limited-to-environments.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/desktop-entry-limited-to-environments.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,12 @@ +Tag: desktop-entry-limited-to-environments +Severity: info +Certainty: wild-guess +Check: menu-format +Info: This desktop entry uses OnlyShowIn to limit the environments in + which it's displayed but lists multiple environments. This is often a + sign of a desktop file written assuming that only GNOME, KDE, and Xfce + are in use and the desktop file intended to exclude one of them. This + unintentionally hides the application from desktop environments such as + LXDE where it would work fine. If this application supports any desktop + environment except some specific ones, it should list the unsupported + environments in the NotShowIn key instead. diff -Nru lintian-2.93.0/tags/d/desktop-entry-limited-to-environments.tag lintian-2.89.0ubuntu1/tags/d/desktop-entry-limited-to-environments.tag --- lintian-2.93.0/tags/d/desktop-entry-limited-to-environments.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/desktop-entry-limited-to-environments.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,11 +0,0 @@ -Tag: desktop-entry-limited-to-environments -Severity: info -Check: menu-format -Explanation: This desktop entry uses OnlyShowIn to limit the environments in - which it's displayed but lists multiple environments. This is often a - sign of a desktop file written assuming that only GNOME, KDE, and Xfce - are in use and the desktop file intended to exclude one of them. This - unintentionally hides the application from desktop environments such as - LXDE where it would work fine. If this application supports any desktop - environment except some specific ones, it should list the unsupported - environments in the NotShowIn key instead. diff -Nru lintian-2.93.0/tags/d/desktop-entry-missing-required-key.desc lintian-2.89.0ubuntu1/tags/d/desktop-entry-missing-required-key.desc --- lintian-2.93.0/tags/d/desktop-entry-missing-required-key.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/desktop-entry-missing-required-key.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: desktop-entry-missing-required-key +Severity: error +Check: menu-format +Info: Desktop entries must contain, at a minimum, the keys Type and Name. + . + The desktop-file-validate tool in the desktop-file-utils package is + useful for checking the syntax of desktop entries. +Ref: https://specifications.freedesktop.org/desktop-entry-spec/latest/ar01s06.html diff -Nru lintian-2.93.0/tags/d/desktop-entry-missing-required-key.tag lintian-2.89.0ubuntu1/tags/d/desktop-entry-missing-required-key.tag --- lintian-2.93.0/tags/d/desktop-entry-missing-required-key.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/desktop-entry-missing-required-key.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: desktop-entry-missing-required-key -Severity: error -Check: menu-format -Explanation: Desktop entries must contain, at a minimum, the keys Type and Name. - . - The desktop-file-validate tool in the desktop-file-utils package is - useful for checking the syntax of desktop entries. -See-Also: https://specifications.freedesktop.org/desktop-entry-spec/latest/ar01s06.html diff -Nru lintian-2.93.0/tags/d/desktop-entry-unknown-type.desc lintian-2.89.0ubuntu1/tags/d/desktop-entry-unknown-type.desc --- lintian-2.93.0/tags/d/desktop-entry-unknown-type.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/desktop-entry-unknown-type.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,13 @@ +Tag: desktop-entry-unknown-type +Severity: warning +Check: menu-format +Info: This desktop entry uses a type that's not one of the currently + recognized values of "Application", "Link" or "Directory". + Implementations should ignore any unknown values but it's still likely + an error if you used something else and this check should be updated if + any new desktop file types start being used. Note that case is + significant. + . + The desktop-file-validate tool in the desktop-file-utils package is + useful for checking the syntax of desktop entries. +Ref: https://specifications.freedesktop.org/desktop-entry-spec/latest/ar01s06.html diff -Nru lintian-2.93.0/tags/d/desktop-entry-unknown-type.tag lintian-2.89.0ubuntu1/tags/d/desktop-entry-unknown-type.tag --- lintian-2.93.0/tags/d/desktop-entry-unknown-type.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/desktop-entry-unknown-type.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,13 +0,0 @@ -Tag: desktop-entry-unknown-type -Severity: warning -Check: menu-format -Explanation: This desktop entry uses a type that's not one of the currently - recognized values of "Application", "Link" or "Directory". - Implementations should ignore any unknown values but it's still likely - an error if you used something else and this check should be updated if - any new desktop file types start being used. Note that case is - significant. - . - The desktop-file-validate tool in the desktop-file-utils package is - useful for checking the syntax of desktop entries. -See-Also: https://specifications.freedesktop.org/desktop-entry-spec/latest/ar01s06.html diff -Nru lintian-2.93.0/tags/d/desktop-entry-uses-reserved-category.desc lintian-2.89.0ubuntu1/tags/d/desktop-entry-uses-reserved-category.desc --- lintian-2.93.0/tags/d/desktop-entry-uses-reserved-category.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/desktop-entry-uses-reserved-category.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,12 @@ +Tag: desktop-entry-uses-reserved-category +Severity: warning +Check: menu-format +Info: This desktop entry includes a Reserved Category, one which has a + desktop-specific meaning that has not yet been standardized, but does not + include an OnlyShowIn key. Desktop entries using a Reserved Category + must include an OnlyShowIn key limiting the entry to those environments + that support the category. + . + The desktop-file-validate tool in the desktop-file-utils package is + useful for checking the syntax of desktop entries. +Ref: https://specifications.freedesktop.org/menu-spec/latest/apa.html diff -Nru lintian-2.93.0/tags/d/desktop-entry-uses-reserved-category.tag lintian-2.89.0ubuntu1/tags/d/desktop-entry-uses-reserved-category.tag --- lintian-2.93.0/tags/d/desktop-entry-uses-reserved-category.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/desktop-entry-uses-reserved-category.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,12 +0,0 @@ -Tag: desktop-entry-uses-reserved-category -Severity: warning -Check: menu-format -Explanation: This desktop entry includes a Reserved Category, one which has a - desktop-specific meaning that has not yet been standardized, but does not - include an OnlyShowIn key. Desktop entries using a Reserved Category - must include an OnlyShowIn key limiting the entry to those environments - that support the category. - . - The desktop-file-validate tool in the desktop-file-utils package is - useful for checking the syntax of desktop entries. -See-Also: https://specifications.freedesktop.org/menu-spec/latest/apa.html diff -Nru lintian-2.93.0/tags/d/desktop-file-in-wrong-dir.desc lintian-2.89.0ubuntu1/tags/d/desktop-file-in-wrong-dir.desc --- lintian-2.93.0/tags/d/desktop-file-in-wrong-dir.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/desktop-file-in-wrong-dir.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: desktop-file-in-wrong-dir +Severity: warning +Check: files/desktop +Info: The package contains a .desktop file in an obsolete directory. + According to the menu-spec draft on freedesktop.org, those .desktop files + that are intended to create a menu should be placed in + /usr/share/applications, not /usr/share/gnome/apps. diff -Nru lintian-2.93.0/tags/d/desktop-file-in-wrong-dir.tag lintian-2.89.0ubuntu1/tags/d/desktop-file-in-wrong-dir.tag --- lintian-2.93.0/tags/d/desktop-file-in-wrong-dir.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/desktop-file-in-wrong-dir.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: desktop-file-in-wrong-dir -Severity: warning -Check: files/desktop -Explanation: The package contains a .desktop file in an obsolete directory. - According to the menu-spec draft on freedesktop.org, those .desktop files - that are intended to create a menu should be placed in - /usr/share/applications, not /usr/share/gnome/apps. diff -Nru lintian-2.93.0/tags/d/desktop-mime-but-no-exec-code.desc lintian-2.89.0ubuntu1/tags/d/desktop-mime-but-no-exec-code.desc --- lintian-2.93.0/tags/d/desktop-mime-but-no-exec-code.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/desktop-mime-but-no-exec-code.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: desktop-mime-but-no-exec-code +Severity: warning +Certainty: possible +Check: menu-format +Info: The desktop entry lists support for at least one mime type, but does not + provide codes like %f, %F, %u or %U for the Exec key. + . + If the application can indeed handle files of the listed mime types, it should + specify a way to pass the filenames as parameters. diff -Nru lintian-2.93.0/tags/d/desktop-mime-but-no-exec-code.tag lintian-2.89.0ubuntu1/tags/d/desktop-mime-but-no-exec-code.tag --- lintian-2.93.0/tags/d/desktop-mime-but-no-exec-code.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/desktop-mime-but-no-exec-code.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: desktop-mime-but-no-exec-code -Severity: warning -Check: menu-format -Explanation: The desktop entry lists support for at least one mime type, but does not - provide codes like %f, %F, %u or %U for the Exec key. - . - If the application can indeed handle files of the listed mime types, it should - specify a way to pass the filenames as parameters. diff -Nru lintian-2.93.0/tags/d/development-package-ships-elf-binary-in-path.desc lintian-2.89.0ubuntu1/tags/d/development-package-ships-elf-binary-in-path.desc --- lintian-2.93.0/tags/d/development-package-ships-elf-binary-in-path.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/development-package-ships-elf-binary-in-path.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,21 @@ +Tag: development-package-ships-elf-binary-in-path +Severity: info +Certainty: possible +Check: binaries +Experimental: yes +Info: This development package (ie. from the libdevel section of + the archive) installs an ELF binary within $PATH. + . + Commonly, executables in development packages provide values that are + relevant for using the library. Source packages that use such + development packages tend to execute those executables to discover how + to use the library. + . + When performing a cross build, host architecture binaries are generally not + executable. However, development packages need to be installed on the host + architecture so such files are useless. + . + An alternative approach is to use pkg-config(1) or potentially + splitting architecture-independent development tools into a separate + package that can be marked Multi-Arch: foreign. +Ref: #794295, #794103 diff -Nru lintian-2.93.0/tags/d/development-package-ships-elf-binary-in-path.tag lintian-2.89.0ubuntu1/tags/d/development-package-ships-elf-binary-in-path.tag --- lintian-2.93.0/tags/d/development-package-ships-elf-binary-in-path.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/development-package-ships-elf-binary-in-path.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,20 +0,0 @@ -Tag: development-package-ships-elf-binary-in-path -Severity: info -Check: binaries -Experimental: yes -Explanation: This development package (ie. from the libdevel section of - the archive) installs an ELF binary within $PATH. - . - Commonly, executables in development packages provide values that are - relevant for using the library. Source packages that use such - development packages tend to execute those executables to discover how - to use the library. - . - When performing a cross build, host architecture binaries are generally not - executable. However, development packages need to be installed on the host - architecture so such files are useless. - . - An alternative approach is to use pkg-config(1) or potentially - splitting architecture-independent development tools into a separate - package that can be marked Multi-Arch: foreign. -See-Also: Bug#794295, Bug#794103 diff -Nru lintian-2.93.0/tags/d/dfsg-version-in-native-package.desc lintian-2.89.0ubuntu1/tags/d/dfsg-version-in-native-package.desc --- lintian-2.93.0/tags/d/dfsg-version-in-native-package.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/dfsg-version-in-native-package.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: dfsg-version-in-native-package +Severity: warning +Check: fields/version +Info: The version number of this package contains "dfsg", but it's a + native package. "dfsg" is conventionally used in the upstream version of + packages that are repackaged for Debian Free Software Guidelines + compliance reasons. The convention doesn't make sense in native + packages. diff -Nru lintian-2.93.0/tags/d/dfsg-version-in-native-package.tag lintian-2.89.0ubuntu1/tags/d/dfsg-version-in-native-package.tag --- lintian-2.93.0/tags/d/dfsg-version-in-native-package.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/dfsg-version-in-native-package.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: dfsg-version-in-native-package -Severity: warning -Check: fields/version -Explanation: The version number of this package contains "dfsg", but it's a - native package. "dfsg" is conventionally used in the upstream version of - packages that are repackaged for Debian Free Software Guidelines - compliance reasons. The convention doesn't make sense in native - packages. diff -Nru lintian-2.93.0/tags/d/dfsg-version-misspelled.desc lintian-2.89.0ubuntu1/tags/d/dfsg-version-misspelled.desc --- lintian-2.93.0/tags/d/dfsg-version-misspelled.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/dfsg-version-misspelled.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: dfsg-version-misspelled +Severity: warning +Check: fields/version +Info: The version number of this package contains "dsfg". You probably + meant "dfsg", the conventional marker for upstream packages that are + repackaged for Debian Free Software Guidelines compliance reasons. diff -Nru lintian-2.93.0/tags/d/dfsg-version-misspelled.tag lintian-2.89.0ubuntu1/tags/d/dfsg-version-misspelled.tag --- lintian-2.93.0/tags/d/dfsg-version-misspelled.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/dfsg-version-misspelled.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: dfsg-version-misspelled -Severity: warning -Check: fields/version -Explanation: The version number of this package contains "dsfg". You probably - meant "dfsg", the conventional marker for upstream packages that are - repackaged for Debian Free Software Guidelines compliance reasons. diff -Nru lintian-2.93.0/tags/d/dfsg-version-with-period.desc lintian-2.89.0ubuntu1/tags/d/dfsg-version-with-period.desc --- lintian-2.93.0/tags/d/dfsg-version-with-period.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/dfsg-version-with-period.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,13 @@ +Tag: dfsg-version-with-period +Severity: info +Certainty: possible +Check: fields/version +Info: The version number of this package contains ".dfsg", probably in a + form like "1.2.dfsg1". There is a subtle sorting problem with this + version method: 1.2.dfsg1 is considered a later version than 1.2.1. If + upstream adds another level to its versioning, finding a good version + number for the next upstream release will be awkward. + . + Upstream may never do this, in which case this isn't a problem, but it's + normally better to use "+dfsg" instead (such as "1.2+dfsg1"). "+" sorts + before ".", so 1.2 < 1.2+dfsg1 < 1.2.1 as normally desired. diff -Nru lintian-2.93.0/tags/d/dfsg-version-with-period.tag lintian-2.89.0ubuntu1/tags/d/dfsg-version-with-period.tag --- lintian-2.93.0/tags/d/dfsg-version-with-period.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/dfsg-version-with-period.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,12 +0,0 @@ -Tag: dfsg-version-with-period -Severity: info -Check: fields/version -Explanation: The version number of this package contains ".dfsg", probably in a - form like "1.2.dfsg1". There is a subtle sorting problem with this - version method: 1.2.dfsg1 is considered a later version than 1.2.1. If - upstream adds another level to its versioning, finding a good version - number for the next upstream release will be awkward. - . - Upstream may never do this, in which case this isn't a problem, but it's - normally better to use "+dfsg" instead (such as "1.2+dfsg1"). "+" sorts - before ".", so 1.2 < 1.2+dfsg1 < 1.2.1 as normally desired. diff -Nru lintian-2.93.0/tags/d/dh-clean-k-is-deprecated.desc lintian-2.89.0ubuntu1/tags/d/dh-clean-k-is-deprecated.desc --- lintian-2.93.0/tags/d/dh-clean-k-is-deprecated.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/dh-clean-k-is-deprecated.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: dh-clean-k-is-deprecated +Severity: warning +Check: debhelper +Ref: dh_clean(1) +Info: This package calls dh_clean -k in its debian/rules file + instead of dh_prep. diff -Nru lintian-2.93.0/tags/d/dh-clean-k-is-deprecated.tag lintian-2.89.0ubuntu1/tags/d/dh-clean-k-is-deprecated.tag --- lintian-2.93.0/tags/d/dh-clean-k-is-deprecated.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/dh-clean-k-is-deprecated.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: dh-clean-k-is-deprecated -Severity: warning -Check: debhelper -See-Also: dh_clean(1) -Explanation: This package calls dh_clean -k in its debian/rules file - instead of dh_prep. diff -Nru lintian-2.93.0/tags/d/dh-exec-install-not-allowed-here.desc lintian-2.89.0ubuntu1/tags/d/dh-exec-install-not-allowed-here.desc --- lintian-2.93.0/tags/d/dh-exec-install-not-allowed-here.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/dh-exec-install-not-allowed-here.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: dh-exec-install-not-allowed-here +Severity: error +Certainty: possible +Check: debhelper +Info: The package uses a dh-exec-install construct in a debhelper + config file, where it is not permitted. + . + The dh-exec-install constructs are only allowed in dh_install's + .install and dh_installman's .manpages files, and nowhere else. diff -Nru lintian-2.93.0/tags/d/dh-exec-install-not-allowed-here.tag lintian-2.89.0ubuntu1/tags/d/dh-exec-install-not-allowed-here.tag --- lintian-2.93.0/tags/d/dh-exec-install-not-allowed-here.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/dh-exec-install-not-allowed-here.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: dh-exec-install-not-allowed-here -Severity: error -Check: debhelper -Explanation: The package uses a dh-exec-install construct in a debhelper - config file, where it is not permitted. - . - The dh-exec-install constructs are only allowed in dh_install's - .install and dh_installman's .manpages files, and nowhere else. diff -Nru lintian-2.93.0/tags/d/dh-exec-private-helper.desc lintian-2.89.0ubuntu1/tags/d/dh-exec-private-helper.desc --- lintian-2.93.0/tags/d/dh-exec-private-helper.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/dh-exec-private-helper.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: dh-exec-private-helper +Severity: error +Check: debhelper +Info: The packaging file uses dh-exec, but it does not use /usr/bin/dh-exec. + . + If running dh-exec with the default set of helpers is not desired, + use its --with or --without options instead of directly using the + desired helper. diff -Nru lintian-2.93.0/tags/d/dh-exec-private-helper.tag lintian-2.89.0ubuntu1/tags/d/dh-exec-private-helper.tag --- lintian-2.93.0/tags/d/dh-exec-private-helper.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/dh-exec-private-helper.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: dh-exec-private-helper -Severity: error -Check: debhelper -Explanation: The packaging file uses dh-exec, but it does not use /usr/bin/dh-exec. - . - If running dh-exec with the default set of helpers is not desired, - use its --with or --without options instead of directly using the - desired helper. diff -Nru lintian-2.93.0/tags/d/dh-exec-script-without-dh-exec-features.desc lintian-2.89.0ubuntu1/tags/d/dh-exec-script-without-dh-exec-features.desc --- lintian-2.93.0/tags/d/dh-exec-script-without-dh-exec-features.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/dh-exec-script-without-dh-exec-features.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: dh-exec-script-without-dh-exec-features +Severity: warning +Certainty: possible +Check: debhelper +Info: The package uses dh-exec in at least one of its files, but does + not use any of the features provided by dh-exec. + . + If the features provided by dh-exec is not needed, please remove the + executable bit, and the dh-exec usage. diff -Nru lintian-2.93.0/tags/d/dh-exec-script-without-dh-exec-features.tag lintian-2.89.0ubuntu1/tags/d/dh-exec-script-without-dh-exec-features.tag --- lintian-2.93.0/tags/d/dh-exec-script-without-dh-exec-features.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/dh-exec-script-without-dh-exec-features.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: dh-exec-script-without-dh-exec-features -Severity: warning -Check: debhelper -Explanation: The package uses dh-exec in at least one of its files, but does - not use any of the features provided by dh-exec. - . - If the features provided by dh-exec is not needed, please remove the - executable bit, and the dh-exec usage. diff -Nru lintian-2.93.0/tags/d/dh-exec-subst-unknown-variable.desc lintian-2.89.0ubuntu1/tags/d/dh-exec-subst-unknown-variable.desc --- lintian-2.93.0/tags/d/dh-exec-subst-unknown-variable.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/dh-exec-subst-unknown-variable.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,11 @@ +Tag: dh-exec-subst-unknown-variable +Severity: info +Certainty: wild-guess +Check: debhelper +Info: The package uses a variable in one of its debhelper config + files, but the variable is not one known to dpkg-architecture. + . + It is recommended to use a known subset of variables. If the package + needs more than that, and makes sure the variable is exported through + the build one way or the other, then this tag can be safely ignored + or overridden. diff -Nru lintian-2.93.0/tags/d/dh-exec-subst-unknown-variable.tag lintian-2.89.0ubuntu1/tags/d/dh-exec-subst-unknown-variable.tag --- lintian-2.93.0/tags/d/dh-exec-subst-unknown-variable.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/dh-exec-subst-unknown-variable.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,10 +0,0 @@ -Tag: dh-exec-subst-unknown-variable -Severity: info -Check: debhelper -Explanation: The package uses a variable in one of its debhelper config - files, but the variable is not one known to dpkg-architecture. - . - It is recommended to use a known subset of variables. If the package - needs more than that, and makes sure the variable is exported through - the build one way or the other, then this tag can be safely ignored - or overridden. diff -Nru lintian-2.93.0/tags/d/dh-exec-useless-usage.desc lintian-2.89.0ubuntu1/tags/d/dh-exec-useless-usage.desc --- lintian-2.93.0/tags/d/dh-exec-useless-usage.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/dh-exec-useless-usage.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,20 @@ +Tag: dh-exec-useless-usage +Severity: info +Certainty: possible +Check: debhelper +Info: The package uses dh-exec for things it is not needed for. + . + This typically includes using ${DEB_HOST_MULTIARCH} in an install + target where a wildcard would suffice. For example, if you had: + . + #! /usr/bin/dh-exec + usr/lib/${DEB_HOST_MULTIARCH} + . + This could be replaced with the following in most cases, dropping the + need for dh-exec: + . + usr/lib/* + . + However, there may be other directories that match the wildcard, + which one does not wish to install. In that case, this warning should + be ignored or overridden. diff -Nru lintian-2.93.0/tags/d/dh-exec-useless-usage.tag lintian-2.89.0ubuntu1/tags/d/dh-exec-useless-usage.tag --- lintian-2.93.0/tags/d/dh-exec-useless-usage.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/dh-exec-useless-usage.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,19 +0,0 @@ -Tag: dh-exec-useless-usage -Severity: info -Check: debhelper -Explanation: The package uses dh-exec for things it is not needed for. - . - This typically includes using ${DEB_HOST_MULTIARCH} in an install - target where a wildcard would suffice. For example, if you had: - . - #! /usr/bin/dh-exec - usr/lib/${DEB_HOST_MULTIARCH} - . - This could be replaced with the following in most cases, dropping the - need for dh-exec: - . - usr/lib/* - . - However, there may be other directories that match the wildcard, - which one does not wish to install. In that case, this warning should - be ignored or overridden. diff -Nru lintian-2.93.0/tags/d/dh_installmanpages-is-obsolete.desc lintian-2.89.0ubuntu1/tags/d/dh_installmanpages-is-obsolete.desc --- lintian-2.93.0/tags/d/dh_installmanpages-is-obsolete.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/dh_installmanpages-is-obsolete.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: dh_installmanpages-is-obsolete +Severity: warning +Check: debhelper +Ref: dh_installmanpages(1) +Info: This package calls dh_installmanpages in its debian/rules file. + dh_installmanpages is deprecated in favour of dh_installman. diff -Nru lintian-2.93.0/tags/d/dh_installmanpages-is-obsolete.tag lintian-2.89.0ubuntu1/tags/d/dh_installmanpages-is-obsolete.tag --- lintian-2.93.0/tags/d/dh_installmanpages-is-obsolete.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/dh_installmanpages-is-obsolete.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: dh_installmanpages-is-obsolete -Severity: warning -Check: debhelper -See-Also: dh_installmanpages(1) -Explanation: This package calls dh_installmanpages in its debian/rules file. - dh_installmanpages is deprecated in favour of dh_installman. diff -Nru lintian-2.93.0/tags/d/dh-make-template-in-source.desc lintian-2.89.0ubuntu1/tags/d/dh-make-template-in-source.desc --- lintian-2.93.0/tags/d/dh-make-template-in-source.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/dh-make-template-in-source.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: dh-make-template-in-source +Severity: warning +Certainty: possible +Check: debhelper +Info: This package contains debian/*.ex and/or debian/ex.* files + installed by dh_make. These are intended to be filled in with the + package's details and renamed for use by various debhelper commands. + If they are not being used, they should be removed. diff -Nru lintian-2.93.0/tags/d/dh-make-template-in-source.tag lintian-2.89.0ubuntu1/tags/d/dh-make-template-in-source.tag --- lintian-2.93.0/tags/d/dh-make-template-in-source.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/dh-make-template-in-source.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: dh-make-template-in-source -Severity: warning -Check: debhelper -Explanation: This package contains debian/*.ex and/or debian/ex.* files - installed by dh_make. These are intended to be filled in with the - package's details and renamed for use by various debhelper commands. - If they are not being used, they should be removed. diff -Nru lintian-2.93.0/tags/d/dh-quilt-addon-but-quilt-source-format.desc lintian-2.89.0ubuntu1/tags/d/dh-quilt-addon-but-quilt-source-format.desc --- lintian-2.93.0/tags/d/dh-quilt-addon-but-quilt-source-format.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/dh-quilt-addon-but-quilt-source-format.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: dh-quilt-addon-but-quilt-source-format +Severity: warning +Check: debhelper +Info: The package uses (for example) dh $@ --with quilt in + debian/rules but is already using the 3.0 (quilt) + source format via the debian/source/format file. + . + Please remove the --with quilt argument. diff -Nru lintian-2.93.0/tags/d/dh-quilt-addon-but-quilt-source-format.tag lintian-2.89.0ubuntu1/tags/d/dh-quilt-addon-but-quilt-source-format.tag --- lintian-2.93.0/tags/d/dh-quilt-addon-but-quilt-source-format.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/dh-quilt-addon-but-quilt-source-format.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: dh-quilt-addon-but-quilt-source-format -Severity: warning -Check: debhelper -Explanation: The package uses (for example) dh $@ --with quilt in - debian/rules but is already using the 3.0 (quilt) - source format via the debian/source/format file. - . - Please remove the --with quilt argument. diff -Nru lintian-2.93.0/tags/d/diff-contains-arch-control-dir.desc lintian-2.89.0ubuntu1/tags/d/diff-contains-arch-control-dir.desc --- lintian-2.93.0/tags/d/diff-contains-arch-control-dir.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/diff-contains-arch-control-dir.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,11 @@ +Tag: diff-contains-arch-control-dir +Severity: warning +Check: cruft +Info: The Debian diff or native package contains files in an {arch} or + .arch-ids directory or a directory starting with ,, (used by baz + for debugging traces). These are usually artifacts of the revision + control system used by the Debian maintainer and not useful in a diff or + native package. dpkg-source will automatically exclude these if + it is passed -I or -i for native and non-native + packages respectively. +Ref: dpkg-source(1) diff -Nru lintian-2.93.0/tags/d/diff-contains-arch-control-dir.tag lintian-2.89.0ubuntu1/tags/d/diff-contains-arch-control-dir.tag --- lintian-2.93.0/tags/d/diff-contains-arch-control-dir.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/diff-contains-arch-control-dir.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,11 +0,0 @@ -Tag: diff-contains-arch-control-dir -Severity: warning -Check: cruft -Explanation: The Debian diff or native package contains files in an {arch} or - .arch-ids directory or a directory starting with ,, (used by baz - for debugging traces). These are usually artifacts of the revision - control system used by the Debian maintainer and not useful in a diff or - native package. dpkg-source will automatically exclude these if - it is passed -I or -i for native and non-native - packages respectively. -See-Also: dpkg-source(1) diff -Nru lintian-2.93.0/tags/d/diff-contains-arch-inventory-file.desc lintian-2.89.0ubuntu1/tags/d/diff-contains-arch-inventory-file.desc --- lintian-2.93.0/tags/d/diff-contains-arch-inventory-file.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/diff-contains-arch-inventory-file.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: diff-contains-arch-inventory-file +Severity: warning +Check: cruft +Info: The Debian diff or native package contains an + .arch-inventory file. This is Arch metadata that should + normally not be distributed. diff -Nru lintian-2.93.0/tags/d/diff-contains-arch-inventory-file.tag lintian-2.89.0ubuntu1/tags/d/diff-contains-arch-inventory-file.tag --- lintian-2.93.0/tags/d/diff-contains-arch-inventory-file.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/diff-contains-arch-inventory-file.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: diff-contains-arch-inventory-file -Severity: warning -Check: cruft -Explanation: The Debian diff or native package contains an - .arch-inventory file. This is Arch metadata that should - normally not be distributed. diff -Nru lintian-2.93.0/tags/d/diff-contains-bts-control-dir.desc lintian-2.89.0ubuntu1/tags/d/diff-contains-bts-control-dir.desc --- lintian-2.93.0/tags/d/diff-contains-bts-control-dir.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/diff-contains-bts-control-dir.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: diff-contains-bts-control-dir +Severity: warning +Check: cruft +Info: The Debian diff or native package contains files in a directory + used by a bug tracking system, which are not useful in a diff or native + package. dpkg-source will automatically exclude these if it + is passed -I or -i for native and non-native packages + respectively. +Ref: dpkg-source(1) diff -Nru lintian-2.93.0/tags/d/diff-contains-bts-control-dir.tag lintian-2.89.0ubuntu1/tags/d/diff-contains-bts-control-dir.tag --- lintian-2.93.0/tags/d/diff-contains-bts-control-dir.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/diff-contains-bts-control-dir.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: diff-contains-bts-control-dir -Severity: warning -Check: cruft -Explanation: The Debian diff or native package contains files in a directory - used by a bug tracking system, which are not useful in a diff or native - package. dpkg-source will automatically exclude these if it - is passed -I or -i for native and non-native packages - respectively. -See-Also: dpkg-source(1) diff -Nru lintian-2.93.0/tags/d/diff-contains-bzr-control-dir.desc lintian-2.89.0ubuntu1/tags/d/diff-contains-bzr-control-dir.desc --- lintian-2.93.0/tags/d/diff-contains-bzr-control-dir.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/diff-contains-bzr-control-dir.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: diff-contains-bzr-control-dir +Severity: warning +Check: cruft +Info: The Debian diff or native package contains files in a .bzr + directory. These are usually artifacts of the revision control system + used by the Debian maintainer and not useful in a diff or native package. + dpkg-source will automatically exclude these if it is passed + -I or -i for native and non-native packages respectively. +Ref: dpkg-source(1) diff -Nru lintian-2.93.0/tags/d/diff-contains-bzr-control-dir.tag lintian-2.89.0ubuntu1/tags/d/diff-contains-bzr-control-dir.tag --- lintian-2.93.0/tags/d/diff-contains-bzr-control-dir.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/diff-contains-bzr-control-dir.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: diff-contains-bzr-control-dir -Severity: warning -Check: cruft -Explanation: The Debian diff or native package contains files in a .bzr - directory. These are usually artifacts of the revision control system - used by the Debian maintainer and not useful in a diff or native package. - dpkg-source will automatically exclude these if it is passed - -I or -i for native and non-native packages respectively. -See-Also: dpkg-source(1) diff -Nru lintian-2.93.0/tags/d/diff-contains-cmake-cache-file.desc lintian-2.89.0ubuntu1/tags/d/diff-contains-cmake-cache-file.desc --- lintian-2.93.0/tags/d/diff-contains-cmake-cache-file.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/diff-contains-cmake-cache-file.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,11 @@ +Tag: diff-contains-cmake-cache-file +Severity: error +Certainty: possible +Check: cruft +Info: The Debian diff contains a CMake cache file. These files embed the + full path of the source tree in which they're created and cause build + failures if they exist when the source is built under a different path, + so they will always cause errors on the buildds. The file was probably + accidentally included. If it is present in the upstream source, don't + modify it in the Debian diff; instead, delete it before the build in + debian/rules. diff -Nru lintian-2.93.0/tags/d/diff-contains-cmake-cache-file.tag lintian-2.89.0ubuntu1/tags/d/diff-contains-cmake-cache-file.tag --- lintian-2.93.0/tags/d/diff-contains-cmake-cache-file.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/diff-contains-cmake-cache-file.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,10 +0,0 @@ -Tag: diff-contains-cmake-cache-file -Severity: error -Check: cruft -Explanation: The Debian diff contains a CMake cache file. These files embed the - full path of the source tree in which they're created and cause build - failures if they exist when the source is built under a different path, - so they will always cause errors on the buildds. The file was probably - accidentally included. If it is present in the upstream source, don't - modify it in the Debian diff; instead, delete it before the build in - debian/rules. diff -Nru lintian-2.93.0/tags/d/diff-contains-cvs-conflict-copy.desc lintian-2.89.0ubuntu1/tags/d/diff-contains-cvs-conflict-copy.desc --- lintian-2.93.0/tags/d/diff-contains-cvs-conflict-copy.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/diff-contains-cvs-conflict-copy.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: diff-contains-cvs-conflict-copy +Severity: warning +Check: cruft +Info: The Debian diff or native package contains a CVS conflict copy. + These have file names like .#file.version and are generated by + CVS when a conflict was detected when merging local changes with updates + from a source repository. They're useful only while resolving the + conflict and should not be included in the package. diff -Nru lintian-2.93.0/tags/d/diff-contains-cvs-conflict-copy.tag lintian-2.89.0ubuntu1/tags/d/diff-contains-cvs-conflict-copy.tag --- lintian-2.93.0/tags/d/diff-contains-cvs-conflict-copy.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/diff-contains-cvs-conflict-copy.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: diff-contains-cvs-conflict-copy -Severity: warning -Check: cruft -Explanation: The Debian diff or native package contains a CVS conflict copy. - These have file names like .#file.version and are generated by - CVS when a conflict was detected when merging local changes with updates - from a source repository. They're useful only while resolving the - conflict and should not be included in the package. diff -Nru lintian-2.93.0/tags/d/diff-contains-cvs-control-dir.desc lintian-2.89.0ubuntu1/tags/d/diff-contains-cvs-control-dir.desc --- lintian-2.93.0/tags/d/diff-contains-cvs-control-dir.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/diff-contains-cvs-control-dir.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: diff-contains-cvs-control-dir +Severity: warning +Check: cruft +Info: The Debian diff or native package contains files in a CVS directory. + These are usually artifacts of the revision control system used by the + Debian maintainer and not useful in a diff or native package. + dpkg-source will automatically exclude these if it is passed + -I or -i for native and non-native packages respectively. +Ref: dpkg-source(1) diff -Nru lintian-2.93.0/tags/d/diff-contains-cvs-control-dir.tag lintian-2.89.0ubuntu1/tags/d/diff-contains-cvs-control-dir.tag --- lintian-2.93.0/tags/d/diff-contains-cvs-control-dir.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/diff-contains-cvs-control-dir.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: diff-contains-cvs-control-dir -Severity: warning -Check: cruft -Explanation: The Debian diff or native package contains files in a CVS directory. - These are usually artifacts of the revision control system used by the - Debian maintainer and not useful in a diff or native package. - dpkg-source will automatically exclude these if it is passed - -I or -i for native and non-native packages respectively. -See-Also: dpkg-source(1) diff -Nru lintian-2.93.0/tags/d/diff-contains-editor-backup-file.desc lintian-2.89.0ubuntu1/tags/d/diff-contains-editor-backup-file.desc --- lintian-2.93.0/tags/d/diff-contains-editor-backup-file.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/diff-contains-editor-backup-file.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: diff-contains-editor-backup-file +Severity: warning +Check: cruft +Info: The Debian diff or native package contains a file ending in + ~ or of the form .xxx.swp, which is normally either an + Emacs or vim backup file or a backup file created by programs such as + autoheader or debconf-updatepo. This usually causes no + harm, but it's messy and bloats the size of the Debian diff to no useful + purpose. diff -Nru lintian-2.93.0/tags/d/diff-contains-editor-backup-file.tag lintian-2.89.0ubuntu1/tags/d/diff-contains-editor-backup-file.tag --- lintian-2.93.0/tags/d/diff-contains-editor-backup-file.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/diff-contains-editor-backup-file.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: diff-contains-editor-backup-file -Severity: warning -Check: cruft -Explanation: The Debian diff or native package contains a file ending in - ~ or of the form .xxx.swp, which is normally either an - Emacs or vim backup file or a backup file created by programs such as - autoheader or debconf-updatepo. This usually causes no - harm, but it's messy and bloats the size of the Debian diff to no useful - purpose. diff -Nru lintian-2.93.0/tags/d/diff-contains-git-control-dir.desc lintian-2.89.0ubuntu1/tags/d/diff-contains-git-control-dir.desc --- lintian-2.93.0/tags/d/diff-contains-git-control-dir.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/diff-contains-git-control-dir.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: diff-contains-git-control-dir +Severity: warning +Check: cruft +Info: The Debian diff or native package contains files in a .git + directory. These are usually artifacts of the revision control system + used by the Debian maintainer and not useful in a diff or native package. + dpkg-source will automatically exclude these if it is passed + -I or -i for native and non-native packages respectively. +Ref: dpkg-source(1) diff -Nru lintian-2.93.0/tags/d/diff-contains-git-control-dir.tag lintian-2.89.0ubuntu1/tags/d/diff-contains-git-control-dir.tag --- lintian-2.93.0/tags/d/diff-contains-git-control-dir.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/diff-contains-git-control-dir.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: diff-contains-git-control-dir -Severity: warning -Check: cruft -Explanation: The Debian diff or native package contains files in a .git - directory. These are usually artifacts of the revision control system - used by the Debian maintainer and not useful in a diff or native package. - dpkg-source will automatically exclude these if it is passed - -I or -i for native and non-native packages respectively. -See-Also: dpkg-source(1) diff -Nru lintian-2.93.0/tags/d/diff-contains-hg-control-dir.desc lintian-2.89.0ubuntu1/tags/d/diff-contains-hg-control-dir.desc --- lintian-2.93.0/tags/d/diff-contains-hg-control-dir.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/diff-contains-hg-control-dir.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: diff-contains-hg-control-dir +Severity: warning +Check: cruft +Info: The Debian diff or native package contains files in a .hg + directory. These are usually artifacts of the revision control system + used by the Debian maintainer and not useful in a diff or native package. + dpkg-source will automatically exclude these if it is passed + -I or -i for native and non-native packages respectively. +Ref: dpkg-source(1) diff -Nru lintian-2.93.0/tags/d/diff-contains-hg-control-dir.tag lintian-2.89.0ubuntu1/tags/d/diff-contains-hg-control-dir.tag --- lintian-2.93.0/tags/d/diff-contains-hg-control-dir.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/diff-contains-hg-control-dir.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: diff-contains-hg-control-dir -Severity: warning -Check: cruft -Explanation: The Debian diff or native package contains files in a .hg - directory. These are usually artifacts of the revision control system - used by the Debian maintainer and not useful in a diff or native package. - dpkg-source will automatically exclude these if it is passed - -I or -i for native and non-native packages respectively. -See-Also: dpkg-source(1) diff -Nru lintian-2.93.0/tags/d/diff-contains-hg-tags-file.desc lintian-2.89.0ubuntu1/tags/d/diff-contains-hg-tags-file.desc --- lintian-2.93.0/tags/d/diff-contains-hg-tags-file.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/diff-contains-hg-tags-file.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: diff-contains-hg-tags-file +Severity: warning +Check: cruft +Info: The Debian diff or native package contains an .hgtags + file. This file is Mercurial metadata that should normally not be + distributed. It stores hashes of tagged commits in a Mercurial + repository and isn't therefore useful without the repository. diff -Nru lintian-2.93.0/tags/d/diff-contains-hg-tags-file.tag lintian-2.89.0ubuntu1/tags/d/diff-contains-hg-tags-file.tag --- lintian-2.93.0/tags/d/diff-contains-hg-tags-file.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/diff-contains-hg-tags-file.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: diff-contains-hg-tags-file -Severity: warning -Check: cruft -Explanation: The Debian diff or native package contains an .hgtags - file. This file is Mercurial metadata that should normally not be - distributed. It stores hashes of tagged commits in a Mercurial - repository and isn't therefore useful without the repository. diff -Nru lintian-2.93.0/tags/d/diff-contains-patch-failure-file.desc lintian-2.89.0ubuntu1/tags/d/diff-contains-patch-failure-file.desc --- lintian-2.93.0/tags/d/diff-contains-patch-failure-file.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/diff-contains-patch-failure-file.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: diff-contains-patch-failure-file +Severity: warning +Certainty: possible +Check: cruft +Info: The Debian diff or native package contains a file that looks like + the files left behind by the patch utility when it cannot + completely apply a diff. This may be left over from a patch applied by + the maintainer. Normally such files should not be included in the + package. diff -Nru lintian-2.93.0/tags/d/diff-contains-patch-failure-file.tag lintian-2.89.0ubuntu1/tags/d/diff-contains-patch-failure-file.tag --- lintian-2.93.0/tags/d/diff-contains-patch-failure-file.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/diff-contains-patch-failure-file.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: diff-contains-patch-failure-file -Severity: warning -Check: cruft -Explanation: The Debian diff or native package contains a file that looks like - the files left behind by the patch utility when it cannot - completely apply a diff. This may be left over from a patch applied by - the maintainer. Normally such files should not be included in the - package. diff -Nru lintian-2.93.0/tags/d/diff-contains-quilt-control-dir.desc lintian-2.89.0ubuntu1/tags/d/diff-contains-quilt-control-dir.desc --- lintian-2.93.0/tags/d/diff-contains-quilt-control-dir.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/diff-contains-quilt-control-dir.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: diff-contains-quilt-control-dir +Severity: warning +Check: cruft +Info: The Debian diff or native package contains files in a directory + used by quilt, which are not useful in a diff or native package. + dpkg-source will automatically exclude these if it is passed + -I or -i for native and non-native packages + respectively. +Ref: dpkg-source(1) diff -Nru lintian-2.93.0/tags/d/diff-contains-quilt-control-dir.tag lintian-2.89.0ubuntu1/tags/d/diff-contains-quilt-control-dir.tag --- lintian-2.93.0/tags/d/diff-contains-quilt-control-dir.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/diff-contains-quilt-control-dir.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: diff-contains-quilt-control-dir -Severity: warning -Check: cruft -Explanation: The Debian diff or native package contains files in a directory - used by quilt, which are not useful in a diff or native package. - dpkg-source will automatically exclude these if it is passed - -I or -i for native and non-native packages - respectively. -See-Also: dpkg-source(1) diff -Nru lintian-2.93.0/tags/d/diff-contains-substvars.desc lintian-2.89.0ubuntu1/tags/d/diff-contains-substvars.desc --- lintian-2.93.0/tags/d/diff-contains-substvars.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/diff-contains-substvars.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: diff-contains-substvars +Severity: warning +Check: cruft +Info: Lintian found a substvars file in the Debian diff for this source + package. The debian/substvars (or debian/package.substvars) file + is usually generated and modified dynamically by debian/rules targets, in + which case it must be removed by the clean target. +Ref: policy 4.10 diff -Nru lintian-2.93.0/tags/d/diff-contains-substvars.tag lintian-2.89.0ubuntu1/tags/d/diff-contains-substvars.tag --- lintian-2.93.0/tags/d/diff-contains-substvars.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/diff-contains-substvars.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: diff-contains-substvars -Severity: warning -Check: cruft -Explanation: Lintian found a substvars file in the Debian diff for this source - package. The debian/substvars (or debian/package.substvars) file - is usually generated and modified dynamically by debian/rules targets, in - which case it must be removed by the clean target. -See-Also: policy 4.10 diff -Nru lintian-2.93.0/tags/d/diff-contains-svk-commit-file.desc lintian-2.89.0ubuntu1/tags/d/diff-contains-svk-commit-file.desc --- lintian-2.93.0/tags/d/diff-contains-svk-commit-file.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/diff-contains-svk-commit-file.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: diff-contains-svk-commit-file +Severity: warning +Check: cruft +Info: The Debian diff or native package contains an + svk-commitNNN.tmp, almost certainly a left-over from a failed + svk commit by the Debian package maintainer. diff -Nru lintian-2.93.0/tags/d/diff-contains-svk-commit-file.tag lintian-2.89.0ubuntu1/tags/d/diff-contains-svk-commit-file.tag --- lintian-2.93.0/tags/d/diff-contains-svk-commit-file.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/diff-contains-svk-commit-file.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: diff-contains-svk-commit-file -Severity: warning -Check: cruft -Explanation: The Debian diff or native package contains an - svk-commitNNN.tmp, almost certainly a left-over from a failed - svk commit by the Debian package maintainer. diff -Nru lintian-2.93.0/tags/d/diff-contains-svn-commit-file.desc lintian-2.89.0ubuntu1/tags/d/diff-contains-svn-commit-file.desc --- lintian-2.93.0/tags/d/diff-contains-svn-commit-file.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/diff-contains-svn-commit-file.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: diff-contains-svn-commit-file +Severity: warning +Check: cruft +Info: The Debian diff or native package contains an + svn-commit(.NNN).tmp, almost certainly a left-over from a failed + Subversion commit by the Debian package maintainer. diff -Nru lintian-2.93.0/tags/d/diff-contains-svn-commit-file.tag lintian-2.89.0ubuntu1/tags/d/diff-contains-svn-commit-file.tag --- lintian-2.93.0/tags/d/diff-contains-svn-commit-file.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/diff-contains-svn-commit-file.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: diff-contains-svn-commit-file -Severity: warning -Check: cruft -Explanation: The Debian diff or native package contains an - svn-commit(.NNN).tmp, almost certainly a left-over from a failed - Subversion commit by the Debian package maintainer. diff -Nru lintian-2.93.0/tags/d/diff-contains-svn-conflict-file.desc lintian-2.89.0ubuntu1/tags/d/diff-contains-svn-conflict-file.desc --- lintian-2.93.0/tags/d/diff-contains-svn-conflict-file.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/diff-contains-svn-conflict-file.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: diff-contains-svn-conflict-file +Severity: warning +Check: cruft +Info: The Debian diff or native package contains a file that looks like a + Subversion conflict file. These are generated by Subversion when a + conflict was detected while merging local changes with updates from a + source repository. Use svn resolved to remove them and clear + the Subversion conflict state after you have resolved the conflict. diff -Nru lintian-2.93.0/tags/d/diff-contains-svn-conflict-file.tag lintian-2.89.0ubuntu1/tags/d/diff-contains-svn-conflict-file.tag --- lintian-2.93.0/tags/d/diff-contains-svn-conflict-file.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/diff-contains-svn-conflict-file.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: diff-contains-svn-conflict-file -Severity: warning -Check: cruft -Explanation: The Debian diff or native package contains a file that looks like a - Subversion conflict file. These are generated by Subversion when a - conflict was detected while merging local changes with updates from a - source repository. Use svn resolved to remove them and clear - the Subversion conflict state after you have resolved the conflict. diff -Nru lintian-2.93.0/tags/d/diff-contains-svn-control-dir.desc lintian-2.89.0ubuntu1/tags/d/diff-contains-svn-control-dir.desc --- lintian-2.93.0/tags/d/diff-contains-svn-control-dir.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/diff-contains-svn-control-dir.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: diff-contains-svn-control-dir +Severity: warning +Check: cruft +Info: The Debian diff or native package contains files in an .svn + directory. These are usually artifacts of the revision control system + used by the Debian maintainer and not useful in a diff or native package. + dpkg-source will automatically exclude these if it is passed + -I or -i for native and non-native packages respectively. +Ref: dpkg-source(1) diff -Nru lintian-2.93.0/tags/d/diff-contains-svn-control-dir.tag lintian-2.89.0ubuntu1/tags/d/diff-contains-svn-control-dir.tag --- lintian-2.93.0/tags/d/diff-contains-svn-control-dir.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/diff-contains-svn-control-dir.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: diff-contains-svn-control-dir -Severity: warning -Check: cruft -Explanation: The Debian diff or native package contains files in an .svn - directory. These are usually artifacts of the revision control system - used by the Debian maintainer and not useful in a diff or native package. - dpkg-source will automatically exclude these if it is passed - -I or -i for native and non-native packages respectively. -See-Also: dpkg-source(1) diff -Nru lintian-2.93.0/tags/d/direct-changes-in-diff-but-no-patch-system.desc lintian-2.89.0ubuntu1/tags/d/direct-changes-in-diff-but-no-patch-system.desc --- lintian-2.93.0/tags/d/direct-changes-in-diff-but-no-patch-system.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/direct-changes-in-diff-but-no-patch-system.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,13 @@ +Tag: direct-changes-in-diff-but-no-patch-system +Severity: pedantic +Check: debian/patches +Info: The Debian diff.gz contains changes to files or creation of additional + files outside the debian directory. Keeping the changes as separate + patches under the control of a patch system allows for more fine grained + control over them. The package will also more easily support possible + future source package formats if all changes outside the debian + directory are stored as patches. + . + If the diff only creates new files that can be copied into place by the + package build rules, consider putting them in the debian + directory rather than using a patch system. diff -Nru lintian-2.93.0/tags/d/direct-changes-in-diff-but-no-patch-system.tag lintian-2.89.0ubuntu1/tags/d/direct-changes-in-diff-but-no-patch-system.tag --- lintian-2.93.0/tags/d/direct-changes-in-diff-but-no-patch-system.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/direct-changes-in-diff-but-no-patch-system.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,13 +0,0 @@ -Tag: direct-changes-in-diff-but-no-patch-system -Severity: pedantic -Check: debian/patches -Explanation: The Debian diff.gz contains changes to files or creation of additional - files outside the debian directory. Keeping the changes as separate - patches under the control of a patch system allows for more fine grained - control over them. The package will also more easily support possible - future source package formats if all changes outside the debian - directory are stored as patches. - . - If the diff only creates new files that can be copied into place by the - package build rules, consider putting them in the debian - directory rather than using a patch system. diff -Nru lintian-2.93.0/tags/d/directory-in-etc-sv-directory-without-executable-run-script.desc lintian-2.89.0ubuntu1/tags/d/directory-in-etc-sv-directory-without-executable-run-script.desc --- lintian-2.93.0/tags/d/directory-in-etc-sv-directory-without-executable-run-script.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/directory-in-etc-sv-directory-without-executable-run-script.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,11 @@ +Tag: directory-in-etc-sv-directory-without-executable-run-script +Severity: error +Certainty: possible +Check: init.d +Info: This package provides the specified directory under + /etc/sv but it does not ship a run script under this + directory. + . + Please check that you are installing your run script to the + right location and that has the correct executable permissions. +Ref: dh_runit(1) diff -Nru lintian-2.93.0/tags/d/directory-in-etc-sv-directory-without-executable-run-script.tag lintian-2.89.0ubuntu1/tags/d/directory-in-etc-sv-directory-without-executable-run-script.tag --- lintian-2.93.0/tags/d/directory-in-etc-sv-directory-without-executable-run-script.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/directory-in-etc-sv-directory-without-executable-run-script.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,10 +0,0 @@ -Tag: directory-in-etc-sv-directory-without-executable-run-script -Severity: error -Check: init.d -Explanation: This package provides the specified directory under - /etc/sv but it does not ship a run script under this - directory. - . - Please check that you are installing your run script to the - right location and that has the correct executable permissions. -See-Also: dh_runit(1) diff -Nru lintian-2.93.0/tags/d/dir-in-usr-local.desc lintian-2.89.0ubuntu1/tags/d/dir-in-usr-local.desc --- lintian-2.93.0/tags/d/dir-in-usr-local.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/dir-in-usr-local.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,12 @@ +Tag: dir-in-usr-local +Severity: error +Check: files/hierarchy/standard +Info: The package installs a directory in /usr/local/... which is + not allowed. + . + If you want to provide an empty directory in /usr/local for + convenience of the local system administrator, please follow the rules + in the policy manual (section 9.1.2), i.e., create the directories in + the postinst script but don't fail if this isn't possible (e.g. if + /usr/local is mounted read-only). +Ref: policy 9.1.2 diff -Nru lintian-2.93.0/tags/d/dir-in-usr-local.tag lintian-2.89.0ubuntu1/tags/d/dir-in-usr-local.tag --- lintian-2.93.0/tags/d/dir-in-usr-local.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/dir-in-usr-local.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,12 +0,0 @@ -Tag: dir-in-usr-local -Severity: error -Check: files/hierarchy/standard -Explanation: The package installs a directory in /usr/local/... which is - not allowed. - . - If you want to provide an empty directory in /usr/local for - convenience of the local system administrator, please follow the rules - in the policy manual (section 9.1.2), i.e., create the directories in - the postinst script but don't fail if this isn't possible (e.g. if - /usr/local is mounted read-only). -See-Also: policy 9.1.2 diff -Nru lintian-2.93.0/tags/d/dir-or-file-in-build-tree.desc lintian-2.89.0ubuntu1/tags/d/dir-or-file-in-build-tree.desc --- lintian-2.93.0/tags/d/dir-or-file-in-build-tree.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/dir-or-file-in-build-tree.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: dir-or-file-in-build-tree +Severity: error +Certainty: possible +Check: files/build-path +Info: The package installs a file in common build paths. + . + This often occurs if the package uses regular expressions to + strip the build path without properly regex quoting the build + path. diff -Nru lintian-2.93.0/tags/d/dir-or-file-in-build-tree.tag lintian-2.89.0ubuntu1/tags/d/dir-or-file-in-build-tree.tag --- lintian-2.93.0/tags/d/dir-or-file-in-build-tree.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/dir-or-file-in-build-tree.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: dir-or-file-in-build-tree -Severity: error -Check: files/build-path -Explanation: The package installs a file in common build paths. - . - This often occurs if the package uses regular expressions to - strip the build path without properly regex quoting the build - path. diff -Nru lintian-2.93.0/tags/d/dir-or-file-in-etc-opt.desc lintian-2.89.0ubuntu1/tags/d/dir-or-file-in-etc-opt.desc --- lintian-2.93.0/tags/d/dir-or-file-in-etc-opt.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/dir-or-file-in-etc-opt.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: dir-or-file-in-etc-opt +Severity: error +Check: files/hierarchy/standard +Info: Debian packages should not install into /etc/opt, because it + is reserved for add-on software. +Ref: fhs optaddonapplicationsoftwarepackages diff -Nru lintian-2.93.0/tags/d/dir-or-file-in-etc-opt.tag lintian-2.89.0ubuntu1/tags/d/dir-or-file-in-etc-opt.tag --- lintian-2.93.0/tags/d/dir-or-file-in-etc-opt.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/dir-or-file-in-etc-opt.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: dir-or-file-in-etc-opt -Severity: error -Check: files/hierarchy/standard -Explanation: Debian packages should not install into /etc/opt, because it - is reserved for add-on software. -See-Also: fhs optaddonapplicationsoftwarepackages diff -Nru lintian-2.93.0/tags/d/dir-or-file-in-home.desc lintian-2.89.0ubuntu1/tags/d/dir-or-file-in-home.desc --- lintian-2.93.0/tags/d/dir-or-file-in-home.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/dir-or-file-in-home.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,5 @@ +Tag: dir-or-file-in-home +Severity: error +Check: files/hierarchy/standard +Info: Debian packages should not install into /home, because it + is reserved for users. diff -Nru lintian-2.93.0/tags/d/dir-or-file-in-home.tag lintian-2.89.0ubuntu1/tags/d/dir-or-file-in-home.tag --- lintian-2.93.0/tags/d/dir-or-file-in-home.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/dir-or-file-in-home.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,5 +0,0 @@ -Tag: dir-or-file-in-home -Severity: error -Check: files/hierarchy/standard -Explanation: Debian packages should not install into /home, because it - is reserved for users. diff -Nru lintian-2.93.0/tags/d/dir-or-file-in-mnt.desc lintian-2.89.0ubuntu1/tags/d/dir-or-file-in-mnt.desc --- lintian-2.93.0/tags/d/dir-or-file-in-mnt.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/dir-or-file-in-mnt.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: dir-or-file-in-mnt +Severity: error +Check: files/hierarchy/standard +Info: Packages should not install into /mnt. The FHS states that + this directory is reserved for the local system administrator for + temporary mounts and that it must not be used by installation programs. +Ref: fhs mntmountpointforatemporarilymount diff -Nru lintian-2.93.0/tags/d/dir-or-file-in-mnt.tag lintian-2.89.0ubuntu1/tags/d/dir-or-file-in-mnt.tag --- lintian-2.93.0/tags/d/dir-or-file-in-mnt.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/dir-or-file-in-mnt.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: dir-or-file-in-mnt -Severity: error -Check: files/hierarchy/standard -Explanation: Packages should not install into /mnt. The FHS states that - this directory is reserved for the local system administrator for - temporary mounts and that it must not be used by installation programs. -See-Also: fhs mntmountpointforatemporarilymount diff -Nru lintian-2.93.0/tags/d/dir-or-file-in-opt.desc lintian-2.89.0ubuntu1/tags/d/dir-or-file-in-opt.desc --- lintian-2.93.0/tags/d/dir-or-file-in-opt.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/dir-or-file-in-opt.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: dir-or-file-in-opt +Severity: error +Check: files/hierarchy/standard +Info: Debian packages should not install into /opt, because it + is reserved for add-on software. +Ref: fhs optaddonapplicationsoftwarepackages diff -Nru lintian-2.93.0/tags/d/dir-or-file-in-opt.tag lintian-2.89.0ubuntu1/tags/d/dir-or-file-in-opt.tag --- lintian-2.93.0/tags/d/dir-or-file-in-opt.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/dir-or-file-in-opt.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: dir-or-file-in-opt -Severity: error -Check: files/hierarchy/standard -Explanation: Debian packages should not install into /opt, because it - is reserved for add-on software. -See-Also: fhs optaddonapplicationsoftwarepackages diff -Nru lintian-2.93.0/tags/d/dir-or-file-in-run.desc lintian-2.89.0ubuntu1/tags/d/dir-or-file-in-run.desc --- lintian-2.93.0/tags/d/dir-or-file-in-run.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/dir-or-file-in-run.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: dir-or-file-in-run +Severity: error +Certainty: possible +Check: files/hierarchy/standard +Info: /run may be a temporary filesystem, so any directories + or files needed there must be created dynamically at boot time. +Ref: policy 9.3.2 diff -Nru lintian-2.93.0/tags/d/dir-or-file-in-run.tag lintian-2.89.0ubuntu1/tags/d/dir-or-file-in-run.tag --- lintian-2.93.0/tags/d/dir-or-file-in-run.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/dir-or-file-in-run.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: dir-or-file-in-run -Severity: error -Check: files/hierarchy/standard -Explanation: /run may be a temporary filesystem, so any directories - or files needed there must be created dynamically at boot time. -See-Also: policy 9.3.2 diff -Nru lintian-2.93.0/tags/d/dir-or-file-in-srv.desc lintian-2.89.0ubuntu1/tags/d/dir-or-file-in-srv.desc --- lintian-2.93.0/tags/d/dir-or-file-in-srv.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/dir-or-file-in-srv.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,15 @@ +Tag: dir-or-file-in-srv +Severity: error +Check: files/hierarchy/standard +Info: Debian packages should not install into /srv. The + specification of /srv states that its structure is at the + discretion of the local administrator and no package should rely on any + particular structure. Debian packages that install files directly into + /srv can't adjust for local policy about its structure and in + essence force a particular structure. + . + If a package wishes to put its data in /srv, it must do this in + a way that allows the local administrator to specify and preserve their + chosen directory structure (such as through post-install configuration, + setup scripts, debconf prompting, etc.). +Ref: fhs srvdataforservicesprovidedbysystem diff -Nru lintian-2.93.0/tags/d/dir-or-file-in-srv.tag lintian-2.89.0ubuntu1/tags/d/dir-or-file-in-srv.tag --- lintian-2.93.0/tags/d/dir-or-file-in-srv.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/dir-or-file-in-srv.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,15 +0,0 @@ -Tag: dir-or-file-in-srv -Severity: error -Check: files/hierarchy/standard -Explanation: Debian packages should not install into /srv. The - specification of /srv states that its structure is at the - discretion of the local administrator and no package should rely on any - particular structure. Debian packages that install files directly into - /srv can't adjust for local policy about its structure and in - essence force a particular structure. - . - If a package wishes to put its data in /srv, it must do this in - a way that allows the local administrator to specify and preserve their - chosen directory structure (such as through post-install configuration, - setup scripts, debconf prompting, etc.). -See-Also: fhs srvdataforservicesprovidedbysystem diff -Nru lintian-2.93.0/tags/d/dir-or-file-in-tmp.desc lintian-2.89.0ubuntu1/tags/d/dir-or-file-in-tmp.desc --- lintian-2.93.0/tags/d/dir-or-file-in-tmp.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/dir-or-file-in-tmp.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: dir-or-file-in-tmp +Severity: error +Check: files/hierarchy/standard +Info: Packages must not install files into /tmp or + /var/tmp. The File Hierarchy Standard specifies that such files + may be removed by the administrator and that programs may not depend on + any files in /tmp being preserved across invocations, which + combined mean that it makes no sense to ship files in these directories. +Ref: fhs tmptemporaryfiles, fhs vartmptemporaryfilespreservedbetwee diff -Nru lintian-2.93.0/tags/d/dir-or-file-in-tmp.tag lintian-2.89.0ubuntu1/tags/d/dir-or-file-in-tmp.tag --- lintian-2.93.0/tags/d/dir-or-file-in-tmp.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/dir-or-file-in-tmp.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: dir-or-file-in-tmp -Severity: error -Check: files/hierarchy/standard -Explanation: Packages must not install files into /tmp or - /var/tmp. The File Hierarchy Standard specifies that such files - may be removed by the administrator and that programs may not depend on - any files in /tmp being preserved across invocations, which - combined mean that it makes no sense to ship files in these directories. -See-Also: fhs tmptemporaryfiles, fhs vartmptemporaryfilespreservedbetwee diff -Nru lintian-2.93.0/tags/d/dir-or-file-in-var-lock.desc lintian-2.89.0ubuntu1/tags/d/dir-or-file-in-var-lock.desc --- lintian-2.93.0/tags/d/dir-or-file-in-var-lock.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/dir-or-file-in-var-lock.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: dir-or-file-in-var-lock +Severity: error +Certainty: possible +Check: files/hierarchy/standard +Info: /var/lock may be a temporary filesystem, so any directories + or files needed there must be created dynamically at boot time. +Ref: policy 9.3.2 diff -Nru lintian-2.93.0/tags/d/dir-or-file-in-var-lock.tag lintian-2.89.0ubuntu1/tags/d/dir-or-file-in-var-lock.tag --- lintian-2.93.0/tags/d/dir-or-file-in-var-lock.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/dir-or-file-in-var-lock.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: dir-or-file-in-var-lock -Severity: error -Check: files/hierarchy/standard -Explanation: /var/lock may be a temporary filesystem, so any directories - or files needed there must be created dynamically at boot time. -See-Also: policy 9.3.2 diff -Nru lintian-2.93.0/tags/d/dir-or-file-in-var-run.desc lintian-2.89.0ubuntu1/tags/d/dir-or-file-in-var-run.desc --- lintian-2.93.0/tags/d/dir-or-file-in-var-run.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/dir-or-file-in-var-run.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: dir-or-file-in-var-run +Severity: error +Certainty: possible +Check: files/hierarchy/standard +Info: /var/run may be a temporary filesystem, so any directories + or files needed there must be created dynamically at boot time. +Ref: policy 9.3.2 diff -Nru lintian-2.93.0/tags/d/dir-or-file-in-var-run.tag lintian-2.89.0ubuntu1/tags/d/dir-or-file-in-var-run.tag --- lintian-2.93.0/tags/d/dir-or-file-in-var-run.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/dir-or-file-in-var-run.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: dir-or-file-in-var-run -Severity: error -Check: files/hierarchy/standard -Explanation: /var/run may be a temporary filesystem, so any directories - or files needed there must be created dynamically at boot time. -See-Also: policy 9.3.2 diff -Nru lintian-2.93.0/tags/d/dir-or-file-in-var-www.desc lintian-2.89.0ubuntu1/tags/d/dir-or-file-in-var-www.desc --- lintian-2.93.0/tags/d/dir-or-file-in-var-www.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/dir-or-file-in-var-www.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,21 @@ +Tag: dir-or-file-in-var-www +Severity: error +Certainty: possible +Check: files/hierarchy/standard +Ref: fhs thevarhierarchy +Info: Debian packages should not install files under /var/www. + This is not one of the /var directories in the File Hierarchy + Standard and is under the control of the local administrator. Packages + should not assume that it is the document root for a web server; it is + very common for users to change the default document root and packages + should not assume that users will keep any particular setting. + . + Packages that want to make files available via an installed web server + should instead put instructions for the local administrator in a + README.Debian file and ideally include configuration fragments for common + web servers such as Apache. + . + As an exception, packages are permitted to create the /var/www + directory due to its past history as the default document root, but + should at most copy over a default file in postinst for a new install. + In this case, please add a Lintian override. diff -Nru lintian-2.93.0/tags/d/dir-or-file-in-var-www.tag lintian-2.89.0ubuntu1/tags/d/dir-or-file-in-var-www.tag --- lintian-2.93.0/tags/d/dir-or-file-in-var-www.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/dir-or-file-in-var-www.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,20 +0,0 @@ -Tag: dir-or-file-in-var-www -Severity: error -Check: files/hierarchy/standard -See-Also: fhs thevarhierarchy -Explanation: Debian packages should not install files under /var/www. - This is not one of the /var directories in the File Hierarchy - Standard and is under the control of the local administrator. Packages - should not assume that it is the document root for a web server; it is - very common for users to change the default document root and packages - should not assume that users will keep any particular setting. - . - Packages that want to make files available via an installed web server - should instead put instructions for the local administrator in a - README.Debian file and ideally include configuration fragments for common - web servers such as Apache. - . - As an exception, packages are permitted to create the /var/www - directory due to its past history as the default document root, but - should at most copy over a default file in postinst for a new install. - In this case, please add a Lintian override. diff -Nru lintian-2.93.0/tags/d/distant-prerequisite-in-shlibs.desc lintian-2.89.0ubuntu1/tags/d/distant-prerequisite-in-shlibs.desc --- lintian-2.93.0/tags/d/distant-prerequisite-in-shlibs.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/distant-prerequisite-in-shlibs.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,18 @@ +Tag: distant-prerequisite-in-shlibs +Severity: warning +Certainty: possible +Check: shared-libs +Renamed-From: shlibs-declares-dependency-on-other-package +Info: This package declares in its shlibs control file either a dependency + on some other package not listed in the Provides of this package or on a + version of this package that the package version doesn't satisfy. + . + Packages should normally only list in their shlibs control file the + shared libraries included in that package, and therefore the dependencies + listed there should normally be satisfied by either the package itself or + one of its Provides. + . + In unusual circumstances where it's necessary to declare more complex + dependencies in the shlibs control file, please add a Lintian override + for this warning. +Ref: policy 8.6 diff -Nru lintian-2.93.0/tags/d/distant-prerequisite-in-shlibs.tag lintian-2.89.0ubuntu1/tags/d/distant-prerequisite-in-shlibs.tag --- lintian-2.93.0/tags/d/distant-prerequisite-in-shlibs.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/distant-prerequisite-in-shlibs.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,17 +0,0 @@ -Tag: distant-prerequisite-in-shlibs -Severity: warning -Check: shared-libs -Renamed-From: shlibs-declares-dependency-on-other-package -Explanation: This package declares in its shlibs control file either a dependency - on some other package not listed in the Provides of this package or on a - version of this package that the package version doesn't satisfy. - . - Packages should normally only list in their shlibs control file the - shared libraries included in that package, and therefore the dependencies - listed there should normally be satisfied by either the package itself or - one of its Provides. - . - In unusual circumstances where it's necessary to declare more complex - dependencies in the shlibs control file, please add a Lintian override - for this warning. -See-Also: policy 8.6 diff -Nru lintian-2.93.0/tags/d/distribution-and-changes-mismatch.desc lintian-2.89.0ubuntu1/tags/d/distribution-and-changes-mismatch.desc --- lintian-2.93.0/tags/d/distribution-and-changes-mismatch.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/distribution-and-changes-mismatch.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,13 @@ +Tag: distribution-and-changes-mismatch +Severity: warning +Certainty: possible +Check: fields/distribution +Info: The Distribution in the .changes file indicates + that packages should be installed into one distribution (suite), but the + distribution in the Changes field copied from + debian/changelog indicates that a different distribution + was intended. + . + This is an easy mistake to make when invoking "sbuild ... foo.dsc". + Double-check the -d option if using sbuild in this way. +Ref: #542747, #529281 diff -Nru lintian-2.93.0/tags/d/distribution-and-changes-mismatch.tag lintian-2.89.0ubuntu1/tags/d/distribution-and-changes-mismatch.tag --- lintian-2.93.0/tags/d/distribution-and-changes-mismatch.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/distribution-and-changes-mismatch.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,12 +0,0 @@ -Tag: distribution-and-changes-mismatch -Severity: warning -Check: fields/distribution -Explanation: The Distribution in the .changes file indicates - that packages should be installed into one distribution (suite), but the - distribution in the Changes field copied from - debian/changelog indicates that a different distribution - was intended. - . - This is an easy mistake to make when invoking "sbuild ... foo.dsc". - Double-check the -d option if using sbuild in this way. -See-Also: Bug#542747, Bug#529281 diff -Nru lintian-2.93.0/tags/d/distribution-and-experimental-mismatch.desc lintian-2.89.0ubuntu1/tags/d/distribution-and-experimental-mismatch.desc --- lintian-2.93.0/tags/d/distribution-and-experimental-mismatch.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/distribution-and-experimental-mismatch.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,11 @@ +Tag: distribution-and-experimental-mismatch +Severity: error +Check: fields/distribution +Info: The Distribution in the .changes file indicates + that packages should be installed into a non-experimental distribution + (suite), but the distribution in the Changes field copied from + debian/changelog indicates that experimental was intended. + . + This is an easy mistake to make when invoking "sbuild ... foo.dsc". + Double-check the -d option if using sbuild in this way. +Ref: #542747, #529281 diff -Nru lintian-2.93.0/tags/d/distribution-and-experimental-mismatch.tag lintian-2.89.0ubuntu1/tags/d/distribution-and-experimental-mismatch.tag --- lintian-2.93.0/tags/d/distribution-and-experimental-mismatch.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/distribution-and-experimental-mismatch.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,11 +0,0 @@ -Tag: distribution-and-experimental-mismatch -Severity: error -Check: fields/distribution -Explanation: The Distribution in the .changes file indicates - that packages should be installed into a non-experimental distribution - (suite), but the distribution in the Changes field copied from - debian/changelog indicates that experimental was intended. - . - This is an easy mistake to make when invoking "sbuild ... foo.dsc". - Double-check the -d option if using sbuild in this way. -See-Also: Bug#542747, Bug#529281 diff -Nru lintian-2.93.0/tags/d/diversion-for-unknown-file.desc lintian-2.89.0ubuntu1/tags/d/diversion-for-unknown-file.desc --- lintian-2.93.0/tags/d/diversion-for-unknown-file.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/diversion-for-unknown-file.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,5 @@ +Tag: diversion-for-unknown-file +Severity: error +Check: scripts +Info: The maintainer script adds a diversion for a file that is not + provided by this package. diff -Nru lintian-2.93.0/tags/d/diversion-for-unknown-file.tag lintian-2.89.0ubuntu1/tags/d/diversion-for-unknown-file.tag --- lintian-2.93.0/tags/d/diversion-for-unknown-file.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/diversion-for-unknown-file.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,5 +0,0 @@ -Tag: diversion-for-unknown-file -Severity: error -Check: scripts -Explanation: The maintainer script adds a diversion for a file that is not - provided by this package. diff -Nru lintian-2.93.0/tags/d/django-package-does-not-depend-on-django.desc lintian-2.89.0ubuntu1/tags/d/django-package-does-not-depend-on-django.desc --- lintian-2.93.0/tags/d/django-package-does-not-depend-on-django.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/django-package-does-not-depend-on-django.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: django-package-does-not-depend-on-django +Severity: warning +Check: languages/python +Info: This package appears to be library module for the Django web development + framework but it does not specify a binary dependency on the Django package + itself. + . + Please add a Depends on python-django or python3-django. diff -Nru lintian-2.93.0/tags/d/django-package-does-not-depend-on-django.tag lintian-2.89.0ubuntu1/tags/d/django-package-does-not-depend-on-django.tag --- lintian-2.93.0/tags/d/django-package-does-not-depend-on-django.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/django-package-does-not-depend-on-django.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: django-package-does-not-depend-on-django -Severity: warning -Check: languages/python -Explanation: This package appears to be library module for the Django web development - framework but it does not specify a binary dependency on the Django package - itself. - . - Please add a Depends on python-django or python3-django. diff -Nru lintian-2.93.0/tags/d/dm-upload-allowed-is-obsolete.desc lintian-2.89.0ubuntu1/tags/d/dm-upload-allowed-is-obsolete.desc --- lintian-2.93.0/tags/d/dm-upload-allowed-is-obsolete.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/dm-upload-allowed-is-obsolete.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: dm-upload-allowed-is-obsolete +Severity: warning +Check: fields/dm-upload-allowed +Info: The implementation of the "Debian Maintainers" GR has changed + and the "DM-Upload-Allowed" field is now obsolete. + . + Instead these permissions are granted via "dak-commands" files. +Ref: https://lists.debian.org/debian-devel-announce/2012/09/msg00008.html diff -Nru lintian-2.93.0/tags/d/dm-upload-allowed-is-obsolete.tag lintian-2.89.0ubuntu1/tags/d/dm-upload-allowed-is-obsolete.tag --- lintian-2.93.0/tags/d/dm-upload-allowed-is-obsolete.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/dm-upload-allowed-is-obsolete.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: dm-upload-allowed-is-obsolete -Severity: warning -Check: fields/dm-upload-allowed -Explanation: The implementation of the "Debian Maintainers" GR has changed - and the "DM-Upload-Allowed" field is now obsolete. - . - Instead these permissions are granted via "dak-commands" files. -See-Also: https://lists.debian.org/debian-devel-announce/2012/09/msg00008.html diff -Nru lintian-2.93.0/tags/d/doc-base-abstract-field-is-template.desc lintian-2.89.0ubuntu1/tags/d/doc-base-abstract-field-is-template.desc --- lintian-2.93.0/tags/d/doc-base-abstract-field-is-template.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/doc-base-abstract-field-is-template.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: doc-base-abstract-field-is-template +Severity: warning +Certainty: possible +Check: menus +Info: The Abstract field of doc-base contains a "manage online manuals" + phrase, which was copied verbatim from an example control file found in + section 2.3.1 of the Debian doc-base Manual. diff -Nru lintian-2.93.0/tags/d/doc-base-abstract-field-is-template.tag lintian-2.89.0ubuntu1/tags/d/doc-base-abstract-field-is-template.tag --- lintian-2.93.0/tags/d/doc-base-abstract-field-is-template.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/doc-base-abstract-field-is-template.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: doc-base-abstract-field-is-template -Severity: warning -Check: menus -Explanation: The Abstract field of doc-base contains a "manage online manuals" - phrase, which was copied verbatim from an example control file found in - section 2.3.1 of the Debian doc-base Manual. diff -Nru lintian-2.93.0/tags/d/doc-base-abstract-field-separator-extra-whitespace.desc lintian-2.89.0ubuntu1/tags/d/doc-base-abstract-field-separator-extra-whitespace.desc --- lintian-2.93.0/tags/d/doc-base-abstract-field-separator-extra-whitespace.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/doc-base-abstract-field-separator-extra-whitespace.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: doc-base-abstract-field-separator-extra-whitespace +Severity: warning +Check: menus +Info: Unnecessary spaces were found in the paragraph separator line of the + doc-base's Abstract field. The separator line should consist of a single + space followed by a single dot. +Ref: doc-base 2.3.2 diff -Nru lintian-2.93.0/tags/d/doc-base-abstract-field-separator-extra-whitespace.tag lintian-2.89.0ubuntu1/tags/d/doc-base-abstract-field-separator-extra-whitespace.tag --- lintian-2.93.0/tags/d/doc-base-abstract-field-separator-extra-whitespace.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/doc-base-abstract-field-separator-extra-whitespace.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: doc-base-abstract-field-separator-extra-whitespace -Severity: warning -Check: menus -Explanation: Unnecessary spaces were found in the paragraph separator line of the - doc-base's Abstract field. The separator line should consist of a single - space followed by a single dot. -See-Also: doc-base 2.3.2 diff -Nru lintian-2.93.0/tags/d/doc-base-abstract-might-contain-extra-leading-whitespace.desc lintian-2.89.0ubuntu1/tags/d/doc-base-abstract-might-contain-extra-leading-whitespace.desc --- lintian-2.93.0/tags/d/doc-base-abstract-might-contain-extra-leading-whitespace.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/doc-base-abstract-might-contain-extra-leading-whitespace.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: doc-base-abstract-might-contain-extra-leading-whitespace +Severity: warning +Certainty: possible +Check: menus +Info: Continuation lines of the Abstract field of doc-base control file + should start with only one space unless they are meant to be displayed + verbatim by frontends. +Ref: doc-base 2.3.2 diff -Nru lintian-2.93.0/tags/d/doc-base-abstract-might-contain-extra-leading-whitespace.tag lintian-2.89.0ubuntu1/tags/d/doc-base-abstract-might-contain-extra-leading-whitespace.tag --- lintian-2.93.0/tags/d/doc-base-abstract-might-contain-extra-leading-whitespace.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/doc-base-abstract-might-contain-extra-leading-whitespace.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: doc-base-abstract-might-contain-extra-leading-whitespace -Severity: warning -Check: menus -Explanation: Continuation lines of the Abstract field of doc-base control file - should start with only one space unless they are meant to be displayed - verbatim by frontends. -See-Also: doc-base 2.3.2 diff -Nru lintian-2.93.0/tags/d/doc-base-document-field-ends-in-whitespace.desc lintian-2.89.0ubuntu1/tags/d/doc-base-document-field-ends-in-whitespace.desc --- lintian-2.93.0/tags/d/doc-base-document-field-ends-in-whitespace.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/doc-base-document-field-ends-in-whitespace.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: doc-base-document-field-ends-in-whitespace +Severity: error +Check: menus +Info: The Document field in a doc-base file should not end in whitespace. + doc-base (at least as of 0.8.5) cannot cope with such fields and + debhelper 5.0.57 or earlier may create files ending in whitespace when + installing such files. diff -Nru lintian-2.93.0/tags/d/doc-base-document-field-ends-in-whitespace.tag lintian-2.89.0ubuntu1/tags/d/doc-base-document-field-ends-in-whitespace.tag --- lintian-2.93.0/tags/d/doc-base-document-field-ends-in-whitespace.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/doc-base-document-field-ends-in-whitespace.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: doc-base-document-field-ends-in-whitespace -Severity: error -Check: menus -Explanation: The Document field in a doc-base file should not end in whitespace. - doc-base (at least as of 0.8.5) cannot cope with such fields and - debhelper 5.0.57 or earlier may create files ending in whitespace when - installing such files. diff -Nru lintian-2.93.0/tags/d/doc-base-document-field-not-in-first-line.desc lintian-2.89.0ubuntu1/tags/d/doc-base-document-field-not-in-first-line.desc --- lintian-2.93.0/tags/d/doc-base-document-field-not-in-first-line.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/doc-base-document-field-not-in-first-line.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: doc-base-document-field-not-in-first-line +Severity: error +Check: menus +Info: The Document field in doc-base control file must be located at + first line of the file. While unregistering documents, doc-base 0.8 + and later parses only the first line of the control file for performance + reasons. +Ref: doc-base 2.3.2.1 diff -Nru lintian-2.93.0/tags/d/doc-base-document-field-not-in-first-line.tag lintian-2.89.0ubuntu1/tags/d/doc-base-document-field-not-in-first-line.tag --- lintian-2.93.0/tags/d/doc-base-document-field-not-in-first-line.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/doc-base-document-field-not-in-first-line.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: doc-base-document-field-not-in-first-line -Severity: error -Check: menus -Explanation: The Document field in doc-base control file must be located at - first line of the file. While unregistering documents, doc-base 0.8 - and later parses only the first line of the control file for performance - reasons. -See-Also: doc-base 2.3.2.1 diff -Nru lintian-2.93.0/tags/d/doc-base-file-lacks-required-field.desc lintian-2.89.0ubuntu1/tags/d/doc-base-file-lacks-required-field.desc --- lintian-2.93.0/tags/d/doc-base-file-lacks-required-field.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/doc-base-file-lacks-required-field.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: doc-base-file-lacks-required-field +Severity: error +Check: menus +Info: The doc-base control file does not contain a required field for the + appropriate section. +Ref: doc-base 2.3.2.1, doc-base 2.3.2.2 diff -Nru lintian-2.93.0/tags/d/doc-base-file-lacks-required-field.tag lintian-2.89.0ubuntu1/tags/d/doc-base-file-lacks-required-field.tag --- lintian-2.93.0/tags/d/doc-base-file-lacks-required-field.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/doc-base-file-lacks-required-field.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: doc-base-file-lacks-required-field -Severity: error -Check: menus -Explanation: The doc-base control file does not contain a required field for the - appropriate section. -See-Also: doc-base 2.3.2.1, doc-base 2.3.2.2 diff -Nru lintian-2.93.0/tags/d/doc-base-file-no-format.desc lintian-2.89.0ubuntu1/tags/d/doc-base-file-no-format.desc --- lintian-2.93.0/tags/d/doc-base-file-no-format.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/doc-base-file-no-format.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: doc-base-file-no-format +Severity: error +Check: menus +Info: A format section of this doc-base control file didn't specify a + format. Each section after the first must specify a format. +Ref: doc-base 2.3.2.2 diff -Nru lintian-2.93.0/tags/d/doc-base-file-no-format-section.desc lintian-2.89.0ubuntu1/tags/d/doc-base-file-no-format-section.desc --- lintian-2.93.0/tags/d/doc-base-file-no-format-section.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/doc-base-file-no-format-section.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: doc-base-file-no-format-section +Severity: error +Check: menus +Info: This doc-base control file didn't specify any format + section. +Ref: doc-base 2.3.2.2 diff -Nru lintian-2.93.0/tags/d/doc-base-file-no-format-section.tag lintian-2.89.0ubuntu1/tags/d/doc-base-file-no-format-section.tag --- lintian-2.93.0/tags/d/doc-base-file-no-format-section.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/doc-base-file-no-format-section.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: doc-base-file-no-format-section -Severity: error -Check: menus -Explanation: This doc-base control file didn't specify any format - section. -See-Also: doc-base 2.3.2.2 diff -Nru lintian-2.93.0/tags/d/doc-base-file-no-format.tag lintian-2.89.0ubuntu1/tags/d/doc-base-file-no-format.tag --- lintian-2.93.0/tags/d/doc-base-file-no-format.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/doc-base-file-no-format.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: doc-base-file-no-format -Severity: error -Check: menus -Explanation: A format section of this doc-base control file didn't specify a - format. Each section after the first must specify a format. -See-Also: doc-base 2.3.2.2 diff -Nru lintian-2.93.0/tags/d/doc-base-file-no-index.desc lintian-2.89.0ubuntu1/tags/d/doc-base-file-no-index.desc --- lintian-2.93.0/tags/d/doc-base-file-no-index.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/doc-base-file-no-index.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: doc-base-file-no-index +Severity: error +Check: menus +Info: Format sections in doc-base control files for HTML or Info documents + must contain an Index field specifying the starting document for the + documentation. Even if the documentation is a single file, this field + must be present. +Ref: doc-base 2.3.2.2 diff -Nru lintian-2.93.0/tags/d/doc-base-file-no-index.tag lintian-2.89.0ubuntu1/tags/d/doc-base-file-no-index.tag --- lintian-2.93.0/tags/d/doc-base-file-no-index.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/doc-base-file-no-index.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: doc-base-file-no-index -Severity: error -Check: menus -Explanation: Format sections in doc-base control files for HTML or Info documents - must contain an Index field specifying the starting document for the - documentation. Even if the documentation is a single file, this field - must be present. -See-Also: doc-base 2.3.2.2 diff -Nru lintian-2.93.0/tags/d/doc-base-file-references-missing-file.desc lintian-2.89.0ubuntu1/tags/d/doc-base-file-references-missing-file.desc --- lintian-2.93.0/tags/d/doc-base-file-references-missing-file.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/doc-base-file-references-missing-file.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: doc-base-file-references-missing-file +Severity: error +Check: menus +Info: One of the files referenced in an Index or Files field in this + doc-base control file does not exist in the package. The doc-base + control files should be installed by the package that provides the + documents they are registering. diff -Nru lintian-2.93.0/tags/d/doc-base-file-references-missing-file.tag lintian-2.89.0ubuntu1/tags/d/doc-base-file-references-missing-file.tag --- lintian-2.93.0/tags/d/doc-base-file-references-missing-file.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/doc-base-file-references-missing-file.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: doc-base-file-references-missing-file -Severity: error -Check: menus -Explanation: One of the files referenced in an Index or Files field in this - doc-base control file does not exist in the package. The doc-base - control files should be installed by the package that provides the - documents they are registering. diff -Nru lintian-2.93.0/tags/d/doc-base-file-references-wrong-path.desc lintian-2.89.0ubuntu1/tags/d/doc-base-file-references-wrong-path.desc --- lintian-2.93.0/tags/d/doc-base-file-references-wrong-path.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/doc-base-file-references-wrong-path.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: doc-base-file-references-wrong-path +Severity: error +Check: menus +Info: The specified doc-base control file references a file in an + Index or Files field that does not start with + /usr/share/doc or /usr/share/info. +Ref: doc-base 2.3.2.2 diff -Nru lintian-2.93.0/tags/d/doc-base-file-references-wrong-path.tag lintian-2.89.0ubuntu1/tags/d/doc-base-file-references-wrong-path.tag --- lintian-2.93.0/tags/d/doc-base-file-references-wrong-path.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/doc-base-file-references-wrong-path.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: doc-base-file-references-wrong-path -Severity: error -Check: menus -Explanation: The specified doc-base control file references a file in an - Index or Files field that does not start with - /usr/share/doc or /usr/share/info. -See-Also: doc-base 2.3.2.2 diff -Nru lintian-2.93.0/tags/d/doc-base-file-separator-extra-whitespace.desc lintian-2.89.0ubuntu1/tags/d/doc-base-file-separator-extra-whitespace.desc --- lintian-2.93.0/tags/d/doc-base-file-separator-extra-whitespace.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/doc-base-file-separator-extra-whitespace.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: doc-base-file-separator-extra-whitespace +Severity: warning +Check: menus +Info: Unnecessary spaces were found in the doc-base file sections' + separator. The section separator is an empty line and should not contain + any whitespace. +Ref: doc-base 2.3.2 diff -Nru lintian-2.93.0/tags/d/doc-base-file-separator-extra-whitespace.tag lintian-2.89.0ubuntu1/tags/d/doc-base-file-separator-extra-whitespace.tag --- lintian-2.93.0/tags/d/doc-base-file-separator-extra-whitespace.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/doc-base-file-separator-extra-whitespace.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: doc-base-file-separator-extra-whitespace -Severity: warning -Check: menus -Explanation: Unnecessary spaces were found in the doc-base file sections' - separator. The section separator is an empty line and should not contain - any whitespace. -See-Also: doc-base 2.3.2 diff -Nru lintian-2.93.0/tags/d/doc-base-file-syntax-error.desc lintian-2.89.0ubuntu1/tags/d/doc-base-file-syntax-error.desc --- lintian-2.93.0/tags/d/doc-base-file-syntax-error.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/doc-base-file-syntax-error.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,5 @@ +Tag: doc-base-file-syntax-error +Severity: error +Check: menus +Info: Lintian found a syntax error in the doc-base control file. +Ref: doc-base 2.3.2.2 diff -Nru lintian-2.93.0/tags/d/doc-base-file-syntax-error.tag lintian-2.89.0ubuntu1/tags/d/doc-base-file-syntax-error.tag --- lintian-2.93.0/tags/d/doc-base-file-syntax-error.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/doc-base-file-syntax-error.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,5 +0,0 @@ -Tag: doc-base-file-syntax-error -Severity: error -Check: menus -Explanation: Lintian found a syntax error in the doc-base control file. -See-Also: doc-base 2.3.2.2 diff -Nru lintian-2.93.0/tags/d/doc-base-file-unknown-field.desc lintian-2.89.0ubuntu1/tags/d/doc-base-file-unknown-field.desc --- lintian-2.93.0/tags/d/doc-base-file-unknown-field.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/doc-base-file-unknown-field.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: doc-base-file-unknown-field +Severity: error +Check: menus +Info: The doc-base control file contains field which is either unknown + or not valid for the section where was found. Possible reasons for this + error are: a typo in field name, missing empty line between control file + sections, or an extra empty line separating sections. +Ref: doc-base 2.3.2.1, doc-base 2.3.2.2 diff -Nru lintian-2.93.0/tags/d/doc-base-file-unknown-field.tag lintian-2.89.0ubuntu1/tags/d/doc-base-file-unknown-field.tag --- lintian-2.93.0/tags/d/doc-base-file-unknown-field.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/doc-base-file-unknown-field.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: doc-base-file-unknown-field -Severity: error -Check: menus -Explanation: The doc-base control file contains field which is either unknown - or not valid for the section where was found. Possible reasons for this - error are: a typo in field name, missing empty line between control file - sections, or an extra empty line separating sections. -See-Also: doc-base 2.3.2.1, doc-base 2.3.2.2 diff -Nru lintian-2.93.0/tags/d/doc-base-file-unknown-format.desc lintian-2.89.0ubuntu1/tags/d/doc-base-file-unknown-format.desc --- lintian-2.93.0/tags/d/doc-base-file-unknown-format.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/doc-base-file-unknown-format.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: doc-base-file-unknown-format +Severity: warning +Check: menus +Info: The Format field in this doc-base control file declares a format + that is not supported. Recognized formats are "HTML", "Text", "PDF", + "PostScript", "Info", "DVI", and "DebianDoc-SGML" (case-insensitive). +Ref: doc-base 2.3.2.2 diff -Nru lintian-2.93.0/tags/d/doc-base-file-unknown-format.tag lintian-2.89.0ubuntu1/tags/d/doc-base-file-unknown-format.tag --- lintian-2.93.0/tags/d/doc-base-file-unknown-format.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/doc-base-file-unknown-format.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: doc-base-file-unknown-format -Severity: warning -Check: menus -Explanation: The Format field in this doc-base control file declares a format - that is not supported. Recognized formats are "HTML", "Text", "PDF", - "PostScript", "Info", "DVI", and "DebianDoc-SGML" (case-insensitive). -See-Also: doc-base 2.3.2.2 diff -Nru lintian-2.93.0/tags/d/doc-base-index-references-multiple-files.desc lintian-2.89.0ubuntu1/tags/d/doc-base-index-references-multiple-files.desc --- lintian-2.93.0/tags/d/doc-base-index-references-multiple-files.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/doc-base-index-references-multiple-files.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: doc-base-index-references-multiple-files +Severity: error +Check: menus +Info: The Index field in a doc-base file should reference the single index + file for that document. Any other files belonging to the same document + should be listed in the Files field. +Ref: doc-base 2.3.2.2 diff -Nru lintian-2.93.0/tags/d/doc-base-index-references-multiple-files.tag lintian-2.89.0ubuntu1/tags/d/doc-base-index-references-multiple-files.tag --- lintian-2.93.0/tags/d/doc-base-index-references-multiple-files.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/doc-base-index-references-multiple-files.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: doc-base-index-references-multiple-files -Severity: error -Check: menus -Explanation: The Index field in a doc-base file should reference the single index - file for that document. Any other files belonging to the same document - should be listed in the Files field. -See-Also: doc-base 2.3.2.2 diff -Nru lintian-2.93.0/tags/d/doc-base-invalid-document-field.desc lintian-2.89.0ubuntu1/tags/d/doc-base-invalid-document-field.desc --- lintian-2.93.0/tags/d/doc-base-invalid-document-field.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/doc-base-invalid-document-field.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: doc-base-invalid-document-field +Severity: error +Check: menus +Info: The Document field should consists only of letters (a-z), digits + (0-9), plus (+) or minus (-) signs, and dots (.). In particular, + uppercase letters are not allowed. +Ref: doc-base 2.2 diff -Nru lintian-2.93.0/tags/d/doc-base-invalid-document-field.tag lintian-2.89.0ubuntu1/tags/d/doc-base-invalid-document-field.tag --- lintian-2.93.0/tags/d/doc-base-invalid-document-field.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/doc-base-invalid-document-field.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: doc-base-invalid-document-field -Severity: error -Check: menus -Explanation: The Document field should consists only of letters (a-z), digits - (0-9), plus (+) or minus (-) signs, and dots (.). In particular, - uppercase letters are not allowed. -See-Also: doc-base 2.2 diff -Nru lintian-2.93.0/tags/d/doc-base-unknown-section.desc lintian-2.89.0ubuntu1/tags/d/doc-base-unknown-section.desc --- lintian-2.93.0/tags/d/doc-base-unknown-section.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/doc-base-unknown-section.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: doc-base-unknown-section +Severity: warning +Check: menus +Info: The section indicated in this doc-base control file is not one of + the standard doc-base sections. The doc-base sections are based on the + menu sections but are not exactly the same. +Ref: doc-base 2.3.3, /usr/share/doc/doc-base/doc-base.html/index.html diff -Nru lintian-2.93.0/tags/d/doc-base-unknown-section.tag lintian-2.89.0ubuntu1/tags/d/doc-base-unknown-section.tag --- lintian-2.93.0/tags/d/doc-base-unknown-section.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/doc-base-unknown-section.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: doc-base-unknown-section -Severity: warning -Check: menus -Explanation: The section indicated in this doc-base control file is not one of - the standard doc-base sections. The doc-base sections are based on the - menu sections but are not exactly the same. -See-Also: doc-base 2.3.3, /usr/share/doc/doc-base/doc-base.html/index.html diff -Nru lintian-2.93.0/tags/d/doc-base-uses-applications-section.desc lintian-2.89.0ubuntu1/tags/d/doc-base-uses-applications-section.desc --- lintian-2.93.0/tags/d/doc-base-uses-applications-section.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/doc-base-uses-applications-section.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: doc-base-uses-applications-section +Severity: warning +Check: menus +Info: The section indicated in this doc-base control file has a top-level + section of Apps or Applications. This section is only used in menu, not + in doc-base. Simply removing the Applications/ part of the + section will lead to a valid doc-base section. +Ref: doc-base 2.3.3 diff -Nru lintian-2.93.0/tags/d/doc-base-uses-applications-section.tag lintian-2.89.0ubuntu1/tags/d/doc-base-uses-applications-section.tag --- lintian-2.93.0/tags/d/doc-base-uses-applications-section.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/doc-base-uses-applications-section.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: doc-base-uses-applications-section -Severity: warning -Check: menus -Explanation: The section indicated in this doc-base control file has a top-level - section of Apps or Applications. This section is only used in menu, not - in doc-base. Simply removing the Applications/ part of the - section will lead to a valid doc-base section. -See-Also: doc-base 2.3.3 diff -Nru lintian-2.93.0/tags/d/doc-package-depends-on-main-package.desc lintian-2.89.0ubuntu1/tags/d/doc-package-depends-on-main-package.desc --- lintian-2.93.0/tags/d/doc-package-depends-on-main-package.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/doc-package-depends-on-main-package.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: doc-package-depends-on-main-package +Severity: warning +Certainty: possible +Check: fields/package-relations +Info: The name of this package suggests that it is a documentation package. + It is usually not desirable for documentation packages to depend on the + packages they document, because users may want to install the docs before + they decide whether they want to install the package. Also, documentation + packages are often architecture-independent, so on other architectures + the package on which it depends may not even exist. diff -Nru lintian-2.93.0/tags/d/doc-package-depends-on-main-package.tag lintian-2.89.0ubuntu1/tags/d/doc-package-depends-on-main-package.tag --- lintian-2.93.0/tags/d/doc-package-depends-on-main-package.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/doc-package-depends-on-main-package.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: doc-package-depends-on-main-package -Severity: warning -Check: fields/package-relations -Explanation: The name of this package suggests that it is a documentation package. - It is usually not desirable for documentation packages to depend on the - packages they document, because users may want to install the docs before - they decide whether they want to install the package. Also, documentation - packages are often architecture-independent, so on other architectures - the package on which it depends may not even exist. diff -Nru lintian-2.93.0/tags/d/documentation-package-not-architecture-independent.desc lintian-2.89.0ubuntu1/tags/d/documentation-package-not-architecture-independent.desc --- lintian-2.93.0/tags/d/documentation-package-not-architecture-independent.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/documentation-package-not-architecture-independent.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,5 @@ +Tag: documentation-package-not-architecture-independent +Severity: warning +Check: fields/architecture +Info: Documentation packages usually shouldn't carry anything that requires + recompiling on various architectures, in order to save space on mirrors. diff -Nru lintian-2.93.0/tags/d/documentation-package-not-architecture-independent.tag lintian-2.89.0ubuntu1/tags/d/documentation-package-not-architecture-independent.tag --- lintian-2.93.0/tags/d/documentation-package-not-architecture-independent.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/documentation-package-not-architecture-independent.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,5 +0,0 @@ -Tag: documentation-package-not-architecture-independent -Severity: warning -Check: fields/architecture -Explanation: Documentation packages usually shouldn't carry anything that requires - recompiling on various architectures, in order to save space on mirrors. diff -Nru lintian-2.93.0/tags/d/doubly-armored-upstream-signature.desc lintian-2.89.0ubuntu1/tags/d/doubly-armored-upstream-signature.desc --- lintian-2.93.0/tags/d/doubly-armored-upstream-signature.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/doubly-armored-upstream-signature.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: doubly-armored-upstream-signature +Severity: error +Check: upstream-signature +Info: The packaging includes a detached upstream signature file that was armored + twice (or more) using gpg --enarmor. That is an error. + . + Please armor the signature just once. You can also use standard tools such as + gpg --armor --detach-sig. diff -Nru lintian-2.93.0/tags/d/doubly-armored-upstream-signature.tag lintian-2.89.0ubuntu1/tags/d/doubly-armored-upstream-signature.tag --- lintian-2.93.0/tags/d/doubly-armored-upstream-signature.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/doubly-armored-upstream-signature.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: doubly-armored-upstream-signature -Severity: error -Check: upstream-signature -Explanation: The packaging includes a detached upstream signature file that was armored - twice (or more) using gpg --enarmor. That is an error. - . - Please armor the signature just once. You can also use standard tools such as - gpg --armor --detach-sig. diff -Nru lintian-2.93.0/tags/d/dpatch-build-dep-but-no-patch-list.desc lintian-2.89.0ubuntu1/tags/d/dpatch-build-dep-but-no-patch-list.desc --- lintian-2.93.0/tags/d/dpatch-build-dep-but-no-patch-list.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/dpatch-build-dep-but-no-patch-list.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,11 @@ +Tag: dpatch-build-dep-but-no-patch-list +Severity: warning +Check: debian/patches/dpatch +Info: Using dpatch requires you to explicitly list all patches you want + to apply in debian/patches/00list. This package build-depends on dpatch, + but does not provide a patch list. You should either remove the dpatch + build dependency or add a patch list. + . + Note that an empty file cannot be represented in the Debian diff, so an + empty patch list will disappear in the source package. If you intended + for the series file to be empty, add a comment line. diff -Nru lintian-2.93.0/tags/d/dpatch-build-dep-but-no-patch-list.tag lintian-2.89.0ubuntu1/tags/d/dpatch-build-dep-but-no-patch-list.tag --- lintian-2.93.0/tags/d/dpatch-build-dep-but-no-patch-list.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/dpatch-build-dep-but-no-patch-list.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,11 +0,0 @@ -Tag: dpatch-build-dep-but-no-patch-list -Severity: warning -Check: debian/patches/dpatch -Explanation: Using dpatch requires you to explicitly list all patches you want - to apply in debian/patches/00list. This package build-depends on dpatch, - but does not provide a patch list. You should either remove the dpatch - build dependency or add a patch list. - . - Note that an empty file cannot be represented in the Debian diff, so an - empty patch list will disappear in the source package. If you intended - for the series file to be empty, add a comment line. diff -Nru lintian-2.93.0/tags/d/dpatch-index-references-non-existent-patch.desc lintian-2.89.0ubuntu1/tags/d/dpatch-index-references-non-existent-patch.desc --- lintian-2.93.0/tags/d/dpatch-index-references-non-existent-patch.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/dpatch-index-references-non-existent-patch.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,5 @@ +Tag: dpatch-index-references-non-existent-patch +Severity: error +Check: debian/patches/dpatch +Info: In the 00list file listing all your dpatches, you referenced a file + that does not exist. This will lead to a fatal error when calling dpatch. diff -Nru lintian-2.93.0/tags/d/dpatch-index-references-non-existent-patch.tag lintian-2.89.0ubuntu1/tags/d/dpatch-index-references-non-existent-patch.tag --- lintian-2.93.0/tags/d/dpatch-index-references-non-existent-patch.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/dpatch-index-references-non-existent-patch.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,5 +0,0 @@ -Tag: dpatch-index-references-non-existent-patch -Severity: error -Check: debian/patches/dpatch -Explanation: In the 00list file listing all your dpatches, you referenced a file - that does not exist. This will lead to a fatal error when calling dpatch. diff -Nru lintian-2.93.0/tags/d/dpatch-missing-description.desc lintian-2.89.0ubuntu1/tags/d/dpatch-missing-description.desc --- lintian-2.93.0/tags/d/dpatch-missing-description.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/dpatch-missing-description.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,14 @@ +Tag: dpatch-missing-description +Severity: info +Check: debian/patches/dpatch +Info: dpatch files should carry a description of the included patch. + Description lines start with "## DP:". + . + As well as a description of the purpose and function of the patch, the + description should ideally contain author information, a URL for the bug + report (if any), Debian or upstream bugs fixed by it, upstream status, + the Debian version and date the patch was first included, and any other + information that would be useful if someone were investigating the + patch and underlying problem. Please consider using the DEP 3 format for + this information. +Ref: https://dep-team.pages.debian.net/deps/dep3/ diff -Nru lintian-2.93.0/tags/d/dpatch-missing-description.tag lintian-2.89.0ubuntu1/tags/d/dpatch-missing-description.tag --- lintian-2.93.0/tags/d/dpatch-missing-description.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/dpatch-missing-description.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,14 +0,0 @@ -Tag: dpatch-missing-description -Severity: info -Check: debian/patches/dpatch -Explanation: dpatch files should carry a description of the included patch. - Description lines start with "## DP:". - . - As well as a description of the purpose and function of the patch, the - description should ideally contain author information, a URL for the bug - report (if any), Debian or upstream bugs fixed by it, upstream status, - the Debian version and date the patch was first included, and any other - information that would be useful if someone were investigating the - patch and underlying problem. Please consider using the DEP 3 format for - this information. -See-Also: https://dep-team.pages.debian.net/deps/dep3/ diff -Nru lintian-2.93.0/tags/d/duplicate-changelog-files.desc lintian-2.89.0ubuntu1/tags/d/duplicate-changelog-files.desc --- lintian-2.93.0/tags/d/duplicate-changelog-files.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/duplicate-changelog-files.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: duplicate-changelog-files +Severity: warning +Certainty: possible +Check: files/duplicates +Info: The package appears to be shipping two copies of the changelog. + . + If the second copy is really needed, consider making it a symlink to + the canonical place for the relevant changelog. + . + Both upstream and Debian changelogs are checked with this tag. diff -Nru lintian-2.93.0/tags/d/duplicate-changelog-files.tag lintian-2.89.0ubuntu1/tags/d/duplicate-changelog-files.tag --- lintian-2.93.0/tags/d/duplicate-changelog-files.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/duplicate-changelog-files.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: duplicate-changelog-files -Severity: warning -Check: files/duplicates -Explanation: The package appears to be shipping two copies of the changelog. - . - If the second copy is really needed, consider making it a symlink to - the canonical place for the relevant changelog. - . - Both upstream and Debian changelogs are checked with this tag. diff -Nru lintian-2.93.0/tags/d/duplicate-conffile.desc lintian-2.89.0ubuntu1/tags/d/duplicate-conffile.desc --- lintian-2.93.0/tags/d/duplicate-conffile.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/duplicate-conffile.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: duplicate-conffile +Severity: error +Check: conffiles +Info: The file is listed more than once in your debian/conffiles file. + Usually, this is because debhelper (dh_installdeb, compat level 3 or higher) + will add any files in your package located in /etc automatically to the list + of conffiles, so if you do that manually too, you'll get duplicates. diff -Nru lintian-2.93.0/tags/d/duplicate-conffile.tag lintian-2.89.0ubuntu1/tags/d/duplicate-conffile.tag --- lintian-2.93.0/tags/d/duplicate-conffile.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/duplicate-conffile.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: duplicate-conffile -Severity: error -Check: conffiles -Explanation: The file is listed more than once in your debian/conffiles file. - Usually, this is because debhelper (dh_installdeb, compat level 3 or higher) - will add any files in your package located in /etc automatically to the list - of conffiles, so if you do that manually too, you'll get duplicates. diff -Nru lintian-2.93.0/tags/d/duplicate-contact.desc lintian-2.89.0ubuntu1/tags/d/duplicate-contact.desc --- lintian-2.93.0/tags/d/duplicate-contact.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/duplicate-contact.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,5 @@ +Tag: duplicate-contact +Severity: warning +Check: fields/mail-address +Info: The contact appears more than once in the named field. + The duplicate information should be removed. diff -Nru lintian-2.93.0/tags/d/duplicate-contact.tag lintian-2.89.0ubuntu1/tags/d/duplicate-contact.tag --- lintian-2.93.0/tags/d/duplicate-contact.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/duplicate-contact.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,5 +0,0 @@ -Tag: duplicate-contact -Severity: warning -Check: fields/mail-address -Explanation: The contact appears more than once in the named field. - The duplicate information should be removed. diff -Nru lintian-2.93.0/tags/d/duplicate-entry-in-symbols-control-file.desc lintian-2.89.0ubuntu1/tags/d/duplicate-entry-in-symbols-control-file.desc --- lintian-2.93.0/tags/d/duplicate-entry-in-symbols-control-file.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/duplicate-entry-in-symbols-control-file.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,4 @@ +Tag: duplicate-entry-in-symbols-control-file +Severity: error +Check: shared-libs +Info: The symbols control file contains a duplicate entry. diff -Nru lintian-2.93.0/tags/d/duplicate-entry-in-symbols-control-file.tag lintian-2.89.0ubuntu1/tags/d/duplicate-entry-in-symbols-control-file.tag --- lintian-2.93.0/tags/d/duplicate-entry-in-symbols-control-file.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/duplicate-entry-in-symbols-control-file.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,4 +0,0 @@ -Tag: duplicate-entry-in-symbols-control-file -Severity: error -Check: shared-libs -Explanation: The symbols control file contains a duplicate entry. diff -Nru lintian-2.93.0/tags/d/duplicate-field-in-doc-base.desc lintian-2.89.0ubuntu1/tags/d/duplicate-field-in-doc-base.desc --- lintian-2.93.0/tags/d/duplicate-field-in-doc-base.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/duplicate-field-in-doc-base.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,5 @@ +Tag: duplicate-field-in-doc-base +Severity: error +Check: menus +Renamed-From: doc-base-file-duplicated-field +Info: The doc-base control file contains a duplicated field. diff -Nru lintian-2.93.0/tags/d/duplicate-field-in-doc-base.tag lintian-2.89.0ubuntu1/tags/d/duplicate-field-in-doc-base.tag --- lintian-2.93.0/tags/d/duplicate-field-in-doc-base.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/duplicate-field-in-doc-base.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,5 +0,0 @@ -Tag: duplicate-field-in-doc-base -Severity: error -Check: menus -Renamed-From: doc-base-file-duplicated-field -Explanation: The doc-base control file contains a duplicated field. diff -Nru lintian-2.93.0/tags/d/duplicate-files.desc lintian-2.89.0ubuntu1/tags/d/duplicate-files.desc --- lintian-2.93.0/tags/d/duplicate-files.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/duplicate-files.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,17 @@ +Tag: duplicate-files +Severity: pedantic +Certainty: possible +Check: files/duplicates +Experimental: yes +Ref: jdupes(1) +Info: The package ships the two (or more) files with the exact same + contents. + . + Duplicates can often be replaced with symlinks by running: + . + jdupes -rl debian/${binary}/usr + . + ... after they are installed, eg. in override_dh_link. In + addition, please consider reporting this upstream. + . + Note: empty files are exempt from this check. diff -Nru lintian-2.93.0/tags/d/duplicate-files.tag lintian-2.89.0ubuntu1/tags/d/duplicate-files.tag --- lintian-2.93.0/tags/d/duplicate-files.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/duplicate-files.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,16 +0,0 @@ -Tag: duplicate-files -Severity: pedantic -Check: files/duplicates -Experimental: yes -See-Also: jdupes(1) -Explanation: The package ships the two (or more) files with the exact same - contents. - . - Duplicates can often be replaced with symlinks by running: - . - jdupes -rl debian/${binary}/usr - . - ... after they are installed, eg. in override_dh_link. In - addition, please consider reporting this upstream. - . - Note: empty files are exempt from this check. diff -Nru lintian-2.93.0/tags/d/duplicate-font-file.desc lintian-2.89.0ubuntu1/tags/d/duplicate-font-file.desc --- lintian-2.93.0/tags/d/duplicate-font-file.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/duplicate-font-file.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,17 @@ +Tag: duplicate-font-file +Severity: warning +Certainty: possible +Check: fonts +Info: This package appears to include a font file that is already provided + by another package in Debian. Ideally it should instead depend on the + relevant font package. If the application in this package loads the font + file by name, you may need to include a symlink pointing to the file name + of the font in its Debian package. + . + Sometimes the font package containing the font is huge and you only need + one font. In that case, you have a few options: modify the package (in + conjunction with upstream) to use libfontconfig to find the font that you + prefer but fall back on whatever installed font is available, ask that + the font package be split apart into packages of a more reasonable size, + or add an override and be aware of the duplication when new versions of + the font are released. diff -Nru lintian-2.93.0/tags/d/duplicate-font-file.tag lintian-2.89.0ubuntu1/tags/d/duplicate-font-file.tag --- lintian-2.93.0/tags/d/duplicate-font-file.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/duplicate-font-file.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,16 +0,0 @@ -Tag: duplicate-font-file -Severity: warning -Check: fonts -Explanation: This package appears to include a font file that is already provided - by another package in Debian. Ideally it should instead depend on the - relevant font package. If the application in this package loads the font - file by name, you may need to include a symlink pointing to the file name - of the font in its Debian package. - . - Sometimes the font package containing the font is huge and you only need - one font. In that case, you have a few options: modify the package (in - conjunction with upstream) to use libfontconfig to find the font that you - prefer but fall back on whatever installed font is available, ask that - the font package be split apart into packages of a more reasonable size, - or add an override and be aware of the duplication when new versions of - the font are released. diff -Nru lintian-2.93.0/tags/d/duplicate-format-in-doc-base.desc lintian-2.89.0ubuntu1/tags/d/duplicate-format-in-doc-base.desc --- lintian-2.93.0/tags/d/duplicate-format-in-doc-base.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/duplicate-format-in-doc-base.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: duplicate-format-in-doc-base +Severity: error +Check: menus +Renamed-From: doc-base-file-duplicated-format +Info: The doc-base control file contains a duplicated format. Doc-base + files must not register different documents in one control file. +Ref: doc-base 2.3.2.2 diff -Nru lintian-2.93.0/tags/d/duplicate-format-in-doc-base.tag lintian-2.89.0ubuntu1/tags/d/duplicate-format-in-doc-base.tag --- lintian-2.93.0/tags/d/duplicate-format-in-doc-base.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/duplicate-format-in-doc-base.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: duplicate-format-in-doc-base -Severity: error -Check: menus -Renamed-From: doc-base-file-duplicated-format -Explanation: The doc-base control file contains a duplicated format. Doc-base - files must not register different documents in one control file. -See-Also: doc-base 2.3.2.2 diff -Nru lintian-2.93.0/tags/d/duplicate-globbing-patterns.desc lintian-2.89.0ubuntu1/tags/d/duplicate-globbing-patterns.desc --- lintian-2.93.0/tags/d/duplicate-globbing-patterns.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/duplicate-globbing-patterns.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: duplicate-globbing-patterns +Severity: error +Check: debian/copyright/dep5 +Info: A globbing pattern was used again in debian/copyright. + It always an error and may indicate confusion about the applicable + license for the autor or any reader of the file. + . + Please remove all but one of the identical globbing patterns. +Ref: Bug#90574, + https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ diff -Nru lintian-2.93.0/tags/d/duplicate-globbing-patterns.tag lintian-2.89.0ubuntu1/tags/d/duplicate-globbing-patterns.tag --- lintian-2.93.0/tags/d/duplicate-globbing-patterns.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/duplicate-globbing-patterns.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,10 +0,0 @@ -Tag: duplicate-globbing-patterns -Severity: error -Check: debian/copyright/dep5 -Explanation: A globbing pattern was used again in debian/copyright. - It always an error and may indicate confusion about the applicable - license for the autor or any reader of the file. - . - Please remove all but one of the identical globbing patterns. -See-Also: Bug#90574, - https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ diff -Nru lintian-2.93.0/tags/d/duplicate-in-relation-field.desc lintian-2.89.0ubuntu1/tags/d/duplicate-in-relation-field.desc --- lintian-2.93.0/tags/d/duplicate-in-relation-field.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/duplicate-in-relation-field.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: duplicate-in-relation-field +Severity: pedantic +Check: debian/control +Info: The given field in the debian/control file contains + relations that are either identical or imply each other. The less + restrictive one can be removed. This is done automatically by + dpkg-source and dpkg-gencontrol, so this does not + affect the generated package. diff -Nru lintian-2.93.0/tags/d/duplicate-in-relation-field.tag lintian-2.89.0ubuntu1/tags/d/duplicate-in-relation-field.tag --- lintian-2.93.0/tags/d/duplicate-in-relation-field.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/duplicate-in-relation-field.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: duplicate-in-relation-field -Severity: pedantic -Check: debian/control -Explanation: The given field in the debian/control file contains - relations that are either identical or imply each other. The less - restrictive one can be removed. This is done automatically by - dpkg-source and dpkg-gencontrol, so this does not - affect the generated package. diff -Nru lintian-2.93.0/tags/d/duplicate-in-shlibs.desc lintian-2.89.0ubuntu1/tags/d/duplicate-in-shlibs.desc --- lintian-2.93.0/tags/d/duplicate-in-shlibs.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/duplicate-in-shlibs.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,5 @@ +Tag: duplicate-in-shlibs +Severity: error +Check: shared-libs +Renamed-From: duplicate-entry-in-shlibs-control-file +Info: The shlibs control file contains a duplicate entry. diff -Nru lintian-2.93.0/tags/d/duplicate-in-shlibs.tag lintian-2.89.0ubuntu1/tags/d/duplicate-in-shlibs.tag --- lintian-2.93.0/tags/d/duplicate-in-shlibs.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/duplicate-in-shlibs.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,5 +0,0 @@ -Tag: duplicate-in-shlibs -Severity: error -Check: shared-libs -Renamed-From: duplicate-entry-in-shlibs-control-file -Explanation: The shlibs control file contains a duplicate entry. diff -Nru lintian-2.93.0/tags/d/duplicate-key-in-desktop.desc lintian-2.89.0ubuntu1/tags/d/duplicate-key-in-desktop.desc --- lintian-2.93.0/tags/d/duplicate-key-in-desktop.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/duplicate-key-in-desktop.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: duplicate-key-in-desktop +Severity: warning +Check: menu-format +Renamed-From: duplicated-key-in-desktop-entry +Info: The desktop entry contains two instances of the same key. The + behavior of such desktop entries is not well-defined by the standard. + . + The desktop-file-validate tool in the desktop-file-utils package is + useful for checking the syntax of desktop entries. diff -Nru lintian-2.93.0/tags/d/duplicate-key-in-desktop.tag lintian-2.89.0ubuntu1/tags/d/duplicate-key-in-desktop.tag --- lintian-2.93.0/tags/d/duplicate-key-in-desktop.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/duplicate-key-in-desktop.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: duplicate-key-in-desktop -Severity: warning -Check: menu-format -Renamed-From: duplicated-key-in-desktop-entry -Explanation: The desktop entry contains two instances of the same key. The - behavior of such desktop entries is not well-defined by the standard. - . - The desktop-file-validate tool in the desktop-file-utils package is - useful for checking the syntax of desktop entries. diff -Nru lintian-2.93.0/tags/d/duplicate-long-description.desc lintian-2.89.0ubuntu1/tags/d/duplicate-long-description.desc --- lintian-2.93.0/tags/d/duplicate-long-description.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/duplicate-long-description.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: duplicate-long-description +Severity: info +Check: debian/control +Info: The listed binary packages all share the same extended description. + Some additional information in the extended description explaining what + is in each package and how it differs from the other packages is useful, + particularly for users who aren't familiar with Debian's package naming + conventions. diff -Nru lintian-2.93.0/tags/d/duplicate-long-description-in-template.desc lintian-2.89.0ubuntu1/tags/d/duplicate-long-description-in-template.desc --- lintian-2.93.0/tags/d/duplicate-long-description-in-template.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/duplicate-long-description-in-template.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: duplicate-long-description-in-template +Severity: warning +Check: debian/debconf +Info: The long description of one of the templates provided by this package + is a duplicate of the short description. If you cannot provide a good + extended description, it is better to leave it blank. diff -Nru lintian-2.93.0/tags/d/duplicate-long-description-in-template.tag lintian-2.89.0ubuntu1/tags/d/duplicate-long-description-in-template.tag --- lintian-2.93.0/tags/d/duplicate-long-description-in-template.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/duplicate-long-description-in-template.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: duplicate-long-description-in-template -Severity: warning -Check: debian/debconf -Explanation: The long description of one of the templates provided by this package - is a duplicate of the short description. If you cannot provide a good - extended description, it is better to leave it blank. diff -Nru lintian-2.93.0/tags/d/duplicate-long-description.tag lintian-2.89.0ubuntu1/tags/d/duplicate-long-description.tag --- lintian-2.93.0/tags/d/duplicate-long-description.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/duplicate-long-description.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: duplicate-long-description -Severity: info -Check: debian/control -Explanation: The listed binary packages all share the same extended description. - Some additional information in the extended description explaining what - is in each package and how it differs from the other packages is useful, - particularly for users who aren't familiar with Debian's package naming - conventions. diff -Nru lintian-2.93.0/tags/d/duplicate-packaging-file.desc lintian-2.89.0ubuntu1/tags/d/duplicate-packaging-file.desc --- lintian-2.93.0/tags/d/duplicate-packaging-file.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/duplicate-packaging-file.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,14 @@ +Tag: duplicate-packaging-file +Severity: warning +Check: debian/filenames +Info: Some packaging files obtain different names when they are copied + from source to installation packages. Debhelper sometimes adds *.Debian + extensions to NEWS, README and TODO files. That can be confusing. + . + Debhelper's behavior also depends on the filename. + . + This source package contains both a file with the proper name and also + a file with incorrect name. Please remove the file as indicated. + . + Please merge all relevant information into the surviving file. +Ref: #429510, #946126 diff -Nru lintian-2.93.0/tags/d/duplicate-packaging-file.tag lintian-2.89.0ubuntu1/tags/d/duplicate-packaging-file.tag --- lintian-2.93.0/tags/d/duplicate-packaging-file.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/duplicate-packaging-file.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,14 +0,0 @@ -Tag: duplicate-packaging-file -Severity: warning -Check: debian/filenames -Explanation: Some packaging files obtain different names when they are copied - from source to installation packages. Debhelper sometimes adds *.Debian - extensions to NEWS, README and TODO files. That can be confusing. - . - Debhelper's behavior also depends on the filename. - . - This source package contains both a file with the proper name and also - a file with incorrect name. Please remove the file as indicated. - . - Please merge all relevant information into the surviving file. -See-Also: Bug#429510, Bug#946126 diff -Nru lintian-2.93.0/tags/d/duplicate-short-description.desc lintian-2.89.0ubuntu1/tags/d/duplicate-short-description.desc --- lintian-2.93.0/tags/d/duplicate-short-description.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/duplicate-short-description.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: duplicate-short-description +Severity: info +Certainty: possible +Check: debian/control +Info: The listed binary packages all share the same short description (the + first line of the Description control field). The package names may + provide enough additional information to distinguish between the + packages, but it's common to also add a word or two to the short + description to clarify the difference. diff -Nru lintian-2.93.0/tags/d/duplicate-short-description.tag lintian-2.89.0ubuntu1/tags/d/duplicate-short-description.tag --- lintian-2.93.0/tags/d/duplicate-short-description.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/duplicate-short-description.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: duplicate-short-description -Severity: info -Check: debian/control -Explanation: The listed binary packages all share the same short description (the - first line of the Description control field). The package names may - provide enough additional information to distinguish between the - packages, but it's common to also add a word or two to the short - description to clarify the difference. diff -Nru lintian-2.93.0/tags/d/duplicate-tag-in-menu.desc lintian-2.89.0ubuntu1/tags/d/duplicate-tag-in-menu.desc --- lintian-2.93.0/tags/d/duplicate-tag-in-menu.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/duplicate-tag-in-menu.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: duplicate-tag-in-menu +Severity: warning +Check: menu-format +Renamed-From: duplicated-tag-in-menu-item +Info: The menu item contains two instances of the same tag. This is just a + waste of space, as menu will only use one of them. +Ref: menu 3.2 diff -Nru lintian-2.93.0/tags/d/duplicate-tag-in-menu.tag lintian-2.89.0ubuntu1/tags/d/duplicate-tag-in-menu.tag --- lintian-2.93.0/tags/d/duplicate-tag-in-menu.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/duplicate-tag-in-menu.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: duplicate-tag-in-menu -Severity: warning -Check: menu-format -Renamed-From: duplicated-tag-in-menu-item -Explanation: The menu item contains two instances of the same tag. This is just a - waste of space, as menu will only use one of them. -See-Also: menu 3.2 diff -Nru lintian-2.93.0/tags/d/duplicate-updaterc.d-calls-in-postinst.desc lintian-2.89.0ubuntu1/tags/d/duplicate-updaterc.d-calls-in-postinst.desc --- lintian-2.93.0/tags/d/duplicate-updaterc.d-calls-in-postinst.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/duplicate-updaterc.d-calls-in-postinst.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,5 @@ +Tag: duplicate-updaterc.d-calls-in-postinst +Severity: error +Check: init.d +Info: The postinst script calls update-rc.d several + times for the same /etc/init.d script. diff -Nru lintian-2.93.0/tags/d/duplicate-updaterc.d-calls-in-postinst.tag lintian-2.89.0ubuntu1/tags/d/duplicate-updaterc.d-calls-in-postinst.tag --- lintian-2.93.0/tags/d/duplicate-updaterc.d-calls-in-postinst.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/duplicate-updaterc.d-calls-in-postinst.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,5 +0,0 @@ -Tag: duplicate-updaterc.d-calls-in-postinst -Severity: error -Check: init.d -Explanation: The postinst script calls update-rc.d several - times for the same /etc/init.d script. diff -Nru lintian-2.93.0/tags/d/duplicate-updaterc.d-calls-in-postrm.desc lintian-2.89.0ubuntu1/tags/d/duplicate-updaterc.d-calls-in-postrm.desc --- lintian-2.93.0/tags/d/duplicate-updaterc.d-calls-in-postrm.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/duplicate-updaterc.d-calls-in-postrm.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,5 @@ +Tag: duplicate-updaterc.d-calls-in-postrm +Severity: error +Check: init.d +Info: The postrm script calls update-rc.d several + times for the same /etc/init.d script. diff -Nru lintian-2.93.0/tags/d/duplicate-updaterc.d-calls-in-postrm.tag lintian-2.89.0ubuntu1/tags/d/duplicate-updaterc.d-calls-in-postrm.tag --- lintian-2.93.0/tags/d/duplicate-updaterc.d-calls-in-postrm.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/d/duplicate-updaterc.d-calls-in-postrm.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,5 +0,0 @@ -Tag: duplicate-updaterc.d-calls-in-postrm -Severity: error -Check: init.d -Explanation: The postrm script calls update-rc.d several - times for the same /etc/init.d script. diff -Nru lintian-2.93.0/tags/e/elf-maintainer-script.desc lintian-2.89.0ubuntu1/tags/e/elf-maintainer-script.desc --- lintian-2.93.0/tags/e/elf-maintainer-script.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/e/elf-maintainer-script.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,4 @@ +Tag: elf-maintainer-script +Severity: classification +Check: scripts +Info: The maintainer script is an ELF binary. diff -Nru lintian-2.93.0/tags/e/elf-maintainer-script.tag lintian-2.89.0ubuntu1/tags/e/elf-maintainer-script.tag --- lintian-2.93.0/tags/e/elf-maintainer-script.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/e/elf-maintainer-script.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,4 +0,0 @@ -Tag: elf-maintainer-script -Severity: classification -Check: scripts -Explanation: The maintainer script is an ELF binary. diff -Nru lintian-2.93.0/tags/e/emacsen-common-without-dh-elpa.desc lintian-2.89.0ubuntu1/tags/e/emacsen-common-without-dh-elpa.desc --- lintian-2.93.0/tags/e/emacsen-common-without-dh-elpa.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/e/emacsen-common-without-dh-elpa.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,15 @@ +Tag: emacsen-common-without-dh-elpa +Severity: warning +Check: emacs/elpa +Info: The package uses the emacsen-common infrastructure but the + package was not built with dh-elpa. Please consider transitioning + the package build to use dh-elpa, unless the package is required to + work with XEmacs. + . + dh-elpa centralises the emacsen-common maintscripts, which makes for + fewer bugs, and significantly easier cross-archive updates to emacsen + packages. + . + In addition, a package built with dh-elpa integrates with the GNU + Emacs package manager, for a better user experience. +Ref: dh_elpa(1), dh-make-elpa(1), https://wiki.debian.org/Teams/DebianEmacsenTeam/elpa-hello diff -Nru lintian-2.93.0/tags/e/emacsen-common-without-dh-elpa.tag lintian-2.89.0ubuntu1/tags/e/emacsen-common-without-dh-elpa.tag --- lintian-2.93.0/tags/e/emacsen-common-without-dh-elpa.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/e/emacsen-common-without-dh-elpa.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,15 +0,0 @@ -Tag: emacsen-common-without-dh-elpa -Severity: warning -Check: emacs/elpa -Explanation: The package uses the emacsen-common infrastructure but the - package was not built with dh-elpa. Please consider transitioning - the package build to use dh-elpa, unless the package is required to - work with XEmacs. - . - dh-elpa centralises the emacsen-common maintscripts, which makes for - fewer bugs, and significantly easier cross-archive updates to emacsen - packages. - . - In addition, a package built with dh-elpa integrates with the GNU - Emacs package manager, for a better user experience. -See-Also: dh_elpa(1), dh-make-elpa(1), https://wiki.debian.org/Teams/DebianEmacsenTeam/elpa-hello diff -Nru lintian-2.93.0/tags/e/embedded-feedparser-library.desc lintian-2.89.0ubuntu1/tags/e/embedded-feedparser-library.desc --- lintian-2.93.0/tags/e/embedded-feedparser-library.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/e/embedded-feedparser-library.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: embedded-feedparser-library +Severity: warning +Check: languages/python/feedparser +Info: This package contains an embedded copy of Mark Pilgrim's Universal + Feed Parser. Please depend on the "python-feedparser" package and use + the normal Python import mechanism to load it. +Ref: policy 4.13 diff -Nru lintian-2.93.0/tags/e/embedded-feedparser-library.tag lintian-2.89.0ubuntu1/tags/e/embedded-feedparser-library.tag --- lintian-2.93.0/tags/e/embedded-feedparser-library.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/e/embedded-feedparser-library.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: embedded-feedparser-library -Severity: warning -Check: languages/python/feedparser -Explanation: This package contains an embedded copy of Mark Pilgrim's Universal - Feed Parser. Please depend on the "python-feedparser" package and use - the normal Python import mechanism to load it. -See-Also: policy 4.13 diff -Nru lintian-2.93.0/tags/e/embedded-javascript-library.desc lintian-2.89.0ubuntu1/tags/e/embedded-javascript-library.desc --- lintian-2.93.0/tags/e/embedded-javascript-library.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/e/embedded-javascript-library.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: embedded-javascript-library +Severity: warning +Certainty: possible +Check: languages/javascript/embedded +Info: This package contains an embedded copy of JavaScript libraries + that are now available in their own packages (for example, JQuery, + Prototype, Mochikit or "Cropper"). Please depend on the appropriate + package and symlink the library into the appropriate location. +Ref: policy 4.13 diff -Nru lintian-2.93.0/tags/e/embedded-javascript-library.tag lintian-2.89.0ubuntu1/tags/e/embedded-javascript-library.tag --- lintian-2.93.0/tags/e/embedded-javascript-library.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/e/embedded-javascript-library.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: embedded-javascript-library -Severity: warning -Check: languages/javascript/embedded -Explanation: This package contains an embedded copy of JavaScript libraries - that are now available in their own packages (for example, JQuery, - Prototype, Mochikit or "Cropper"). Please depend on the appropriate - package and symlink the library into the appropriate location. -See-Also: policy 4.13 diff -Nru lintian-2.93.0/tags/e/embedded-library.desc lintian-2.89.0ubuntu1/tags/e/embedded-library.desc --- lintian-2.93.0/tags/e/embedded-library.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/e/embedded-library.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,13 @@ +Tag: embedded-library +Severity: error +Certainty: possible +Check: binaries +Ref: policy 4.13 +Info: The given ELF object appears to have been statically linked to + a library. Doing this is strongly discouraged due to the extra work + needed by the security team to fix all the extra embedded copies or + trigger the package rebuilds, as appropriate. + . + If the package uses a modified version of the given library it is highly + recommended to coordinate with the library's maintainer to include the + changes on the system version of the library. diff -Nru lintian-2.93.0/tags/e/embedded-library.tag lintian-2.89.0ubuntu1/tags/e/embedded-library.tag --- lintian-2.93.0/tags/e/embedded-library.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/e/embedded-library.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,12 +0,0 @@ -Tag: embedded-library -Severity: error -Check: binaries -See-Also: policy 4.13 -Explanation: The given ELF object appears to have been statically linked to - a library. Doing this is strongly discouraged due to the extra work - needed by the security team to fix all the extra embedded copies or - trigger the package rebuilds, as appropriate. - . - If the package uses a modified version of the given library it is highly - recommended to coordinate with the library's maintainer to include the - changes on the system version of the library. diff -Nru lintian-2.93.0/tags/e/embedded-pear-module.desc lintian-2.89.0ubuntu1/tags/e/embedded-pear-module.desc --- lintian-2.93.0/tags/e/embedded-pear-module.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/e/embedded-pear-module.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: embedded-pear-module +Severity: warning +Certainty: possible +Check: languages/php/pear/embedded +Experimental: yes +Info: This package appears to contain an embedded copy of a PEAR module. + Please depend on the respective PEAR package providing the module and + make sure the library can be found by the scripts via the include_path. +Ref: policy 4.13 diff -Nru lintian-2.93.0/tags/e/embedded-pear-module.tag lintian-2.89.0ubuntu1/tags/e/embedded-pear-module.tag --- lintian-2.93.0/tags/e/embedded-pear-module.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/e/embedded-pear-module.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: embedded-pear-module -Severity: warning -Check: languages/php/pear/embedded -Experimental: yes -Explanation: This package appears to contain an embedded copy of a PEAR module. - Please depend on the respective PEAR package providing the module and - make sure the library can be found by the scripts via the include_path. -See-Also: policy 4.13 diff -Nru lintian-2.93.0/tags/e/embedded-php-library.desc lintian-2.89.0ubuntu1/tags/e/embedded-php-library.desc --- lintian-2.93.0/tags/e/embedded-php-library.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/e/embedded-php-library.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: embedded-php-library +Severity: warning +Certainty: possible +Check: languages/php/embedded +Info: This package appears to contain an embedded copy of a PHP library. + Please depend on the respective package providing the library and + make sure it can be found by the scripts via the include_path. +Ref: policy 4.13 diff -Nru lintian-2.93.0/tags/e/embedded-php-library.tag lintian-2.89.0ubuntu1/tags/e/embedded-php-library.tag --- lintian-2.93.0/tags/e/embedded-php-library.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/e/embedded-php-library.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: embedded-php-library -Severity: warning -Check: languages/php/embedded -Explanation: This package appears to contain an embedded copy of a PHP library. - Please depend on the respective package providing the library and - make sure it can be found by the scripts via the include_path. -See-Also: policy 4.13 diff -Nru lintian-2.93.0/tags/e/embedded-script-includes-copyright-statement.desc lintian-2.89.0ubuntu1/tags/e/embedded-script-includes-copyright-statement.desc --- lintian-2.93.0/tags/e/embedded-script-includes-copyright-statement.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/e/embedded-script-includes-copyright-statement.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,12 @@ +Tag: embedded-script-includes-copyright-statement +Severity: pedantic +Certainty: possible +Check: cruft +Info: The specified file includes an embedded script with a copyright + statement. + . + The script was likely copy-pasted and likely needs to be rebuilt from + the original source. + . + This script may be also outdated and may need need to be updated from a + security point of view. diff -Nru lintian-2.93.0/tags/e/embedded-script-includes-copyright-statement.tag lintian-2.89.0ubuntu1/tags/e/embedded-script-includes-copyright-statement.tag --- lintian-2.93.0/tags/e/embedded-script-includes-copyright-statement.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/e/embedded-script-includes-copyright-statement.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,11 +0,0 @@ -Tag: embedded-script-includes-copyright-statement -Severity: pedantic -Check: cruft -Explanation: The specified file includes an embedded script with a copyright - statement. - . - The script was likely copy-pasted and likely needs to be rebuilt from - the original source. - . - This script may be also outdated and may need need to be updated from a - security point of view. diff -Nru lintian-2.93.0/tags/e/empty-binary-package.desc lintian-2.89.0ubuntu1/tags/e/empty-binary-package.desc --- lintian-2.93.0/tags/e/empty-binary-package.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/e/empty-binary-package.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,18 @@ +Tag: empty-binary-package +Severity: warning +Certainty: wild-guess +Check: files/empty-package +Info: This binary package appears to be empty, and its description does + not say that it's a metapackage or a transitional package. This is + often due to problems with updating debhelper *.install files during + package renames or similar problems where installation rules don't put + files in the correct place. + . + If the package is deliberately empty, please mention in the package long + description one of the phrases "metapackage", "dummy", "dependency + package", or "empty package". + . + Previously, Lintian also accepted the use of "virtual package". This + was removed to avoid overloading the term. If you have been relying on + the phrase "virtual package" to avoid this warning, please replace it + with one of the others. diff -Nru lintian-2.93.0/tags/e/empty-binary-package.tag lintian-2.89.0ubuntu1/tags/e/empty-binary-package.tag --- lintian-2.93.0/tags/e/empty-binary-package.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/e/empty-binary-package.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,17 +0,0 @@ -Tag: empty-binary-package -Severity: warning -Check: files/empty-package -Explanation: This binary package appears to be empty, and its description does - not say that it's a metapackage or a transitional package. This is - often due to problems with updating debhelper *.install files during - package renames or similar problems where installation rules don't put - files in the correct place. - . - If the package is deliberately empty, please mention in the package long - description one of the phrases "metapackage", "dummy", "dependency - package", or "empty package". - . - Previously, Lintian also accepted the use of "virtual package". This - was removed to avoid overloading the term. If you have been relying on - the phrase "virtual package" to avoid this warning, please replace it - with one of the others. diff -Nru lintian-2.93.0/tags/e/empty-debian-diff.desc lintian-2.89.0ubuntu1/tags/e/empty-debian-diff.desc --- lintian-2.93.0/tags/e/empty-debian-diff.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/e/empty-debian-diff.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,16 @@ +Tag: empty-debian-diff +Severity: warning +Certainty: possible +Check: cruft +Info: The Debian diff of this non-native package appears to be completely + empty. This usually indicates a mistake when generating the upstream + tarball, or it may mean that this was intended to be a native package and + was built non-native by mistake. + . + If the Debian packaging is maintained in conjunction with upstream, this + may be intentional, but it's not recommended best practice. If the + software is only for Debian, it should be a native package; otherwise, + it's better to omit the debian directory from upstream releases + and add it in the Debian diff. Otherwise, it can cause problems for some + package updates in Debian (files can't be removed from the + debian directory via the diff, for example). diff -Nru lintian-2.93.0/tags/e/empty-debian-diff.tag lintian-2.89.0ubuntu1/tags/e/empty-debian-diff.tag --- lintian-2.93.0/tags/e/empty-debian-diff.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/e/empty-debian-diff.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,15 +0,0 @@ -Tag: empty-debian-diff -Severity: warning -Check: cruft -Explanation: The Debian diff of this non-native package appears to be completely - empty. This usually indicates a mistake when generating the upstream - tarball, or it may mean that this was intended to be a native package and - was built non-native by mistake. - . - If the Debian packaging is maintained in conjunction with upstream, this - may be intentional, but it's not recommended best practice. If the - software is only for Debian, it should be a native package; otherwise, - it's better to omit the debian directory from upstream releases - and add it in the Debian diff. Otherwise, it can cause problems for some - package updates in Debian (files can't be removed from the - debian directory via the diff, for example). diff -Nru lintian-2.93.0/tags/e/empty-debian-tests-control.desc lintian-2.89.0ubuntu1/tags/e/empty-debian-tests-control.desc --- lintian-2.93.0/tags/e/empty-debian-tests-control.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/e/empty-debian-tests-control.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: empty-debian-tests-control +Severity: error +Check: testsuite +Info: + The debian/tests/control is empty when any comments are removed. +Ref: https://salsa.debian.org/ci-team/autopkgtest/tree/master/doc/README.package-tests.rst diff -Nru lintian-2.93.0/tags/e/empty-debian-tests-control.tag lintian-2.89.0ubuntu1/tags/e/empty-debian-tests-control.tag --- lintian-2.93.0/tags/e/empty-debian-tests-control.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/e/empty-debian-tests-control.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: empty-debian-tests-control -Severity: error -Check: testsuite -Explanation: - The debian/tests/control is empty when any comments are removed. -See-Also: https://salsa.debian.org/ci-team/autopkgtest/tree/master/doc/README.package-tests.rst diff -Nru lintian-2.93.0/tags/e/empty-field.desc lintian-2.89.0ubuntu1/tags/e/empty-field.desc --- lintian-2.93.0/tags/e/empty-field.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/e/empty-field.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: empty-field +Severity: warning +Check: fields/empty +Info: The named field in this package's control file is empty + or consists only of whitespace. +Ref: policy 2.4, #879809 diff -Nru lintian-2.93.0/tags/e/empty-field.tag lintian-2.89.0ubuntu1/tags/e/empty-field.tag --- lintian-2.93.0/tags/e/empty-field.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/e/empty-field.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: empty-field -Severity: warning -Check: fields/empty -Explanation: The named field in this package's control file is empty - or consists only of whitespace. -See-Also: policy 2.4, Bug#879809 diff -Nru lintian-2.93.0/tags/e/empty-manual-page.desc lintian-2.89.0ubuntu1/tags/e/empty-manual-page.desc --- lintian-2.93.0/tags/e/empty-manual-page.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/e/empty-manual-page.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,4 @@ +Tag: empty-manual-page +Severity: error +Check: documentation/manual +Info: The referenced manual page is empty. diff -Nru lintian-2.93.0/tags/e/empty-manual-page.tag lintian-2.89.0ubuntu1/tags/e/empty-manual-page.tag --- lintian-2.93.0/tags/e/empty-manual-page.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/e/empty-manual-page.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,4 +0,0 @@ -Tag: empty-manual-page -Severity: error -Check: documentation/manual -Explanation: The referenced manual page is empty. diff -Nru lintian-2.93.0/tags/e/empty-shared-library-symbols.desc lintian-2.89.0ubuntu1/tags/e/empty-shared-library-symbols.desc --- lintian-2.93.0/tags/e/empty-shared-library-symbols.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/e/empty-shared-library-symbols.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,12 @@ +Tag: empty-shared-library-symbols +Severity: error +Check: shared-libs +Renamed-From: pkg-has-symbols-control-file-but-no-shared-libs +Info: Although the package does not include any shared libraries, it does + have a symbols control file. If you did include a shared library, check that + the SONAME of the library is set and that it matches the contents of the + symbols file. + . + SONAMEs are set with something like gcc -Wl,-soname,libfoo.so.0, + where 0 is the major version of the library. If your package uses libtool, + then libtool invoked with the right options should be doing this. diff -Nru lintian-2.93.0/tags/e/empty-shared-library-symbols.tag lintian-2.89.0ubuntu1/tags/e/empty-shared-library-symbols.tag --- lintian-2.93.0/tags/e/empty-shared-library-symbols.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/e/empty-shared-library-symbols.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,12 +0,0 @@ -Tag: empty-shared-library-symbols -Severity: error -Check: shared-libs -Renamed-From: pkg-has-symbols-control-file-but-no-shared-libs -Explanation: Although the package does not include any shared libraries, it does - have a symbols control file. If you did include a shared library, check that - the SONAME of the library is set and that it matches the contents of the - symbols file. - . - SONAMEs are set with something like gcc -Wl,-soname,libfoo.so.0, - where 0 is the major version of the library. If your package uses libtool, - then libtool invoked with the right options should be doing this. diff -Nru lintian-2.93.0/tags/e/empty-shlibs.desc lintian-2.89.0ubuntu1/tags/e/empty-shlibs.desc --- lintian-2.93.0/tags/e/empty-shlibs.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/e/empty-shlibs.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,16 @@ +Tag: empty-shlibs +Severity: error +Check: shared-libs +Renamed-From: pkg-has-shlibs-control-file-but-no-actual-shared-libs +Info: Although the package does not include any shared libraries, it does + have a shlibs control file. If you did include a shared library, check that + the SONAME of the library is set and that it matches the contents of the + shlibs file. + . + SONAMEs are set with something like gcc -Wl,-soname,libfoo.so.0, + where 0 is the major version of the library. If your package uses libtool, + then libtool invoked with the right options should be doing this. + . + Note this is sometimes triggered for packages with a private shared + library due to a bug in Debhelper. +Ref: #204975, #633853 diff -Nru lintian-2.93.0/tags/e/empty-shlibs.tag lintian-2.89.0ubuntu1/tags/e/empty-shlibs.tag --- lintian-2.93.0/tags/e/empty-shlibs.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/e/empty-shlibs.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,16 +0,0 @@ -Tag: empty-shlibs -Severity: error -Check: shared-libs -Renamed-From: pkg-has-shlibs-control-file-but-no-actual-shared-libs -Explanation: Although the package does not include any shared libraries, it does - have a shlibs control file. If you did include a shared library, check that - the SONAME of the library is set and that it matches the contents of the - shlibs file. - . - SONAMEs are set with something like gcc -Wl,-soname,libfoo.so.0, - where 0 is the major version of the library. If your package uses libtool, - then libtool invoked with the right options should be doing this. - . - Note this is sometimes triggered for packages with a private shared - library due to a bug in Debhelper. -See-Also: Bug#204975, Bug#633853 diff -Nru lintian-2.93.0/tags/e/empty-short-license-in-dep5-copyright.desc lintian-2.89.0ubuntu1/tags/e/empty-short-license-in-dep5-copyright.desc --- lintian-2.93.0/tags/e/empty-short-license-in-dep5-copyright.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/e/empty-short-license-in-dep5-copyright.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: empty-short-license-in-dep5-copyright +Severity: warning +Certainty: possible +Check: debian/copyright/dep5 +Ref: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ +Info: The short license field in the machine readable copyright file + is empty. diff -Nru lintian-2.93.0/tags/e/empty-short-license-in-dep5-copyright.tag lintian-2.89.0ubuntu1/tags/e/empty-short-license-in-dep5-copyright.tag --- lintian-2.93.0/tags/e/empty-short-license-in-dep5-copyright.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/e/empty-short-license-in-dep5-copyright.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: empty-short-license-in-dep5-copyright -Severity: warning -Check: debian/copyright/dep5 -See-Also: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ -Explanation: The short license field in the machine readable copyright file - is empty. diff -Nru lintian-2.93.0/tags/e/empty-translated-choices.desc lintian-2.89.0ubuntu1/tags/e/empty-translated-choices.desc --- lintian-2.93.0/tags/e/empty-translated-choices.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/e/empty-translated-choices.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: empty-translated-choices +Severity: error +Certainty: possible +Check: debian/debconf +Info: When the translation of a Choices: field is empty, the whole question + is skipped (and nothing is selected). Please verify that the translation + you're using is valid. diff -Nru lintian-2.93.0/tags/e/empty-translated-choices.tag lintian-2.89.0ubuntu1/tags/e/empty-translated-choices.tag --- lintian-2.93.0/tags/e/empty-translated-choices.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/e/empty-translated-choices.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: empty-translated-choices -Severity: error -Check: debian/debconf -Explanation: When the translation of a Choices: field is empty, the whole question - is skipped (and nothing is selected). Please verify that the translation - you're using is valid. diff -Nru lintian-2.93.0/tags/e/empty-udeb-package.desc lintian-2.89.0ubuntu1/tags/e/empty-udeb-package.desc --- lintian-2.93.0/tags/e/empty-udeb-package.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/e/empty-udeb-package.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,14 @@ +Tag: empty-udeb-package +Severity: info +Certainty: wild-guess +Check: files/empty-package +Experimental: yes +Info: This udeb package appears to be empty, and its description does + not say that it's a metapackage or a package. This is often due to + problems with updating debhelper *.install files during package + renames or similar problems where installation rules don't put files + in the correct place. + . + If the package is deliberately empty, you can avoid this tag by + using one of the following phrases "metapackage", "dummy", "dependency + package", or "empty package" in the long description of the udeb. diff -Nru lintian-2.93.0/tags/e/empty-udeb-package.tag lintian-2.89.0ubuntu1/tags/e/empty-udeb-package.tag --- lintian-2.93.0/tags/e/empty-udeb-package.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/e/empty-udeb-package.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,13 +0,0 @@ -Tag: empty-udeb-package -Severity: info -Check: files/empty-package -Experimental: yes -Explanation: This udeb package appears to be empty, and its description does - not say that it's a metapackage or a package. This is often due to - problems with updating debhelper *.install files during package - renames or similar problems where installation rules don't put files - in the correct place. - . - If the package is deliberately empty, you can avoid this tag by - using one of the following phrases "metapackage", "dummy", "dependency - package", or "empty package" in the long description of the udeb. diff -Nru lintian-2.93.0/tags/e/empty-upstream-sources.desc lintian-2.89.0ubuntu1/tags/e/empty-upstream-sources.desc --- lintian-2.93.0/tags/e/empty-upstream-sources.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/e/empty-upstream-sources.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,5 @@ +Tag: empty-upstream-sources +Severity: error +Check: origtar +Info: The .orig.tar.gz file is empty. +Ref: #471537 diff -Nru lintian-2.93.0/tags/e/empty-upstream-sources.tag lintian-2.89.0ubuntu1/tags/e/empty-upstream-sources.tag --- lintian-2.93.0/tags/e/empty-upstream-sources.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/e/empty-upstream-sources.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,5 +0,0 @@ -Tag: empty-upstream-sources -Severity: error -Check: origtar -Explanation: The .orig.tar.gz file is empty. -See-Also: Bug#471537 diff -Nru lintian-2.93.0/tags/e/epoch-changed-but-upstream-version-did-not-go-backwards.desc lintian-2.89.0ubuntu1/tags/e/epoch-changed-but-upstream-version-did-not-go-backwards.desc --- lintian-2.93.0/tags/e/epoch-changed-but-upstream-version-did-not-go-backwards.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/e/epoch-changed-but-upstream-version-did-not-go-backwards.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,28 @@ +Tag: epoch-changed-but-upstream-version-did-not-go-backwards +Severity: error +Certainty: possible +Check: debian/changelog +Info: The previous version of this package had a different version epoch + to the current version but the upstream version did not go "backwards". + For example, the previous package version was "1:1.0-1" and the current + version is "2:2.0-1". + . + This was likely an accidental bump or addition of an epoch. + . + Epochs exist to cope with changes to the upstream version numbering + scheme. Whilst they are a powerful tool, increasing or adding an epoch + has many downsides including causing issues with versioned dependencies, + being misleading to users and being aesthetically unappealing. Whilst + they should be avoided, valid reasons to add or increment the epoch + include: + . + - Upstream changed their versioning scheme in a way that makes the + latest version lower than the previous one. + - You need to permanently revert to a lower upstream version. + . + Temporary revertions (eg. after an NMU) should use not modify or + introduce an epoch - please use the CURRENT+reallyFORMER until + you can upload the latest version again. + . + If you are unsure whether you need to increase the epoch for a package, + please consult the debian-devel mailing list. diff -Nru lintian-2.93.0/tags/e/epoch-changed-but-upstream-version-did-not-go-backwards.tag lintian-2.89.0ubuntu1/tags/e/epoch-changed-but-upstream-version-did-not-go-backwards.tag --- lintian-2.93.0/tags/e/epoch-changed-but-upstream-version-did-not-go-backwards.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/e/epoch-changed-but-upstream-version-did-not-go-backwards.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,27 +0,0 @@ -Tag: epoch-changed-but-upstream-version-did-not-go-backwards -Severity: error -Check: debian/changelog -Explanation: The previous version of this package had a different version epoch - to the current version but the upstream version did not go "backwards". - For example, the previous package version was "1:1.0-1" and the current - version is "2:2.0-1". - . - This was likely an accidental bump or addition of an epoch. - . - Epochs exist to cope with changes to the upstream version numbering - scheme. Whilst they are a powerful tool, increasing or adding an epoch - has many downsides including causing issues with versioned dependencies, - being misleading to users and being aesthetically unappealing. Whilst - they should be avoided, valid reasons to add or increment the epoch - include: - . - - Upstream changed their versioning scheme in a way that makes the - latest version lower than the previous one. - - You need to permanently revert to a lower upstream version. - . - Temporary revertions (eg. after an NMU) should use not modify or - introduce an epoch - please use the CURRENT+reallyFORMER until - you can upload the latest version again. - . - If you are unsure whether you need to increase the epoch for a package, - please consult the debian-devel mailing list. diff -Nru lintian-2.93.0/tags/e/epoch-change-without-comment.desc lintian-2.89.0ubuntu1/tags/e/epoch-change-without-comment.desc --- lintian-2.93.0/tags/e/epoch-change-without-comment.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/e/epoch-change-without-comment.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,27 @@ +Tag: epoch-change-without-comment +Severity: warning +Certainty: possible +Check: debian/changelog +Info: The previous version of this package had a different version epoch + (eg. 2:1.0-1) to the current version but there's no reference to this in + the changelog entry. + . + Epochs exist to cope with changes to the upstream version numbering + scheme. Whilst they are a powerful tool, increasing or adding an epoch + has many downsides including causing issues with versioned dependencies, + being misleading to users and being aesthetically unappealing. Whilst + they should be avoided, valid reasons to add or increment the epoch + include: + . + - Upstream changed their versioning scheme in a way that makes the + latest version lower than the previous one. + - You need to permanently revert to a lower upstream version. + . + Temporary revertions (eg. after an NMU) should use not modify or + introduce an epoch - please use the CURRENT+reallyFORMER until + you can upload the latest version again. + . + If you are unsure whether you need to increase the epoch for a package, + please consult the debian-devel mailing list. + . + Lintian looks in this version's changelog entry for the phrase "epoch". diff -Nru lintian-2.93.0/tags/e/epoch-change-without-comment.tag lintian-2.89.0ubuntu1/tags/e/epoch-change-without-comment.tag --- lintian-2.93.0/tags/e/epoch-change-without-comment.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/e/epoch-change-without-comment.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,26 +0,0 @@ -Tag: epoch-change-without-comment -Severity: warning -Check: debian/changelog -Explanation: The previous version of this package had a different version epoch - (eg. 2:1.0-1) to the current version but there's no reference to this in - the changelog entry. - . - Epochs exist to cope with changes to the upstream version numbering - scheme. Whilst they are a powerful tool, increasing or adding an epoch - has many downsides including causing issues with versioned dependencies, - being misleading to users and being aesthetically unappealing. Whilst - they should be avoided, valid reasons to add or increment the epoch - include: - . - - Upstream changed their versioning scheme in a way that makes the - latest version lower than the previous one. - - You need to permanently revert to a lower upstream version. - . - Temporary revertions (eg. after an NMU) should use not modify or - introduce an epoch - please use the CURRENT+reallyFORMER until - you can upload the latest version again. - . - If you are unsure whether you need to increase the epoch for a package, - please consult the debian-devel mailing list. - . - Lintian looks in this version's changelog entry for the phrase "epoch". diff -Nru lintian-2.93.0/tags/e/essential-in-source-package.desc lintian-2.89.0ubuntu1/tags/e/essential-in-source-package.desc --- lintian-2.93.0/tags/e/essential-in-source-package.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/e/essential-in-source-package.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,5 @@ +Tag: essential-in-source-package +Severity: error +Check: fields/essential +Info: This field should only appear in binary packages. +Ref: policy 5.6.9 diff -Nru lintian-2.93.0/tags/e/essential-in-source-package.tag lintian-2.89.0ubuntu1/tags/e/essential-in-source-package.tag --- lintian-2.93.0/tags/e/essential-in-source-package.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/e/essential-in-source-package.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,5 +0,0 @@ -Tag: essential-in-source-package -Severity: error -Check: fields/essential -Explanation: This field should only appear in binary packages. -See-Also: policy 5.6.9 diff -Nru lintian-2.93.0/tags/e/essential-no-not-needed.desc lintian-2.89.0ubuntu1/tags/e/essential-no-not-needed.desc --- lintian-2.93.0/tags/e/essential-no-not-needed.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/e/essential-no-not-needed.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: essential-no-not-needed +Severity: warning +Check: fields/essential +Info: Having "Essential: no" is the same as not having the field at all, + so it just makes the Packages file longer with no benefit. +Ref: policy 5.6.9 diff -Nru lintian-2.93.0/tags/e/essential-no-not-needed.tag lintian-2.89.0ubuntu1/tags/e/essential-no-not-needed.tag --- lintian-2.93.0/tags/e/essential-no-not-needed.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/e/essential-no-not-needed.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: essential-no-not-needed -Severity: warning -Check: fields/essential -Explanation: Having "Essential: no" is the same as not having the field at all, - so it just makes the Packages file longer with no benefit. -See-Also: policy 5.6.9 diff -Nru lintian-2.93.0/tags/e/example-incorrect-path-for-interpreter.desc lintian-2.89.0ubuntu1/tags/e/example-incorrect-path-for-interpreter.desc --- lintian-2.93.0/tags/e/example-incorrect-path-for-interpreter.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/e/example-incorrect-path-for-interpreter.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,14 @@ +Tag: example-incorrect-path-for-interpreter +Severity: info +Check: scripts +Info: The interpreter used by this example script is installed at another + location on Debian systems. Normally the path should be updated to match + the Debian location. + . + Whilst the script may work, it is in violation of Debian Policy. This + may have been caused by usrmerge. + . + Note that, as a particular exception, Debian Policy § 10.4 states that + Perl scripts should use /usr/bin/perl directly and not + /usr/bin/env, etc. +Ref: policy 10.4, https://wiki.debian.org/UsrMerge diff -Nru lintian-2.93.0/tags/e/example-incorrect-path-for-interpreter.tag lintian-2.89.0ubuntu1/tags/e/example-incorrect-path-for-interpreter.tag --- lintian-2.93.0/tags/e/example-incorrect-path-for-interpreter.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/e/example-incorrect-path-for-interpreter.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,14 +0,0 @@ -Tag: example-incorrect-path-for-interpreter -Severity: info -Check: scripts -Explanation: The interpreter used by this example script is installed at another - location on Debian systems. Normally the path should be updated to match - the Debian location. - . - Whilst the script may work, it is in violation of Debian Policy. This - may have been caused by usrmerge. - . - Note that, as a particular exception, Debian Policy § 10.4 states that - Perl scripts should use /usr/bin/perl directly and not - /usr/bin/env, etc. -See-Also: policy 10.4, https://wiki.debian.org/UsrMerge diff -Nru lintian-2.93.0/tags/e/example-interpreter-in-usr-local.desc lintian-2.89.0ubuntu1/tags/e/example-interpreter-in-usr-local.desc --- lintian-2.93.0/tags/e/example-interpreter-in-usr-local.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/e/example-interpreter-in-usr-local.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: example-interpreter-in-usr-local +Severity: pedantic +Check: scripts +Info: This package contains an example script that looks for an + interpreter in a directory in /usr/local. Since Debian does not install + anything in /usr/local, the example script would probably need + modifications before a user could run it. diff -Nru lintian-2.93.0/tags/e/example-interpreter-in-usr-local.tag lintian-2.89.0ubuntu1/tags/e/example-interpreter-in-usr-local.tag --- lintian-2.93.0/tags/e/example-interpreter-in-usr-local.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/e/example-interpreter-in-usr-local.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: example-interpreter-in-usr-local -Severity: pedantic -Check: scripts -Explanation: This package contains an example script that looks for an - interpreter in a directory in /usr/local. Since Debian does not install - anything in /usr/local, the example script would probably need - modifications before a user could run it. diff -Nru lintian-2.93.0/tags/e/example-interpreter-not-absolute.desc lintian-2.89.0ubuntu1/tags/e/example-interpreter-not-absolute.desc --- lintian-2.93.0/tags/e/example-interpreter-not-absolute.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/e/example-interpreter-not-absolute.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: example-interpreter-not-absolute +Severity: info +Check: scripts +Info: This example script uses a relative path to locate its interpreter. + This path will be taken relative to the caller's current directory, not + the script's, so a user will probably not be able to run the example + without modification. This tag can also be caused by script headers like + #!@BASH@, which usually mean that the examples were copied out + of the source tree before proper Autoconf path substitution. diff -Nru lintian-2.93.0/tags/e/example-interpreter-not-absolute.tag lintian-2.89.0ubuntu1/tags/e/example-interpreter-not-absolute.tag --- lintian-2.93.0/tags/e/example-interpreter-not-absolute.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/e/example-interpreter-not-absolute.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: example-interpreter-not-absolute -Severity: info -Check: scripts -Explanation: This example script uses a relative path to locate its interpreter. - This path will be taken relative to the caller's current directory, not - the script's, so a user will probably not be able to run the example - without modification. This tag can also be caused by script headers like - #!@BASH@, which usually mean that the examples were copied out - of the source tree before proper Autoconf path substitution. diff -Nru lintian-2.93.0/tags/e/example-script-uses-bin-env.desc lintian-2.89.0ubuntu1/tags/e/example-script-uses-bin-env.desc --- lintian-2.93.0/tags/e/example-script-uses-bin-env.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/e/example-script-uses-bin-env.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: example-script-uses-bin-env +Severity: info +Check: scripts +Info: This example script uses /bin/env as its interpreter (used to find + the actual interpreter on the user's path). There is no /bin/env on + Debian systems; env is instead installed as /usr/bin/env. Usually, the + path to env in the script should be changed. diff -Nru lintian-2.93.0/tags/e/example-script-uses-bin-env.tag lintian-2.89.0ubuntu1/tags/e/example-script-uses-bin-env.tag --- lintian-2.93.0/tags/e/example-script-uses-bin-env.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/e/example-script-uses-bin-env.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: example-script-uses-bin-env -Severity: info -Check: scripts -Explanation: This example script uses /bin/env as its interpreter (used to find - the actual interpreter on the user's path). There is no /bin/env on - Debian systems; env is instead installed as /usr/bin/env. Usually, the - path to env in the script should be changed. diff -Nru lintian-2.93.0/tags/e/example-script-uses-deprecated-nodejs-location.desc lintian-2.89.0ubuntu1/tags/e/example-script-uses-deprecated-nodejs-location.desc --- lintian-2.93.0/tags/e/example-script-uses-deprecated-nodejs-location.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/e/example-script-uses-deprecated-nodejs-location.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,15 @@ +Tag: example-script-uses-deprecated-nodejs-location +Severity: warning +Certainty: possible +Check: scripts +Info: You used /usr/bin/nodejs or /usr/bin/env nodejs as an + interpreter for an example script. + . + The /usr/bin/node binary was previously provided by + ax25-node and packages were required to use /usr/bin/nodejs + instead. ax25-node has since been removed from the archive and the + nodejs package now ships the /usr/bin/node binary to match + the rest of the Node.js ecosystem. + . + Please update your package to use the node variant. +Ref: #614907, #862051 diff -Nru lintian-2.93.0/tags/e/example-script-uses-deprecated-nodejs-location.tag lintian-2.89.0ubuntu1/tags/e/example-script-uses-deprecated-nodejs-location.tag --- lintian-2.93.0/tags/e/example-script-uses-deprecated-nodejs-location.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/e/example-script-uses-deprecated-nodejs-location.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,14 +0,0 @@ -Tag: example-script-uses-deprecated-nodejs-location -Severity: warning -Check: scripts -Explanation: You used /usr/bin/nodejs or /usr/bin/env nodejs as an - interpreter for an example script. - . - The /usr/bin/node binary was previously provided by - ax25-node and packages were required to use /usr/bin/nodejs - instead. ax25-node has since been removed from the archive and the - nodejs package now ships the /usr/bin/node binary to match - the rest of the Node.js ecosystem. - . - Please update your package to use the node variant. -See-Also: Bug#614907, Bug#862051 diff -Nru lintian-2.93.0/tags/e/example-script-without-interpreter.desc lintian-2.89.0ubuntu1/tags/e/example-script-without-interpreter.desc --- lintian-2.93.0/tags/e/example-script-without-interpreter.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/e/example-script-without-interpreter.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,5 @@ +Tag: example-script-without-interpreter +Severity: info +Check: scripts +Info: This example file starts with the #! sequence that identifies + scripts, but it does not name an interpreter. diff -Nru lintian-2.93.0/tags/e/example-script-without-interpreter.tag lintian-2.89.0ubuntu1/tags/e/example-script-without-interpreter.tag --- lintian-2.93.0/tags/e/example-script-without-interpreter.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/e/example-script-without-interpreter.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,5 +0,0 @@ -Tag: example-script-without-interpreter -Severity: info -Check: scripts -Explanation: This example file starts with the #! sequence that identifies - scripts, but it does not name an interpreter. diff -Nru lintian-2.93.0/tags/e/example-shell-script-fails-syntax-check.desc lintian-2.89.0ubuntu1/tags/e/example-shell-script-fails-syntax-check.desc --- lintian-2.93.0/tags/e/example-shell-script-fails-syntax-check.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/e/example-shell-script-fails-syntax-check.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,13 @@ +Tag: example-shell-script-fails-syntax-check +Severity: pedantic +Certainty: possible +Check: scripts +Info: Running this shell script with the shell's -n option set fails, + which means that the script has syntax errors. The most common cause of + this problem is a script expecting /bin/sh to be bash checked on + a system using dash as /bin/sh. + . + Run e.g. sh -n yourscript to see the errors yourself. + . + Note this can have false-positives, for an example with bash scripts + using "extglob". diff -Nru lintian-2.93.0/tags/e/example-shell-script-fails-syntax-check.tag lintian-2.89.0ubuntu1/tags/e/example-shell-script-fails-syntax-check.tag --- lintian-2.93.0/tags/e/example-shell-script-fails-syntax-check.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/e/example-shell-script-fails-syntax-check.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,12 +0,0 @@ -Tag: example-shell-script-fails-syntax-check -Severity: pedantic -Check: scripts -Explanation: Running this shell script with the shell's -n option set fails, - which means that the script has syntax errors. The most common cause of - this problem is a script expecting /bin/sh to be bash checked on - a system using dash as /bin/sh. - . - Run e.g. sh -n yourscript to see the errors yourself. - . - Note this can have false-positives, for an example with bash scripts - using "extglob". diff -Nru lintian-2.93.0/tags/e/example-unusual-interpreter.desc lintian-2.89.0ubuntu1/tags/e/example-unusual-interpreter.desc --- lintian-2.93.0/tags/e/example-unusual-interpreter.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/e/example-unusual-interpreter.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: example-unusual-interpreter +Severity: pedantic +Certainty: possible +Check: scripts +Info: This package contains an example script for an interpreter that + is not shipped in the package and is not known to Lintian. It is + possible that there is a typo or the interpreter is not executable. diff -Nru lintian-2.93.0/tags/e/example-unusual-interpreter.tag lintian-2.89.0ubuntu1/tags/e/example-unusual-interpreter.tag --- lintian-2.93.0/tags/e/example-unusual-interpreter.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/e/example-unusual-interpreter.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: example-unusual-interpreter -Severity: pedantic -Check: scripts -Explanation: This package contains an example script for an interpreter that - is not shipped in the package and is not known to Lintian. It is - possible that there is a typo or the interpreter is not executable. diff -Nru lintian-2.93.0/tags/e/example-wrong-path-for-interpreter.desc lintian-2.89.0ubuntu1/tags/e/example-wrong-path-for-interpreter.desc --- lintian-2.93.0/tags/e/example-wrong-path-for-interpreter.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/e/example-wrong-path-for-interpreter.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: example-wrong-path-for-interpreter +Severity: info +Check: scripts +Info: The interpreter used by this example script is installed at another + location on Debian systems. Normally the path should be updated to match + the Debian location. + . + Note that, as a particular exception, Debian Policy § 10.4 states that + Perl scripts should use /usr/bin/perl directly and not + /usr/bin/env, etc. diff -Nru lintian-2.93.0/tags/e/example-wrong-path-for-interpreter.tag lintian-2.89.0ubuntu1/tags/e/example-wrong-path-for-interpreter.tag --- lintian-2.93.0/tags/e/example-wrong-path-for-interpreter.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/e/example-wrong-path-for-interpreter.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,10 +0,0 @@ -Tag: example-wrong-path-for-interpreter -Severity: info -Check: scripts -Explanation: The interpreter used by this example script is installed at another - location on Debian systems. Normally the path should be updated to match - the Debian location. - . - Note that, as a particular exception, Debian Policy § 10.4 states that - Perl scripts should use /usr/bin/perl directly and not - /usr/bin/env, etc. diff -Nru lintian-2.93.0/tags/e/excessive-debhelper-overrides.desc lintian-2.89.0ubuntu1/tags/e/excessive-debhelper-overrides.desc --- lintian-2.93.0/tags/e/excessive-debhelper-overrides.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/e/excessive-debhelper-overrides.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,25 @@ +Tag: excessive-debhelper-overrides +Severity: warning +Certainty: possible +Check: debhelper +Info: The debian/rules file appears to include a suspiciously + high number of override_dh_-style overrides. + . + It is likely that is this was intended to optimise package builds by + introducing "no-op" overrides that avoid specific debhelper commands. + . + However, whilst using overrides are not a problem per-se, such a list + is usually subject to constant revision, prevents future debhelper + versions fixing archive-wide problems, adds unnecessary + noise/distraction for anyone reviewing the package, and increases the + package's "bus factor". It is, in addition, aesthetically displeasing. + . + Furthermore, this is typically a premature optimisation. debhelper already + includes optimizations to avoid running commands when unnecessary. If you find + a debhelper command taking unnecessarily long when it has no work to do, + please work with the debhelper developers to help debhelper skip that command + in more circumstances, optimizing not only your package build but everyone + else's as well. + . + Please remove the unnecessary overrides. +Ref: debhelper(7), dh(1) diff -Nru lintian-2.93.0/tags/e/excessive-debhelper-overrides.tag lintian-2.89.0ubuntu1/tags/e/excessive-debhelper-overrides.tag --- lintian-2.93.0/tags/e/excessive-debhelper-overrides.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/e/excessive-debhelper-overrides.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,24 +0,0 @@ -Tag: excessive-debhelper-overrides -Severity: warning -Check: debhelper -Explanation: The debian/rules file appears to include a suspiciously - high number of override_dh_-style overrides. - . - It is likely that is this was intended to optimise package builds by - introducing "no-op" overrides that avoid specific debhelper commands. - . - However, whilst using overrides are not a problem per-se, such a list - is usually subject to constant revision, prevents future debhelper - versions fixing archive-wide problems, adds unnecessary - noise/distraction for anyone reviewing the package, and increases the - package's "bus factor". It is, in addition, aesthetically displeasing. - . - Furthermore, this is typically a premature optimisation. debhelper already - includes optimizations to avoid running commands when unnecessary. If you find - a debhelper command taking unnecessarily long when it has no work to do, - please work with the debhelper developers to help debhelper skip that command - in more circumstances, optimizing not only your package build but everyone - else's as well. - . - Please remove the unnecessary overrides. -See-Also: debhelper(7), dh(1) diff -Nru lintian-2.93.0/tags/e/excessive-priority-for-library-package.desc lintian-2.89.0ubuntu1/tags/e/excessive-priority-for-library-package.desc --- lintian-2.93.0/tags/e/excessive-priority-for-library-package.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/e/excessive-priority-for-library-package.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,13 @@ +Tag: excessive-priority-for-library-package +Severity: warning +Certainty: possible +Check: fields/priority +Info: The given package appears to be a library package, but it has "Priority" + of "required", "important", or "standard". + . + In general, a library package should only get pulled in on a system because + some other package depends on it; no library package needs installation on a + system where nothing uses it. + . + Please update debian/control and downgrade the severity to, for + example, Priority: optional. diff -Nru lintian-2.93.0/tags/e/excessive-priority-for-library-package.tag lintian-2.89.0ubuntu1/tags/e/excessive-priority-for-library-package.tag --- lintian-2.93.0/tags/e/excessive-priority-for-library-package.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/e/excessive-priority-for-library-package.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,12 +0,0 @@ -Tag: excessive-priority-for-library-package -Severity: warning -Check: fields/priority -Explanation: The given package appears to be a library package, but it has "Priority" - of "required", "important", or "standard". - . - In general, a library package should only get pulled in on a system because - some other package depends on it; no library package needs installation on a - system where nothing uses it. - . - Please update debian/control and downgrade the severity to, for - example, Priority: optional. diff -Nru lintian-2.93.0/tags/e/exclusive-runtime-tests-field.desc lintian-2.89.0ubuntu1/tags/e/exclusive-runtime-tests-field.desc --- lintian-2.93.0/tags/e/exclusive-runtime-tests-field.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/e/exclusive-runtime-tests-field.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: exclusive-runtime-tests-field +Severity: warning +Check: testsuite +Info: Exclusive field are specified in some paragraph of the + debian/tests/control file. +Ref: https://salsa.debian.org/ci-team/autopkgtest/tree/master/doc/README.package-tests.rst diff -Nru lintian-2.93.0/tags/e/exclusive-runtime-tests-field.tag lintian-2.89.0ubuntu1/tags/e/exclusive-runtime-tests-field.tag --- lintian-2.93.0/tags/e/exclusive-runtime-tests-field.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/e/exclusive-runtime-tests-field.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: exclusive-runtime-tests-field -Severity: warning -Check: testsuite -Explanation: Exclusive field are specified in some paragraph of the - debian/tests/control file. -See-Also: https://salsa.debian.org/ci-team/autopkgtest/tree/master/doc/README.package-tests.rst diff -Nru lintian-2.93.0/tags/e/executable-debhelper-file-without-being-executable.desc lintian-2.89.0ubuntu1/tags/e/executable-debhelper-file-without-being-executable.desc --- lintian-2.93.0/tags/e/executable-debhelper-file-without-being-executable.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/e/executable-debhelper-file-without-being-executable.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: executable-debhelper-file-without-being-executable +Severity: error +Certainty: possible +Check: debhelper +Info: The packaging file is marked executable, but it does not appear to be + executable (e.g. it has no #! line). + . + If debhelper file is not supposed to be executable, please remove the + executable bit from it. diff -Nru lintian-2.93.0/tags/e/executable-debhelper-file-without-being-executable.tag lintian-2.89.0ubuntu1/tags/e/executable-debhelper-file-without-being-executable.tag --- lintian-2.93.0/tags/e/executable-debhelper-file-without-being-executable.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/e/executable-debhelper-file-without-being-executable.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: executable-debhelper-file-without-being-executable -Severity: error -Check: debhelper -Explanation: The packaging file is marked executable, but it does not appear to be - executable (e.g. it has no #! line). - . - If debhelper file is not supposed to be executable, please remove the - executable bit from it. diff -Nru lintian-2.93.0/tags/e/executable-desktop-file.desc lintian-2.89.0ubuntu1/tags/e/executable-desktop-file.desc --- lintian-2.93.0/tags/e/executable-desktop-file.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/e/executable-desktop-file.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,5 @@ +Tag: executable-desktop-file +Severity: error +Check: menu-format +Info: The desktop entry file is marked executable. Desktop entries are + regular files and should be installed mode 0644. diff -Nru lintian-2.93.0/tags/e/executable-desktop-file.tag lintian-2.89.0ubuntu1/tags/e/executable-desktop-file.tag --- lintian-2.93.0/tags/e/executable-desktop-file.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/e/executable-desktop-file.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,5 +0,0 @@ -Tag: executable-desktop-file -Severity: error -Check: menu-format -Explanation: The desktop entry file is marked executable. Desktop entries are - regular files and should be installed mode 0644. diff -Nru lintian-2.93.0/tags/e/executable-in-usr-lib.desc lintian-2.89.0ubuntu1/tags/e/executable-in-usr-lib.desc --- lintian-2.93.0/tags/e/executable-in-usr-lib.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/e/executable-in-usr-lib.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,14 @@ +Tag: executable-in-usr-lib +Severity: pedantic +Check: files/permissions/usr-lib +Info: The package ships an executable file in /usr/lib. + . + Please move the file to /usr/libexec. + . + Debian adopted the Filesystem Hierarchy Specification (FHS) + version 3.0 starting with our policy revision 4.1.5. The + FHS 3.0 describes /usr/libexec. Please use that + location for executables. +Ref: policy 9.1.1, + https://refspecs.linuxfoundation.org/FHS_3.0/fhs/ch04s07.html, + Bug#954149 diff -Nru lintian-2.93.0/tags/e/executable-in-usr-lib.tag lintian-2.89.0ubuntu1/tags/e/executable-in-usr-lib.tag --- lintian-2.93.0/tags/e/executable-in-usr-lib.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/e/executable-in-usr-lib.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,14 +0,0 @@ -Tag: executable-in-usr-lib -Severity: pedantic -Check: files/permissions/usr-lib -Explanation: The package ships an executable file in /usr/lib. - . - Please move the file to /usr/libexec. - . - Debian adopted the Filesystem Hierarchy Specification (FHS) - version 3.0 starting with our policy revision 4.1.5. The - FHS 3.0 describes /usr/libexec. Please use that - location for executables. -See-Also: policy 9.1.1, - https://refspecs.linuxfoundation.org/FHS_3.0/fhs/ch04s07.html, - Bug#954149 diff -Nru lintian-2.93.0/tags/e/executable-in-usr-share-docbase.desc lintian-2.89.0ubuntu1/tags/e/executable-in-usr-share-docbase.desc --- lintian-2.93.0/tags/e/executable-in-usr-share-docbase.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/e/executable-in-usr-share-docbase.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,4 @@ +Tag: executable-in-usr-share-docbase +Severity: error +Check: menus +Info: Files in /usr/share/doc-base may not be marked as executables. diff -Nru lintian-2.93.0/tags/e/executable-in-usr-share-docbase.tag lintian-2.89.0ubuntu1/tags/e/executable-in-usr-share-docbase.tag --- lintian-2.93.0/tags/e/executable-in-usr-share-docbase.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/e/executable-in-usr-share-docbase.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,4 +0,0 @@ -Tag: executable-in-usr-share-docbase -Severity: error -Check: menus -Explanation: Files in /usr/share/doc-base may not be marked as executables. diff -Nru lintian-2.93.0/tags/e/executable-in-usr-share-doc.desc lintian-2.89.0ubuntu1/tags/e/executable-in-usr-share-doc.desc --- lintian-2.93.0/tags/e/executable-in-usr-share-doc.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/e/executable-in-usr-share-doc.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: executable-in-usr-share-doc +Severity: error +Check: documentation +Info: Usually, documentation files in /usr/share/doc should have mode + 0644. If the executable is an example, it should go in + /usr/share/doc/pkg/examples. diff -Nru lintian-2.93.0/tags/e/executable-in-usr-share-doc.tag lintian-2.89.0ubuntu1/tags/e/executable-in-usr-share-doc.tag --- lintian-2.93.0/tags/e/executable-in-usr-share-doc.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/e/executable-in-usr-share-doc.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: executable-in-usr-share-doc -Severity: error -Check: documentation -Explanation: Usually, documentation files in /usr/share/doc should have mode - 0644. If the executable is an example, it should go in - /usr/share/doc/*pkg*/examples. diff -Nru lintian-2.93.0/tags/e/executable-is-not-world-readable.desc lintian-2.89.0ubuntu1/tags/e/executable-is-not-world-readable.desc --- lintian-2.93.0/tags/e/executable-is-not-world-readable.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/e/executable-is-not-world-readable.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: executable-is-not-world-readable +Severity: warning +Check: files/permissions +Info: All executables should be readable by any user. Since anyone can + download the Debian package and obtain a copy of the executable, no + security is gained by making the executable unreadable even for setuid + binaries. If only members of a certain group may execute this file, + remove execute permission for world, but leave read permission. +Ref: policy 10.9 diff -Nru lintian-2.93.0/tags/e/executable-is-not-world-readable.tag lintian-2.89.0ubuntu1/tags/e/executable-is-not-world-readable.tag --- lintian-2.93.0/tags/e/executable-is-not-world-readable.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/e/executable-is-not-world-readable.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: executable-is-not-world-readable -Severity: warning -Check: files/permissions -Explanation: All executables should be readable by any user. Since anyone can - download the Debian package and obtain a copy of the executable, no - security is gained by making the executable unreadable even for setuid - binaries. If only members of a certain group may execute this file, - remove execute permission for world, but leave read permission. -See-Also: policy 10.9 diff -Nru lintian-2.93.0/tags/e/executable-jar-without-main-class.desc lintian-2.89.0ubuntu1/tags/e/executable-jar-without-main-class.desc --- lintian-2.93.0/tags/e/executable-jar-without-main-class.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/e/executable-jar-without-main-class.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,5 @@ +Tag: executable-jar-without-main-class +Severity: error +Check: languages/java +Ref: java-policy 2.2 +Info: An executable JAR must have a Main-Class set in its manifest. diff -Nru lintian-2.93.0/tags/e/executable-jar-without-main-class.tag lintian-2.89.0ubuntu1/tags/e/executable-jar-without-main-class.tag --- lintian-2.93.0/tags/e/executable-jar-without-main-class.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/e/executable-jar-without-main-class.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,5 +0,0 @@ -Tag: executable-jar-without-main-class -Severity: error -Check: languages/java -See-Also: java-policy 2.2 -Explanation: An executable JAR must have a Main-Class set in its manifest. diff -Nru lintian-2.93.0/tags/e/executable-manual-page.desc lintian-2.89.0ubuntu1/tags/e/executable-manual-page.desc --- lintian-2.93.0/tags/e/executable-manual-page.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/e/executable-manual-page.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,5 @@ +Tag: executable-manual-page +Severity: error +Check: documentation/manual +Renamed-From: executable-manpage +Info: Manual pages are not meant to be executed. diff -Nru lintian-2.93.0/tags/e/executable-manual-page.tag lintian-2.89.0ubuntu1/tags/e/executable-manual-page.tag --- lintian-2.93.0/tags/e/executable-manual-page.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/e/executable-manual-page.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,5 +0,0 @@ -Tag: executable-manual-page -Severity: error -Check: documentation/manual -Renamed-From: executable-manpage -Explanation: Manual pages are not meant to be executed. diff -Nru lintian-2.93.0/tags/e/executable-menu-file.desc lintian-2.89.0ubuntu1/tags/e/executable-menu-file.desc --- lintian-2.93.0/tags/e/executable-menu-file.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/e/executable-menu-file.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,5 @@ +Tag: executable-menu-file +Severity: warning +Check: menus +Info: Menu files should normally not be marked as executables. You only + need to do this if your package has to generate menu entries dynamically. diff -Nru lintian-2.93.0/tags/e/executable-menu-file.tag lintian-2.89.0ubuntu1/tags/e/executable-menu-file.tag --- lintian-2.93.0/tags/e/executable-menu-file.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/e/executable-menu-file.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,5 +0,0 @@ -Tag: executable-menu-file -Severity: warning -Check: menus -Explanation: Menu files should normally not be marked as executables. You only - need to do this if your package has to generate menu entries dynamically. diff -Nru lintian-2.93.0/tags/e/executable-not-elf-or-script.desc lintian-2.89.0ubuntu1/tags/e/executable-not-elf-or-script.desc --- lintian-2.93.0/tags/e/executable-not-elf-or-script.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/e/executable-not-elf-or-script.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,12 @@ +Tag: executable-not-elf-or-script +Severity: warning +Check: scripts +Info: This executable file is not an ELF format binary, and does not start + with the #! sequence that marks interpreted scripts. It might be a sh + script that fails to name /bin/sh as its shell, or it may be incorrectly + marked as executable. Sometimes upstream files developed on Windows are + marked unnecessarily as executable on other systems. + . + If you are using debhelper to build your package, running dh_fixperms will + often correct this problem for you. +Ref: policy 10.4 diff -Nru lintian-2.93.0/tags/e/executable-not-elf-or-script.tag lintian-2.89.0ubuntu1/tags/e/executable-not-elf-or-script.tag --- lintian-2.93.0/tags/e/executable-not-elf-or-script.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/e/executable-not-elf-or-script.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,12 +0,0 @@ -Tag: executable-not-elf-or-script -Severity: warning -Check: scripts -Explanation: This executable file is not an ELF format binary, and does not start - with the #! sequence that marks interpreted scripts. It might be a sh - script that fails to name /bin/sh as its shell, or it may be incorrectly - marked as executable. Sometimes upstream files developed on Windows are - marked unnecessarily as executable on other systems. - . - If you are using debhelper to build your package, running dh_fixperms will - often correct this problem for you. -See-Also: policy 10.4 diff -Nru lintian-2.93.0/tags/e/executable-stack-in-shared-library.desc lintian-2.89.0ubuntu1/tags/e/executable-stack-in-shared-library.desc --- lintian-2.93.0/tags/e/executable-stack-in-shared-library.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/e/executable-stack-in-shared-library.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,16 @@ +Tag: executable-stack-in-shared-library +Severity: warning +Certainty: possible +Check: shared-libs +Renamed-From: shlib-with-executable-stack +Info: The listed shared library declares the stack as executable. + . + Executable stack is usually an error as it is only needed if the code + contains GCC trampolines or similar constructs which uses code on the + stack. One possible source for false positives are object files built + from assembler files which don't define a proper .note.GNU-stack + section. + . + To see the permissions on the stack, run readelf -l on the + shared library and look for the program header of type GNU_STACK. In the + flag column, there should not be an E flag set. diff -Nru lintian-2.93.0/tags/e/executable-stack-in-shared-library.tag lintian-2.89.0ubuntu1/tags/e/executable-stack-in-shared-library.tag --- lintian-2.93.0/tags/e/executable-stack-in-shared-library.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/e/executable-stack-in-shared-library.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,15 +0,0 @@ -Tag: executable-stack-in-shared-library -Severity: warning -Check: shared-libs -Renamed-From: shlib-with-executable-stack -Explanation: The listed shared library declares the stack as executable. - . - Executable stack is usually an error as it is only needed if the code - contains GCC trampolines or similar constructs which uses code on the - stack. One possible source for false positives are object files built - from assembler files which don't define a proper .note.GNU-stack - section. - . - To see the permissions on the stack, run readelf -l on the - shared library and look for the program header of type GNU_STACK. In the - flag column, there should not be an E flag set. diff -Nru lintian-2.93.0/tags/e/exit-in-shared-library.desc lintian-2.89.0ubuntu1/tags/e/exit-in-shared-library.desc --- lintian-2.93.0/tags/e/exit-in-shared-library.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/e/exit-in-shared-library.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,15 @@ +Tag: exit-in-shared-library +Severity: info +Certainty: possible +Check: shared-libs +Experimental: yes +Renamed-From: shlib-calls-exit +Info: The listed shared library calls the C library exit() or _exit() + functions. + . + In the case of an error, the library should instead return an appropriate + error code to the calling program which can then determine how to handle + the error, including performing any required clean-up. + . + In most cases, removing the call should be discussed with upstream, + particularly as it may produce an ABI change. diff -Nru lintian-2.93.0/tags/e/exit-in-shared-library.tag lintian-2.89.0ubuntu1/tags/e/exit-in-shared-library.tag --- lintian-2.93.0/tags/e/exit-in-shared-library.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/e/exit-in-shared-library.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,14 +0,0 @@ -Tag: exit-in-shared-library -Severity: info -Check: shared-libs -Experimental: yes -Renamed-From: shlib-calls-exit -Explanation: The listed shared library calls the C library exit() or _exit() - functions. - . - In the case of an error, the library should instead return an appropriate - error code to the calling program which can then determine how to handle - the error, including performing any required clean-up. - . - In most cases, removing the call should be discussed with upstream, - particularly as it may produce an ABI change. diff -Nru lintian-2.93.0/tags/e/experimental-to-unstable-without-comment.desc lintian-2.89.0ubuntu1/tags/e/experimental-to-unstable-without-comment.desc --- lintian-2.93.0/tags/e/experimental-to-unstable-without-comment.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/e/experimental-to-unstable-without-comment.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,14 @@ +Tag: experimental-to-unstable-without-comment +Severity: pedantic +Certainty: possible +Check: debian/changelog +Info: The previous version of this package had a distribution of + "experimental", this version has a distribution of "unstable", and there's + apparently no comment about the change of distributions. + . + Lintian looks in this version's changelog entry for the phrase "to + unstable" or "to sid", with or without quotation marks around the + distribution name. + . + This may indicate a mistake in setting the distribution and an accidental + upload to unstable of a package intended for experimental. diff -Nru lintian-2.93.0/tags/e/experimental-to-unstable-without-comment.tag lintian-2.89.0ubuntu1/tags/e/experimental-to-unstable-without-comment.tag --- lintian-2.93.0/tags/e/experimental-to-unstable-without-comment.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/e/experimental-to-unstable-without-comment.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,13 +0,0 @@ -Tag: experimental-to-unstable-without-comment -Severity: pedantic -Check: debian/changelog -Explanation: The previous version of this package had a distribution of - "experimental", this version has a distribution of "unstable", and there's - apparently no comment about the change of distributions. - . - Lintian looks in this version's changelog entry for the phrase "to - unstable" or "to sid", with or without quotation marks around the - distribution name. - . - This may indicate a mistake in setting the distribution and an accidental - upload to unstable of a package intended for experimental. diff -Nru lintian-2.93.0/tags/e/explicit-default-in-package-type.desc lintian-2.89.0ubuntu1/tags/e/explicit-default-in-package-type.desc --- lintian-2.93.0/tags/e/explicit-default-in-package-type.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/e/explicit-default-in-package-type.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: explicit-default-in-package-type +Severity: warning +Check: fields/package-type +Info: Having Package-Type: deb is the same as not having + the field at all, so it makes the Packages file longer with no + benefit. Policy also discourages it. +Ref: policy 5.6.28 diff -Nru lintian-2.93.0/tags/e/explicit-default-in-package-type.tag lintian-2.89.0ubuntu1/tags/e/explicit-default-in-package-type.tag --- lintian-2.93.0/tags/e/explicit-default-in-package-type.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/e/explicit-default-in-package-type.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: explicit-default-in-package-type -Severity: warning -Check: fields/package-type -Explanation: Having Package-Type: deb is the same as not having - the field at all, so it makes the Packages file longer with no - benefit. Policy also discourages it. -See-Also: policy 5.6.28 diff -Nru lintian-2.93.0/tags/e/explicitly-armored-upstream-signature.desc lintian-2.89.0ubuntu1/tags/e/explicitly-armored-upstream-signature.desc --- lintian-2.93.0/tags/e/explicitly-armored-upstream-signature.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/e/explicitly-armored-upstream-signature.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: explicitly-armored-upstream-signature +Severity: warning +Check: upstream-signature +Info: The packaging includes a detached upstream signature file that was armored + explicitly using gpg --enarmor. That is likely an error. + . + Please generate the signature with gpg --armor --detach-sig instead. diff -Nru lintian-2.93.0/tags/e/explicitly-armored-upstream-signature.tag lintian-2.89.0ubuntu1/tags/e/explicitly-armored-upstream-signature.tag --- lintian-2.93.0/tags/e/explicitly-armored-upstream-signature.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/e/explicitly-armored-upstream-signature.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: explicitly-armored-upstream-signature -Severity: warning -Check: upstream-signature -Explanation: The packaging includes a detached upstream signature file that was armored - explicitly using gpg --enarmor. That is likely an error. - . - Please generate the signature with gpg --armor --detach-sig instead. diff -Nru lintian-2.93.0/tags/e/extended-description-contains-empty-paragraph.desc lintian-2.89.0ubuntu1/tags/e/extended-description-contains-empty-paragraph.desc --- lintian-2.93.0/tags/e/extended-description-contains-empty-paragraph.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/e/extended-description-contains-empty-paragraph.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,5 @@ +Tag: extended-description-contains-empty-paragraph +Severity: warning +Check: fields/description +Info: The extended description (the lines after the first line of the + "Description:" field) contains an empty paragraph. diff -Nru lintian-2.93.0/tags/e/extended-description-contains-empty-paragraph.tag lintian-2.89.0ubuntu1/tags/e/extended-description-contains-empty-paragraph.tag --- lintian-2.93.0/tags/e/extended-description-contains-empty-paragraph.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/e/extended-description-contains-empty-paragraph.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,5 +0,0 @@ -Tag: extended-description-contains-empty-paragraph -Severity: warning -Check: fields/description -Explanation: The extended description (the lines after the first line of the - "Description:" field) contains an empty paragraph. diff -Nru lintian-2.93.0/tags/e/extended-description-is-empty.desc lintian-2.89.0ubuntu1/tags/e/extended-description-is-empty.desc --- lintian-2.93.0/tags/e/extended-description-is-empty.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/e/extended-description-is-empty.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: extended-description-is-empty +Severity: error +Check: fields/description +Info: The extended description (the lines after the first line of the + "Description:" field) is empty. +Ref: policy 3.4 diff -Nru lintian-2.93.0/tags/e/extended-description-is-empty.tag lintian-2.89.0ubuntu1/tags/e/extended-description-is-empty.tag --- lintian-2.93.0/tags/e/extended-description-is-empty.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/e/extended-description-is-empty.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: extended-description-is-empty -Severity: error -Check: fields/description -Explanation: The extended description (the lines after the first line of the - "Description:" field) is empty. -See-Also: policy 3.4 diff -Nru lintian-2.93.0/tags/e/extended-description-is-probably-too-short.desc lintian-2.89.0ubuntu1/tags/e/extended-description-is-probably-too-short.desc --- lintian-2.93.0/tags/e/extended-description-is-probably-too-short.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/e/extended-description-is-probably-too-short.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,11 @@ +Tag: extended-description-is-probably-too-short +Severity: info +Certainty: possible +Check: fields/description +Ref: devref 6.2.1, devref 6.2.3 +Info: The extended description (the lines after the first line of the + "Description:" field) is only one or two lines long. The extended + description should provide a user with enough information to decide + whether they want to install this package, what it contains, and how it + compares to similar packages. One or two lines is normally not enough to + do this. diff -Nru lintian-2.93.0/tags/e/extended-description-is-probably-too-short.tag lintian-2.89.0ubuntu1/tags/e/extended-description-is-probably-too-short.tag --- lintian-2.93.0/tags/e/extended-description-is-probably-too-short.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/e/extended-description-is-probably-too-short.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,10 +0,0 @@ -Tag: extended-description-is-probably-too-short -Severity: info -Check: fields/description -See-Also: devref 6.2.1, devref 6.2.3 -Explanation: The extended description (the lines after the first line of the - "Description:" field) is only one or two lines long. The extended - description should provide a user with enough information to decide - whether they want to install this package, what it contains, and how it - compares to similar packages. One or two lines is normally not enough to - do this. diff -Nru lintian-2.93.0/tags/e/extended-description-line-too-long.desc lintian-2.89.0ubuntu1/tags/e/extended-description-line-too-long.desc --- lintian-2.93.0/tags/e/extended-description-line-too-long.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/e/extended-description-line-too-long.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: extended-description-line-too-long +Severity: warning +Check: fields/description +Info: One or more lines in the extended part of the "Description:" field + have been found to contain more than 80 characters. For the benefit of + users of 80x25 terminals, it is recommended that the lines do not exceed + 80 characters. +Ref: policy 3.4.1 diff -Nru lintian-2.93.0/tags/e/extended-description-line-too-long.tag lintian-2.89.0ubuntu1/tags/e/extended-description-line-too-long.tag --- lintian-2.93.0/tags/e/extended-description-line-too-long.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/e/extended-description-line-too-long.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: extended-description-line-too-long -Severity: warning -Check: fields/description -Explanation: One or more lines in the extended part of the "Description:" field - have been found to contain more than 80 characters. For the benefit of - users of 80x25 terminals, it is recommended that the lines do not exceed - 80 characters. -See-Also: policy 3.4.1 diff -Nru lintian-2.93.0/tags/e/extra-license-file.desc lintian-2.89.0ubuntu1/tags/e/extra-license-file.desc --- lintian-2.93.0/tags/e/extra-license-file.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/e/extra-license-file.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: extra-license-file +Severity: info +Certainty: possible +Check: files/licenses +Ref: policy 12.5 +Info: All license information should be collected in the + debian/copyright file. This usually makes it unnecessary + for the package to install this information in other places as well. diff -Nru lintian-2.93.0/tags/e/extra-license-file.tag lintian-2.89.0ubuntu1/tags/e/extra-license-file.tag --- lintian-2.93.0/tags/e/extra-license-file.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/e/extra-license-file.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: extra-license-file -Severity: info -Check: files/licenses -See-Also: policy 12.5 -Explanation: All license information should be collected in the - debian/copyright file. This usually makes it unnecessary - for the package to install this information in other places as well. diff -Nru lintian-2.93.0/tags/e/extra-whitespace-around-name-in-changelog-trailer.desc lintian-2.89.0ubuntu1/tags/e/extra-whitespace-around-name-in-changelog-trailer.desc --- lintian-2.93.0/tags/e/extra-whitespace-around-name-in-changelog-trailer.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/e/extra-whitespace-around-name-in-changelog-trailer.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: extra-whitespace-around-name-in-changelog-trailer +Severity: warning +Check: nmu +Info: There is too much whitespace around the name in debian/changelog. + . + The format is: + -- NAME <EMAIL> DATE + . + Note that there must be exactly 1 space after the "--" and exactly + 2 spaces before the "DATE". diff -Nru lintian-2.93.0/tags/e/extra-whitespace-around-name-in-changelog-trailer.tag lintian-2.89.0ubuntu1/tags/e/extra-whitespace-around-name-in-changelog-trailer.tag --- lintian-2.93.0/tags/e/extra-whitespace-around-name-in-changelog-trailer.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/e/extra-whitespace-around-name-in-changelog-trailer.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,10 +0,0 @@ -Tag: extra-whitespace-around-name-in-changelog-trailer -Severity: warning -Check: nmu -Explanation: There is too much whitespace around the name in debian/changelog. - . - The format is: - -- NAME <EMAIL> DATE - . - Note that there must be exactly 1 space after the "--" and exactly - 2 spaces before the "DATE". diff -Nru lintian-2.93.0/tags/f/faulty-debian-qa-group-address.desc lintian-2.89.0ubuntu1/tags/f/faulty-debian-qa-group-address.desc --- lintian-2.93.0/tags/f/faulty-debian-qa-group-address.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/f/faulty-debian-qa-group-address.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: faulty-debian-qa-group-address +Severity: error +Check: fields/mail-address +Renamed-From: wrong-debian-qa-address-set-as-maintainer +Info: Orphaned packages should no longer have the address + <debian-qa@lists.debian.org> in the Maintainer field. + . + The correct Maintainer field for orphaned packages is + Debian QA Group <packages@qa.debian.org>. +Ref: devref 5.9.4 diff -Nru lintian-2.93.0/tags/f/faulty-debian-qa-group-address.tag lintian-2.89.0ubuntu1/tags/f/faulty-debian-qa-group-address.tag --- lintian-2.93.0/tags/f/faulty-debian-qa-group-address.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/f/faulty-debian-qa-group-address.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,10 +0,0 @@ -Tag: faulty-debian-qa-group-address -Severity: error -Check: fields/mail-address -Renamed-From: wrong-debian-qa-address-set-as-maintainer -Explanation: Orphaned packages should no longer have the address - <debian-qa@lists.debian.org> in the Maintainer field. - . - The correct Maintainer field for orphaned packages is - Debian QA Group <packages@qa.debian.org>. -See-Also: devref 5.9.4 diff -Nru lintian-2.93.0/tags/f/faulty-debian-qa-group-phrase.desc lintian-2.89.0ubuntu1/tags/f/faulty-debian-qa-group-phrase.desc --- lintian-2.93.0/tags/f/faulty-debian-qa-group-phrase.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/f/faulty-debian-qa-group-phrase.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: faulty-debian-qa-group-phrase +Severity: error +Check: fields/mail-address +Info: Orphaned packages should have "Debian QA Group + <packages@qa.debian.org>" in the maintainer field. +Ref: devref 5.9.4 diff -Nru lintian-2.93.0/tags/f/faulty-debian-qa-group-phrase.tag lintian-2.89.0ubuntu1/tags/f/faulty-debian-qa-group-phrase.tag --- lintian-2.93.0/tags/f/faulty-debian-qa-group-phrase.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/f/faulty-debian-qa-group-phrase.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: faulty-debian-qa-group-phrase -Severity: error -Check: fields/mail-address -Explanation: Orphaned packages should have "Debian QA Group - <packages@qa.debian.org>" in the maintainer field. -See-Also: devref 5.9.4 diff -Nru lintian-2.93.0/tags/f/field-too-long.desc lintian-2.89.0ubuntu1/tags/f/field-too-long.desc --- lintian-2.93.0/tags/f/field-too-long.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/f/field-too-long.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,11 @@ +Tag: field-too-long +Severity: error +Check: fields/length +Info: The length of the specified field is too long. + . + Overly-long fields not only can break some tools tools (eg. + reprepro(1)) they can waste space as they are shipped to all + users. + . + Please reduce the number of characters. +Ref: #942493 diff -Nru lintian-2.93.0/tags/f/field-too-long.tag lintian-2.89.0ubuntu1/tags/f/field-too-long.tag --- lintian-2.93.0/tags/f/field-too-long.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/f/field-too-long.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,11 +0,0 @@ -Tag: field-too-long -Severity: error -Check: fields/length -Explanation: The length of the specified field is too long. - . - Overly-long fields not only can break some tools tools (eg. - reprepro(1)) they can waste space as they are shipped to all - users. - . - Please reduce the number of characters. -See-Also: Bug#942493 diff -Nru lintian-2.93.0/tags/f/file-contains-fixme-placeholder.desc lintian-2.89.0ubuntu1/tags/f/file-contains-fixme-placeholder.desc --- lintian-2.93.0/tags/f/file-contains-fixme-placeholder.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/f/file-contains-fixme-placeholder.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: file-contains-fixme-placeholder +Severity: info +Check: cruft +Info: This file appears to be incomplete or insufficiently modified as it + contains a "FIXME" placeholder text. These can often be generated by + package generation tools such as dh_make or npm2deb. + . + Please double-check the file and replace the placeholder with the required + command or information. diff -Nru lintian-2.93.0/tags/f/file-contains-fixme-placeholder.tag lintian-2.89.0ubuntu1/tags/f/file-contains-fixme-placeholder.tag --- lintian-2.93.0/tags/f/file-contains-fixme-placeholder.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/f/file-contains-fixme-placeholder.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: file-contains-fixme-placeholder -Severity: info -Check: cruft -Explanation: This file appears to be incomplete or insufficiently modified as it - contains a "FIXME" placeholder text. These can often be generated by - package generation tools such as dh_make or npm2deb. - . - Please double-check the file and replace the placeholder with the required - command or information. diff -Nru lintian-2.93.0/tags/f/file-directly-in-usr-share.desc lintian-2.89.0ubuntu1/tags/f/file-directly-in-usr-share.desc --- lintian-2.93.0/tags/f/file-directly-in-usr-share.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/f/file-directly-in-usr-share.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: file-directly-in-usr-share +Severity: error +Check: files/hierarchy/standard +Info: Packages should not install files directly in /usr/share, + i.e., without a subdirectory. + . + You should either create a subdirectory /usr/share/... for your + package or place the file in /usr/share/misc. diff -Nru lintian-2.93.0/tags/f/file-directly-in-usr-share-doc.desc lintian-2.89.0ubuntu1/tags/f/file-directly-in-usr-share-doc.desc --- lintian-2.93.0/tags/f/file-directly-in-usr-share-doc.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/f/file-directly-in-usr-share-doc.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: file-directly-in-usr-share-doc +Severity: error +Check: documentation +Info: Documentation files have to be installed in + /usr/share/doc/pkg. +Ref: policy 12.3 diff -Nru lintian-2.93.0/tags/f/file-directly-in-usr-share-doc.tag lintian-2.89.0ubuntu1/tags/f/file-directly-in-usr-share-doc.tag --- lintian-2.93.0/tags/f/file-directly-in-usr-share-doc.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/f/file-directly-in-usr-share-doc.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: file-directly-in-usr-share-doc -Severity: error -Check: documentation -Explanation: Documentation files have to be installed in - /usr/share/doc/*pkg*. -See-Also: policy 12.3 diff -Nru lintian-2.93.0/tags/f/file-directly-in-usr-share.tag lintian-2.89.0ubuntu1/tags/f/file-directly-in-usr-share.tag --- lintian-2.93.0/tags/f/file-directly-in-usr-share.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/f/file-directly-in-usr-share.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: file-directly-in-usr-share -Severity: error -Check: files/hierarchy/standard -Explanation: Packages should not install files directly in /usr/share, - i.e., without a subdirectory. - . - You should either create a subdirectory /usr/share/... for your - package or place the file in /usr/share/misc. diff -Nru lintian-2.93.0/tags/f/file-in-discouraged-x11-font-directory.desc lintian-2.89.0ubuntu1/tags/f/file-in-discouraged-x11-font-directory.desc --- lintian-2.93.0/tags/f/file-in-discouraged-x11-font-directory.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/f/file-in-discouraged-x11-font-directory.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: file-in-discouraged-x11-font-directory +Severity: warning +Check: desktop/x11 +Ref: policy 11.8.5 +Info: For historical reasons, use of PEX, CID, + Speedo, and cyrillic subdirectories of + /usr/share/fonts/X11 are permitted, but installation of files + into these directories is discouraged. Support for the first three font + types is deprecated or no longer available, and Cyrillic fonts should use + the normal font directories where possible. diff -Nru lintian-2.93.0/tags/f/file-in-discouraged-x11-font-directory.tag lintian-2.89.0ubuntu1/tags/f/file-in-discouraged-x11-font-directory.tag --- lintian-2.93.0/tags/f/file-in-discouraged-x11-font-directory.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/f/file-in-discouraged-x11-font-directory.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,10 +0,0 @@ -Tag: file-in-discouraged-x11-font-directory -Severity: warning -Check: desktop/x11 -See-Also: policy 11.8.5 -Explanation: For historical reasons, use of PEX, CID, - Speedo, and cyrillic subdirectories of - /usr/share/fonts/X11 are permitted, but installation of files - into these directories is discouraged. Support for the first three font - types is deprecated or no longer available, and Cyrillic fonts should use - the normal font directories where possible. diff -Nru lintian-2.93.0/tags/f/file-in-etc-not-marked-as-conffile.desc lintian-2.89.0ubuntu1/tags/f/file-in-etc-not-marked-as-conffile.desc --- lintian-2.93.0/tags/f/file-in-etc-not-marked-as-conffile.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/f/file-in-etc-not-marked-as-conffile.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: file-in-etc-not-marked-as-conffile +Severity: error +Check: conffiles +Ref: policy 10.7 +Info: Files in /etc must be marked conffiles if they are included + in a package. Otherwise they should be created by maintainer scripts. diff -Nru lintian-2.93.0/tags/f/file-in-etc-not-marked-as-conffile.tag lintian-2.89.0ubuntu1/tags/f/file-in-etc-not-marked-as-conffile.tag --- lintian-2.93.0/tags/f/file-in-etc-not-marked-as-conffile.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/f/file-in-etc-not-marked-as-conffile.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: file-in-etc-not-marked-as-conffile -Severity: error -Check: conffiles -See-Also: policy 10.7 -Explanation: Files in /etc must be marked conffiles if they are included - in a package. Otherwise they should be created by maintainer scripts. diff -Nru lintian-2.93.0/tags/f/file-in-etc-rc.d-marked-as-conffile.desc lintian-2.89.0ubuntu1/tags/f/file-in-etc-rc.d-marked-as-conffile.desc --- lintian-2.93.0/tags/f/file-in-etc-rc.d-marked-as-conffile.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/f/file-in-etc-rc.d-marked-as-conffile.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,5 @@ +Tag: file-in-etc-rc.d-marked-as-conffile +Severity: error +Check: conffiles +Ref: policy 9.3.3 +Info: The symbolic links in /etc/rc?.d may not be marked as conffiles. diff -Nru lintian-2.93.0/tags/f/file-in-etc-rc.d-marked-as-conffile.tag lintian-2.89.0ubuntu1/tags/f/file-in-etc-rc.d-marked-as-conffile.tag --- lintian-2.93.0/tags/f/file-in-etc-rc.d-marked-as-conffile.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/f/file-in-etc-rc.d-marked-as-conffile.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,5 +0,0 @@ -Tag: file-in-etc-rc.d-marked-as-conffile -Severity: error -Check: conffiles -See-Also: policy 9.3.3 -Explanation: The symbolic links in /etc/rc?.d may not be marked as conffiles. diff -Nru lintian-2.93.0/tags/f/file-in-root-and-usr.desc lintian-2.89.0ubuntu1/tags/f/file-in-root-and-usr.desc --- lintian-2.93.0/tags/f/file-in-root-and-usr.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/f/file-in-root-and-usr.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,12 @@ +Tag: file-in-root-and-usr +Severity: error +Check: usrmerge +Info: The package ships two files with the same name installed both in + /{bin,sbin,lib*}/ and /usr/{bin,sbin,lib*}/. + This is incompatible with the merged /usr directories scheme. + . + Packages with conflicting files must remove one of them if possible or + make it a symlink to the other and manage the links in the maintainer + scripts. +Ref: https://wiki.debian.org/UsrMerge, + https://anonscm.debian.org/cgit/users/md/usrmerge.git/plain/debian/README.Debian diff -Nru lintian-2.93.0/tags/f/file-in-root-and-usr.tag lintian-2.89.0ubuntu1/tags/f/file-in-root-and-usr.tag --- lintian-2.93.0/tags/f/file-in-root-and-usr.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/f/file-in-root-and-usr.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,12 +0,0 @@ -Tag: file-in-root-and-usr -Severity: error -Check: usrmerge -Explanation: The package ships two files with the same name installed both in - /{bin,sbin,lib*}/ and /usr/{bin,sbin,lib*}/. - This is incompatible with the merged /usr directories scheme. - . - Packages with conflicting files must remove one of them if possible or - make it a symlink to the other and manage the links in the maintainer - scripts. -See-Also: https://wiki.debian.org/UsrMerge, - https://anonscm.debian.org/cgit/users/md/usrmerge.git/plain/debian/README.Debian diff -Nru lintian-2.93.0/tags/f/file-in-unknown-x11-font-directory.desc lintian-2.89.0ubuntu1/tags/f/file-in-unknown-x11-font-directory.desc --- lintian-2.93.0/tags/f/file-in-unknown-x11-font-directory.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/f/file-in-unknown-x11-font-directory.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: file-in-unknown-x11-font-directory +Severity: error +Check: desktop/x11 +Ref: policy 11.8.5 +Info: Subdirectories of /usr/share/fonts/X11 other than + 100dpi, 75dpi, misc, Type1, and some + historic exceptions must be neither created nor used. (The directories + encodings and util, used by some X Window System + packages, are also permitted by Lintian.) diff -Nru lintian-2.93.0/tags/f/file-in-unknown-x11-font-directory.tag lintian-2.89.0ubuntu1/tags/f/file-in-unknown-x11-font-directory.tag --- lintian-2.93.0/tags/f/file-in-unknown-x11-font-directory.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/f/file-in-unknown-x11-font-directory.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: file-in-unknown-x11-font-directory -Severity: error -Check: desktop/x11 -See-Also: policy 11.8.5 -Explanation: Subdirectories of /usr/share/fonts/X11 other than - 100dpi, 75dpi, misc, Type1, and some - historic exceptions must be neither created nor used. (The directories - encodings and util, used by some X Window System - packages, are also permitted by Lintian.) diff -Nru lintian-2.93.0/tags/f/file-in-unusual-dir.desc lintian-2.89.0ubuntu1/tags/f/file-in-unusual-dir.desc --- lintian-2.93.0/tags/f/file-in-unusual-dir.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/f/file-in-unusual-dir.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,5 @@ +Tag: file-in-unusual-dir +Severity: warning +Check: files/hierarchy/standard +Info: This file or symbolic link is in a directory where files are not + normally installed by Debian packages. diff -Nru lintian-2.93.0/tags/f/file-in-unusual-dir.tag lintian-2.89.0ubuntu1/tags/f/file-in-unusual-dir.tag --- lintian-2.93.0/tags/f/file-in-unusual-dir.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/f/file-in-unusual-dir.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,5 +0,0 @@ -Tag: file-in-unusual-dir -Severity: warning -Check: files/hierarchy/standard -Explanation: This file or symbolic link is in a directory where files are not - normally installed by Debian packages. diff -Nru lintian-2.93.0/tags/f/file-in-usr-lib-sgml.desc lintian-2.89.0ubuntu1/tags/f/file-in-usr-lib-sgml.desc --- lintian-2.93.0/tags/f/file-in-usr-lib-sgml.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/f/file-in-usr-lib-sgml.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: file-in-usr-lib-sgml +Severity: warning +Check: files/sgml +Ref: fhs theusrhierarchy +Info: This package installs a file in /usr/lib/sgml. This was + the old location for SGML catalogs and similar flies. All those files + should now go into /usr/share/sgml. diff -Nru lintian-2.93.0/tags/f/file-in-usr-lib-sgml.tag lintian-2.89.0ubuntu1/tags/f/file-in-usr-lib-sgml.tag --- lintian-2.93.0/tags/f/file-in-usr-lib-sgml.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/f/file-in-usr-lib-sgml.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: file-in-usr-lib-sgml -Severity: warning -Check: files/sgml -See-Also: fhs theusrhierarchy -Explanation: This package installs a file in /usr/lib/sgml. This was - the old location for SGML catalogs and similar flies. All those files - should now go into /usr/share/sgml. diff -Nru lintian-2.93.0/tags/f/file-in-usr-lib-site-python.desc lintian-2.89.0ubuntu1/tags/f/file-in-usr-lib-site-python.desc --- lintian-2.93.0/tags/f/file-in-usr-lib-site-python.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/f/file-in-usr-lib-site-python.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: file-in-usr-lib-site-python +Severity: error +Check: languages/python +Ref: python-policy 2.5 +Info: The directory /usr/lib/site-python has been deprecated as a + location for installing Python modules and may be dropped from Python's + module search path in a future version. Most likely this module is a + private module and should be packaged in a directory outside of Python's + default search path. diff -Nru lintian-2.93.0/tags/f/file-in-usr-lib-site-python.tag lintian-2.89.0ubuntu1/tags/f/file-in-usr-lib-site-python.tag --- lintian-2.93.0/tags/f/file-in-usr-lib-site-python.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/f/file-in-usr-lib-site-python.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: file-in-usr-lib-site-python -Severity: error -Check: languages/python -See-Also: python-policy 2.5 -Explanation: The directory /usr/lib/site-python has been deprecated as a - location for installing Python modules and may be dropped from Python's - module search path in a future version. Most likely this module is a - private module and should be packaged in a directory outside of Python's - default search path. diff -Nru lintian-2.93.0/tags/f/file-in-usr-local.desc lintian-2.89.0ubuntu1/tags/f/file-in-usr-local.desc --- lintian-2.93.0/tags/f/file-in-usr-local.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/f/file-in-usr-local.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: file-in-usr-local +Severity: error +Check: files/hierarchy/standard +Info: The package installs a file in /usr/local/... which is + not allowed. +Ref: policy 9.1.2 diff -Nru lintian-2.93.0/tags/f/file-in-usr-local.tag lintian-2.89.0ubuntu1/tags/f/file-in-usr-local.tag --- lintian-2.93.0/tags/f/file-in-usr-local.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/f/file-in-usr-local.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: file-in-usr-local -Severity: error -Check: files/hierarchy/standard -Explanation: The package installs a file in /usr/local/... which is - not allowed. -See-Also: policy 9.1.2 diff -Nru lintian-2.93.0/tags/f/file-in-usr-marked-as-conffile.desc lintian-2.89.0ubuntu1/tags/f/file-in-usr-marked-as-conffile.desc --- lintian-2.93.0/tags/f/file-in-usr-marked-as-conffile.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/f/file-in-usr-marked-as-conffile.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: file-in-usr-marked-as-conffile +Severity: error +Check: conffiles +Ref: policy 10.7.2 +Info: All configuration files must reside in /etc. Files below + /usr may not be marked as conffiles since /usr might be + mounted read-only. The local system administrator would therefore not + have a chance to modify this configuration file. diff -Nru lintian-2.93.0/tags/f/file-in-usr-marked-as-conffile.tag lintian-2.89.0ubuntu1/tags/f/file-in-usr-marked-as-conffile.tag --- lintian-2.93.0/tags/f/file-in-usr-marked-as-conffile.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/f/file-in-usr-marked-as-conffile.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: file-in-usr-marked-as-conffile -Severity: error -Check: conffiles -See-Also: policy 10.7.2 -Explanation: All configuration files must reside in /etc. Files below - /usr may not be marked as conffiles since /usr might be - mounted read-only. The local system administrator would therefore not - have a chance to modify this configuration file. diff -Nru lintian-2.93.0/tags/f/file-missing-in-md5sums.desc lintian-2.89.0ubuntu1/tags/f/file-missing-in-md5sums.desc --- lintian-2.93.0/tags/f/file-missing-in-md5sums.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/f/file-missing-in-md5sums.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: file-missing-in-md5sums +Severity: warning +Check: md5sums +Info: The package contains a file which isn't listed in the md5sums control + file. + . + Usually, this error occurs during the package build process if the + debian/tmp/ directory is touched after dh_md5sums + is run. diff -Nru lintian-2.93.0/tags/f/file-missing-in-md5sums.tag lintian-2.89.0ubuntu1/tags/f/file-missing-in-md5sums.tag --- lintian-2.93.0/tags/f/file-missing-in-md5sums.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/f/file-missing-in-md5sums.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: file-missing-in-md5sums -Severity: warning -Check: md5sums -Explanation: The package contains a file which isn't listed in the md5sums control - file. - . - Usually, this error occurs during the package build process if the - debian/tmp/ directory is touched after dh_md5sums - is run. diff -Nru lintian-2.93.0/tags/f/file-name-contains-wildcard-character.desc lintian-2.89.0ubuntu1/tags/f/file-name-contains-wildcard-character.desc --- lintian-2.93.0/tags/f/file-name-contains-wildcard-character.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/f/file-name-contains-wildcard-character.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: file-name-contains-wildcard-character +Severity: warning +Certainty: possible +Check: files/names +Info: The file name contains shell wildcard characters. + . + These are most likely unexpanded wildcard characters from (for example) + debian/*.install files, or it may have been installed by accident. diff -Nru lintian-2.93.0/tags/f/file-name-contains-wildcard-character.tag lintian-2.89.0ubuntu1/tags/f/file-name-contains-wildcard-character.tag --- lintian-2.93.0/tags/f/file-name-contains-wildcard-character.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/f/file-name-contains-wildcard-character.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: file-name-contains-wildcard-character -Severity: warning -Check: files/names -Explanation: The file name contains shell wildcard characters. - . - These are most likely unexpanded wildcard characters from (for example) - debian/*.install files, or it may have been installed by accident. diff -Nru lintian-2.93.0/tags/f/file-name-ends-in-whitespace.desc lintian-2.89.0ubuntu1/tags/f/file-name-ends-in-whitespace.desc --- lintian-2.93.0/tags/f/file-name-ends-in-whitespace.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/f/file-name-ends-in-whitespace.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: file-name-ends-in-whitespace +Severity: warning +Certainty: possible +Check: files/names +Info: This package installs a file or directory whose name ends in + whitespace. This might be intentional but it's normally a mistake. If + it is intentional, add a Lintian override. + . + One possible cause is using debhelper 5.0.57 or earlier to install a + doc-base file with a Document field that ends in whitespace. diff -Nru lintian-2.93.0/tags/f/file-name-ends-in-whitespace.tag lintian-2.89.0ubuntu1/tags/f/file-name-ends-in-whitespace.tag --- lintian-2.93.0/tags/f/file-name-ends-in-whitespace.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/f/file-name-ends-in-whitespace.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: file-name-ends-in-whitespace -Severity: warning -Check: files/names -Explanation: This package installs a file or directory whose name ends in - whitespace. This might be intentional but it's normally a mistake. If - it is intentional, add a Lintian override. - . - One possible cause is using debhelper 5.0.57 or earlier to install a - doc-base file with a Document field that ends in whitespace. diff -Nru lintian-2.93.0/tags/f/file-name-in-PATH-is-not-ASCII.desc lintian-2.89.0ubuntu1/tags/f/file-name-in-PATH-is-not-ASCII.desc --- lintian-2.93.0/tags/f/file-name-in-PATH-is-not-ASCII.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/f/file-name-in-PATH-is-not-ASCII.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: file-name-in-PATH-is-not-ASCII +Severity: error +Check: files/names +Ref: policy 10.10 +Info: The given file is in PATH but consists of non-ASCII characters. + . + Note that Lintian may be unable to display the filename accurately. + Unprintable characters may have been replaced. diff -Nru lintian-2.93.0/tags/f/file-name-in-PATH-is-not-ASCII.tag lintian-2.89.0ubuntu1/tags/f/file-name-in-PATH-is-not-ASCII.tag --- lintian-2.93.0/tags/f/file-name-in-PATH-is-not-ASCII.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/f/file-name-in-PATH-is-not-ASCII.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: file-name-in-PATH-is-not-ASCII -Severity: error -Check: files/names -See-Also: policy 10.10 -Explanation: The given file is in PATH but consists of non-ASCII characters. - . - Note that Lintian may be unable to display the filename accurately. - Unprintable characters may have been replaced. diff -Nru lintian-2.93.0/tags/f/file-references-package-build-path.desc lintian-2.89.0ubuntu1/tags/f/file-references-package-build-path.desc --- lintian-2.93.0/tags/f/file-references-package-build-path.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/f/file-references-package-build-path.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,19 @@ +Tag: file-references-package-build-path +Severity: info +Certainty: possible +Check: files/contents +Info: The listed file or maintainer script appears to reference + the build path used to build the package as specified in the + Build-Path field of the .buildinfo file. + . + This is likely to cause the package to be unreproducible, but it may + also indicate that the package will not work correctly outside of the + maintainer's own system. + . + Please note that this tag will not appear unless the + .buildinfo file contains a Build-Path field. That + field is optional. You may have to set + DEB_BUILD_OPTIONS=buildinfo=+path or use + --buildinfo-option=--always-include-path with + dpkg-buildpackage when building. +Ref: https://reproducible-builds.org/, https://wiki.debian.org/ReproducibleBuilds/BuildinfoFiles, dpkg-genbuildinfo(1) diff -Nru lintian-2.93.0/tags/f/file-references-package-build-path.tag lintian-2.89.0ubuntu1/tags/f/file-references-package-build-path.tag --- lintian-2.93.0/tags/f/file-references-package-build-path.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/f/file-references-package-build-path.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,18 +0,0 @@ -Tag: file-references-package-build-path -Severity: info -Check: files/contents -Explanation: The listed file or maintainer script appears to reference - the build path used to build the package as specified in the - Build-Path field of the .buildinfo file. - . - This is likely to cause the package to be unreproducible, but it may - also indicate that the package will not work correctly outside of the - maintainer's own system. - . - Please note that this tag will not appear unless the - .buildinfo file contains a Build-Path field. That - field is optional. You may have to set - DEB_BUILD_OPTIONS=buildinfo=+path or use - --buildinfo-option=--always-include-path with - dpkg-buildpackage when building. -See-Also: https://reproducible-builds.org/, https://wiki.debian.org/ReproducibleBuilds/BuildinfoFiles, dpkg-genbuildinfo(1) diff -Nru lintian-2.93.0/tags/f/files-excluded-without-copyright-format-1.0.desc lintian-2.89.0ubuntu1/tags/f/files-excluded-without-copyright-format-1.0.desc --- lintian-2.93.0/tags/f/files-excluded-without-copyright-format-1.0.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/f/files-excluded-without-copyright-format-1.0.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,15 @@ +Tag: files-excluded-without-copyright-format-1.0 +Severity: error +Check: debian/copyright/dep5 +Info: The Files-Excluded field in debian/copyright is + used to exclude files from upstream source packages such as when they + violate the Debian Free Software Guidelines + . + However, this field will be ignored by uscan(1) if the copyright + file is not declared as following the 1.0 format. + . + Please ensure your debian/copyright file starts with the + following line: + . + Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ +Ref: uscan(1) diff -Nru lintian-2.93.0/tags/f/files-excluded-without-copyright-format-1.0.tag lintian-2.89.0ubuntu1/tags/f/files-excluded-without-copyright-format-1.0.tag --- lintian-2.93.0/tags/f/files-excluded-without-copyright-format-1.0.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/f/files-excluded-without-copyright-format-1.0.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,15 +0,0 @@ -Tag: files-excluded-without-copyright-format-1.0 -Severity: error -Check: debian/copyright/dep5 -Explanation: The Files-Excluded field in debian/copyright is - used to exclude files from upstream source packages such as when they - violate the Debian Free Software Guidelines - . - However, this field will be ignored by uscan(1) if the copyright - file is not declared as following the 1.0 format. - . - Please ensure your debian/copyright file starts with the - following line: - . - Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ -See-Also: uscan(1) diff -Nru lintian-2.93.0/tags/f/file-size-mismatch-in-changes-file.desc lintian-2.89.0ubuntu1/tags/f/file-size-mismatch-in-changes-file.desc --- lintian-2.93.0/tags/f/file-size-mismatch-in-changes-file.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/f/file-size-mismatch-in-changes-file.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: file-size-mismatch-in-changes-file +Severity: error +Check: changes-file +Info: The actual file size does not match what's listed in the + .changes file. +Ref: policy 5.6.21, policy 5.6.24 diff -Nru lintian-2.93.0/tags/f/file-size-mismatch-in-changes-file.tag lintian-2.89.0ubuntu1/tags/f/file-size-mismatch-in-changes-file.tag --- lintian-2.93.0/tags/f/file-size-mismatch-in-changes-file.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/f/file-size-mismatch-in-changes-file.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: file-size-mismatch-in-changes-file -Severity: error -Check: changes-file -Explanation: The actual file size does not match what's listed in the - .changes file. -See-Also: policy 5.6.21, policy 5.6.24 diff -Nru lintian-2.93.0/tags/f/file-without-copyright-information.desc lintian-2.89.0ubuntu1/tags/f/file-without-copyright-information.desc --- lintian-2.93.0/tags/f/file-without-copyright-information.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/f/file-without-copyright-information.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: file-without-copyright-information +Severity: warning +Certainty: possible +Check: debian/copyright/dep5 +Ref: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ +Info: The source tree contains a file which was not matched by any of + the Files paragraphs in debian/copyright. Either adjust existing + wildcards to match that file or add a new Files paragraph. diff -Nru lintian-2.93.0/tags/f/file-without-copyright-information.tag lintian-2.89.0ubuntu1/tags/f/file-without-copyright-information.tag --- lintian-2.93.0/tags/f/file-without-copyright-information.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/f/file-without-copyright-information.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: file-without-copyright-information -Severity: warning -Check: debian/copyright/dep5 -See-Also: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ -Explanation: The source tree contains a file which was not matched by any of - the Files paragraphs in debian/copyright. Either adjust existing - wildcards to match that file or add a new Files paragraph. diff -Nru lintian-2.93.0/tags/f/font-in-non-font-package.desc lintian-2.89.0ubuntu1/tags/f/font-in-non-font-package.desc --- lintian-2.93.0/tags/f/font-in-non-font-package.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/f/font-in-non-font-package.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,12 @@ +Tag: font-in-non-font-package +Severity: info +Certainty: possible +Check: fonts +Info: This package contains a *.ttf, *.otf, or *.pfb file, file + extensions used by TrueType, OpenType, or Type 1 fonts, but the package + does not appear to be a dedicated font package. Dedicated font package + names should begin with fonts-. (Type 1 fonts are also allowed + in packages starting with xfonts-.) If the font is already + packaged, you should depend on that package instead. Otherwise, normally + the font should be packaged separately, since fonts are usually useful + outside of the package that embeds them. diff -Nru lintian-2.93.0/tags/f/font-in-non-font-package.tag lintian-2.89.0ubuntu1/tags/f/font-in-non-font-package.tag --- lintian-2.93.0/tags/f/font-in-non-font-package.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/f/font-in-non-font-package.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,11 +0,0 @@ -Tag: font-in-non-font-package -Severity: info -Check: fonts -Explanation: This package contains a *.ttf, *.otf, or *.pfb file, file - extensions used by TrueType, OpenType, or Type 1 fonts, but the package - does not appear to be a dedicated font package. Dedicated font package - names should begin with fonts-. (Type 1 fonts are also allowed - in packages starting with xfonts-.) If the font is already - packaged, you should depend on that package instead. Otherwise, normally - the font should be packaged separately, since fonts are usually useful - outside of the package that embeds them. diff -Nru lintian-2.93.0/tags/f/font-outside-font-dir.desc lintian-2.89.0ubuntu1/tags/f/font-outside-font-dir.desc --- lintian-2.93.0/tags/f/font-outside-font-dir.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/f/font-outside-font-dir.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: font-outside-font-dir +Severity: info +Certainty: possible +Check: fonts +Info: This package contains a TrueType, OpenType, or Type 1 fonts, + but the package does not install this file under /usr/share/fonts/. +Ref: https://wiki.debian.org/Fonts/PackagingPolicy diff -Nru lintian-2.93.0/tags/f/font-outside-font-dir.tag lintian-2.89.0ubuntu1/tags/f/font-outside-font-dir.tag --- lintian-2.93.0/tags/f/font-outside-font-dir.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/f/font-outside-font-dir.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: font-outside-font-dir -Severity: info -Check: fonts -Explanation: This package contains a TrueType, OpenType, or Type 1 fonts, - but the package does not install this file under /usr/share/fonts/. -See-Also: https://wiki.debian.org/Fonts/PackagingPolicy diff -Nru lintian-2.93.0/tags/f/font-package-not-multi-arch-foreign.desc lintian-2.89.0ubuntu1/tags/f/font-package-not-multi-arch-foreign.desc --- lintian-2.93.0/tags/f/font-package-not-multi-arch-foreign.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/f/font-package-not-multi-arch-foreign.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: font-package-not-multi-arch-foreign +Severity: warning +Check: fields/multi-arch +Info: This package is architecture all and hence requires a Multi-Arch + foreign value. + . + An Architecture: all package to satisfy the dependencies of a + foreign-architecture package, it must be marked Multi-Arch: foreign + or Multi-Arch: allowed. +Ref: https://wiki.ubuntu.com/MultiarchSpec#Dependencies_involving_Architecture:_all_packages diff -Nru lintian-2.93.0/tags/f/font-package-not-multi-arch-foreign.tag lintian-2.89.0ubuntu1/tags/f/font-package-not-multi-arch-foreign.tag --- lintian-2.93.0/tags/f/font-package-not-multi-arch-foreign.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/f/font-package-not-multi-arch-foreign.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,10 +0,0 @@ -Tag: font-package-not-multi-arch-foreign -Severity: warning -Check: fields/multi-arch -Explanation: This package is architecture all and hence requires a Multi-Arch - foreign value. - . - An Architecture: all package to satisfy the dependencies of a - foreign-architecture package, it must be marked Multi-Arch: foreign - or Multi-Arch: allowed. -See-Also: https://wiki.ubuntu.com/MultiarchSpec#Dependencies_involving_Architecture:_all_packages diff -Nru lintian-2.93.0/tags/f/forbidden-config-interpreter.desc lintian-2.89.0ubuntu1/tags/f/forbidden-config-interpreter.desc --- lintian-2.93.0/tags/f/forbidden-config-interpreter.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/f/forbidden-config-interpreter.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: forbidden-config-interpreter +Severity: error +Check: scripts +Info: This package contains a config script for pre-configuring + the package. During pre-configuration, however, only essential packages + are guaranteed to be installed, so you cannot use a non-essential + interpreter. diff -Nru lintian-2.93.0/tags/f/forbidden-config-interpreter.tag lintian-2.89.0ubuntu1/tags/f/forbidden-config-interpreter.tag --- lintian-2.93.0/tags/f/forbidden-config-interpreter.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/f/forbidden-config-interpreter.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: forbidden-config-interpreter -Severity: error -Check: scripts -Explanation: This package contains a config script for pre-configuring - the package. During pre-configuration, however, only essential packages - are guaranteed to be installed, so you cannot use a non-essential - interpreter. diff -Nru lintian-2.93.0/tags/f/forbidden-postrm-interpreter.desc lintian-2.89.0ubuntu1/tags/f/forbidden-postrm-interpreter.desc --- lintian-2.93.0/tags/f/forbidden-postrm-interpreter.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/f/forbidden-postrm-interpreter.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: forbidden-postrm-interpreter +Severity: error +Check: scripts +Info: This package contains a postrm maintainer script that uses + an interpreter that isn't essential. The purge action of + postrm can only rely on essential packages, which means the + interpreter used by postrm must be one of the essential ones + (sh, bash, or perl). +Ref: policy 7.2 diff -Nru lintian-2.93.0/tags/f/forbidden-postrm-interpreter.tag lintian-2.89.0ubuntu1/tags/f/forbidden-postrm-interpreter.tag --- lintian-2.93.0/tags/f/forbidden-postrm-interpreter.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/f/forbidden-postrm-interpreter.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: forbidden-postrm-interpreter -Severity: error -Check: scripts -Explanation: This package contains a postrm maintainer script that uses - an interpreter that isn't essential. The purge action of - postrm can only rely on essential packages, which means the - interpreter used by postrm must be one of the essential ones - (sh, bash, or perl). -See-Also: policy 7.2 diff -Nru lintian-2.93.0/tags/f/format-3.0-but-debian-changes-patch.desc lintian-2.89.0ubuntu1/tags/f/format-3.0-but-debian-changes-patch.desc --- lintian-2.93.0/tags/f/format-3.0-but-debian-changes-patch.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/f/format-3.0-but-debian-changes-patch.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,12 @@ +Tag: format-3.0-but-debian-changes-patch +Severity: warning +Check: debian/patches/quilt +Info: This package declares source format 3.0 (quilt), but the Debian + .debian.tar.gz file contains a debian-changes-VERSION patch, which represents + direct changes to files outside of the debian directory. This often + indicates accidental changes that weren't meant to be in the package or changes + that were supposed to be separated out into a patch. + . + If this is intentional, you may wish to consider adding + single-debian-patch to debian/source/options, and/or a patch + header to debian/source/patch-header explaining why this is done. diff -Nru lintian-2.93.0/tags/f/format-3.0-but-debian-changes-patch.tag lintian-2.89.0ubuntu1/tags/f/format-3.0-but-debian-changes-patch.tag --- lintian-2.93.0/tags/f/format-3.0-but-debian-changes-patch.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/f/format-3.0-but-debian-changes-patch.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,12 +0,0 @@ -Tag: format-3.0-but-debian-changes-patch -Severity: warning -Check: debian/patches/quilt -Explanation: This package declares source format 3.0 (quilt), but the Debian - .debian.tar.gz file contains a debian-changes-VERSION patch, which represents - direct changes to files outside of the debian directory. This often - indicates accidental changes that weren't meant to be in the package or changes - that were supposed to be separated out into a patch. - . - If this is intentional, you may wish to consider adding - single-debian-patch to debian/source/options, and/or a patch - header to debian/source/patch-header explaining why this is done. diff -Nru lintian-2.93.0/tags/f/FSSTND-dir-in-manual-page.desc lintian-2.89.0ubuntu1/tags/f/FSSTND-dir-in-manual-page.desc --- lintian-2.93.0/tags/f/FSSTND-dir-in-manual-page.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/f/FSSTND-dir-in-manual-page.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: FSSTND-dir-in-manual-page +Severity: info +Check: documentation/manual +Info: The manual page references a directory that is specified + in the FSSTND but not in the FHS which is used by Debian. + This can be an indicator of a mismatch of the location of + files as installed for Debian and as described by the manual page. + . + If you have to change file locations to abide by Debian Policy + please also patch the manual page to mention these new locations. diff -Nru lintian-2.93.0/tags/f/FSSTND-dir-in-manual-page.tag lintian-2.89.0ubuntu1/tags/f/FSSTND-dir-in-manual-page.tag --- lintian-2.93.0/tags/f/FSSTND-dir-in-manual-page.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/f/FSSTND-dir-in-manual-page.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,10 +0,0 @@ -Tag: FSSTND-dir-in-manual-page -Severity: info -Check: documentation/manual -Explanation: The manual page references a directory that is specified - in the FSSTND but not in the FHS which is used by Debian. - This can be an indicator of a mismatch of the location of - files as installed for Debian and as described by the manual page. - . - If you have to change file locations to abide by Debian Policy - please also patch the manual page to mention these new locations. diff -Nru lintian-2.93.0/tags/f/FSSTND-dir-in-usr.desc lintian-2.89.0ubuntu1/tags/f/FSSTND-dir-in-usr.desc --- lintian-2.93.0/tags/f/FSSTND-dir-in-usr.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/f/FSSTND-dir-in-usr.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: FSSTND-dir-in-usr +Severity: error +Check: files/hierarchy/standard +Info: As of policy version 3.0.0.0, Debian no longer follows the FSSTND. + . + Instead, the Filesystem Hierarchy Standard (FHS), version 2.3, is + used. You can find it in /usr/share/doc/debian-policy/fhs/ . +Ref: policy 9.1.1 diff -Nru lintian-2.93.0/tags/f/FSSTND-dir-in-usr.tag lintian-2.89.0ubuntu1/tags/f/FSSTND-dir-in-usr.tag --- lintian-2.93.0/tags/f/FSSTND-dir-in-usr.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/f/FSSTND-dir-in-usr.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: FSSTND-dir-in-usr -Severity: error -Check: files/hierarchy/standard -Explanation: As of policy version 3.0.0.0, Debian no longer follows the FSSTND. - . - Instead, the Filesystem Hierarchy Standard (FHS), version 2.3, is - used. You can find it in /usr/share/doc/debian-policy/fhs/ . -See-Also: policy 9.1.1 diff -Nru lintian-2.93.0/tags/f/FSSTND-dir-in-var.desc lintian-2.89.0ubuntu1/tags/f/FSSTND-dir-in-var.desc --- lintian-2.93.0/tags/f/FSSTND-dir-in-var.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/f/FSSTND-dir-in-var.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: FSSTND-dir-in-var +Severity: error +Check: files/hierarchy/standard +Info: As of policy version 3.0.0.0, Debian no longer follows the FSSTND. + . + Instead, the Filesystem Hierarchy Standard (FHS), version 2.3, is + used. You can find it in /usr/share/doc/debian-policy/fhs/ . +Ref: policy 9.1.1 diff -Nru lintian-2.93.0/tags/f/FSSTND-dir-in-var.tag lintian-2.89.0ubuntu1/tags/f/FSSTND-dir-in-var.tag --- lintian-2.93.0/tags/f/FSSTND-dir-in-var.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/f/FSSTND-dir-in-var.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: FSSTND-dir-in-var -Severity: error -Check: files/hierarchy/standard -Explanation: As of policy version 3.0.0.0, Debian no longer follows the FSSTND. - . - Instead, the Filesystem Hierarchy Standard (FHS), version 2.3, is - used. You can find it in /usr/share/doc/debian-policy/fhs/ . -See-Also: policy 9.1.1 diff -Nru lintian-2.93.0/tags/g/game-outside-section.desc lintian-2.89.0ubuntu1/tags/g/game-outside-section.desc --- lintian-2.93.0/tags/g/game-outside-section.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/g/game-outside-section.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: game-outside-section +Severity: warning +Certainty: possible +Check: games +Renamed-From: games-package-should-be-section-games +Info: All the executables in this package are in /usr/games, but + the package is not in section games. This can be intentional but is + usually a mistake. diff -Nru lintian-2.93.0/tags/g/game-outside-section.tag lintian-2.89.0ubuntu1/tags/g/game-outside-section.tag --- lintian-2.93.0/tags/g/game-outside-section.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/g/game-outside-section.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: game-outside-section -Severity: warning -Check: games -Renamed-From: games-package-should-be-section-games -Explanation: All the executables in this package are in /usr/games, but - the package is not in section games. This can be intentional but is - usually a mistake. diff -Nru lintian-2.93.0/tags/g/gawk-script-but-no-gawk-dep.desc lintian-2.89.0ubuntu1/tags/g/gawk-script-but-no-gawk-dep.desc --- lintian-2.93.0/tags/g/gawk-script-but-no-gawk-dep.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/g/gawk-script-but-no-gawk-dep.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: gawk-script-but-no-gawk-dep +Severity: error +Check: scripts +Info: Packages that use gawk scripts must depend on the gawk package. + If they don't need gawk-specific features, and can just as easily work + with mawk, then they should be awk scripts instead. + . + In some cases a weaker relationship, such as Suggests or Recommends, will + be more appropriate. diff -Nru lintian-2.93.0/tags/g/gawk-script-but-no-gawk-dep.tag lintian-2.89.0ubuntu1/tags/g/gawk-script-but-no-gawk-dep.tag --- lintian-2.93.0/tags/g/gawk-script-but-no-gawk-dep.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/g/gawk-script-but-no-gawk-dep.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: gawk-script-but-no-gawk-dep -Severity: error -Check: scripts -Explanation: Packages that use gawk scripts must depend on the gawk package. - If they don't need gawk-specific features, and can just as easily work - with mawk, then they should be awk scripts instead. - . - In some cases a weaker relationship, such as Suggests or Recommends, will - be more appropriate. diff -Nru lintian-2.93.0/tags/g/gfortran-module-does-not-declare-version.desc lintian-2.89.0ubuntu1/tags/g/gfortran-module-does-not-declare-version.desc --- lintian-2.93.0/tags/g/gfortran-module-does-not-declare-version.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/g/gfortran-module-does-not-declare-version.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: gfortran-module-does-not-declare-version +Severity: warning +Check: languages/fortran/gfortran +Info: The installation package ships a GFORTRAN module which does not + declare a module version number. That number is needed to establish the + proper prerequisites for binary rebuilds. +Ref: #796352, + #714730, + https://salsa.debian.org/science-team/dh-fortran-mod/blob/debian/master/dh_fortran_mod.in diff -Nru lintian-2.93.0/tags/g/gfortran-module-does-not-declare-version.tag lintian-2.89.0ubuntu1/tags/g/gfortran-module-does-not-declare-version.tag --- lintian-2.93.0/tags/g/gfortran-module-does-not-declare-version.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/g/gfortran-module-does-not-declare-version.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: gfortran-module-does-not-declare-version -Severity: warning -Check: languages/fortran/gfortran -Explanation: The installation package ships a GFORTRAN module which does not - declare a module version number. That number is needed to establish the - proper prerequisites for binary rebuilds. -See-Also: Bug#796352, - Bug#714730, - https://salsa.debian.org/science-team/dh-fortran-mod/blob/debian/master/dh_fortran_mod.in diff -Nru lintian-2.93.0/tags/g/gir-in-arch-all-package.desc lintian-2.89.0ubuntu1/tags/g/gir-in-arch-all-package.desc --- lintian-2.93.0/tags/g/gir-in-arch-all-package.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/g/gir-in-arch-all-package.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: gir-in-arch-all-package +Severity: warning +Check: desktop/gnome/gir +Info: GObject-Introspection XML files + (/usr/share/gir-1.0/Foo-23.gir) must be made available in + an architecture-dependent package of the same source. +Ref: /usr/share/doc/gobject-introspection/policy.txt diff -Nru lintian-2.93.0/tags/g/gir-in-arch-all-package.tag lintian-2.89.0ubuntu1/tags/g/gir-in-arch-all-package.tag --- lintian-2.93.0/tags/g/gir-in-arch-all-package.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/g/gir-in-arch-all-package.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: gir-in-arch-all-package -Severity: warning -Check: desktop/gnome/gir -Explanation: GObject-Introspection XML files - (/usr/share/gir-1.0/Foo-23.gir) must be made available in - an architecture-dependent package of the same source. -See-Also: /usr/share/doc/gobject-introspection/policy.txt diff -Nru lintian-2.93.0/tags/g/gir-missing-typelib-dependency.desc lintian-2.89.0ubuntu1/tags/g/gir-missing-typelib-dependency.desc --- lintian-2.93.0/tags/g/gir-missing-typelib-dependency.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/g/gir-missing-typelib-dependency.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,25 @@ +Tag: gir-missing-typelib-dependency +Severity: warning +Certainty: possible +Check: desktop/gnome/gir +Info: Development packages that contain GObject-Introspection XML files + (/usr/share/gir-1.0/Foo-23.gir) must depend on the package + containing the corresponding binary typelib, which is conventionally named + gir1.2-foo-23. The dependency must be strictly versioned + (for example gir1.2-foo-23 (= ${binary:Version}) when using + debhelper). + . + If multiple typelibs are shipped in the same package, then that package + should have versioned Provides for the names that would have been + used for separate packages. In this case, Lintian does not emit this tag + when a group of binary packages from the same source is checked together. + . + For example, libgtk-3-dev contains Gtk-3.0.gir, + Gdk-3.0.gir and GdkX11-3.0.gir. + gir1.2-gtk-3.0 contains all three corresponding typelibs, + so it is sufficient for libgtk-3-dev to depend on + gir1.2-gtk-3.0. Giving gir1.2-gtk-3.0 Provides + entries for gir1.2-gdk-3.0 (= ${binary:Version}) + and gir1.2-gdkx11-3.0 (= ${binary:Version}) signals this + situation to Lintian. +Ref: /usr/share/doc/gobject-introspection/policy.txt diff -Nru lintian-2.93.0/tags/g/gir-missing-typelib-dependency.tag lintian-2.89.0ubuntu1/tags/g/gir-missing-typelib-dependency.tag --- lintian-2.93.0/tags/g/gir-missing-typelib-dependency.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/g/gir-missing-typelib-dependency.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,24 +0,0 @@ -Tag: gir-missing-typelib-dependency -Severity: warning -Check: desktop/gnome/gir -Explanation: Development packages that contain GObject-Introspection XML files - (/usr/share/gir-1.0/Foo-23.gir) must depend on the package - containing the corresponding binary typelib, which is conventionally named - gir1.2-foo-23. The dependency must be strictly versioned - (for example gir1.2-foo-23 (= ${binary:Version}) when using - debhelper). - . - If multiple typelibs are shipped in the same package, then that package - should have versioned Provides for the names that would have been - used for separate packages. In this case, Lintian does not emit this tag - when a group of binary packages from the same source is checked together. - . - For example, libgtk-3-dev contains Gtk-3.0.gir, - Gdk-3.0.gir and GdkX11-3.0.gir. - gir1.2-gtk-3.0 contains all three corresponding typelibs, - so it is sufficient for libgtk-3-dev to depend on - gir1.2-gtk-3.0. Giving gir1.2-gtk-3.0 Provides - entries for gir1.2-gdk-3.0 (= ${binary:Version}) - and gir1.2-gdkx11-3.0 (= ${binary:Version}) signals this - situation to Lintian. -See-Also: /usr/share/doc/gobject-introspection/policy.txt diff -Nru lintian-2.93.0/tags/g/gir-section-not-libdevel.desc lintian-2.89.0ubuntu1/tags/g/gir-section-not-libdevel.desc --- lintian-2.93.0/tags/g/gir-section-not-libdevel.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/g/gir-section-not-libdevel.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: gir-section-not-libdevel +Severity: warning +Check: desktop/gnome/gir +Info: GObject-Introspection XML files + (/usr/share/gir-1.0/Foo-23.gir) must be made available in + a development package in the libdevel section of the archive. + This is normally the same libfoo-dev package that contains + other development files. +Ref: /usr/share/doc/gobject-introspection/policy.txt diff -Nru lintian-2.93.0/tags/g/gir-section-not-libdevel.tag lintian-2.89.0ubuntu1/tags/g/gir-section-not-libdevel.tag --- lintian-2.93.0/tags/g/gir-section-not-libdevel.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/g/gir-section-not-libdevel.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: gir-section-not-libdevel -Severity: warning -Check: desktop/gnome/gir -Explanation: GObject-Introspection XML files - (/usr/share/gir-1.0/Foo-23.gir) must be made available in - a development package in the libdevel section of the archive. - This is normally the same libfoo-dev package that contains - other development files. -See-Also: /usr/share/doc/gobject-introspection/policy.txt diff -Nru lintian-2.93.0/tags/g/git-patches-not-exported.desc lintian-2.89.0ubuntu1/tags/g/git-patches-not-exported.desc --- lintian-2.93.0/tags/g/git-patches-not-exported.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/g/git-patches-not-exported.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,16 @@ +Tag: git-patches-not-exported +Severity: error +Certainty: possible +Check: debian/source-dir +Info: The source package contains files in + debian/source/git-patches. These patches should have been exported + via the quilt-patches-deb-export-hook of gitpkg. + . + It does not look like the patches were exported for this source package. + . + You will see this tag when you generate a source package without + gitpkg (or with a misconfigured version) unless the patches + were exported manually. + . + See the above mentioned hook file (in /usr/share/gitpkg/hooks) + for information on how to export patches manually. diff -Nru lintian-2.93.0/tags/g/git-patches-not-exported.tag lintian-2.89.0ubuntu1/tags/g/git-patches-not-exported.tag --- lintian-2.93.0/tags/g/git-patches-not-exported.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/g/git-patches-not-exported.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,15 +0,0 @@ -Tag: git-patches-not-exported -Severity: error -Check: debian/source-dir -Explanation: The source package contains files in - debian/source/git-patches. These patches should have been exported - via the quilt-patches-deb-export-hook of gitpkg. - . - It does not look like the patches were exported for this source package. - . - You will see this tag when you generate a source package without - gitpkg (or with a misconfigured version) unless the patches - were exported manually. - . - See the above mentioned hook file (in /usr/share/gitpkg/hooks) - for information on how to export patches manually. diff -Nru lintian-2.93.0/tags/g/global-data-in-games-directory.desc lintian-2.89.0ubuntu1/tags/g/global-data-in-games-directory.desc --- lintian-2.93.0/tags/g/global-data-in-games-directory.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/g/global-data-in-games-directory.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,14 @@ +Tag: global-data-in-games-directory +Severity: error +Check: games +Info: This package contains files under /usr/share/games, such as + desktop files, icons, pixmaps, or MIME type entries, that are global + system data. The user's desktop environment will only check in the + directories directly under /usr/share and this information + should be put in the global directory even if it is for games. + . + The most common cause of this problem is using a + --datadir=/usr/share/games argument to configure or an + equivalent and using the upstream installation rules. These files need + to be moved into the corresponding directories directly under + /usr/share. diff -Nru lintian-2.93.0/tags/g/global-data-in-games-directory.tag lintian-2.89.0ubuntu1/tags/g/global-data-in-games-directory.tag --- lintian-2.93.0/tags/g/global-data-in-games-directory.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/g/global-data-in-games-directory.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,14 +0,0 @@ -Tag: global-data-in-games-directory -Severity: error -Check: games -Explanation: This package contains files under /usr/share/games, such as - desktop files, icons, pixmaps, or MIME type entries, that are global - system data. The user's desktop environment will only check in the - directories directly under /usr/share and this information - should be put in the global directory even if it is for games. - . - The most common cause of this problem is using a - --datadir=/usr/share/games argument to configure or an - equivalent and using the upstream installation rules. These files need - to be moved into the corresponding directories directly under - /usr/share. diff -Nru lintian-2.93.0/tags/g/global-files-wildcard-not-first-paragraph-in-dep5-copyright.desc lintian-2.89.0ubuntu1/tags/g/global-files-wildcard-not-first-paragraph-in-dep5-copyright.desc --- lintian-2.93.0/tags/g/global-files-wildcard-not-first-paragraph-in-dep5-copyright.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/g/global-files-wildcard-not-first-paragraph-in-dep5-copyright.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,15 @@ +Tag: global-files-wildcard-not-first-paragraph-in-dep5-copyright +Severity: warning +Check: debian/copyright/dep5 +Info: The specified paragraph in the machine readable copyright file references + all possible files but is not the first paragraph. For example: + . + Files: filea + Copyright: 2009, ... + . + Files: * + Copyright: 2010, ... + . + As the paragraphs is matched on a "last match wins" principle, all proceeding + paragraphs are overridden. +Ref: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ diff -Nru lintian-2.93.0/tags/g/global-files-wildcard-not-first-paragraph-in-dep5-copyright.tag lintian-2.89.0ubuntu1/tags/g/global-files-wildcard-not-first-paragraph-in-dep5-copyright.tag --- lintian-2.93.0/tags/g/global-files-wildcard-not-first-paragraph-in-dep5-copyright.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/g/global-files-wildcard-not-first-paragraph-in-dep5-copyright.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,15 +0,0 @@ -Tag: global-files-wildcard-not-first-paragraph-in-dep5-copyright -Severity: warning -Check: debian/copyright/dep5 -Explanation: The specified paragraph in the machine readable copyright file references - all possible files but is not the first paragraph. For example: - . - Files: filea - Copyright: 2009, ... - . - Files: * - Copyright: 2010, ... - . - As the paragraphs is matched on a "last match wins" principle, all proceeding - paragraphs are overridden. -See-Also: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ diff -Nru lintian-2.93.0/tags/g/globbing-patterns-out-of-order.desc lintian-2.89.0ubuntu1/tags/g/globbing-patterns-out-of-order.desc --- lintian-2.93.0/tags/g/globbing-patterns-out-of-order.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/g/globbing-patterns-out-of-order.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,13 @@ +Tag: globbing-patterns-out-of-order +Severity: warning +Check: debian/copyright/dep5 +Info: The Files sections in debian/copyright are out of order. + The relative directory depth should increase from one section to the next. + That is the general pattern of the specification, with * at the top. + . + When sections are in another order, some files may be associated + with the wrong license. + . + Please reorder the sections. +Ref: Bug#905747, + https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ diff -Nru lintian-2.93.0/tags/g/globbing-patterns-out-of-order.tag lintian-2.89.0ubuntu1/tags/g/globbing-patterns-out-of-order.tag --- lintian-2.93.0/tags/g/globbing-patterns-out-of-order.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/g/globbing-patterns-out-of-order.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,13 +0,0 @@ -Tag: globbing-patterns-out-of-order -Severity: warning -Check: debian/copyright/dep5 -Explanation: The Files sections in debian/copyright are out of order. - The relative directory depth should increase from one section to the next. - That is the general pattern of the specification, with * at the top. - . - When sections are in another order, some files may be associated - with the wrong license. - . - Please reorder the sections. -See-Also: Bug#905747, - https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ diff -Nru lintian-2.93.0/tags/g/gobject-introspection-package-missing-depends-on-gir-depends.desc lintian-2.89.0ubuntu1/tags/g/gobject-introspection-package-missing-depends-on-gir-depends.desc --- lintian-2.93.0/tags/g/gobject-introspection-package-missing-depends-on-gir-depends.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/g/gobject-introspection-package-missing-depends-on-gir-depends.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: gobject-introspection-package-missing-depends-on-gir-depends +Severity: error +Check: debian/control +Info: The package is a GObject Introspection package but does not specify a + dependency on the ${gir:Depends} substvar. Without the dependencies, a + program usually aborts. + . + Often, this can be fixed by adding the --with=gir debhelper + sequence. diff -Nru lintian-2.93.0/tags/g/gobject-introspection-package-missing-depends-on-gir-depends.tag lintian-2.89.0ubuntu1/tags/g/gobject-introspection-package-missing-depends-on-gir-depends.tag --- lintian-2.93.0/tags/g/gobject-introspection-package-missing-depends-on-gir-depends.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/g/gobject-introspection-package-missing-depends-on-gir-depends.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: gobject-introspection-package-missing-depends-on-gir-depends -Severity: error -Check: debian/control -Explanation: The package is a GObject Introspection package but does not specify a - dependency on the ${gir:Depends} substvar. Without the dependencies, a - program usually aborts. - . - Often, this can be fixed by adding the --with=gir debhelper - sequence. diff -Nru lintian-2.93.0/tags/g/groff-message.desc lintian-2.89.0ubuntu1/tags/g/groff-message.desc --- lintian-2.93.0/tags/g/groff-message.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/g/groff-message.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,39 @@ +Tag: groff-message +Severity: warning +Check: documentation/manual +Renamed-From: manpage-has-errors-from-man +Info: A manual page provoked warnings or errors from the man + program. Here are some common ones: + . + "cannot adjust" or "can't break" are issues with paragraph filling. They + are usually related to long lines. Justifying text on the left hand side + can help with adjustments. Hyphenation can help with breaks. + . + For more information, please see "Manipulating Filling and Adjusting" + and "Manipulating Hyphenation" in the Groff manual (see info groff). + . + "can't find numbered character" usually means that the input was in a + national legacy encoding. The warning means that some characters were + dropped. Please use escapes such as \[:a] as described on the + groff_char manual page. + . + Other common warnings are formatting typos. String arguments to + .IP require quotes. Usually, some text is lost or mangled. See + the groff_man (or groff_mdoc if using mdoc) + manual page for details on macros. + . + The check for manual pages uses the --warnings option to + man to catch common problems, like a . or a ' + at the beginning of a line as literal text. They are interpreted as + Groff commands. Just reformat the paragraph so the characters are not at + the beginning of a line. You can also add a zero-width space (\&) + in front of them. + . + Aside from overrides, warnings can be disabled with the .warn + directive. Please see "Debugging" in the Groff manual. + . + You can see the warnings yourself by running the command used by Lintian: + . + LC_ALL=en_US.UTF-8 MANROFFSEQ='' MANWIDTH=80 \ + man --warnings -E UTF-8 -l -Tutf8 -Z <file> >/dev/null +Ref: groff_man(7), groff_mdoc(7) diff -Nru lintian-2.93.0/tags/g/groff-message.tag lintian-2.89.0ubuntu1/tags/g/groff-message.tag --- lintian-2.93.0/tags/g/groff-message.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/g/groff-message.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,39 +0,0 @@ -Tag: groff-message -Severity: warning -Check: documentation/manual -Renamed-From: manpage-has-errors-from-man -Explanation: A manual page provoked warnings or errors from the man - program. Here are some common ones: - . - "cannot adjust" or "can't break" are issues with paragraph filling. They - are usually related to long lines. Justifying text on the left hand side - can help with adjustments. Hyphenation can help with breaks. - . - For more information, please see "Manipulating Filling and Adjusting" - and "Manipulating Hyphenation" in the Groff manual (see info groff). - . - "can't find numbered character" usually means that the input was in a - national legacy encoding. The warning means that some characters were - dropped. Please use escapes such as \[:a] as described on the - groff_char manual page. - . - Other common warnings are formatting typos. String arguments to - .IP require quotes. Usually, some text is lost or mangled. See - the groff_man (or groff_mdoc if using mdoc) - manual page for details on macros. - . - The check for manual pages uses the --warnings option to - man to catch common problems, like a . or a ' - at the beginning of a line as literal text. They are interpreted as - Groff commands. Just reformat the paragraph so the characters are not at - the beginning of a line. You can also add a zero-width space (\&) - in front of them. - . - Aside from overrides, warnings can be disabled with the .warn - directive. Please see "Debugging" in the Groff manual. - . - You can see the warnings yourself by running the command used by Lintian: - . - LC_ALL=en_US.UTF-8 MANROFFSEQ='' MANWIDTH=80 \ - man --warnings -E UTF-8 -l -Tutf8 -Z <file> >/dev/null -See-Also: groff_man(7), groff_mdoc(7) diff -Nru lintian-2.93.0/tags/g/gzip-file-is-not-multi-arch-same-safe.desc lintian-2.89.0ubuntu1/tags/g/gzip-file-is-not-multi-arch-same-safe.desc --- lintian-2.93.0/tags/g/gzip-file-is-not-multi-arch-same-safe.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/g/gzip-file-is-not-multi-arch-same-safe.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: gzip-file-is-not-multi-arch-same-safe +Severity: error +Check: files/compressed/gz +Info: The gzip file contains a timestamp that will differ between + architectures. Multi-Arch: same implies all shared files must be + byte-for-byte identical. + . + This can usually be fixed by passing -n to gzip. diff -Nru lintian-2.93.0/tags/g/gzip-file-is-not-multi-arch-same-safe.tag lintian-2.89.0ubuntu1/tags/g/gzip-file-is-not-multi-arch-same-safe.tag --- lintian-2.93.0/tags/g/gzip-file-is-not-multi-arch-same-safe.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/g/gzip-file-is-not-multi-arch-same-safe.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: gzip-file-is-not-multi-arch-same-safe -Severity: error -Check: files/compressed/gz -Explanation: The gzip file contains a timestamp that will differ between - architectures. Multi-Arch: same implies all shared files must be - byte-for-byte identical. - . - This can usually be fixed by passing -n to gzip. diff -Nru lintian-2.93.0/tags/h/hardening-no-bindnow.desc lintian-2.89.0ubuntu1/tags/h/hardening-no-bindnow.desc --- lintian-2.93.0/tags/h/hardening-no-bindnow.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/h/hardening-no-bindnow.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,17 @@ +Tag: hardening-no-bindnow +Severity: info +Check: binaries +Info: This package provides an ELF binary that lacks the "bindnow" + linker flag. + . + This is needed (together with "relro") to make the "Global Offset + Table" (GOT) fully read-only. The bindnow feature trades startup + time for improved security. Please consider enabling this feature + or consider overriding the tag (possibly with a comment about why). + . + If you use dpkg-buildflags, you may have to add + hardening=+bindnow or hardening=+all to + DEB_BUILD_MAINT_OPTIONS. + . + The relevant compiler flags are set in LDFLAGS. +Ref: https://wiki.debian.org/Hardening diff -Nru lintian-2.93.0/tags/h/hardening-no-bindnow.tag lintian-2.89.0ubuntu1/tags/h/hardening-no-bindnow.tag --- lintian-2.93.0/tags/h/hardening-no-bindnow.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/h/hardening-no-bindnow.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,17 +0,0 @@ -Tag: hardening-no-bindnow -Severity: info -Check: binaries -Explanation: This package provides an ELF binary that lacks the "bindnow" - linker flag. - . - This is needed (together with "relro") to make the "Global Offset - Table" (GOT) fully read-only. The bindnow feature trades startup - time for improved security. Please consider enabling this feature - or consider overriding the tag (possibly with a comment about why). - . - If you use dpkg-buildflags, you may have to add - hardening=+bindnow or hardening=+all to - DEB_BUILD_MAINT_OPTIONS. - . - The relevant compiler flags are set in LDFLAGS. -See-Also: https://wiki.debian.org/Hardening diff -Nru lintian-2.93.0/tags/h/hardening-no-fortify-functions.desc lintian-2.89.0ubuntu1/tags/h/hardening-no-fortify-functions.desc --- lintian-2.93.0/tags/h/hardening-no-fortify-functions.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/h/hardening-no-fortify-functions.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,14 @@ +Tag: hardening-no-fortify-functions +Severity: info +Certainty: wild-guess +Check: binaries +Info: This package provides an ELF binary that lacks the use of fortified + libc functions. Either there are no potentially unfortified functions + called by any routines, all unfortified calls have already been fully + validated at compile-time, or the package was not built with the default + Debian compiler flags defined by dpkg-buildflags. If built using + dpkg-buildflags directly, be sure to import CPPFLAGS. + . + NB: Due to false-positives, Lintian ignores some unprotected functions + (e.g. memcpy). +Ref: https://wiki.debian.org/Hardening, #673112 diff -Nru lintian-2.93.0/tags/h/hardening-no-fortify-functions.tag lintian-2.89.0ubuntu1/tags/h/hardening-no-fortify-functions.tag --- lintian-2.93.0/tags/h/hardening-no-fortify-functions.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/h/hardening-no-fortify-functions.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,13 +0,0 @@ -Tag: hardening-no-fortify-functions -Severity: info -Check: binaries -Explanation: This package provides an ELF binary that lacks the use of fortified - libc functions. Either there are no potentially unfortified functions - called by any routines, all unfortified calls have already been fully - validated at compile-time, or the package was not built with the default - Debian compiler flags defined by dpkg-buildflags. If built using - dpkg-buildflags directly, be sure to import CPPFLAGS. - . - NB: Due to false-positives, Lintian ignores some unprotected functions - (e.g. memcpy). -See-Also: https://wiki.debian.org/Hardening, Bug#673112 diff -Nru lintian-2.93.0/tags/h/hardening-no-pie.desc lintian-2.89.0ubuntu1/tags/h/hardening-no-pie.desc --- lintian-2.93.0/tags/h/hardening-no-pie.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/h/hardening-no-pie.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,23 @@ +Tag: hardening-no-pie +Severity: warning +Check: binaries +Info: This package provides an ELF executable that was not compiled + as a position independent executable (PIE). + . + In Debian, since version 6.2.0-7 of the gcc-6 package GCC will + compile ELF binaries with PIE by default. In most cases a simple + rebuild will be sufficient to remove this tag. + . + PIE is required for fully enabling Address Space Layout + Randomization (ASLR), which makes "Return-oriented" attacks more + difficult. + . + Historically, PIE has been associated with noticeable performance + overhead on i386. However, GCC >= 5 has implemented an optimization + that can reduce the overhead significantly. + . + If you use dpkg-buildflags with hardening=+all,-pie + in DEB_BUILD_MAINT_OPTIONS, remove the -pie. +Ref: https://wiki.debian.org/Hardening, + https://gcc.gnu.org/gcc-5/changes.html, + https://software.intel.com/en-us/blogs/2014/12/26/new-optimizations-for-x86-in-upcoming-gcc-50-32bit-pic-mode diff -Nru lintian-2.93.0/tags/h/hardening-no-pie.tag lintian-2.89.0ubuntu1/tags/h/hardening-no-pie.tag --- lintian-2.93.0/tags/h/hardening-no-pie.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/h/hardening-no-pie.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,23 +0,0 @@ -Tag: hardening-no-pie -Severity: warning -Check: binaries -Explanation: This package provides an ELF executable that was not compiled - as a position independent executable (PIE). - . - In Debian, since version 6.2.0-7 of the gcc-6 package GCC will - compile ELF binaries with PIE by default. In most cases a simple - rebuild will be sufficient to remove this tag. - . - PIE is required for fully enabling Address Space Layout - Randomization (ASLR), which makes "Return-oriented" attacks more - difficult. - . - Historically, PIE has been associated with noticeable performance - overhead on i386. However, GCC >= 5 has implemented an optimization - that can reduce the overhead significantly. - . - If you use dpkg-buildflags with hardening=+all,-pie - in DEB_BUILD_MAINT_OPTIONS, remove the -pie. -See-Also: https://wiki.debian.org/Hardening, - https://gcc.gnu.org/gcc-5/changes.html, - https://software.intel.com/en-us/blogs/2014/12/26/new-optimizations-for-x86-in-upcoming-gcc-50-32bit-pic-mode diff -Nru lintian-2.93.0/tags/h/hardening-no-relro.desc lintian-2.89.0ubuntu1/tags/h/hardening-no-relro.desc --- lintian-2.93.0/tags/h/hardening-no-relro.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/h/hardening-no-relro.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: hardening-no-relro +Severity: warning +Check: binaries +Info: This package provides an ELF binary that lacks the "read-only + relocation" link flag. This package was likely not built with the + default Debian compiler flags defined by dpkg-buildflags. + If built using dpkg-buildflags directly, be sure to import + LDFLAGS. +Ref: https://wiki.debian.org/Hardening diff -Nru lintian-2.93.0/tags/h/hardening-no-relro.tag lintian-2.89.0ubuntu1/tags/h/hardening-no-relro.tag --- lintian-2.93.0/tags/h/hardening-no-relro.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/h/hardening-no-relro.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: hardening-no-relro -Severity: warning -Check: binaries -Explanation: This package provides an ELF binary that lacks the "read-only - relocation" link flag. This package was likely not built with the - default Debian compiler flags defined by dpkg-buildflags. - If built using dpkg-buildflags directly, be sure to import - LDFLAGS. -See-Also: https://wiki.debian.org/Hardening diff -Nru lintian-2.93.0/tags/h/header-has-overly-generic-name.desc lintian-2.89.0ubuntu1/tags/h/header-has-overly-generic-name.desc --- lintian-2.93.0/tags/h/header-has-overly-generic-name.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/h/header-has-overly-generic-name.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: header-has-overly-generic-name +Severity: error +Check: files/includes +Info: This package installs a header to the /usr/include global + namespace with an overly generic name. + . + This was either a mistake and/or likely to cause conflicts with other + packages. diff -Nru lintian-2.93.0/tags/h/header-has-overly-generic-name.tag lintian-2.89.0ubuntu1/tags/h/header-has-overly-generic-name.tag --- lintian-2.93.0/tags/h/header-has-overly-generic-name.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/h/header-has-overly-generic-name.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: header-has-overly-generic-name -Severity: error -Check: files/includes -Explanation: This package installs a header to the /usr/include global - namespace with an overly generic name. - . - This was either a mistake and/or likely to cause conflicts with other - packages. diff -Nru lintian-2.93.0/tags/h/helper-templates-in-copyright.desc lintian-2.89.0ubuntu1/tags/h/helper-templates-in-copyright.desc --- lintian-2.93.0/tags/h/helper-templates-in-copyright.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/h/helper-templates-in-copyright.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: helper-templates-in-copyright +Severity: error +Check: debian/copyright +Info: The /usr/share/doc/pkg/copyright file still contains + template markers from a packaging helper. Please fill in the actual + license, upstream copyright holders, and download information about the + package and remove any remaining templates generated by the packaging + helper. diff -Nru lintian-2.93.0/tags/h/helper-templates-in-copyright.tag lintian-2.89.0ubuntu1/tags/h/helper-templates-in-copyright.tag --- lintian-2.93.0/tags/h/helper-templates-in-copyright.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/h/helper-templates-in-copyright.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: helper-templates-in-copyright -Severity: error -Check: debian/copyright -Explanation: The /usr/share/doc/*pkg*/copyright file still contains - template markers from a packaging helper. Please fill in the actual - license, upstream copyright holders, and download information about the - package and remove any remaining templates generated by the packaging - helper. diff -Nru lintian-2.93.0/tags/h/homepage-field-uses-insecure-uri.desc lintian-2.89.0ubuntu1/tags/h/homepage-field-uses-insecure-uri.desc --- lintian-2.93.0/tags/h/homepage-field-uses-insecure-uri.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/h/homepage-field-uses-insecure-uri.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,5 @@ +Tag: homepage-field-uses-insecure-uri +Severity: pedantic +Check: fields/homepage +Info: The Homepage field uses an unencrypted transport protocol for the + URI. diff -Nru lintian-2.93.0/tags/h/homepage-field-uses-insecure-uri.tag lintian-2.89.0ubuntu1/tags/h/homepage-field-uses-insecure-uri.tag --- lintian-2.93.0/tags/h/homepage-field-uses-insecure-uri.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/h/homepage-field-uses-insecure-uri.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,5 +0,0 @@ -Tag: homepage-field-uses-insecure-uri -Severity: pedantic -Check: fields/homepage -Explanation: The Homepage field uses an unencrypted transport protocol for the - URI. diff -Nru lintian-2.93.0/tags/h/homepage-for-bioconductor-package-not-canonical.desc lintian-2.89.0ubuntu1/tags/h/homepage-for-bioconductor-package-not-canonical.desc --- lintian-2.93.0/tags/h/homepage-for-bioconductor-package-not-canonical.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/h/homepage-for-bioconductor-package-not-canonical.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,14 @@ +Tag: homepage-for-bioconductor-package-not-canonical +Severity: info +Check: fields/homepage +Info: The Homepage field for this package points to an uncanonical Bioconductor URL. + Please update to use the current canonical URL instead. The canonical URL is + recommended for use in publications, etc., will always redirect to current + release version (or devel if package is not in release yet). For example, the + link for the package "foo" should be: + . + https://bioconductor.org/packages/foo/ + . + not: + . + https://www.bioconductor.org/packages/(release|devel|*)/bioc/html/foo.html diff -Nru lintian-2.93.0/tags/h/homepage-for-bioconductor-package-not-canonical.tag lintian-2.89.0ubuntu1/tags/h/homepage-for-bioconductor-package-not-canonical.tag --- lintian-2.93.0/tags/h/homepage-for-bioconductor-package-not-canonical.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/h/homepage-for-bioconductor-package-not-canonical.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,14 +0,0 @@ -Tag: homepage-for-bioconductor-package-not-canonical -Severity: info -Check: fields/homepage -Explanation: The Homepage field for this package points to an uncanonical Bioconductor URL. - Please update to use the current canonical URL instead. The canonical URL is - recommended for use in publications, etc., will always redirect to current - release version (or devel if package is not in release yet). For example, the - link for the package "foo" should be: - . - https://bioconductor.org/packages/foo/ - . - not: - . - https://www.bioconductor.org/packages/(release|devel|*)/bioc/html/foo.html diff -Nru lintian-2.93.0/tags/h/homepage-for-cpan-package-contains-version.desc lintian-2.89.0ubuntu1/tags/h/homepage-for-cpan-package-contains-version.desc --- lintian-2.93.0/tags/h/homepage-for-cpan-package-contains-version.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/h/homepage-for-cpan-package-contains-version.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,17 @@ +Tag: homepage-for-cpan-package-contains-version +Severity: warning +Check: fields/homepage +Info: The Homepage field for this package points to CPAN and the URL + includes the version. It's better to link to the unversioned CPAN page + so that the URL doesn't have to be updated for each new release. For + example, use: + . + http://search.cpan.org/dist/HTML-Template/ + . + or + . + https://metacpan.org/release/HTML-Template/ + . + not: + . + http://search.cpan.org/~samtregar/HTML-Template-2.9/ diff -Nru lintian-2.93.0/tags/h/homepage-for-cpan-package-contains-version.tag lintian-2.89.0ubuntu1/tags/h/homepage-for-cpan-package-contains-version.tag --- lintian-2.93.0/tags/h/homepage-for-cpan-package-contains-version.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/h/homepage-for-cpan-package-contains-version.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,17 +0,0 @@ -Tag: homepage-for-cpan-package-contains-version -Severity: warning -Check: fields/homepage -Explanation: The Homepage field for this package points to CPAN and the URL - includes the version. It's better to link to the unversioned CPAN page - so that the URL doesn't have to be updated for each new release. For - example, use: - . - http://search.cpan.org/dist/HTML-Template/ - . - or - . - https://metacpan.org/release/HTML-Template/ - . - not: - . - http://search.cpan.org/~samtregar/HTML-Template-2.9/ diff -Nru lintian-2.93.0/tags/h/homepage-for-cran-package-not-canonical.desc lintian-2.89.0ubuntu1/tags/h/homepage-for-cran-package-not-canonical.desc --- lintian-2.93.0/tags/h/homepage-for-cran-package-not-canonical.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/h/homepage-for-cran-package-not-canonical.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,14 @@ +Tag: homepage-for-cran-package-not-canonical +Severity: info +Check: fields/homepage +Info: The Homepage field for this package points to an uncanonical CRAN URL. + Please update to use the current canonical URL instead. The canonical URL is + recommended for use in publications, etc., will always redirect to current + release version (or devel if package is not in release yet). For example, the + link for the package "foo" should be: + . + https://cran.r-project.org/package=foo + . + not: + . + https://cran.r-project.org/web/packages/foo/index.html diff -Nru lintian-2.93.0/tags/h/homepage-for-cran-package-not-canonical.tag lintian-2.89.0ubuntu1/tags/h/homepage-for-cran-package-not-canonical.tag --- lintian-2.93.0/tags/h/homepage-for-cran-package-not-canonical.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/h/homepage-for-cran-package-not-canonical.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,14 +0,0 @@ -Tag: homepage-for-cran-package-not-canonical -Severity: info -Check: fields/homepage -Explanation: The Homepage field for this package points to an uncanonical CRAN URL. - Please update to use the current canonical URL instead. The canonical URL is - recommended for use in publications, etc., will always redirect to current - release version (or devel if package is not in release yet). For example, the - link for the package "foo" should be: - . - https://cran.r-project.org/package=foo - . - not: - . - https://cran.r-project.org/web/packages/foo/index.html diff -Nru lintian-2.93.0/tags/h/homepage-in-binary-package.desc lintian-2.89.0ubuntu1/tags/h/homepage-in-binary-package.desc --- lintian-2.93.0/tags/h/homepage-in-binary-package.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/h/homepage-in-binary-package.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,14 @@ +Tag: homepage-in-binary-package +Severity: info +Certainty: possible +Check: fields/homepage +Info: This non-native source package produces at least one binary package + with a Homepage field. However, the source package itself has + no Homepage field. Unfortunately, this results in some + source-based tools/services (e.g. the PTS) not linking to the homepage + of the upstream project. + . + If you move the Homepage field to the source paragraph in + debian/control then all binary packages from this source + will inherit the value by default. +Ref: policy 5.6.23 diff -Nru lintian-2.93.0/tags/h/homepage-in-binary-package.tag lintian-2.89.0ubuntu1/tags/h/homepage-in-binary-package.tag --- lintian-2.93.0/tags/h/homepage-in-binary-package.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/h/homepage-in-binary-package.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,13 +0,0 @@ -Tag: homepage-in-binary-package -Severity: info -Check: fields/homepage -Explanation: This non-native source package produces at least one binary package - with a Homepage field. However, the source package itself has - no Homepage field. Unfortunately, this results in some - source-based tools/services (e.g. the PTS) not linking to the homepage - of the upstream project. - . - If you move the Homepage field to the source paragraph in - debian/control then all binary packages from this source - will inherit the value by default. -See-Also: policy 5.6.23 diff -Nru lintian-2.93.0/tags/h/homepage-refers-to-filesystem-listing.desc lintian-2.89.0ubuntu1/tags/h/homepage-refers-to-filesystem-listing.desc --- lintian-2.93.0/tags/h/homepage-refers-to-filesystem-listing.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/h/homepage-refers-to-filesystem-listing.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: homepage-refers-to-filesystem-listing +Severity: info +Check: fields/homepage +Info: The Homepage field for this package points to a + download directory / filesystem listing. + . + Please update the field to point to the project's regular homepage. diff -Nru lintian-2.93.0/tags/h/homepage-refers-to-filesystem-listing.tag lintian-2.89.0ubuntu1/tags/h/homepage-refers-to-filesystem-listing.tag --- lintian-2.93.0/tags/h/homepage-refers-to-filesystem-listing.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/h/homepage-refers-to-filesystem-listing.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: homepage-refers-to-filesystem-listing -Severity: info -Check: fields/homepage -Explanation: The Homepage field for this package points to a - download directory / filesystem listing. - . - Please update the field to point to the project's regular homepage. diff -Nru lintian-2.93.0/tags/h/homepage-refers-to-obsolete-debian-infrastructure.desc lintian-2.89.0ubuntu1/tags/h/homepage-refers-to-obsolete-debian-infrastructure.desc --- lintian-2.93.0/tags/h/homepage-refers-to-obsolete-debian-infrastructure.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/h/homepage-refers-to-obsolete-debian-infrastructure.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,13 @@ +Tag: homepage-refers-to-obsolete-debian-infrastructure +Severity: warning +Check: fields/homepage +Info: The Homepage field for this package points to an area + within the *.debian.org infrastructure that has been deprecated. + . + After 1st May 2018, the Alioth service became read-only in May 2018. + Packages should migrate to website hosting on https://salsa.debian.org. + . + For further information about salsa.debian.org, including how to add + HTTP redirects from alioth, please consult the Debian Wiki. +Ref: https://lists.debian.org/debian-devel-announce/2017/08/msg00008.html, + https://wiki.debian.org/Salsa diff -Nru lintian-2.93.0/tags/h/homepage-refers-to-obsolete-debian-infrastructure.tag lintian-2.89.0ubuntu1/tags/h/homepage-refers-to-obsolete-debian-infrastructure.tag --- lintian-2.93.0/tags/h/homepage-refers-to-obsolete-debian-infrastructure.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/h/homepage-refers-to-obsolete-debian-infrastructure.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,13 +0,0 @@ -Tag: homepage-refers-to-obsolete-debian-infrastructure -Severity: warning -Check: fields/homepage -Explanation: The Homepage field for this package points to an area - within the *.debian.org infrastructure that has been deprecated. - . - After 1st May 2018, the Alioth service became read-only in May 2018. - Packages should migrate to website hosting on https://salsa.debian.org. - . - For further information about salsa.debian.org, including how to add - HTTP redirects from alioth, please consult the Debian Wiki. -See-Also: https://lists.debian.org/debian-devel-announce/2017/08/msg00008.html, - https://wiki.debian.org/Salsa diff -Nru lintian-2.93.0/tags/h/html-changelog-without-text-version.desc lintian-2.89.0ubuntu1/tags/h/html-changelog-without-text-version.desc --- lintian-2.93.0/tags/h/html-changelog-without-text-version.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/h/html-changelog-without-text-version.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: html-changelog-without-text-version +Severity: error +Check: debian/changelog +Info: If the upstream changelog file is HTML formatted, a text version + should also be accessible as "changelog.gz". (This can be created by + "lynx -dump -nolist") +Ref: policy 12.7 diff -Nru lintian-2.93.0/tags/h/html-changelog-without-text-version.tag lintian-2.89.0ubuntu1/tags/h/html-changelog-without-text-version.tag --- lintian-2.93.0/tags/h/html-changelog-without-text-version.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/h/html-changelog-without-text-version.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: html-changelog-without-text-version -Severity: error -Check: debian/changelog -Explanation: If the upstream changelog file is HTML formatted, a text version - should also be accessible as "changelog.gz". (This can be created by - "lynx -dump -nolist") -See-Also: policy 12.7 diff -Nru lintian-2.93.0/tags/h/hyphen-file.desc lintian-2.89.0ubuntu1/tags/h/hyphen-file.desc --- lintian-2.93.0/tags/h/hyphen-file.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/h/hyphen-file.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: hyphen-file +Severity: error +Certainty: possible +Check: files/names +Info: The given file is literally installed as - (hyphen + symbol). Normally this indicates a mistake in the package when + attempting to write to standard output. +Ref: #882638 diff -Nru lintian-2.93.0/tags/h/hyphen-file.tag lintian-2.89.0ubuntu1/tags/h/hyphen-file.tag --- lintian-2.93.0/tags/h/hyphen-file.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/h/hyphen-file.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: hyphen-file -Severity: error -Check: files/names -Explanation: The given file is literally installed as - (hyphen - symbol). Normally this indicates a mistake in the package when - attempting to write to standard output. -See-Also: Bug#882638 diff -Nru lintian-2.93.0/tags/h/hyphen-in-upstream-part-of-debian-changelog-version.desc lintian-2.89.0ubuntu1/tags/h/hyphen-in-upstream-part-of-debian-changelog-version.desc --- lintian-2.93.0/tags/h/hyphen-in-upstream-part-of-debian-changelog-version.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/h/hyphen-in-upstream-part-of-debian-changelog-version.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: hyphen-in-upstream-part-of-debian-changelog-version +Severity: pedantic +Check: debian/changelog +Info: The upstream version in the debian changelog contains one or more + hyphens. While that is okay according to Debian Policy, some tools may + croak. +Ref: policy 5.6.12 diff -Nru lintian-2.93.0/tags/h/hyphen-in-upstream-part-of-debian-changelog-version.tag lintian-2.89.0ubuntu1/tags/h/hyphen-in-upstream-part-of-debian-changelog-version.tag --- lintian-2.93.0/tags/h/hyphen-in-upstream-part-of-debian-changelog-version.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/h/hyphen-in-upstream-part-of-debian-changelog-version.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: hyphen-in-upstream-part-of-debian-changelog-version -Severity: pedantic -Check: debian/changelog -Explanation: The upstream version in the debian changelog contains one or more - hyphens. While that is okay according to Debian Policy, some tools may - croak. -See-Also: policy 5.6.12 diff -Nru lintian-2.93.0/tags/i/icon-size-and-directory-name-mismatch.desc lintian-2.89.0ubuntu1/tags/i/icon-size-and-directory-name-mismatch.desc --- lintian-2.93.0/tags/i/icon-size-and-directory-name-mismatch.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/icon-size-and-directory-name-mismatch.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: icon-size-and-directory-name-mismatch +Severity: warning +Check: desktop/icons +Info: The icon has a size that differs from the size specified by the name + of the directory under which it was installed. The icon was probably + mistakenly installed into the wrong directory. diff -Nru lintian-2.93.0/tags/i/icon-size-and-directory-name-mismatch.tag lintian-2.89.0ubuntu1/tags/i/icon-size-and-directory-name-mismatch.tag --- lintian-2.93.0/tags/i/icon-size-and-directory-name-mismatch.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/icon-size-and-directory-name-mismatch.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: icon-size-and-directory-name-mismatch -Severity: warning -Check: desktop/icons -Explanation: The icon has a size that differs from the size specified by the name - of the directory under which it was installed. The icon was probably - mistakenly installed into the wrong directory. diff -Nru lintian-2.93.0/tags/i/illegal-multi-arch-value.desc lintian-2.89.0ubuntu1/tags/i/illegal-multi-arch-value.desc --- lintian-2.93.0/tags/i/illegal-multi-arch-value.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/illegal-multi-arch-value.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: illegal-multi-arch-value +Severity: error +Check: fields/multi-arch +Info: The package is architecture all and has the Multi-Arch same value. + . + This combination is not allowed by the Multi-Arch specification. +Ref: https://wiki.ubuntu.com/MultiarchSpec diff -Nru lintian-2.93.0/tags/i/illegal-multi-arch-value.tag lintian-2.89.0ubuntu1/tags/i/illegal-multi-arch-value.tag --- lintian-2.93.0/tags/i/illegal-multi-arch-value.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/illegal-multi-arch-value.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: illegal-multi-arch-value -Severity: error -Check: fields/multi-arch -Explanation: The package is architecture all and has the Multi-Arch same value. - . - This combination is not allowed by the Multi-Arch specification. -See-Also: https://wiki.ubuntu.com/MultiarchSpec diff -Nru lintian-2.93.0/tags/i/illegal-runtime-test-name.desc lintian-2.89.0ubuntu1/tags/i/illegal-runtime-test-name.desc --- lintian-2.93.0/tags/i/illegal-runtime-test-name.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/illegal-runtime-test-name.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: illegal-runtime-test-name +Severity: warning +Check: testsuite +Info: Runtime test names in debian/tests/control are only allowed to + contain decimal digits, lowercase ASCII letters, plus or minus signs, + dots or slashes. +Ref: https://salsa.debian.org/ci-team/autopkgtest/tree/master/doc/README.package-tests.rst diff -Nru lintian-2.93.0/tags/i/illegal-runtime-test-name.tag lintian-2.89.0ubuntu1/tags/i/illegal-runtime-test-name.tag --- lintian-2.93.0/tags/i/illegal-runtime-test-name.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/illegal-runtime-test-name.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: illegal-runtime-test-name -Severity: warning -Check: testsuite -Explanation: Runtime test names in debian/tests/control are only allowed to - contain decimal digits, lowercase ASCII letters, plus or minus signs, - dots or slashes. -See-Also: https://salsa.debian.org/ci-team/autopkgtest/tree/master/doc/README.package-tests.rst diff -Nru lintian-2.93.0/tags/i/image-file-has-conflicting-name.desc lintian-2.89.0ubuntu1/tags/i/image-file-has-conflicting-name.desc --- lintian-2.93.0/tags/i/image-file-has-conflicting-name.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/image-file-has-conflicting-name.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: image-file-has-conflicting-name +Severity: info +Check: images/filenames +Info: An image file in this package has a name that is + usually associated with another image format. +Ref: #717818 diff -Nru lintian-2.93.0/tags/i/image-file-has-conflicting-name.tag lintian-2.89.0ubuntu1/tags/i/image-file-has-conflicting-name.tag --- lintian-2.93.0/tags/i/image-file-has-conflicting-name.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/image-file-has-conflicting-name.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: image-file-has-conflicting-name -Severity: info -Check: images/filenames -Explanation: An image file in this package has a name that is - usually associated with another image format. -See-Also: Bug#717818 diff -Nru lintian-2.93.0/tags/i/image-file-has-unexpected-name.desc lintian-2.89.0ubuntu1/tags/i/image-file-has-unexpected-name.desc --- lintian-2.93.0/tags/i/image-file-has-unexpected-name.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/image-file-has-unexpected-name.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: image-file-has-unexpected-name +Severity: pedantic +Check: images/filenames +Info: An image file in this package has a name not generally + associated with its format. +Ref: #717818 diff -Nru lintian-2.93.0/tags/i/image-file-has-unexpected-name.tag lintian-2.89.0ubuntu1/tags/i/image-file-has-unexpected-name.tag --- lintian-2.93.0/tags/i/image-file-has-unexpected-name.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/image-file-has-unexpected-name.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: image-file-has-unexpected-name -Severity: pedantic -Check: images/filenames -Explanation: An image file in this package has a name not generally - associated with its format. -See-Also: Bug#717818 diff -Nru lintian-2.93.0/tags/i/image-file-in-usr-lib.desc lintian-2.89.0ubuntu1/tags/i/image-file-in-usr-lib.desc --- lintian-2.93.0/tags/i/image-file-in-usr-lib.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/image-file-in-usr-lib.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: image-file-in-usr-lib +Severity: pedantic +Check: images +Info: This package installs a pixmap or a bitmap within /usr/lib. + According to the Filesystem Hierarchy Standard, architecture-independent + files should be placed within /usr/share instead. diff -Nru lintian-2.93.0/tags/i/image-file-in-usr-lib.tag lintian-2.89.0ubuntu1/tags/i/image-file-in-usr-lib.tag --- lintian-2.93.0/tags/i/image-file-in-usr-lib.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/image-file-in-usr-lib.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: image-file-in-usr-lib -Severity: pedantic -Check: images -Explanation: This package installs a pixmap or a bitmap within /usr/lib. - According to the Filesystem Hierarchy Standard, architecture-independent - files should be placed within /usr/share instead. diff -Nru lintian-2.93.0/tags/i/improbable-bug-number-in-closes.desc lintian-2.89.0ubuntu1/tags/i/improbable-bug-number-in-closes.desc --- lintian-2.93.0/tags/i/improbable-bug-number-in-closes.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/improbable-bug-number-in-closes.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: improbable-bug-number-in-closes +Severity: warning +Certainty: possible +Check: debian/changelog +Info: The most recent changelog closes a low-numbered bug number. + While this is distantly possible, it's more likely a typo or a + placeholder value that mistakenly wasn't filled in. diff -Nru lintian-2.93.0/tags/i/improbable-bug-number-in-closes.tag lintian-2.89.0ubuntu1/tags/i/improbable-bug-number-in-closes.tag --- lintian-2.93.0/tags/i/improbable-bug-number-in-closes.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/improbable-bug-number-in-closes.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: improbable-bug-number-in-closes -Severity: warning -Check: debian/changelog -Explanation: The most recent changelog closes a low-numbered bug number. - While this is distantly possible, it's more likely a typo or a - placeholder value that mistakenly wasn't filled in. diff -Nru lintian-2.93.0/tags/i/incompatible-java-bytecode-format.desc lintian-2.89.0ubuntu1/tags/i/incompatible-java-bytecode-format.desc --- lintian-2.93.0/tags/i/incompatible-java-bytecode-format.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/incompatible-java-bytecode-format.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: incompatible-java-bytecode-format +Severity: warning +Certainty: possible +Check: languages/java +Info: The package contains Java class files with a minimum requirement on the + listed Java version. This Java version is not supported by the default JVM + in Debian and is therefore likely to be a mistake. +Ref: #673276 diff -Nru lintian-2.93.0/tags/i/incompatible-java-bytecode-format.tag lintian-2.89.0ubuntu1/tags/i/incompatible-java-bytecode-format.tag --- lintian-2.93.0/tags/i/incompatible-java-bytecode-format.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/incompatible-java-bytecode-format.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: incompatible-java-bytecode-format -Severity: warning -Check: languages/java -Explanation: The package contains Java class files with a minimum requirement on the - listed Java version. This Java version is not supported by the default JVM - in Debian and is therefore likely to be a mistake. -See-Also: Bug#673276 diff -Nru lintian-2.93.0/tags/i/incomplete-creative-commons-license.desc lintian-2.89.0ubuntu1/tags/i/incomplete-creative-commons-license.desc --- lintian-2.93.0/tags/i/incomplete-creative-commons-license.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/incomplete-creative-commons-license.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,24 @@ +Tag: incomplete-creative-commons-license +Severity: warning +Certainty: possible +Check: debian/copyright/dep5 +Info: The package appears to be licensed under a Creative Commons + license but only includes the human-readable summary in the + debian/copyright file which is not the actual licence. The Creative + Commons webpages contains the following disclaimer: + . + This deed highlights only some of the key features and terms of the + actual license. It is not a license and has no legal value. You should + carefully review all of the terms and conditions of the actual license + before using the licensed material. + . + Creative Commons is not a law firm and does not provide legal + services. Distributing, displaying, or linking to this deed or the + license that it summarizes does not create a lawyer-client or any + other relationship. + . + Please use the full, plain-text version of the license text which may + be found here: + . + https://creativecommons.org/2014/01/07/plaintext-versions-of-creative-commons-4-0-licenses/ +Ref: #903470, #795402 diff -Nru lintian-2.93.0/tags/i/incomplete-creative-commons-license.tag lintian-2.89.0ubuntu1/tags/i/incomplete-creative-commons-license.tag --- lintian-2.93.0/tags/i/incomplete-creative-commons-license.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/incomplete-creative-commons-license.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,23 +0,0 @@ -Tag: incomplete-creative-commons-license -Severity: warning -Check: debian/copyright/dep5 -Explanation: The package appears to be licensed under a Creative Commons - license but only includes the human-readable summary in the - debian/copyright file which is not the actual licence. The Creative - Commons webpages contains the following disclaimer: - . - This deed highlights only some of the key features and terms of the - actual license. It is not a license and has no legal value. You should - carefully review all of the terms and conditions of the actual license - before using the licensed material. - . - Creative Commons is not a law firm and does not provide legal - services. Distributing, displaying, or linking to this deed or the - license that it summarizes does not create a lawyer-client or any - other relationship. - . - Please use the full, plain-text version of the license text which may - be found here: - . - https://creativecommons.org/2014/01/07/plaintext-versions-of-creative-commons-4-0-licenses/ -See-Also: Bug#903470, Bug#795402 diff -Nru lintian-2.93.0/tags/i/inconsistent-appstream-metadata-license.desc lintian-2.89.0ubuntu1/tags/i/inconsistent-appstream-metadata-license.desc --- lintian-2.93.0/tags/i/inconsistent-appstream-metadata-license.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/inconsistent-appstream-metadata-license.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: inconsistent-appstream-metadata-license +Severity: warning +Certainty: possible +Check: debian/copyright/dep5 +Info: The specified AppStream metadata file specifies a + metadata_license field but this does not match the files in + debian/copyright. +Ref: https://wiki.debian.org/AppStream/Guidelines, + https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ diff -Nru lintian-2.93.0/tags/i/inconsistent-appstream-metadata-license.tag lintian-2.89.0ubuntu1/tags/i/inconsistent-appstream-metadata-license.tag --- lintian-2.93.0/tags/i/inconsistent-appstream-metadata-license.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/inconsistent-appstream-metadata-license.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: inconsistent-appstream-metadata-license -Severity: warning -Check: debian/copyright/dep5 -Explanation: The specified AppStream metadata file specifies a - metadata_license field but this does not match the files in - debian/copyright. -See-Also: https://wiki.debian.org/AppStream/Guidelines, - https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ diff -Nru lintian-2.93.0/tags/i/inconsistent-maintainer.desc lintian-2.89.0ubuntu1/tags/i/inconsistent-maintainer.desc --- lintian-2.93.0/tags/i/inconsistent-maintainer.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/inconsistent-maintainer.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: inconsistent-maintainer +Severity: error +Check: fields/maintainer +Info: The Maintainer address in a group of related processables is + inconsistent as indicated. + . + This sometimes happens when environmental variables like DEBEMAIL + are set to different values when building sources and changes separately. + Please use the same maintainer everywhere. +Ref: #546525, https://wiki.ubuntu.com/DebianMaintainerField, Ubuntu Bug#1862787 diff -Nru lintian-2.93.0/tags/i/inconsistent-maintainer.tag lintian-2.89.0ubuntu1/tags/i/inconsistent-maintainer.tag --- lintian-2.93.0/tags/i/inconsistent-maintainer.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/inconsistent-maintainer.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,10 +0,0 @@ -Tag: inconsistent-maintainer -Severity: error -Check: fields/maintainer -Explanation: The Maintainer address in a group of related processables is - inconsistent as indicated. - . - This sometimes happens when environmental variables like DEBEMAIL - are set to different values when building sources and changes separately. - Please use the same maintainer everywhere. -See-Also: Bug#546525, https://wiki.ubuntu.com/DebianMaintainerField, Ubuntu Bug#1862787 diff -Nru lintian-2.93.0/tags/i/incorrect-libdir-in-la-file.desc lintian-2.89.0ubuntu1/tags/i/incorrect-libdir-in-la-file.desc --- lintian-2.93.0/tags/i/incorrect-libdir-in-la-file.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/incorrect-libdir-in-la-file.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: incorrect-libdir-in-la-file +Severity: error +Certainty: possible +Check: shared-libs +Info: The given .la file points to a libdir other than the path where it is + installed. This can be caused by resetting prefix at make install + time instead of using DESTDIR. The incorrect path will cause + packages linking to this library using libtool to build incorrectly (adding + incorrect paths to RPATH, for example). diff -Nru lintian-2.93.0/tags/i/incorrect-libdir-in-la-file.tag lintian-2.89.0ubuntu1/tags/i/incorrect-libdir-in-la-file.tag --- lintian-2.93.0/tags/i/incorrect-libdir-in-la-file.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/incorrect-libdir-in-la-file.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: incorrect-libdir-in-la-file -Severity: error -Check: shared-libs -Explanation: The given .la file points to a libdir other than the path where it is - installed. This can be caused by resetting prefix at make install - time instead of using DESTDIR. The incorrect path will cause - packages linking to this library using libtool to build incorrectly (adding - incorrect paths to RPATH, for example). diff -Nru lintian-2.93.0/tags/i/incorrect-locale-code.desc lintian-2.89.0ubuntu1/tags/i/incorrect-locale-code.desc --- lintian-2.93.0/tags/i/incorrect-locale-code.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/incorrect-locale-code.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,16 @@ +Tag: incorrect-locale-code +Severity: warning +Certainty: possible +Check: files/locales +Info: The package appears to ship locales for a language but uses an + incorrect locale code as a subdirectory of /usr/share/locale. + This usually results in users of the intended target language not + finding the locale. The language codes used in the locale directories + are those from the ISO 639-1 and ISO 639-2 standards, not those + usually used as TLDs (which are from the ISO 3166 standard). + . + When both standards define a language code for a given language, the + ISO 639-1 code should be used (i.e. the two lettered code). + . + Lintian only knows about some commonly-mistaken set of incorrect + locale codes. diff -Nru lintian-2.93.0/tags/i/incorrect-locale-code.tag lintian-2.89.0ubuntu1/tags/i/incorrect-locale-code.tag --- lintian-2.93.0/tags/i/incorrect-locale-code.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/incorrect-locale-code.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,15 +0,0 @@ -Tag: incorrect-locale-code -Severity: warning -Check: files/locales -Explanation: The package appears to ship locales for a language but uses an - incorrect locale code as a subdirectory of /usr/share/locale. - This usually results in users of the intended target language not - finding the locale. The language codes used in the locale directories - are those from the ISO 639-1 and ISO 639-2 standards, not those - usually used as TLDs (which are from the ISO 3166 standard). - . - When both standards define a language code for a given language, the - ISO 639-1 code should be used (i.e. the two lettered code). - . - Lintian only knows about some commonly-mistaken set of incorrect - locale codes. diff -Nru lintian-2.93.0/tags/i/incorrect-naming-of-pkcs11-module.desc lintian-2.89.0ubuntu1/tags/i/incorrect-naming-of-pkcs11-module.desc --- lintian-2.93.0/tags/i/incorrect-naming-of-pkcs11-module.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/incorrect-naming-of-pkcs11-module.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,11 @@ +Tag: incorrect-naming-of-pkcs11-module +Severity: error +Check: files/p11-kit +Info: This package ships a PKCS#11 module configuration file under + /usr/share/p11-kit/modules, but its naming doesn't conform + to what p11-kit expects. Files in that directory should + respect the following convention, case insensitive: + [a-z0-9][a-z0-9_.-]*.module + . + p11-kit currently warns on every file that does not follow the + convention and may ignore them in the future. diff -Nru lintian-2.93.0/tags/i/incorrect-naming-of-pkcs11-module.tag lintian-2.89.0ubuntu1/tags/i/incorrect-naming-of-pkcs11-module.tag --- lintian-2.93.0/tags/i/incorrect-naming-of-pkcs11-module.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/incorrect-naming-of-pkcs11-module.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,11 +0,0 @@ -Tag: incorrect-naming-of-pkcs11-module -Severity: error -Check: files/p11-kit -Explanation: This package ships a PKCS#11 module configuration file under - /usr/share/p11-kit/modules, but its naming doesn't conform - to what p11-kit expects. Files in that directory should - respect the following convention, case insensitive: - [a-z0-9][a-z0-9_.-]*.module - . - p11-kit currently warns on every file that does not follow the - convention and may ignore them in the future. diff -Nru lintian-2.93.0/tags/i/incorrect-packaging-filename.desc lintian-2.89.0ubuntu1/tags/i/incorrect-packaging-filename.desc --- lintian-2.93.0/tags/i/incorrect-packaging-filename.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/incorrect-packaging-filename.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,16 @@ +Tag: incorrect-packaging-filename +Severity: warning +Check: debian/filenames +Info: Some packaging files obtain different names when they are copied + from source to installation packages. Debhelper sometimes adds *.Debian + extensions to NEWS, README and TODO files. That can be confusing. + . + Debhelper's behavior also depends on the filename. + . + This source package contains a file that debhelper will not find. The + file will not be included in your installation packages. Important + information, such as incompatibilties on upgrades, may not reach your + users. + . + Please rename the file as indicated. +Ref: #429510, #946126, #946041 diff -Nru lintian-2.93.0/tags/i/incorrect-packaging-filename.tag lintian-2.89.0ubuntu1/tags/i/incorrect-packaging-filename.tag --- lintian-2.93.0/tags/i/incorrect-packaging-filename.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/incorrect-packaging-filename.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,16 +0,0 @@ -Tag: incorrect-packaging-filename -Severity: warning -Check: debian/filenames -Explanation: Some packaging files obtain different names when they are copied - from source to installation packages. Debhelper sometimes adds *.Debian - extensions to NEWS, README and TODO files. That can be confusing. - . - Debhelper's behavior also depends on the filename. - . - This source package contains a file that debhelper will not find. The - file will not be included in your installation packages. Important - information, such as incompatibilties on upgrades, may not reach your - users. - . - Please rename the file as indicated. -See-Also: Bug#429510, Bug#946126, Bug#946041 diff -Nru lintian-2.93.0/tags/i/incorrect-path-for-interpreter.desc lintian-2.89.0ubuntu1/tags/i/incorrect-path-for-interpreter.desc --- lintian-2.93.0/tags/i/incorrect-path-for-interpreter.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/incorrect-path-for-interpreter.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,13 @@ +Tag: incorrect-path-for-interpreter +Severity: warning +Check: scripts +Info: The interpreter you used is installed at another location on Debian + systems. + . + Whilst the script may work, it is in violation of Debian Policy. This + may have been caused by usrmerge. + . + Note that, as a particular exception, Debian Policy § 10.4 states that + Perl scripts should use /usr/bin/perl directly and not + /usr/bin/env, etc. +Ref: policy 10.4, https://wiki.debian.org/UsrMerge diff -Nru lintian-2.93.0/tags/i/incorrect-path-for-interpreter.tag lintian-2.89.0ubuntu1/tags/i/incorrect-path-for-interpreter.tag --- lintian-2.93.0/tags/i/incorrect-path-for-interpreter.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/incorrect-path-for-interpreter.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,13 +0,0 @@ -Tag: incorrect-path-for-interpreter -Severity: warning -Check: scripts -Explanation: The interpreter you used is installed at another location on Debian - systems. - . - Whilst the script may work, it is in violation of Debian Policy. This - may have been caused by usrmerge. - . - Note that, as a particular exception, Debian Policy § 10.4 states that - Perl scripts should use /usr/bin/perl directly and not - /usr/bin/env, etc. -See-Also: policy 10.4, https://wiki.debian.org/UsrMerge diff -Nru lintian-2.93.0/tags/i/info-document-has-wrong-extension.desc lintian-2.89.0ubuntu1/tags/i/info-document-has-wrong-extension.desc --- lintian-2.93.0/tags/i/info-document-has-wrong-extension.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/info-document-has-wrong-extension.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,4 @@ +Tag: info-document-has-wrong-extension +Severity: warning +Check: documentation/texinfo +Info: The info document has an extension other than info*.gz. diff -Nru lintian-2.93.0/tags/i/info-document-has-wrong-extension.tag lintian-2.89.0ubuntu1/tags/i/info-document-has-wrong-extension.tag --- lintian-2.93.0/tags/i/info-document-has-wrong-extension.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/info-document-has-wrong-extension.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,4 +0,0 @@ -Tag: info-document-has-wrong-extension -Severity: warning -Check: documentation/texinfo -Explanation: The info document has an extension other than info*.gz. diff -Nru lintian-2.93.0/tags/i/info-document-missing-dir-entry.desc lintian-2.89.0ubuntu1/tags/i/info-document-missing-dir-entry.desc --- lintian-2.93.0/tags/i/info-document-missing-dir-entry.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/info-document-missing-dir-entry.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,16 @@ +Tag: info-document-missing-dir-entry +Severity: error +Check: documentation/texinfo +Info: This info document has no directory entry. This is text between + START-INFO-DIR-ENTRY and END-INFO-DIR-ENTRY lines which is copied into + the dir file in /usr/share/info by + install-info. The best solution is to add lines like: + . + @dircategory Software development + @direntry + * foo: (foo). Foo creator and editor + @end direntry + . + to the texinfo source so that the generated info file will contain an + appropriate entry. You will have to ensure that the build process builds + new info files rather than using ones built by upstream. diff -Nru lintian-2.93.0/tags/i/info-document-missing-dir-entry.tag lintian-2.89.0ubuntu1/tags/i/info-document-missing-dir-entry.tag --- lintian-2.93.0/tags/i/info-document-missing-dir-entry.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/info-document-missing-dir-entry.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,16 +0,0 @@ -Tag: info-document-missing-dir-entry -Severity: error -Check: documentation/texinfo -Explanation: This info document has no directory entry. This is text between - START-INFO-DIR-ENTRY and END-INFO-DIR-ENTRY lines which is copied into - the dir file in /usr/share/info by - install-info. The best solution is to add lines like: - . - @dircategory Software development - @direntry - * foo: (foo). Foo creator and editor - @end direntry - . - to the texinfo source so that the generated info file will contain an - appropriate entry. You will have to ensure that the build process builds - new info files rather than using ones built by upstream. diff -Nru lintian-2.93.0/tags/i/info-document-missing-dir-section.desc lintian-2.89.0ubuntu1/tags/i/info-document-missing-dir-section.desc --- lintian-2.93.0/tags/i/info-document-missing-dir-section.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/info-document-missing-dir-section.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,13 @@ +Tag: info-document-missing-dir-section +Severity: error +Check: documentation/texinfo +Info: This info document has no INFO-DIR-SECTION line. + install-info will be unable to determine the section into which + this info page should be put. The best solution is to add a line like: + . + @dircategory Software development + . + to the texinfo source so that the generated info file will contain a + section. See /usr/share/info/dir for sections to choose from. + You will have to ensure that the build process builds new info files + rather than using ones built by upstream. diff -Nru lintian-2.93.0/tags/i/info-document-missing-dir-section.tag lintian-2.89.0ubuntu1/tags/i/info-document-missing-dir-section.tag --- lintian-2.93.0/tags/i/info-document-missing-dir-section.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/info-document-missing-dir-section.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,13 +0,0 @@ -Tag: info-document-missing-dir-section -Severity: error -Check: documentation/texinfo -Explanation: This info document has no INFO-DIR-SECTION line. - install-info will be unable to determine the section into which - this info page should be put. The best solution is to add a line like: - . - @dircategory Software development - . - to the texinfo source so that the generated info file will contain a - section. See /usr/share/info/dir for sections to choose from. - You will have to ensure that the build process builds new info files - rather than using ones built by upstream. diff -Nru lintian-2.93.0/tags/i/info-document-missing-image-file.desc lintian-2.89.0ubuntu1/tags/i/info-document-missing-image-file.desc --- lintian-2.93.0/tags/i/info-document-missing-image-file.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/info-document-missing-image-file.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,19 @@ +Tag: info-document-missing-image-file +Severity: warning +Check: documentation/texinfo +Info: This info document contains an "[image]" but the image file it + specifies is missing. Texinfo @image{} becomes + . + [image src="filename.png"] + . + in the .info. Emacs 22 and up info + mode can display this in a GUI if filename.png is in + /usr/share/info or if the src gives a path to the file + elsewhere. + . + If you put an image file in /usr/share/info then please name + it like the document so as to avoid name clashes. Eg. foo.info might + call an image foo-example1.png. If upstream does not do this already + then it may be easier to sed the src="" to a path + elsewhere, perhaps to share with an HTML rendition under say + /usr/share/doc/foo/html/. diff -Nru lintian-2.93.0/tags/i/info-document-missing-image-file.tag lintian-2.89.0ubuntu1/tags/i/info-document-missing-image-file.tag --- lintian-2.93.0/tags/i/info-document-missing-image-file.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/info-document-missing-image-file.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,19 +0,0 @@ -Tag: info-document-missing-image-file -Severity: warning -Check: documentation/texinfo -Explanation: This info document contains an "[image]" but the image file it - specifies is missing. Texinfo @image{} becomes - . - [image src="filename.png"] - . - in the .info. Emacs 22 and up info - mode can display this in a GUI if filename.png is in - /usr/share/info or if the src gives a path to the file - elsewhere. - . - If you put an image file in /usr/share/info then please name - it like the document so as to avoid name clashes. Eg. foo.info might - call an image foo-example1.png. If upstream does not do this already - then it may be easier to sed the src="" to a path - elsewhere, perhaps to share with an HTML rendition under say - /usr/share/doc/foo/html/. diff -Nru lintian-2.93.0/tags/i/info-document-not-compressed.desc lintian-2.89.0ubuntu1/tags/i/info-document-not-compressed.desc --- lintian-2.93.0/tags/i/info-document-not-compressed.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/info-document-not-compressed.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,5 @@ +Tag: info-document-not-compressed +Severity: error +Check: documentation/texinfo +Info: Info documents should be compressed with gzip -9n. +Ref: policy 12.2 diff -Nru lintian-2.93.0/tags/i/info-document-not-compressed.tag lintian-2.89.0ubuntu1/tags/i/info-document-not-compressed.tag --- lintian-2.93.0/tags/i/info-document-not-compressed.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/info-document-not-compressed.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,5 +0,0 @@ -Tag: info-document-not-compressed -Severity: error -Check: documentation/texinfo -Explanation: Info documents should be compressed with gzip -9n. -See-Also: policy 12.2 diff -Nru lintian-2.93.0/tags/i/info-document-not-compressed-with-gzip.desc lintian-2.89.0ubuntu1/tags/i/info-document-not-compressed-with-gzip.desc --- lintian-2.93.0/tags/i/info-document-not-compressed-with-gzip.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/info-document-not-compressed-with-gzip.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: info-document-not-compressed-with-gzip +Severity: error +Check: documentation/texinfo +Info: Info documents should be compressed with gzip -9n. This + file ends in .gz but doesn't appear to be a gzip-compressed + file. +Ref: policy 12.2 diff -Nru lintian-2.93.0/tags/i/info-document-not-compressed-with-gzip.tag lintian-2.89.0ubuntu1/tags/i/info-document-not-compressed-with-gzip.tag --- lintian-2.93.0/tags/i/info-document-not-compressed-with-gzip.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/info-document-not-compressed-with-gzip.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: info-document-not-compressed-with-gzip -Severity: error -Check: documentation/texinfo -Explanation: Info documents should be compressed with gzip -9n. This - file ends in .gz but doesn't appear to be a gzip-compressed - file. -See-Also: policy 12.2 diff -Nru lintian-2.93.0/tags/i/info-document-not-compressed-with-max-compression.desc lintian-2.89.0ubuntu1/tags/i/info-document-not-compressed-with-max-compression.desc --- lintian-2.93.0/tags/i/info-document-not-compressed-with-max-compression.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/info-document-not-compressed-with-max-compression.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: info-document-not-compressed-with-max-compression +Severity: error +Check: documentation/texinfo +Info: Info documents should be compressed with gzip -9n. This + file is compressed with gzip, but without using maximum compression. +Ref: policy 12.2 diff -Nru lintian-2.93.0/tags/i/info-document-not-compressed-with-max-compression.tag lintian-2.89.0ubuntu1/tags/i/info-document-not-compressed-with-max-compression.tag --- lintian-2.93.0/tags/i/info-document-not-compressed-with-max-compression.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/info-document-not-compressed-with-max-compression.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: info-document-not-compressed-with-max-compression -Severity: error -Check: documentation/texinfo -Explanation: Info documents should be compressed with gzip -9n. This - file is compressed with gzip, but without using maximum compression. -See-Also: policy 12.2 diff -Nru lintian-2.93.0/tags/i/init.d-script-contains-skeleton-template-content.desc lintian-2.89.0ubuntu1/tags/i/init.d-script-contains-skeleton-template-content.desc --- lintian-2.93.0/tags/i/init.d-script-contains-skeleton-template-content.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/init.d-script-contains-skeleton-template-content.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: init.d-script-contains-skeleton-template-content +Severity: error +Check: init.d +Info: The given init script appears to contain content from the + /etc/init.d/skeleton example. + . + Please double-check the script and/or replace it with content suitable to + this binary package. diff -Nru lintian-2.93.0/tags/i/init.d-script-contains-skeleton-template-content.tag lintian-2.89.0ubuntu1/tags/i/init.d-script-contains-skeleton-template-content.tag --- lintian-2.93.0/tags/i/init.d-script-contains-skeleton-template-content.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/init.d-script-contains-skeleton-template-content.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: init.d-script-contains-skeleton-template-content -Severity: error -Check: init.d -Explanation: The given init script appears to contain content from the - /etc/init.d/skeleton example. - . - Please double-check the script and/or replace it with content suitable to - this binary package. diff -Nru lintian-2.93.0/tags/i/init.d-script-depends-on-all-virtual-facility.desc lintian-2.89.0ubuntu1/tags/i/init.d-script-depends-on-all-virtual-facility.desc --- lintian-2.93.0/tags/i/init.d-script-depends-on-all-virtual-facility.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/init.d-script-depends-on-all-virtual-facility.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: init.d-script-depends-on-all-virtual-facility +Severity: error +Certainty: possible +Check: init.d +Info: The given init script declares a dependency on the virtual + facility "$all". This virtual facility is reserved for very special + cases, that work specifically with init system. + . + Regular services should not use this facility. +Ref: https://wiki.debian.org/LSBInitScripts diff -Nru lintian-2.93.0/tags/i/init.d-script-depends-on-all-virtual-facility.tag lintian-2.89.0ubuntu1/tags/i/init.d-script-depends-on-all-virtual-facility.tag --- lintian-2.93.0/tags/i/init.d-script-depends-on-all-virtual-facility.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/init.d-script-depends-on-all-virtual-facility.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: init.d-script-depends-on-all-virtual-facility -Severity: error -Check: init.d -Explanation: The given init script declares a dependency on the virtual - facility "$all". This virtual facility is reserved for very special - cases, that work specifically with init system. - . - Regular services should not use this facility. -See-Also: https://wiki.debian.org/LSBInitScripts diff -Nru lintian-2.93.0/tags/i/init.d-script-depends-on-unknown-virtual-facility.desc lintian-2.89.0ubuntu1/tags/i/init.d-script-depends-on-unknown-virtual-facility.desc --- lintian-2.93.0/tags/i/init.d-script-depends-on-unknown-virtual-facility.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/init.d-script-depends-on-unknown-virtual-facility.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: init.d-script-depends-on-unknown-virtual-facility +Severity: error +Certainty: possible +Check: init.d +Info: The given init script declares a dependency on a virtual facility + that is not known to be provided by any init.d script in the archive. + If the dependency cannot be satisfied upon the package's + installation, insserv will refuse the activation of the init.d script. +Ref: https://wiki.debian.org/LSBInitScripts diff -Nru lintian-2.93.0/tags/i/init.d-script-depends-on-unknown-virtual-facility.tag lintian-2.89.0ubuntu1/tags/i/init.d-script-depends-on-unknown-virtual-facility.tag --- lintian-2.93.0/tags/i/init.d-script-depends-on-unknown-virtual-facility.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/init.d-script-depends-on-unknown-virtual-facility.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: init.d-script-depends-on-unknown-virtual-facility -Severity: error -Check: init.d -Explanation: The given init script declares a dependency on a virtual facility - that is not known to be provided by any init.d script in the archive. - If the dependency cannot be satisfied upon the package's - installation, insserv will refuse the activation of the init.d script. -See-Also: https://wiki.debian.org/LSBInitScripts diff -Nru lintian-2.93.0/tags/i/init.d-script-does-not-implement-required-option.desc lintian-2.89.0ubuntu1/tags/i/init.d-script-does-not-implement-required-option.desc --- lintian-2.93.0/tags/i/init.d-script-does-not-implement-required-option.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/init.d-script-does-not-implement-required-option.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: init.d-script-does-not-implement-required-option +Severity: error +Check: init.d +Ref: policy 9.3.2 +Info: The /etc/init.d scripts have to support the following + command line arguments: start, stop, restart, force-reload. diff -Nru lintian-2.93.0/tags/i/init.d-script-does-not-implement-required-option.tag lintian-2.89.0ubuntu1/tags/i/init.d-script-does-not-implement-required-option.tag --- lintian-2.93.0/tags/i/init.d-script-does-not-implement-required-option.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/init.d-script-does-not-implement-required-option.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: init.d-script-does-not-implement-required-option -Severity: error -Check: init.d -See-Also: policy 9.3.2 -Explanation: The /etc/init.d scripts have to support the following - command line arguments: start, stop, restart, force-reload. diff -Nru lintian-2.93.0/tags/i/init.d-script-does-not-implement-status-option.desc lintian-2.89.0ubuntu1/tags/i/init.d-script-does-not-implement-status-option.desc --- lintian-2.93.0/tags/i/init.d-script-does-not-implement-status-option.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/init.d-script-does-not-implement-status-option.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: init.d-script-does-not-implement-status-option +Severity: info +Check: init.d +Ref: https://wiki.debian.org/LSBInitScripts +Info: The specified /etc/init.d script does not implement the + status option. This is actually required by LSB, often + requested by users and will be required by the Debian Policy in + the future. diff -Nru lintian-2.93.0/tags/i/init.d-script-does-not-implement-status-option.tag lintian-2.89.0ubuntu1/tags/i/init.d-script-does-not-implement-status-option.tag --- lintian-2.93.0/tags/i/init.d-script-does-not-implement-status-option.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/init.d-script-does-not-implement-status-option.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: init.d-script-does-not-implement-status-option -Severity: info -Check: init.d -See-Also: https://wiki.debian.org/LSBInitScripts -Explanation: The specified /etc/init.d script does not implement the - status option. This is actually required by LSB, often - requested by users and will be required by the Debian Policy in - the future. diff -Nru lintian-2.93.0/tags/i/init.d-script-does-not-provide-itself.desc lintian-2.89.0ubuntu1/tags/i/init.d-script-does-not-provide-itself.desc --- lintian-2.93.0/tags/i/init.d-script-does-not-provide-itself.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/init.d-script-does-not-provide-itself.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: init.d-script-does-not-provide-itself +Severity: info +Certainty: possible +Check: init.d +Info: This /etc/init.d script indicates it provides one or + more facilities, but none of the provided facilities match the name of + the init script. In certain cases, it may be necessary to not follow + that convention, but normally init scripts should always provide a + facility matching the name of the init script. +Ref: https://wiki.debian.org/LSBInitScripts diff -Nru lintian-2.93.0/tags/i/init.d-script-does-not-provide-itself.tag lintian-2.89.0ubuntu1/tags/i/init.d-script-does-not-provide-itself.tag --- lintian-2.93.0/tags/i/init.d-script-does-not-provide-itself.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/init.d-script-does-not-provide-itself.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: init.d-script-does-not-provide-itself -Severity: info -Check: init.d -Explanation: This /etc/init.d script indicates it provides one or - more facilities, but none of the provided facilities match the name of - the init script. In certain cases, it may be necessary to not follow - that convention, but normally init scripts should always provide a - facility matching the name of the init script. -See-Also: https://wiki.debian.org/LSBInitScripts diff -Nru lintian-2.93.0/tags/i/init.d-script-does-not-source-init-functions.desc lintian-2.89.0ubuntu1/tags/i/init.d-script-does-not-source-init-functions.desc --- lintian-2.93.0/tags/i/init.d-script-does-not-source-init-functions.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/init.d-script-does-not-source-init-functions.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,11 @@ +Tag: init.d-script-does-not-source-init-functions +Severity: warning +Check: systemd +Info: The /etc/init.d script does not source + /lib/lsb/init-functions. The systemd package provides + /lib/lsb/init-functions.d/40-systemd to redirect + /etc/init.d/$script calls to systemctl. + . + Please add a line like this to your /etc/init.d script: + . + . /lib/lsb/init-functions diff -Nru lintian-2.93.0/tags/i/init.d-script-does-not-source-init-functions.tag lintian-2.89.0ubuntu1/tags/i/init.d-script-does-not-source-init-functions.tag --- lintian-2.93.0/tags/i/init.d-script-does-not-source-init-functions.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/init.d-script-does-not-source-init-functions.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,11 +0,0 @@ -Tag: init.d-script-does-not-source-init-functions -Severity: warning -Check: systemd -Explanation: The /etc/init.d script does not source - /lib/lsb/init-functions. The systemd package provides - /lib/lsb/init-functions.d/40-systemd to redirect - /etc/init.d/$script calls to systemctl. - . - Please add a line like this to your /etc/init.d script: - . - . /lib/lsb/init-functions diff -Nru lintian-2.93.0/tags/i/init.d-script-has-bad-lsb-line.desc lintian-2.89.0ubuntu1/tags/i/init.d-script-has-bad-lsb-line.desc --- lintian-2.93.0/tags/i/init.d-script-has-bad-lsb-line.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/init.d-script-has-bad-lsb-line.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: init.d-script-has-bad-lsb-line +Severity: warning +Check: init.d +Ref: https://wiki.debian.org/LSBInitScripts +Info: This line in the LSB keyword section of an /etc/init.d + script doesn't match the required formatting of that section. Note that + keyword settings must start with #, a single space, the keyword, + a colon, and some whitespace, followed by the value (if any). Only the + Description keyword allows continuation lines, and continuation lines + must begin with # and either a tab or two or more spaces. diff -Nru lintian-2.93.0/tags/i/init.d-script-has-bad-lsb-line.tag lintian-2.89.0ubuntu1/tags/i/init.d-script-has-bad-lsb-line.tag --- lintian-2.93.0/tags/i/init.d-script-has-bad-lsb-line.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/init.d-script-has-bad-lsb-line.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,10 +0,0 @@ -Tag: init.d-script-has-bad-lsb-line -Severity: warning -Check: init.d -See-Also: https://wiki.debian.org/LSBInitScripts -Explanation: This line in the LSB keyword section of an /etc/init.d - script doesn't match the required formatting of that section. Note that - keyword settings must start with #, a single space, the keyword, - a colon, and some whitespace, followed by the value (if any). Only the - Description keyword allows continuation lines, and continuation lines - must begin with # and either a tab or two or more spaces. diff -Nru lintian-2.93.0/tags/i/init.d-script-has-bad-start-runlevel.desc lintian-2.89.0ubuntu1/tags/i/init.d-script-has-bad-start-runlevel.desc --- lintian-2.93.0/tags/i/init.d-script-has-bad-start-runlevel.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/init.d-script-has-bad-start-runlevel.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: init.d-script-has-bad-start-runlevel +Severity: warning +Check: init.d +Ref: https://wiki.debian.org/LSBInitScripts +Info: The given runlevel specified in the Default-Start keyword of the LSB + keyword section of this /etc/init.d script isn't one of the + recognized standard runlevels (S, 0, 1, 2, 3, 4, 5, and 6). diff -Nru lintian-2.93.0/tags/i/init.d-script-has-bad-start-runlevel.tag lintian-2.89.0ubuntu1/tags/i/init.d-script-has-bad-start-runlevel.tag --- lintian-2.93.0/tags/i/init.d-script-has-bad-start-runlevel.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/init.d-script-has-bad-start-runlevel.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: init.d-script-has-bad-start-runlevel -Severity: warning -Check: init.d -See-Also: https://wiki.debian.org/LSBInitScripts -Explanation: The given runlevel specified in the Default-Start keyword of the LSB - keyword section of this /etc/init.d script isn't one of the - recognized standard runlevels (S, 0, 1, 2, 3, 4, 5, and 6). diff -Nru lintian-2.93.0/tags/i/init.d-script-has-bad-stop-runlevel.desc lintian-2.89.0ubuntu1/tags/i/init.d-script-has-bad-stop-runlevel.desc --- lintian-2.93.0/tags/i/init.d-script-has-bad-stop-runlevel.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/init.d-script-has-bad-stop-runlevel.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: init.d-script-has-bad-stop-runlevel +Severity: warning +Check: init.d +Ref: https://wiki.debian.org/LSBInitScripts +Info: The given runlevel specified in the Default-Stop keyword of the LSB + keyword section of this /etc/init.d script isn't one of the + recognized standard runlevels (0, 1, 2, 3, 4, 5, and 6). diff -Nru lintian-2.93.0/tags/i/init.d-script-has-bad-stop-runlevel.tag lintian-2.89.0ubuntu1/tags/i/init.d-script-has-bad-stop-runlevel.tag --- lintian-2.93.0/tags/i/init.d-script-has-bad-stop-runlevel.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/init.d-script-has-bad-stop-runlevel.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: init.d-script-has-bad-stop-runlevel -Severity: warning -Check: init.d -See-Also: https://wiki.debian.org/LSBInitScripts -Explanation: The given runlevel specified in the Default-Stop keyword of the LSB - keyword section of this /etc/init.d script isn't one of the - recognized standard runlevels (0, 1, 2, 3, 4, 5, and 6). diff -Nru lintian-2.93.0/tags/i/init.d-script-has-conflicting-start-stop.desc lintian-2.89.0ubuntu1/tags/i/init.d-script-has-conflicting-start-stop.desc --- lintian-2.93.0/tags/i/init.d-script-has-conflicting-start-stop.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/init.d-script-has-conflicting-start-stop.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: init.d-script-has-conflicting-start-stop +Severity: warning +Check: init.d +Ref: https://wiki.debian.org/LSBInitScripts +Info: The given runlevel was included in both the Default-Start and + Default-Stop keywords of the LSB keyword section of this + /etc/init.d script. Since it doesn't make sense to both start + and stop a service in the same runlevel, there is probably an error in + one or the other of these keywords. diff -Nru lintian-2.93.0/tags/i/init.d-script-has-conflicting-start-stop.tag lintian-2.89.0ubuntu1/tags/i/init.d-script-has-conflicting-start-stop.tag --- lintian-2.93.0/tags/i/init.d-script-has-conflicting-start-stop.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/init.d-script-has-conflicting-start-stop.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: init.d-script-has-conflicting-start-stop -Severity: warning -Check: init.d -See-Also: https://wiki.debian.org/LSBInitScripts -Explanation: The given runlevel was included in both the Default-Start and - Default-Stop keywords of the LSB keyword section of this - /etc/init.d script. Since it doesn't make sense to both start - and stop a service in the same runlevel, there is probably an error in - one or the other of these keywords. diff -Nru lintian-2.93.0/tags/i/init.d-script-has-duplicate-lsb-keyword.desc lintian-2.89.0ubuntu1/tags/i/init.d-script-has-duplicate-lsb-keyword.desc --- lintian-2.93.0/tags/i/init.d-script-has-duplicate-lsb-keyword.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/init.d-script-has-duplicate-lsb-keyword.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: init.d-script-has-duplicate-lsb-keyword +Severity: warning +Check: init.d +Ref: https://wiki.debian.org/LSBInitScripts +Info: The given keyword was set twice in the LSB keyword section in this + /etc/init.d script. This is probably a mistake; the behavior of + setting the same keyword twice is undefined. diff -Nru lintian-2.93.0/tags/i/init.d-script-has-duplicate-lsb-keyword.tag lintian-2.89.0ubuntu1/tags/i/init.d-script-has-duplicate-lsb-keyword.tag --- lintian-2.93.0/tags/i/init.d-script-has-duplicate-lsb-keyword.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/init.d-script-has-duplicate-lsb-keyword.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: init.d-script-has-duplicate-lsb-keyword -Severity: warning -Check: init.d -See-Also: https://wiki.debian.org/LSBInitScripts -Explanation: The given keyword was set twice in the LSB keyword section in this - /etc/init.d script. This is probably a mistake; the behavior of - setting the same keyword twice is undefined. diff -Nru lintian-2.93.0/tags/i/init.d-script-has-duplicate-lsb-section.desc lintian-2.89.0ubuntu1/tags/i/init.d-script-has-duplicate-lsb-section.desc --- lintian-2.93.0/tags/i/init.d-script-has-duplicate-lsb-section.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/init.d-script-has-duplicate-lsb-section.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: init.d-script-has-duplicate-lsb-section +Severity: error +Check: init.d +Ref: https://wiki.debian.org/LSBInitScripts +Info: This /etc/init.d script has more than one LSB keyword + section. These sections start with ### BEGIN INIT INFO and end + with ### END INIT INFO. There should be only one such section + per init script. diff -Nru lintian-2.93.0/tags/i/init.d-script-has-duplicate-lsb-section.tag lintian-2.89.0ubuntu1/tags/i/init.d-script-has-duplicate-lsb-section.tag --- lintian-2.93.0/tags/i/init.d-script-has-duplicate-lsb-section.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/init.d-script-has-duplicate-lsb-section.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: init.d-script-has-duplicate-lsb-section -Severity: error -Check: init.d -See-Also: https://wiki.debian.org/LSBInitScripts -Explanation: This /etc/init.d script has more than one LSB keyword - section. These sections start with ### BEGIN INIT INFO and end - with ### END INIT INFO. There should be only one such section - per init script. diff -Nru lintian-2.93.0/tags/i/init.d-script-has-unknown-lsb-keyword.desc lintian-2.89.0ubuntu1/tags/i/init.d-script-has-unknown-lsb-keyword.desc --- lintian-2.93.0/tags/i/init.d-script-has-unknown-lsb-keyword.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/init.d-script-has-unknown-lsb-keyword.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: init.d-script-has-unknown-lsb-keyword +Severity: warning +Check: init.d +Ref: https://wiki.debian.org/LSBInitScripts +Info: The given keyword was set in the LSB keyword section in this + /etc/init.d script but isn't one of the known LSB keywords and + doesn't begin with X-. One of the standard keywords may have + been misspelled. diff -Nru lintian-2.93.0/tags/i/init.d-script-has-unknown-lsb-keyword.tag lintian-2.89.0ubuntu1/tags/i/init.d-script-has-unknown-lsb-keyword.tag --- lintian-2.93.0/tags/i/init.d-script-has-unknown-lsb-keyword.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/init.d-script-has-unknown-lsb-keyword.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: init.d-script-has-unknown-lsb-keyword -Severity: warning -Check: init.d -See-Also: https://wiki.debian.org/LSBInitScripts -Explanation: The given keyword was set in the LSB keyword section in this - /etc/init.d script but isn't one of the known LSB keywords and - doesn't begin with X-. One of the standard keywords may have - been misspelled. diff -Nru lintian-2.93.0/tags/i/init.d-script-has-unterminated-lsb-section.desc lintian-2.89.0ubuntu1/tags/i/init.d-script-has-unterminated-lsb-section.desc --- lintian-2.93.0/tags/i/init.d-script-has-unterminated-lsb-section.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/init.d-script-has-unterminated-lsb-section.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,11 @@ +Tag: init.d-script-has-unterminated-lsb-section +Severity: error +Check: init.d +Ref: https://wiki.debian.org/LSBInitScripts +Info: This /etc/init.d script has an LSB keyword section starting + with ### BEGIN INIT INFO but either has no matching ### END + INIT INFO or has lines between those two markers that are not + comments. The line number given is the first line that doesn't look like + part of an LSB keyword section. There must be an end marker after all + the keyword settings and there must not be any lines between those + markers that do not begin with #. diff -Nru lintian-2.93.0/tags/i/init.d-script-has-unterminated-lsb-section.tag lintian-2.89.0ubuntu1/tags/i/init.d-script-has-unterminated-lsb-section.tag --- lintian-2.93.0/tags/i/init.d-script-has-unterminated-lsb-section.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/init.d-script-has-unterminated-lsb-section.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,11 +0,0 @@ -Tag: init.d-script-has-unterminated-lsb-section -Severity: error -Check: init.d -See-Also: https://wiki.debian.org/LSBInitScripts -Explanation: This /etc/init.d script has an LSB keyword section starting - with ### BEGIN INIT INFO but either has no matching ### END - INIT INFO or has lines between those two markers that are not - comments. The line number given is the first line that doesn't look like - part of an LSB keyword section. There must be an end marker after all - the keyword settings and there must not be any lines between those - markers that do not begin with #. diff -Nru lintian-2.93.0/tags/i/init.d-script-missing-dependency-on-local_fs.desc lintian-2.89.0ubuntu1/tags/i/init.d-script-missing-dependency-on-local_fs.desc --- lintian-2.93.0/tags/i/init.d-script-missing-dependency-on-local_fs.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/init.d-script-missing-dependency-on-local_fs.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,13 @@ +Tag: init.d-script-missing-dependency-on-local_fs +Severity: error +Certainty: possible +Check: init.d +Info: The given init script seems to refer to /var, possibly + using a file from there. Without a dependency on $local_fs in + Required-Start or Required-Stop, as appropriate, the init script might be + run before /var is mounted or after it's unmounted. + . + Using Should-Start or Should-Stop to declare the dependency is + conceptually incorrect since the $local_fs facility is always + available. Required-Start or Required-Stop should be used instead. +Ref: https://wiki.debian.org/LSBInitScripts diff -Nru lintian-2.93.0/tags/i/init.d-script-missing-dependency-on-local_fs.tag lintian-2.89.0ubuntu1/tags/i/init.d-script-missing-dependency-on-local_fs.tag --- lintian-2.93.0/tags/i/init.d-script-missing-dependency-on-local_fs.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/init.d-script-missing-dependency-on-local_fs.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,12 +0,0 @@ -Tag: init.d-script-missing-dependency-on-local_fs -Severity: error -Check: init.d -Explanation: The given init script seems to refer to /var, possibly - using a file from there. Without a dependency on $local_fs in - Required-Start or Required-Stop, as appropriate, the init script might be - run before /var is mounted or after it's unmounted. - . - Using Should-Start or Should-Stop to declare the dependency is - conceptually incorrect since the $local_fs facility is always - available. Required-Start or Required-Stop should be used instead. -See-Also: https://wiki.debian.org/LSBInitScripts diff -Nru lintian-2.93.0/tags/i/init.d-script-missing-lsb-keyword.desc lintian-2.89.0ubuntu1/tags/i/init.d-script-missing-lsb-keyword.desc --- lintian-2.93.0/tags/i/init.d-script-missing-lsb-keyword.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/init.d-script-missing-lsb-keyword.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: init.d-script-missing-lsb-keyword +Severity: warning +Check: init.d +Ref: https://wiki.debian.org/LSBInitScripts +Info: This /etc/init.d script has an LSB keyword section, but it + is missing the given required LSB keyword. If the value of this keyword + should be empty, please still include it in the LSB keyword section with + an empty value. diff -Nru lintian-2.93.0/tags/i/init.d-script-missing-lsb-keyword.tag lintian-2.89.0ubuntu1/tags/i/init.d-script-missing-lsb-keyword.tag --- lintian-2.93.0/tags/i/init.d-script-missing-lsb-keyword.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/init.d-script-missing-lsb-keyword.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: init.d-script-missing-lsb-keyword -Severity: warning -Check: init.d -See-Also: https://wiki.debian.org/LSBInitScripts -Explanation: This /etc/init.d script has an LSB keyword section, but it - is missing the given required LSB keyword. If the value of this keyword - should be empty, please still include it in the LSB keyword section with - an empty value. diff -Nru lintian-2.93.0/tags/i/init.d-script-missing-lsb-section.desc lintian-2.89.0ubuntu1/tags/i/init.d-script-missing-lsb-section.desc --- lintian-2.93.0/tags/i/init.d-script-missing-lsb-section.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/init.d-script-missing-lsb-section.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: init.d-script-missing-lsb-section +Severity: warning +Check: init.d +Ref: https://wiki.debian.org/LSBInitScripts +Info: This /etc/init.d script does not have an LSB keyword + section (or the ### BEGIN INIT INFO tag is incorrect). This + section provides description and runlevel information in a standard + format and provides dependency information that can be used to + parallelize the boot process. Please consider adding it. diff -Nru lintian-2.93.0/tags/i/init.d-script-missing-lsb-section.tag lintian-2.89.0ubuntu1/tags/i/init.d-script-missing-lsb-section.tag --- lintian-2.93.0/tags/i/init.d-script-missing-lsb-section.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/init.d-script-missing-lsb-section.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: init.d-script-missing-lsb-section -Severity: warning -Check: init.d -See-Also: https://wiki.debian.org/LSBInitScripts -Explanation: This /etc/init.d script does not have an LSB keyword - section (or the ### BEGIN INIT INFO tag is incorrect). This - section provides description and runlevel information in a standard - format and provides dependency information that can be used to - parallelize the boot process. Please consider adding it. diff -Nru lintian-2.93.0/tags/i/init.d-script-missing-lsb-short-description.desc lintian-2.89.0ubuntu1/tags/i/init.d-script-missing-lsb-short-description.desc --- lintian-2.93.0/tags/i/init.d-script-missing-lsb-short-description.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/init.d-script-missing-lsb-short-description.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: init.d-script-missing-lsb-short-description +Severity: info +Check: init.d +Ref: https://wiki.debian.org/LSBInitScripts +Info: This /etc/init.d script has an LSB keyword section, but it + is missing a Short-Description LSB keyword. This field isn't directly + used currently, but adding it is still a good idea for documentation + purposes. diff -Nru lintian-2.93.0/tags/i/init.d-script-missing-lsb-short-description.tag lintian-2.89.0ubuntu1/tags/i/init.d-script-missing-lsb-short-description.tag --- lintian-2.93.0/tags/i/init.d-script-missing-lsb-short-description.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/init.d-script-missing-lsb-short-description.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: init.d-script-missing-lsb-short-description -Severity: info -Check: init.d -See-Also: https://wiki.debian.org/LSBInitScripts -Explanation: This /etc/init.d script has an LSB keyword section, but it - is missing a Short-Description LSB keyword. This field isn't directly - used currently, but adding it is still a good idea for documentation - purposes. diff -Nru lintian-2.93.0/tags/i/init.d-script-missing-start.desc lintian-2.89.0ubuntu1/tags/i/init.d-script-missing-start.desc --- lintian-2.93.0/tags/i/init.d-script-missing-start.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/init.d-script-missing-start.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: init.d-script-missing-start +Severity: warning +Check: init.d +Info: The given /etc/init.d script indicates it should be + started at one of the runlevels 2-5 but not at all of them. This is a + mistake. The system administrators should be given the opportunity to + customize the runlevels at their will. +Ref: policy 9.3.3.1 diff -Nru lintian-2.93.0/tags/i/init.d-script-missing-start.tag lintian-2.89.0ubuntu1/tags/i/init.d-script-missing-start.tag --- lintian-2.93.0/tags/i/init.d-script-missing-start.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/init.d-script-missing-start.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: init.d-script-missing-start -Severity: warning -Check: init.d -Explanation: The given /etc/init.d script indicates it should be - started at one of the runlevels 2-5 but not at all of them. This is a - mistake. The system administrators should be given the opportunity to - customize the runlevels at their will. -See-Also: policy 9.3.3.1 diff -Nru lintian-2.93.0/tags/i/init.d-script-needs-depends-on-lsb-base.desc lintian-2.89.0ubuntu1/tags/i/init.d-script-needs-depends-on-lsb-base.desc --- lintian-2.93.0/tags/i/init.d-script-needs-depends-on-lsb-base.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/init.d-script-needs-depends-on-lsb-base.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: init.d-script-needs-depends-on-lsb-base +Severity: error +Certainty: possible +Check: init.d +Info: The given init script sources the /lib/lsb/init-functions utility + functions without declaring the corresponding dependency on lsb-base. + . + This dependency is not required for packages that ship a native service file. diff -Nru lintian-2.93.0/tags/i/init.d-script-needs-depends-on-lsb-base.tag lintian-2.89.0ubuntu1/tags/i/init.d-script-needs-depends-on-lsb-base.tag --- lintian-2.93.0/tags/i/init.d-script-needs-depends-on-lsb-base.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/init.d-script-needs-depends-on-lsb-base.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: init.d-script-needs-depends-on-lsb-base -Severity: error -Check: init.d -Explanation: The given init script sources the /lib/lsb/init-functions utility - functions without declaring the corresponding dependency on lsb-base. - . - This dependency is not required for packages that ship a native service file. diff -Nru lintian-2.93.0/tags/i/init.d-script-not-included-in-package.desc lintian-2.89.0ubuntu1/tags/i/init.d-script-not-included-in-package.desc --- lintian-2.93.0/tags/i/init.d-script-not-included-in-package.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/init.d-script-not-included-in-package.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,5 @@ +Tag: init.d-script-not-included-in-package +Severity: error +Check: init.d +Info: The /etc/init.d script is registered in the + postinst script, but is not included in the package. diff -Nru lintian-2.93.0/tags/i/init.d-script-not-included-in-package.tag lintian-2.89.0ubuntu1/tags/i/init.d-script-not-included-in-package.tag --- lintian-2.93.0/tags/i/init.d-script-not-included-in-package.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/init.d-script-not-included-in-package.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,5 +0,0 @@ -Tag: init.d-script-not-included-in-package -Severity: error -Check: init.d -Explanation: The /etc/init.d script is registered in the - postinst script, but is not included in the package. diff -Nru lintian-2.93.0/tags/i/init.d-script-not-marked-as-conffile.desc lintian-2.89.0ubuntu1/tags/i/init.d-script-not-marked-as-conffile.desc --- lintian-2.93.0/tags/i/init.d-script-not-marked-as-conffile.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/init.d-script-not-marked-as-conffile.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: init.d-script-not-marked-as-conffile +Severity: warning +Certainty: wild-guess +Check: init.d +Ref: policy 9.3.2 +Info: /etc/init.d scripts should be marked as conffiles. + . + This is usually an error, but the Policy allows for managing these files + manually in maintainer scripts and Lintian cannot reliably detect that. diff -Nru lintian-2.93.0/tags/i/init.d-script-not-marked-as-conffile.tag lintian-2.89.0ubuntu1/tags/i/init.d-script-not-marked-as-conffile.tag --- lintian-2.93.0/tags/i/init.d-script-not-marked-as-conffile.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/init.d-script-not-marked-as-conffile.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: init.d-script-not-marked-as-conffile -Severity: warning -Check: init.d -See-Also: policy 9.3.2 -Explanation: /etc/init.d scripts should be marked as conffiles. - . - This is usually an error, but the Policy allows for managing these files - manually in maintainer scripts and Lintian cannot reliably detect that. diff -Nru lintian-2.93.0/tags/i/init.d-script-possible-missing-stop.desc lintian-2.89.0ubuntu1/tags/i/init.d-script-possible-missing-stop.desc --- lintian-2.93.0/tags/i/init.d-script-possible-missing-stop.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/init.d-script-possible-missing-stop.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,16 @@ +Tag: init.d-script-possible-missing-stop +Severity: warning +Certainty: possible +Check: init.d +Info: The given /etc/init.d script indicates it should be + stopped at one of the runlevels 0, 1, or 6 but not at all of them. + This is usually a mistake. Normally, facilities that need to be stopped + at any of those runlevels need to be stopped at all of them. + . + For example, if it is safe for the facility provided by this init script + to be stopped by sendsigs at runlevels 0 and 6, there should be + no reason to special case runlevel 1, where killprocs would + stop it. If the facility needs special shutdown handling when rebooting + the system (runlevel 6), it probably needs the same handling when + halting the system (runlevel 0) or switching to single-user mode + (runlevel 1). diff -Nru lintian-2.93.0/tags/i/init.d-script-possible-missing-stop.tag lintian-2.89.0ubuntu1/tags/i/init.d-script-possible-missing-stop.tag --- lintian-2.93.0/tags/i/init.d-script-possible-missing-stop.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/init.d-script-possible-missing-stop.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,15 +0,0 @@ -Tag: init.d-script-possible-missing-stop -Severity: warning -Check: init.d -Explanation: The given /etc/init.d script indicates it should be - stopped at one of the runlevels 0, 1, or 6 but not at all of them. - This is usually a mistake. Normally, facilities that need to be stopped - at any of those runlevels need to be stopped at all of them. - . - For example, if it is safe for the facility provided by this init script - to be stopped by sendsigs at runlevels 0 and 6, there should be - no reason to special case runlevel 1, where killprocs would - stop it. If the facility needs special shutdown handling when rebooting - the system (runlevel 6), it probably needs the same handling when - halting the system (runlevel 0) or switching to single-user mode - (runlevel 1). diff -Nru lintian-2.93.0/tags/i/init.d-script-provides-virtual-facility.desc lintian-2.89.0ubuntu1/tags/i/init.d-script-provides-virtual-facility.desc --- lintian-2.93.0/tags/i/init.d-script-provides-virtual-facility.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/init.d-script-provides-virtual-facility.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,16 @@ +Tag: init.d-script-provides-virtual-facility +Severity: warning +Check: init.d +Info: This /etc/init.d script indicates in its LSB headers that + it provides a virtual facility, denoted by the dollar sign in front of + the name. + . + This is not the correct way to provide a virtual facility. Instead, the + package should include a file in /etc/insserv.conf.d, usually + named after the package, containing: + . + $virtual_facility_name +init-script-name + . + to declare that the named init script provides the named virtual + facility. +Ref: https://wiki.debian.org/LSBInitScripts/DebianVirtualFacilities diff -Nru lintian-2.93.0/tags/i/init.d-script-provides-virtual-facility.tag lintian-2.89.0ubuntu1/tags/i/init.d-script-provides-virtual-facility.tag --- lintian-2.93.0/tags/i/init.d-script-provides-virtual-facility.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/init.d-script-provides-virtual-facility.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,16 +0,0 @@ -Tag: init.d-script-provides-virtual-facility -Severity: warning -Check: init.d -Explanation: This /etc/init.d script indicates in its LSB headers that - it provides a virtual facility, denoted by the dollar sign in front of - the name. - . - This is not the correct way to provide a virtual facility. Instead, the - package should include a file in /etc/insserv.conf.d, usually - named after the package, containing: - . - $virtual_facility_name +init-script-name - . - to declare that the named init script provides the named virtual - facility. -See-Also: https://wiki.debian.org/LSBInitScripts/DebianVirtualFacilities diff -Nru lintian-2.93.0/tags/i/init.d-script-should-always-start-service.desc lintian-2.89.0ubuntu1/tags/i/init.d-script-should-always-start-service.desc --- lintian-2.93.0/tags/i/init.d-script-should-always-start-service.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/init.d-script-should-always-start-service.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,20 @@ +Tag: init.d-script-should-always-start-service +Severity: error +Certainty: possible +Check: init.d +Info: The specified file under /etc/default/ includes a line + such as ENABLED=, DISABLED=, RUN=, etc. + . + This is an older practice used so that the package's init script would + not start the service until the local system administrator changed this + value. + . + However, this hides from the underlying init system whether or not the + daemon should actually be started leading to confusing behavior + including service package start returning success without the + service actually starting. + . + Please remove this mechanism and disable enabling the daemon on install + via dh_installinit --no-enable or move to automatically + starting it. +Ref: policy 9.3.3.1, update-rc.d(8), dh_installinit(1) diff -Nru lintian-2.93.0/tags/i/init.d-script-should-always-start-service.tag lintian-2.89.0ubuntu1/tags/i/init.d-script-should-always-start-service.tag --- lintian-2.93.0/tags/i/init.d-script-should-always-start-service.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/init.d-script-should-always-start-service.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,19 +0,0 @@ -Tag: init.d-script-should-always-start-service -Severity: error -Check: init.d -Explanation: The specified file under /etc/default/ includes a line - such as ENABLED=, DISABLED=, RUN=, etc. - . - This is an older practice used so that the package's init script would - not start the service until the local system administrator changed this - value. - . - However, this hides from the underlying init system whether or not the - daemon should actually be started leading to confusing behavior - including service package start returning success without the - service actually starting. - . - Please remove this mechanism and disable enabling the daemon on install - via dh_installinit --no-enable or move to automatically - starting it. -See-Also: policy 9.3.3.1, update-rc.d(8), dh_installinit(1) diff -Nru lintian-2.93.0/tags/i/init.d-script-sourcing-without-test.desc lintian-2.89.0ubuntu1/tags/i/init.d-script-sourcing-without-test.desc --- lintian-2.93.0/tags/i/init.d-script-sourcing-without-test.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/init.d-script-sourcing-without-test.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,12 @@ +Tag: init.d-script-sourcing-without-test +Severity: error +Certainty: possible +Check: init.d +Info: The given /etc/init.d script seems to be sourcing an + /etc/default/ file without checking for its existence first. + Files in /etc/default/ can be deleted by the administrator at + any time, and init scripts are required to handle the situation + gracefully. For example: + . + [ -r /etc/default/foo ] && . /etc/default/foo +Ref: policy 9.3.2 diff -Nru lintian-2.93.0/tags/i/init.d-script-sourcing-without-test.tag lintian-2.89.0ubuntu1/tags/i/init.d-script-sourcing-without-test.tag --- lintian-2.93.0/tags/i/init.d-script-sourcing-without-test.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/init.d-script-sourcing-without-test.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,11 +0,0 @@ -Tag: init.d-script-sourcing-without-test -Severity: error -Check: init.d -Explanation: The given /etc/init.d script seems to be sourcing an - /etc/default/ file without checking for its existence first. - Files in /etc/default/ can be deleted by the administrator at - any time, and init scripts are required to handle the situation - gracefully. For example: - . - [ -r /etc/default/foo ] && . /etc/default/foo -See-Also: policy 9.3.2 diff -Nru lintian-2.93.0/tags/i/init.d-script-starts-in-stop-runlevel.desc lintian-2.89.0ubuntu1/tags/i/init.d-script-starts-in-stop-runlevel.desc --- lintian-2.93.0/tags/i/init.d-script-starts-in-stop-runlevel.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/init.d-script-starts-in-stop-runlevel.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: init.d-script-starts-in-stop-runlevel +Severity: error +Check: init.d +Info: This /etc/init.d script specifies the 0 or 6 runlevels in + Default-Start in its LSB keyword section. The 0 and 6 runlevels are + meant to only stop services, not to start them. Even if the init script + is doing something that isn't exactly stopping a service, the run-level + should be listed in Default-Stop, not Default-Start, and the script + should perform those actions when passed the stop argument. diff -Nru lintian-2.93.0/tags/i/init.d-script-starts-in-stop-runlevel.tag lintian-2.89.0ubuntu1/tags/i/init.d-script-starts-in-stop-runlevel.tag --- lintian-2.93.0/tags/i/init.d-script-starts-in-stop-runlevel.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/init.d-script-starts-in-stop-runlevel.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: init.d-script-starts-in-stop-runlevel -Severity: error -Check: init.d -Explanation: This /etc/init.d script specifies the 0 or 6 runlevels in - Default-Start in its LSB keyword section. The 0 and 6 runlevels are - meant to only stop services, not to start them. Even if the init script - is doing something that isn't exactly stopping a service, the run-level - should be listed in Default-Stop, not Default-Start, and the script - should perform those actions when passed the stop argument. diff -Nru lintian-2.93.0/tags/i/init-d-script-stops-in-s-runlevel.desc lintian-2.89.0ubuntu1/tags/i/init-d-script-stops-in-s-runlevel.desc --- lintian-2.93.0/tags/i/init-d-script-stops-in-s-runlevel.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/init-d-script-stops-in-s-runlevel.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: init-d-script-stops-in-s-runlevel +Severity: warning +Check: init.d +Info: This /etc/init.d script specifies the S runlevel in + Default-Stop in its LSB keyword section. The S runlevel is not a real + runlevel and is only used during boot. There is no way to switch to it + and hence no use for stop scripts for it, so S should be removed from + Default-Stop. diff -Nru lintian-2.93.0/tags/i/init-d-script-stops-in-s-runlevel.tag lintian-2.89.0ubuntu1/tags/i/init-d-script-stops-in-s-runlevel.tag --- lintian-2.93.0/tags/i/init-d-script-stops-in-s-runlevel.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/init-d-script-stops-in-s-runlevel.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: init-d-script-stops-in-s-runlevel -Severity: warning -Check: init.d -Explanation: This /etc/init.d script specifies the S runlevel in - Default-Stop in its LSB keyword section. The S runlevel is not a real - runlevel and is only used during boot. There is no way to switch to it - and hence no use for stop scripts for it, so S should be removed from - Default-Stop. diff -Nru lintian-2.93.0/tags/i/init.d-script-uses-usr-interpreter.desc lintian-2.89.0ubuntu1/tags/i/init.d-script-uses-usr-interpreter.desc --- lintian-2.93.0/tags/i/init.d-script-uses-usr-interpreter.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/init.d-script-uses-usr-interpreter.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,16 @@ +Tag: init.d-script-uses-usr-interpreter +Severity: warning +Certainty: possible +Check: init.d +Info: The given /etc/init.d script specifies an interpreter in + its shebang located under /usr. + . + It indicates that the init script may be using a non-essential + interpreter. Since init scripts are configuration files, they may be + left on the system after their package has been removed but not purged. + At that point, the package dependencies are not guaranteed to exist and + the interpreter may therefore not be available. + . + It's generally best to write init scripts using /bin/sh or + /bin/bash where possible, since they are guaranteed to always be + available. diff -Nru lintian-2.93.0/tags/i/init.d-script-uses-usr-interpreter.tag lintian-2.89.0ubuntu1/tags/i/init.d-script-uses-usr-interpreter.tag --- lintian-2.93.0/tags/i/init.d-script-uses-usr-interpreter.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/init.d-script-uses-usr-interpreter.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,15 +0,0 @@ -Tag: init.d-script-uses-usr-interpreter -Severity: warning -Check: init.d -Explanation: The given /etc/init.d script specifies an interpreter in - its shebang located under /usr. - . - It indicates that the init script may be using a non-essential - interpreter. Since init scripts are configuration files, they may be - left on the system after their package has been removed but not purged. - At that point, the package dependencies are not guaranteed to exist and - the interpreter may therefore not be available. - . - It's generally best to write init scripts using /bin/sh or - /bin/bash where possible, since they are guaranteed to always be - available. diff -Nru lintian-2.93.0/tags/i/initial-upload-closes-no-bugs.desc lintian-2.89.0ubuntu1/tags/i/initial-upload-closes-no-bugs.desc --- lintian-2.93.0/tags/i/initial-upload-closes-no-bugs.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/initial-upload-closes-no-bugs.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,12 @@ +Tag: initial-upload-closes-no-bugs +Severity: warning +Check: debian/changelog +Renamed-From: new-package-should-close-itp-bug +Info: This package appears to be the first packaging of a new upstream + software package (there is only one changelog entry and the Debian + revision is 1), but it does not close any bugs. The initial upload of a + new package should close the corresponding ITP bug for that package. + . + This warning can be ignored if the package is not intended for Debian or + if it is a split of an existing Debian package. +Ref: devref 5.1 diff -Nru lintian-2.93.0/tags/i/initial-upload-closes-no-bugs.tag lintian-2.89.0ubuntu1/tags/i/initial-upload-closes-no-bugs.tag --- lintian-2.93.0/tags/i/initial-upload-closes-no-bugs.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/initial-upload-closes-no-bugs.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,12 +0,0 @@ -Tag: initial-upload-closes-no-bugs -Severity: warning -Check: debian/changelog -Renamed-From: new-package-should-close-itp-bug -Explanation: This package appears to be the first packaging of a new upstream - software package (there is only one changelog entry and the Debian - revision is 1), but it does not close any bugs. The initial upload of a - new package should close the corresponding ITP bug for that package. - . - This warning can be ignored if the package is not intended for Debian or - if it is a split of an existing Debian package. -See-Also: devref 5.1 diff -Nru lintian-2.93.0/tags/i/init-script-is-not-a-file.desc lintian-2.89.0ubuntu1/tags/i/init-script-is-not-a-file.desc --- lintian-2.93.0/tags/i/init-script-is-not-a-file.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/init-script-is-not-a-file.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,5 @@ +Tag: init-script-is-not-a-file +Severity: error +Check: systemd +Info: The package contains an init script that is not a regular file or + resolvable symlink. diff -Nru lintian-2.93.0/tags/i/init-script-is-not-a-file.tag lintian-2.89.0ubuntu1/tags/i/init-script-is-not-a-file.tag --- lintian-2.93.0/tags/i/init-script-is-not-a-file.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/init-script-is-not-a-file.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,5 +0,0 @@ -Tag: init-script-is-not-a-file -Severity: error -Check: systemd -Explanation: The package contains an init script that is not a regular file or - resolvable symlink. diff -Nru lintian-2.93.0/tags/i/insecure-copyright-format-uri.desc lintian-2.89.0ubuntu1/tags/i/insecure-copyright-format-uri.desc --- lintian-2.93.0/tags/i/insecure-copyright-format-uri.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/insecure-copyright-format-uri.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: insecure-copyright-format-uri +Severity: pedantic +Check: debian/copyright/dep5 +Ref: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ +Info: Format URI of the machine-readable copyright file uses the plain HTTP + unencrypted transport protocol. Using HTTPS is preferred since policy 4.0.0. + . + Please use + https://www.debian.org/doc/packaging-manuals/copyright-format/version/ + as the format URI instead. diff -Nru lintian-2.93.0/tags/i/insecure-copyright-format-uri.tag lintian-2.89.0ubuntu1/tags/i/insecure-copyright-format-uri.tag --- lintian-2.93.0/tags/i/insecure-copyright-format-uri.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/insecure-copyright-format-uri.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,10 +0,0 @@ -Tag: insecure-copyright-format-uri -Severity: pedantic -Check: debian/copyright/dep5 -See-Also: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ -Explanation: Format URI of the machine-readable copyright file uses the plain HTTP - unencrypted transport protocol. Using HTTPS is preferred since policy 4.0.0. - . - Please use - https://www.debian.org/doc/packaging-manuals/copyright-format/*version*/ - as the format URI instead. diff -Nru lintian-2.93.0/tags/i/install-info-used-in-maintainer-script.desc lintian-2.89.0ubuntu1/tags/i/install-info-used-in-maintainer-script.desc --- lintian-2.93.0/tags/i/install-info-used-in-maintainer-script.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/install-info-used-in-maintainer-script.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,11 @@ +Tag: install-info-used-in-maintainer-script +Severity: error +Certainty: possible +Check: scripts +Info: This script apparently runs install-info. Updating the + /usr/share/info/dir file is now handled automatically by + triggers, so running install-info from maintainer scripts is no + longer necessary. + . + If debhelper generated the maintainer script fragment, rebuilding the + package with debhelper 7.2.17 or later will fix this problem. diff -Nru lintian-2.93.0/tags/i/install-info-used-in-maintainer-script.tag lintian-2.89.0ubuntu1/tags/i/install-info-used-in-maintainer-script.tag --- lintian-2.93.0/tags/i/install-info-used-in-maintainer-script.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/install-info-used-in-maintainer-script.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,10 +0,0 @@ -Tag: install-info-used-in-maintainer-script -Severity: error -Check: scripts -Explanation: This script apparently runs install-info. Updating the - /usr/share/info/dir file is now handled automatically by - triggers, so running install-info from maintainer scripts is no - longer necessary. - . - If debhelper generated the maintainer script fragment, rebuilding the - package with debhelper 7.2.17 or later will fix this problem. diff -Nru lintian-2.93.0/tags/i/interpreter-in-usr-local.desc lintian-2.89.0ubuntu1/tags/i/interpreter-in-usr-local.desc --- lintian-2.93.0/tags/i/interpreter-in-usr-local.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/interpreter-in-usr-local.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: interpreter-in-usr-local +Severity: error +Check: scripts +Info: This package contains a script that looks for an interpreter in a + directory in /usr/local. Since Debian does not install anything in + /usr/local, this is the wrong place to look. diff -Nru lintian-2.93.0/tags/i/interpreter-in-usr-local.tag lintian-2.89.0ubuntu1/tags/i/interpreter-in-usr-local.tag --- lintian-2.93.0/tags/i/interpreter-in-usr-local.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/interpreter-in-usr-local.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: interpreter-in-usr-local -Severity: error -Check: scripts -Explanation: This package contains a script that looks for an interpreter in a - directory in /usr/local. Since Debian does not install anything in - /usr/local, this is the wrong place to look. diff -Nru lintian-2.93.0/tags/i/interpreter-not-absolute.desc lintian-2.89.0ubuntu1/tags/i/interpreter-not-absolute.desc --- lintian-2.93.0/tags/i/interpreter-not-absolute.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/interpreter-not-absolute.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: interpreter-not-absolute +Severity: warning +Check: scripts +Info: This script uses a relative path to locate its interpreter. + This path will be taken relative to the caller's current directory, not + the script's, so it is not likely to be what was intended. diff -Nru lintian-2.93.0/tags/i/interpreter-not-absolute.tag lintian-2.89.0ubuntu1/tags/i/interpreter-not-absolute.tag --- lintian-2.93.0/tags/i/interpreter-not-absolute.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/interpreter-not-absolute.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: interpreter-not-absolute -Severity: warning -Check: scripts -Explanation: This script uses a relative path to locate its interpreter. - This path will be taken relative to the caller's current directory, not - the script's, so it is not likely to be what was intended. diff -Nru lintian-2.93.0/tags/i/intra-source-package-circular-dependency.desc lintian-2.89.0ubuntu1/tags/i/intra-source-package-circular-dependency.desc --- lintian-2.93.0/tags/i/intra-source-package-circular-dependency.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/intra-source-package-circular-dependency.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,14 @@ +Tag: intra-source-package-circular-dependency +Severity: warning +Check: group-checks +Info: The listed packages from the same source circularly depend + (or pre-depend) on each other. This makes it difficult for tools + to properly handle install/upgrade sequences. Furthermore this + complicates automated removal of unused packages. + . + If possible, consider removing or reducing one of the depends. + . + Note: This check is limited to packages created from the same + source package. Full circular dependencies between binaries from + different source packages is beyond the scope of Lintian. +Ref: policy 7.2 diff -Nru lintian-2.93.0/tags/i/intra-source-package-circular-dependency.tag lintian-2.89.0ubuntu1/tags/i/intra-source-package-circular-dependency.tag --- lintian-2.93.0/tags/i/intra-source-package-circular-dependency.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/intra-source-package-circular-dependency.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,14 +0,0 @@ -Tag: intra-source-package-circular-dependency -Severity: warning -Check: group-checks -Explanation: The listed packages from the same source circularly depend - (or pre-depend) on each other. This makes it difficult for tools - to properly handle install/upgrade sequences. Furthermore this - complicates automated removal of unused packages. - . - If possible, consider removing or reducing one of the depends. - . - Note: This check is limited to packages created from the same - source package. Full circular dependencies between binaries from - different source packages is beyond the scope of Lintian. -See-Also: policy 7.2 diff -Nru lintian-2.93.0/tags/i/invalid-arch-string-in-source-relation.desc lintian-2.89.0ubuntu1/tags/i/invalid-arch-string-in-source-relation.desc --- lintian-2.93.0/tags/i/invalid-arch-string-in-source-relation.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/invalid-arch-string-in-source-relation.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: invalid-arch-string-in-source-relation +Severity: error +Certainty: possible +Check: fields/package-relations +Ref: policy 5.6.8 +Info: The architecture string in the source relation includes an unknown + architecture. This may be a typo, or it may be an architecture that dpkg + doesn't know about yet. A common problem is incorrectly separating + architectures with a comma, such as [i386, m68k]. Architectures + are separated by spaces; this should instead be [i386 m68k]. diff -Nru lintian-2.93.0/tags/i/invalid-arch-string-in-source-relation.tag lintian-2.89.0ubuntu1/tags/i/invalid-arch-string-in-source-relation.tag --- lintian-2.93.0/tags/i/invalid-arch-string-in-source-relation.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/invalid-arch-string-in-source-relation.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: invalid-arch-string-in-source-relation -Severity: error -Check: fields/package-relations -See-Also: policy 5.6.8 -Explanation: The architecture string in the source relation includes an unknown - architecture. This may be a typo, or it may be an architecture that dpkg - doesn't know about yet. A common problem is incorrectly separating - architectures with a comma, such as [i386, m68k]. Architectures - are separated by spaces; this should instead be [i386 m68k]. diff -Nru lintian-2.93.0/tags/i/invalid-date-in-debian-changelog.desc lintian-2.89.0ubuntu1/tags/i/invalid-date-in-debian-changelog.desc --- lintian-2.93.0/tags/i/invalid-date-in-debian-changelog.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/invalid-date-in-debian-changelog.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,16 @@ +Tag: invalid-date-in-debian-changelog +Severity: error +Check: debian/changelog +Info: The date format in the latest changelog entry file appears to be invalid. + . + Dates should use the following format (compatible and with the same semantics + of RFC 2822 and RFC 5322): + . + day-of-week, dd month yyyy hh:mm:ss +zzzz + . + To avoid problems like this, consider using a tool like dch(1) or + date(1) to generate the date. Example: + . + $ date -R -ud '2013-11-05 23:59:59' + Tue, 05 Nov 2013 23:59:59 +0000 +Ref: policy 4.4 diff -Nru lintian-2.93.0/tags/i/invalid-date-in-debian-changelog.tag lintian-2.89.0ubuntu1/tags/i/invalid-date-in-debian-changelog.tag --- lintian-2.93.0/tags/i/invalid-date-in-debian-changelog.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/invalid-date-in-debian-changelog.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,16 +0,0 @@ -Tag: invalid-date-in-debian-changelog -Severity: error -Check: debian/changelog -Explanation: The date format in the latest changelog entry file appears to be invalid. - . - Dates should use the following format (compatible and with the same semantics - of RFC 2822 and RFC 5322): - . - day-of-week, dd month yyyy hh:mm:ss +zzzz - . - To avoid problems like this, consider using a tool like dch(1) or - date(1) to generate the date. Example: - . - $ date -R -ud '2013-11-05 23:59:59' - Tue, 05 Nov 2013 23:59:59 +0000 -See-Also: policy 4.4 diff -Nru lintian-2.93.0/tags/i/invalid-escape-sequence-in-dep5-copyright.desc lintian-2.89.0ubuntu1/tags/i/invalid-escape-sequence-in-dep5-copyright.desc --- lintian-2.93.0/tags/i/invalid-escape-sequence-in-dep5-copyright.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/invalid-escape-sequence-in-dep5-copyright.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: invalid-escape-sequence-in-dep5-copyright +Severity: warning +Certainty: possible +Check: debian/copyright/dep5 +Ref: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ +Info: The only allowed escape sequences are "\*", "\?" and "\\" (without + quotes) to produce a literal star, question mark and backslash, respectively. + Without the escaping backslash, the star and question mark take the role of + globbing operators similar to shell globs which is why they have to be + escaped. No other escapable characters than "*", "?" and "\" exist. diff -Nru lintian-2.93.0/tags/i/invalid-escape-sequence-in-dep5-copyright.tag lintian-2.89.0ubuntu1/tags/i/invalid-escape-sequence-in-dep5-copyright.tag --- lintian-2.93.0/tags/i/invalid-escape-sequence-in-dep5-copyright.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/invalid-escape-sequence-in-dep5-copyright.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: invalid-escape-sequence-in-dep5-copyright -Severity: warning -Check: debian/copyright/dep5 -See-Also: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ -Explanation: The only allowed escape sequences are "\*", "\?" and "\\" (without - quotes) to produce a literal star, question mark and backslash, respectively. - Without the escaping backslash, the star and question mark take the role of - globbing operators similar to shell globs which is why they have to be - escaped. No other escapable characters than "*", "?" and "\" exist. diff -Nru lintian-2.93.0/tags/i/invalid-field-for-derivative.desc lintian-2.89.0ubuntu1/tags/i/invalid-field-for-derivative.desc --- lintian-2.93.0/tags/i/invalid-field-for-derivative.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/invalid-field-for-derivative.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,17 @@ +Tag: invalid-field-for-derivative +Severity: error +Check: fields/derivatives +Info: The specified field in debian/control does not match the + required format for this Debian derivative. + . + Derivative distributions of Debian may enforce additional restrictions + on such fields for many reasons including ensuring that: + . + - Debian maintainers are not contacted for forked or packages that + are otherwise modified by the derivative. + - The original maintainer is still credited for their work (eg. in a + XSBC-Original-Maintainer fied. + - References to revision control systems (eg. Vcs-Git) are + pointing to the correct, updated location. + - Fields that become misleading in the context of a derivative are + removed. diff -Nru lintian-2.93.0/tags/i/invalid-field-for-derivative.tag lintian-2.89.0ubuntu1/tags/i/invalid-field-for-derivative.tag --- lintian-2.93.0/tags/i/invalid-field-for-derivative.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/invalid-field-for-derivative.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,17 +0,0 @@ -Tag: invalid-field-for-derivative -Severity: error -Check: fields/derivatives -Explanation: The specified field in debian/control does not match the - required format for this Debian derivative. - . - Derivative distributions of Debian may enforce additional restrictions - on such fields for many reasons including ensuring that: - . - - Debian maintainers are not contacted for forked or packages that - are otherwise modified by the derivative. - - The original maintainer is still credited for their work (eg. in a - XSBC-Original-Maintainer fied. - - References to revision control systems (eg. Vcs-Git) are - pointing to the correct, updated location. - - Fields that become misleading in the context of a derivative are - removed. diff -Nru lintian-2.93.0/tags/i/invalid-po-file.desc lintian-2.89.0ubuntu1/tags/i/invalid-po-file.desc --- lintian-2.93.0/tags/i/invalid-po-file.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/invalid-po-file.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: invalid-po-file +Severity: warning +Check: debian/po-debconf +Info: Errors were found in the listed PO file that will cause its content + to be discarded. Run msgfmt on the file to see the error + messages. diff -Nru lintian-2.93.0/tags/i/invalid-po-file.tag lintian-2.89.0ubuntu1/tags/i/invalid-po-file.tag --- lintian-2.93.0/tags/i/invalid-po-file.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/invalid-po-file.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: invalid-po-file -Severity: warning -Check: debian/po-debconf -Explanation: Errors were found in the listed PO file that will cause its content - to be discarded. Run msgfmt on the file to see the error - messages. diff -Nru lintian-2.93.0/tags/i/invalid-potfiles-in.desc lintian-2.89.0ubuntu1/tags/i/invalid-potfiles-in.desc --- lintian-2.93.0/tags/i/invalid-potfiles-in.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/invalid-potfiles-in.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,11 @@ +Tag: invalid-potfiles-in +Severity: warning +Check: debian/po-debconf +Info: Errors were found in the debian/po/POTFILES.in file. + . + Please make sure that all strings marked for translation are in uniform + encoding (say UTF-8) then prepend the following line to POTFILES.in and + rerun intltool-update. + . + [encoding: UTF-8] +Ref: #849912, #883653 diff -Nru lintian-2.93.0/tags/i/invalid-potfiles-in.tag lintian-2.89.0ubuntu1/tags/i/invalid-potfiles-in.tag --- lintian-2.93.0/tags/i/invalid-potfiles-in.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/invalid-potfiles-in.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,11 +0,0 @@ -Tag: invalid-potfiles-in -Severity: warning -Check: debian/po-debconf -Explanation: Errors were found in the debian/po/POTFILES.in file. - . - Please make sure that all strings marked for translation are in uniform - encoding (say UTF-8) then prepend the following line to POTFILES.in and - rerun intltool-update. - . - [encoding: UTF-8] -See-Also: Bug#849912, Bug#883653 diff -Nru lintian-2.93.0/tags/i/invalid-profile-name-in-build-profiles-field.desc lintian-2.89.0ubuntu1/tags/i/invalid-profile-name-in-build-profiles-field.desc --- lintian-2.93.0/tags/i/invalid-profile-name-in-build-profiles-field.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/invalid-profile-name-in-build-profiles-field.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: invalid-profile-name-in-build-profiles-field +Severity: error +Certainty: possible +Check: debian/control +Info: The restriction formula in Build-Profiles field includes an unknown build + profile. The only allowed build profiles are "cross", "nobiarch", + "nocheck", "nodoc", "nogolang", "noguile", "noinsttest", "nojava", + "nolua", "noperl", "nopython", "noruby", "noudeb", "stage1", "stage2" + and "pkg.srcpkg.anything". +Ref: https://wiki.debian.org/BuildProfileSpec#Registered_profile_names diff -Nru lintian-2.93.0/tags/i/invalid-profile-name-in-build-profiles-field.tag lintian-2.89.0ubuntu1/tags/i/invalid-profile-name-in-build-profiles-field.tag --- lintian-2.93.0/tags/i/invalid-profile-name-in-build-profiles-field.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/invalid-profile-name-in-build-profiles-field.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: invalid-profile-name-in-build-profiles-field -Severity: error -Check: debian/control -Explanation: The restriction formula in Build-Profiles field includes an unknown build - profile. The only allowed build profiles are "cross", "nobiarch", - "nocheck", "nodoc", "nogolang", "noguile", "noinsttest", "nojava", - "nolua", "noperl", "nopython", "noruby", "noudeb", "stage1", "stage2" - and "pkg.*srcpkg*.*anything*". -See-Also: https://wiki.debian.org/BuildProfileSpec#Registered_profile_names diff -Nru lintian-2.93.0/tags/i/invalid-profile-name-in-source-relation.desc lintian-2.89.0ubuntu1/tags/i/invalid-profile-name-in-source-relation.desc --- lintian-2.93.0/tags/i/invalid-profile-name-in-source-relation.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/invalid-profile-name-in-source-relation.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,19 @@ +Tag: invalid-profile-name-in-source-relation +Severity: error +Certainty: possible +Check: fields/package-relations +Info: The restriction formula in the source relation includes an unknown build + profile. The only allowed build profiles are + "cross", + "nobiarch", + "nocheck", + "nodoc", + "nogolang", + "nojava", + "noperl", + "nopython", + "noudeb", + "stage1", + "stage2" + and "pkg.srcpkg.anything". +Ref: https://wiki.debian.org/BuildProfileSpec#Registered_profile_names diff -Nru lintian-2.93.0/tags/i/invalid-profile-name-in-source-relation.tag lintian-2.89.0ubuntu1/tags/i/invalid-profile-name-in-source-relation.tag --- lintian-2.93.0/tags/i/invalid-profile-name-in-source-relation.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/invalid-profile-name-in-source-relation.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,18 +0,0 @@ -Tag: invalid-profile-name-in-source-relation -Severity: error -Check: fields/package-relations -Explanation: The restriction formula in the source relation includes an unknown build - profile. The only allowed build profiles are - "cross", - "nobiarch", - "nocheck", - "nodoc", - "nogolang", - "nojava", - "noperl", - "nopython", - "noudeb", - "stage1", - "stage2" - and "pkg.*srcpkg*.*anything*". -See-Also: https://wiki.debian.org/BuildProfileSpec#Registered_profile_names diff -Nru lintian-2.93.0/tags/i/invalid-restriction-formula-in-build-profiles-field.desc lintian-2.89.0ubuntu1/tags/i/invalid-restriction-formula-in-build-profiles-field.desc --- lintian-2.93.0/tags/i/invalid-restriction-formula-in-build-profiles-field.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/invalid-restriction-formula-in-build-profiles-field.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: invalid-restriction-formula-in-build-profiles-field +Severity: error +Check: debian/control +Info: The restriction formula in the Build-Profiles field must have the same + format as the restriction formula in the Build-Depends field with angle + brackets. +Ref: https://wiki.debian.org/BuildProfileSpec#The_Build-Profiles_field diff -Nru lintian-2.93.0/tags/i/invalid-restriction-formula-in-build-profiles-field.tag lintian-2.89.0ubuntu1/tags/i/invalid-restriction-formula-in-build-profiles-field.tag --- lintian-2.93.0/tags/i/invalid-restriction-formula-in-build-profiles-field.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/invalid-restriction-formula-in-build-profiles-field.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: invalid-restriction-formula-in-build-profiles-field -Severity: error -Check: debian/control -Explanation: The restriction formula in the Build-Profiles field must have the same - format as the restriction formula in the Build-Depends field with angle - brackets. -See-Also: https://wiki.debian.org/BuildProfileSpec#The_Build-Profiles_field diff -Nru lintian-2.93.0/tags/i/invalid-short-name-in-dep5-copyright.desc lintian-2.89.0ubuntu1/tags/i/invalid-short-name-in-dep5-copyright.desc --- lintian-2.93.0/tags/i/invalid-short-name-in-dep5-copyright.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/invalid-short-name-in-dep5-copyright.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: invalid-short-name-in-dep5-copyright +Severity: warning +Check: debian/copyright/dep5 +Ref: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ +Info: The “License” field contains a short name observed to be a + misspelling of one of the standard short names. diff -Nru lintian-2.93.0/tags/i/invalid-short-name-in-dep5-copyright.tag lintian-2.89.0ubuntu1/tags/i/invalid-short-name-in-dep5-copyright.tag --- lintian-2.93.0/tags/i/invalid-short-name-in-dep5-copyright.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/invalid-short-name-in-dep5-copyright.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: invalid-short-name-in-dep5-copyright -Severity: warning -Check: debian/copyright/dep5 -See-Also: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ -Explanation: The “License” field contains a short name observed to be a - misspelling of one of the standard short names. diff -Nru lintian-2.93.0/tags/i/invalid-standards-version.desc lintian-2.89.0ubuntu1/tags/i/invalid-standards-version.desc --- lintian-2.93.0/tags/i/invalid-standards-version.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/invalid-standards-version.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: invalid-standards-version +Severity: error +Check: fields/standards-version +Info: The source package refers to a Standards-Version which never + existed. Please update your package to latest Policy and set this + control field appropriately. diff -Nru lintian-2.93.0/tags/i/invalid-standards-version.tag lintian-2.89.0ubuntu1/tags/i/invalid-standards-version.tag --- lintian-2.93.0/tags/i/invalid-standards-version.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/invalid-standards-version.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: invalid-standards-version -Severity: error -Check: fields/standards-version -Explanation: The source package refers to a Standards-Version which never - existed. Please update your package to latest Policy and set this - control field appropriately. diff -Nru lintian-2.93.0/tags/i/invalid-template-id-in-symbols-file.desc lintian-2.89.0ubuntu1/tags/i/invalid-template-id-in-symbols-file.desc --- lintian-2.93.0/tags/i/invalid-template-id-in-symbols-file.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/invalid-template-id-in-symbols-file.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: invalid-template-id-in-symbols-file +Severity: error +Check: shared-libs +Info: The symbol definition refers to an alternative dependency template + which is not defined for the library containing the symbol. + . + The first alternative dependency template for a library the id number + of 1, with the ids of subsequent alternative templates increasing in + sequence. diff -Nru lintian-2.93.0/tags/i/invalid-template-id-in-symbols-file.tag lintian-2.89.0ubuntu1/tags/i/invalid-template-id-in-symbols-file.tag --- lintian-2.93.0/tags/i/invalid-template-id-in-symbols-file.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/invalid-template-id-in-symbols-file.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: invalid-template-id-in-symbols-file -Severity: error -Check: shared-libs -Explanation: The symbol definition refers to an alternative dependency template - which is not defined for the library containing the symbol. - . - The first alternative dependency template for a library the id number - of 1, with the ids of subsequent alternative templates increasing in - sequence. diff -Nru lintian-2.93.0/tags/i/invalid-value-in-built-using-field.desc lintian-2.89.0ubuntu1/tags/i/invalid-value-in-built-using-field.desc --- lintian-2.93.0/tags/i/invalid-value-in-built-using-field.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/invalid-value-in-built-using-field.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,11 @@ +Tag: invalid-value-in-built-using-field +Severity: error +Check: fields/built-using +Info: The Built-Using field contains invalid fields. + . + The Built-Using field must consist of simple source (= + version) clauses. Notably, it must use a strictly equal in the + relation. + . + Only first issue is shown. +Ref: policy 7.8 diff -Nru lintian-2.93.0/tags/i/invalid-value-in-built-using-field.tag lintian-2.89.0ubuntu1/tags/i/invalid-value-in-built-using-field.tag --- lintian-2.93.0/tags/i/invalid-value-in-built-using-field.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/invalid-value-in-built-using-field.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,11 +0,0 @@ -Tag: invalid-value-in-built-using-field -Severity: error -Check: fields/built-using -Explanation: The Built-Using field contains invalid fields. - . - The Built-Using field must consist of simple source (= - version) clauses. Notably, it must use a strictly equal in the - relation. - . - Only first issue is shown. -See-Also: policy 7.8 diff -Nru lintian-2.93.0/tags/i/invalid-versioned-provides.desc lintian-2.89.0ubuntu1/tags/i/invalid-versioned-provides.desc --- lintian-2.93.0/tags/i/invalid-versioned-provides.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/invalid-versioned-provides.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: invalid-versioned-provides +Severity: error +Check: fields/package-relations +Ref: policy 7.1, #761219 +Info: The package declares a provides relation with an invalid version + operator (e.g. ">="). + . + If a provides is versioned, it must use "=". diff -Nru lintian-2.93.0/tags/i/invalid-versioned-provides.tag lintian-2.89.0ubuntu1/tags/i/invalid-versioned-provides.tag --- lintian-2.93.0/tags/i/invalid-versioned-provides.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/invalid-versioned-provides.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: invalid-versioned-provides -Severity: error -Check: fields/package-relations -See-Also: policy 7.1, Bug#761219 -Explanation: The package declares a provides relation with an invalid version - operator (e.g. ">="). - . - If a provides is versioned, it must use "=". diff -Nru lintian-2.93.0/tags/i/invalid-version-number-for-derivative.desc lintian-2.89.0ubuntu1/tags/i/invalid-version-number-for-derivative.desc --- lintian-2.93.0/tags/i/invalid-version-number-for-derivative.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/invalid-version-number-for-derivative.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: invalid-version-number-for-derivative +Severity: error +Check: fields/version +Info: The version number for this package does not comply with the + required format for this Debian derivative. + . + Derivative distributions of Debian may enforce additional restrictions + on the version in order to ensure that forked (or packages that are + otherwise modified) are marked as such. diff -Nru lintian-2.93.0/tags/i/invalid-version-number-for-derivative.tag lintian-2.89.0ubuntu1/tags/i/invalid-version-number-for-derivative.tag --- lintian-2.93.0/tags/i/invalid-version-number-for-derivative.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/invalid-version-number-for-derivative.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: invalid-version-number-for-derivative -Severity: error -Check: fields/version -Explanation: The version number for this package does not comply with the - required format for this Debian derivative. - . - Derivative distributions of Debian may enforce additional restrictions - on the version in order to ensure that forked (or packages that are - otherwise modified) are marked as such. diff -Nru lintian-2.93.0/tags/i/isdefault-flag-is-deprecated.desc lintian-2.89.0ubuntu1/tags/i/isdefault-flag-is-deprecated.desc --- lintian-2.93.0/tags/i/isdefault-flag-is-deprecated.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/isdefault-flag-is-deprecated.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,13 @@ +Tag: isdefault-flag-is-deprecated +Severity: warning +Certainty: possible +Check: debian/debconf +Info: The "isdefault" flag on debconf questions is deprecated as of debconf + 0.5.00, and has been replaced by "seen" with the inverse meaning. From + debconf 0.5 onwards there should be very few reasons to use isdefault/seen + anyway, as backing up works much better now. See + /usr/share/doc/debconf-doc/changelog.gz for more information. + . + The misuse of isdefault often leads to questions being asked twice in one + installation run, or, worse, on every upgrade. Please test your package + carefully to make sure this does not happen. diff -Nru lintian-2.93.0/tags/i/isdefault-flag-is-deprecated.tag lintian-2.89.0ubuntu1/tags/i/isdefault-flag-is-deprecated.tag --- lintian-2.93.0/tags/i/isdefault-flag-is-deprecated.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/i/isdefault-flag-is-deprecated.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,12 +0,0 @@ -Tag: isdefault-flag-is-deprecated -Severity: warning -Check: debian/debconf -Explanation: The "isdefault" flag on debconf questions is deprecated as of debconf - 0.5.00, and has been replaced by "seen" with the inverse meaning. From - debconf 0.5 onwards there should be very few reasons to use isdefault/seen - anyway, as backing up works much better now. See - /usr/share/doc/debconf-doc/changelog.gz for more information. - . - The misuse of isdefault often leads to questions being asked twice in one - installation run, or, worse, on every upgrade. Please test your package - carefully to make sure this does not happen. diff -Nru lintian-2.93.0/tags/j/jar-contains-source.desc lintian-2.89.0ubuntu1/tags/j/jar-contains-source.desc --- lintian-2.93.0/tags/j/jar-contains-source.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/j/jar-contains-source.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,12 @@ +Tag: jar-contains-source +Severity: warning +Check: languages/java +Info: The package ships the specified Jar file containing a + .java file alongside a corresponding .class file. + . + This wastes disk space as the source is always available via apt + source. + . + Please ensure that the specified .java files are not shipped in + the Jar file. +Ref: java-policy 2.4 diff -Nru lintian-2.93.0/tags/j/jar-contains-source.tag lintian-2.89.0ubuntu1/tags/j/jar-contains-source.tag --- lintian-2.93.0/tags/j/jar-contains-source.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/j/jar-contains-source.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,12 +0,0 @@ -Tag: jar-contains-source -Severity: warning -Check: languages/java -Explanation: The package ships the specified Jar file containing a - .java file alongside a corresponding .class file. - . - This wastes disk space as the source is always available via apt - source. - . - Please ensure that the specified .java files are not shipped in - the Jar file. -See-Also: java-policy 2.4 diff -Nru lintian-2.93.0/tags/j/jar-not-in-usr-share.desc lintian-2.89.0ubuntu1/tags/j/jar-not-in-usr-share.desc --- lintian-2.93.0/tags/j/jar-not-in-usr-share.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/j/jar-not-in-usr-share.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,15 @@ +Tag: jar-not-in-usr-share +Severity: warning +Certainty: possible +Check: languages/java +Ref: java-policy 2.2, java-policy 2.3 +Info: The classpath listed in some of the files references files outside + of /usr/share, while all installed JAR files must be within + /usr/share/java for libraries or /usr/share/package for JARs for + private use. + . + The rationale is that jar files are in almost all cases architecture + independent and therefore should be in /usr/share. If the jar file is + truly architecture dependent or it cannot be moved since symlinked jar + files are not accepted by the application, then please override this + tag. diff -Nru lintian-2.93.0/tags/j/jar-not-in-usr-share.tag lintian-2.89.0ubuntu1/tags/j/jar-not-in-usr-share.tag --- lintian-2.93.0/tags/j/jar-not-in-usr-share.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/j/jar-not-in-usr-share.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,14 +0,0 @@ -Tag: jar-not-in-usr-share -Severity: warning -Check: languages/java -See-Also: java-policy 2.2, java-policy 2.3 -Explanation: The classpath listed in some of the files references files outside - of /usr/share, while all installed JAR files must be within - /usr/share/java for libraries or /usr/share/*package* for JARs for - private use. - . - The rationale is that jar files are in almost all cases architecture - independent and therefore should be in /usr/share. If the jar file is - truly architecture dependent or it cannot be moved since symlinked jar - files are not accepted by the application, then please override this - tag. diff -Nru lintian-2.93.0/tags/j/javalib-but-no-public-jars.desc lintian-2.89.0ubuntu1/tags/j/javalib-but-no-public-jars.desc --- lintian-2.93.0/tags/j/javalib-but-no-public-jars.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/j/javalib-but-no-public-jars.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: javalib-but-no-public-jars +Severity: info +Certainty: possible +Check: languages/java +Info: The name of the package suggests that it contains a java library but + it does not contain any JAR file in /usr/share/java, while the java policy + mandates that JAR files outside /usr/share/java are for private use. diff -Nru lintian-2.93.0/tags/j/javalib-but-no-public-jars.tag lintian-2.89.0ubuntu1/tags/j/javalib-but-no-public-jars.tag --- lintian-2.93.0/tags/j/javalib-but-no-public-jars.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/j/javalib-but-no-public-jars.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: javalib-but-no-public-jars -Severity: info -Check: languages/java -Explanation: The name of the package suggests that it contains a java library but - it does not contain any JAR file in /usr/share/java, while the java policy - mandates that JAR files outside /usr/share/java are for private use. diff -Nru lintian-2.93.0/tags/k/killall-is-dangerous.desc lintian-2.89.0ubuntu1/tags/k/killall-is-dangerous.desc --- lintian-2.93.0/tags/k/killall-is-dangerous.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/k/killall-is-dangerous.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: killall-is-dangerous +Severity: warning +Certainty: possible +Check: scripts +Info: The maintainer script seems to call killall. Since this + utility kills processes by name, it may well end up killing unrelated + processes. Most uses of killall should use invoke-rc.d + instead. diff -Nru lintian-2.93.0/tags/k/killall-is-dangerous.tag lintian-2.89.0ubuntu1/tags/k/killall-is-dangerous.tag --- lintian-2.93.0/tags/k/killall-is-dangerous.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/k/killall-is-dangerous.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: killall-is-dangerous -Severity: warning -Check: scripts -Explanation: The maintainer script seems to call killall. Since this - utility kills processes by name, it may well end up killing unrelated - processes. Most uses of killall should use invoke-rc.d - instead. diff -Nru lintian-2.93.0/tags/l/lacks-ldconfig-trigger.desc lintian-2.89.0ubuntu1/tags/l/lacks-ldconfig-trigger.desc --- lintian-2.93.0/tags/l/lacks-ldconfig-trigger.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/l/lacks-ldconfig-trigger.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,17 @@ +Tag: lacks-ldconfig-trigger +Severity: error +Check: shared-libs +Renamed-From: package-must-activate-ldconfig-trigger +Info: The package installs shared libraries in a directory controlled by + the dynamic library loader. Therefore, the package must trigger libc's + "ldconfig" trigger to ensure the ldconfig cache is updated. + . + If the package is using debhelper, dh_makeshlibs should + automatically discover this and add the trigger itself. + Otherwise, please add activate-noawait ldconfig to the + triggers file in the control member. + . + Note this tag may trigger for packages built with debhelper before + version 9.20151004. In such case, a simple rebuild will often be + sufficient to fix this issue. +Ref: policy 8.1.1, https://lists.debian.org/debian-devel/2015/08/msg00412.html diff -Nru lintian-2.93.0/tags/l/lacks-ldconfig-trigger.tag lintian-2.89.0ubuntu1/tags/l/lacks-ldconfig-trigger.tag --- lintian-2.93.0/tags/l/lacks-ldconfig-trigger.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/l/lacks-ldconfig-trigger.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,17 +0,0 @@ -Tag: lacks-ldconfig-trigger -Severity: error -Check: shared-libs -Renamed-From: package-must-activate-ldconfig-trigger -Explanation: The package installs shared libraries in a directory controlled by - the dynamic library loader. Therefore, the package must trigger libc's - "ldconfig" trigger to ensure the ldconfig cache is updated. - . - If the package is using debhelper, dh_makeshlibs should - automatically discover this and add the trigger itself. - Otherwise, please add activate-noawait ldconfig to the - triggers file in the control member. - . - Note this tag may trigger for packages built with debhelper before - version 9.20151004. In such case, a simple rebuild will often be - sufficient to fix this issue. -See-Also: policy 8.1.1, https://lists.debian.org/debian-devel/2015/08/msg00412.html diff -Nru lintian-2.93.0/tags/l/lacks-unversioned-link-to-shared-library.desc lintian-2.89.0ubuntu1/tags/l/lacks-unversioned-link-to-shared-library.desc --- lintian-2.93.0/tags/l/lacks-unversioned-link-to-shared-library.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/l/lacks-unversioned-link-to-shared-library.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,20 @@ +Tag: lacks-unversioned-link-to-shared-library +Severity: warning +Check: shared-libs +Renamed-From: dev-pkg-without-shlib-symlink +Info: A "-dev" package is supposed to install a "libsomething.so" symbolic + link referencing the corresponding shared library. Notice how the link name + doesn't include the version number -- this is because such a link is used + by the linker when other programs are built against this shared library. + . + The symlink is generally expected in the same directory as the library + itself. The major exception to this rule is if the library is installed + in (or beneath) /lib, where the symlink must be installed in the + same dir beneath /usr. + . + Example: If the library is installed in /lib/i386-linux-gnu/libXYZ.so.V, + the symlink is expected at /usr/lib/i386-linux-gnu/libXYZ.so. + . + Implementation detail: This tag is emitted for the library package and not + the "-dev" package. +Ref: policy 8.4 diff -Nru lintian-2.93.0/tags/l/lacks-unversioned-link-to-shared-library.tag lintian-2.89.0ubuntu1/tags/l/lacks-unversioned-link-to-shared-library.tag --- lintian-2.93.0/tags/l/lacks-unversioned-link-to-shared-library.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/l/lacks-unversioned-link-to-shared-library.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,20 +0,0 @@ -Tag: lacks-unversioned-link-to-shared-library -Severity: warning -Check: shared-libs -Renamed-From: dev-pkg-without-shlib-symlink -Explanation: A "-dev" package is supposed to install a "libsomething.so" symbolic - link referencing the corresponding shared library. Notice how the link name - doesn't include the version number -- this is because such a link is used - by the linker when other programs are built against this shared library. - . - The symlink is generally expected in the same directory as the library - itself. The major exception to this rule is if the library is installed - in (or beneath) /lib, where the symlink must be installed in the - same dir beneath /usr. - . - Example: If the library is installed in /lib/i386-linux-gnu/libXYZ.so.V, - the symlink is expected at /usr/lib/i386-linux-gnu/libXYZ.so. - . - Implementation detail: This tag is emitted for the library package and not - the "-dev" package. -See-Also: policy 8.4 diff -Nru lintian-2.93.0/tags/l/lacks-versioned-link-to-shared-library.desc lintian-2.89.0ubuntu1/tags/l/lacks-versioned-link-to-shared-library.desc --- lintian-2.93.0/tags/l/lacks-versioned-link-to-shared-library.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/l/lacks-versioned-link-to-shared-library.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: lacks-versioned-link-to-shared-library +Severity: error +Check: shared-libs +Renamed-From: ldconfig-symlink-missing-for-shlib +Info: The package should not only include the shared library itself, but also + the symbolic link which ldconfig would produce. (This is necessary, so + that the link gets removed by dpkg automatically when the package + gets removed.) If the symlink is in the package, check that the SONAME of the + library matches the info in the shlibs file. +Ref: policy 8.1 diff -Nru lintian-2.93.0/tags/l/lacks-versioned-link-to-shared-library.tag lintian-2.89.0ubuntu1/tags/l/lacks-versioned-link-to-shared-library.tag --- lintian-2.93.0/tags/l/lacks-versioned-link-to-shared-library.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/l/lacks-versioned-link-to-shared-library.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,10 +0,0 @@ -Tag: lacks-versioned-link-to-shared-library -Severity: error -Check: shared-libs -Renamed-From: ldconfig-symlink-missing-for-shlib -Explanation: The package should not only include the shared library itself, but also - the symbolic link which ldconfig would produce. (This is necessary, so - that the link gets removed by dpkg automatically when the package - gets removed.) If the symlink is in the package, check that the SONAME of the - library matches the info in the shlibs file. -See-Also: policy 8.1 diff -Nru lintian-2.93.0/tags/l/latest-changelog-entry-without-new-date.desc lintian-2.89.0ubuntu1/tags/l/latest-changelog-entry-without-new-date.desc --- lintian-2.93.0/tags/l/latest-changelog-entry-without-new-date.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/l/latest-changelog-entry-without-new-date.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: latest-changelog-entry-without-new-date +Severity: error +Check: debian/changelog +Info: The latest Debian changelog entry has either the same or even an + older date as the entry before. + . + This can result in subtle bugs due to the SOURCE_DATE_EPOCH + environment variable being the same between the older and newer + versions. diff -Nru lintian-2.93.0/tags/l/latest-changelog-entry-without-new-date.tag lintian-2.89.0ubuntu1/tags/l/latest-changelog-entry-without-new-date.tag --- lintian-2.93.0/tags/l/latest-changelog-entry-without-new-date.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/l/latest-changelog-entry-without-new-date.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: latest-changelog-entry-without-new-date -Severity: error -Check: debian/changelog -Explanation: The latest Debian changelog entry has either the same or even an - older date as the entry before. - . - This can result in subtle bugs due to the SOURCE_DATE_EPOCH - environment variable being the same between the older and newer - versions. diff -Nru lintian-2.93.0/tags/l/latest-debian-changelog-entry-reuses-existing-version.desc lintian-2.89.0ubuntu1/tags/l/latest-debian-changelog-entry-reuses-existing-version.desc --- lintian-2.93.0/tags/l/latest-debian-changelog-entry-reuses-existing-version.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/l/latest-debian-changelog-entry-reuses-existing-version.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,15 @@ +Tag: latest-debian-changelog-entry-reuses-existing-version +Severity: warning +Check: debian/changelog +Info: The latest changelog entry has a version that matches one used in + the specified previous entry. All versions of a source package must be + unique even after a leading epoch has been stripped off. + . + Files generated by the current version of this source package would + conflict with some historical files. This is because the Debian archive + does not allow multiple files with the same name and different contents + and the generated .dsc, .deb, etc. do not embed the epoch in their + filenames. + . + Please pick another version, for example by increasing the Debian + revision. diff -Nru lintian-2.93.0/tags/l/latest-debian-changelog-entry-reuses-existing-version.tag lintian-2.89.0ubuntu1/tags/l/latest-debian-changelog-entry-reuses-existing-version.tag --- lintian-2.93.0/tags/l/latest-debian-changelog-entry-reuses-existing-version.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/l/latest-debian-changelog-entry-reuses-existing-version.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,15 +0,0 @@ -Tag: latest-debian-changelog-entry-reuses-existing-version -Severity: warning -Check: debian/changelog -Explanation: The latest changelog entry has a version that matches one used in - the specified previous entry. All versions of a source package must be - unique even after a leading epoch has been stripped off. - . - Files generated by the current version of this source package would - conflict with some historical files. This is because the Debian archive - does not allow multiple files with the same name and different contents - and the generated .dsc, .deb, etc. do not embed the epoch in their - filenames. - . - Please pick another version, for example by increasing the Debian - revision. diff -Nru lintian-2.93.0/tags/l/latest-debian-changelog-entry-without-new-date.desc lintian-2.89.0ubuntu1/tags/l/latest-debian-changelog-entry-without-new-date.desc --- lintian-2.93.0/tags/l/latest-debian-changelog-entry-without-new-date.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/l/latest-debian-changelog-entry-without-new-date.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: latest-debian-changelog-entry-without-new-date +Severity: error +Check: debian/changelog +Info: The latest Debian changelog entry has either the same or even an + older date as the entry before. + . + This can result in subtle bugs due to the SOURCE_DATE_EPOCH + environment variable being the same between the older and newer + versions. diff -Nru lintian-2.93.0/tags/l/latest-debian-changelog-entry-without-new-date.tag lintian-2.89.0ubuntu1/tags/l/latest-debian-changelog-entry-without-new-date.tag --- lintian-2.93.0/tags/l/latest-debian-changelog-entry-without-new-date.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/l/latest-debian-changelog-entry-without-new-date.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: latest-debian-changelog-entry-without-new-date -Severity: error -Check: debian/changelog -Explanation: The latest Debian changelog entry has either the same or even an - older date as the entry before. - . - This can result in subtle bugs due to the SOURCE_DATE_EPOCH - environment variable being the same between the older and newer - versions. diff -Nru lintian-2.93.0/tags/l/ldconfig-symlink-is-not-a-symlink.desc lintian-2.89.0ubuntu1/tags/l/ldconfig-symlink-is-not-a-symlink.desc --- lintian-2.93.0/tags/l/ldconfig-symlink-is-not-a-symlink.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/l/ldconfig-symlink-is-not-a-symlink.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: ldconfig-symlink-is-not-a-symlink +Severity: error +Check: shared-libs +Info: The package installs a file with the name, ldconfig would use for + the symbolic link to reference the shared library. +Ref: policy 8.1 diff -Nru lintian-2.93.0/tags/l/ldconfig-symlink-is-not-a-symlink.tag lintian-2.89.0ubuntu1/tags/l/ldconfig-symlink-is-not-a-symlink.tag --- lintian-2.93.0/tags/l/ldconfig-symlink-is-not-a-symlink.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/l/ldconfig-symlink-is-not-a-symlink.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: ldconfig-symlink-is-not-a-symlink -Severity: error -Check: shared-libs -Explanation: The package installs a file with the name, ldconfig would use for - the symbolic link to reference the shared library. -See-Also: policy 8.1 diff -Nru lintian-2.93.0/tags/l/ldconfig-symlink-referencing-wrong-file.desc lintian-2.89.0ubuntu1/tags/l/ldconfig-symlink-referencing-wrong-file.desc --- lintian-2.93.0/tags/l/ldconfig-symlink-referencing-wrong-file.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/l/ldconfig-symlink-referencing-wrong-file.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: ldconfig-symlink-referencing-wrong-file +Severity: error +Check: shared-libs +Info: The symbolic link references the wrong file. (It should reference + the shared library.) +Ref: policy 8.1 diff -Nru lintian-2.93.0/tags/l/ldconfig-symlink-referencing-wrong-file.tag lintian-2.89.0ubuntu1/tags/l/ldconfig-symlink-referencing-wrong-file.tag --- lintian-2.93.0/tags/l/ldconfig-symlink-referencing-wrong-file.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/l/ldconfig-symlink-referencing-wrong-file.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: ldconfig-symlink-referencing-wrong-file -Severity: error -Check: shared-libs -Explanation: The symbolic link references the wrong file. (It should reference - the shared library.) -See-Also: policy 8.1 diff -Nru lintian-2.93.0/tags/l/lengthy-symlink.desc lintian-2.89.0ubuntu1/tags/l/lengthy-symlink.desc --- lintian-2.93.0/tags/l/lengthy-symlink.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/l/lengthy-symlink.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: lengthy-symlink +Severity: error +Check: files/symbolic-links +Info: This link goes up, and then back down into the same subdirectory. + Making it shorter will improve its chances of finding the right file + if the user's system has lots of symlinked directories. + . + If you use debhelper, running dh_link after creating the package structure + will fix this problem for you. +Ref: policy 10.5 diff -Nru lintian-2.93.0/tags/l/lengthy-symlink.tag lintian-2.89.0ubuntu1/tags/l/lengthy-symlink.tag --- lintian-2.93.0/tags/l/lengthy-symlink.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/l/lengthy-symlink.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,10 +0,0 @@ -Tag: lengthy-symlink -Severity: error -Check: files/symbolic-links -Explanation: This link goes up, and then back down into the same subdirectory. - Making it shorter will improve its chances of finding the right file - if the user's system has lots of symlinked directories. - . - If you use debhelper, running dh_link after creating the package structure - will fix this problem for you. -See-Also: policy 10.5 diff -Nru lintian-2.93.0/tags/l/libapp-perl-package-name.desc lintian-2.89.0ubuntu1/tags/l/libapp-perl-package-name.desc --- lintian-2.93.0/tags/l/libapp-perl-package-name.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/l/libapp-perl-package-name.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,13 @@ +Tag: libapp-perl-package-name +Severity: error +Certainty: possible +Check: application-not-library +Info: This package contains a program in $PATH and is named + libapp-*-perl which usually implies that the upstream project on CPAN + is under the App:: hierarchy for applications. Instead of + libfoo-bar-perl it should be named foo-bar. + . + People tend to skip library-like named packages when looking for + applications in the package list and hence wouldn't notice this + package. +Ref: https://perl-team.pages.debian.net/policy.html#Package_Naming_Policy diff -Nru lintian-2.93.0/tags/l/libapp-perl-package-name.tag lintian-2.89.0ubuntu1/tags/l/libapp-perl-package-name.tag --- lintian-2.93.0/tags/l/libapp-perl-package-name.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/l/libapp-perl-package-name.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,12 +0,0 @@ -Tag: libapp-perl-package-name -Severity: error -Check: application-not-library -Explanation: This package contains a program in $PATH and is named - libapp-*-perl which usually implies that the upstream project on CPAN - is under the App:: hierarchy for applications. Instead of - libfoo-bar-perl it should be named foo-bar. - . - People tend to skip library-like named packages when looking for - applications in the package list and hence wouldn't notice this - package. -See-Also: https://perl-team.pages.debian.net/policy.html#Package_Naming_Policy diff -Nru lintian-2.93.0/tags/l/libmodule-build-perl-needs-to-be-in-build-depends.desc lintian-2.89.0ubuntu1/tags/l/libmodule-build-perl-needs-to-be-in-build-depends.desc --- lintian-2.93.0/tags/l/libmodule-build-perl-needs-to-be-in-build-depends.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/l/libmodule-build-perl-needs-to-be-in-build-depends.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +# Imported from pkg-perl-tools +Tag: libmodule-build-perl-needs-to-be-in-build-depends +Severity: error +Check: fields/package-relations +Experimental: yes +Info: libmodule-build-perl needs to be in Build-Depends, not in + Build-Depends-Indep, since it's used in the clean target. diff -Nru lintian-2.93.0/tags/l/libmodule-build-perl-needs-to-be-in-build-depends.tag lintian-2.89.0ubuntu1/tags/l/libmodule-build-perl-needs-to-be-in-build-depends.tag --- lintian-2.93.0/tags/l/libmodule-build-perl-needs-to-be-in-build-depends.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/l/libmodule-build-perl-needs-to-be-in-build-depends.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -# Imported from pkg-perl-tools -Tag: libmodule-build-perl-needs-to-be-in-build-depends -Severity: error -Check: fields/package-relations -Experimental: yes -Explanation: libmodule-build-perl needs to be in Build-Depends, not in - Build-Depends-Indep, since it's used in the clean target. diff -Nru lintian-2.93.0/tags/l/libmodule-build-tiny-perl-needs-to-be-in-build-depends.desc lintian-2.89.0ubuntu1/tags/l/libmodule-build-tiny-perl-needs-to-be-in-build-depends.desc --- lintian-2.93.0/tags/l/libmodule-build-tiny-perl-needs-to-be-in-build-depends.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/l/libmodule-build-tiny-perl-needs-to-be-in-build-depends.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +# Imported from pkg-perl-tools +Tag: libmodule-build-tiny-perl-needs-to-be-in-build-depends +Severity: error +Check: fields/package-relations +Experimental: yes +Info: libmodule-build-tiny-perl needs to be in Build-Depends, not + in Build-Depends-Indep, since it's used in the clean target. diff -Nru lintian-2.93.0/tags/l/libmodule-build-tiny-perl-needs-to-be-in-build-depends.tag lintian-2.89.0ubuntu1/tags/l/libmodule-build-tiny-perl-needs-to-be-in-build-depends.tag --- lintian-2.93.0/tags/l/libmodule-build-tiny-perl-needs-to-be-in-build-depends.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/l/libmodule-build-tiny-perl-needs-to-be-in-build-depends.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -# Imported from pkg-perl-tools -Tag: libmodule-build-tiny-perl-needs-to-be-in-build-depends -Severity: error -Check: fields/package-relations -Experimental: yes -Explanation: libmodule-build-tiny-perl needs to be in Build-Depends, not - in Build-Depends-Indep, since it's used in the clean target. diff -Nru lintian-2.93.0/tags/l/library-in-root-and-usr.desc lintian-2.89.0ubuntu1/tags/l/library-in-root-and-usr.desc --- lintian-2.93.0/tags/l/library-in-root-and-usr.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/l/library-in-root-and-usr.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,12 @@ +Tag: library-in-root-and-usr +Severity: error +Check: usrmerge +Info: The package ships two files with the same name installed both in + /lib*/ and /usr/lib*/ (or their subdirectories). + This is not useful and is incompatible with the merged /usr directories + scheme. + . + Shared library files, both static and dynamic, must be installed in + the correct directories as documented in Policy 8.1. +Ref: https://wiki.debian.org/UsrMerge, + policy 8.1 diff -Nru lintian-2.93.0/tags/l/library-in-root-and-usr.tag lintian-2.89.0ubuntu1/tags/l/library-in-root-and-usr.tag --- lintian-2.93.0/tags/l/library-in-root-and-usr.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/l/library-in-root-and-usr.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,12 +0,0 @@ -Tag: library-in-root-and-usr -Severity: error -Check: usrmerge -Explanation: The package ships two files with the same name installed both in - /lib*/ and /usr/lib*/ (or their subdirectories). - This is not useful and is incompatible with the merged /usr directories - scheme. - . - Shared library files, both static and dynamic, must be installed in - the correct directories as documented in Policy 8.1. -See-Also: https://wiki.debian.org/UsrMerge, - policy 8.1 diff -Nru lintian-2.93.0/tags/l/library-not-linked-against-libc.desc lintian-2.89.0ubuntu1/tags/l/library-not-linked-against-libc.desc --- lintian-2.93.0/tags/l/library-not-linked-against-libc.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/l/library-not-linked-against-libc.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,13 @@ +Tag: library-not-linked-against-libc +Severity: error +Certainty: possible +Check: binaries +Ref: policy 10.2, #698720 +Info: The package installs a library which is not dynamically linked + against libc. + . + It is theoretically possible to have a library which doesn't use any + symbols from libc, but it is far more likely that this is a violation + of the requirement that "shared libraries must be linked against all + libraries that they use symbols from in the same way that binaries + are". diff -Nru lintian-2.93.0/tags/l/library-not-linked-against-libc.tag lintian-2.89.0ubuntu1/tags/l/library-not-linked-against-libc.tag --- lintian-2.93.0/tags/l/library-not-linked-against-libc.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/l/library-not-linked-against-libc.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,12 +0,0 @@ -Tag: library-not-linked-against-libc -Severity: error -Check: binaries -See-Also: policy 10.2, Bug#698720 -Explanation: The package installs a library which is not dynamically linked - against libc. - . - It is theoretically possible to have a library which doesn't use any - symbols from libc, but it is far more likely that this is a violation - of the requirement that "shared libraries must be linked against all - libraries that they use symbols from in the same way that binaries - are". diff -Nru lintian-2.93.0/tags/l/library-package-name-for-application.desc lintian-2.89.0ubuntu1/tags/l/library-package-name-for-application.desc --- lintian-2.93.0/tags/l/library-package-name-for-application.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/l/library-package-name-for-application.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,16 @@ +Tag: library-package-name-for-application +Severity: info +Certainty: wild-guess +Check: application-not-library +Experimental: yes +Info: This package contains a program in $PATH but is named like a + library. E.g. instead of libfoo-bar-perl it should be named just + foo-bar. + . + People tend to skip library-like named packages when looking for + applications in the package list and hence wouldn't notice this + package. See the reference for some (not perl-specific) reasoning. + . + In case the program in $PATH is only a helper tool and the package is + primarily a library, please add a Lintian override for this tag. +Ref: https://perl-team.pages.debian.net/policy.html#Package_Naming_Policy diff -Nru lintian-2.93.0/tags/l/library-package-name-for-application.tag lintian-2.89.0ubuntu1/tags/l/library-package-name-for-application.tag --- lintian-2.93.0/tags/l/library-package-name-for-application.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/l/library-package-name-for-application.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,15 +0,0 @@ -Tag: library-package-name-for-application -Severity: info -Check: application-not-library -Experimental: yes -Explanation: This package contains a program in $PATH but is named like a - library. E.g. instead of libfoo-bar-perl it should be named just - foo-bar. - . - People tend to skip library-like named packages when looking for - applications in the package list and hence wouldn't notice this - package. See the reference for some (not perl-specific) reasoning. - . - In case the program in $PATH is only a helper tool and the package is - primarily a library, please add a Lintian override for this tag. -See-Also: https://perl-team.pages.debian.net/policy.html#Package_Naming_Policy diff -Nru lintian-2.93.0/tags/l/lib-recommends-documentation.desc lintian-2.89.0ubuntu1/tags/l/lib-recommends-documentation.desc --- lintian-2.93.0/tags/l/lib-recommends-documentation.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/l/lib-recommends-documentation.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,13 @@ +Tag: lib-recommends-documentation +Severity: warning +Certainty: possible +Check: fields/package-relations +Info: The given package appears to be a library package, but it recommends + a documentation package. Doing this can pull in unwanted (and often + large) documentation packages since recommends are installed by default + and library packages are pulled by applications that use them. Users + usually only care about the library documentation if they're developing + against the library, not just using it, so the development package should + recommend the documentation instead. If there is no development package + (for modules for scripting languages, for example), consider Suggests + instead of Recommends. diff -Nru lintian-2.93.0/tags/l/lib-recommends-documentation.tag lintian-2.89.0ubuntu1/tags/l/lib-recommends-documentation.tag --- lintian-2.93.0/tags/l/lib-recommends-documentation.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/l/lib-recommends-documentation.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,12 +0,0 @@ -Tag: lib-recommends-documentation -Severity: warning -Check: fields/package-relations -Explanation: The given package appears to be a library package, but it recommends - a documentation package. Doing this can pull in unwanted (and often - large) documentation packages since recommends are installed by default - and library packages are pulled by applications that use them. Users - usually only care about the library documentation if they're developing - against the library, not just using it, so the development package should - recommend the documentation instead. If there is no development package - (for modules for scripting languages, for example), consider Suggests - instead of Recommends. diff -Nru lintian-2.93.0/tags/l/license-file-listed-in-debian-copyright.desc lintian-2.89.0ubuntu1/tags/l/license-file-listed-in-debian-copyright.desc --- lintian-2.93.0/tags/l/license-file-listed-in-debian-copyright.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/l/license-file-listed-in-debian-copyright.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: license-file-listed-in-debian-copyright +Severity: info +Check: debian/copyright/dep5 +Info: A file containing a software license is listed in + debian/copyright. That is not necessary. Please remove + the entry referring to the license file. diff -Nru lintian-2.93.0/tags/l/license-file-listed-in-debian-copyright.tag lintian-2.89.0ubuntu1/tags/l/license-file-listed-in-debian-copyright.tag --- lintian-2.93.0/tags/l/license-file-listed-in-debian-copyright.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/l/license-file-listed-in-debian-copyright.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: license-file-listed-in-debian-copyright -Severity: info -Check: debian/copyright/dep5 -Explanation: A file containing a software license is listed in - debian/copyright. That is not necessary. Please remove - the entry referring to the license file. diff -Nru lintian-2.93.0/tags/l/license-problem-bad-php-license.desc lintian-2.89.0ubuntu1/tags/l/license-problem-bad-php-license.desc --- lintian-2.93.0/tags/l/license-problem-bad-php-license.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/l/license-problem-bad-php-license.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,11 @@ +Tag: license-problem-bad-php-license +Severity: error +Certainty: possible +Check: cruft +Info: This package appears to be covered by version 2.x of the PHP license, + which is not appropriate for anything other than the PHP interpreter + itself. + . + Note that PEAR modules are not a part of the PHP interpreter and cannot + use this license. +Ref: https://ftp-master.debian.org/REJECT-FAQ.html, #616436 diff -Nru lintian-2.93.0/tags/l/license-problem-bad-php-license.tag lintian-2.89.0ubuntu1/tags/l/license-problem-bad-php-license.tag --- lintian-2.93.0/tags/l/license-problem-bad-php-license.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/l/license-problem-bad-php-license.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,10 +0,0 @@ -Tag: license-problem-bad-php-license -Severity: error -Check: cruft -Explanation: This package appears to be covered by version 2.x of the PHP license, - which is not appropriate for anything other than the PHP interpreter - itself. - . - Note that PEAR modules are not a part of the PHP interpreter and cannot - use this license. -See-Also: https://ftp-master.debian.org/REJECT-FAQ.html, Bug#616436 diff -Nru lintian-2.93.0/tags/l/license-problem-cc-by-nc-sa.desc lintian-2.89.0ubuntu1/tags/l/license-problem-cc-by-nc-sa.desc --- lintian-2.93.0/tags/l/license-problem-cc-by-nc-sa.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/l/license-problem-cc-by-nc-sa.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: license-problem-cc-by-nc-sa +Severity: error +Certainty: possible +Check: cruft +Info: The given source file is copyrighted under the non-free + Creative Commons Non-Commercial Share-Alike (CC-NC-SA) license. diff -Nru lintian-2.93.0/tags/l/license-problem-cc-by-nc-sa.tag lintian-2.89.0ubuntu1/tags/l/license-problem-cc-by-nc-sa.tag --- lintian-2.93.0/tags/l/license-problem-cc-by-nc-sa.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/l/license-problem-cc-by-nc-sa.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,5 +0,0 @@ -Tag: license-problem-cc-by-nc-sa -Severity: error -Check: cruft -Explanation: The given source file is copyrighted under the non-free - Creative Commons Non-Commercial Share-Alike (CC-NC-SA) license. diff -Nru lintian-2.93.0/tags/l/license-problem-convert-utf-code.desc lintian-2.89.0ubuntu1/tags/l/license-problem-convert-utf-code.desc --- lintian-2.93.0/tags/l/license-problem-convert-utf-code.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/l/license-problem-convert-utf-code.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,16 @@ +Tag: license-problem-convert-utf-code +Severity: error +Certainty: possible +Check: cruft +Info: The following file source files include material under a + non-free license from Unicode Inc. Therefore, it is + not possible to ship this in main or contrib. + . + This license does not grant any permission + to modify the files (thus failing DFSG#3). Moreover, the license grant + seems to attempt to restrict use to "products supporting the Unicode + Standard" (thus failing DFSG#6). + . + In this case a solution is to use libicu and to remove this code + by repacking. +Ref: #823100 diff -Nru lintian-2.93.0/tags/l/license-problem-convert-utf-code.tag lintian-2.89.0ubuntu1/tags/l/license-problem-convert-utf-code.tag --- lintian-2.93.0/tags/l/license-problem-convert-utf-code.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/l/license-problem-convert-utf-code.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,15 +0,0 @@ -Tag: license-problem-convert-utf-code -Severity: error -Check: cruft -Explanation: The following file source files include material under a - non-free license from Unicode Inc. Therefore, it is - not possible to ship this in main or contrib. - . - This license does not grant any permission - to modify the files (thus failing DFSG#3). Moreover, the license grant - seems to attempt to restrict use to "products supporting the Unicode - Standard" (thus failing DFSG#6). - . - In this case a solution is to use libicu and to remove this code - by repacking. -See-Also: Bug#823100 diff -Nru lintian-2.93.0/tags/l/license-problem-font-adobe-copyrighted-fragment.desc lintian-2.89.0ubuntu1/tags/l/license-problem-font-adobe-copyrighted-fragment.desc --- lintian-2.93.0/tags/l/license-problem-font-adobe-copyrighted-fragment.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/l/license-problem-font-adobe-copyrighted-fragment.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: license-problem-font-adobe-copyrighted-fragment +Severity: error +Certainty: possible +Check: fonts/postscript/type1 +Info: This type 1 font file includes some postscript fragment with a + non-free license of Adobe. In order to check if this tag is genuine + please follow the procedure described in the reference. + . + Should this be a false-positive, please override the tag. +Ref: https://wiki.debian.org/qa.debian.org/type1nondfsg diff -Nru lintian-2.93.0/tags/l/license-problem-font-adobe-copyrighted-fragment-no-credit.desc lintian-2.89.0ubuntu1/tags/l/license-problem-font-adobe-copyrighted-fragment-no-credit.desc --- lintian-2.93.0/tags/l/license-problem-font-adobe-copyrighted-fragment-no-credit.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/l/license-problem-font-adobe-copyrighted-fragment-no-credit.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,13 @@ +Tag: license-problem-font-adobe-copyrighted-fragment-no-credit +Severity: error +Certainty: possible +Check: fonts/postscript/type1 +Info: This type 1 font file includes some postscript fragment with a + non-free license of Adobe. In order to check if this tag is genuine + please follow the procedure described in the reference. + . + Moreover the fragment was likely verbatim copied from black + book without any credit to Adobe. + . + Should this be a false-positive, please override the tag. +Ref: https://wiki.debian.org/qa.debian.org/type1nondfsg diff -Nru lintian-2.93.0/tags/l/license-problem-font-adobe-copyrighted-fragment-no-credit.tag lintian-2.89.0ubuntu1/tags/l/license-problem-font-adobe-copyrighted-fragment-no-credit.tag --- lintian-2.93.0/tags/l/license-problem-font-adobe-copyrighted-fragment-no-credit.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/l/license-problem-font-adobe-copyrighted-fragment-no-credit.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,12 +0,0 @@ -Tag: license-problem-font-adobe-copyrighted-fragment-no-credit -Severity: error -Check: fonts/postscript/type1 -Explanation: This type 1 font file includes some postscript fragment with a - non-free license of Adobe. In order to check if this tag is genuine - please follow the procedure described in the reference. - . - Moreover the fragment was likely verbatim copied from black - book without any credit to Adobe. - . - Should this be a false-positive, please override the tag. -See-Also: https://wiki.debian.org/qa.debian.org/type1nondfsg diff -Nru lintian-2.93.0/tags/l/license-problem-font-adobe-copyrighted-fragment.tag lintian-2.89.0ubuntu1/tags/l/license-problem-font-adobe-copyrighted-fragment.tag --- lintian-2.93.0/tags/l/license-problem-font-adobe-copyrighted-fragment.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/l/license-problem-font-adobe-copyrighted-fragment.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: license-problem-font-adobe-copyrighted-fragment -Severity: error -Check: fonts/postscript/type1 -Explanation: This type 1 font file includes some postscript fragment with a - non-free license of Adobe. In order to check if this tag is genuine - please follow the procedure described in the reference. - . - Should this be a false-positive, please override the tag. -See-Also: https://wiki.debian.org/qa.debian.org/type1nondfsg diff -Nru lintian-2.93.0/tags/l/license-problem-gfdl-invariants.desc lintian-2.89.0ubuntu1/tags/l/license-problem-gfdl-invariants.desc --- lintian-2.93.0/tags/l/license-problem-gfdl-invariants.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/l/license-problem-gfdl-invariants.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,13 @@ +Tag: license-problem-gfdl-invariants +Severity: error +Certainty: possible +Check: cruft +Info: The given source file is licensed under GFDL with invariant + section or front-cover or back-cover text. + . + GFDL with invariant sections, front-cover or back-cover texts are not + suitable for main. + . + If this file be multi-licensed, please override the tag. +Ref: https://wiki.debian.org/qa.debian.org/gfdlinvariant, + https://www.debian.org/vote/2006/vote_001 diff -Nru lintian-2.93.0/tags/l/license-problem-gfdl-invariants-empty.desc lintian-2.89.0ubuntu1/tags/l/license-problem-gfdl-invariants-empty.desc --- lintian-2.93.0/tags/l/license-problem-gfdl-invariants-empty.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/l/license-problem-gfdl-invariants-empty.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,12 @@ +Tag: license-problem-gfdl-invariants-empty +Severity: info +Certainty: possible +Check: cruft +Info: The given source file is licensed under GFDL, but without any + precision about the presence of invariant sections, front-cover or + back-cover text. + . + GFDL license explicitly requests you to document this non-presence. + . +Ref: https://wiki.debian.org/qa.debian.org/gfdlinvariant, + https://www.debian.org/vote/2006/vote_001 diff -Nru lintian-2.93.0/tags/l/license-problem-gfdl-invariants-empty.tag lintian-2.89.0ubuntu1/tags/l/license-problem-gfdl-invariants-empty.tag --- lintian-2.93.0/tags/l/license-problem-gfdl-invariants-empty.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/l/license-problem-gfdl-invariants-empty.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,11 +0,0 @@ -Tag: license-problem-gfdl-invariants-empty -Severity: info -Check: cruft -Explanation: The given source file is licensed under GFDL, but without any - precision about the presence of invariant sections, front-cover or - back-cover text. - . - GFDL license explicitly requests you to document this non-presence. - . -See-Also: https://wiki.debian.org/qa.debian.org/gfdlinvariant, - https://www.debian.org/vote/2006/vote_001 diff -Nru lintian-2.93.0/tags/l/license-problem-gfdl-invariants.tag lintian-2.89.0ubuntu1/tags/l/license-problem-gfdl-invariants.tag --- lintian-2.93.0/tags/l/license-problem-gfdl-invariants.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/l/license-problem-gfdl-invariants.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,12 +0,0 @@ -Tag: license-problem-gfdl-invariants -Severity: error -Check: cruft -Explanation: The given source file is licensed under GFDL with invariant - section or front-cover or back-cover text. - . - GFDL with invariant sections, front-cover or back-cover texts are not - suitable for main. - . - If this file be multi-licensed, please override the tag. -See-Also: https://wiki.debian.org/qa.debian.org/gfdlinvariant, - https://www.debian.org/vote/2006/vote_001 diff -Nru lintian-2.93.0/tags/l/license-problem-gfdl-non-official-text.desc lintian-2.89.0ubuntu1/tags/l/license-problem-gfdl-non-official-text.desc --- lintian-2.93.0/tags/l/license-problem-gfdl-non-official-text.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/l/license-problem-gfdl-non-official-text.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: license-problem-gfdl-non-official-text +Severity: pedantic +Certainty: possible +Check: cruft +Info: The given source file is licensed under GFDL, but using a + non-official text for the "no invariant sections" part. + . + Please ask upstream to always use (case insensitive): + with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. diff -Nru lintian-2.93.0/tags/l/license-problem-gfdl-non-official-text.tag lintian-2.89.0ubuntu1/tags/l/license-problem-gfdl-non-official-text.tag --- lintian-2.93.0/tags/l/license-problem-gfdl-non-official-text.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/l/license-problem-gfdl-non-official-text.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: license-problem-gfdl-non-official-text -Severity: pedantic -Check: cruft -Explanation: The given source file is licensed under GFDL, but using a - non-official text for the "no invariant sections" part. - . - Please ask upstream to always use (case insensitive): - with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. diff -Nru lintian-2.93.0/tags/l/license-problem-json-evil.desc lintian-2.89.0ubuntu1/tags/l/license-problem-json-evil.desc --- lintian-2.93.0/tags/l/license-problem-json-evil.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/l/license-problem-json-evil.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: license-problem-json-evil +Severity: error +Certainty: possible +Check: cruft +Info: The given source file is copyrighted under the non-free + license of json and the infamous clause: + The Software shall be used for Good, not Evil. +Ref: https://wiki.debian.org/qa.debian.org/jsonevil diff -Nru lintian-2.93.0/tags/l/license-problem-json-evil.tag lintian-2.89.0ubuntu1/tags/l/license-problem-json-evil.tag --- lintian-2.93.0/tags/l/license-problem-json-evil.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/l/license-problem-json-evil.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: license-problem-json-evil -Severity: error -Check: cruft -Explanation: The given source file is copyrighted under the non-free - license of json and the infamous clause: - The Software shall be used for Good, not Evil. -See-Also: https://wiki.debian.org/qa.debian.org/jsonevil diff -Nru lintian-2.93.0/tags/l/license-problem-md5sum-non-distributable-file.desc lintian-2.89.0ubuntu1/tags/l/license-problem-md5sum-non-distributable-file.desc --- lintian-2.93.0/tags/l/license-problem-md5sum-non-distributable-file.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/l/license-problem-md5sum-non-distributable-file.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,12 @@ +Tag: license-problem-md5sum-non-distributable-file +Severity: error +Check: cruft +Info: The following file is not distributable even in the non-free + archive. + . + Please re-package the package without the file (if possible) + or ask the FTP-masters to remove the package. + . + If the package has been uploaded to Debian before, please + remember to also notify snapshot.debian.org about this + package containing a non-distributable file. diff -Nru lintian-2.93.0/tags/l/license-problem-md5sum-non-distributable-file.tag lintian-2.89.0ubuntu1/tags/l/license-problem-md5sum-non-distributable-file.tag --- lintian-2.93.0/tags/l/license-problem-md5sum-non-distributable-file.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/l/license-problem-md5sum-non-distributable-file.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,12 +0,0 @@ -Tag: license-problem-md5sum-non-distributable-file -Severity: error -Check: cruft -Explanation: The following file is not distributable even in the non-free - archive. - . - Please re-package the package without the file (if possible) - or ask the FTP-masters to remove the package. - . - If the package has been uploaded to Debian before, please - remember to also notify snapshot.debian.org about this - package containing a non-distributable file. diff -Nru lintian-2.93.0/tags/l/license-problem-md5sum-non-free-file.desc lintian-2.89.0ubuntu1/tags/l/license-problem-md5sum-non-free-file.desc --- lintian-2.93.0/tags/l/license-problem-md5sum-non-free-file.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/l/license-problem-md5sum-non-free-file.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: license-problem-md5sum-non-free-file +Severity: error +Check: cruft +Info: The following file is not suitable for main or contrib. + . + Please re-package the package without the file (if possible) + or ask the FTP-masters to remove the package. + . + You could also split this package and move this file into the + non-free archive. diff -Nru lintian-2.93.0/tags/l/license-problem-md5sum-non-free-file.tag lintian-2.89.0ubuntu1/tags/l/license-problem-md5sum-non-free-file.tag --- lintian-2.93.0/tags/l/license-problem-md5sum-non-free-file.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/l/license-problem-md5sum-non-free-file.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,10 +0,0 @@ -Tag: license-problem-md5sum-non-free-file -Severity: error -Check: cruft -Explanation: The following file is not suitable for main or contrib. - . - Please re-package the package without the file (if possible) - or ask the FTP-masters to remove the package. - . - You could also split this package and move this file into the - non-free archive. diff -Nru lintian-2.93.0/tags/l/license-problem-non-free-img-lenna.desc lintian-2.89.0ubuntu1/tags/l/license-problem-non-free-img-lenna.desc --- lintian-2.93.0/tags/l/license-problem-non-free-img-lenna.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/l/license-problem-non-free-img-lenna.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,24 @@ +Tag: license-problem-non-free-img-lenna +Severity: error +Certainty: possible +Check: cruft +Ref: https://en.wikipedia.org/wiki/Lenna, https://www.debian.org/vote/2012/vote_002, #771191 +Info: The given source file is cropped from a Playboy centerfold. + . + This image is a picture of Lena Söderberg, + shot by photographer Dwight Hooker, cropped from + the centerfold of the November 1972 issue of Playboy magazine. + . + According to Hutchison, Jamie (May-June 2001). "Culture, + Communication, and an Information Age Madonna" (PDF). + IEEE Professional Communication Society Newsletter 45 (3). + (page 5 second column second paragraph), this image is + distributable but not free. + . + Moreover, Lenna photo has been pointed to as an example + of sexism in the sciences, reinforcing gender stereotypes. + . + Please use well known and free test images. + . + Please also submit the md5sum, sha1sum, and sha256 of this file + as a bug report for Lintian. diff -Nru lintian-2.93.0/tags/l/license-problem-non-free-img-lenna.tag lintian-2.89.0ubuntu1/tags/l/license-problem-non-free-img-lenna.tag --- lintian-2.93.0/tags/l/license-problem-non-free-img-lenna.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/l/license-problem-non-free-img-lenna.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,23 +0,0 @@ -Tag: license-problem-non-free-img-lenna -Severity: error -Check: cruft -See-Also: https://en.wikipedia.org/wiki/Lenna, https://www.debian.org/vote/2012/vote_002, Bug#771191 -Explanation: The given source file is cropped from a Playboy centerfold. - . - This image is a picture of Lena Söderberg, - shot by photographer Dwight Hooker, cropped from - the centerfold of the November 1972 issue of Playboy magazine. - . - According to Hutchison, Jamie (May-June 2001). "Culture, - Communication, and an Information Age Madonna" (PDF). - IEEE Professional Communication Society Newsletter 45 (3). - (page 5 second column second paragraph), this image is - distributable but not free. - . - Moreover, Lenna photo has been pointed to as an example - of sexism in the sciences, reinforcing gender stereotypes. - . - Please use well known and free test images. - . - Please also submit the md5sum, sha1sum, and sha256 of this file - as a bug report for Lintian. diff -Nru lintian-2.93.0/tags/l/license-problem-non-free-RFC-BCP78.desc lintian-2.89.0ubuntu1/tags/l/license-problem-non-free-RFC-BCP78.desc --- lintian-2.93.0/tags/l/license-problem-non-free-RFC-BCP78.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/l/license-problem-non-free-RFC-BCP78.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,12 @@ +Tag: license-problem-non-free-RFC-BCP78 +Severity: error +Certainty: possible +Check: cruft +Info: The given source file is licensed under the non-free RFC + license (BCP78). + . + The majority of IETF documents, such as RFCs, are not licensed + under DFSG-free terms, and should thus not be included in Debian main. + . + If this file is multi-licensed, please override the tag. +Ref: https://wiki.debian.org/NonFreeIETFDocuments diff -Nru lintian-2.93.0/tags/l/license-problem-non-free-RFC-BCP78.tag lintian-2.89.0ubuntu1/tags/l/license-problem-non-free-RFC-BCP78.tag --- lintian-2.93.0/tags/l/license-problem-non-free-RFC-BCP78.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/l/license-problem-non-free-RFC-BCP78.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,11 +0,0 @@ -Tag: license-problem-non-free-RFC-BCP78 -Severity: error -Check: cruft -Explanation: The given source file is licensed under the non-free RFC - license (BCP78). - . - The majority of IETF documents, such as RFCs, are not licensed - under DFSG-free terms, and should thus not be included in Debian main. - . - If this file is multi-licensed, please override the tag. -See-Also: https://wiki.debian.org/NonFreeIETFDocuments diff -Nru lintian-2.93.0/tags/l/license-problem-non-free-RFC.desc lintian-2.89.0ubuntu1/tags/l/license-problem-non-free-RFC.desc --- lintian-2.93.0/tags/l/license-problem-non-free-RFC.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/l/license-problem-non-free-RFC.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,12 @@ +Tag: license-problem-non-free-RFC +Severity: error +Certainty: possible +Check: cruft +Info: The given source file is licensed under the newer RFC + license. + . + The majority of IETF documents, such as RFCs, are not licensed + under DFSG-free terms, and should thus not be included in Debian main. + . + If this file is multi-licensed, please override the tag. +Ref: https://wiki.debian.org/NonFreeIETFDocuments diff -Nru lintian-2.93.0/tags/l/license-problem-non-free-RFC.tag lintian-2.89.0ubuntu1/tags/l/license-problem-non-free-RFC.tag --- lintian-2.93.0/tags/l/license-problem-non-free-RFC.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/l/license-problem-non-free-RFC.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,11 +0,0 @@ -Tag: license-problem-non-free-RFC -Severity: error -Check: cruft -Explanation: The given source file is licensed under the newer RFC - license. - . - The majority of IETF documents, such as RFCs, are not licensed - under DFSG-free terms, and should thus not be included in Debian main. - . - If this file is multi-licensed, please override the tag. -See-Also: https://wiki.debian.org/NonFreeIETFDocuments diff -Nru lintian-2.93.0/tags/l/license-problem-nvidia-intellectual.desc lintian-2.89.0ubuntu1/tags/l/license-problem-nvidia-intellectual.desc --- lintian-2.93.0/tags/l/license-problem-nvidia-intellectual.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/l/license-problem-nvidia-intellectual.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,15 @@ +Tag: license-problem-nvidia-intellectual +Severity: error +Certainty: possible +Check: cruft +Info: The following source files include material under a + non-distributable license from Nvidia. Therefore, it is + not even possible to ship this in non-free. + . + Please re-package the package without the file (if possible) + or ask the FTP-masters to remove the package. + . + If the package has been uploaded to Debian before, please + remember to also notify snapshot.debian.org about this + package containing a non-distributable file. +Ref: https://bugs.debian.org/724930#27 diff -Nru lintian-2.93.0/tags/l/license-problem-nvidia-intellectual.tag lintian-2.89.0ubuntu1/tags/l/license-problem-nvidia-intellectual.tag --- lintian-2.93.0/tags/l/license-problem-nvidia-intellectual.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/l/license-problem-nvidia-intellectual.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,14 +0,0 @@ -Tag: license-problem-nvidia-intellectual -Severity: error -Check: cruft -Explanation: The following source files include material under a - non-distributable license from Nvidia. Therefore, it is - not even possible to ship this in non-free. - . - Please re-package the package without the file (if possible) - or ask the FTP-masters to remove the package. - . - If the package has been uploaded to Debian before, please - remember to also notify snapshot.debian.org about this - package containing a non-distributable file. -See-Also: https://bugs.debian.org/724930#27 diff -Nru lintian-2.93.0/tags/l/license-problem-php-license.desc lintian-2.89.0ubuntu1/tags/l/license-problem-php-license.desc --- lintian-2.93.0/tags/l/license-problem-php-license.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/l/license-problem-php-license.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,11 @@ +Tag: license-problem-php-license +Severity: error +Certainty: possible +Check: cruft +Info: This package appears to be covered by version 3.0 (exactly) of the + PHP license. This license is not applicable to anything that is not PHP + and has no contributions from the PHP Group. + . + This tag is not emitted for packages from pecl.php.net as determined by + the Source: field in debian/copyright. +Ref: https://ftp-master.debian.org/REJECT-FAQ.html diff -Nru lintian-2.93.0/tags/l/license-problem-php-license.tag lintian-2.89.0ubuntu1/tags/l/license-problem-php-license.tag --- lintian-2.93.0/tags/l/license-problem-php-license.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/l/license-problem-php-license.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,10 +0,0 @@ -Tag: license-problem-php-license -Severity: error -Check: cruft -Explanation: This package appears to be covered by version 3.0 (exactly) of the - PHP license. This license is not applicable to anything that is not PHP - and has no contributions from the PHP Group. - . - This tag is not emitted for packages from pecl.php.net as determined by - the Source: field in debian/copyright. -See-Also: https://ftp-master.debian.org/REJECT-FAQ.html diff -Nru lintian-2.93.0/tags/l/license-problem-undefined-license.desc lintian-2.89.0ubuntu1/tags/l/license-problem-undefined-license.desc --- lintian-2.93.0/tags/l/license-problem-undefined-license.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/l/license-problem-undefined-license.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,21 @@ +Tag: license-problem-undefined-license +Severity: error +Certainty: possible +Check: debian/copyright/dep5 +Ref: https://ftp-master.debian.org/REJECT-FAQ.html +Info: Your copyright file references a license that is not defined. + Due to copyright law or treaties, files that are not available under + a defined license are non-free and non-re-distributable. + . + Referencing an undefined license could mean the file cannot be + distributed in Debian or it could simply mean that the existing + license needs to be documented. In both cases, + the copyright file should be updated to reflect reality. + . + Please re-package the package without the file (if possible) + or ask the FTP-masters to remove the package. + . + If the package has been uploaded to Debian before, and if + affected files cannot be distributed in Debian please + remember to also notify snapshot.debian.org about this + package containing a non-distributable file. diff -Nru lintian-2.93.0/tags/l/license-problem-undefined-license.tag lintian-2.89.0ubuntu1/tags/l/license-problem-undefined-license.tag --- lintian-2.93.0/tags/l/license-problem-undefined-license.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/l/license-problem-undefined-license.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,20 +0,0 @@ -Tag: license-problem-undefined-license -Severity: error -Check: debian/copyright/dep5 -See-Also: https://ftp-master.debian.org/REJECT-FAQ.html -Explanation: Your copyright file references a license that is not defined. - Due to copyright law or treaties, files that are not available under - a defined license are non-free and non-re-distributable. - . - Referencing an undefined license could mean the file cannot be - distributed in Debian or it could simply mean that the existing - license needs to be documented. In both cases, - the copyright file should be updated to reflect reality. - . - Please re-package the package without the file (if possible) - or ask the FTP-masters to remove the package. - . - If the package has been uploaded to Debian before, and if - affected files cannot be distributed in Debian please - remember to also notify snapshot.debian.org about this - package containing a non-distributable file. diff -Nru lintian-2.93.0/tags/l/linked-with-obsolete-library.desc lintian-2.89.0ubuntu1/tags/l/linked-with-obsolete-library.desc --- lintian-2.93.0/tags/l/linked-with-obsolete-library.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/l/linked-with-obsolete-library.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,20 @@ +Tag: linked-with-obsolete-library +Severity: info +Check: libraries/shared/obsolete +Info: This tag is currently only issued for libcblas.so. For an explanation, + please continue below. + . + The symbols in libcblas.so, which represent the CBLAS API, + were merged into libblas.so. (Note the missing letter C.) + Please use libblas.so instead. + . + The old library is still being shipped until all packages have modified + their build systems, but it is not managed by update-alternatives + and may result in poor performance. Please do not use it anymore. + . + Some packages may require functionality specific to Atlas3, which is not + implemented by other BLAS/CBLAS alternatives. Please override the + tag if your package falls into that category. +Ref: https://wiki.debian.org/DebianScience/LinearAlgebraLibraries , + https://lists.debian.org/debian-devel/2019/10/msg00273.html , + https://salsa.debian.org/science-team/lapack/-/blob/master/debian/README.if-you-look-for-libcblas.so.3 diff -Nru lintian-2.93.0/tags/l/linked-with-obsolete-library.tag lintian-2.89.0ubuntu1/tags/l/linked-with-obsolete-library.tag --- lintian-2.93.0/tags/l/linked-with-obsolete-library.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/l/linked-with-obsolete-library.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,20 +0,0 @@ -Tag: linked-with-obsolete-library -Severity: info -Check: libraries/shared/obsolete -Explanation: This tag is currently only issued for libcblas.so. For an explanation, - please continue below. - . - The symbols in libcblas.so, which represent the CBLAS API, - were merged into libblas.so. (Note the missing letter C.) - Please use libblas.so instead. - . - The old library is still being shipped until all packages have modified - their build systems, but it is not managed by update-alternatives - and may result in poor performance. Please do not use it anymore. - . - Some packages may require functionality specific to Atlas3, which is not - implemented by other BLAS/CBLAS alternatives. Please override the - tag if your package falls into that category. -See-Also: https://wiki.debian.org/DebianScience/LinearAlgebraLibraries , - https://lists.debian.org/debian-devel/2019/10/msg00273.html , - https://salsa.debian.org/science-team/lapack/-/blob/master/debian/README.if-you-look-for-libcblas.so.3 diff -Nru lintian-2.93.0/tags/l/link-to-shared-library-in-wrong-package.desc lintian-2.89.0ubuntu1/tags/l/link-to-shared-library-in-wrong-package.desc --- lintian-2.93.0/tags/l/link-to-shared-library-in-wrong-package.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/l/link-to-shared-library-in-wrong-package.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,18 @@ +Tag: link-to-shared-library-in-wrong-package +Severity: warning +Certainty: possible +Check: shared-libs +Renamed-From: non-dev-pkg-with-shlib-symlink +Info: Although this package is not a "-dev" package, it installs a + "libsomething.so" symbolic link referencing the corresponding shared + library. When the link doesn't include the version number, it is used by + the linker when other programs are built against this shared library. + . + Shared libraries are supposed to place such symbolic links in their + respective "-dev" packages, so it is a bug to include it with the main + library package. + . + However, if this is a small package which includes the runtime and the + development libraries, this is not a bug. In the latter case, please + override this warning. +Ref: policy 8.4 diff -Nru lintian-2.93.0/tags/l/link-to-shared-library-in-wrong-package.tag lintian-2.89.0ubuntu1/tags/l/link-to-shared-library-in-wrong-package.tag --- lintian-2.93.0/tags/l/link-to-shared-library-in-wrong-package.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/l/link-to-shared-library-in-wrong-package.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,17 +0,0 @@ -Tag: link-to-shared-library-in-wrong-package -Severity: warning -Check: shared-libs -Renamed-From: non-dev-pkg-with-shlib-symlink -Explanation: Although this package is not a "-dev" package, it installs a - "libsomething.so" symbolic link referencing the corresponding shared - library. When the link doesn't include the version number, it is used by - the linker when other programs are built against this shared library. - . - Shared libraries are supposed to place such symbolic links in their - respective "-dev" packages, so it is a bug to include it with the main - library package. - . - However, if this is a small package which includes the runtime and the - development libraries, this is not a bug. In the latter case, please - override this warning. -See-Also: policy 8.4 diff -Nru lintian-2.93.0/tags/l/loads-obsolete-confmodule.desc lintian-2.89.0ubuntu1/tags/l/loads-obsolete-confmodule.desc --- lintian-2.93.0/tags/l/loads-obsolete-confmodule.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/l/loads-obsolete-confmodule.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: loads-obsolete-confmodule +Severity: warning +Check: debian/debconf +Info: The maintainer script uses an obsolete name for a debconf confmodule. + Shell scripts should source /usr/share/debconf/confmodule, while + Perl scripts should use Debconf::Client::ConfModule. +Ref: debconf-devel(7) diff -Nru lintian-2.93.0/tags/l/loads-obsolete-confmodule.tag lintian-2.89.0ubuntu1/tags/l/loads-obsolete-confmodule.tag --- lintian-2.93.0/tags/l/loads-obsolete-confmodule.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/l/loads-obsolete-confmodule.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: loads-obsolete-confmodule -Severity: warning -Check: debian/debconf -Explanation: The maintainer script uses an obsolete name for a debconf confmodule. - Shell scripts should source /usr/share/debconf/confmodule, while - Perl scripts should use Debconf::Client::ConfModule. -See-Also: debconf-devel(7) diff -Nru lintian-2.93.0/tags/l/lzma-deb-archive.desc lintian-2.89.0ubuntu1/tags/l/lzma-deb-archive.desc --- lintian-2.93.0/tags/l/lzma-deb-archive.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/l/lzma-deb-archive.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: lzma-deb-archive +Severity: error +Check: deb-format +Info: The data portion of this binary package is compressed with lzma. + This is supported by dpkg but not yet permitted in the Debian archive. + Such a package will be rejected by DAK. diff -Nru lintian-2.93.0/tags/l/lzma-deb-archive.tag lintian-2.89.0ubuntu1/tags/l/lzma-deb-archive.tag --- lintian-2.93.0/tags/l/lzma-deb-archive.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/l/lzma-deb-archive.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: lzma-deb-archive -Severity: error -Check: deb-format -Explanation: The data portion of this binary package is compressed with lzma. - This is supported by dpkg but not yet permitted in the Debian archive. - Such a package will be rejected by DAK. diff -Nru lintian-2.93.0/tags/m/macos-ds-store-file-in-package.desc lintian-2.89.0ubuntu1/tags/m/macos-ds-store-file-in-package.desc --- lintian-2.93.0/tags/m/macos-ds-store-file-in-package.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/macos-ds-store-file-in-package.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: macos-ds-store-file-in-package +Severity: warning +Check: foreign-operating-systems +Info: There is a file in the package named .DS_Store or + .DS_Store.gz, the file name used by Mac OS X to store folder + attributes. Such files are generally useless in Debian packages and were + usually accidentally included by copying complete directories from the + source tarball. diff -Nru lintian-2.93.0/tags/m/macos-ds-store-file-in-package.tag lintian-2.89.0ubuntu1/tags/m/macos-ds-store-file-in-package.tag --- lintian-2.93.0/tags/m/macos-ds-store-file-in-package.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/macos-ds-store-file-in-package.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: macos-ds-store-file-in-package -Severity: warning -Check: foreign-operating-systems -Explanation: There is a file in the package named .DS_Store or - .DS_Store.gz, the file name used by Mac OS X to store folder - attributes. Such files are generally useless in Debian packages and were - usually accidentally included by copying complete directories from the - source tarball. diff -Nru lintian-2.93.0/tags/m/macos-resource-fork-file-in-package.desc lintian-2.89.0ubuntu1/tags/m/macos-resource-fork-file-in-package.desc --- lintian-2.93.0/tags/m/macos-resource-fork-file-in-package.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/macos-resource-fork-file-in-package.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: macos-resource-fork-file-in-package +Severity: warning +Check: foreign-operating-systems +Info: There is a file in the package with a name starting with + ._, the file name pattern used by Mac OS X to store resource + forks in non-native file systems. Such files are generally useless in + Debian packages and were usually accidentally included by copying + complete directories from the source tarball. diff -Nru lintian-2.93.0/tags/m/macos-resource-fork-file-in-package.tag lintian-2.89.0ubuntu1/tags/m/macos-resource-fork-file-in-package.tag --- lintian-2.93.0/tags/m/macos-resource-fork-file-in-package.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/macos-resource-fork-file-in-package.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: macos-resource-fork-file-in-package -Severity: warning -Check: foreign-operating-systems -Explanation: There is a file in the package with a name starting with - ._, the file name pattern used by Mac OS X to store resource - forks in non-native file systems. Such files are generally useless in - Debian packages and were usually accidentally included by copying - complete directories from the source tarball. diff -Nru lintian-2.93.0/tags/m/magic-arch-in-arch-list.desc lintian-2.89.0ubuntu1/tags/m/magic-arch-in-arch-list.desc --- lintian-2.93.0/tags/m/magic-arch-in-arch-list.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/magic-arch-in-arch-list.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: magic-arch-in-arch-list +Severity: error +Check: fields/architecture +Info: The special architecture value "any" only makes sense if it occurs + alone or (in a *.dsc file) together with "all". The value "all" may + appear together with other architectures in a *.dsc file but must + occur alone if used in a binary package. +Ref: policy 5.6.8, #626775 diff -Nru lintian-2.93.0/tags/m/magic-arch-in-arch-list.tag lintian-2.89.0ubuntu1/tags/m/magic-arch-in-arch-list.tag --- lintian-2.93.0/tags/m/magic-arch-in-arch-list.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/magic-arch-in-arch-list.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: magic-arch-in-arch-list -Severity: error -Check: fields/architecture -Explanation: The special architecture value "any" only makes sense if it occurs - alone or (in a *.dsc file) together with "all". The value "all" may - appear together with other architectures in a *.dsc file but must - occur alone if used in a binary package. -See-Also: policy 5.6.8, Bug#626775 diff -Nru lintian-2.93.0/tags/m/mail-address-loops-or-bounces.desc lintian-2.89.0ubuntu1/tags/m/mail-address-loops-or-bounces.desc --- lintian-2.93.0/tags/m/mail-address-loops-or-bounces.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/mail-address-loops-or-bounces.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,17 @@ +Tag: mail-address-loops-or-bounces +Severity: error +Check: fields/mail-address +Renamed-From: + maintainer-address-causes-mail-loops-or-bounces + uploader-address-causes-mail-loops-or-bounces +Info: The contact's mail address either loops back to itself or is known + to bounce. + . + Loops happen because an address is package@packages.debian.org + or to package@packages.qa.debian.org. Bounces happen when the + receipient, typically a mailing list, is known to bounce mails. + . + The mail address must accept messages from role accounts used to send + automated mails regarding the package, including those from the bug + tracking system. +Ref: policy 3.3 diff -Nru lintian-2.93.0/tags/m/mail-address-loops-or-bounces.tag lintian-2.89.0ubuntu1/tags/m/mail-address-loops-or-bounces.tag --- lintian-2.93.0/tags/m/mail-address-loops-or-bounces.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/mail-address-loops-or-bounces.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,17 +0,0 @@ -Tag: mail-address-loops-or-bounces -Severity: error -Check: fields/mail-address -Renamed-From: - maintainer-address-causes-mail-loops-or-bounces - uploader-address-causes-mail-loops-or-bounces -Explanation: The contact's mail address either loops back to itself or is known - to bounce. - . - Loops happen because an address is package@packages.debian.org - or to package@packages.qa.debian.org. Bounces happen when the - receipient, typically a mailing list, is known to bounce mails. - . - The mail address must accept messages from role accounts used to send - automated mails regarding the package, including those from the bug - tracking system. -See-Also: policy 3.3 diff -Nru lintian-2.93.0/tags/m/mail-contact.desc lintian-2.89.0ubuntu1/tags/m/mail-contact.desc --- lintian-2.93.0/tags/m/mail-contact.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/mail-contact.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: mail-contact +Severity: classification +Check: fields/mail-address +Renamed-From: + maintainer + uploader +Info: This person is a contact in the named group for this package. diff -Nru lintian-2.93.0/tags/m/mail-contact.tag lintian-2.89.0ubuntu1/tags/m/mail-contact.tag --- lintian-2.93.0/tags/m/mail-contact.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/mail-contact.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: mail-contact -Severity: classification -Check: fields/mail-address -Renamed-From: - maintainer - uploader -Explanation: This person is a contact in the named group for this package. diff -Nru lintian-2.93.0/tags/m/mailing-list-on-alioth.desc lintian-2.89.0ubuntu1/tags/m/mailing-list-on-alioth.desc --- lintian-2.93.0/tags/m/mailing-list-on-alioth.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/mailing-list-on-alioth.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: mailing-list-on-alioth +Severity: classification +Check: fields/mail-address +Info: The specified email address uses lists.alioth.debian.org. That + system was migrated to a separate debian.net system run by DDs. + Teams were encouraged to migrate to the new system, but they are + also free to use the old address going forward if they like. + . + For further information, please consult the Debian Wiki. +Ref: https://wiki.debian.org/Alioth/MailingListContinuation, Bug#962448 diff -Nru lintian-2.93.0/tags/m/mailing-list-on-alioth.tag lintian-2.89.0ubuntu1/tags/m/mailing-list-on-alioth.tag --- lintian-2.93.0/tags/m/mailing-list-on-alioth.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/mailing-list-on-alioth.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,10 +0,0 @@ -Tag: mailing-list-on-alioth -Severity: classification -Check: fields/mail-address -Explanation: The specified email address uses lists.alioth.debian.org. That - system was migrated to a separate debian.net system run by DDs. - Teams were encouraged to migrate to the new system, but they are - also free to use the old address going forward if they like. - . - For further information, please consult the Debian Wiki. -See-Also: https://wiki.debian.org/Alioth/MailingListContinuation, Bug#962448 diff -Nru lintian-2.93.0/tags/m/mail-transport-agent-dependency-does-not-specify-default-mta.desc lintian-2.89.0ubuntu1/tags/m/mail-transport-agent-dependency-does-not-specify-default-mta.desc --- lintian-2.93.0/tags/m/mail-transport-agent-dependency-does-not-specify-default-mta.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/mail-transport-agent-dependency-does-not-specify-default-mta.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,12 @@ +Tag: mail-transport-agent-dependency-does-not-specify-default-mta +Severity: warning +Check: fields/package-relations +Info: This package has a relationship with the mail-transport-agent + virtual package but does not specify the default-mta as an + alternative. + . + default-mta and mail-transport-agent should only ever be in a set of + alternatives together, with default-mta listed first. + . + Please add a "or" dependency on default-mta before + mail-transport-agent. diff -Nru lintian-2.93.0/tags/m/mail-transport-agent-dependency-does-not-specify-default-mta.tag lintian-2.89.0ubuntu1/tags/m/mail-transport-agent-dependency-does-not-specify-default-mta.tag --- lintian-2.93.0/tags/m/mail-transport-agent-dependency-does-not-specify-default-mta.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/mail-transport-agent-dependency-does-not-specify-default-mta.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,12 +0,0 @@ -Tag: mail-transport-agent-dependency-does-not-specify-default-mta -Severity: warning -Check: fields/package-relations -Explanation: This package has a relationship with the mail-transport-agent - virtual package but does not specify the default-mta as an - alternative. - . - default-mta and mail-transport-agent should only ever be in a set of - alternatives together, with default-mta listed first. - . - Please add a "or" dependency on default-mta before - mail-transport-agent. diff -Nru lintian-2.93.0/tags/m/maintainer-also-in-uploaders.desc lintian-2.89.0ubuntu1/tags/m/maintainer-also-in-uploaders.desc --- lintian-2.93.0/tags/m/maintainer-also-in-uploaders.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/maintainer-also-in-uploaders.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: maintainer-also-in-uploaders +Severity: warning +Check: fields/uploaders +Info: The maintainer value also appears on the Uploaders field. + There were some reasons why this was useful when Uploaders support was + first introduced, but those have long-since been fixed and there is no + longer any need to list the maintainer in Uploaders. The duplicate + information should probably be removed. diff -Nru lintian-2.93.0/tags/m/maintainer-also-in-uploaders.tag lintian-2.89.0ubuntu1/tags/m/maintainer-also-in-uploaders.tag --- lintian-2.93.0/tags/m/maintainer-also-in-uploaders.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/maintainer-also-in-uploaders.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: maintainer-also-in-uploaders -Severity: warning -Check: fields/uploaders -Explanation: The maintainer value also appears on the Uploaders field. - There were some reasons why this was useful when Uploaders support was - first introduced, but those have long-since been fixed and there is no - longer any need to list the maintainer in Uploaders. The duplicate - information should probably be removed. diff -Nru lintian-2.93.0/tags/m/maintainer-desktop-entry.desc lintian-2.89.0ubuntu1/tags/m/maintainer-desktop-entry.desc --- lintian-2.93.0/tags/m/maintainer-desktop-entry.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/maintainer-desktop-entry.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: maintainer-desktop-entry +Severity: pedantic +Check: debian/desktop-entries +Info: The maintainer keeps a desktop entry in ./debian. Please forward + the desktop entry upstream and ask them to include it in their version + control system, and in their next release. + . + If the desktop entry was already forwarded or rejected, or the upstream + is gone, please override the tag and annotate it with a suitable comment. +Ref: social contract item 2, devref 3.1.4, policy 4.3 diff -Nru lintian-2.93.0/tags/m/maintainer-desktop-entry.tag lintian-2.89.0ubuntu1/tags/m/maintainer-desktop-entry.tag --- lintian-2.93.0/tags/m/maintainer-desktop-entry.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/maintainer-desktop-entry.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,10 +0,0 @@ -Tag: maintainer-desktop-entry -Severity: pedantic -Check: debian/desktop-entries -Explanation: The maintainer keeps a desktop entry in ./debian. Please forward - the desktop entry upstream and ask them to include it in their version - control system, and in their next release. - . - If the desktop entry was already forwarded or rejected, or the upstream - is gone, please override the tag and annotate it with a suitable comment. -See-Also: social contract item 2, devref 3.1.4, policy 4.3 diff -Nru lintian-2.93.0/tags/m/maintainer-manual-page.desc lintian-2.89.0ubuntu1/tags/m/maintainer-manual-page.desc --- lintian-2.93.0/tags/m/maintainer-manual-page.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/maintainer-manual-page.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,11 @@ +Tag: maintainer-manual-page +Severity: pedantic +Check: debian/manual-pages +Renamed-From: maintainer-manpage +Info: The maintainer keeps a manual page in ./debian. Please forward the + manual page upstream and ask them to include in their version control + system, and in their next release. + . + If the manual page was already forwarded or rejected, or the upstream is + gone, please override the tag and annotate it with a suitable comment. +Ref: social contract item 2, devref 3.1.4, policy 4.3 diff -Nru lintian-2.93.0/tags/m/maintainer-manual-page.tag lintian-2.89.0ubuntu1/tags/m/maintainer-manual-page.tag --- lintian-2.93.0/tags/m/maintainer-manual-page.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/maintainer-manual-page.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,11 +0,0 @@ -Tag: maintainer-manual-page -Severity: pedantic -Check: debian/manual-pages -Renamed-From: maintainer-manpage -Explanation: The maintainer keeps a manual page in ./debian. Please forward the - manual page upstream and ask them to include in their version control - system, and in their next release. - . - If the manual page was already forwarded or rejected, or the upstream is - gone, please override the tag and annotate it with a suitable comment. -See-Also: social contract item 2, devref 3.1.4, policy 4.3 diff -Nru lintian-2.93.0/tags/m/maintainer-script-calls-chown-improperly.desc lintian-2.89.0ubuntu1/tags/m/maintainer-script-calls-chown-improperly.desc --- lintian-2.93.0/tags/m/maintainer-script-calls-chown-improperly.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/maintainer-script-calls-chown-improperly.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: maintainer-script-calls-chown-improperly +Severity: warning +Check: scripts +Renamed-From: maintainer-script-should-not-use-deprecated-chown-usage +Info: chown user.group is called in one of the maintainer + scripts. The correct syntax is chown user:group. Using "." as a + separator is still supported by the GNU tools, but it will fail as soon + as a system uses the "." in user or group names. +Ref: chown(1) diff -Nru lintian-2.93.0/tags/m/maintainer-script-calls-chown-improperly.tag lintian-2.89.0ubuntu1/tags/m/maintainer-script-calls-chown-improperly.tag --- lintian-2.93.0/tags/m/maintainer-script-calls-chown-improperly.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/maintainer-script-calls-chown-improperly.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: maintainer-script-calls-chown-improperly -Severity: warning -Check: scripts -Renamed-From: maintainer-script-should-not-use-deprecated-chown-usage -Explanation: chown user.group is called in one of the maintainer - scripts. The correct syntax is chown user:group. Using "." as a - separator is still supported by the GNU tools, but it will fail as soon - as a system uses the "." in user or group names. -See-Also: chown(1) diff -Nru lintian-2.93.0/tags/m/maintainer-script-calls-gconftool.desc lintian-2.89.0ubuntu1/tags/m/maintainer-script-calls-gconftool.desc --- lintian-2.93.0/tags/m/maintainer-script-calls-gconftool.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/maintainer-script-calls-gconftool.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: maintainer-script-calls-gconftool +Severity: warning +Certainty: possible +Check: scripts +Renamed-From: maintainer-script-should-not-use-gconftool +Info: This script apparently runs gconftool or gconftool-2. It should + probably be calling gconf-schemas or update-gconf-defaults instead. diff -Nru lintian-2.93.0/tags/m/maintainer-script-calls-gconftool.tag lintian-2.89.0ubuntu1/tags/m/maintainer-script-calls-gconftool.tag --- lintian-2.93.0/tags/m/maintainer-script-calls-gconftool.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/maintainer-script-calls-gconftool.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: maintainer-script-calls-gconftool -Severity: warning -Check: scripts -Renamed-From: maintainer-script-should-not-use-gconftool -Explanation: This script apparently runs gconftool or gconftool-2. It should - probably be calling gconf-schemas or update-gconf-defaults instead. diff -Nru lintian-2.93.0/tags/m/maintainer-script-calls-init-script-directly.desc lintian-2.89.0ubuntu1/tags/m/maintainer-script-calls-init-script-directly.desc --- lintian-2.93.0/tags/m/maintainer-script-calls-init-script-directly.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/maintainer-script-calls-init-script-directly.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: maintainer-script-calls-init-script-directly +Severity: error +Check: scripts +Info: This script apparently runs an init script directly rather than + using invoke-rc.d. The use of invoke-rc.d to invoke the /etc/init.d/* + initscripts instead of calling them directly is required. Maintainer + scripts may call the init script directly only if invoke-rc.d is not + available. +Ref: policy 9.3.3.2 diff -Nru lintian-2.93.0/tags/m/maintainer-script-calls-init-script-directly.tag lintian-2.89.0ubuntu1/tags/m/maintainer-script-calls-init-script-directly.tag --- lintian-2.93.0/tags/m/maintainer-script-calls-init-script-directly.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/maintainer-script-calls-init-script-directly.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: maintainer-script-calls-init-script-directly -Severity: error -Check: scripts -Explanation: This script apparently runs an init script directly rather than - using invoke-rc.d. The use of invoke-rc.d to invoke the /etc/init.d/* - initscripts instead of calling them directly is required. Maintainer - scripts may call the init script directly only if invoke-rc.d is not - available. -See-Also: policy 9.3.3.2 diff -Nru lintian-2.93.0/tags/m/maintainer-script-calls-install-sgmlcatalog.desc lintian-2.89.0ubuntu1/tags/m/maintainer-script-calls-install-sgmlcatalog.desc --- lintian-2.93.0/tags/m/maintainer-script-calls-install-sgmlcatalog.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/maintainer-script-calls-install-sgmlcatalog.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: maintainer-script-calls-install-sgmlcatalog +Severity: error +Check: scripts +Renamed-From: maintainer-script-should-not-use-install-sgmlcatalog +Info: The maintainer script apparently runs install-sgmlcatalog. + install-sgmlcatalog is deprecated and should only have been used + in postinst or prerm to remove the entries from earlier packages. + Given how long ago this transition was, consider removing it + entirely. diff -Nru lintian-2.93.0/tags/m/maintainer-script-calls-install-sgmlcatalog.tag lintian-2.89.0ubuntu1/tags/m/maintainer-script-calls-install-sgmlcatalog.tag --- lintian-2.93.0/tags/m/maintainer-script-calls-install-sgmlcatalog.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/maintainer-script-calls-install-sgmlcatalog.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: maintainer-script-calls-install-sgmlcatalog -Severity: error -Check: scripts -Renamed-From: maintainer-script-should-not-use-install-sgmlcatalog -Explanation: The maintainer script apparently runs install-sgmlcatalog. - install-sgmlcatalog is deprecated and should only have been used - in postinst or prerm to remove the entries from earlier packages. - Given how long ago this transition was, consider removing it - entirely. diff -Nru lintian-2.93.0/tags/m/maintainer-script-calls-service.desc lintian-2.89.0ubuntu1/tags/m/maintainer-script-calls-service.desc --- lintian-2.93.0/tags/m/maintainer-script-calls-service.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/maintainer-script-calls-service.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,14 @@ +Tag: maintainer-script-calls-service +Severity: error +Check: scripts +Experimental: yes +Renamed-From: maintainer-script-should-not-use-service +Info: The maintainer script apparently runs the service command. This + command is reserved for local administrators and must never be used + by a Debian package. + . + Please replace with calls to update-rc.d(8) and + invoke-rc.d(8). If your package installs this service, this + can be automated using dh_installinit(1) or + dh_installsystemd(1). +Ref: policy 9.3.3 diff -Nru lintian-2.93.0/tags/m/maintainer-script-calls-service.tag lintian-2.89.0ubuntu1/tags/m/maintainer-script-calls-service.tag --- lintian-2.93.0/tags/m/maintainer-script-calls-service.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/maintainer-script-calls-service.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,14 +0,0 @@ -Tag: maintainer-script-calls-service -Severity: error -Check: scripts -Experimental: yes -Renamed-From: maintainer-script-should-not-use-service -Explanation: The maintainer script apparently runs the service command. This - command is reserved for local administrators and must never be used - by a Debian package. - . - Please replace with calls to update-rc.d(8) and - invoke-rc.d(8). If your package installs this service, this - can be automated using dh_installinit(1) or - dh_installsystemd(1). -See-Also: policy 9.3.3 diff -Nru lintian-2.93.0/tags/m/maintainer-script-calls-start-stop-daemon.desc lintian-2.89.0ubuntu1/tags/m/maintainer-script-calls-start-stop-daemon.desc --- lintian-2.93.0/tags/m/maintainer-script-calls-start-stop-daemon.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/maintainer-script-calls-start-stop-daemon.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: maintainer-script-calls-start-stop-daemon +Severity: warning +Check: scripts +Renamed-From: maintainer-script-should-not-use-start-stop-daemon +Info: The maintainer script seems to call start-stop-daemon + directly. Long-running daemons should be started and stopped via init + scripts using invoke-rc.d rather than directly in maintainer + scripts. +Ref: policy 9.3.3.2 diff -Nru lintian-2.93.0/tags/m/maintainer-script-calls-start-stop-daemon.tag lintian-2.89.0ubuntu1/tags/m/maintainer-script-calls-start-stop-daemon.tag --- lintian-2.93.0/tags/m/maintainer-script-calls-start-stop-daemon.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/maintainer-script-calls-start-stop-daemon.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: maintainer-script-calls-start-stop-daemon -Severity: warning -Check: scripts -Renamed-From: maintainer-script-should-not-use-start-stop-daemon -Explanation: The maintainer script seems to call start-stop-daemon - directly. Long-running daemons should be started and stopped via init - scripts using invoke-rc.d rather than directly in maintainer - scripts. -See-Also: policy 9.3.3.2 diff -Nru lintian-2.93.0/tags/m/maintainer-script-calls-systemctl.desc lintian-2.89.0ubuntu1/tags/m/maintainer-script-calls-systemctl.desc --- lintian-2.93.0/tags/m/maintainer-script-calls-systemctl.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/maintainer-script-calls-systemctl.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,12 @@ +Tag: maintainer-script-calls-systemctl +Severity: warning +Check: systemd +Ref: https://wiki.debian.org/Teams/pkg-systemd/Packaging +Info: The maintainer script calls systemctl directly. Actions such as enabling + a unit file should be done using deb-systemd-helper so that they work + on machines with or without systemd. Starting a service should be done via + invoke-rc.d if the service has a corresponding sysvinit script or + deb-systemd-invoke if it does not. + . + If you are using debhelper, please use the systemd debhelper + addon, which is provided by debhelper (>= 9.20160709~). diff -Nru lintian-2.93.0/tags/m/maintainer-script-calls-systemctl.tag lintian-2.89.0ubuntu1/tags/m/maintainer-script-calls-systemctl.tag --- lintian-2.93.0/tags/m/maintainer-script-calls-systemctl.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/maintainer-script-calls-systemctl.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,12 +0,0 @@ -Tag: maintainer-script-calls-systemctl -Severity: warning -Check: systemd -See-Also: https://wiki.debian.org/Teams/pkg-systemd/Packaging -Explanation: The maintainer script calls systemctl directly. Actions such as enabling - a unit file should be done using deb-systemd-helper so that they work - on machines with or without systemd. Starting a service should be done via - invoke-rc.d if the service has a corresponding sysvinit script or - deb-systemd-invoke if it does not. - . - If you are using debhelper, please use the systemd debhelper - addon, which is provided by debhelper (>= 9.20160709~). diff -Nru lintian-2.93.0/tags/m/maintainer-script-changes-ld-so-conf.desc lintian-2.89.0ubuntu1/tags/m/maintainer-script-changes-ld-so-conf.desc --- lintian-2.93.0/tags/m/maintainer-script-changes-ld-so-conf.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/maintainer-script-changes-ld-so-conf.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,18 @@ +Tag: maintainer-script-changes-ld-so-conf +Severity: error +Certainty: possible +Check: scripts +Renamed-From: maintainer-script-should-not-modify-ld-so-conf +Info: This package appears to modify /etc/ld.so.conf and does not + appear to be part of libc. Packages installing shared libraries in + non-standard locations were previously permitted to modify + /etc/ld.so.conf to add the non-standard path, but this permission was + removed in Policy 3.8.3. + . + Packages containing shared libraries should either install them into + /usr/lib or should require binaries built against them to set + RPATH to find the library at run-time. Installing libraries in a + different directory and modifying the run-time linker path is equivalent + to installing them into /usr/lib except now conflicting library + packages may cause random segfaults and difficult-to-debug problems + instead of conflicts in the package manager. diff -Nru lintian-2.93.0/tags/m/maintainer-script-changes-ld-so-conf.tag lintian-2.89.0ubuntu1/tags/m/maintainer-script-changes-ld-so-conf.tag --- lintian-2.93.0/tags/m/maintainer-script-changes-ld-so-conf.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/maintainer-script-changes-ld-so-conf.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,17 +0,0 @@ -Tag: maintainer-script-changes-ld-so-conf -Severity: error -Check: scripts -Renamed-From: maintainer-script-should-not-modify-ld-so-conf -Explanation: This package appears to modify /etc/ld.so.conf and does not - appear to be part of libc. Packages installing shared libraries in - non-standard locations were previously permitted to modify - /etc/ld.so.conf to add the non-standard path, but this permission was - removed in Policy 3.8.3. - . - Packages containing shared libraries should either install them into - /usr/lib or should require binaries built against them to set - RPATH to find the library at run-time. Installing libraries in a - different directory and modifying the run-time linker path is equivalent - to installing them into /usr/lib except now conflicting library - packages may cause random segfaults and difficult-to-debug problems - instead of conflicts in the package manager. diff -Nru lintian-2.93.0/tags/m/maintainer-script-changes-netbase.desc lintian-2.89.0ubuntu1/tags/m/maintainer-script-changes-netbase.desc --- lintian-2.93.0/tags/m/maintainer-script-changes-netbase.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/maintainer-script-changes-netbase.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: maintainer-script-changes-netbase +Severity: error +Check: scripts +Renamed-From: maintainer-script-should-not-modify-netbase-managed-file +Info: The maintainer script modifies at least one of the files + /etc/services, /etc/protocols, and /etc/rpc, + which are managed by the netbase package. Instead of doing this, please + file a wishlist bug against netbase to have an appropriate entry added. +Ref: policy 11.2 diff -Nru lintian-2.93.0/tags/m/maintainer-script-changes-netbase.tag lintian-2.89.0ubuntu1/tags/m/maintainer-script-changes-netbase.tag --- lintian-2.93.0/tags/m/maintainer-script-changes-netbase.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/maintainer-script-changes-netbase.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: maintainer-script-changes-netbase -Severity: error -Check: scripts -Renamed-From: maintainer-script-should-not-modify-netbase-managed-file -Explanation: The maintainer script modifies at least one of the files - /etc/services, /etc/protocols, and /etc/rpc, - which are managed by the netbase package. Instead of doing this, please - file a wishlist bug against netbase to have an appropriate entry added. -See-Also: policy 11.2 diff -Nru lintian-2.93.0/tags/m/maintainer-script-does-not-check-for-existence-of-installdocs.desc lintian-2.89.0ubuntu1/tags/m/maintainer-script-does-not-check-for-existence-of-installdocs.desc --- lintian-2.93.0/tags/m/maintainer-script-does-not-check-for-existence-of-installdocs.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/maintainer-script-does-not-check-for-existence-of-installdocs.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,12 @@ +Tag: maintainer-script-does-not-check-for-existence-of-installdocs +Severity: error +Certainty: possible +Check: menus +Info: The maintainer script calls the install-docs command without + checking for existence first. (The doc-base package which provides + the command is not marked as "essential" package.) + . + For example, use the following code in your maintainer script: + if which install-docs > /dev/null; then + install-docs -i /usr/share/doc-base/<your-package> + fi diff -Nru lintian-2.93.0/tags/m/maintainer-script-does-not-check-for-existence-of-installdocs.tag lintian-2.89.0ubuntu1/tags/m/maintainer-script-does-not-check-for-existence-of-installdocs.tag --- lintian-2.93.0/tags/m/maintainer-script-does-not-check-for-existence-of-installdocs.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/maintainer-script-does-not-check-for-existence-of-installdocs.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,11 +0,0 @@ -Tag: maintainer-script-does-not-check-for-existence-of-installdocs -Severity: error -Check: menus -Explanation: The maintainer script calls the install-docs command without - checking for existence first. (The doc-base package which provides - the command is not marked as "essential" package.) - . - For example, use the following code in your maintainer script: - if which install-docs > /dev/null; then - install-docs -i /usr/share/doc-base/<your-package> - fi diff -Nru lintian-2.93.0/tags/m/maintainer-script-does-not-check-for-existence-of-updatemenus.desc lintian-2.89.0ubuntu1/tags/m/maintainer-script-does-not-check-for-existence-of-updatemenus.desc --- lintian-2.93.0/tags/m/maintainer-script-does-not-check-for-existence-of-updatemenus.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/maintainer-script-does-not-check-for-existence-of-updatemenus.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,11 @@ +Tag: maintainer-script-does-not-check-for-existence-of-updatemenus +Severity: error +Certainty: possible +Check: menus +Info: The maintainer script calls the update-menus command without + checking for existence first. (The menu package which provides the + command is not marked as "essential" package.) + . + For example, use the following code in your maintainer script: + . + if which update-menus > /dev/null; then update-menus ; fi diff -Nru lintian-2.93.0/tags/m/maintainer-script-does-not-check-for-existence-of-updatemenus.tag lintian-2.89.0ubuntu1/tags/m/maintainer-script-does-not-check-for-existence-of-updatemenus.tag --- lintian-2.93.0/tags/m/maintainer-script-does-not-check-for-existence-of-updatemenus.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/maintainer-script-does-not-check-for-existence-of-updatemenus.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,10 +0,0 @@ -Tag: maintainer-script-does-not-check-for-existence-of-updatemenus -Severity: error -Check: menus -Explanation: The maintainer script calls the update-menus command without - checking for existence first. (The menu package which provides the - command is not marked as "essential" package.) - . - For example, use the following code in your maintainer script: - . - if which update-menus > /dev/null; then update-menus ; fi diff -Nru lintian-2.93.0/tags/m/maintainer-script-empty.desc lintian-2.89.0ubuntu1/tags/m/maintainer-script-empty.desc --- lintian-2.93.0/tags/m/maintainer-script-empty.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/maintainer-script-empty.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,12 @@ +Tag: maintainer-script-empty +Severity: warning +Check: scripts +Info: The maintainer script doesn't seem to contain any code other than + comments and boilerplate (set -e, exit statements, and the case statement + to parse options). While this is harmless in most cases, it is probably + not what you wanted, may mean the package will leave unnecessary files + behind until purged, and may even lead to problems in rare situations + where dpkg would fail if no maintainer script was present. + . + If the package currently doesn't need to do anything in this maintainer + script, it shouldn't be included in the package. diff -Nru lintian-2.93.0/tags/m/maintainer-script-empty.tag lintian-2.89.0ubuntu1/tags/m/maintainer-script-empty.tag --- lintian-2.93.0/tags/m/maintainer-script-empty.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/maintainer-script-empty.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,12 +0,0 @@ -Tag: maintainer-script-empty -Severity: warning -Check: scripts -Explanation: The maintainer script doesn't seem to contain any code other than - comments and boilerplate (set -e, exit statements, and the case statement - to parse options). While this is harmless in most cases, it is probably - not what you wanted, may mean the package will leave unnecessary files - behind until purged, and may even lead to problems in rare situations - where dpkg would fail if no maintainer script was present. - . - If the package currently doesn't need to do anything in this maintainer - script, it shouldn't be included in the package. diff -Nru lintian-2.93.0/tags/m/maintainer-script-has-invalid-update-inetd-options.desc lintian-2.89.0ubuntu1/tags/m/maintainer-script-has-invalid-update-inetd-options.desc --- lintian-2.93.0/tags/m/maintainer-script-has-invalid-update-inetd-options.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/maintainer-script-has-invalid-update-inetd-options.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,17 @@ +Tag: maintainer-script-has-invalid-update-inetd-options +Severity: warning +Certainty: possible +Check: scripts +Ref: update-inetd(1), #909758, #909506 +Info: The specified maintainer script seems to call + update-inetd(1) with an invalid option combination. + . + For example, the --group--add and --pattern is only valid + without --add. + . + Whilst these have been ignored in the past they now emit a warning + which will become an error in the future, resulting in upgrade/removal + failures. + . + Please correct the call to update-inetd(1). diff -Nru lintian-2.93.0/tags/m/maintainer-script-has-invalid-update-inetd-options.tag lintian-2.89.0ubuntu1/tags/m/maintainer-script-has-invalid-update-inetd-options.tag --- lintian-2.93.0/tags/m/maintainer-script-has-invalid-update-inetd-options.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/maintainer-script-has-invalid-update-inetd-options.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,16 +0,0 @@ -Tag: maintainer-script-has-invalid-update-inetd-options -Severity: warning -Check: scripts -See-Also: update-inetd(1), Bug#909758, Bug#909506 -Explanation: The specified maintainer script seems to call - update-inetd(1) with an invalid option combination. - . - For example, the --group parameter is only valid in - combination with --add and --pattern is only valid - without --add. - . - Whilst these have been ignored in the past they now emit a warning - which will become an error in the future, resulting in upgrade/removal - failures. - . - Please correct the call to update-inetd(1). diff -Nru lintian-2.93.0/tags/m/maintainer-script-has-unexpanded-debhelper-token.desc lintian-2.89.0ubuntu1/tags/m/maintainer-script-has-unexpanded-debhelper-token.desc --- lintian-2.93.0/tags/m/maintainer-script-has-unexpanded-debhelper-token.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/maintainer-script-has-unexpanded-debhelper-token.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: maintainer-script-has-unexpanded-debhelper-token +Severity: warning +Certainty: possible +Check: scripts +Info: Lintian has detected the presence of a #DEBHELPER# token in the + listed maintainer/control script. By default, dh_installdeb will remove + the token when it makes a substitution in a script. + . + Please note that dh_installdeb does not substitute the #DEBHELPER# + token in udebs. diff -Nru lintian-2.93.0/tags/m/maintainer-script-has-unexpanded-debhelper-token.tag lintian-2.89.0ubuntu1/tags/m/maintainer-script-has-unexpanded-debhelper-token.tag --- lintian-2.93.0/tags/m/maintainer-script-has-unexpanded-debhelper-token.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/maintainer-script-has-unexpanded-debhelper-token.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: maintainer-script-has-unexpanded-debhelper-token -Severity: warning -Check: scripts -Explanation: Lintian has detected the presence of a #DEBHELPER# token in the - listed maintainer/control script. By default, dh_installdeb will remove - the token when it makes a substitution in a script. - . - Please note that dh_installdeb does *not* substitute the #DEBHELPER# - token in udebs. diff -Nru lintian-2.93.0/tags/m/maintainer-script-hides-init-failure.desc lintian-2.89.0ubuntu1/tags/m/maintainer-script-hides-init-failure.desc --- lintian-2.93.0/tags/m/maintainer-script-hides-init-failure.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/maintainer-script-hides-init-failure.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,12 @@ +Tag: maintainer-script-hides-init-failure +Severity: warning +Check: scripts +Renamed-From: maintainer-script-should-not-hide-init-failure +Info: This script calls invoke-rc.d to run an init script but then, if the + init script fails, exits successfully (using || exit 0). If the init + script fails, the maintainer script should probably fail. + . + The most likely cause of this problem is that the package was built with + a debhelper version suffering from Bug#337664 that inserted incorrect + invoke-rc.d code in the generated maintainer script. The package needs to + be reuploaded (could be bin-NMUd, no source changes needed). diff -Nru lintian-2.93.0/tags/m/maintainer-script-hides-init-failure.tag lintian-2.89.0ubuntu1/tags/m/maintainer-script-hides-init-failure.tag --- lintian-2.93.0/tags/m/maintainer-script-hides-init-failure.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/maintainer-script-hides-init-failure.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,12 +0,0 @@ -Tag: maintainer-script-hides-init-failure -Severity: warning -Check: scripts -Renamed-From: maintainer-script-should-not-hide-init-failure -Explanation: This script calls invoke-rc.d to run an init script but then, if the - init script fails, exits successfully (using || exit 0). If the init - script fails, the maintainer script should probably fail. - . - The most likely cause of this problem is that the package was built with - a debhelper version suffering from Bug#337664 that inserted incorrect - invoke-rc.d code in the generated maintainer script. The package needs to - be reuploaded (could be bin-NMUd, no source changes needed). diff -Nru lintian-2.93.0/tags/m/maintainer-script-ignores-errors.desc lintian-2.89.0ubuntu1/tags/m/maintainer-script-ignores-errors.desc --- lintian-2.93.0/tags/m/maintainer-script-ignores-errors.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/maintainer-script-ignores-errors.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: maintainer-script-ignores-errors +Severity: warning +Check: scripts +Ref: policy 10.4 +Info: The maintainer script doesn't seem to set the -e flag which + ensures that the script's execution is aborted when any executed command + fails. diff -Nru lintian-2.93.0/tags/m/maintainer-script-ignores-errors.tag lintian-2.89.0ubuntu1/tags/m/maintainer-script-ignores-errors.tag --- lintian-2.93.0/tags/m/maintainer-script-ignores-errors.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/maintainer-script-ignores-errors.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: maintainer-script-ignores-errors -Severity: warning -Check: scripts -See-Also: policy 10.4 -Explanation: The maintainer script doesn't seem to set the -e flag which - ensures that the script's execution is aborted when any executed command - fails. diff -Nru lintian-2.93.0/tags/m/maintainer-script-interpreter.desc lintian-2.89.0ubuntu1/tags/m/maintainer-script-interpreter.desc --- lintian-2.93.0/tags/m/maintainer-script-interpreter.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/maintainer-script-interpreter.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,4 @@ +Tag: maintainer-script-interpreter +Severity: classification +Check: scripts +Info: Interpreter used in maintainer script or ELF diff -Nru lintian-2.93.0/tags/m/maintainer-script-interpreter.tag lintian-2.89.0ubuntu1/tags/m/maintainer-script-interpreter.tag --- lintian-2.93.0/tags/m/maintainer-script-interpreter.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/maintainer-script-interpreter.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,4 +0,0 @@ -Tag: maintainer-script-interpreter -Severity: classification -Check: scripts -Explanation: Interpreter used in maintainer script or ELF diff -Nru lintian-2.93.0/tags/m/maintainer-script-lacks-debhelper-token.desc lintian-2.89.0ubuntu1/tags/m/maintainer-script-lacks-debhelper-token.desc --- lintian-2.93.0/tags/m/maintainer-script-lacks-debhelper-token.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/maintainer-script-lacks-debhelper-token.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: maintainer-script-lacks-debhelper-token +Severity: warning +Certainty: possible +Check: debhelper +Info: This package is built using debhelper commands that may modify + maintainer scripts, but the maintainer scripts do not contain + the "#DEBHELPER#" token debhelper uses to modify them. + . + Adding the token to the scripts is recommended. diff -Nru lintian-2.93.0/tags/m/maintainer-script-lacks-debhelper-token.tag lintian-2.89.0ubuntu1/tags/m/maintainer-script-lacks-debhelper-token.tag --- lintian-2.93.0/tags/m/maintainer-script-lacks-debhelper-token.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/maintainer-script-lacks-debhelper-token.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: maintainer-script-lacks-debhelper-token -Severity: warning -Check: debhelper -Explanation: This package is built using debhelper commands that may modify - maintainer scripts, but the maintainer scripts do not contain - the "#DEBHELPER#" token debhelper uses to modify them. - . - Adding the token to the scripts is recommended. diff -Nru lintian-2.93.0/tags/m/maintainer-script-lacks-home-in-adduser.desc lintian-2.89.0ubuntu1/tags/m/maintainer-script-lacks-home-in-adduser.desc --- lintian-2.93.0/tags/m/maintainer-script-lacks-home-in-adduser.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/maintainer-script-lacks-home-in-adduser.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,18 @@ +Tag: maintainer-script-lacks-home-in-adduser +Severity: error +Check: scripts +Renamed-From: maintainer-script-should-not-use-adduser-system-without-home +Info: The maintainer script apparently runs 'adduser --system' + but hardcodes a path under '/home' for the '--home' option or + does not use the '--home' option. + . + The FHS says: /home is a fairly standard concept, but it + is clearly a site-specific filesystem. The setup will differ + from host to host. Therefore, no program should rely on this + location. + . + Note that passing --no-create-home alone does not solve the issue + because home field of passwd file point to a non existing + /home subdirectory. Please use + adduser --no-create-home --home /nonexistent instead. +Ref: fhs homeuserhomedirectories, adduser(8) diff -Nru lintian-2.93.0/tags/m/maintainer-script-lacks-home-in-adduser.tag lintian-2.89.0ubuntu1/tags/m/maintainer-script-lacks-home-in-adduser.tag --- lintian-2.93.0/tags/m/maintainer-script-lacks-home-in-adduser.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/maintainer-script-lacks-home-in-adduser.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,18 +0,0 @@ -Tag: maintainer-script-lacks-home-in-adduser -Severity: error -Check: scripts -Renamed-From: maintainer-script-should-not-use-adduser-system-without-home -Explanation: The maintainer script apparently runs 'adduser --system' - but hardcodes a path under '/home' for the '--home' option or - does not use the '--home' option. - . - The FHS says: /home is a fairly standard concept, but it - is clearly a site-specific filesystem. The setup will differ - from host to host. Therefore, no program should rely on this - location. - . - Note that passing --no-create-home alone does not solve the issue - because home field of passwd file point to a non existing - /home subdirectory. Please use - adduser --no-create-home --home /nonexistent instead. -See-Also: fhs homeuserhomedirectories, adduser(8) diff -Nru lintian-2.93.0/tags/m/maintainer-script-modifies-inetd-conf.desc lintian-2.89.0ubuntu1/tags/m/maintainer-script-modifies-inetd-conf.desc --- lintian-2.93.0/tags/m/maintainer-script-modifies-inetd-conf.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/maintainer-script-modifies-inetd-conf.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: maintainer-script-modifies-inetd-conf +Severity: error +Check: scripts +Info: The maintainer script modifies /etc/inetd.conf directly. + This file must not be modified directly; instead, use the + update-inetd script or the DebianNet.pm Perl module. +Ref: policy 11.2 diff -Nru lintian-2.93.0/tags/m/maintainer-script-modifies-inetd-conf.tag lintian-2.89.0ubuntu1/tags/m/maintainer-script-modifies-inetd-conf.tag --- lintian-2.93.0/tags/m/maintainer-script-modifies-inetd-conf.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/maintainer-script-modifies-inetd-conf.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: maintainer-script-modifies-inetd-conf -Severity: error -Check: scripts -Explanation: The maintainer script modifies /etc/inetd.conf directly. - This file must not be modified directly; instead, use the - update-inetd script or the DebianNet.pm Perl module. -See-Also: policy 11.2 diff -Nru lintian-2.93.0/tags/m/maintainer-script-needs-depends-on-adduser.desc lintian-2.89.0ubuntu1/tags/m/maintainer-script-needs-depends-on-adduser.desc --- lintian-2.93.0/tags/m/maintainer-script-needs-depends-on-adduser.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/maintainer-script-needs-depends-on-adduser.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,5 @@ +Tag: maintainer-script-needs-depends-on-adduser +Severity: warning +Check: scripts +Info: This script calls adduser, but the package does not depend or + pre-depend on the adduser package. diff -Nru lintian-2.93.0/tags/m/maintainer-script-needs-depends-on-adduser.tag lintian-2.89.0ubuntu1/tags/m/maintainer-script-needs-depends-on-adduser.tag --- lintian-2.93.0/tags/m/maintainer-script-needs-depends-on-adduser.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/maintainer-script-needs-depends-on-adduser.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,5 +0,0 @@ -Tag: maintainer-script-needs-depends-on-adduser -Severity: warning -Check: scripts -Explanation: This script calls adduser, but the package does not depend or - pre-depend on the adduser package. diff -Nru lintian-2.93.0/tags/m/maintainer-script-needs-depends-on-gconf2.desc lintian-2.89.0ubuntu1/tags/m/maintainer-script-needs-depends-on-gconf2.desc --- lintian-2.93.0/tags/m/maintainer-script-needs-depends-on-gconf2.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/maintainer-script-needs-depends-on-gconf2.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: maintainer-script-needs-depends-on-gconf2 +Severity: warning +Check: scripts +Info: This script calls gconf-schemas, which comes from the gconf2 package, + but does not depend or pre-depend on gconf2. If you are using dh_gconf, + add a dependency on ${misc:Depends} and dh_gconf will take care of this + for you. diff -Nru lintian-2.93.0/tags/m/maintainer-script-needs-depends-on-gconf2.tag lintian-2.89.0ubuntu1/tags/m/maintainer-script-needs-depends-on-gconf2.tag --- lintian-2.93.0/tags/m/maintainer-script-needs-depends-on-gconf2.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/maintainer-script-needs-depends-on-gconf2.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: maintainer-script-needs-depends-on-gconf2 -Severity: warning -Check: scripts -Explanation: This script calls gconf-schemas, which comes from the gconf2 package, - but does not depend or pre-depend on gconf2. If you are using dh_gconf, - add a dependency on ${misc:Depends} and dh_gconf will take care of this - for you. diff -Nru lintian-2.93.0/tags/m/maintainer-script-needs-depends-on-ucf.desc lintian-2.89.0ubuntu1/tags/m/maintainer-script-needs-depends-on-ucf.desc --- lintian-2.93.0/tags/m/maintainer-script-needs-depends-on-ucf.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/maintainer-script-needs-depends-on-ucf.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,5 @@ +Tag: maintainer-script-needs-depends-on-ucf +Severity: warning +Check: scripts +Info: This script calls ucf, but the package does not depend or pre-depend + on the ucf package. diff -Nru lintian-2.93.0/tags/m/maintainer-script-needs-depends-on-ucf.tag lintian-2.89.0ubuntu1/tags/m/maintainer-script-needs-depends-on-ucf.tag --- lintian-2.93.0/tags/m/maintainer-script-needs-depends-on-ucf.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/maintainer-script-needs-depends-on-ucf.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,5 +0,0 @@ -Tag: maintainer-script-needs-depends-on-ucf -Severity: warning -Check: scripts -Explanation: This script calls ucf, but the package does not depend or pre-depend - on the ucf package. diff -Nru lintian-2.93.0/tags/m/maintainer-script-needs-depends-on-update-inetd.desc lintian-2.89.0ubuntu1/tags/m/maintainer-script-needs-depends-on-update-inetd.desc --- lintian-2.93.0/tags/m/maintainer-script-needs-depends-on-update-inetd.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/maintainer-script-needs-depends-on-update-inetd.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: maintainer-script-needs-depends-on-update-inetd +Severity: warning +Check: scripts +Info: This script calls update-inetd, but the package does not depend or + pre-depend on inet-superserver, any of the providers of inet-superserver + which provide it, or update-inetd. + . + update-inetd has been moved from netbase into a separate package, so a + dependency on netbase should be updated to depend on "openbsd-inetd | + inet-superserver". diff -Nru lintian-2.93.0/tags/m/maintainer-script-needs-depends-on-update-inetd.tag lintian-2.89.0ubuntu1/tags/m/maintainer-script-needs-depends-on-update-inetd.tag --- lintian-2.93.0/tags/m/maintainer-script-needs-depends-on-update-inetd.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/maintainer-script-needs-depends-on-update-inetd.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,10 +0,0 @@ -Tag: maintainer-script-needs-depends-on-update-inetd -Severity: warning -Check: scripts -Explanation: This script calls update-inetd, but the package does not depend or - pre-depend on inet-superserver, any of the providers of inet-superserver - which provide it, or update-inetd. - . - update-inetd has been moved from netbase into a separate package, so a - dependency on netbase should be updated to depend on "openbsd-inetd | - inet-superserver". diff -Nru lintian-2.93.0/tags/m/maintainer-script-needs-depends-on-xfonts-utils.desc lintian-2.89.0ubuntu1/tags/m/maintainer-script-needs-depends-on-xfonts-utils.desc --- lintian-2.93.0/tags/m/maintainer-script-needs-depends-on-xfonts-utils.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/maintainer-script-needs-depends-on-xfonts-utils.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,11 @@ +Tag: maintainer-script-needs-depends-on-xfonts-utils +Severity: warning +Check: scripts +Info: This script calls a utility provided by the xfonts-utils package + but does not depend or pre-depend on this package. + . + Packages that call update-fonts-scale, update-fonts-dir (etc.) need to + depend on xfonts-utils.If you are using debhelper. + . + Please add a dependency on ${misc:Depends} and dh_installxfonts will + take care of this for you. diff -Nru lintian-2.93.0/tags/m/maintainer-script-needs-depends-on-xfonts-utils.tag lintian-2.89.0ubuntu1/tags/m/maintainer-script-needs-depends-on-xfonts-utils.tag --- lintian-2.93.0/tags/m/maintainer-script-needs-depends-on-xfonts-utils.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/maintainer-script-needs-depends-on-xfonts-utils.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,11 +0,0 @@ -Tag: maintainer-script-needs-depends-on-xfonts-utils -Severity: warning -Check: scripts -Explanation: This script calls a utility provided by the xfonts-utils package - but does not depend or pre-depend on this package. - . - Packages that call update-fonts-scale, update-fonts-dir (etc.) need to - depend on xfonts-utils.If you are using debhelper. - . - Please add a dependency on ${misc:Depends} and dh_installxfonts will - take care of this for you. diff -Nru lintian-2.93.0/tags/m/maintainer-script-needs-depends-on-xml-core.desc lintian-2.89.0ubuntu1/tags/m/maintainer-script-needs-depends-on-xml-core.desc --- lintian-2.93.0/tags/m/maintainer-script-needs-depends-on-xml-core.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/maintainer-script-needs-depends-on-xml-core.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: maintainer-script-needs-depends-on-xml-core +Severity: warning +Check: scripts +Info: This script calls update-xmlcatalog, which comes from the xml-core + package, but does not depend or pre-depend on xml-core. Packages that call + update-xmlcatalog need to depend on xml-core. If you are using + dh_installxmlcatalogs, add a dependency on ${misc:Depends} and + dh_installxmlcatalogs will take care of this for you. diff -Nru lintian-2.93.0/tags/m/maintainer-script-needs-depends-on-xml-core.tag lintian-2.89.0ubuntu1/tags/m/maintainer-script-needs-depends-on-xml-core.tag --- lintian-2.93.0/tags/m/maintainer-script-needs-depends-on-xml-core.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/maintainer-script-needs-depends-on-xml-core.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: maintainer-script-needs-depends-on-xml-core -Severity: warning -Check: scripts -Explanation: This script calls update-xmlcatalog, which comes from the xml-core - package, but does not depend or pre-depend on xml-core. Packages that call - update-xmlcatalog need to depend on xml-core. If you are using - dh_installxmlcatalogs, add a dependency on ${misc:Depends} and - dh_installxmlcatalogs will take care of this for you. diff -Nru lintian-2.93.0/tags/m/maintainer-script-removes-device-files.desc lintian-2.89.0ubuntu1/tags/m/maintainer-script-removes-device-files.desc --- lintian-2.93.0/tags/m/maintainer-script-removes-device-files.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/maintainer-script-removes-device-files.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: maintainer-script-removes-device-files +Severity: error +Check: scripts +Ref: policy 10.6 +Info: Maintainer scripts must not remove device files. This is left to + the system administrator. diff -Nru lintian-2.93.0/tags/m/maintainer-script-removes-device-files.tag lintian-2.89.0ubuntu1/tags/m/maintainer-script-removes-device-files.tag --- lintian-2.93.0/tags/m/maintainer-script-removes-device-files.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/maintainer-script-removes-device-files.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: maintainer-script-removes-device-files -Severity: error -Check: scripts -See-Also: policy 10.6 -Explanation: Maintainer scripts must not remove device files. This is left to - the system administrator. diff -Nru lintian-2.93.0/tags/m/maintainer-script-sets-alternative-improperly.desc lintian-2.89.0ubuntu1/tags/m/maintainer-script-sets-alternative-improperly.desc --- lintian-2.93.0/tags/m/maintainer-script-sets-alternative-improperly.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/maintainer-script-sets-alternative-improperly.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,12 @@ +Tag: maintainer-script-sets-alternative-improperly +Severity: warning +Check: scripts +Renamed-From: maintainer-script-should-not-use-update-alternatives-set +Info: The maintainer script calls update-alternatives --set + <alternative> foo or update-alternatives --config + <alternative> or update-alternatives --set-selections. + . + This makes it impossible to distinguish between an alternative that's + manually set because the user set it and one that's manually set because + the package set it. +Ref: update-alternatives(8) diff -Nru lintian-2.93.0/tags/m/maintainer-script-sets-alternative-improperly.tag lintian-2.89.0ubuntu1/tags/m/maintainer-script-sets-alternative-improperly.tag --- lintian-2.93.0/tags/m/maintainer-script-sets-alternative-improperly.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/maintainer-script-sets-alternative-improperly.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,12 +0,0 @@ -Tag: maintainer-script-sets-alternative-improperly -Severity: warning -Check: scripts -Renamed-From: maintainer-script-should-not-use-update-alternatives-set -Explanation: The maintainer script calls update-alternatives --set - <alternative> foo or update-alternatives --config - <alternative> or update-alternatives --set-selections. - . - This makes it impossible to distinguish between an alternative that's - manually set because the user set it and one that's manually set because - the package set it. -See-Also: update-alternatives(8) diff -Nru lintian-2.93.0/tags/m/maintainer-script-should-not-parse-etc-passwd-or-group.desc lintian-2.89.0ubuntu1/tags/m/maintainer-script-should-not-parse-etc-passwd-or-group.desc --- lintian-2.93.0/tags/m/maintainer-script-should-not-parse-etc-passwd-or-group.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/maintainer-script-should-not-parse-etc-passwd-or-group.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,11 @@ +Tag: maintainer-script-should-not-parse-etc-passwd-or-group +Severity: warning +Certainty: possible +Check: scripts +Ref: getent(1), nss(5) +Info: The maintainer script appears to manually parse /etc/passwd + or /etc/group instead of using the getent(1) utility + to display entries. + . + This bypasses the Name Service Switch (NSS), avoiding querying + centralised or networked user databases such as LDAP, etc. diff -Nru lintian-2.93.0/tags/m/maintainer-script-should-not-parse-etc-passwd-or-group.tag lintian-2.89.0ubuntu1/tags/m/maintainer-script-should-not-parse-etc-passwd-or-group.tag --- lintian-2.93.0/tags/m/maintainer-script-should-not-parse-etc-passwd-or-group.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/maintainer-script-should-not-parse-etc-passwd-or-group.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,10 +0,0 @@ -Tag: maintainer-script-should-not-parse-etc-passwd-or-group -Severity: warning -Check: scripts -See-Also: getent(1), nss(5) -Explanation: The maintainer script appears to manually parse /etc/passwd - or /etc/group instead of using the getent(1) utility - to display entries. - . - This bypasses the Name Service Switch (NSS), avoiding querying - centralised or networked user databases such as LDAP, etc. diff -Nru lintian-2.93.0/tags/m/maintainer-script-should-not-use-dpkg-maintscript-helper.desc lintian-2.89.0ubuntu1/tags/m/maintainer-script-should-not-use-dpkg-maintscript-helper.desc --- lintian-2.93.0/tags/m/maintainer-script-should-not-use-dpkg-maintscript-helper.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/maintainer-script-should-not-use-dpkg-maintscript-helper.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: maintainer-script-should-not-use-dpkg-maintscript-helper +Severity: warning +Check: scripts +Info: The maintainer script seems to make manual calls to the + dpkg-maintscript-helper(1) utility. + . + Please use package.maintscript files instead; the + dh_installdeb(1) tool will do some basic validation of some of + the commands listed in this file to catch common mistakes. +Ref: dpkg-maintscript-helper(1), dh_installdeb(1) diff -Nru lintian-2.93.0/tags/m/maintainer-script-should-not-use-dpkg-maintscript-helper.tag lintian-2.89.0ubuntu1/tags/m/maintainer-script-should-not-use-dpkg-maintscript-helper.tag --- lintian-2.93.0/tags/m/maintainer-script-should-not-use-dpkg-maintscript-helper.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/maintainer-script-should-not-use-dpkg-maintscript-helper.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,10 +0,0 @@ -Tag: maintainer-script-should-not-use-dpkg-maintscript-helper -Severity: warning -Check: scripts -Explanation: The maintainer script seems to make manual calls to the - dpkg-maintscript-helper(1) utility. - . - Please use package.maintscript files instead; the - dh_installdeb(1) tool will do some basic validation of some of - the commands listed in this file to catch common mistakes. -See-Also: dpkg-maintscript-helper(1), dh_installdeb(1) diff -Nru lintian-2.93.0/tags/m/maintainer-script-should-not-use-piuparts-variable.desc lintian-2.89.0ubuntu1/tags/m/maintainer-script-should-not-use-piuparts-variable.desc --- lintian-2.93.0/tags/m/maintainer-script-should-not-use-piuparts-variable.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/maintainer-script-should-not-use-piuparts-variable.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,13 @@ +Tag: maintainer-script-should-not-use-piuparts-variable +Severity: warning +Certainty: possible +Check: scripts +Ref: piuparts(1), https://piuparts.debian.org/doc/README.html +Info: The maintainer script appears to reference one of the + PIUPARTS_* variables such as PIUPARTS_TEST or + PIUPARTS_PHASE. + . + These variables are intended to be used by custom piuparts(1) + scripts and not by maintainer scripts themselves. + . + Please remove the references to this variable. diff -Nru lintian-2.93.0/tags/m/maintainer-script-should-not-use-piuparts-variable.tag lintian-2.89.0ubuntu1/tags/m/maintainer-script-should-not-use-piuparts-variable.tag --- lintian-2.93.0/tags/m/maintainer-script-should-not-use-piuparts-variable.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/maintainer-script-should-not-use-piuparts-variable.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,12 +0,0 @@ -Tag: maintainer-script-should-not-use-piuparts-variable -Severity: warning -Check: scripts -See-Also: piuparts(1), https://piuparts.debian.org/doc/README.html -Explanation: The maintainer script appears to reference one of the - PIUPARTS_* variables such as PIUPARTS_TEST or - PIUPARTS_PHASE. - . - These variables are intended to be used by custom piuparts(1) - scripts and not by maintainer scripts themselves. - . - Please remove the references to this variable. diff -Nru lintian-2.93.0/tags/m/maintainer-script-supports-ancient-package-version.desc lintian-2.89.0ubuntu1/tags/m/maintainer-script-supports-ancient-package-version.desc --- lintian-2.93.0/tags/m/maintainer-script-supports-ancient-package-version.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/maintainer-script-supports-ancient-package-version.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: maintainer-script-supports-ancient-package-version +Severity: info +Certainty: possible +Check: scripts +Experimental: yes +Info: The maintainer script appears to detect the specified version + which was prepared prior to the release of oldstable. + . + Please remove the code/check for this version as such upgrades + (etc.) are unsupported. diff -Nru lintian-2.93.0/tags/m/maintainer-script-supports-ancient-package-version.tag lintian-2.89.0ubuntu1/tags/m/maintainer-script-supports-ancient-package-version.tag --- lintian-2.93.0/tags/m/maintainer-script-supports-ancient-package-version.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/maintainer-script-supports-ancient-package-version.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: maintainer-script-supports-ancient-package-version -Severity: info -Check: scripts -Experimental: yes -Explanation: The maintainer script appears to detect the specified version - which was prepared prior to the release of oldstable. - . - Please remove the code/check for this version as such upgrades - (etc.) are unsupported. diff -Nru lintian-2.93.0/tags/m/maintainer-script-switches-dir-to-symlink-unsafely.desc lintian-2.89.0ubuntu1/tags/m/maintainer-script-switches-dir-to-symlink-unsafely.desc --- lintian-2.93.0/tags/m/maintainer-script-switches-dir-to-symlink-unsafely.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/maintainer-script-switches-dir-to-symlink-unsafely.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,12 @@ +Tag: maintainer-script-switches-dir-to-symlink-unsafely +Severity: error +Certainty: possible +Check: scripts +Experimental: yes +Renamed-From: maintainer-script-may-use-dir_to_symlink_helper +Info: The maintainer script apparently change a directory to a symlink + not using dir_to_symlink command of dpkg-maintscript-helper, that take + great care to avoid a lot of problems. + . + Please use the dpkg-maintscript-helper dir_to_symlink command. +Ref: dpkg-maintscript-helper(1) diff -Nru lintian-2.93.0/tags/m/maintainer-script-switches-dir-to-symlink-unsafely.tag lintian-2.89.0ubuntu1/tags/m/maintainer-script-switches-dir-to-symlink-unsafely.tag --- lintian-2.93.0/tags/m/maintainer-script-switches-dir-to-symlink-unsafely.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/maintainer-script-switches-dir-to-symlink-unsafely.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,11 +0,0 @@ -Tag: maintainer-script-switches-dir-to-symlink-unsafely -Severity: error -Check: scripts -Experimental: yes -Renamed-From: maintainer-script-may-use-dir_to_symlink_helper -Explanation: The maintainer script apparently change a directory to a symlink - not using dir_to_symlink command of dpkg-maintscript-helper, that take - great care to avoid a lot of problems. - . - Please use the dpkg-maintscript-helper dir_to_symlink command. -See-Also: dpkg-maintscript-helper(1) diff -Nru lintian-2.93.0/tags/m/maintainer-script-updates-fontconfig-cache-improperly.desc lintian-2.89.0ubuntu1/tags/m/maintainer-script-updates-fontconfig-cache-improperly.desc --- lintian-2.93.0/tags/m/maintainer-script-updates-fontconfig-cache-improperly.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/maintainer-script-updates-fontconfig-cache-improperly.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: maintainer-script-updates-fontconfig-cache-improperly +Severity: warning +Certainty: possible +Check: scripts +Renamed-From: maintainer-script-should-not-use-fc-cache +Info: This script apparently runs fc-cache. Updating of the fontconfig + cache files is now handled automatically by triggers, so running fc-cache + from maintainer scripts is no longer necessary. diff -Nru lintian-2.93.0/tags/m/maintainer-script-updates-fontconfig-cache-improperly.tag lintian-2.89.0ubuntu1/tags/m/maintainer-script-updates-fontconfig-cache-improperly.tag --- lintian-2.93.0/tags/m/maintainer-script-updates-fontconfig-cache-improperly.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/maintainer-script-updates-fontconfig-cache-improperly.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: maintainer-script-updates-fontconfig-cache-improperly -Severity: warning -Check: scripts -Renamed-From: maintainer-script-should-not-use-fc-cache -Explanation: This script apparently runs fc-cache. Updating of the fontconfig - cache files is now handled automatically by triggers, so running fc-cache - from maintainer scripts is no longer necessary. diff -Nru lintian-2.93.0/tags/m/maintainer-script-without-set-e.desc lintian-2.89.0ubuntu1/tags/m/maintainer-script-without-set-e.desc --- lintian-2.93.0/tags/m/maintainer-script-without-set-e.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/maintainer-script-without-set-e.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: maintainer-script-without-set-e +Severity: pedantic +Check: scripts +Ref: policy 10.4 +Info: The maintainer script passes -e to the shell on the + #! line rather than using set -e in the body of the + script. This is fine for normal operation, but if the script is run by + hand with sh /path/to/script (common in debugging), -e + will not be in effect. It's therefore better to use set -e in + the body of the script. diff -Nru lintian-2.93.0/tags/m/maintainer-script-without-set-e.tag lintian-2.89.0ubuntu1/tags/m/maintainer-script-without-set-e.tag --- lintian-2.93.0/tags/m/maintainer-script-without-set-e.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/maintainer-script-without-set-e.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,10 +0,0 @@ -Tag: maintainer-script-without-set-e -Severity: pedantic -Check: scripts -See-Also: policy 10.4 -Explanation: The maintainer script passes -e to the shell on the - #! line rather than using set -e in the body of the - script. This is fine for normal operation, but if the script is run by - hand with sh /path/to/script (common in debugging), -e - will not be in effect. It's therefore better to use set -e in - the body of the script. diff -Nru lintian-2.93.0/tags/m/maintainer-shell-script-fails-syntax-check.desc lintian-2.89.0ubuntu1/tags/m/maintainer-shell-script-fails-syntax-check.desc --- lintian-2.93.0/tags/m/maintainer-shell-script-fails-syntax-check.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/maintainer-shell-script-fails-syntax-check.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: maintainer-shell-script-fails-syntax-check +Severity: error +Check: scripts +Info: Running this shell script with the shell's -n option set fails, + which means that the script has syntax errors. This will likely make + the package uninstallable. + . + Run e.g. sh -n yourscript to see the errors yourself. diff -Nru lintian-2.93.0/tags/m/maintainer-shell-script-fails-syntax-check.tag lintian-2.89.0ubuntu1/tags/m/maintainer-shell-script-fails-syntax-check.tag --- lintian-2.93.0/tags/m/maintainer-shell-script-fails-syntax-check.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/maintainer-shell-script-fails-syntax-check.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: maintainer-shell-script-fails-syntax-check -Severity: error -Check: scripts -Explanation: Running this shell script with the shell's -n option set fails, - which means that the script has syntax errors. This will likely make - the package uninstallable. - . - Run e.g. sh -n yourscript to see the errors yourself. diff -Nru lintian-2.93.0/tags/m/maintainer-upload-has-incorrect-version-number.desc lintian-2.89.0ubuntu1/tags/m/maintainer-upload-has-incorrect-version-number.desc --- lintian-2.93.0/tags/m/maintainer-upload-has-incorrect-version-number.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/maintainer-upload-has-incorrect-version-number.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: maintainer-upload-has-incorrect-version-number +Severity: warning +Check: nmu +Info: A maintainer upload should have a Debian revision without dots. + Revisions with dots are reserved for Non-Maintainer Uploads (NMUs). If you + do a maintainer-upload with dots a potential NMU'er has problems choosing a + correct version number. diff -Nru lintian-2.93.0/tags/m/maintainer-upload-has-incorrect-version-number.tag lintian-2.89.0ubuntu1/tags/m/maintainer-upload-has-incorrect-version-number.tag --- lintian-2.93.0/tags/m/maintainer-upload-has-incorrect-version-number.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/maintainer-upload-has-incorrect-version-number.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: maintainer-upload-has-incorrect-version-number -Severity: warning -Check: nmu -Explanation: A maintainer upload should have a Debian revision without dots. - Revisions with dots are reserved for Non-Maintainer Uploads (NMUs). If you - do a maintainer-upload with dots a potential NMU'er has problems choosing a - correct version number. diff -Nru lintian-2.93.0/tags/m/maintscript-calls-ldconfig.desc lintian-2.89.0ubuntu1/tags/m/maintscript-calls-ldconfig.desc --- lintian-2.93.0/tags/m/maintscript-calls-ldconfig.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/maintscript-calls-ldconfig.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,16 @@ +Tag: maintscript-calls-ldconfig +Severity: warning +Check: shared-libs +Info: The given maintainer script calls ldconfig. However, explicit + calls in maintainer scripts should be replaced by a dpkg trigger. + . + Please replace the "ldconfig" call with an activate-noawait + ldconfig trigger. With debhelper it is usually sufficient + to simply add that line to debian/<package>.triggers. + . + If you use debhelper, this warning will appear if the package was + compiled with debhelper before 9.20151004. Assuming all ldconfig + invocations have been added by debhelper, this warning will + disappear once the package is rebuilt with a newer version of + debhelper. +Ref: https://lists.debian.org/debian-devel/2015/08/msg00412.html diff -Nru lintian-2.93.0/tags/m/maintscript-calls-ldconfig.tag lintian-2.89.0ubuntu1/tags/m/maintscript-calls-ldconfig.tag --- lintian-2.93.0/tags/m/maintscript-calls-ldconfig.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/maintscript-calls-ldconfig.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,16 +0,0 @@ -Tag: maintscript-calls-ldconfig -Severity: warning -Check: shared-libs -Explanation: The given maintainer script calls ldconfig. However, explicit - calls in maintainer scripts should be replaced by a dpkg trigger. - . - Please replace the "ldconfig" call with an activate-noawait - ldconfig trigger. With debhelper it is usually sufficient - to simply add that line to debian/<package>.triggers. - . - If you use debhelper, this warning will appear if the package was - compiled with debhelper before 9.20151004. Assuming all ldconfig - invocations have been added by debhelper, this warning will - disappear once the package is rebuilt with a newer version of - debhelper. -See-Also: https://lists.debian.org/debian-devel/2015/08/msg00412.html diff -Nru lintian-2.93.0/tags/m/maintscript-includes-maint-script-parameters.desc lintian-2.89.0ubuntu1/tags/m/maintscript-includes-maint-script-parameters.desc --- lintian-2.93.0/tags/m/maintscript-includes-maint-script-parameters.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/maintscript-includes-maint-script-parameters.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: maintscript-includes-maint-script-parameters +Severity: warning +Certainty: possible +Check: debhelper +Info: Lines in a debian/*.maintscript correspond to + dpkg-maintscript-helper(1) commands and parameters. However, the + "maint-script-parameters" should not be included as debhelper will add those + automatically. See dh_installdeb(1) for more information. diff -Nru lintian-2.93.0/tags/m/maintscript-includes-maint-script-parameters.tag lintian-2.89.0ubuntu1/tags/m/maintscript-includes-maint-script-parameters.tag --- lintian-2.93.0/tags/m/maintscript-includes-maint-script-parameters.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/maintscript-includes-maint-script-parameters.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: maintscript-includes-maint-script-parameters -Severity: warning -Check: debhelper -Explanation: Lines in a debian/*.maintscript correspond to - dpkg-maintscript-helper(1) commands and parameters. However, the - "maint-script-parameters" should not be included as debhelper will add those - automatically. See dh_installdeb(1) for more information. diff -Nru lintian-2.93.0/tags/m/making-assumptions-about-interfaces-in-templates.desc lintian-2.89.0ubuntu1/tags/m/making-assumptions-about-interfaces-in-templates.desc --- lintian-2.93.0/tags/m/making-assumptions-about-interfaces-in-templates.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/making-assumptions-about-interfaces-in-templates.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: making-assumptions-about-interfaces-in-templates +Severity: warning +Certainty: possible +Check: debian/debconf +Info: Template text should not make reference to widgets belonging to + some debconf interfaces. Sentences like "If you answer Yes..." have no + meaning for users of graphical interfaces which use checkboxes for + boolean questions. +Ref: devref 6.5.2.4 diff -Nru lintian-2.93.0/tags/m/making-assumptions-about-interfaces-in-templates.tag lintian-2.89.0ubuntu1/tags/m/making-assumptions-about-interfaces-in-templates.tag --- lintian-2.93.0/tags/m/making-assumptions-about-interfaces-in-templates.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/making-assumptions-about-interfaces-in-templates.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: making-assumptions-about-interfaces-in-templates -Severity: warning -Check: debian/debconf -Explanation: Template text should not make reference to widgets belonging to - some debconf interfaces. Sentences like "If you answer Yes..." have no - meaning for users of graphical interfaces which use checkboxes for - boolean questions. -See-Also: devref 6.5.2.4 diff -Nru lintian-2.93.0/tags/m/malformed-changes-file.desc lintian-2.89.0ubuntu1/tags/m/malformed-changes-file.desc --- lintian-2.93.0/tags/m/malformed-changes-file.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/malformed-changes-file.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,11 @@ +Tag: malformed-changes-file +Severity: error +Check: fields/format +Info: There is no "Format" field in your .changes file. This probably + indicates some serious problem with the file. Perhaps it's not actually + a changes file, or it's not in the proper format, or it's PGP-signed + twice. + . + Since Lintian was unable to parse this .changes file, any further checks + on it were skipped. +Ref: policy 5.5 diff -Nru lintian-2.93.0/tags/m/malformed-changes-file.tag lintian-2.89.0ubuntu1/tags/m/malformed-changes-file.tag --- lintian-2.93.0/tags/m/malformed-changes-file.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/malformed-changes-file.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,11 +0,0 @@ -Tag: malformed-changes-file -Severity: error -Check: fields/format -Explanation: There is no "Format" field in your .changes file. This probably - indicates some serious problem with the file. Perhaps it's not actually - a changes file, or it's not in the proper format, or it's PGP-signed - twice. - . - Since Lintian was unable to parse this .changes file, any further checks - on it were skipped. -See-Also: policy 5.5 diff -Nru lintian-2.93.0/tags/m/malformed-contact.desc lintian-2.89.0ubuntu1/tags/m/malformed-contact.desc --- lintian-2.93.0/tags/m/malformed-contact.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/malformed-contact.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,17 @@ +Tag: malformed-contact +Severity: error +Check: fields/mail-address +Renamed-From: + maintainer-address-missing + changed-by-address-missing + malformed-maintainer-field + malformed-uploaders-field + malformed-changed-by-field + maintainer-address-malformed + uploader-address-malformed + changed-by-address-malformed +Info: The named field identifying contact persons could not be + parsed according to the rules in the Policy Manual. +Ref: policy 5.6.2, + policy 5.6.3, + policy 5.6.4 diff -Nru lintian-2.93.0/tags/m/malformed-contact.tag lintian-2.89.0ubuntu1/tags/m/malformed-contact.tag --- lintian-2.93.0/tags/m/malformed-contact.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/malformed-contact.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,17 +0,0 @@ -Tag: malformed-contact -Severity: error -Check: fields/mail-address -Renamed-From: - maintainer-address-missing - changed-by-address-missing - malformed-maintainer-field - malformed-uploaders-field - malformed-changed-by-field - maintainer-address-malformed - uploader-address-malformed - changed-by-address-malformed -Explanation: The named field identifying contact persons could not be - parsed according to the rules in the Policy Manual. -See-Also: policy 5.6.2, - policy 5.6.3, - policy 5.6.4 diff -Nru lintian-2.93.0/tags/m/malformed-deb-archive.desc lintian-2.89.0ubuntu1/tags/m/malformed-deb-archive.desc --- lintian-2.93.0/tags/m/malformed-deb-archive.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/malformed-deb-archive.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,11 @@ +Tag: malformed-deb-archive +Severity: error +Check: deb-format +Info: The binary package is not a correctly constructed archive. A binary + Debian package must be an ar archive with exactly three members: + debian-binary, control.tar.gz, and one of + data.tar.gz, data.tar.bz2 or data.tar.xz + in exactly that order. The debian-binary member must start + with a single line containing the version number, with a major revision + of 2. +Ref: deb(5) diff -Nru lintian-2.93.0/tags/m/malformed-deb-archive.tag lintian-2.89.0ubuntu1/tags/m/malformed-deb-archive.tag --- lintian-2.93.0/tags/m/malformed-deb-archive.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/malformed-deb-archive.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,11 +0,0 @@ -Tag: malformed-deb-archive -Severity: error -Check: deb-format -Explanation: The binary package is not a correctly constructed archive. A binary - Debian package must be an ar archive with exactly three members: - debian-binary, control.tar.gz, and one of - data.tar.gz, data.tar.bz2 or data.tar.xz - in exactly that order. The debian-binary member must start - with a single line containing the version number, with a major revision - of 2. -See-Also: deb(5) diff -Nru lintian-2.93.0/tags/m/malformed-debian-changelog-version.desc lintian-2.89.0ubuntu1/tags/m/malformed-debian-changelog-version.desc --- lintian-2.93.0/tags/m/malformed-debian-changelog-version.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/malformed-debian-changelog-version.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: malformed-debian-changelog-version +Severity: error +Check: debian/changelog +Info: The version string in the latest changelog entry was not parsed + correctly. Usually, that means it does not conform to policy. +Ref: policy 5.6.12 diff -Nru lintian-2.93.0/tags/m/malformed-debian-changelog-version.tag lintian-2.89.0ubuntu1/tags/m/malformed-debian-changelog-version.tag --- lintian-2.93.0/tags/m/malformed-debian-changelog-version.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/malformed-debian-changelog-version.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: malformed-debian-changelog-version -Severity: error -Check: debian/changelog -Explanation: The version string in the latest changelog entry was not parsed - correctly. Usually, that means it does not conform to policy. -See-Also: policy 5.6.12 diff -Nru lintian-2.93.0/tags/m/malformed-dm-upload-allowed.desc lintian-2.89.0ubuntu1/tags/m/malformed-dm-upload-allowed.desc --- lintian-2.93.0/tags/m/malformed-dm-upload-allowed.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/malformed-dm-upload-allowed.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: malformed-dm-upload-allowed +Severity: error +Check: fields/dm-upload-allowed +Ref: https://www.debian.org/vote/2007/vote_003 +Info: The Dm-Upload-Allowed field in this package is set to something + other than "yes". The only standardized value for this field in the + Debian GR is "yes" and other values (including capitalization variants) + may not work as expected. diff -Nru lintian-2.93.0/tags/m/malformed-dm-upload-allowed.tag lintian-2.89.0ubuntu1/tags/m/malformed-dm-upload-allowed.tag --- lintian-2.93.0/tags/m/malformed-dm-upload-allowed.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/malformed-dm-upload-allowed.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: malformed-dm-upload-allowed -Severity: error -Check: fields/dm-upload-allowed -See-Also: https://www.debian.org/vote/2007/vote_003 -Explanation: The Dm-Upload-Allowed field in this package is set to something - other than "yes". The only standardized value for this field in the - Debian GR is "yes" and other values (including capitalization variants) - may not work as expected. diff -Nru lintian-2.93.0/tags/m/malformed-md5sums-control-file.desc lintian-2.89.0ubuntu1/tags/m/malformed-md5sums-control-file.desc --- lintian-2.93.0/tags/m/malformed-md5sums-control-file.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/malformed-md5sums-control-file.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: malformed-md5sums-control-file +Severity: error +Check: md5sums +Info: The indicated line of the md5sums control file for this package was + malformed. Each line of an md5sums control file should contain an MD5 + checksum, some whitespace, and then the path to the file corresponding to + that checksum. diff -Nru lintian-2.93.0/tags/m/malformed-md5sums-control-file.tag lintian-2.89.0ubuntu1/tags/m/malformed-md5sums-control-file.tag --- lintian-2.93.0/tags/m/malformed-md5sums-control-file.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/malformed-md5sums-control-file.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: malformed-md5sums-control-file -Severity: error -Check: md5sums -Explanation: The indicated line of the md5sums control file for this package was - malformed. Each line of an md5sums control file should contain an MD5 - checksum, some whitespace, and then the path to the file corresponding to - that checksum. diff -Nru lintian-2.93.0/tags/m/malformed-override.desc lintian-2.89.0ubuntu1/tags/m/malformed-override.desc --- lintian-2.93.0/tags/m/malformed-override.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/malformed-override.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,13 @@ +Tag: malformed-override +Severity: error +Check: lintian +Ref: lintian 2.4.1 +Info: Lintian discovered an override entry with an invalid format. An + override entry should have the format: + . + [[<package>][ <archlist>][ <type>]:] <tag>[ <extra> ...] + . + where <package> is the package name, <archlist> is an + architecture list, <type> specifies the package type (binary is the + default), <tag> is the tag to override, and <extra> is any + specific information for the particular tag to override. diff -Nru lintian-2.93.0/tags/m/malformed-override.tag lintian-2.89.0ubuntu1/tags/m/malformed-override.tag --- lintian-2.93.0/tags/m/malformed-override.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/malformed-override.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,13 +0,0 @@ -Tag: malformed-override -Severity: error -Check: lintian -See-Also: lintian 2.4.1 -Explanation: Lintian discovered an override entry with an invalid format. An - override entry should have the format: - . - [[<package>][ <archlist>][ <type>]:] <tag>[ <extra> ...] - . - where <package> is the package name, <archlist> is an - architecture list, <type> specifies the package type (binary is the - default), <tag> is the tag to override, and <extra> is any - specific information for the particular tag to override. diff -Nru lintian-2.93.0/tags/m/malformed-prompt-in-templates.desc lintian-2.89.0ubuntu1/tags/m/malformed-prompt-in-templates.desc --- lintian-2.93.0/tags/m/malformed-prompt-in-templates.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/malformed-prompt-in-templates.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,11 @@ +Tag: malformed-prompt-in-templates +Severity: warning +Check: debian/debconf +Info: The short description of a select, multiselect, string and password + debconf template is a prompt and not a title. Avoid question style + prompts ("IP Address?") in favour of "opened" prompts ("IP address:"). + The use of colons is recommended. + . + If this template is only used internally by the package and not displayed + to the user, put "for internal use" in the short description. +Ref: devref 6.5.4.2 diff -Nru lintian-2.93.0/tags/m/malformed-prompt-in-templates.tag lintian-2.89.0ubuntu1/tags/m/malformed-prompt-in-templates.tag --- lintian-2.93.0/tags/m/malformed-prompt-in-templates.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/malformed-prompt-in-templates.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,11 +0,0 @@ -Tag: malformed-prompt-in-templates -Severity: warning -Check: debian/debconf -Explanation: The short description of a select, multiselect, string and password - debconf template is a prompt and not a title. Avoid question style - prompts ("IP Address?") in favour of "opened" prompts ("IP address:"). - The use of colons is recommended. - . - If this template is only used internally by the package and not displayed - to the user, put "for internal use" in the short description. -See-Also: devref 6.5.4.2 diff -Nru lintian-2.93.0/tags/m/malformed-python-version.desc lintian-2.89.0ubuntu1/tags/m/malformed-python-version.desc --- lintian-2.93.0/tags/m/malformed-python-version.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/malformed-python-version.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,16 @@ +Tag: malformed-python-version +Severity: error +Check: languages/python +Ref: python-policy 3.4 +Info: The Python-Version or Python3-Version control field is not in one + of the valid formats. It should be in one of the following: + . + all + current + current, >= X.Y + >= X.Y + >= A.B, << X.Y + A.B, X.Y + . + (One or more specific versions may be listed with the last form.) A.B + and X.Y should be Python versions. diff -Nru lintian-2.93.0/tags/m/malformed-python-version.tag lintian-2.89.0ubuntu1/tags/m/malformed-python-version.tag --- lintian-2.93.0/tags/m/malformed-python-version.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/malformed-python-version.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,16 +0,0 @@ -Tag: malformed-python-version -Severity: error -Check: languages/python -See-Also: python-policy 3.4 -Explanation: The Python-Version or Python3-Version control field is not in one - of the valid formats. It should be in one of the following: - . - all - current - current, >= X.Y - >= X.Y - >= A.B, << X.Y - A.B, X.Y - . - (One or more specific versions may be listed with the last form.) A.B - and X.Y should be Python versions. diff -Nru lintian-2.93.0/tags/m/malformed-question-in-templates.desc lintian-2.89.0ubuntu1/tags/m/malformed-question-in-templates.desc --- lintian-2.93.0/tags/m/malformed-question-in-templates.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/malformed-question-in-templates.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,11 @@ +Tag: malformed-question-in-templates +Severity: warning +Check: debian/debconf +Info: The short description of a boolean debconf template should be + phrased in the form of a question which should be kept short and should + generally end with a question mark. Terse writing style is permitted and + even encouraged if the question is rather long. + . + If this template is only used internally by the package and not displayed + to the user, put "for internal use" in the short description. +Ref: devref 6.5.4.2.2 diff -Nru lintian-2.93.0/tags/m/malformed-question-in-templates.tag lintian-2.89.0ubuntu1/tags/m/malformed-question-in-templates.tag --- lintian-2.93.0/tags/m/malformed-question-in-templates.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/malformed-question-in-templates.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,11 +0,0 @@ -Tag: malformed-question-in-templates -Severity: warning -Check: debian/debconf -Explanation: The short description of a boolean debconf template should be - phrased in the form of a question which should be kept short and should - generally end with a question mark. Terse writing style is permitted and - even encouraged if the question is rather long. - . - If this template is only used internally by the package and not displayed - to the user, put "for internal use" in the short description. -See-Also: devref 6.5.4.2.2 diff -Nru lintian-2.93.0/tags/m/malformed-template-name.desc lintian-2.89.0ubuntu1/tags/m/malformed-template-name.desc --- lintian-2.93.0/tags/m/malformed-template-name.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/malformed-template-name.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: malformed-template-name +Severity: error +Check: debian/debconf +Info: The "Template:" field should contain more than one component, each + separated by a slash ("/"). Each component may only consist of the + alphanumeric characters, "+", "-", and ".". diff -Nru lintian-2.93.0/tags/m/malformed-template-name.tag lintian-2.89.0ubuntu1/tags/m/malformed-template-name.tag --- lintian-2.93.0/tags/m/malformed-template-name.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/malformed-template-name.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: malformed-template-name -Severity: error -Check: debian/debconf -Explanation: The "Template:" field should contain more than one component, each - separated by a slash ("/"). Each component may only consist of the - alphanumeric characters, "+", "-", and ".". diff -Nru lintian-2.93.0/tags/m/malformed-title-in-templates.desc lintian-2.89.0ubuntu1/tags/m/malformed-title-in-templates.desc --- lintian-2.93.0/tags/m/malformed-title-in-templates.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/malformed-title-in-templates.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: malformed-title-in-templates +Severity: warning +Check: debian/debconf +Info: The short description of a note debconf template should be written + as a title and therefore should not end with a period, question mark, + colon, or semicolon. +Ref: devref 6.5.4.2.4 diff -Nru lintian-2.93.0/tags/m/malformed-title-in-templates.tag lintian-2.89.0ubuntu1/tags/m/malformed-title-in-templates.tag --- lintian-2.93.0/tags/m/malformed-title-in-templates.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/malformed-title-in-templates.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: malformed-title-in-templates -Severity: warning -Check: debian/debconf -Explanation: The short description of a note debconf template should be written - as a title and therefore should not end with a period, question mark, - colon, or semicolon. -See-Also: devref 6.5.4.2.4 diff -Nru lintian-2.93.0/tags/m/manual-page-for-system-command.desc lintian-2.89.0ubuntu1/tags/m/manual-page-for-system-command.desc --- lintian-2.93.0/tags/m/manual-page-for-system-command.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/manual-page-for-system-command.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,13 @@ +Tag: manual-page-for-system-command +Check: documentation/manual +Severity: pedantic +Renamed-From: command-in-sbin-has-manpage-in-incorrect-section +Info: The command in /sbin or /usr/sbin are system + administration commands; their manual pages thus belong in section 8, + not section 1. + . + Please check whether the command is actually useful to non-privileged + user in which case it should be moved to /bin or + /usr/bin, or alternatively the manual page should be moved to + section 8 instead, ie. /usr/share/man/man8. +Ref: hier(7) diff -Nru lintian-2.93.0/tags/m/manual-page-for-system-command.tag lintian-2.89.0ubuntu1/tags/m/manual-page-for-system-command.tag --- lintian-2.93.0/tags/m/manual-page-for-system-command.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/manual-page-for-system-command.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,13 +0,0 @@ -Tag: manual-page-for-system-command -Check: documentation/manual -Severity: pedantic -Renamed-From: command-in-sbin-has-manpage-in-incorrect-section -Explanation: The command in /sbin or /usr/sbin are system - administration commands; their manual pages thus belong in section 8, - not section 1. - . - Please check whether the command is actually useful to non-privileged - user in which case it should be moved to /bin or - /usr/bin, or alternatively the manual page should be moved to - section 8 instead, ie. /usr/share/man/man8. -See-Also: hier(7) diff -Nru lintian-2.93.0/tags/m/manual-page-from-template.desc lintian-2.89.0ubuntu1/tags/m/manual-page-from-template.desc --- lintian-2.93.0/tags/m/manual-page-from-template.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/manual-page-from-template.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,12 @@ +Tag: manual-page-from-template +Severity: error +Check: documentation/manual +Renamed-From: manpage-is-dh_make-template +Info: This manual page appears to be an unmodified or insufficiently + modified copy of the dh_make manual page template. It has a whatis entry + (the brief description found in the NAME section) of the form: + . + package - program to do something + . + Please double-check the manual page and replace the template language + with specific information about this program. diff -Nru lintian-2.93.0/tags/m/manual-page-from-template.tag lintian-2.89.0ubuntu1/tags/m/manual-page-from-template.tag --- lintian-2.93.0/tags/m/manual-page-from-template.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/manual-page-from-template.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,12 +0,0 @@ -Tag: manual-page-from-template -Severity: error -Check: documentation/manual -Renamed-From: manpage-is-dh_make-template -Explanation: This manual page appears to be an unmodified or insufficiently - modified copy of the dh_make manual page template. It has a whatis entry - (the brief description found in the NAME section) of the form: - . - package - program to do something - . - Please double-check the manual page and replace the template language - with specific information about this program. diff -Nru lintian-2.93.0/tags/m/manual-page-in-udeb.desc lintian-2.89.0ubuntu1/tags/m/manual-page-in-udeb.desc --- lintian-2.93.0/tags/m/manual-page-in-udeb.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/manual-page-in-udeb.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,5 @@ +Tag: manual-page-in-udeb +Severity: error +Check: documentation/manual +Renamed-From: manpage-in-udeb +Info: udeb packages should not contain any manual pages. diff -Nru lintian-2.93.0/tags/m/manual-page-in-udeb.tag lintian-2.89.0ubuntu1/tags/m/manual-page-in-udeb.tag --- lintian-2.93.0/tags/m/manual-page-in-udeb.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/manual-page-in-udeb.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,5 +0,0 @@ -Tag: manual-page-in-udeb -Severity: error -Check: documentation/manual -Renamed-From: manpage-in-udeb -Explanation: udeb packages should not contain any manual pages. diff -Nru lintian-2.93.0/tags/m/manual-page-with-generic-name.desc lintian-2.89.0ubuntu1/tags/m/manual-page-with-generic-name.desc --- lintian-2.93.0/tags/m/manual-page-with-generic-name.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/manual-page-with-generic-name.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: manual-page-with-generic-name +Severity: error +Check: documentation/manual +Renamed-From: manpage-has-overly-generic-name +Info: The manual page appears to have an overly generic name that is likely to + clash with other packages. + . + Please check your debian/rules or upstream Makefile. diff -Nru lintian-2.93.0/tags/m/manual-page-with-generic-name.tag lintian-2.89.0ubuntu1/tags/m/manual-page-with-generic-name.tag --- lintian-2.93.0/tags/m/manual-page-with-generic-name.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/manual-page-with-generic-name.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: manual-page-with-generic-name -Severity: error -Check: documentation/manual -Renamed-From: manpage-has-overly-generic-name -Explanation: The manual page appears to have an overly generic name that is likely to - clash with other packages. - . - Please check your debian/rules or upstream Makefile. diff -Nru lintian-2.93.0/tags/m/maven-plugin-in-usr-share-java.desc lintian-2.89.0ubuntu1/tags/m/maven-plugin-in-usr-share-java.desc --- lintian-2.93.0/tags/m/maven-plugin-in-usr-share-java.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/maven-plugin-in-usr-share-java.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: maven-plugin-in-usr-share-java +Severity: warning +Certainty: possible +Check: languages/java +Info: A maven plugin is incorrectly installed in /usr/share/java. + Maven plugins should be installed in /usr/share/maven-repo diff -Nru lintian-2.93.0/tags/m/maven-plugin-in-usr-share-java.tag lintian-2.89.0ubuntu1/tags/m/maven-plugin-in-usr-share-java.tag --- lintian-2.93.0/tags/m/maven-plugin-in-usr-share-java.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/maven-plugin-in-usr-share-java.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,5 +0,0 @@ -Tag: maven-plugin-in-usr-share-java -Severity: warning -Check: languages/java -Explanation: A maven plugin is incorrectly installed in /usr/share/java. - Maven plugins should be installed in /usr/share/maven-repo diff -Nru lintian-2.93.0/tags/m/mawk-script-but-no-mawk-dep.desc lintian-2.89.0ubuntu1/tags/m/mawk-script-but-no-mawk-dep.desc --- lintian-2.93.0/tags/m/mawk-script-but-no-mawk-dep.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/mawk-script-but-no-mawk-dep.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: mawk-script-but-no-mawk-dep +Severity: error +Check: scripts +Info: Packages that use mawk scripts must depend on the mawk package. + If they don't need mawk-specific features, and can just as easily work + with gawk, then they should be awk scripts instead. + . + In some cases a weaker relationship, such as Suggests or Recommends, will + be more appropriate. diff -Nru lintian-2.93.0/tags/m/mawk-script-but-no-mawk-dep.tag lintian-2.89.0ubuntu1/tags/m/mawk-script-but-no-mawk-dep.tag --- lintian-2.93.0/tags/m/mawk-script-but-no-mawk-dep.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/mawk-script-but-no-mawk-dep.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: mawk-script-but-no-mawk-dep -Severity: error -Check: scripts -Explanation: Packages that use mawk scripts must depend on the mawk package. - If they don't need mawk-specific features, and can just as easily work - with gawk, then they should be awk scripts instead. - . - In some cases a weaker relationship, such as Suggests or Recommends, will - be more appropriate. diff -Nru lintian-2.93.0/tags/m/maybe-not-arch-all-binnmuable.desc lintian-2.89.0ubuntu1/tags/m/maybe-not-arch-all-binnmuable.desc --- lintian-2.93.0/tags/m/maybe-not-arch-all-binnmuable.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/maybe-not-arch-all-binnmuable.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,11 @@ +Tag: maybe-not-arch-all-binnmuable +Severity: pedantic +Certainty: wild-guess +Check: debian/version-substvars +Experimental: yes +Info: Tag to attempt to measure the number of packages that might + have an issue with arch:all binNMUs. + . + At this time, please do not attempt to "fix" the problem. It + is not clear what the solution is (if any at all), nor is it clear + that this is something that will or should be supported. diff -Nru lintian-2.93.0/tags/m/maybe-not-arch-all-binnmuable.tag lintian-2.89.0ubuntu1/tags/m/maybe-not-arch-all-binnmuable.tag --- lintian-2.93.0/tags/m/maybe-not-arch-all-binnmuable.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/maybe-not-arch-all-binnmuable.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,10 +0,0 @@ -Tag: maybe-not-arch-all-binnmuable -Severity: pedantic -Check: debian/version-substvars -Experimental: yes -Explanation: Tag to attempt to measure the number of packages that might - have an issue with arch:all binNMUs. - . - At this time, please do *not* attempt to "fix" the problem. It - is not clear what the solution is (if any at all), nor is it clear - that this is something that will or should be supported. diff -Nru lintian-2.93.0/tags/m/md5sum-mismatch.desc lintian-2.89.0ubuntu1/tags/m/md5sum-mismatch.desc --- lintian-2.93.0/tags/m/md5sum-mismatch.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/md5sum-mismatch.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,12 @@ +Tag: md5sum-mismatch +Severity: error +Check: md5sums +Info: The md5sum listed for the file does not match the actual file + contents. + . + Usually, this error occurs during the package build process if the + debian/tmp/ directory is touched after dh_md5sums + is run. + . + Font files regenerated at post-install time by t1c2pfb + should be overridden. diff -Nru lintian-2.93.0/tags/m/md5sum-mismatch.tag lintian-2.89.0ubuntu1/tags/m/md5sum-mismatch.tag --- lintian-2.93.0/tags/m/md5sum-mismatch.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/md5sum-mismatch.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,12 +0,0 @@ -Tag: md5sum-mismatch -Severity: error -Check: md5sums -Explanation: The md5sum listed for the file does not match the actual file - contents. - . - Usually, this error occurs during the package build process if the - debian/tmp/ directory is touched after dh_md5sums - is run. - . - Font files regenerated at post-install time by t1c2pfb - should be overridden. diff -Nru lintian-2.93.0/tags/m/md5sums-lists-nonexistent-file.desc lintian-2.89.0ubuntu1/tags/m/md5sums-lists-nonexistent-file.desc --- lintian-2.93.0/tags/m/md5sums-lists-nonexistent-file.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/md5sums-lists-nonexistent-file.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: md5sums-lists-nonexistent-file +Severity: error +Check: md5sums +Info: The md5sums control file lists a file which is not included in the + package. + . + Usually, this error occurs during the package build process if the + debian/tmp/ directory is touched after dh_md5sums + is run. diff -Nru lintian-2.93.0/tags/m/md5sums-lists-nonexistent-file.tag lintian-2.89.0ubuntu1/tags/m/md5sums-lists-nonexistent-file.tag --- lintian-2.93.0/tags/m/md5sums-lists-nonexistent-file.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/md5sums-lists-nonexistent-file.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: md5sums-lists-nonexistent-file -Severity: error -Check: md5sums -Explanation: The md5sums control file lists a file which is not included in the - package. - . - Usually, this error occurs during the package build process if the - debian/tmp/ directory is touched after dh_md5sums - is run. diff -Nru lintian-2.93.0/tags/m/mentions-deprecated-usr-lib-perl5-directory.desc lintian-2.89.0ubuntu1/tags/m/mentions-deprecated-usr-lib-perl5-directory.desc --- lintian-2.93.0/tags/m/mentions-deprecated-usr-lib-perl5-directory.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/mentions-deprecated-usr-lib-perl5-directory.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,11 @@ +# Imported from pkg-perl-tools (named usr-lib-perl5-mentioned there) +Tag: mentions-deprecated-usr-lib-perl5-directory +Severity: error +Certainty: possible +Check: cruft +Experimental: yes +Info: As of Perl 5.20, the vendorarch directory is /usr/lib/<triplet>/perl5, + but this package still uses usr/lib/perl5 in some of the files under debian/. + Please replace that with the value of $Config{vendorarch} configuration + parameter, e.g. + $(shell perl -MConfig -wE'say substr($$Config{vendorarch},1)') diff -Nru lintian-2.93.0/tags/m/mentions-deprecated-usr-lib-perl5-directory.tag lintian-2.89.0ubuntu1/tags/m/mentions-deprecated-usr-lib-perl5-directory.tag --- lintian-2.93.0/tags/m/mentions-deprecated-usr-lib-perl5-directory.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/mentions-deprecated-usr-lib-perl5-directory.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,10 +0,0 @@ -# Imported from pkg-perl-tools (named usr-lib-perl5-mentioned there) -Tag: mentions-deprecated-usr-lib-perl5-directory -Severity: error -Check: cruft -Experimental: yes -Explanation: As of Perl 5.20, the vendorarch directory is /usr/lib/<triplet>/perl5, - but this package still uses usr/lib/perl5 in some of the files under debian/. - Please replace that with the value of $Config{vendorarch} configuration - parameter, e.g. - $(shell perl -MConfig -wE'say substr($$Config{vendorarch},1)') diff -Nru lintian-2.93.0/tags/m/menu-command-not-in-package.desc lintian-2.89.0ubuntu1/tags/m/menu-command-not-in-package.desc --- lintian-2.93.0/tags/m/menu-command-not-in-package.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/menu-command-not-in-package.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: menu-command-not-in-package +Severity: warning +Certainty: possible +Check: menu-format +Info: The menu item specifies a command which is not available in the package. + In most cases this is a typo or after you moved a binary around, but forgot + to update the menu file. diff -Nru lintian-2.93.0/tags/m/menu-command-not-in-package.tag lintian-2.89.0ubuntu1/tags/m/menu-command-not-in-package.tag --- lintian-2.93.0/tags/m/menu-command-not-in-package.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/menu-command-not-in-package.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: menu-command-not-in-package -Severity: warning -Check: menu-format -Explanation: The menu item specifies a command which is not available in the package. - In most cases this is a typo or after you moved a binary around, but forgot - to update the menu file. diff -Nru lintian-2.93.0/tags/m/menu-file-in-usr-lib.desc lintian-2.89.0ubuntu1/tags/m/menu-file-in-usr-lib.desc --- lintian-2.93.0/tags/m/menu-file-in-usr-lib.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/menu-file-in-usr-lib.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: menu-file-in-usr-lib +Severity: warning +Check: menus +Info: As of menu, version 2.1.25, /usr/lib/menu as location for menu + files is deprecated (but still works perfectly). Menu files should + now be placed in /usr/share/menu instead. Only menu files that are + actually binary executables still need to go to /usr/lib/menu. +Ref: menu 3.1 diff -Nru lintian-2.93.0/tags/m/menu-file-in-usr-lib.tag lintian-2.89.0ubuntu1/tags/m/menu-file-in-usr-lib.tag --- lintian-2.93.0/tags/m/menu-file-in-usr-lib.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/menu-file-in-usr-lib.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: menu-file-in-usr-lib -Severity: warning -Check: menus -Explanation: As of menu, version 2.1.25, /usr/lib/menu as location for menu - files is deprecated (but still works perfectly). Menu files should - now be placed in /usr/share/menu instead. Only menu files that are - actually binary executables still need to go to /usr/lib/menu. -See-Also: menu 3.1 diff -Nru lintian-2.93.0/tags/m/menu-icon-cannot-be-parsed.desc lintian-2.89.0ubuntu1/tags/m/menu-icon-cannot-be-parsed.desc --- lintian-2.93.0/tags/m/menu-icon-cannot-be-parsed.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/menu-icon-cannot-be-parsed.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: menu-icon-cannot-be-parsed +Severity: warning +Check: menu-format +Info: The icon file could not be parsed. Perhaps this means a bad XPM file, + or perhaps it means the Lintian parsing needs to be improved. If the + window managers and standard tools accept the file then probably it's the + latter; please file a bug on Lintian then. diff -Nru lintian-2.93.0/tags/m/menu-icon-cannot-be-parsed.tag lintian-2.89.0ubuntu1/tags/m/menu-icon-cannot-be-parsed.tag --- lintian-2.93.0/tags/m/menu-icon-cannot-be-parsed.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/menu-icon-cannot-be-parsed.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: menu-icon-cannot-be-parsed -Severity: warning -Check: menu-format -Explanation: The icon file could not be parsed. Perhaps this means a bad XPM file, - or perhaps it means the Lintian parsing needs to be improved. If the - window managers and standard tools accept the file then probably it's the - latter; please file a bug on Lintian then. diff -Nru lintian-2.93.0/tags/m/menu-icon-missing.desc lintian-2.89.0ubuntu1/tags/m/menu-icon-missing.desc --- lintian-2.93.0/tags/m/menu-icon-missing.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/menu-icon-missing.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,15 @@ +Tag: menu-icon-missing +Severity: warning +Certainty: possible +Check: menu-format +Info: This icon file couldn't be found. If the path to the icon in the + menu file is an absolute path, make sure that icon exists at that path in + the package. If the path is relative or a simple filename, make sure the + icon is installed in /usr/share/pixmaps, the default location. + . + If the icon is provided by another package on which this package + depends, Lintian may not be able to determine that icon pages are + available. In this case, after confirming that all icons are + available after this package and its dependencies are installed, + please add a Lintian override. +Ref: menu 3.7 diff -Nru lintian-2.93.0/tags/m/menu-icon-missing.tag lintian-2.89.0ubuntu1/tags/m/menu-icon-missing.tag --- lintian-2.93.0/tags/m/menu-icon-missing.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/menu-icon-missing.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,14 +0,0 @@ -Tag: menu-icon-missing -Severity: warning -Check: menu-format -Explanation: This icon file couldn't be found. If the path to the icon in the - menu file is an absolute path, make sure that icon exists at that path in - the package. If the path is relative or a simple filename, make sure the - icon is installed in /usr/share/pixmaps, the default location. - . - If the icon is provided by another package on which this package - depends, Lintian may not be able to determine that icon pages are - available. In this case, after confirming that all icons are - available after this package and its dependencies are installed, - please add a Lintian override. -See-Also: menu 3.7 diff -Nru lintian-2.93.0/tags/m/menu-icon-not-in-xpm-format.desc lintian-2.89.0ubuntu1/tags/m/menu-icon-not-in-xpm-format.desc --- lintian-2.93.0/tags/m/menu-icon-not-in-xpm-format.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/menu-icon-not-in-xpm-format.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: menu-icon-not-in-xpm-format +Severity: error +Check: menu-format +Info: Icons in the Debian menu system should be in XPM format. + . + While other image types (e.g. png images) appears to "just work", + window managers are not "required to support them". Accordingly + using non-XPM icons could break interoperability. +Ref: menu 3.7, #591812 diff -Nru lintian-2.93.0/tags/m/menu-icon-not-in-xpm-format.tag lintian-2.89.0ubuntu1/tags/m/menu-icon-not-in-xpm-format.tag --- lintian-2.93.0/tags/m/menu-icon-not-in-xpm-format.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/menu-icon-not-in-xpm-format.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: menu-icon-not-in-xpm-format -Severity: error -Check: menu-format -Explanation: Icons in the Debian menu system should be in XPM format. - . - While other image types (e.g. png images) appears to "just work", - window managers are not "required to support them". Accordingly - using non-XPM icons could break interoperability. -See-Also: menu 3.7, Bug#591812 diff -Nru lintian-2.93.0/tags/m/menu-icon-too-big.desc lintian-2.89.0ubuntu1/tags/m/menu-icon-too-big.desc --- lintian-2.93.0/tags/m/menu-icon-too-big.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/menu-icon-too-big.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: menu-icon-too-big +Severity: error +Check: menu-format +Info: Icons in the Debian menu system should be at most 32x32 pixels + (icon16x16 icons should of course be at most 16x16 pixels) +Ref: menu 3.7 diff -Nru lintian-2.93.0/tags/m/menu-icon-too-big.tag lintian-2.89.0ubuntu1/tags/m/menu-icon-too-big.tag --- lintian-2.93.0/tags/m/menu-icon-too-big.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/menu-icon-too-big.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: menu-icon-too-big -Severity: error -Check: menu-format -Explanation: Icons in the Debian menu system should be at most 32x32 pixels - (icon16x16 icons should of course be at most 16x16 pixels) -See-Also: menu 3.7 diff -Nru lintian-2.93.0/tags/m/menu-icon-uses-relative-path.desc lintian-2.89.0ubuntu1/tags/m/menu-icon-uses-relative-path.desc --- lintian-2.93.0/tags/m/menu-icon-uses-relative-path.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/menu-icon-uses-relative-path.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: menu-icon-uses-relative-path +Severity: warning +Check: menu-format +Info: This package contains a menu file which references an icon by a relative + path. However, icons should be referenced by an absolute path in menu files. +Ref: menu 3.2, #693477 diff -Nru lintian-2.93.0/tags/m/menu-icon-uses-relative-path.tag lintian-2.89.0ubuntu1/tags/m/menu-icon-uses-relative-path.tag --- lintian-2.93.0/tags/m/menu-icon-uses-relative-path.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/menu-icon-uses-relative-path.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: menu-icon-uses-relative-path -Severity: warning -Check: menu-format -Explanation: This package contains a menu file which references an icon by a relative - path. However, icons should be referenced by an absolute path in menu files. -See-Also: menu 3.2, Bug#693477 diff -Nru lintian-2.93.0/tags/m/menu-item-contains-unknown-tag.desc lintian-2.89.0ubuntu1/tags/m/menu-item-contains-unknown-tag.desc --- lintian-2.93.0/tags/m/menu-item-contains-unknown-tag.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/menu-item-contains-unknown-tag.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: menu-item-contains-unknown-tag +Severity: warning +Check: menu-format +Info: The menu item has a line that has a tag in it that is not one + of the standard tags (needs=, section=, title=, longtitle=, command=, etc). + While other tags can be used for specialized purposes, this is rare and + it's more likely the tag's name is misspelled. diff -Nru lintian-2.93.0/tags/m/menu-item-contains-unknown-tag.tag lintian-2.89.0ubuntu1/tags/m/menu-item-contains-unknown-tag.tag --- lintian-2.93.0/tags/m/menu-item-contains-unknown-tag.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/menu-item-contains-unknown-tag.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: menu-item-contains-unknown-tag -Severity: warning -Check: menu-format -Explanation: The menu item has a line that has a tag in it that is not one - of the standard tags (needs=, section=, title=, longtitle=, command=, etc). - While other tags can be used for specialized purposes, this is rare and - it's more likely the tag's name is misspelled. diff -Nru lintian-2.93.0/tags/m/menu-item-creates-new-root-section.desc lintian-2.89.0ubuntu1/tags/m/menu-item-creates-new-root-section.desc --- lintian-2.93.0/tags/m/menu-item-creates-new-root-section.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/menu-item-creates-new-root-section.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: menu-item-creates-new-root-section +Severity: error +Check: menu-format +Info: The menu item has a line that specifies a new section to put a menu + entry in, and this section appears right in the root menu. This is + almost certainly an error. No new sections should be added to the root + menu without discussion with the author of menu. diff -Nru lintian-2.93.0/tags/m/menu-item-creates-new-root-section.tag lintian-2.89.0ubuntu1/tags/m/menu-item-creates-new-root-section.tag --- lintian-2.93.0/tags/m/menu-item-creates-new-root-section.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/menu-item-creates-new-root-section.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: menu-item-creates-new-root-section -Severity: error -Check: menu-format -Explanation: The menu item has a line that specifies a new section to put a menu - entry in, and this section appears right in the root menu. This is - almost certainly an error. No new sections should be added to the root - menu without discussion with the author of menu. diff -Nru lintian-2.93.0/tags/m/menu-item-creates-new-section.desc lintian-2.89.0ubuntu1/tags/m/menu-item-creates-new-section.desc --- lintian-2.93.0/tags/m/menu-item-creates-new-section.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/menu-item-creates-new-section.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: menu-item-creates-new-section +Severity: warning +Check: menu-format +Info: The menu item has a line that specifies an unknown section or uses a + section that is intended only as a menu root, not as a section that + applications should use directly. Check the spelling of the section and + check the section against the list in the menu policy. (The menu + sections changed as of June of 2007.) +Ref: menu-policy 2.1 diff -Nru lintian-2.93.0/tags/m/menu-item-creates-new-section.tag lintian-2.89.0ubuntu1/tags/m/menu-item-creates-new-section.tag --- lintian-2.93.0/tags/m/menu-item-creates-new-section.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/menu-item-creates-new-section.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: menu-item-creates-new-section -Severity: warning -Check: menu-format -Explanation: The menu item has a line that specifies an unknown section or uses a - section that is intended only as a menu root, not as a section that - applications should use directly. Check the spelling of the section and - check the section against the list in the menu policy. (The menu - sections changed as of June of 2007.) -See-Also: menu-policy 2.1 diff -Nru lintian-2.93.0/tags/m/menu-item-missing-required-tag.desc lintian-2.89.0ubuntu1/tags/m/menu-item-missing-required-tag.desc --- lintian-2.93.0/tags/m/menu-item-missing-required-tag.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/menu-item-missing-required-tag.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: menu-item-missing-required-tag +Severity: error +Check: menu-format +Info: The menu item has a line that is missing a required tag. It's likely + that the line will have no effect without this tag. install-menu may + report this as an error during package installation. diff -Nru lintian-2.93.0/tags/m/menu-item-missing-required-tag.tag lintian-2.89.0ubuntu1/tags/m/menu-item-missing-required-tag.tag --- lintian-2.93.0/tags/m/menu-item-missing-required-tag.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/menu-item-missing-required-tag.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: menu-item-missing-required-tag -Severity: error -Check: menu-format -Explanation: The menu item has a line that is missing a required tag. It's likely - that the line will have no effect without this tag. install-menu may - report this as an error during package installation. diff -Nru lintian-2.93.0/tags/m/menu-item-needs-dwww.desc lintian-2.89.0ubuntu1/tags/m/menu-item-needs-dwww.desc --- lintian-2.93.0/tags/m/menu-item-needs-dwww.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/menu-item-needs-dwww.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: menu-item-needs-dwww +Severity: warning +Check: menu-format +Info: The menu item has needs=dwww. This is deprecated. Instead, you should + register your documentation with doc-base, and dwww entries will be + automatically generated. diff -Nru lintian-2.93.0/tags/m/menu-item-needs-dwww.tag lintian-2.89.0ubuntu1/tags/m/menu-item-needs-dwww.tag --- lintian-2.93.0/tags/m/menu-item-needs-dwww.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/menu-item-needs-dwww.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: menu-item-needs-dwww -Severity: warning -Check: menu-format -Explanation: The menu item has needs=dwww. This is deprecated. Instead, you should - register your documentation with doc-base, and dwww entries will be - automatically generated. diff -Nru lintian-2.93.0/tags/m/menu-item-needs-tag-has-unknown-value.desc lintian-2.89.0ubuntu1/tags/m/menu-item-needs-tag-has-unknown-value.desc --- lintian-2.93.0/tags/m/menu-item-needs-tag-has-unknown-value.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/menu-item-needs-tag-has-unknown-value.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: menu-item-needs-tag-has-unknown-value +Severity: warning +Check: menu-format +Info: The menu item has a line that has a needs= field with a strange value. + This may be intentional, but it's probably a typo that will make menu + ignore the line. diff -Nru lintian-2.93.0/tags/m/menu-item-needs-tag-has-unknown-value.tag lintian-2.89.0ubuntu1/tags/m/menu-item-needs-tag-has-unknown-value.tag --- lintian-2.93.0/tags/m/menu-item-needs-tag-has-unknown-value.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/menu-item-needs-tag-has-unknown-value.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: menu-item-needs-tag-has-unknown-value -Severity: warning -Check: menu-format -Explanation: The menu item has a line that has a needs= field with a strange value. - This may be intentional, but it's probably a typo that will make menu - ignore the line. diff -Nru lintian-2.93.0/tags/m/menu-item-uses-apps-games-section.desc lintian-2.89.0ubuntu1/tags/m/menu-item-uses-apps-games-section.desc --- lintian-2.93.0/tags/m/menu-item-uses-apps-games-section.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/menu-item-uses-apps-games-section.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: menu-item-uses-apps-games-section +Severity: warning +Check: menu-format +Info: The menu item has a line that specifies a section under "Apps/Games". + This section has been moved to just "Games". +Ref: menu-policy 2.1 diff -Nru lintian-2.93.0/tags/m/menu-item-uses-apps-games-section.tag lintian-2.89.0ubuntu1/tags/m/menu-item-uses-apps-games-section.tag --- lintian-2.93.0/tags/m/menu-item-uses-apps-games-section.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/menu-item-uses-apps-games-section.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: menu-item-uses-apps-games-section -Severity: warning -Check: menu-format -Explanation: The menu item has a line that specifies a section under "Apps/Games". - This section has been moved to just "Games". -See-Also: menu-policy 2.1 diff -Nru lintian-2.93.0/tags/m/menu-item-uses-apps-section.desc lintian-2.89.0ubuntu1/tags/m/menu-item-uses-apps-section.desc --- lintian-2.93.0/tags/m/menu-item-uses-apps-section.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/menu-item-uses-apps-section.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: menu-item-uses-apps-section +Severity: warning +Check: menu-format +Info: The menu item has a line that specifies a section under "Apps". + This section has been moved to "Applications". +Ref: menu-policy 2.1 diff -Nru lintian-2.93.0/tags/m/menu-item-uses-apps-section.tag lintian-2.89.0ubuntu1/tags/m/menu-item-uses-apps-section.tag --- lintian-2.93.0/tags/m/menu-item-uses-apps-section.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/menu-item-uses-apps-section.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: menu-item-uses-apps-section -Severity: warning -Check: menu-format -Explanation: The menu item has a line that specifies a section under "Apps". - This section has been moved to "Applications". -See-Also: menu-policy 2.1 diff -Nru lintian-2.93.0/tags/m/menu-item-uses-icon-none.desc lintian-2.89.0ubuntu1/tags/m/menu-item-uses-icon-none.desc --- lintian-2.93.0/tags/m/menu-item-uses-icon-none.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/menu-item-uses-icon-none.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,5 @@ +Tag: menu-item-uses-icon-none +Severity: warning +Check: menu-format +Info: The menu item has a line that uses icon=none. This is redundant and + deprecated -- if there is no icon, just leave off the icon tag. diff -Nru lintian-2.93.0/tags/m/menu-item-uses-icon-none.tag lintian-2.89.0ubuntu1/tags/m/menu-item-uses-icon-none.tag --- lintian-2.93.0/tags/m/menu-item-uses-icon-none.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/menu-item-uses-icon-none.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,5 +0,0 @@ -Tag: menu-item-uses-icon-none -Severity: warning -Check: menu-format -Explanation: The menu item has a line that uses icon=none. This is redundant and - deprecated -- if there is no icon, just leave off the icon tag. diff -Nru lintian-2.93.0/tags/m/menu-item-uses-windowmanagers-section.desc lintian-2.89.0ubuntu1/tags/m/menu-item-uses-windowmanagers-section.desc --- lintian-2.93.0/tags/m/menu-item-uses-windowmanagers-section.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/menu-item-uses-windowmanagers-section.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: menu-item-uses-windowmanagers-section +Severity: warning +Check: menu-format +Info: The menu item has a line that specifies a section under + "WindowManagers". This section has been moved to "Window Managers". +Ref: menu-policy 2.1 diff -Nru lintian-2.93.0/tags/m/menu-item-uses-windowmanagers-section.tag lintian-2.89.0ubuntu1/tags/m/menu-item-uses-windowmanagers-section.tag --- lintian-2.93.0/tags/m/menu-item-uses-windowmanagers-section.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/menu-item-uses-windowmanagers-section.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: menu-item-uses-windowmanagers-section -Severity: warning -Check: menu-format -Explanation: The menu item has a line that specifies a section under - "WindowManagers". This section has been moved to "Window Managers". -See-Also: menu-policy 2.1 diff -Nru lintian-2.93.0/tags/m/menu-method-lacks-include.desc lintian-2.89.0ubuntu1/tags/m/menu-method-lacks-include.desc --- lintian-2.93.0/tags/m/menu-method-lacks-include.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/menu-method-lacks-include.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: menu-method-lacks-include +Severity: error +Check: menus +Renamed-From: menu-method-should-include-menu-h +Info: A menu-method file must include the menu.h configuration file + (using "!include menu.h"). +Ref: menu 5, http://www.tldp.org/HOWTO/NCURSES-Programming-HOWTO/menus.html diff -Nru lintian-2.93.0/tags/m/menu-method-lacks-include.tag lintian-2.89.0ubuntu1/tags/m/menu-method-lacks-include.tag --- lintian-2.93.0/tags/m/menu-method-lacks-include.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/menu-method-lacks-include.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: menu-method-lacks-include -Severity: error -Check: menus -Renamed-From: menu-method-should-include-menu-h -Explanation: A menu-method file must include the menu.h configuration file - (using "!include menu.h"). -See-Also: menu 5, http://www.tldp.org/HOWTO/NCURSES-Programming-HOWTO/menus.html diff -Nru lintian-2.93.0/tags/m/mismatched-override.desc lintian-2.89.0ubuntu1/tags/m/mismatched-override.desc --- lintian-2.93.0/tags/m/mismatched-override.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/mismatched-override.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,14 @@ +Tag: mismatched-override +Severity: warning +Check: lintian +Info: The named tag could have been silenced but the context specified + with the override did not match. + . + Lintian may now provide a different context for the tag, or something + could have changed in a new version of your package. Either way, + overrides work best when you require only little context. + . + You can use wildcards, such as * or ? in the context to + makes a match more likely. + . + Please remove or adjust the override, whichever suits your purpose. diff -Nru lintian-2.93.0/tags/m/mismatched-override.tag lintian-2.89.0ubuntu1/tags/m/mismatched-override.tag --- lintian-2.93.0/tags/m/mismatched-override.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/mismatched-override.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,14 +0,0 @@ -Tag: mismatched-override -Severity: warning -Check: lintian -Explanation: The named tag could have been silenced but the context specified - with the override did not match. - . - Lintian may now provide a different context for the tag, or something - could have changed in a new version of your package. Either way, - overrides work best when you require only little context. - . - You can use wildcards, such as * or ? in the context to - makes a match more likely. - . - Please remove or adjust the override, whichever suits your purpose. diff -Nru lintian-2.93.0/tags/m/mismatched-python-substvar.desc lintian-2.89.0ubuntu1/tags/m/mismatched-python-substvar.desc --- lintian-2.93.0/tags/m/mismatched-python-substvar.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/mismatched-python-substvar.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: mismatched-python-substvar +Severity: warning +Check: languages/python +Info: The specified package declares a dependency on ${python:Depends} + whilst appearing to be a Python 3.x package or a dependency on + ${python3:Depends} when it appears to be a package for Python 2.x. + . + Please adjust the substvar to match the intended Python version. diff -Nru lintian-2.93.0/tags/m/mismatched-python-substvar.tag lintian-2.89.0ubuntu1/tags/m/mismatched-python-substvar.tag --- lintian-2.93.0/tags/m/mismatched-python-substvar.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/mismatched-python-substvar.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: mismatched-python-substvar -Severity: warning -Check: languages/python -Explanation: The specified package declares a dependency on ${python:Depends} - whilst appearing to be a Python 3.x package or a dependency on - ${python3:Depends} when it appears to be a package for Python 2.x. - . - Please adjust the substvar to match the intended Python version. diff -Nru lintian-2.93.0/tags/m/mismatch-translated-choices.desc lintian-2.89.0ubuntu1/tags/m/mismatch-translated-choices.desc --- lintian-2.93.0/tags/m/mismatch-translated-choices.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/mismatch-translated-choices.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,12 @@ +Tag: mismatch-translated-choices +Severity: error +Check: debian/debconf +Info: A "Choices:" field is a comma separated list, and translated + "Choices:" fields must have the exact same number of elements. One + of the translations does not follow this rule, you should contact the + translator and request for a new translation where elements of "Choices:" + fields have no embedded commas. + . + Cdebconf understands escaped commas in such fields, but packages + outside the scope of debian-installer must not have them until they are + also supported by debconf. diff -Nru lintian-2.93.0/tags/m/mismatch-translated-choices.tag lintian-2.89.0ubuntu1/tags/m/mismatch-translated-choices.tag --- lintian-2.93.0/tags/m/mismatch-translated-choices.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/mismatch-translated-choices.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,12 +0,0 @@ -Tag: mismatch-translated-choices -Severity: error -Check: debian/debconf -Explanation: A "Choices:" field is a comma separated list, and translated - "Choices:" fields must have the exact same number of elements. One - of the translations does not follow this rule, you should contact the - translator and request for a new translation where elements of "Choices:" - fields have no embedded commas. - . - Cdebconf understands escaped commas in such fields, but packages - outside the scope of debian-installer must not have them until they are - also supported by debconf. diff -Nru lintian-2.93.0/tags/m/misnamed-po-file.desc lintian-2.89.0ubuntu1/tags/m/misnamed-po-file.desc --- lintian-2.93.0/tags/m/misnamed-po-file.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/misnamed-po-file.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,14 @@ +Tag: misnamed-po-file +Severity: warning +Certainty: possible +Check: debian/po-debconf +Info: The name of this PO file doesn't appear to be a valid language + code. Any files in debian/po ending in .po will be + processed as translations by po2debconf for the language code equal to + the file name without the trailing .po. If the file name does + not correctly reflect the language of the translation, the translation + will not be accessible to users of that language. + . + If this file isn't actually a PO file, rename it to something that + doesn't end in .po or move it to another directory so that + translation merging programs will not be confused. diff -Nru lintian-2.93.0/tags/m/misnamed-po-file.tag lintian-2.89.0ubuntu1/tags/m/misnamed-po-file.tag --- lintian-2.93.0/tags/m/misnamed-po-file.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/misnamed-po-file.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,13 +0,0 @@ -Tag: misnamed-po-file -Severity: warning -Check: debian/po-debconf -Explanation: The name of this PO file doesn't appear to be a valid language - code. Any files in debian/po ending in .po will be - processed as translations by po2debconf for the language code equal to - the file name without the trailing .po. If the file name does - not correctly reflect the language of the translation, the translation - will not be accessible to users of that language. - . - If this file isn't actually a PO file, rename it to something that - doesn't end in .po or move it to another directory so that - translation merging programs will not be confused. diff -Nru lintian-2.93.0/tags/m/misplaced-extra-member-in-deb.desc lintian-2.89.0ubuntu1/tags/m/misplaced-extra-member-in-deb.desc --- lintian-2.93.0/tags/m/misplaced-extra-member-in-deb.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/misplaced-extra-member-in-deb.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: misplaced-extra-member-in-deb +Severity: error +Check: deb-format +Info: The binary package contains an extra member that Lintian did not + expect or expected at a different position. +Ref: deb(5) diff -Nru lintian-2.93.0/tags/m/misplaced-extra-member-in-deb.tag lintian-2.89.0ubuntu1/tags/m/misplaced-extra-member-in-deb.tag --- lintian-2.93.0/tags/m/misplaced-extra-member-in-deb.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/misplaced-extra-member-in-deb.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: misplaced-extra-member-in-deb -Severity: error -Check: deb-format -Explanation: The binary package contains an extra member that Lintian did not - expect or expected at a different position. -See-Also: deb(5) diff -Nru lintian-2.93.0/tags/m/missing-build-dependency.desc lintian-2.89.0ubuntu1/tags/m/missing-build-dependency.desc --- lintian-2.93.0/tags/m/missing-build-dependency.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/missing-build-dependency.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,16 @@ +Tag: missing-build-dependency +Severity: error +Certainty: possible +Check: debian/rules +Ref: policy 4.2 +Info: The package doesn't specify a build dependency on a package that is + used in debian/rules. + . + Lintian intentionally does not take into account transitive dependencies. + Even if the package build-depends on some package that in turn + depends on the needed package, an explicit build dependency should + be added. Otherwise, a latent bug is created that will appear without + warning if the other package is ever updated to change its dependencies. + Even if this seems unlikely, please always add explicit build + dependencies on every non-essential, non-build-essential package that is + used directly during the build. diff -Nru lintian-2.93.0/tags/m/missing-build-dependency-for-dh-addon.desc lintian-2.89.0ubuntu1/tags/m/missing-build-dependency-for-dh-addon.desc --- lintian-2.93.0/tags/m/missing-build-dependency-for-dh-addon.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/missing-build-dependency-for-dh-addon.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: missing-build-dependency-for-dh-addon +Severity: error +Certainty: possible +Check: debhelper +Info: The source package appears to be using a dh addon but doesn't build + depend on the package that actually provides it. If it uses it, it must + build depend on it. diff -Nru lintian-2.93.0/tags/m/missing-build-dependency-for-dh-addon.tag lintian-2.89.0ubuntu1/tags/m/missing-build-dependency-for-dh-addon.tag --- lintian-2.93.0/tags/m/missing-build-dependency-for-dh-addon.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/missing-build-dependency-for-dh-addon.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: missing-build-dependency-for-dh-addon -Severity: error -Check: debhelper -Explanation: The source package appears to be using a dh addon but doesn't build - depend on the package that actually provides it. If it uses it, it must - build depend on it. diff -Nru lintian-2.93.0/tags/m/missing-build-dependency-for-dh_-command.desc lintian-2.89.0ubuntu1/tags/m/missing-build-dependency-for-dh_-command.desc --- lintian-2.93.0/tags/m/missing-build-dependency-for-dh_-command.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/missing-build-dependency-for-dh_-command.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: missing-build-dependency-for-dh_-command +Severity: error +Certainty: possible +Check: debhelper +Info: The source package appears to be using a dh_ command but doesn't build + depend on the package that actually provides it. If it uses it, it must + build depend on it. diff -Nru lintian-2.93.0/tags/m/missing-build-dependency-for-dh_-command.tag lintian-2.89.0ubuntu1/tags/m/missing-build-dependency-for-dh_-command.tag --- lintian-2.93.0/tags/m/missing-build-dependency-for-dh_-command.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/missing-build-dependency-for-dh_-command.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: missing-build-dependency-for-dh_-command -Severity: error -Check: debhelper -Explanation: The source package appears to be using a dh_ command but doesn't build - depend on the package that actually provides it. If it uses it, it must - build depend on it. diff -Nru lintian-2.93.0/tags/m/missing-build-dependency.tag lintian-2.89.0ubuntu1/tags/m/missing-build-dependency.tag --- lintian-2.93.0/tags/m/missing-build-dependency.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/missing-build-dependency.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,15 +0,0 @@ -Tag: missing-build-dependency -Severity: error -Check: debian/rules -See-Also: policy 4.2 -Explanation: The package doesn't specify a build dependency on a package that is - used in debian/rules. - . - Lintian intentionally does not take into account transitive dependencies. - Even if the package build-depends on some package that in turn - depends on the needed package, an explicit build dependency should - be added. Otherwise, a latent bug is created that will appear without - warning if the other package is ever updated to change its dependencies. - Even if this seems unlikely, please always add explicit build - dependencies on every non-essential, non-build-essential package that is - used directly during the build. diff -Nru lintian-2.93.0/tags/m/missing-build-depends-for-clean-target-in-debian-rules.desc lintian-2.89.0ubuntu1/tags/m/missing-build-depends-for-clean-target-in-debian-rules.desc --- lintian-2.93.0/tags/m/missing-build-depends-for-clean-target-in-debian-rules.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/missing-build-depends-for-clean-target-in-debian-rules.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: missing-build-depends-for-clean-target-in-debian-rules +Severity: error +Check: debian/rules +Renamed-From: clean-should-be-satisfied-by-build-depends +Ref: policy 7.7 +Info: The specified package is required to run the clean target of + debian/rules and therefore must be listed in Build-Depends, not + Build-Depends-Indep, even if no architecture-dependent packages are + built. diff -Nru lintian-2.93.0/tags/m/missing-build-depends-for-clean-target-in-debian-rules.tag lintian-2.89.0ubuntu1/tags/m/missing-build-depends-for-clean-target-in-debian-rules.tag --- lintian-2.93.0/tags/m/missing-build-depends-for-clean-target-in-debian-rules.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/missing-build-depends-for-clean-target-in-debian-rules.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: missing-build-depends-for-clean-target-in-debian-rules -Severity: error -Check: debian/rules -Renamed-From: clean-should-be-satisfied-by-build-depends -See-Also: policy 7.7 -Explanation: The specified package is required to run the clean target of - debian/rules and therefore must be listed in Build-Depends, not - Build-Depends-Indep, even if no architecture-dependent packages are - built. diff -Nru lintian-2.93.0/tags/m/missing-built-using-field-for-golang-package.desc lintian-2.89.0ubuntu1/tags/m/missing-built-using-field-for-golang-package.desc --- lintian-2.93.0/tags/m/missing-built-using-field-for-golang-package.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/missing-built-using-field-for-golang-package.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,12 @@ +Tag: missing-built-using-field-for-golang-package +Severity: info +Check: debian/control +Info: This package builds a binary package which does not include + ${misc:Built-Using} in its Built-Using control field. + . + The ${misc:Built-Using} substvar is populated by + dh-golang(1) and used for scheduling binNMUs. + . + Please add the following line to your package definition: + . + Built-Using: ${misc:Built-Using} diff -Nru lintian-2.93.0/tags/m/missing-built-using-field-for-golang-package.tag lintian-2.89.0ubuntu1/tags/m/missing-built-using-field-for-golang-package.tag --- lintian-2.93.0/tags/m/missing-built-using-field-for-golang-package.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/missing-built-using-field-for-golang-package.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,12 +0,0 @@ -Tag: missing-built-using-field-for-golang-package -Severity: info -Check: debian/control -Explanation: This package builds a binary package which does not include - ${misc:Built-Using} in its Built-Using control field. - . - The ${misc:Built-Using} substvar is populated by - dh-golang(1) and used for scheduling binNMUs. - . - Please add the following line to your package definition: - . - Built-Using: ${misc:Built-Using} diff -Nru lintian-2.93.0/tags/m/missing-call-to-dpkg-maintscript-helper.desc lintian-2.89.0ubuntu1/tags/m/missing-call-to-dpkg-maintscript-helper.desc --- lintian-2.93.0/tags/m/missing-call-to-dpkg-maintscript-helper.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/missing-call-to-dpkg-maintscript-helper.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: missing-call-to-dpkg-maintscript-helper +Severity: error +Check: scripts +Info: The maintainer script is missing a call to the specified + dpkg-maintscript-helper command which requires coordinated actions from + several maintainer scripts. +Ref: dpkg-maintscript-helper(1) diff -Nru lintian-2.93.0/tags/m/missing-call-to-dpkg-maintscript-helper.tag lintian-2.89.0ubuntu1/tags/m/missing-call-to-dpkg-maintscript-helper.tag --- lintian-2.93.0/tags/m/missing-call-to-dpkg-maintscript-helper.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/missing-call-to-dpkg-maintscript-helper.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: missing-call-to-dpkg-maintscript-helper -Severity: error -Check: scripts -Explanation: The maintainer script is missing a call to the specified - dpkg-maintscript-helper command which requires coordinated actions from - several maintainer scripts. -See-Also: dpkg-maintscript-helper(1) diff -Nru lintian-2.93.0/tags/m/missing-call-to-update-fonts.desc lintian-2.89.0ubuntu1/tags/m/missing-call-to-update-fonts.desc --- lintian-2.93.0/tags/m/missing-call-to-update-fonts.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/missing-call-to-update-fonts.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,11 @@ +Tag: missing-call-to-update-fonts +Severity: warning +Certainty: possible +Check: scripts +Info: The maintainer script ships the specified X11 font but does not + appear to call update-fonts-scale or update-fonts-dir in its postinst + script. + . + If you are using dh_installxfonts, add a dependency on ${misc:Depends} + and dh_installxfonts will take care of this for you. +Ref: https://lists.debian.org/msgid-search/CAJqvfD-A1EPXxF_mS=_BaQ0FtqygVwRUf+23WqSqrkSmYgVAtA@mail.gmail.com diff -Nru lintian-2.93.0/tags/m/missing-call-to-update-fonts.tag lintian-2.89.0ubuntu1/tags/m/missing-call-to-update-fonts.tag --- lintian-2.93.0/tags/m/missing-call-to-update-fonts.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/missing-call-to-update-fonts.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,10 +0,0 @@ -Tag: missing-call-to-update-fonts -Severity: warning -Check: scripts -Explanation: The maintainer script ships the specified X11 font but does not - appear to call update-fonts-scale or update-fonts-dir in its postinst - script. - . - If you are using dh_installxfonts, add a dependency on ${misc:Depends} - and dh_installxfonts will take care of this for you. -See-Also: https://lists.debian.org/msgid-search/CAJqvfD-A1EPXxF_mS=_BaQ0FtqygVwRUf+23WqSqrkSmYgVAtA@mail.gmail.com diff -Nru lintian-2.93.0/tags/m/missing-debconf-dependency.desc lintian-2.89.0ubuntu1/tags/m/missing-debconf-dependency.desc --- lintian-2.93.0/tags/m/missing-debconf-dependency.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/missing-debconf-dependency.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: missing-debconf-dependency +Severity: warning +Certainty: possible +Check: debian/debconf +Info: Packages using debconf should depend on it, since debconf is not an + essential package. diff -Nru lintian-2.93.0/tags/m/missing-debconf-dependency-for-preinst.desc lintian-2.89.0ubuntu1/tags/m/missing-debconf-dependency-for-preinst.desc --- lintian-2.93.0/tags/m/missing-debconf-dependency-for-preinst.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/missing-debconf-dependency-for-preinst.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: missing-debconf-dependency-for-preinst +Severity: warning +Certainty: possible +Check: debian/debconf +Info: Packages using debconf in their preinst scripts must pre-depend + on debconf. + . + Since debconf is usually installed already, that is better than + depending on it but falling back to a different configuration system. diff -Nru lintian-2.93.0/tags/m/missing-debconf-dependency-for-preinst.tag lintian-2.89.0ubuntu1/tags/m/missing-debconf-dependency-for-preinst.tag --- lintian-2.93.0/tags/m/missing-debconf-dependency-for-preinst.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/missing-debconf-dependency-for-preinst.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: missing-debconf-dependency-for-preinst -Severity: warning -Check: debian/debconf -Explanation: Packages using debconf in their preinst scripts must pre-depend - on debconf. - . - Since debconf is usually installed already, that is better than - depending on it but falling back to a different configuration system. diff -Nru lintian-2.93.0/tags/m/missing-debconf-dependency.tag lintian-2.89.0ubuntu1/tags/m/missing-debconf-dependency.tag --- lintian-2.93.0/tags/m/missing-debconf-dependency.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/missing-debconf-dependency.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,5 +0,0 @@ -Tag: missing-debconf-dependency -Severity: warning -Check: debian/debconf -Explanation: Packages using debconf should depend on it, since debconf is not an - essential package. diff -Nru lintian-2.93.0/tags/m/missing-debian-source-format.desc lintian-2.89.0ubuntu1/tags/m/missing-debian-source-format.desc --- lintian-2.93.0/tags/m/missing-debian-source-format.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/missing-debian-source-format.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,19 @@ +Tag: missing-debian-source-format +Severity: warning +Check: debian/source-dir +Info: Explicitly selecting a source format by putting the format in + debian/source/format is recommended. This allows for + future removal of the 1.0 default for the package source format and, + depending on the source format, may allow unambiguous declaration of + whether this package is native or non-native. + . + If you don't have a reason to stay with the old format for this package, + please consider switching to "3.0 (quilt)" (for packages with a separate + upstream tarball) or to "3.0 (native)" (for Debian native packages). + . + If you wish to keep using the old format, please create that file and put + "1.0" in it to be explicit about the source package version. If you have + problems with the 3.0 format, the dpkg maintainers are interested in + hearing, at debian-dpkg@lists.debian.org, the (technical) reasons why the + new formats do not suit you. +Ref: dpkg-source(1), https://wiki.debian.org/Projects/DebSrc3.0 diff -Nru lintian-2.93.0/tags/m/missing-debian-source-format.tag lintian-2.89.0ubuntu1/tags/m/missing-debian-source-format.tag --- lintian-2.93.0/tags/m/missing-debian-source-format.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/missing-debian-source-format.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,19 +0,0 @@ -Tag: missing-debian-source-format -Severity: warning -Check: debian/source-dir -Explanation: Explicitly selecting a source format by putting the format in - debian/source/format is recommended. This allows for - future removal of the 1.0 default for the package source format and, - depending on the source format, may allow unambiguous declaration of - whether this package is native or non-native. - . - If you don't have a reason to stay with the old format for this package, - please consider switching to "3.0 (quilt)" (for packages with a separate - upstream tarball) or to "3.0 (native)" (for Debian native packages). - . - If you wish to keep using the old format, please create that file and put - "1.0" in it to be explicit about the source package version. If you have - problems with the 3.0 format, the dpkg maintainers are interested in - hearing, at debian-dpkg@lists.debian.org, the (technical) reasons why the - new formats do not suit you. -See-Also: dpkg-source(1), https://wiki.debian.org/Projects/DebSrc3.0 diff -Nru lintian-2.93.0/tags/m/missing-dependency-on-libc.desc lintian-2.89.0ubuntu1/tags/m/missing-dependency-on-libc.desc --- lintian-2.93.0/tags/m/missing-dependency-on-libc.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/missing-dependency-on-libc.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,15 @@ +Tag: missing-dependency-on-libc +Severity: error +Certainty: possible +Check: binaries +Ref: policy 8.6.1 +Info: The listed file appears to be linked against the C library, but the + package doesn't depend on the C library package. Normally this indicates + that ${shlibs:Depends} was omitted from the Depends line for this package + in debian/control. + . + All shared libraries and compiled binaries must be run through + dpkg-shlibdeps to find out any libraries they are linked against (often + via the dh_shlibdeps debhelper command). The package containing these + files must then depend on ${shlibs:Depends} in debian/control to + get the proper package dependencies for those libraries. diff -Nru lintian-2.93.0/tags/m/missing-dependency-on-libc.tag lintian-2.89.0ubuntu1/tags/m/missing-dependency-on-libc.tag --- lintian-2.93.0/tags/m/missing-dependency-on-libc.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/missing-dependency-on-libc.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,14 +0,0 @@ -Tag: missing-dependency-on-libc -Severity: error -Check: binaries -See-Also: policy 8.6.1 -Explanation: The listed file appears to be linked against the C library, but the - package doesn't depend on the C library package. Normally this indicates - that ${shlibs:Depends} was omitted from the Depends line for this package - in debian/control. - . - All shared libraries and compiled binaries must be run through - dpkg-shlibdeps to find out any libraries they are linked against (often - via the dh_shlibdeps debhelper command). The package containing these - files must then depend on ${shlibs:Depends} in debian/control to - get the proper package dependencies for those libraries. diff -Nru lintian-2.93.0/tags/m/missing-dependency-on-libstdc++.desc lintian-2.89.0ubuntu1/tags/m/missing-dependency-on-libstdc++.desc --- lintian-2.93.0/tags/m/missing-dependency-on-libstdc++.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/missing-dependency-on-libstdc++.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,16 @@ +Tag: missing-dependency-on-libstdc++ +Severity: error +Certainty: possible +Check: binaries +Experimental: yes +Ref: policy 8.6.1 +Info: The listed file appears to be linked against the C++ library, but the + package doesn't depend on the C++ library package. Normally this indicates + that ${shlibs:Depends} was omitted from the Depends line for this package + in debian/control. + . + All shared libraries and compiled binaries must be run through + dpkg-shlibdeps to find out any libraries they are linked against (often + via the dh_shlibdeps debhelper command). The package containing these + files must then depend on ${shlibs:Depends} in debian/control to + get the proper package dependencies for those libraries. diff -Nru lintian-2.93.0/tags/m/missing-dependency-on-libstdc++.tag lintian-2.89.0ubuntu1/tags/m/missing-dependency-on-libstdc++.tag --- lintian-2.93.0/tags/m/missing-dependency-on-libstdc++.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/missing-dependency-on-libstdc++.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,15 +0,0 @@ -Tag: missing-dependency-on-libstdc++ -Severity: error -Check: binaries -Experimental: yes -See-Also: policy 8.6.1 -Explanation: The listed file appears to be linked against the C++ library, but the - package doesn't depend on the C++ library package. Normally this indicates - that ${shlibs:Depends} was omitted from the Depends line for this package - in debian/control. - . - All shared libraries and compiled binaries must be run through - dpkg-shlibdeps to find out any libraries they are linked against (often - via the dh_shlibdeps debhelper command). The package containing these - files must then depend on ${shlibs:Depends} in debian/control to - get the proper package dependencies for those libraries. diff -Nru lintian-2.93.0/tags/m/missing-dependency-on-numpy-abi.desc lintian-2.89.0ubuntu1/tags/m/missing-dependency-on-numpy-abi.desc --- lintian-2.93.0/tags/m/missing-dependency-on-numpy-abi.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/missing-dependency-on-numpy-abi.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: missing-dependency-on-numpy-abi +Severity: error +Certainty: possible +Check: binaries +Info: This package includes a Python extension module, which uses Numpy via its + binary interface. Such packages must depend on python3-numpy-abiN. + . + If the package is using debhelper, this problem is usually due to a + missing dh_numpy3 call in debian/rules. +Ref: /usr/share/doc/python3-numpy/README.DebianMaints diff -Nru lintian-2.93.0/tags/m/missing-dependency-on-numpy-abi.tag lintian-2.89.0ubuntu1/tags/m/missing-dependency-on-numpy-abi.tag --- lintian-2.93.0/tags/m/missing-dependency-on-numpy-abi.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/missing-dependency-on-numpy-abi.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: missing-dependency-on-numpy-abi -Severity: error -Check: binaries -Explanation: This package includes a Python extension module, which uses Numpy via its - binary interface. Such packages must depend on python3-numpy-abi*N*. - . - If the package is using debhelper, this problem is usually due to a - missing dh_numpy3 call in debian/rules. -See-Also: /usr/share/doc/python3-numpy/README.DebianMaints diff -Nru lintian-2.93.0/tags/m/missing-dependency-on-perlapi.desc lintian-2.89.0ubuntu1/tags/m/missing-dependency-on-perlapi.desc --- lintian-2.93.0/tags/m/missing-dependency-on-perlapi.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/missing-dependency-on-perlapi.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,11 @@ +Tag: missing-dependency-on-perlapi +Severity: error +Check: binaries +Ref: perl-policy 4.4.2 +Info: This package includes a *.so file in /usr/lib/.../perl5, + normally indicating that it includes a binary Perl module. Binary Perl + modules must depend on perlapi-$Config{version} (from the Config module). + If the package is using debhelper, this problem is usually due to a + missing dh_perl call in debian/rules or a missing + ${perl:Depends} substitution variable in the Depends line in + debian/control. diff -Nru lintian-2.93.0/tags/m/missing-dependency-on-perlapi.tag lintian-2.89.0ubuntu1/tags/m/missing-dependency-on-perlapi.tag --- lintian-2.93.0/tags/m/missing-dependency-on-perlapi.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/missing-dependency-on-perlapi.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,11 +0,0 @@ -Tag: missing-dependency-on-perlapi -Severity: error -Check: binaries -See-Also: perl-policy 4.4.2 -Explanation: This package includes a *.so file in /usr/lib/.../perl5, - normally indicating that it includes a binary Perl module. Binary Perl - modules must depend on perlapi-$Config{version} (from the Config module). - If the package is using debhelper, this problem is usually due to a - missing dh_perl call in debian/rules or a missing - ${perl:Depends} substitution variable in the Depends line in - debian/control. diff -Nru lintian-2.93.0/tags/m/missing-dependency-on-phpapi.desc lintian-2.89.0ubuntu1/tags/m/missing-dependency-on-phpapi.desc --- lintian-2.93.0/tags/m/missing-dependency-on-phpapi.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/missing-dependency-on-phpapi.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,15 @@ +Tag: missing-dependency-on-phpapi +Severity: error +Check: binaries +Info: This package includes a *.so file in /usr/lib/phpN + (where N is a number representing the major PHP version), normally + indicating that it includes a PHP extension. PHP extensions must + depend on phpapi-$(php-configN --phpapi), without adding an + alternative package with the OR operator. + . + This can usually be achieved by, for example, adding the following + code to the binary-arch target of the rules file and adding + ${php:Depends} to the Depends field of the binary + package shipping the extension: + . + echo "php:Depends=phpapi-$(php-config5 --phpapi)" > debian/substvars diff -Nru lintian-2.93.0/tags/m/missing-dependency-on-phpapi.tag lintian-2.89.0ubuntu1/tags/m/missing-dependency-on-phpapi.tag --- lintian-2.93.0/tags/m/missing-dependency-on-phpapi.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/missing-dependency-on-phpapi.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,15 +0,0 @@ -Tag: missing-dependency-on-phpapi -Severity: error -Check: binaries -Explanation: This package includes a *.so file in /usr/lib/phpN - (where N is a number representing the major PHP version), normally - indicating that it includes a PHP extension. PHP extensions must - depend on phpapi-$(php-configN --phpapi), without adding an - alternative package with the OR operator. - . - This can usually be achieved by, for example, adding the following - code to the binary-arch target of the rules file and adding - ${php:Depends} to the Depends field of the binary - package shipping the extension: - . - echo "php:Depends=phpapi-$(php-config5 --phpapi)" > debian/substvars diff -Nru lintian-2.93.0/tags/m/missing-depends-line.desc lintian-2.89.0ubuntu1/tags/m/missing-depends-line.desc --- lintian-2.93.0/tags/m/missing-depends-line.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/missing-depends-line.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: missing-depends-line +Severity: warning +Check: binaries +Info: The package contains an ELF binary with dynamic dependencies, + but does not have a Depends line in its control file. This usually + means that a call to dpkg-shlibdeps is missing from the + package's debian/rules file. diff -Nru lintian-2.93.0/tags/m/missing-depends-line.tag lintian-2.89.0ubuntu1/tags/m/missing-depends-line.tag --- lintian-2.93.0/tags/m/missing-depends-line.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/missing-depends-line.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: missing-depends-line -Severity: warning -Check: binaries -Explanation: The package contains an ELF binary with dynamic dependencies, - but does not have a Depends line in its control file. This usually - means that a call to dpkg-shlibdeps is missing from the - package's debian/rules file. diff -Nru lintian-2.93.0/tags/m/missing-depends-on-sensible-utils.desc lintian-2.89.0ubuntu1/tags/m/missing-depends-on-sensible-utils.desc --- lintian-2.93.0/tags/m/missing-depends-on-sensible-utils.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/missing-depends-on-sensible-utils.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,15 @@ +Tag: missing-depends-on-sensible-utils +Severity: error +Certainty: possible +Check: files/contents +Info: The listed file appears to use one or more of the binaries + in sensible-utils but no binary declares a dependency for + this package. + . + As part of the transition to split sensible-utils and + debianutils, the remaining Depends from + debianutils was removed in version 4.8.2. + . + In most cases you will need to add a Depends, + Recommends, Pre-Depends or Suggests + on sensible-utils. diff -Nru lintian-2.93.0/tags/m/missing-depends-on-sensible-utils.tag lintian-2.89.0ubuntu1/tags/m/missing-depends-on-sensible-utils.tag --- lintian-2.93.0/tags/m/missing-depends-on-sensible-utils.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/missing-depends-on-sensible-utils.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,14 +0,0 @@ -Tag: missing-depends-on-sensible-utils -Severity: error -Check: files/contents -Explanation: The listed file appears to use one or more of the binaries - in sensible-utils but no binary declares a dependency for - this package. - . - As part of the transition to split sensible-utils and - debianutils, the remaining Depends from - debianutils was removed in version 4.8.2. - . - In most cases you will need to add a Depends, - Recommends, Pre-Depends or Suggests - on sensible-utils. diff -Nru lintian-2.93.0/tags/m/missing-dep-for-interpreter.desc lintian-2.89.0ubuntu1/tags/m/missing-dep-for-interpreter.desc --- lintian-2.93.0/tags/m/missing-dep-for-interpreter.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/missing-dep-for-interpreter.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: missing-dep-for-interpreter +Severity: error +Certainty: possible +Check: scripts +Info: You used an interpreter for a script that is not in an essential + package. In most cases, you will need to add a Dependency on the + package that contains the interpreter. + . + In some cases a weaker relationship, such as Suggests or Recommends, will + be more appropriate. diff -Nru lintian-2.93.0/tags/m/missing-dep-for-interpreter.tag lintian-2.89.0ubuntu1/tags/m/missing-dep-for-interpreter.tag --- lintian-2.93.0/tags/m/missing-dep-for-interpreter.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/missing-dep-for-interpreter.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: missing-dep-for-interpreter -Severity: error -Check: scripts -Explanation: You used an interpreter for a script that is not in an essential - package. In most cases, you will need to add a Dependency on the - package that contains the interpreter. - . - In some cases a weaker relationship, such as Suggests or Recommends, will - be more appropriate. diff -Nru lintian-2.93.0/tags/m/missing-dep-on-jarwrapper.desc lintian-2.89.0ubuntu1/tags/m/missing-dep-on-jarwrapper.desc --- lintian-2.93.0/tags/m/missing-dep-on-jarwrapper.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/missing-dep-on-jarwrapper.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: missing-dep-on-jarwrapper +Severity: error +Check: languages/java +Ref: java-policy 2.2 +Info: Packages containing an executable JAR must depend on jarwrapper or + other packages providing similar functionalities. diff -Nru lintian-2.93.0/tags/m/missing-dep-on-jarwrapper.tag lintian-2.89.0ubuntu1/tags/m/missing-dep-on-jarwrapper.tag --- lintian-2.93.0/tags/m/missing-dep-on-jarwrapper.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/missing-dep-on-jarwrapper.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: missing-dep-on-jarwrapper -Severity: error -Check: languages/java -See-Also: java-policy 2.2 -Explanation: Packages containing an executable JAR must depend on jarwrapper or - other packages providing similar functionalities. diff -Nru lintian-2.93.0/tags/m/missing-explanation-for-contrib-or-non-free-package.desc lintian-2.89.0ubuntu1/tags/m/missing-explanation-for-contrib-or-non-free-package.desc --- lintian-2.93.0/tags/m/missing-explanation-for-contrib-or-non-free-package.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/missing-explanation-for-contrib-or-non-free-package.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: missing-explanation-for-contrib-or-non-free-package +Severity: info +Check: debian/copyright/dep5 +Info: The specified package is in the contrib or non-free archive + area but does not include a "Comment" (or "Disclaimer") field in + its copyright file. + . + Please add a brief comment why this package cannot be part of the + main Debian distribution. +Ref: policy 12.5 diff -Nru lintian-2.93.0/tags/m/missing-explanation-for-contrib-or-non-free-package.tag lintian-2.89.0ubuntu1/tags/m/missing-explanation-for-contrib-or-non-free-package.tag --- lintian-2.93.0/tags/m/missing-explanation-for-contrib-or-non-free-package.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/missing-explanation-for-contrib-or-non-free-package.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,10 +0,0 @@ -Tag: missing-explanation-for-contrib-or-non-free-package -Severity: info -Check: debian/copyright/dep5 -Explanation: The specified package is in the contrib or non-free archive - area but does not include a "Comment" (or "Disclaimer") field in - its copyright file. - . - Please add a brief comment why this package cannot be part of the - main Debian distribution. -See-Also: policy 12.5 diff -Nru lintian-2.93.0/tags/m/missing-explanation-for-repacked-upstream-tarball.desc lintian-2.89.0ubuntu1/tags/m/missing-explanation-for-repacked-upstream-tarball.desc --- lintian-2.93.0/tags/m/missing-explanation-for-repacked-upstream-tarball.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/missing-explanation-for-repacked-upstream-tarball.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,11 @@ +Tag: missing-explanation-for-repacked-upstream-tarball +Severity: info +Certainty: possible +Check: debian/copyright/dep5 +Info: The version of this package contains dfsg, ds, + or debian which normally indicates that the upstream source + has been repackaged, but there is no "Comment" or "Files-Excluded" + field in its copyright file which explains the reason why. + . + Please add a comment why this tarball was repacked or add a suitable + "Files-Excluded" field. diff -Nru lintian-2.93.0/tags/m/missing-explanation-for-repacked-upstream-tarball.tag lintian-2.89.0ubuntu1/tags/m/missing-explanation-for-repacked-upstream-tarball.tag --- lintian-2.93.0/tags/m/missing-explanation-for-repacked-upstream-tarball.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/missing-explanation-for-repacked-upstream-tarball.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,10 +0,0 @@ -Tag: missing-explanation-for-repacked-upstream-tarball -Severity: info -Check: debian/copyright/dep5 -Explanation: The version of this package contains dfsg, ds, - or debian which normally indicates that the upstream source - has been repackaged, but there is no "Comment" or "Files-Excluded" - field in its copyright file which explains the reason why. - . - Please add a comment why this tarball was repacked or add a suitable - "Files-Excluded" field. diff -Nru lintian-2.93.0/tags/m/missing-field-in-dep5-copyright.desc lintian-2.89.0ubuntu1/tags/m/missing-field-in-dep5-copyright.desc --- lintian-2.93.0/tags/m/missing-field-in-dep5-copyright.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/missing-field-in-dep5-copyright.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: missing-field-in-dep5-copyright +Severity: warning +Certainty: possible +Check: debian/copyright/dep5 +Ref: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ +Info: The paragraph in the machine readable copyright file is missing a field + that is required by the specification. diff -Nru lintian-2.93.0/tags/m/missing-field-in-dep5-copyright.tag lintian-2.89.0ubuntu1/tags/m/missing-field-in-dep5-copyright.tag --- lintian-2.93.0/tags/m/missing-field-in-dep5-copyright.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/missing-field-in-dep5-copyright.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: missing-field-in-dep5-copyright -Severity: warning -Check: debian/copyright/dep5 -See-Also: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ -Explanation: The paragraph in the machine readable copyright file is missing a field - that is required by the specification. diff -Nru lintian-2.93.0/tags/m/missing-file-from-potfiles-in.desc lintian-2.89.0ubuntu1/tags/m/missing-file-from-potfiles-in.desc --- lintian-2.93.0/tags/m/missing-file-from-potfiles-in.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/missing-file-from-potfiles-in.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: missing-file-from-potfiles-in +Severity: warning +Check: debian/po-debconf +Info: A file listed in debian/po/POTFILES.in could not be found + in the source package. +Ref: po-debconf(7) diff -Nru lintian-2.93.0/tags/m/missing-file-from-potfiles-in.tag lintian-2.89.0ubuntu1/tags/m/missing-file-from-potfiles-in.tag --- lintian-2.93.0/tags/m/missing-file-from-potfiles-in.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/missing-file-from-potfiles-in.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: missing-file-from-potfiles-in -Severity: warning -Check: debian/po-debconf -Explanation: A file listed in debian/po/POTFILES.in could not be found - in the source package. -See-Also: po-debconf(7) diff -Nru lintian-2.93.0/tags/m/missing-intermediate-directory.desc lintian-2.89.0ubuntu1/tags/m/missing-intermediate-directory.desc --- lintian-2.93.0/tags/m/missing-intermediate-directory.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/missing-intermediate-directory.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: missing-intermediate-directory +Severity: warning +Check: files/missing +Info: The package contains files in the listed directory, but does + not contain the actual directory itself. Some tools do not cope + very well with this case. Notably Lintian prior to 2.5.32 would + crash on such packages. diff -Nru lintian-2.93.0/tags/m/missing-intermediate-directory.tag lintian-2.89.0ubuntu1/tags/m/missing-intermediate-directory.tag --- lintian-2.93.0/tags/m/missing-intermediate-directory.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/missing-intermediate-directory.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: missing-intermediate-directory -Severity: warning -Check: files/missing -Explanation: The package contains files in the listed directory, but does - not contain the actual directory itself. Some tools do not cope - very well with this case. Notably Lintian prior to 2.5.32 would - crash on such packages. diff -Nru lintian-2.93.0/tags/m/missing-license-paragraph-in-dep5-copyright.desc lintian-2.89.0ubuntu1/tags/m/missing-license-paragraph-in-dep5-copyright.desc --- lintian-2.93.0/tags/m/missing-license-paragraph-in-dep5-copyright.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/missing-license-paragraph-in-dep5-copyright.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,13 @@ +Tag: missing-license-paragraph-in-dep5-copyright +Severity: warning +Certainty: possible +Check: debian/copyright/dep5 +Info: The Files paragraph in the machine readable copyright file + references a license for which no stand-alone License paragraph + exists. + . + Sometimes this tag appears because of incorrect ordering. Stand-alone + License paragraphs must appear after all Files + paragraphs. +Ref: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/, + Bug#959067 diff -Nru lintian-2.93.0/tags/m/missing-license-paragraph-in-dep5-copyright.tag lintian-2.89.0ubuntu1/tags/m/missing-license-paragraph-in-dep5-copyright.tag --- lintian-2.93.0/tags/m/missing-license-paragraph-in-dep5-copyright.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/missing-license-paragraph-in-dep5-copyright.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,12 +0,0 @@ -Tag: missing-license-paragraph-in-dep5-copyright -Severity: warning -Check: debian/copyright/dep5 -Explanation: The Files paragraph in the machine readable copyright file - references a license for which no stand-alone License paragraph - exists. - . - Sometimes this tag appears because of incorrect ordering. Stand-alone - License paragraphs must appear *after* all Files - paragraphs. -See-Also: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/, - Bug#959067 diff -Nru lintian-2.93.0/tags/m/missing-license-text-in-dep5-copyright.desc lintian-2.89.0ubuntu1/tags/m/missing-license-text-in-dep5-copyright.desc --- lintian-2.93.0/tags/m/missing-license-text-in-dep5-copyright.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/missing-license-text-in-dep5-copyright.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: missing-license-text-in-dep5-copyright +Severity: warning +Certainty: possible +Check: debian/copyright/dep5 +Ref: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ +Info: The standalone “License” paragraph contains only short license + name, but not the license text. diff -Nru lintian-2.93.0/tags/m/missing-license-text-in-dep5-copyright.tag lintian-2.89.0ubuntu1/tags/m/missing-license-text-in-dep5-copyright.tag --- lintian-2.93.0/tags/m/missing-license-text-in-dep5-copyright.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/missing-license-text-in-dep5-copyright.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: missing-license-text-in-dep5-copyright -Severity: warning -Check: debian/copyright/dep5 -See-Also: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ -Explanation: The standalone “License” paragraph contains only short license - name, but not the license text. diff -Nru lintian-2.93.0/tags/m/missing-manifest.desc lintian-2.89.0ubuntu1/tags/m/missing-manifest.desc --- lintian-2.93.0/tags/m/missing-manifest.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/missing-manifest.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: missing-manifest +Severity: info +Certainty: possible +Check: languages/java +Info: The jar file contains .class files but no manifest. This may + indicate a build misconfiguration. diff -Nru lintian-2.93.0/tags/m/missing-manifest.tag lintian-2.89.0ubuntu1/tags/m/missing-manifest.tag --- lintian-2.93.0/tags/m/missing-manifest.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/missing-manifest.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,5 +0,0 @@ -Tag: missing-manifest -Severity: info -Check: languages/java -Explanation: The jar file contains .class files but no manifest. This may - indicate a build misconfiguration. diff -Nru lintian-2.93.0/tags/m/missing-notice-file-for-apache-license.desc lintian-2.89.0ubuntu1/tags/m/missing-notice-file-for-apache-license.desc --- lintian-2.93.0/tags/m/missing-notice-file-for-apache-license.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/missing-notice-file-for-apache-license.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,19 @@ +Tag: missing-notice-file-for-apache-license +Severity: error +Certainty: possible +Check: debian/copyright/apache-notice +Info: The package appears to be licensed under the Apache 2.0 license and + a NOTICE file (or similar) exists in the source tree. However, no + files called NOTICE or NOTICE.txt are installed in any + of the binary packages. + . + The Apache 2.0 license requires distributing of such files: + . + (d) If the Work includes a "NOTICE" text file as part of its + distribution, then any Derivative Works that You distribute must + include a readable copy of the attribution notices contained + within such NOTICE file [..] + . + Please include the file in your package, for example by adding + path/to/NOTICE to a debian/package.docs file. +Ref: /usr/share/common-licenses/Apache-2.0 diff -Nru lintian-2.93.0/tags/m/missing-notice-file-for-apache-license.tag lintian-2.89.0ubuntu1/tags/m/missing-notice-file-for-apache-license.tag --- lintian-2.93.0/tags/m/missing-notice-file-for-apache-license.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/missing-notice-file-for-apache-license.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,18 +0,0 @@ -Tag: missing-notice-file-for-apache-license -Severity: error -Check: debian/copyright/apache-notice -Explanation: The package appears to be licensed under the Apache 2.0 license and - a NOTICE file (or similar) exists in the source tree. However, no - files called NOTICE or NOTICE.txt are installed in any - of the binary packages. - . - The Apache 2.0 license requires distributing of such files: - . - (d) If the Work includes a "NOTICE" text file as part of its - distribution, then any Derivative Works that You distribute must - include a readable copy of the attribution notices contained - within such NOTICE file [..] - . - Please include the file in your package, for example by adding - path/to/NOTICE to a debian/package.docs file. -See-Also: /usr/share/common-licenses/Apache-2.0 diff -Nru lintian-2.93.0/tags/m/missing-pkg-php-tools-addon.desc lintian-2.89.0ubuntu1/tags/m/missing-pkg-php-tools-addon.desc --- lintian-2.93.0/tags/m/missing-pkg-php-tools-addon.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/missing-pkg-php-tools-addon.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,11 @@ +Tag: missing-pkg-php-tools-addon +Severity: warning +Certainty: possible +Check: languages/php/pear +Info: The package uses pkg-php-tools but dh command is called without + --with phppear or --with phpcomposer. A PECL package should also have + --with php. + . + pkg-php-tools db addons are the recommended tool for building PHP PEAR or + Composer packages. For more information, install it and read the included + README.PEAR or README.Composer. diff -Nru lintian-2.93.0/tags/m/missing-pkg-php-tools-addon.tag lintian-2.89.0ubuntu1/tags/m/missing-pkg-php-tools-addon.tag --- lintian-2.93.0/tags/m/missing-pkg-php-tools-addon.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/missing-pkg-php-tools-addon.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,10 +0,0 @@ -Tag: missing-pkg-php-tools-addon -Severity: warning -Check: languages/php/pear -Explanation: The package uses pkg-php-tools but dh command is called without - --with phppear or --with phpcomposer. A PECL package should also have - --with php. - . - pkg-php-tools db addons are the recommended tool for building PHP PEAR or - Composer packages. For more information, install it and read the included - README.PEAR or README.Composer. diff -Nru lintian-2.93.0/tags/m/missing-pkg-php-tools-buildsystem.desc lintian-2.89.0ubuntu1/tags/m/missing-pkg-php-tools-buildsystem.desc --- lintian-2.93.0/tags/m/missing-pkg-php-tools-buildsystem.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/missing-pkg-php-tools-buildsystem.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: missing-pkg-php-tools-buildsystem +Severity: warning +Certainty: possible +Check: languages/php/pear +Info: The package uses pkg-php-tools but dh command is called without + --buildsystem=phppear + . + pkg-php-tools build system is the recommended tool for building PHP PEAR + packages. For more information, install it and read the included README.PEAR. diff -Nru lintian-2.93.0/tags/m/missing-pkg-php-tools-buildsystem.tag lintian-2.89.0ubuntu1/tags/m/missing-pkg-php-tools-buildsystem.tag --- lintian-2.93.0/tags/m/missing-pkg-php-tools-buildsystem.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/missing-pkg-php-tools-buildsystem.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: missing-pkg-php-tools-buildsystem -Severity: warning -Check: languages/php/pear -Explanation: The package uses pkg-php-tools but dh command is called without - --buildsystem=phppear - . - pkg-php-tools build system is the recommended tool for building PHP PEAR - packages. For more information, install it and read the included README.PEAR. diff -Nru lintian-2.93.0/tags/m/missing-potfiles-in.desc lintian-2.89.0ubuntu1/tags/m/missing-potfiles-in.desc --- lintian-2.93.0/tags/m/missing-potfiles-in.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/missing-potfiles-in.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: missing-potfiles-in +Severity: warning +Check: debian/po-debconf +Info: The required file POTFILES.in is missing from + debian/po. +Ref: po-debconf(7) diff -Nru lintian-2.93.0/tags/m/missing-potfiles-in.tag lintian-2.89.0ubuntu1/tags/m/missing-potfiles-in.tag --- lintian-2.93.0/tags/m/missing-potfiles-in.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/missing-potfiles-in.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: missing-potfiles-in -Severity: warning -Check: debian/po-debconf -Explanation: The required file POTFILES.in is missing from - debian/po. -See-Also: po-debconf(7) diff -Nru lintian-2.93.0/tags/m/missing-prerequisite-for-gfortran-module.desc lintian-2.89.0ubuntu1/tags/m/missing-prerequisite-for-gfortran-module.desc --- lintian-2.93.0/tags/m/missing-prerequisite-for-gfortran-module.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/missing-prerequisite-for-gfortran-module.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: missing-prerequisite-for-gfortran-module +Severity: warning +Check: languages/fortran/gfortran +Info: The installation package ships a GFORTRAN module but does not depend + on gfortran-mod-, where is the module version (e.g. gfortran-mod-14 + for modules built using GCC 5). +Ref: #796352, + #714730, + https://salsa.debian.org/science-team/dh-fortran-mod/blob/debian/master/dh_fortran_mod.in diff -Nru lintian-2.93.0/tags/m/missing-prerequisite-for-gfortran-module.tag lintian-2.89.0ubuntu1/tags/m/missing-prerequisite-for-gfortran-module.tag --- lintian-2.93.0/tags/m/missing-prerequisite-for-gfortran-module.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/missing-prerequisite-for-gfortran-module.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: missing-prerequisite-for-gfortran-module -Severity: warning -Check: languages/fortran/gfortran -Explanation: The installation package ships a GFORTRAN module but does not depend - on gfortran-mod-<n>, where <n> is the module version (e.g. gfortran-mod-14 - for modules built using GCC 5). -See-Also: Bug#796352, - Bug#714730, - https://salsa.debian.org/science-team/dh-fortran-mod/blob/debian/master/dh_fortran_mod.in diff -Nru lintian-2.93.0/tags/m/missing-python-build-dependency.desc lintian-2.89.0ubuntu1/tags/m/missing-python-build-dependency.desc --- lintian-2.93.0/tags/m/missing-python-build-dependency.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/missing-python-build-dependency.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,14 @@ +Tag: missing-python-build-dependency +Severity: error +Check: debian/rules +Ref: policy 4.2 +Info: The package appears to use Python as part of its build process in + debian/rules but doesn't depend on Python. + . + Normally, packages that use Python as part of the build process should + build-depend on one of python, python-all, python-dev, python-all-dev, + python2, or python2-dev depending on whether they support multiple + versions of Python and whether they're building modules or only using + Python as part of the package build process. Packages that depend on a + specific version of Python may build-depend on the appropriate + pythonX.Y or pythonX.Y-dev package instead. diff -Nru lintian-2.93.0/tags/m/missing-python-build-dependency.tag lintian-2.89.0ubuntu1/tags/m/missing-python-build-dependency.tag --- lintian-2.93.0/tags/m/missing-python-build-dependency.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/missing-python-build-dependency.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,14 +0,0 @@ -Tag: missing-python-build-dependency -Severity: error -Check: debian/rules -See-Also: policy 4.2 -Explanation: The package appears to use Python as part of its build process in - debian/rules but doesn't depend on Python. - . - Normally, packages that use Python as part of the build process should - build-depend on one of python, python-all, python-dev, python-all-dev, - python2, or python2-dev depending on whether they support multiple - versions of Python and whether they're building modules or only using - Python as part of the package build process. Packages that depend on a - specific version of Python may build-depend on the appropriate - pythonX.Y or pythonX.Y-dev package instead. diff -Nru lintian-2.93.0/tags/m/missing-runtime-test-file.desc lintian-2.89.0ubuntu1/tags/m/missing-runtime-test-file.desc --- lintian-2.93.0/tags/m/missing-runtime-test-file.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/missing-runtime-test-file.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: missing-runtime-test-file +Severity: warning +Certainty: possible +Check: testsuite +Info: A test file listed in the debian/tests/control file does not + exist in the package source. +Ref: https://salsa.debian.org/ci-team/autopkgtest/tree/master/doc/README.package-tests.rst diff -Nru lintian-2.93.0/tags/m/missing-runtime-test-file.tag lintian-2.89.0ubuntu1/tags/m/missing-runtime-test-file.tag --- lintian-2.93.0/tags/m/missing-runtime-test-file.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/missing-runtime-test-file.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: missing-runtime-test-file -Severity: warning -Check: testsuite -Explanation: A test file listed in the debian/tests/control file does not - exist in the package source. -See-Also: https://salsa.debian.org/ci-team/autopkgtest/tree/master/doc/README.package-tests.rst diff -Nru lintian-2.93.0/tags/m/missing-separator-between-items.desc lintian-2.89.0ubuntu1/tags/m/missing-separator-between-items.desc --- lintian-2.93.0/tags/m/missing-separator-between-items.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/missing-separator-between-items.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: missing-separator-between-items +Severity: error +Check: debian/control +Info: The given field in the debian/control file contains a list + of items separated by commas and pipes. It appears a separator was + missed between two items. This can lead to bogus or incomplete + dependencies, conflicts etc. diff -Nru lintian-2.93.0/tags/m/missing-separator-between-items.tag lintian-2.89.0ubuntu1/tags/m/missing-separator-between-items.tag --- lintian-2.93.0/tags/m/missing-separator-between-items.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/missing-separator-between-items.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: missing-separator-between-items -Severity: error -Check: debian/control -Explanation: The given field in the debian/control file contains a list - of items separated by commas and pipes. It appears a separator was - missed between two items. This can lead to bogus or incomplete - dependencies, conflicts etc. diff -Nru lintian-2.93.0/tags/m/missing-systemd-service-for-init.d-rcS-script.desc lintian-2.89.0ubuntu1/tags/m/missing-systemd-service-for-init.d-rcS-script.desc --- lintian-2.93.0/tags/m/missing-systemd-service-for-init.d-rcS-script.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/missing-systemd-service-for-init.d-rcS-script.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,15 @@ +Tag: missing-systemd-service-for-init.d-rcS-script +Severity: error +Check: systemd +Ref: https://wiki.debian.org/Teams/pkg-systemd/rcSMigration +Info: The rcS init.d script has no systemd equivalent. + . + Systemd has a SysV init.d script compatibility mode. It provides access to + each SysV init.d script as long as there is no native service file with the + same name (e.g. /lib/systemd/system/rsyslog.service corresponds to + /etc/init.d/rsyslog). + . + Services in rcS.d are particularly problematic, because they often cause + dependency loops, as they are ordered very early in the boot sequence. +Renamed-From: + systemd-no-service-for-init-rcS-script diff -Nru lintian-2.93.0/tags/m/missing-systemd-service-for-init.d-rcS-script.tag lintian-2.89.0ubuntu1/tags/m/missing-systemd-service-for-init.d-rcS-script.tag --- lintian-2.93.0/tags/m/missing-systemd-service-for-init.d-rcS-script.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/missing-systemd-service-for-init.d-rcS-script.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,15 +0,0 @@ -Tag: missing-systemd-service-for-init.d-rcS-script -Severity: error -Check: systemd -See-Also: https://wiki.debian.org/Teams/pkg-systemd/rcSMigration -Explanation: The rcS init.d script has no systemd equivalent. - . - Systemd has a SysV init.d script compatibility mode. It provides access to - each SysV init.d script as long as there is no native service file with the - same name (e.g. /lib/systemd/system/rsyslog.service corresponds to - /etc/init.d/rsyslog). - . - Services in rcS.d are particularly problematic, because they often cause - dependency loops, as they are ordered very early in the boot sequence. -Renamed-From: - systemd-no-service-for-init-rcS-script diff -Nru lintian-2.93.0/tags/m/missing-systemd-service-for-init.d-script.desc lintian-2.89.0ubuntu1/tags/m/missing-systemd-service-for-init.d-script.desc --- lintian-2.93.0/tags/m/missing-systemd-service-for-init.d-script.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/missing-systemd-service-for-init.d-script.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: missing-systemd-service-for-init.d-script +Severity: warning +Check: systemd +Info: The specified init.d script has no equivalent systemd service. + . + Whilst systemd has a SysV init.d script compatibility mode, providing + native systemd support has many advantages such as being able to specify + security hardening features. + . + Please provide a suitable .service file for this script. diff -Nru lintian-2.93.0/tags/m/missing-systemd-service-for-init.d-script.tag lintian-2.89.0ubuntu1/tags/m/missing-systemd-service-for-init.d-script.tag --- lintian-2.93.0/tags/m/missing-systemd-service-for-init.d-script.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/missing-systemd-service-for-init.d-script.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,10 +0,0 @@ -Tag: missing-systemd-service-for-init.d-script -Severity: warning -Check: systemd -Explanation: The specified init.d script has no equivalent systemd service. - . - Whilst systemd has a SysV init.d script compatibility mode, providing - native systemd support has many advantages such as being able to specify - security hardening features. - . - Please provide a suitable .service file for this script. diff -Nru lintian-2.93.0/tags/m/missing-systemd-timer-for-cron-script.desc lintian-2.89.0ubuntu1/tags/m/missing-systemd-timer-for-cron-script.desc --- lintian-2.93.0/tags/m/missing-systemd-timer-for-cron-script.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/missing-systemd-timer-for-cron-script.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,15 @@ +Tag: missing-systemd-timer-for-cron-script +Severity: pedantic +Experimental: yes +Certainty: wild-guess +Check: systemd +Ref: systemd.timer(5), anacron(8) +Info: This package ships the specified cron script but does not ship a + equivalent systemd .timer unit. + . + The "desktop" and "laptop" tasks no longer pull in anacron(8), the + usual solution for desktop installations that are not running all the + time. + . + Please consider shipping an equivalent .timer file for this + script. diff -Nru lintian-2.93.0/tags/m/missing-systemd-timer-for-cron-script.tag lintian-2.89.0ubuntu1/tags/m/missing-systemd-timer-for-cron-script.tag --- lintian-2.93.0/tags/m/missing-systemd-timer-for-cron-script.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/missing-systemd-timer-for-cron-script.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,14 +0,0 @@ -Tag: missing-systemd-timer-for-cron-script -Severity: pedantic -Experimental: yes -Check: systemd -See-Also: systemd.timer(5), anacron(8) -Explanation: This package ships the specified cron script but does not ship a - equivalent systemd .timer unit. - . - The "desktop" and "laptop" tasks no longer pull in anacron(8), the - usual solution for desktop installations that are not running all the - time. - . - Please consider shipping an equivalent .timer file for this - script. diff -Nru lintian-2.93.0/tags/m/missing-templates-pot.desc lintian-2.89.0ubuntu1/tags/m/missing-templates-pot.desc --- lintian-2.93.0/tags/m/missing-templates-pot.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/missing-templates-pot.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: missing-templates-pot +Severity: warning +Check: debian/po-debconf +Info: The required file templates.pot is missing from + debian/po. +Ref: po-debconf(7) diff -Nru lintian-2.93.0/tags/m/missing-templates-pot.tag lintian-2.89.0ubuntu1/tags/m/missing-templates-pot.tag --- lintian-2.93.0/tags/m/missing-templates-pot.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/missing-templates-pot.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: missing-templates-pot -Severity: warning -Check: debian/po-debconf -Explanation: The required file templates.pot is missing from - debian/po. -See-Also: po-debconf(7) diff -Nru lintian-2.93.0/tags/m/missing-tests-control.desc lintian-2.89.0ubuntu1/tags/m/missing-tests-control.desc --- lintian-2.93.0/tags/m/missing-tests-control.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/missing-tests-control.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: missing-tests-control +Severity: info +Check: testsuite +Info: The source package declares the generic Testsuite: autopkgtest + field but provides no debian/tests/control file. + . + The control file is not needed when a specialized test suite such as + autopkgtest-pkg-perl is being used. +Ref: https://salsa.debian.org/ci-team/autopkgtest/tree/master/doc/README.package-tests.rst diff -Nru lintian-2.93.0/tags/m/missing-tests-control.tag lintian-2.89.0ubuntu1/tags/m/missing-tests-control.tag --- lintian-2.93.0/tags/m/missing-tests-control.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/missing-tests-control.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: missing-tests-control -Severity: info -Check: testsuite -Explanation: The source package declares the generic Testsuite: autopkgtest - field but provides no debian/tests/control file. - . - The control file is not needed when a specialized test suite such as - autopkgtest-pkg-perl is being used. -See-Also: https://salsa.debian.org/ci-team/autopkgtest/tree/master/doc/README.package-tests.rst diff -Nru lintian-2.93.0/tags/m/missing-vcs-browser-field.desc lintian-2.89.0ubuntu1/tags/m/missing-vcs-browser-field.desc --- lintian-2.93.0/tags/m/missing-vcs-browser-field.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/missing-vcs-browser-field.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: missing-vcs-browser-field +Severity: info +Check: fields/vcs +Info: A Vcs-* field in this package is pointing to a repository that + supports browsing of the repository via a web browser. + . + This is typically a nicer user-experience for developers and avoids + unnecessary and time-consuming clones of the repository. + . + Please add a suitable Vcs-Browser field to the package. diff -Nru lintian-2.93.0/tags/m/missing-vcs-browser-field.tag lintian-2.89.0ubuntu1/tags/m/missing-vcs-browser-field.tag --- lintian-2.93.0/tags/m/missing-vcs-browser-field.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/missing-vcs-browser-field.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,10 +0,0 @@ -Tag: missing-vcs-browser-field -Severity: info -Check: fields/vcs -Explanation: A Vcs-* field in this package is pointing to a repository that - supports browsing of the repository via a web browser. - . - This is typically a nicer user-experience for developers and avoids - unnecessary and time-consuming clones of the repository. - . - Please add a suitable Vcs-Browser field to the package. diff -Nru lintian-2.93.0/tags/m/missing-versioned-depends-on-init-system-helpers.desc lintian-2.89.0ubuntu1/tags/m/missing-versioned-depends-on-init-system-helpers.desc --- lintian-2.93.0/tags/m/missing-versioned-depends-on-init-system-helpers.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/missing-versioned-depends-on-init-system-helpers.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,16 @@ +Tag: missing-versioned-depends-on-init-system-helpers +Severity: warning +Certainty: possible +Check: scripts +Ref: update.d(8), #910593 +Info: This package uses a command in the specified maintainer script + but does not specify an appropriate minimum dependency on the + init-system-helpers package. It may have been added to the + package's Build-Depends instead of the corresponding binary + package. + . + For example, the defaults-disabled option was added to + update-rc.d in init-system-helpers version 1.50. + . + Please add a suitable Depends: to your debian/control + file. diff -Nru lintian-2.93.0/tags/m/missing-versioned-depends-on-init-system-helpers.tag lintian-2.89.0ubuntu1/tags/m/missing-versioned-depends-on-init-system-helpers.tag --- lintian-2.93.0/tags/m/missing-versioned-depends-on-init-system-helpers.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/missing-versioned-depends-on-init-system-helpers.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,15 +0,0 @@ -Tag: missing-versioned-depends-on-init-system-helpers -Severity: warning -Check: scripts -See-Also: update.d(8), Bug#910593 -Explanation: This package uses a command in the specified maintainer script - but does not specify an appropriate minimum dependency on the - init-system-helpers package. It may have been added to the - package's Build-Depends instead of the corresponding binary - package. - . - For example, the defaults-disabled option was added to - update-rc.d in init-system-helpers version 1.50. - . - Please add a suitable Depends: to your debian/control - file. diff -Nru lintian-2.93.0/tags/m/missing-xs-go-import-path-for-golang-package.desc lintian-2.89.0ubuntu1/tags/m/missing-xs-go-import-path-for-golang-package.desc --- lintian-2.93.0/tags/m/missing-xs-go-import-path-for-golang-package.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/missing-xs-go-import-path-for-golang-package.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,23 @@ +Tag: missing-xs-go-import-path-for-golang-package +Severity: info +Check: debian/control +Info: This source package does not specify a XS-Go-Import-Path + control field. + . + The XS-Go-Import-Path exposes the import path of the Go + package to the Debian archive in an easily machine-readable form which + is then used by tools such as dh-make-golang(1) to resolve + dependencies, avoid accidental duplication in the archive, or in + https://go-team.pages.debian.net/ci.html. + . + For packages using dh-golang, the field should be set to the same + value as the DH_GOPKG variable in debian/rules. + dh-golang will automatically set DH_GOPKG to the + XS-Go-Import-Path value. + . + For packages which do not use dh-golang (or where upstream does + not publish the source in a way that is compatible with go get + and hence does not have a canonical import path) it is preferred to + set a fake import path. Please contact the pkg-go team at + https://go-team.pages.debian.net/ for more specific advice in this + situation. diff -Nru lintian-2.93.0/tags/m/missing-xs-go-import-path-for-golang-package.tag lintian-2.89.0ubuntu1/tags/m/missing-xs-go-import-path-for-golang-package.tag --- lintian-2.93.0/tags/m/missing-xs-go-import-path-for-golang-package.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/missing-xs-go-import-path-for-golang-package.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,23 +0,0 @@ -Tag: missing-xs-go-import-path-for-golang-package -Severity: info -Check: debian/control -Explanation: This source package does not specify a XS-Go-Import-Path - control field. - . - The XS-Go-Import-Path exposes the import path of the Go - package to the Debian archive in an easily machine-readable form which - is then used by tools such as dh-make-golang(1) to resolve - dependencies, avoid accidental duplication in the archive, or in - https://go-team.pages.debian.net/ci.html. - . - For packages using dh-golang, the field should be set to the same - value as the DH_GOPKG variable in debian/rules. - dh-golang will automatically set DH_GOPKG to the - XS-Go-Import-Path value. - . - For packages which do not use dh-golang (or where upstream does - not publish the source in a way that is compatible with go get - and hence does not have a canonical import path) it is preferred to - set a fake import path. Please contact the pkg-go team at - https://go-team.pages.debian.net/ for more specific advice in this - situation. diff -Nru lintian-2.93.0/tags/m/misspelled-closes-bug.desc lintian-2.89.0ubuntu1/tags/m/misspelled-closes-bug.desc --- lintian-2.93.0/tags/m/misspelled-closes-bug.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/misspelled-closes-bug.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: misspelled-closes-bug +Severity: warning +Check: debian/changelog +Ref: policy 5.6.22 +Info: The last changelog entry uses Close: #123456 instead of correct + Closes: #123456 diff -Nru lintian-2.93.0/tags/m/misspelled-closes-bug.tag lintian-2.89.0ubuntu1/tags/m/misspelled-closes-bug.tag --- lintian-2.93.0/tags/m/misspelled-closes-bug.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/misspelled-closes-bug.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: misspelled-closes-bug -Severity: warning -Check: debian/changelog -See-Also: policy 5.6.22 -Explanation: The last changelog entry uses Close: #123456 instead of correct - Closes: #123456 diff -Nru lintian-2.93.0/tags/m/mknod-in-maintainer-script.desc lintian-2.89.0ubuntu1/tags/m/mknod-in-maintainer-script.desc --- lintian-2.93.0/tags/m/mknod-in-maintainer-script.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/mknod-in-maintainer-script.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: mknod-in-maintainer-script +Severity: error +Check: scripts +Ref: policy 10.6 +Info: Maintainer scripts must not create device files directly. They + should call MAKEDEV instead. + . + If mknod is being used to create a FIFO (named pipe), use + mkfifo instead to avoid triggering this tag. diff -Nru lintian-2.93.0/tags/m/mknod-in-maintainer-script.tag lintian-2.89.0ubuntu1/tags/m/mknod-in-maintainer-script.tag --- lintian-2.93.0/tags/m/mknod-in-maintainer-script.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/mknod-in-maintainer-script.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: mknod-in-maintainer-script -Severity: error -Check: scripts -See-Also: policy 10.6 -Explanation: Maintainer scripts must not create device files directly. They - should call MAKEDEV instead. - . - If mknod is being used to create a FIFO (named pipe), use - mkfifo instead to avoid triggering this tag. diff -Nru lintian-2.93.0/tags/m/more-than-one-patch-system.desc lintian-2.89.0ubuntu1/tags/m/more-than-one-patch-system.desc --- lintian-2.93.0/tags/m/more-than-one-patch-system.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/more-than-one-patch-system.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: more-than-one-patch-system +Severity: warning +Check: debian/patches +Info: Either the build-dependencies list more than one patch system or the + package uses the 3.0 (quilt) source format but also has a + dependency on dpatch. It's unlikely that you need both patch + systems at the same time, and having multiple patch systems in play + simultaneously can make understanding and modifying the source package + unnecessarily complex. diff -Nru lintian-2.93.0/tags/m/more-than-one-patch-system.tag lintian-2.89.0ubuntu1/tags/m/more-than-one-patch-system.tag --- lintian-2.93.0/tags/m/more-than-one-patch-system.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/more-than-one-patch-system.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: more-than-one-patch-system -Severity: warning -Check: debian/patches -Explanation: Either the build-dependencies list more than one patch system or the - package uses the 3.0 (quilt) source format but also has a - dependency on dpatch. It's unlikely that you need both patch - systems at the same time, and having multiple patch systems in play - simultaneously can make understanding and modifying the source package - unnecessarily complex. diff -Nru lintian-2.93.0/tags/m/multiarch-foreign-cmake-file.desc lintian-2.89.0ubuntu1/tags/m/multiarch-foreign-cmake-file.desc --- lintian-2.93.0/tags/m/multiarch-foreign-cmake-file.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/multiarch-foreign-cmake-file.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: multiarch-foreign-cmake-file +Severity: error +Check: files/multi-arch +Info: The package is architecture-dependent, ships a cmake file in a public, + architecture-dependent cmake search path and is marked Multi-Arch: + foreign. CMake will be unable to find this file, unless it is installed + for a matching architecture, but the foreign marking says that the + architecture should not matter. + . + Please remove the Multi-Arch: foreign stanza. diff -Nru lintian-2.93.0/tags/m/multiarch-foreign-cmake-file.tag lintian-2.89.0ubuntu1/tags/m/multiarch-foreign-cmake-file.tag --- lintian-2.93.0/tags/m/multiarch-foreign-cmake-file.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/multiarch-foreign-cmake-file.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,10 +0,0 @@ -Tag: multiarch-foreign-cmake-file -Severity: error -Check: files/multi-arch -Explanation: The package is architecture-dependent, ships a cmake file in a public, - architecture-dependent cmake search path and is marked Multi-Arch: - foreign. CMake will be unable to find this file, unless it is installed - for a matching architecture, but the foreign marking says that the - architecture should not matter. - . - Please remove the Multi-Arch: foreign stanza. diff -Nru lintian-2.93.0/tags/m/multiarch-foreign-pkgconfig.desc lintian-2.89.0ubuntu1/tags/m/multiarch-foreign-pkgconfig.desc --- lintian-2.93.0/tags/m/multiarch-foreign-pkgconfig.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/multiarch-foreign-pkgconfig.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: multiarch-foreign-pkgconfig +Severity: error +Check: files/multi-arch +Info: The package is architecture-dependent, ships a pkg-config file in a + public, architecture-dependent pkg-config search path and is marked + Multi-Arch: foreign. pkg-config will be unable to find this file, + unless it is installed for a matching architecture, but the foreign + marking says that the architecture should not matter. + . + Please remove the Multi-Arch: foreign stanza. diff -Nru lintian-2.93.0/tags/m/multiarch-foreign-pkgconfig.tag lintian-2.89.0ubuntu1/tags/m/multiarch-foreign-pkgconfig.tag --- lintian-2.93.0/tags/m/multiarch-foreign-pkgconfig.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/multiarch-foreign-pkgconfig.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,10 +0,0 @@ -Tag: multiarch-foreign-pkgconfig -Severity: error -Check: files/multi-arch -Explanation: The package is architecture-dependent, ships a pkg-config file in a - public, architecture-dependent pkg-config search path and is marked - Multi-Arch: foreign. pkg-config will be unable to find this file, - unless it is installed for a matching architecture, but the foreign - marking says that the architecture should not matter. - . - Please remove the Multi-Arch: foreign stanza. diff -Nru lintian-2.93.0/tags/m/multiarch-foreign-shared-library.desc lintian-2.89.0ubuntu1/tags/m/multiarch-foreign-shared-library.desc --- lintian-2.93.0/tags/m/multiarch-foreign-shared-library.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/multiarch-foreign-shared-library.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,12 @@ +Tag: multiarch-foreign-shared-library +Severity: error +Certainty: possible +Check: files/multi-arch +Info: The package is architecture-dependent, ships a shared library in + a public library search path and is marked Multi-Arch: + foreign. Typically, shared libraries are marked Multi-Arch: + same when possible. Sometimes, private shared libraries are put + into the public library search path to accommodate programs in the + same package, but this package does not contain any programs. + . + Please remove the Multi-Arch: foreign stanza. diff -Nru lintian-2.93.0/tags/m/multiarch-foreign-shared-library.tag lintian-2.89.0ubuntu1/tags/m/multiarch-foreign-shared-library.tag --- lintian-2.93.0/tags/m/multiarch-foreign-shared-library.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/multiarch-foreign-shared-library.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,11 +0,0 @@ -Tag: multiarch-foreign-shared-library -Severity: error -Check: files/multi-arch -Explanation: The package is architecture-dependent, ships a shared library in - a public library search path and is marked Multi-Arch: - foreign. Typically, shared libraries are marked Multi-Arch: - same when possible. Sometimes, private shared libraries are put - into the public library search path to accommodate programs in the - same package, but this package does not contain any programs. - . - Please remove the Multi-Arch: foreign stanza. diff -Nru lintian-2.93.0/tags/m/multiarch-foreign-static-library.desc lintian-2.89.0ubuntu1/tags/m/multiarch-foreign-static-library.desc --- lintian-2.93.0/tags/m/multiarch-foreign-static-library.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/multiarch-foreign-static-library.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,11 @@ +Tag: multiarch-foreign-static-library +Severity: error +Certainty: possible +Check: files/multi-arch +Info: The package is architecture-dependent, ships a static library in a + public, architecture-dependent library search path and is marked + Multi-Arch: foreign. A compiler will be unable to find this file, + unless it is installed for a matching architecture, but the foreign + marking says that the architecture should not matter. + . + Please remove the Multi-Arch: foreign stanza. diff -Nru lintian-2.93.0/tags/m/multiarch-foreign-static-library.tag lintian-2.89.0ubuntu1/tags/m/multiarch-foreign-static-library.tag --- lintian-2.93.0/tags/m/multiarch-foreign-static-library.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/multiarch-foreign-static-library.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,10 +0,0 @@ -Tag: multiarch-foreign-static-library -Severity: error -Check: files/multi-arch -Explanation: The package is architecture-dependent, ships a static library in a - public, architecture-dependent library search path and is marked - Multi-Arch: foreign. A compiler will be unable to find this file, - unless it is installed for a matching architecture, but the foreign - marking says that the architecture should not matter. - . - Please remove the Multi-Arch: foreign stanza. diff -Nru lintian-2.93.0/tags/m/multi-arch-same-package-calls-pycompile.desc lintian-2.89.0ubuntu1/tags/m/multi-arch-same-package-calls-pycompile.desc --- lintian-2.93.0/tags/m/multi-arch-same-package-calls-pycompile.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/multi-arch-same-package-calls-pycompile.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,25 @@ +Tag: multi-arch-same-package-calls-pycompile +Severity: warning +Certainty: possible +Check: scripts +Info: This Multi-Arch: same package uses pycompile or + py3compile in the specified maintainer script. + . + py{,3}compile are tools used to byte-compile Python source + files. It is typically run on installation of Debian packages that ship + Python modules. However, they do not support installing several + architectures of the same package and this is not Multi-Arch: safe. + . + If the contents of the package is not architecture dependent, it should + usually be made binary-all. + . + If the contents of the package is architecture dependent, it should + usually get a dependency on the Python interpreter for the same + architecture. This is a dependency in the form of python3, not + an architecture-qualified dependency such as python3:any (which + can be fulfilled by the Python interpreter for any architecture). + . + If a dependency on the Python interpreter for the same architecture + exists (usually generated by dh-python), the + Multi-Arch: same has no effect and should be dropped. +Ref: pycompile(1), py3compile(1), #812228 diff -Nru lintian-2.93.0/tags/m/multi-arch-same-package-calls-pycompile.tag lintian-2.89.0ubuntu1/tags/m/multi-arch-same-package-calls-pycompile.tag --- lintian-2.93.0/tags/m/multi-arch-same-package-calls-pycompile.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/multi-arch-same-package-calls-pycompile.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,24 +0,0 @@ -Tag: multi-arch-same-package-calls-pycompile -Severity: warning -Check: scripts -Explanation: This Multi-Arch: same package uses pycompile or - py3compile in the specified maintainer script. - . - py{,3}compile are tools used to byte-compile Python source - files. It is typically run on installation of Debian packages that ship - Python modules. However, they do not support installing several - architectures of the same package and this is not Multi-Arch: safe. - . - If the contents of the package is not architecture dependent, it should - usually be made binary-all. - . - If the contents of the package is architecture dependent, it should - usually get a dependency on the Python interpreter for the same - architecture. This is a dependency in the form of python3, not - an architecture-qualified dependency such as python3:any (which - can be fulfilled by the Python interpreter for any architecture). - . - If a dependency on the Python interpreter for the same architecture - exists (usually generated by dh-python), the - Multi-Arch: same has no effect and should be dropped. -See-Also: pycompile(1), py3compile(1), Bug#812228 diff -Nru lintian-2.93.0/tags/m/multi-arch-same-package-has-arch-specific-overrides.desc lintian-2.89.0ubuntu1/tags/m/multi-arch-same-package-has-arch-specific-overrides.desc --- lintian-2.93.0/tags/m/multi-arch-same-package-has-arch-specific-overrides.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/multi-arch-same-package-has-arch-specific-overrides.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: multi-arch-same-package-has-arch-specific-overrides +Severity: warning +Check: fields/multi-arch +Info: The specified file contains architecture-specific Lintian overrides + but this package is declared as Multi-Arch: same. +Ref: lintian 2.4.3, #787406 diff -Nru lintian-2.93.0/tags/m/multi-arch-same-package-has-arch-specific-overrides.tag lintian-2.89.0ubuntu1/tags/m/multi-arch-same-package-has-arch-specific-overrides.tag --- lintian-2.93.0/tags/m/multi-arch-same-package-has-arch-specific-overrides.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/multi-arch-same-package-has-arch-specific-overrides.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: multi-arch-same-package-has-arch-specific-overrides -Severity: warning -Check: fields/multi-arch -Explanation: The specified file contains architecture-specific Lintian overrides - but this package is declared as Multi-Arch: same. -See-Also: lintian 2.4.3, Bug#787406 diff -Nru lintian-2.93.0/tags/m/multiline-architecture-field.desc lintian-2.89.0ubuntu1/tags/m/multiline-architecture-field.desc --- lintian-2.93.0/tags/m/multiline-architecture-field.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/multiline-architecture-field.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: multiline-architecture-field +Severity: error +Check: debian/control +Ref: policy 5.6.8 +Info: The values of the Architecture field in debian/control must not + be separated by anything else than spaces; that is, they must form a + single line and are not allowed to span multiple lines. diff -Nru lintian-2.93.0/tags/m/multiline-architecture-field.tag lintian-2.89.0ubuntu1/tags/m/multiline-architecture-field.tag --- lintian-2.93.0/tags/m/multiline-architecture-field.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/multiline-architecture-field.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: multiline-architecture-field -Severity: error -Check: debian/control -See-Also: policy 5.6.8 -Explanation: The values of the Architecture field in debian/control must not - be separated by anything else than spaces; that is, they must form a - single line and are not allowed to span multiple lines. diff -Nru lintian-2.93.0/tags/m/multiline-field.desc lintian-2.89.0ubuntu1/tags/m/multiline-field.desc --- lintian-2.93.0/tags/m/multiline-field.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/multiline-field.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,5 @@ +Tag: multiline-field +Severity: error +Check: fields/multi-line +Info: Most control fields must have only a single line of data. +Ref: policy 5.1 diff -Nru lintian-2.93.0/tags/m/multiline-field.tag lintian-2.89.0ubuntu1/tags/m/multiline-field.tag --- lintian-2.93.0/tags/m/multiline-field.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/multiline-field.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,5 +0,0 @@ -Tag: multiline-field -Severity: error -Check: fields/multi-line -Explanation: Most control fields must have only a single line of data. -See-Also: policy 5.1 diff -Nru lintian-2.93.0/tags/m/multiple-distributions-in-changes-file.desc lintian-2.89.0ubuntu1/tags/m/multiple-distributions-in-changes-file.desc --- lintian-2.93.0/tags/m/multiple-distributions-in-changes-file.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/multiple-distributions-in-changes-file.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,12 @@ +Tag: multiple-distributions-in-changes-file +Severity: error +Certainty: possible +Check: fields/distribution +Info: You've specified more than one target distribution for your upload + in the *.changes file, probably via the most recent entry in the + debian/changelog file. + . + Although this syntax is valid, it is not accepted by the Debian archive + management software. This may not be a problem if this upload is + targeted at an archive other than Debian's. +Ref: policy 5.6.14 diff -Nru lintian-2.93.0/tags/m/multiple-distributions-in-changes-file.tag lintian-2.89.0ubuntu1/tags/m/multiple-distributions-in-changes-file.tag --- lintian-2.93.0/tags/m/multiple-distributions-in-changes-file.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/m/multiple-distributions-in-changes-file.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,11 +0,0 @@ -Tag: multiple-distributions-in-changes-file -Severity: error -Check: fields/distribution -Explanation: You've specified more than one target distribution for your upload - in the *.changes file, probably via the most recent entry in the - debian/changelog file. - . - Although this syntax is valid, it is not accepted by the Debian archive - management software. This may not be a problem if this upload is - targeted at an archive other than Debian's. -See-Also: policy 5.6.14 diff -Nru lintian-2.93.0/tags/n/named-copyright-for-single-installable.desc lintian-2.89.0ubuntu1/tags/n/named-copyright-for-single-installable.desc --- lintian-2.93.0/tags/n/named-copyright-for-single-installable.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/named-copyright-for-single-installable.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: named-copyright-for-single-installable +Severity: warning +Check: debian/copyright +Ref: policy 12.5 +Info: Every package must include the file /usr/share/doc/pkg/copyright. + A copy of this file should be in debian/copyright in the source package. + . + These sources ship a copyright file named according to debhelper convention + debian/$package.copyright but build only one installable. Please move + the copyright file to debian/copyright. diff -Nru lintian-2.93.0/tags/n/named-copyright-for-single-installable.tag lintian-2.89.0ubuntu1/tags/n/named-copyright-for-single-installable.tag --- lintian-2.93.0/tags/n/named-copyright-for-single-installable.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/named-copyright-for-single-installable.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,10 +0,0 @@ -Tag: named-copyright-for-single-installable -Severity: warning -Check: debian/copyright -See-Also: policy 12.5 -Explanation: Every package must include the file /usr/share/doc/*pkg*/copyright. - A copy of this file should be in debian/copyright in the source package. - . - These sources ship a copyright file named according to debhelper convention - debian/$package.copyright but build only one installable. Please move - the copyright file to debian/copyright. diff -Nru lintian-2.93.0/tags/n/national-encoding.desc lintian-2.89.0ubuntu1/tags/n/national-encoding.desc --- lintian-2.93.0/tags/n/national-encoding.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/national-encoding.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,23 @@ +Tag: national-encoding +Severity: warning +Check: files/encoding +Renamed-From: + national-encoding-in-text-file + debian-changelog-file-uses-obsolete-national-encoding + debian-control-file-uses-obsolete-national-encoding + debian-copyright-file-uses-obsolete-national-encoding + debian-news-file-uses-obsolete-national-encoding + debian-tests-control-uses-national-encoding + doc-base-file-uses-obsolete-national-encoding + national-encoding-in-debconf-template + national-encoding-in-manpage +Info: A file is not valid UTF-8. + . + Debian has used UTF-8 for many years. Support for national encodings + is being phased out. This file probably appears to users in mangled + characters (also called mojibake). + . + Packaging control files must be encoded in valid UTF-8. + . + Please convert the file to UTF-8 using iconv or a similar + tool. diff -Nru lintian-2.93.0/tags/n/national-encoding.tag lintian-2.89.0ubuntu1/tags/n/national-encoding.tag --- lintian-2.93.0/tags/n/national-encoding.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/national-encoding.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,23 +0,0 @@ -Tag: national-encoding -Severity: warning -Check: files/encoding -Renamed-From: - national-encoding-in-text-file - debian-changelog-file-uses-obsolete-national-encoding - debian-control-file-uses-obsolete-national-encoding - debian-copyright-file-uses-obsolete-national-encoding - debian-news-file-uses-obsolete-national-encoding - debian-tests-control-uses-national-encoding - doc-base-file-uses-obsolete-national-encoding - national-encoding-in-debconf-template - national-encoding-in-manpage -Explanation: A file is not valid UTF-8. - . - Debian has used UTF-8 for many years. Support for national encodings - is being phased out. This file probably appears to users in mangled - characters (also called mojibake). - . - Packaging control files must be encoded in valid UTF-8. - . - Please convert the file to UTF-8 using iconv or a similar - tool. diff -Nru lintian-2.93.0/tags/n/native-source-file-without-utf8-name.desc lintian-2.89.0ubuntu1/tags/n/native-source-file-without-utf8-name.desc --- lintian-2.93.0/tags/n/native-source-file-without-utf8-name.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/native-source-file-without-utf8-name.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: native-source-file-without-utf8-name +Severity: error +Check: files/names +Ref: policy 10.10 +Info: The file name in the native source tree is not valid UTF-8. + File names must decode as valid UTF-8. Please rename the file. + . + Unlike other file names in Lintian, which are printed in UTF-8, the + attached reference shows the bytes used by the file system. + Unprintable characters may have been replaced. diff -Nru lintian-2.93.0/tags/n/native-source-file-without-utf8-name.tag lintian-2.89.0ubuntu1/tags/n/native-source-file-without-utf8-name.tag --- lintian-2.93.0/tags/n/native-source-file-without-utf8-name.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/native-source-file-without-utf8-name.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,10 +0,0 @@ -Tag: native-source-file-without-utf8-name -Severity: error -Check: files/names -See-Also: policy 10.10 -Explanation: The file name in the native source tree is not valid UTF-8. - File names must decode as valid UTF-8. Please rename the file. - . - Unlike other file names in Lintian, which are printed in UTF-8, the - attached reference shows the bytes used by the file system. - Unprintable characters may have been replaced. diff -Nru lintian-2.93.0/tags/n/needless-dependency-on-jre.desc lintian-2.89.0ubuntu1/tags/n/needless-dependency-on-jre.desc --- lintian-2.93.0/tags/n/needless-dependency-on-jre.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/needless-dependency-on-jre.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,16 @@ +Tag: needless-dependency-on-jre +Severity: warning +Certainty: possible +Check: fields/package-relations +Info: The package appear to be a Java library and depending on one + or more JRE/JDK packages. As of 05 Apr 2010, the Java Policy no + longer mandates that Java libraries depend on Java Runtimes. + . + If the library package ships executables along with the library, + then please consider making this an application package or move the + binaries to a (new) application package. + . + If there is otherwise a valid reason for this dependency, please override + the tag. +Ref: https://lists.debian.org/debian-devel-changes/2010/04/msg00774.html, + #227587 diff -Nru lintian-2.93.0/tags/n/needless-dependency-on-jre.tag lintian-2.89.0ubuntu1/tags/n/needless-dependency-on-jre.tag --- lintian-2.93.0/tags/n/needless-dependency-on-jre.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/needless-dependency-on-jre.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,15 +0,0 @@ -Tag: needless-dependency-on-jre -Severity: warning -Check: fields/package-relations -Explanation: The package appear to be a Java library and depending on one - or more JRE/JDK packages. As of 05 Apr 2010, the Java Policy no - longer mandates that Java libraries depend on Java Runtimes. - . - If the library package ships executables along with the library, - then please consider making this an application package or move the - binaries to a (new) application package. - . - If there is otherwise a valid reason for this dependency, please override - the tag. -See-Also: https://lists.debian.org/debian-devel-changes/2010/04/msg00774.html, - Bug#227587 diff -Nru lintian-2.93.0/tags/n/needlessly-depends-on-awk.desc lintian-2.89.0ubuntu1/tags/n/needlessly-depends-on-awk.desc --- lintian-2.93.0/tags/n/needlessly-depends-on-awk.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/needlessly-depends-on-awk.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: needlessly-depends-on-awk +Severity: error +Check: fields/package-relations +Info: The package seems to declare a relation on awk. awk is a virtual + package, but it is special since it's de facto essential. If you don't + need to depend on a specific version of awk (which wouldn't work anyway, + as dpkg doesn't support versioned provides), you should remove the + dependency on awk. diff -Nru lintian-2.93.0/tags/n/needlessly-depends-on-awk.tag lintian-2.89.0ubuntu1/tags/n/needlessly-depends-on-awk.tag --- lintian-2.93.0/tags/n/needlessly-depends-on-awk.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/needlessly-depends-on-awk.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: needlessly-depends-on-awk -Severity: error -Check: fields/package-relations -Explanation: The package seems to declare a relation on awk. awk is a virtual - package, but it is special since it's de facto essential. If you don't - need to depend on a specific version of awk (which wouldn't work anyway, - as dpkg doesn't support versioned provides), you should remove the - dependency on awk. diff -Nru lintian-2.93.0/tags/n/needless-suggest-recommend-libservlet-java.desc lintian-2.89.0ubuntu1/tags/n/needless-suggest-recommend-libservlet-java.desc --- lintian-2.93.0/tags/n/needless-suggest-recommend-libservlet-java.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/needless-suggest-recommend-libservlet-java.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,12 @@ +Tag: needless-suggest-recommend-libservlet-java +Severity: warning +Check: fields/package-relations +Info: Package should not suggest or recommend libservlet-java + Java servlets are only used in the context of a server (example: Tomcat or + Jetty). This server will have this dependency and will take care of the + loading of this package with the right libservlet. + . + Removing this dependency will fix this warning. + . + If there is otherwise a valid reason for this suggestion or recommendation, + please override the tag. diff -Nru lintian-2.93.0/tags/n/needless-suggest-recommend-libservlet-java.tag lintian-2.89.0ubuntu1/tags/n/needless-suggest-recommend-libservlet-java.tag --- lintian-2.93.0/tags/n/needless-suggest-recommend-libservlet-java.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/needless-suggest-recommend-libservlet-java.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,12 +0,0 @@ -Tag: needless-suggest-recommend-libservlet-java -Severity: warning -Check: fields/package-relations -Explanation: Package should not suggest or recommend libservlet-java - Java servlets are only used in the context of a server (example: Tomcat or - Jetty). This server will have this dependency and will take care of the - loading of this package with the right libservlet. - . - Removing this dependency will fix this warning. - . - If there is otherwise a valid reason for this suggestion or recommendation, - please override the tag. diff -Nru lintian-2.93.0/tags/n/nested-examples-directory.desc lintian-2.89.0ubuntu1/tags/n/nested-examples-directory.desc --- lintian-2.93.0/tags/n/nested-examples-directory.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/nested-examples-directory.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: nested-examples-directory +Severity: error +Check: documentation/examples +Info: Package contains a usr/share/doc/something/examples/examples + directory. It was most likely installed by accident, since one examples/ + directory should be enough for everybody(tm). diff -Nru lintian-2.93.0/tags/n/nested-examples-directory.tag lintian-2.89.0ubuntu1/tags/n/nested-examples-directory.tag --- lintian-2.93.0/tags/n/nested-examples-directory.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/nested-examples-directory.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: nested-examples-directory -Severity: error -Check: documentation/examples -Explanation: Package contains a usr/share/doc/something/examples/examples - directory. It was most likely installed by accident, since one examples/ - directory should be enough for everybody(tm). diff -Nru lintian-2.93.0/tags/n/newer-debconf-templates.desc lintian-2.89.0ubuntu1/tags/n/newer-debconf-templates.desc --- lintian-2.93.0/tags/n/newer-debconf-templates.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/newer-debconf-templates.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,14 @@ +Tag: newer-debconf-templates +Severity: warning +Certainty: possible +Check: debian/po-debconf +Info: debconf-updatepo has not been run since the last change to your + debconf templates. + . + You should run debconf-updatepo whenever debconf templates files are + changed so that translators can be warned that their files are + outdated. + . + This can be ensured by running debconf-updatepo in the 'clean' target + of debian/rules. PO files will then always be up-to-date when + building the source package. diff -Nru lintian-2.93.0/tags/n/newer-debconf-templates.tag lintian-2.89.0ubuntu1/tags/n/newer-debconf-templates.tag --- lintian-2.93.0/tags/n/newer-debconf-templates.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/newer-debconf-templates.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,13 +0,0 @@ -Tag: newer-debconf-templates -Severity: warning -Check: debian/po-debconf -Explanation: debconf-updatepo has not been run since the last change to your - debconf templates. - . - You should run debconf-updatepo whenever debconf templates files are - changed so that translators can be warned that their files are - outdated. - . - This can be ensured by running debconf-updatepo in the 'clean' target - of debian/rules. PO files will then always be up-to-date when - building the source package. diff -Nru lintian-2.93.0/tags/n/newer-standards-version.desc lintian-2.89.0ubuntu1/tags/n/newer-standards-version.desc --- lintian-2.93.0/tags/n/newer-standards-version.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/newer-standards-version.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: newer-standards-version +Severity: warning +Check: fields/standards-version +Info: The source package refers to a Standards-Version which is + newer than the highest one Lintian is programmed to check. + . + If the source package is correct, please upgrade Lintian to the newest + version. diff -Nru lintian-2.93.0/tags/n/newer-standards-version.tag lintian-2.89.0ubuntu1/tags/n/newer-standards-version.tag --- lintian-2.93.0/tags/n/newer-standards-version.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/newer-standards-version.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: newer-standards-version -Severity: warning -Check: fields/standards-version -Explanation: The source package refers to a Standards-Version which is - newer than the highest one Lintian is programmed to check. - . - If the source package is correct, please upgrade Lintian to the newest - version. diff -Nru lintian-2.93.0/tags/n/new-essential-package.desc lintian-2.89.0ubuntu1/tags/n/new-essential-package.desc --- lintian-2.93.0/tags/n/new-essential-package.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/new-essential-package.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: new-essential-package +Severity: error +Certainty: possible +Check: fields/essential +Info: This package has the Essential flag set. New Essential packages + are sufficiently rare that it seems worth warning about. They should + be discussed on debian-devel first. +Ref: policy 3.8 diff -Nru lintian-2.93.0/tags/n/new-essential-package.tag lintian-2.89.0ubuntu1/tags/n/new-essential-package.tag --- lintian-2.93.0/tags/n/new-essential-package.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/new-essential-package.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: new-essential-package -Severity: error -Check: fields/essential -Explanation: This package has the Essential flag set. New Essential packages - are sufficiently rare that it seems worth warning about. They should - be discussed on debian-devel first. -See-Also: policy 3.8 diff -Nru lintian-2.93.0/tags/n/new-package-should-not-package-python2-module.desc lintian-2.89.0ubuntu1/tags/n/new-package-should-not-package-python2-module.desc --- lintian-2.93.0/tags/n/new-package-should-not-package-python2-module.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/new-package-should-not-package-python2-module.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,26 @@ +Tag: new-package-should-not-package-python2-module +Severity: warning +Check: languages/python +Info: This package appears to be the initial packaging of a new upstream + software package (ie. it contains a single changelog entry). However, it + ships the specified module for Python 2. + . + Python 2.x modules should not be packaged unless strictly necessary (such + as being explicitly requested by an end-user or required as part of a + dependency chain) as the 2.x series of Python is due for deprecation and + will not be maintained by upstream past 2020 and will likely be dropped + after the release of Debian "buster". + . + If upstream have not moved or have no intention to move to Python 3, + please be certain that Debian would benefit from the inclusion, continued + maintenance burden and (eventual) removal of this package before you + upload. + . + This warning can be ignored if the package is not intended for Debian or + if it is a split of an existing Debian package. This warning can also be + ignored if viewed on https://lintian.debian.org/. + . + Please do not override this warning; rather, add a justification to your + changelog entry; Lintian looks in this version's changelog entry for the + specified package name or the phrase "Python 2 version" or similar. + This will ensure that any rationale is preserved for posterity. diff -Nru lintian-2.93.0/tags/n/new-package-should-not-package-python2-module.tag lintian-2.89.0ubuntu1/tags/n/new-package-should-not-package-python2-module.tag --- lintian-2.93.0/tags/n/new-package-should-not-package-python2-module.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/new-package-should-not-package-python2-module.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,26 +0,0 @@ -Tag: new-package-should-not-package-python2-module -Severity: warning -Check: languages/python -Explanation: This package appears to be the initial packaging of a new upstream - software package (ie. it contains a single changelog entry). However, it - ships the specified module for Python 2. - . - Python 2.x modules should not be packaged unless strictly necessary (such - as being explicitly requested by an end-user or required as part of a - dependency chain) as the 2.x series of Python is due for deprecation and - will not be maintained by upstream past 2020 and will likely be dropped - after the release of Debian "buster". - . - If upstream have not moved or have no intention to move to Python 3, - please be certain that Debian would benefit from the inclusion, continued - maintenance burden and (eventual) removal of this package before you - upload. - . - This warning can be ignored if the package is not intended for Debian or - if it is a split of an existing Debian package. This warning can also be - ignored if viewed on https://lintian.debian.org/. - . - Please do not override this warning; rather, add a justification to your - changelog entry; Lintian looks in this version's changelog entry for the - specified package name or the phrase "Python 2 version" or similar. - This will ensure that any rationale is preserved for posterity. diff -Nru lintian-2.93.0/tags/n/new-package-uses-date-based-version-number.desc lintian-2.89.0ubuntu1/tags/n/new-package-uses-date-based-version-number.desc --- lintian-2.93.0/tags/n/new-package-uses-date-based-version-number.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/new-package-uses-date-based-version-number.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,11 @@ +Tag: new-package-uses-date-based-version-number +Severity: warning +Check: debian/changelog +Info: This package appears to be the first packaging of a new upstream + software package (there is only one changelog entry and the Debian + revision is 1) and uses a date-based versioning scheme such as + YYYYMMDD-1. + . + Packages using date-based version numbering should use a "0~" prefix + (eg. 0~20201612-1 or similar) to avoid having to introduce an epoch if + upstream starts tagging releases in a more conventional manner. diff -Nru lintian-2.93.0/tags/n/new-package-uses-date-based-version-number.tag lintian-2.89.0ubuntu1/tags/n/new-package-uses-date-based-version-number.tag --- lintian-2.93.0/tags/n/new-package-uses-date-based-version-number.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/new-package-uses-date-based-version-number.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,11 +0,0 @@ -Tag: new-package-uses-date-based-version-number -Severity: warning -Check: debian/changelog -Explanation: This package appears to be the first packaging of a new upstream - software package (there is only one changelog entry and the Debian - revision is 1) and uses a date-based versioning scheme such as - YYYYMMDD-1. - . - Packages using date-based version numbering should use a "0~" prefix - (eg. 0~20201612-1 or similar) to avoid having to introduce an epoch if - upstream starts tagging releases in a more conventional manner. diff -Nru lintian-2.93.0/tags/n/nfs-temporary-file-in-package.desc lintian-2.89.0ubuntu1/tags/n/nfs-temporary-file-in-package.desc --- lintian-2.93.0/tags/n/nfs-temporary-file-in-package.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/nfs-temporary-file-in-package.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: nfs-temporary-file-in-package +Severity: warning +Check: files/unwanted +Info: There is a file in the package whose name matches the format NFS + uses to temporarily save files that were deleted while another process + had them open. It may have been included in the package by accident + while building the package in an NFS filesystem. diff -Nru lintian-2.93.0/tags/n/nfs-temporary-file-in-package.tag lintian-2.89.0ubuntu1/tags/n/nfs-temporary-file-in-package.tag --- lintian-2.93.0/tags/n/nfs-temporary-file-in-package.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/nfs-temporary-file-in-package.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: nfs-temporary-file-in-package -Severity: warning -Check: files/unwanted -Explanation: There is a file in the package whose name matches the format NFS - uses to temporarily save files that were deleted while another process - had them open. It may have been included in the package by accident - while building the package in an NFS filesystem. diff -Nru lintian-2.93.0/tags/n/nmu-in-changelog.desc lintian-2.89.0ubuntu1/tags/n/nmu-in-changelog.desc --- lintian-2.93.0/tags/n/nmu-in-changelog.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/nmu-in-changelog.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,14 @@ +Tag: nmu-in-changelog +Severity: warning +Certainty: possible +Check: nmu +Renamed-From: changelog-should-not-mention-nmu +Info: The first line of the changelog entry for this package appears to + indicate it is a non-maintainer upload (by including either that string + or the string "NMU" and not saying that it's an acknowledgement), but the + changelog indicates the person making this release is one of the + maintainers. + . + If this was intended to be an NMU, do not add yourself as a maintainer or + uploader. Otherwise, please rephrase your changelog entry to not cause + confusion. diff -Nru lintian-2.93.0/tags/n/nmu-in-changelog.tag lintian-2.89.0ubuntu1/tags/n/nmu-in-changelog.tag --- lintian-2.93.0/tags/n/nmu-in-changelog.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/nmu-in-changelog.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,13 +0,0 @@ -Tag: nmu-in-changelog -Severity: warning -Check: nmu -Renamed-From: changelog-should-not-mention-nmu -Explanation: The first line of the changelog entry for this package appears to - indicate it is a non-maintainer upload (by including either that string - or the string "NMU" and not saying that it's an acknowledgement), but the - changelog indicates the person making this release is one of the - maintainers. - . - If this was intended to be an NMU, do not add yourself as a maintainer or - uploader. Otherwise, please rephrase your changelog entry to not cause - confusion. diff -Nru lintian-2.93.0/tags/n/no-changelog.desc lintian-2.89.0ubuntu1/tags/n/no-changelog.desc --- lintian-2.93.0/tags/n/no-changelog.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/no-changelog.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,18 @@ +Tag: no-changelog +Severity: error +Check: debian/changelog +Renamed-From: + changelog-file-missing-in-native-package + debian-changelog-file-missing +Info: A Debian package that provides a /usr/share/doc/pkg + directory must install a changelog file. + . + For native packages the best name is + /usr/share/doc/pkg/changelog.gz. + . + For non-native packages the best name is + /usr/share/doc/pkg/changelog.Debian.gz. + . + This tag may also be emitted when the changelog exists but does not + otherwise resemble a Debian changelog. +Ref: policy 12.7 diff -Nru lintian-2.93.0/tags/n/no-changelog.tag lintian-2.89.0ubuntu1/tags/n/no-changelog.tag --- lintian-2.93.0/tags/n/no-changelog.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/no-changelog.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,18 +0,0 @@ -Tag: no-changelog -Severity: error -Check: debian/changelog -Renamed-From: - changelog-file-missing-in-native-package - debian-changelog-file-missing -Explanation: A Debian package that provides a /usr/share/doc/*pkg* - directory must install a changelog file. - . - For native packages the best name is - /usr/share/doc/*pkg*/changelog.gz. - . - For non-native packages the best name is - /usr/share/doc/*pkg*/changelog.Debian.gz. - . - This tag may also be emitted when the changelog exists but does not - otherwise resemble a Debian changelog. -See-Also: policy 12.7 diff -Nru lintian-2.93.0/tags/n/no-complete-debconf-translation.desc lintian-2.89.0ubuntu1/tags/n/no-complete-debconf-translation.desc --- lintian-2.93.0/tags/n/no-complete-debconf-translation.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/no-complete-debconf-translation.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,14 @@ +Tag: no-complete-debconf-translation +Severity: info +Certainty: possible +Check: debian/po-debconf +Info: Even though this package provides debconf translation support, there + are no translations or none of the translations are complete. This may + mean that translators weren't properly warned about new strings. + . + Translators may be notified of changes using podebconf-report-po, for + example: + . + podebconf-report-po --call --withtranslators --deadline="+10 days" \ + --languageteam +Ref: devref 6.5.2.2 diff -Nru lintian-2.93.0/tags/n/no-complete-debconf-translation.tag lintian-2.89.0ubuntu1/tags/n/no-complete-debconf-translation.tag --- lintian-2.93.0/tags/n/no-complete-debconf-translation.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/no-complete-debconf-translation.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,13 +0,0 @@ -Tag: no-complete-debconf-translation -Severity: info -Check: debian/po-debconf -Explanation: Even though this package provides debconf translation support, there - are no translations or none of the translations are complete. This may - mean that translators weren't properly warned about new strings. - . - Translators may be notified of changes using podebconf-report-po, for - example: - . - podebconf-report-po --call --withtranslators --deadline="+10 days" \ - --languageteam -See-Also: devref 6.5.2.2 diff -Nru lintian-2.93.0/tags/n/no-copyright-file.desc lintian-2.89.0ubuntu1/tags/n/no-copyright-file.desc --- lintian-2.93.0/tags/n/no-copyright-file.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/no-copyright-file.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: no-copyright-file +Severity: error +Check: debian/copyright +Info: Each binary package has to include a plain file + /usr/share/doc/pkg/copyright +Ref: policy 12.5 diff -Nru lintian-2.93.0/tags/n/no-copyright-file.tag lintian-2.89.0ubuntu1/tags/n/no-copyright-file.tag --- lintian-2.93.0/tags/n/no-copyright-file.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/no-copyright-file.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: no-copyright-file -Severity: error -Check: debian/copyright -Explanation: Each binary package has to include a plain file - /usr/share/doc/*pkg*/copyright -See-Also: policy 12.5 diff -Nru lintian-2.93.0/tags/n/no-ctrl-scripts.desc lintian-2.89.0ubuntu1/tags/n/no-ctrl-scripts.desc --- lintian-2.93.0/tags/n/no-ctrl-scripts.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/no-ctrl-scripts.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,5 @@ +Tag: no-ctrl-scripts +Severity: classification +Check: control-files +Info: The package does not rely on any maintainer scripts (or other + executable control files). diff -Nru lintian-2.93.0/tags/n/no-ctrl-scripts.tag lintian-2.89.0ubuntu1/tags/n/no-ctrl-scripts.tag --- lintian-2.93.0/tags/n/no-ctrl-scripts.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/no-ctrl-scripts.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,5 +0,0 @@ -Tag: no-ctrl-scripts -Severity: classification -Check: control-files -Explanation: The package does not rely on any maintainer scripts (or other - executable control files). diff -Nru lintian-2.93.0/tags/n/no-debconf-config.desc lintian-2.89.0ubuntu1/tags/n/no-debconf-config.desc --- lintian-2.93.0/tags/n/no-debconf-config.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/no-debconf-config.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: no-debconf-config +Severity: error +Certainty: possible +Check: debian/debconf +Info: The package contains a "templates" file in its control area but has no + corresponding "config" script. This is occasionally OK, but is usually an + error. diff -Nru lintian-2.93.0/tags/n/no-debconf-config.tag lintian-2.89.0ubuntu1/tags/n/no-debconf-config.tag --- lintian-2.93.0/tags/n/no-debconf-config.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/no-debconf-config.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: no-debconf-config -Severity: error -Check: debian/debconf -Explanation: The package contains a "templates" file in its control area but has no - corresponding "config" script. This is occasionally OK, but is usually an - error. diff -Nru lintian-2.93.0/tags/n/no-debconf-templates.desc lintian-2.89.0ubuntu1/tags/n/no-debconf-templates.desc --- lintian-2.93.0/tags/n/no-debconf-templates.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/no-debconf-templates.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: no-debconf-templates +Severity: warning +Certainty: possible +Check: debian/debconf +Info: The package contains a "config" script in its control area but has no + corresponding "templates" file. This is occasionally OK, but is usually an + error. diff -Nru lintian-2.93.0/tags/n/no-debconf-templates.tag lintian-2.89.0ubuntu1/tags/n/no-debconf-templates.tag --- lintian-2.93.0/tags/n/no-debconf-templates.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/no-debconf-templates.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: no-debconf-templates -Severity: warning -Check: debian/debconf -Explanation: The package contains a "config" script in its control area but has no - corresponding "templates" file. This is occasionally OK, but is usually an - error. diff -Nru lintian-2.93.0/tags/n/no-debian-copyright-in-source.desc lintian-2.89.0ubuntu1/tags/n/no-debian-copyright-in-source.desc --- lintian-2.93.0/tags/n/no-debian-copyright-in-source.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/no-debian-copyright-in-source.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: no-debian-copyright-in-source +Severity: warning +Check: debian/copyright +Renamed-From: no-debian-copyright +Ref: policy 12.5 +Info: Every package must include the file /usr/share/doc/pkg/copyright. + A copy of this file should be in debian/copyright in the source package. diff -Nru lintian-2.93.0/tags/n/no-debian-copyright-in-source.tag lintian-2.89.0ubuntu1/tags/n/no-debian-copyright-in-source.tag --- lintian-2.93.0/tags/n/no-debian-copyright-in-source.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/no-debian-copyright-in-source.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: no-debian-copyright-in-source -Severity: warning -Check: debian/copyright -Renamed-From: no-debian-copyright -See-Also: policy 12.5 -Explanation: Every package must include the file /usr/share/doc/*pkg*/copyright. - A copy of this file should be in debian/copyright in the source package. diff -Nru lintian-2.93.0/tags/n/nodejs-lock-file.desc lintian-2.89.0ubuntu1/tags/n/nodejs-lock-file.desc --- lintian-2.93.0/tags/n/nodejs-lock-file.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/nodejs-lock-file.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,16 @@ +Tag: nodejs-lock-file +Severity: error +Check: languages/javascript/nodejs +Info: package-lock.json is automatically generated for any operations where + npm modifies either the node_modules tree, or package.json. It + describes the exact tree that was generated, such that subsequent + installs are able to generate identical trees, regardless of + intermediate dependency updates. + . + These information are useless from a debian point of view, because + version are managed by dpkg. + . + Moreover, package-lock.json feature to pin to some version + dependencies is a anti feature of the debian way of managing package, + and could lead to security problems in the likely case of debian + solving security problems by patching instead of upgrading. diff -Nru lintian-2.93.0/tags/n/nodejs-lock-file.tag lintian-2.89.0ubuntu1/tags/n/nodejs-lock-file.tag --- lintian-2.93.0/tags/n/nodejs-lock-file.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/nodejs-lock-file.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,16 +0,0 @@ -Tag: nodejs-lock-file -Severity: error -Check: languages/javascript/nodejs -Explanation: package-lock.json is automatically generated for any operations where - npm modifies either the node_modules tree, or package.json. It - describes the exact tree that was generated, such that subsequent - installs are able to generate identical trees, regardless of - intermediate dependency updates. - . - These information are useless from a debian point of view, because - version are managed by dpkg. - . - Moreover, package-lock.json feature to pin to some version - dependencies is a anti feature of the debian way of managing package, - and could lead to security problems in the likely case of debian - solving security problems by patching instead of upgrading. diff -Nru lintian-2.93.0/tags/n/nodejs-module.desc lintian-2.89.0ubuntu1/tags/n/nodejs-module.desc --- lintian-2.93.0/tags/n/nodejs-module.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/nodejs-module.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,4 @@ +Tag: nodejs-module +Severity: classification +Check: languages/javascript/nodejs +Info: Display nodejs module name, version and path diff -Nru lintian-2.93.0/tags/n/nodejs-module-installed-in-bad-directory.desc lintian-2.89.0ubuntu1/tags/n/nodejs-module-installed-in-bad-directory.desc --- lintian-2.93.0/tags/n/nodejs-module-installed-in-bad-directory.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/nodejs-module-installed-in-bad-directory.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: nodejs-module-installed-in-bad-directory +Severity: warning +Check: languages/javascript/nodejs +Info: This package installs the specified nodejs module in a location that + does not match its name declared in package.json. This renders this module + unusable using a simple require(). + . + You can use pkg-js-tools auto installer to avoid this, see + /usr/share/doc/pkg-js-tools/README.md.gz diff -Nru lintian-2.93.0/tags/n/nodejs-module-installed-in-bad-directory.tag lintian-2.89.0ubuntu1/tags/n/nodejs-module-installed-in-bad-directory.tag --- lintian-2.93.0/tags/n/nodejs-module-installed-in-bad-directory.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/nodejs-module-installed-in-bad-directory.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: nodejs-module-installed-in-bad-directory -Severity: warning -Check: languages/javascript/nodejs -Explanation: This package installs the specified nodejs module in a location that - does not match its name declared in package.json. This renders this module - unusable using a simple require(). - . - You can use pkg-js-tools auto installer to avoid this, see - /usr/share/doc/pkg-js-tools/README.md.gz diff -Nru lintian-2.93.0/tags/n/nodejs-module-installed-in-usr-lib.desc lintian-2.89.0ubuntu1/tags/n/nodejs-module-installed-in-usr-lib.desc --- lintian-2.93.0/tags/n/nodejs-module-installed-in-usr-lib.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/nodejs-module-installed-in-usr-lib.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,11 @@ +Tag: nodejs-module-installed-in-usr-lib +Severity: warning +Check: languages/javascript/nodejs +Info: This package installs the specified file under /usr/lib/nodejs. + Since the release of Buster, these files should be installed under + /usr/share/nodejs (for arch independent modules) or + /usr/lib/$DEB_HOST_MULTIARCH/nodejs (for arch dependent modules) + instead. + . + You can use pkg-js-tools auto installer to avoid this, see + /usr/share/doc/pkg-js-tools/README.md.gz diff -Nru lintian-2.93.0/tags/n/nodejs-module-installed-in-usr-lib.tag lintian-2.89.0ubuntu1/tags/n/nodejs-module-installed-in-usr-lib.tag --- lintian-2.93.0/tags/n/nodejs-module-installed-in-usr-lib.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/nodejs-module-installed-in-usr-lib.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,11 +0,0 @@ -Tag: nodejs-module-installed-in-usr-lib -Severity: warning -Check: languages/javascript/nodejs -Explanation: This package installs the specified file under /usr/lib/nodejs. - Since the release of Buster, these files should be installed under - /usr/share/nodejs (for arch *independent* modules) or - /usr/lib/$DEB_HOST_MULTIARCH/nodejs (for arch *dependent* modules) - instead. - . - You can use pkg-js-tools auto installer to avoid this, see - /usr/share/doc/pkg-js-tools/README.md.gz diff -Nru lintian-2.93.0/tags/n/nodejs-module-not-declared.desc lintian-2.89.0ubuntu1/tags/n/nodejs-module-not-declared.desc --- lintian-2.93.0/tags/n/nodejs-module-not-declared.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/nodejs-module-not-declared.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: nodejs-module-not-declared +Severity: warning +Check: languages/javascript/nodejs +Info: This package installs the specified nodejs module in a nodejs root + directory without declaring it in "Provides:" field in debian/control. + . + You can use Provides: ${nodejs:Provides} provided by pkg-js-tools + to fix this. See /usr/share/doc/pkg-js-tools/README.md.gz for more. diff -Nru lintian-2.93.0/tags/n/nodejs-module-not-declared.tag lintian-2.89.0ubuntu1/tags/n/nodejs-module-not-declared.tag --- lintian-2.93.0/tags/n/nodejs-module-not-declared.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/nodejs-module-not-declared.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: nodejs-module-not-declared -Severity: warning -Check: languages/javascript/nodejs -Explanation: This package installs the specified nodejs module in a nodejs root - directory without declaring it in "Provides:" field in debian/control. - . - You can use Provides: ${nodejs:Provides} provided by pkg-js-tools - to fix this. See /usr/share/doc/pkg-js-tools/README.md.gz for more. diff -Nru lintian-2.93.0/tags/n/nodejs-module.tag lintian-2.89.0ubuntu1/tags/n/nodejs-module.tag --- lintian-2.93.0/tags/n/nodejs-module.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/nodejs-module.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,4 +0,0 @@ -Tag: nodejs-module -Severity: classification -Check: languages/javascript/nodejs -Explanation: Display nodejs module name, version and path diff -Nru lintian-2.93.0/tags/n/no-dep5-copyright.desc lintian-2.89.0ubuntu1/tags/n/no-dep5-copyright.desc --- lintian-2.93.0/tags/n/no-dep5-copyright.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/no-dep5-copyright.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: no-dep5-copyright +Severity: pedantic +Check: debian/copyright/dep5 +Info: This package does not use a machine-readable debian/copyright file. + . + This format makes it easier to review licenses and can be easily parsed + by Lintian. +Ref: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ diff -Nru lintian-2.93.0/tags/n/no-dep5-copyright.tag lintian-2.89.0ubuntu1/tags/n/no-dep5-copyright.tag --- lintian-2.93.0/tags/n/no-dep5-copyright.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/no-dep5-copyright.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: no-dep5-copyright -Severity: pedantic -Check: debian/copyright/dep5 -Explanation: This package does not use a machine-readable debian/copyright file. - . - This format makes it easier to review licenses and can be easily parsed - by Lintian. -See-Also: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ diff -Nru lintian-2.93.0/tags/n/node-package-install-in-nodejs-rootdir.desc lintian-2.89.0ubuntu1/tags/n/node-package-install-in-nodejs-rootdir.desc --- lintian-2.93.0/tags/n/node-package-install-in-nodejs-rootdir.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/node-package-install-in-nodejs-rootdir.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,5 @@ +Tag: node-package-install-in-nodejs-rootdir +Severity: error +Check: languages/javascript/nodejs +Info: This package contains a file under /usr/*/nodejs + instead of /usr/*/nodejs/${package}. diff -Nru lintian-2.93.0/tags/n/node-package-install-in-nodejs-rootdir.tag lintian-2.89.0ubuntu1/tags/n/node-package-install-in-nodejs-rootdir.tag --- lintian-2.93.0/tags/n/node-package-install-in-nodejs-rootdir.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/node-package-install-in-nodejs-rootdir.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,5 +0,0 @@ -Tag: node-package-install-in-nodejs-rootdir -Severity: error -Check: languages/javascript/nodejs -Explanation: This package contains a file under /usr/*/nodejs - instead of /usr/*/nodejs/${package}. diff -Nru lintian-2.93.0/tags/n/no-dh-sequencer.desc lintian-2.89.0ubuntu1/tags/n/no-dh-sequencer.desc --- lintian-2.93.0/tags/n/no-dh-sequencer.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/no-dh-sequencer.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,11 @@ +Tag: no-dh-sequencer +Severity: info +Certainty: possible +Check: debian/rules/dh-sequencer +Info: This package does not use the dh sequencer in debian/rules. + . + While maintainers may use a variety of build systems, this one + is by far the most popular. + . + Maintainers are strongly encouraged to use the dh sequencer + in new packages and convert existing ones when appropriate. diff -Nru lintian-2.93.0/tags/n/no-dh-sequencer.tag lintian-2.89.0ubuntu1/tags/n/no-dh-sequencer.tag --- lintian-2.93.0/tags/n/no-dh-sequencer.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/no-dh-sequencer.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,10 +0,0 @@ -Tag: no-dh-sequencer -Severity: info -Check: debian/rules/dh-sequencer -Explanation: This package does not use the dh sequencer in debian/rules. - . - While maintainers may use a variety of build systems, this one - is by far the most popular. - . - Maintainers are strongly encouraged to use the dh sequencer - in new packages and convert existing ones when appropriate. diff -Nru lintian-2.93.0/tags/n/no-english-manual-page.desc lintian-2.89.0ubuntu1/tags/n/no-english-manual-page.desc --- lintian-2.93.0/tags/n/no-english-manual-page.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/no-english-manual-page.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: no-english-manual-page +Severity: warning +Check: documentation/manual +Renamed-From: binary-without-english-manpage +Info: Each binary in /usr/bin, /usr/sbin, /bin, + /sbin or /usr/games should have a manual page. You do + not provide an English manual page, but only a translated one. + . + Since the English language serves as a fallback option, the lack of an + English page leaves most users without any kind of manual page at all. diff -Nru lintian-2.93.0/tags/n/no-english-manual-page.tag lintian-2.89.0ubuntu1/tags/n/no-english-manual-page.tag --- lintian-2.93.0/tags/n/no-english-manual-page.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/no-english-manual-page.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,10 +0,0 @@ -Tag: no-english-manual-page -Severity: warning -Check: documentation/manual -Renamed-From: binary-without-english-manpage -Explanation: Each binary in /usr/bin, /usr/sbin, /bin, - /sbin or /usr/games should have a manual page. You do - not provide an English manual page, but only a translated one. - . - Since the English language serves as a fallback option, the lack of an - English page leaves most users without any kind of manual page at all. diff -Nru lintian-2.93.0/tags/n/no-homepage-field.desc lintian-2.89.0ubuntu1/tags/n/no-homepage-field.desc --- lintian-2.93.0/tags/n/no-homepage-field.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/no-homepage-field.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: no-homepage-field +Severity: pedantic +Certainty: possible +Check: fields/homepage +Info: This non-native package lacks a Homepage field. If the + package has an upstream home page that contains useful information or + resources for the end user, consider adding a Homepage control + field to debian/control. +Ref: policy 5.6.23 diff -Nru lintian-2.93.0/tags/n/no-homepage-field.tag lintian-2.89.0ubuntu1/tags/n/no-homepage-field.tag --- lintian-2.93.0/tags/n/no-homepage-field.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/no-homepage-field.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: no-homepage-field -Severity: pedantic -Check: fields/homepage -Explanation: This non-native package lacks a Homepage field. If the - package has an upstream home page that contains useful information or - resources for the end user, consider adding a Homepage control - field to debian/control. -See-Also: policy 5.6.23 diff -Nru lintian-2.93.0/tags/n/no-human-maintainers.desc lintian-2.89.0ubuntu1/tags/n/no-human-maintainers.desc --- lintian-2.93.0/tags/n/no-human-maintainers.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/no-human-maintainers.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: no-human-maintainers +Severity: error +Certainty: possible +Check: fields/maintainer +Info: The Maintainer address for this package is a mailing list and there + are no Uploaders listed. Team-maintained packages must list the human + maintainers in the Uploaders field. +Ref: policy 3.3, devref 5.12 diff -Nru lintian-2.93.0/tags/n/no-human-maintainers.tag lintian-2.89.0ubuntu1/tags/n/no-human-maintainers.tag --- lintian-2.93.0/tags/n/no-human-maintainers.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/no-human-maintainers.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: no-human-maintainers -Severity: error -Check: fields/maintainer -Explanation: The Maintainer address for this package is a mailing list and there - are no Uploaders listed. Team-maintained packages must list the human - maintainers in the Uploaders field. -See-Also: policy 3.3, devref 5.12 diff -Nru lintian-2.93.0/tags/n/no-manual-page.desc lintian-2.89.0ubuntu1/tags/n/no-manual-page.desc --- lintian-2.93.0/tags/n/no-manual-page.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/no-manual-page.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,24 @@ +Tag: no-manual-page +Severity: warning +Certainty: possible +Check: documentation/manual +Renamed-From: binary-without-manpage +Info: Each binary in /usr/bin, /usr/sbin, /bin, + /sbin or /usr/games should have a manual page + . + Note that though the man program has the capability to check for + several program names in the NAMES section, each of these programs + should have its own manual page (a symbolic link to the appropriate + manual page is sufficient) because other manual page viewers such as + xman or tkman don't support this. + . + If the name of the manual page differs from the binary by case, man + may be able to find it anyway; however, it is still best practice to match + the exact capitalization of the executable in the manual page. + . + If the manual pages are provided by another package on which this package + depends, Lintian may not be able to determine that manual pages are + available. In this case, after confirming that all binaries do have + manual pages after this package and its dependencies are installed, please + add a Lintian override. +Ref: policy 12.1 diff -Nru lintian-2.93.0/tags/n/no-manual-page.tag lintian-2.89.0ubuntu1/tags/n/no-manual-page.tag --- lintian-2.93.0/tags/n/no-manual-page.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/no-manual-page.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,23 +0,0 @@ -Tag: no-manual-page -Severity: warning -Check: documentation/manual -Renamed-From: binary-without-manpage -Explanation: Each binary in /usr/bin, /usr/sbin, /bin, - /sbin or /usr/games should have a manual page - . - Note that though the man program has the capability to check for - several program names in the NAMES section, each of these programs - should have its own manual page (a symbolic link to the appropriate - manual page is sufficient) because other manual page viewers such as - xman or tkman don't support this. - . - If the name of the manual page differs from the binary by case, man - may be able to find it anyway; however, it is still best practice to match - the exact capitalization of the executable in the manual page. - . - If the manual pages are provided by another package on which this package - depends, Lintian may not be able to determine that manual pages are - available. In this case, after confirming that all binaries do have - manual pages after this package and its dependencies are installed, please - add a Lintian override. -See-Also: policy 12.1 diff -Nru lintian-2.93.0/tags/n/no-md5sums-control-file.desc lintian-2.89.0ubuntu1/tags/n/no-md5sums-control-file.desc --- lintian-2.93.0/tags/n/no-md5sums-control-file.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/no-md5sums-control-file.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,12 @@ +Tag: no-md5sums-control-file +Severity: info +Check: md5sums +Info: This package does not contain an md5sums control file. This control + file listing the MD5 checksums of the contents of the package is not + required, but if present debsums can use it to verify that no files + shipped with your package have been modified. Providing it is + recommended. + . + If you are using debhelper to create your package, just add a call to + dh_md5sums at the end of your binary-indep or binary-arch + target, right before dh_builddeb. diff -Nru lintian-2.93.0/tags/n/no-md5sums-control-file.tag lintian-2.89.0ubuntu1/tags/n/no-md5sums-control-file.tag --- lintian-2.93.0/tags/n/no-md5sums-control-file.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/no-md5sums-control-file.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,12 +0,0 @@ -Tag: no-md5sums-control-file -Severity: info -Check: md5sums -Explanation: This package does not contain an md5sums control file. This control - file listing the MD5 checksums of the contents of the package is not - required, but if present debsums can use it to verify that no files - shipped with your package have been modified. Providing it is - recommended. - . - If you are using debhelper to create your package, just add a call to - dh_md5sums at the end of your binary-indep or binary-arch - target, right before dh_builddeb. diff -Nru lintian-2.93.0/tags/n/non-conf-file-in-modprobe.d.desc lintian-2.89.0ubuntu1/tags/n/non-conf-file-in-modprobe.d.desc --- lintian-2.93.0/tags/n/non-conf-file-in-modprobe.d.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/non-conf-file-in-modprobe.d.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,11 @@ +Tag: non-conf-file-in-modprobe.d +Severity: error +Check: modprobe +Ref: https://lists.debian.org/debian-devel/2009/03/msg00119.html +Info: Files in /etc/modprobe.d should use filenames ending in + .conf. modprobe silently ignores all files which do not match + this convention. + . + If the file is an example containing only comments, consider installing + it in another location as files in /etc/modprobe.d are + read each time modprobe is run (which is often at boot time). diff -Nru lintian-2.93.0/tags/n/non-conf-file-in-modprobe.d.tag lintian-2.89.0ubuntu1/tags/n/non-conf-file-in-modprobe.d.tag --- lintian-2.93.0/tags/n/non-conf-file-in-modprobe.d.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/non-conf-file-in-modprobe.d.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,11 +0,0 @@ -Tag: non-conf-file-in-modprobe.d -Severity: error -Check: modprobe -See-Also: https://lists.debian.org/debian-devel/2009/03/msg00119.html -Explanation: Files in /etc/modprobe.d should use filenames ending in - .conf. modprobe silently ignores all files which do not match - this convention. - . - If the file is an example containing only comments, consider installing - it in another location as files in /etc/modprobe.d are - read each time modprobe is run (which is often at boot time). diff -Nru lintian-2.93.0/tags/n/non-consecutive-debian-revision.desc lintian-2.89.0ubuntu1/tags/n/non-consecutive-debian-revision.desc --- lintian-2.93.0/tags/n/non-consecutive-debian-revision.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/non-consecutive-debian-revision.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: non-consecutive-debian-revision +Severity: pedantic +Certainty: possible +Check: debian/changelog +Experimental: yes +Info: The latest changelog entry refers to a Debian revision (eg. + 1.2-3) that is not consecutive to the previous changelog entry + (eg. 1.2-2). Please use a consecutive Debian revision or use a + UNRELEASED version instead. diff -Nru lintian-2.93.0/tags/n/non-consecutive-debian-revision.tag lintian-2.89.0ubuntu1/tags/n/non-consecutive-debian-revision.tag --- lintian-2.93.0/tags/n/non-consecutive-debian-revision.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/non-consecutive-debian-revision.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: non-consecutive-debian-revision -Severity: pedantic -Check: debian/changelog -Experimental: yes -Explanation: The latest changelog entry refers to a Debian revision (eg. - 1.2-3) that is not consecutive to the previous changelog entry - (eg. 1.2-2). Please use a consecutive Debian revision or use a - UNRELEASED version instead. diff -Nru lintian-2.93.0/tags/n/non-debug-file-in-debug-package.desc lintian-2.89.0ubuntu1/tags/n/non-debug-file-in-debug-package.desc --- lintian-2.93.0/tags/n/non-debug-file-in-debug-package.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/non-debug-file-in-debug-package.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: non-debug-file-in-debug-package +Severity: error +Certainty: possible +Check: files/debug-packages +Info: This auto-generated package (eg. -dbgsym) contains the + specified file that is not a .debug file. + . + This may be due to the upstream build system miscalculating + installation paths. +Ref: #958945 diff -Nru lintian-2.93.0/tags/n/non-debug-file-in-debug-package.tag lintian-2.89.0ubuntu1/tags/n/non-debug-file-in-debug-package.tag --- lintian-2.93.0/tags/n/non-debug-file-in-debug-package.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/non-debug-file-in-debug-package.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: non-debug-file-in-debug-package -Severity: error -Check: files/debug-packages -Explanation: This auto-generated package (eg. -dbgsym) contains the - specified file that is not a .debug file. - . - This may be due to the upstream build system miscalculating - installation paths. -See-Also: Bug#958945 diff -Nru lintian-2.93.0/tags/n/non-empty-dependency_libs-in-la-file.desc lintian-2.89.0ubuntu1/tags/n/non-empty-dependency_libs-in-la-file.desc --- lintian-2.93.0/tags/n/non-empty-dependency_libs-in-la-file.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/non-empty-dependency_libs-in-la-file.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,15 @@ +Tag: non-empty-dependency_libs-in-la-file +Severity: error +Check: shared-libs +Info: The dependency_libs field in the .la file has not been cleared. It has + long been a release goal to get rid of unneeded .la files and clearing the + dependency_libs field from the rest of them. + . + A non-empty dependency_libs field will also stall the Multi-Arch + conversion. + . + The .la file in itself may be useful if the library is loaded dynamically + via libltdl. +Ref: https://wiki.debian.org/ReleaseGoals/LAFileRemoval, + https://lists.debian.org/debian-devel/2011/05/msg01003.html, + https://lists.debian.org/debian-devel/2011/05/msg01146.html diff -Nru lintian-2.93.0/tags/n/non-empty-dependency_libs-in-la-file.tag lintian-2.89.0ubuntu1/tags/n/non-empty-dependency_libs-in-la-file.tag --- lintian-2.93.0/tags/n/non-empty-dependency_libs-in-la-file.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/non-empty-dependency_libs-in-la-file.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,15 +0,0 @@ -Tag: non-empty-dependency_libs-in-la-file -Severity: error -Check: shared-libs -Explanation: The dependency_libs field in the .la file has not been cleared. It has - long been a release goal to get rid of unneeded .la files and clearing the - dependency_libs field from the rest of them. - . - A non-empty dependency_libs field will also stall the Multi-Arch - conversion. - . - The .la file in itself may be useful if the library is loaded dynamically - via libltdl. -See-Also: https://wiki.debian.org/ReleaseGoals/LAFileRemoval, - https://lists.debian.org/debian-devel/2011/05/msg01003.html, - https://lists.debian.org/debian-devel/2011/05/msg01146.html diff -Nru lintian-2.93.0/tags/n/non-etc-file-marked-as-conffile.desc lintian-2.89.0ubuntu1/tags/n/non-etc-file-marked-as-conffile.desc --- lintian-2.93.0/tags/n/non-etc-file-marked-as-conffile.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/non-etc-file-marked-as-conffile.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: non-etc-file-marked-as-conffile +Severity: error +Certainty: possible +Check: conffiles +Info: A file installed in some other directory than /etc + is marked as conffile. A conffile typically implies a configuration + file, and Policy mandates such files to be in /etc. +Ref: policy 10.7.2 diff -Nru lintian-2.93.0/tags/n/non-etc-file-marked-as-conffile.tag lintian-2.89.0ubuntu1/tags/n/non-etc-file-marked-as-conffile.tag --- lintian-2.93.0/tags/n/non-etc-file-marked-as-conffile.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/non-etc-file-marked-as-conffile.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: non-etc-file-marked-as-conffile -Severity: error -Check: conffiles -Explanation: A file installed in some other directory than /etc - is marked as conffile. A conffile typically implies a configuration - file, and Policy mandates such files to be in /etc. -See-Also: policy 10.7.2 diff -Nru lintian-2.93.0/tags/n/no-newline-at-end.desc lintian-2.89.0ubuntu1/tags/n/no-newline-at-end.desc --- lintian-2.93.0/tags/n/no-newline-at-end.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/no-newline-at-end.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: no-newline-at-end +Severity: warning +Check: debian/trailing-whitespace +Info: The named text file does not end with a newline. + . + Git considers it a whitespace error. Emacs will offer to add it. + It is usually a good idea to do so. diff -Nru lintian-2.93.0/tags/n/no-newline-at-end.tag lintian-2.89.0ubuntu1/tags/n/no-newline-at-end.tag --- lintian-2.93.0/tags/n/no-newline-at-end.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/no-newline-at-end.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: no-newline-at-end -Severity: warning -Check: debian/trailing-whitespace -Explanation: The named text file does not end with a newline. - . - Git considers it a whitespace error. Emacs will offer to add it. - It is usually a good idea to do so. diff -Nru lintian-2.93.0/tags/n/non-free-flash.desc lintian-2.89.0ubuntu1/tags/n/non-free-flash.desc --- lintian-2.93.0/tags/n/non-free-flash.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/non-free-flash.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: non-free-flash +Severity: error +Certainty: possible +Check: files/non-free +Info: The given Flash file has a filename which suggests that it may be + one of a number of known Flash files with non-free content. diff -Nru lintian-2.93.0/tags/n/non-free-flash.tag lintian-2.89.0ubuntu1/tags/n/non-free-flash.tag --- lintian-2.93.0/tags/n/non-free-flash.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/non-free-flash.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,5 +0,0 @@ -Tag: non-free-flash -Severity: error -Check: files/non-free -Explanation: The given Flash file has a filename which suggests that it may be - one of a number of known Flash files with non-free content. diff -Nru lintian-2.93.0/tags/n/no-nmu-in-changelog.desc lintian-2.89.0ubuntu1/tags/n/no-nmu-in-changelog.desc --- lintian-2.93.0/tags/n/no-nmu-in-changelog.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/no-nmu-in-changelog.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,15 @@ +Tag: no-nmu-in-changelog +Severity: warning +Check: nmu +Renamed-From: changelog-should-mention-nmu +Info: When you NMU a package, that fact should be mentioned on the first line + in the changelog entry. Use the words "NMU" or "Non-maintainer upload" + (case insensitive). + . + Maybe you didn't intend this upload to be a NMU, in that case, please + double-check that the most recent entry in the changelog is byte-for-byte + identical to the maintainer or one of the uploaders. If this is a local + package (not intended for Debian), you can suppress this warning by + putting "local" in the version number or "local package" on the first + line of the changelog entry. +Ref: devref 5.11.3 diff -Nru lintian-2.93.0/tags/n/no-nmu-in-changelog.tag lintian-2.89.0ubuntu1/tags/n/no-nmu-in-changelog.tag --- lintian-2.93.0/tags/n/no-nmu-in-changelog.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/no-nmu-in-changelog.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,15 +0,0 @@ -Tag: no-nmu-in-changelog -Severity: warning -Check: nmu -Renamed-From: changelog-should-mention-nmu -Explanation: When you NMU a package, that fact should be mentioned on the first line - in the changelog entry. Use the words "NMU" or "Non-maintainer upload" - (case insensitive). - . - Maybe you didn't intend this upload to be a NMU, in that case, please - double-check that the most recent entry in the changelog is byte-for-byte - identical to the maintainer or one of the uploaders. If this is a local - package (not intended for Debian), you can suppress this warning by - putting "local" in the version number or "local package" on the first - line of the changelog entry. -See-Also: devref 5.11.3 diff -Nru lintian-2.93.0/tags/n/non-multi-arch-lib-dir.desc lintian-2.89.0ubuntu1/tags/n/non-multi-arch-lib-dir.desc --- lintian-2.93.0/tags/n/non-multi-arch-lib-dir.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/non-multi-arch-lib-dir.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: non-multi-arch-lib-dir +Severity: warning +Check: files/hierarchy/standard +Info: The following library use an old path (like /lib64 or /lib32) + instead of using multi-arch path (like for instance + /lib/x86_64-linux-gnu/ or /lib/i386-linux-gnu/). +Ref: https://wiki.debian.org/Multiarch diff -Nru lintian-2.93.0/tags/n/non-multi-arch-lib-dir.tag lintian-2.89.0ubuntu1/tags/n/non-multi-arch-lib-dir.tag --- lintian-2.93.0/tags/n/non-multi-arch-lib-dir.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/non-multi-arch-lib-dir.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: non-multi-arch-lib-dir -Severity: warning -Check: files/hierarchy/standard -Explanation: The following library use an old path (like /lib64 or /lib32) - instead of using multi-arch path (like for instance - /lib/x86_64-linux-gnu/ or /lib/i386-linux-gnu/). -See-Also: https://wiki.debian.org/Multiarch diff -Nru lintian-2.93.0/tags/n/non-standard-apache2-configuration-name.desc lintian-2.89.0ubuntu1/tags/n/non-standard-apache2-configuration-name.desc --- lintian-2.93.0/tags/n/non-standard-apache2-configuration-name.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/non-standard-apache2-configuration-name.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: non-standard-apache2-configuration-name +Severity: warning +Check: apache2 +Info: The package appears to be a web application which is installing a + configuration file for the Apache2 HTTPD server. To avoid name clashes, any file + installed to /etc/apache2/{sites,conf}-available should match the binary package + name and must not start with local-. diff -Nru lintian-2.93.0/tags/n/non-standard-apache2-configuration-name.tag lintian-2.89.0ubuntu1/tags/n/non-standard-apache2-configuration-name.tag --- lintian-2.93.0/tags/n/non-standard-apache2-configuration-name.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/non-standard-apache2-configuration-name.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: non-standard-apache2-configuration-name -Severity: warning -Check: apache2 -Explanation: The package appears to be a web application which is installing a - configuration file for the Apache2 HTTPD server. To avoid name clashes, any file - installed to /etc/apache2/{sites,conf}-available should match the binary package - name and must not start with local-. diff -Nru lintian-2.93.0/tags/n/non-standard-apache2-module-package-name.desc lintian-2.89.0ubuntu1/tags/n/non-standard-apache2-module-package-name.desc --- lintian-2.93.0/tags/n/non-standard-apache2-module-package-name.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/non-standard-apache2-module-package-name.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: non-standard-apache2-module-package-name +Severity: warning +Check: apache2 +Info: The package appears to be an Apache2 HTTPD server module but it + does not follow the module naming scheme. Apache2 HTTPD modules should + be called libapache2-mod-name with mod-name being the + actual mod_name.so equivalent. diff -Nru lintian-2.93.0/tags/n/non-standard-apache2-module-package-name.tag lintian-2.89.0ubuntu1/tags/n/non-standard-apache2-module-package-name.tag --- lintian-2.93.0/tags/n/non-standard-apache2-module-package-name.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/non-standard-apache2-module-package-name.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: non-standard-apache2-module-package-name -Severity: warning -Check: apache2 -Explanation: The package appears to be an Apache2 HTTPD server module but it - does not follow the module naming scheme. Apache2 HTTPD modules should - be called libapache2-mod-name with mod-name being the - actual mod_name.so equivalent. diff -Nru lintian-2.93.0/tags/n/non-standard-dir-in-usr.desc lintian-2.89.0ubuntu1/tags/n/non-standard-dir-in-usr.desc --- lintian-2.93.0/tags/n/non-standard-dir-in-usr.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/non-standard-dir-in-usr.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: non-standard-dir-in-usr +Severity: warning +Check: files/hierarchy/standard +Info: The FHS says "No large software packages should use a direct + subdirectory under the /usr hierarchy". This package contains + a directory in /usr that is not mentioned in the Filesystem + Hierarchy Standard. +Ref: fhs theusrhierarchy diff -Nru lintian-2.93.0/tags/n/non-standard-dir-in-usr.tag lintian-2.89.0ubuntu1/tags/n/non-standard-dir-in-usr.tag --- lintian-2.93.0/tags/n/non-standard-dir-in-usr.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/non-standard-dir-in-usr.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: non-standard-dir-in-usr -Severity: warning -Check: files/hierarchy/standard -Explanation: The FHS says "No large software packages should use a direct - subdirectory under the /usr hierarchy". This package contains - a directory in /usr that is not mentioned in the Filesystem - Hierarchy Standard. -See-Also: fhs theusrhierarchy diff -Nru lintian-2.93.0/tags/n/non-standard-dir-in-var.desc lintian-2.89.0ubuntu1/tags/n/non-standard-dir-in-var.desc --- lintian-2.93.0/tags/n/non-standard-dir-in-var.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/non-standard-dir-in-var.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: non-standard-dir-in-var +Severity: error +Check: files/hierarchy/standard +Info: The FHS says "Applications should generally not add directories to + the top level of /var. Such directories should only be added + if they have some system-wide implication, and in consultation with the + FHS mailing list." +Ref: fhs thevarhierarchy diff -Nru lintian-2.93.0/tags/n/non-standard-dir-in-var.tag lintian-2.89.0ubuntu1/tags/n/non-standard-dir-in-var.tag --- lintian-2.93.0/tags/n/non-standard-dir-in-var.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/non-standard-dir-in-var.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: non-standard-dir-in-var -Severity: error -Check: files/hierarchy/standard -Explanation: The FHS says "Applications should generally not add directories to - the top level of /var. Such directories should only be added - if they have some system-wide implication, and in consultation with the - FHS mailing list." -See-Also: fhs thevarhierarchy diff -Nru lintian-2.93.0/tags/n/non-standard-dir-perm.desc lintian-2.89.0ubuntu1/tags/n/non-standard-dir-perm.desc --- lintian-2.93.0/tags/n/non-standard-dir-perm.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/non-standard-dir-perm.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: non-standard-dir-perm +Severity: warning +Certainty: possible +Check: files/permissions +Info: The directory has a mode different from 0755, and it's not one of the + known exceptions. +Ref: policy 10.9 diff -Nru lintian-2.93.0/tags/n/non-standard-dir-perm.tag lintian-2.89.0ubuntu1/tags/n/non-standard-dir-perm.tag --- lintian-2.93.0/tags/n/non-standard-dir-perm.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/non-standard-dir-perm.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: non-standard-dir-perm -Severity: warning -Check: files/permissions -Explanation: The directory has a mode different from 0755, and it's not one of the - known exceptions. -See-Also: policy 10.9 diff -Nru lintian-2.93.0/tags/n/non-standard-executable-perm.desc lintian-2.89.0ubuntu1/tags/n/non-standard-executable-perm.desc --- lintian-2.93.0/tags/n/non-standard-executable-perm.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/non-standard-executable-perm.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: non-standard-executable-perm +Severity: warning +Check: files/permissions +Info: Executables that are not setuid or setgid should always have a mode + of 0755. Since anyone can obtain the executable by downloading the + Debian package and extracting it, restricting access serves little + purpose. +Ref: policy 10.9 diff -Nru lintian-2.93.0/tags/n/non-standard-executable-perm.tag lintian-2.89.0ubuntu1/tags/n/non-standard-executable-perm.tag --- lintian-2.93.0/tags/n/non-standard-executable-perm.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/non-standard-executable-perm.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: non-standard-executable-perm -Severity: warning -Check: files/permissions -Explanation: Executables that are not setuid or setgid should always have a mode - of 0755. Since anyone can obtain the executable by downloading the - Debian package and extracting it, restricting access serves little - purpose. -See-Also: policy 10.9 diff -Nru lintian-2.93.0/tags/n/non-standard-file-perm.desc lintian-2.89.0ubuntu1/tags/n/non-standard-file-perm.desc --- lintian-2.93.0/tags/n/non-standard-file-perm.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/non-standard-file-perm.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: non-standard-file-perm +Severity: warning +Check: files/permissions +Info: The file has a mode different from 0644. In some cases this is + intentional, but in other cases this is a bug. +Ref: policy 10.9 diff -Nru lintian-2.93.0/tags/n/non-standard-file-permissions-for-etc-init.d-script.desc lintian-2.89.0ubuntu1/tags/n/non-standard-file-permissions-for-etc-init.d-script.desc --- lintian-2.93.0/tags/n/non-standard-file-permissions-for-etc-init.d-script.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/non-standard-file-permissions-for-etc-init.d-script.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,5 @@ +Tag: non-standard-file-permissions-for-etc-init.d-script +Severity: error +Check: files/init +Info: Usually, scripts in the /etc/init.d directory should have + mode 0755. diff -Nru lintian-2.93.0/tags/n/non-standard-file-permissions-for-etc-init.d-script.tag lintian-2.89.0ubuntu1/tags/n/non-standard-file-permissions-for-etc-init.d-script.tag --- lintian-2.93.0/tags/n/non-standard-file-permissions-for-etc-init.d-script.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/non-standard-file-permissions-for-etc-init.d-script.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,5 +0,0 @@ -Tag: non-standard-file-permissions-for-etc-init.d-script -Severity: error -Check: files/init -Explanation: Usually, scripts in the /etc/init.d directory should have - mode 0755. diff -Nru lintian-2.93.0/tags/n/non-standard-file-perm.tag lintian-2.89.0ubuntu1/tags/n/non-standard-file-perm.tag --- lintian-2.93.0/tags/n/non-standard-file-perm.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/non-standard-file-perm.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: non-standard-file-perm -Severity: warning -Check: files/permissions -Explanation: The file has a mode different from 0644. In some cases this is - intentional, but in other cases this is a bug. -See-Also: policy 10.9 diff -Nru lintian-2.93.0/tags/n/non-standard-game-executable-perm.desc lintian-2.89.0ubuntu1/tags/n/non-standard-game-executable-perm.desc --- lintian-2.93.0/tags/n/non-standard-game-executable-perm.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/non-standard-game-executable-perm.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: non-standard-game-executable-perm +Severity: warning +Check: files/permissions +Info: The file is owned by the games group but is not mode 2755. If a + game does not have to be setgid games, it should be owned by the root + group like any other executable. This executable is either owned by the + wrong group or is not setgid when it should be. +Ref: policy 11.11 diff -Nru lintian-2.93.0/tags/n/non-standard-game-executable-perm.tag lintian-2.89.0ubuntu1/tags/n/non-standard-game-executable-perm.tag --- lintian-2.93.0/tags/n/non-standard-game-executable-perm.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/non-standard-game-executable-perm.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: non-standard-game-executable-perm -Severity: warning -Check: files/permissions -Explanation: The file is owned by the games group but is not mode 2755. If a - game does not have to be setgid games, it should be owned by the root - group like any other executable. This executable is either owned by the - wrong group or is not setgid when it should be. -See-Also: policy 11.11 diff -Nru lintian-2.93.0/tags/n/non-standard-setuid-executable-perm.desc lintian-2.89.0ubuntu1/tags/n/non-standard-setuid-executable-perm.desc --- lintian-2.93.0/tags/n/non-standard-setuid-executable-perm.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/non-standard-setuid-executable-perm.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: non-standard-setuid-executable-perm +Severity: warning +Check: files/permissions +Info: The file is setuid or setgid and has a mode different from any of + 2755, 4755, 4754, or 6755. Any other permissions on setuid executables + is probably a bug. In particular, removing root write privileges serves + no purpose, group-writable setuid or setgid executables are probably bad + ideas, and setgid executables that are not world-executable serve little + purpose. +Ref: policy 10.9 diff -Nru lintian-2.93.0/tags/n/non-standard-setuid-executable-perm.tag lintian-2.89.0ubuntu1/tags/n/non-standard-setuid-executable-perm.tag --- lintian-2.93.0/tags/n/non-standard-setuid-executable-perm.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/non-standard-setuid-executable-perm.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,10 +0,0 @@ -Tag: non-standard-setuid-executable-perm -Severity: warning -Check: files/permissions -Explanation: The file is setuid or setgid and has a mode different from any of - 2755, 4755, 4754, or 6755. Any other permissions on setuid executables - is probably a bug. In particular, removing root write privileges serves - no purpose, group-writable setuid or setgid executables are probably bad - ideas, and setgid executables that are not world-executable serve little - purpose. -See-Also: policy 10.9 diff -Nru lintian-2.93.0/tags/n/non-standard-toplevel-dir.desc lintian-2.89.0ubuntu1/tags/n/non-standard-toplevel-dir.desc --- lintian-2.93.0/tags/n/non-standard-toplevel-dir.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/non-standard-toplevel-dir.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: non-standard-toplevel-dir +Severity: error +Check: files/hierarchy/standard +Info: The Filesystem Hierarchy Standard forbids the installation of new + files or directories in the root directory. +Ref: fhs therootfilesystem diff -Nru lintian-2.93.0/tags/n/non-standard-toplevel-dir.tag lintian-2.89.0ubuntu1/tags/n/non-standard-toplevel-dir.tag --- lintian-2.93.0/tags/n/non-standard-toplevel-dir.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/non-standard-toplevel-dir.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: non-standard-toplevel-dir -Severity: error -Check: files/hierarchy/standard -Explanation: The Filesystem Hierarchy Standard forbids the installation of new - files or directories in the root directory. -See-Also: fhs therootfilesystem diff -Nru lintian-2.93.0/tags/n/non-virtual-facility-in-initd-script.desc lintian-2.89.0ubuntu1/tags/n/non-virtual-facility-in-initd-script.desc --- lintian-2.93.0/tags/n/non-virtual-facility-in-initd-script.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/non-virtual-facility-in-initd-script.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,15 @@ +Tag: non-virtual-facility-in-initd-script +Severity: error +Certainty: possible +Check: init.d +Renamed-From: init.d-script-should-depend-on-virtual-facility +Info: The given /etc/init.d script depends on a non-virtual + facility that should probably be replaced by a virtual facility. For + example, init scripts should depend on the virtual facility + $network rather than the facility networking, and the + virtual facility $named rather than the specific facility + bind9. + . + Properly using virtual facilities allows multiple implementations of the + same facility and accommodates systems where that specific facility may + not be enough to provide everything the script expects. diff -Nru lintian-2.93.0/tags/n/non-virtual-facility-in-initd-script.tag lintian-2.89.0ubuntu1/tags/n/non-virtual-facility-in-initd-script.tag --- lintian-2.93.0/tags/n/non-virtual-facility-in-initd-script.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/non-virtual-facility-in-initd-script.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,14 +0,0 @@ -Tag: non-virtual-facility-in-initd-script -Severity: error -Check: init.d -Renamed-From: init.d-script-should-depend-on-virtual-facility -Explanation: The given /etc/init.d script depends on a non-virtual - facility that should probably be replaced by a virtual facility. For - example, init scripts should depend on the virtual facility - $network rather than the facility networking, and the - virtual facility $named rather than the specific facility - bind9. - . - Properly using virtual facilities allows multiple implementations of the - same facility and accommodates systems where that specific facility may - not be enough to provide everything the script expects. diff -Nru lintian-2.93.0/tags/n/non-wm-in-windowmanager-menu-section.desc lintian-2.89.0ubuntu1/tags/n/non-wm-in-windowmanager-menu-section.desc --- lintian-2.93.0/tags/n/non-wm-in-windowmanager-menu-section.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/non-wm-in-windowmanager-menu-section.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: non-wm-in-windowmanager-menu-section +Severity: error +Check: menu-format +Info: The menu item is in the Window Manager section but does not needs=wm. + Either it is a window manager and it should needs=wm, either it isn't and + then it must be moved in another section. diff -Nru lintian-2.93.0/tags/n/non-wm-in-windowmanager-menu-section.tag lintian-2.89.0ubuntu1/tags/n/non-wm-in-windowmanager-menu-section.tag --- lintian-2.93.0/tags/n/non-wm-in-windowmanager-menu-section.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/non-wm-in-windowmanager-menu-section.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: non-wm-in-windowmanager-menu-section -Severity: error -Check: menu-format -Explanation: The menu item is in the Window Manager section but does not needs=wm. - Either it is a window manager and it should needs=wm, either it isn't and - then it must be moved in another section. diff -Nru lintian-2.93.0/tags/n/non-wm-module-in-wm-modules-menu-section.desc lintian-2.89.0ubuntu1/tags/n/non-wm-module-in-wm-modules-menu-section.desc --- lintian-2.93.0/tags/n/non-wm-module-in-wm-modules-menu-section.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/non-wm-module-in-wm-modules-menu-section.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: non-wm-module-in-wm-modules-menu-section +Severity: error +Check: menu-format +Info: The menu item is in the FVWM Modules or Window Maker section but + does not declare that it needs a specific window manager (using the needs + key in the menu file). Modules for Fvwm should have needs="fvwmmodule". + Modules for WindowMaker should have needs="wmmaker". diff -Nru lintian-2.93.0/tags/n/non-wm-module-in-wm-modules-menu-section.tag lintian-2.89.0ubuntu1/tags/n/non-wm-module-in-wm-modules-menu-section.tag --- lintian-2.93.0/tags/n/non-wm-module-in-wm-modules-menu-section.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/non-wm-module-in-wm-modules-menu-section.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: non-wm-module-in-wm-modules-menu-section -Severity: error -Check: menu-format -Explanation: The menu item is in the FVWM Modules or Window Maker section but - does not declare that it needs a specific window manager (using the needs - key in the menu file). Modules for Fvwm should have needs="fvwmmodule". - Modules for WindowMaker should have needs="wmmaker". diff -Nru lintian-2.93.0/tags/n/no-op-testsuite.desc lintian-2.89.0ubuntu1/tags/n/no-op-testsuite.desc --- lintian-2.93.0/tags/n/no-op-testsuite.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/no-op-testsuite.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,15 @@ +Tag: no-op-testsuite +Severity: warning +Check: testsuite +Info: This package declares a single autopkgtest which will always + pass as it uses a "no-op" command such as /bin/true. + . + As the results of autopkgtests influence migration from unstable + to testing this is undesirable and could be even considered an + unfair or unwarranted "advantage". Installability of packages is + better tested with piuparts which is also used to influence + testing migration. + . + Please update your autopkgtest to actually test the binary package(s) + when installed. +Ref: https://ci.debian.net/doc/ diff -Nru lintian-2.93.0/tags/n/no-op-testsuite.tag lintian-2.89.0ubuntu1/tags/n/no-op-testsuite.tag --- lintian-2.93.0/tags/n/no-op-testsuite.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/no-op-testsuite.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,15 +0,0 @@ -Tag: no-op-testsuite -Severity: warning -Check: testsuite -Explanation: This package declares a single autopkgtest which will always - pass as it uses a "no-op" command such as /bin/true. - . - As the results of autopkgtests influence migration from unstable - to testing this is undesirable and could be even considered an - unfair or unwarranted "advantage". Installability of packages is - better tested with piuparts which is also used to influence - testing migration. - . - Please update your autopkgtest to actually test the binary package(s) - when installed. -See-Also: https://ci.debian.net/doc/ diff -Nru lintian-2.93.0/tags/n/no-phrase.desc lintian-2.89.0ubuntu1/tags/n/no-phrase.desc --- lintian-2.93.0/tags/n/no-phrase.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/no-phrase.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,13 @@ +Tag: no-phrase +Severity: error +Check: fields/mail-address +Renamed-From: + maintainer-name-missing + changed-by-name-missing +Info: The named contact includes an email address, but no name + (which email folks call the phrase). + . + The contact information must contain both a name and a mail address. +Ref: policy 5.6.2, + policy 5.6.3, + policy 5.6.4 diff -Nru lintian-2.93.0/tags/n/no-phrase.tag lintian-2.89.0ubuntu1/tags/n/no-phrase.tag --- lintian-2.93.0/tags/n/no-phrase.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/no-phrase.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,13 +0,0 @@ -Tag: no-phrase -Severity: error -Check: fields/mail-address -Renamed-From: - maintainer-name-missing - changed-by-name-missing -Explanation: The named contact includes an email address, but no name - (which email folks call the *phrase*). - . - The contact information must contain both a name and a mail address. -See-Also: policy 5.6.2, - policy 5.6.3, - policy 5.6.4 diff -Nru lintian-2.93.0/tags/n/no-qa-in-changelog.desc lintian-2.89.0ubuntu1/tags/n/no-qa-in-changelog.desc --- lintian-2.93.0/tags/n/no-qa-in-changelog.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/no-qa-in-changelog.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: no-qa-in-changelog +Severity: warning +Check: nmu +Renamed-From: changelog-should-mention-qa +Info: If this upload is to orphan this package, please mention this fact on + the first line of the changelog. If this is a QA upload, please mention "QA + (group) upload" there. diff -Nru lintian-2.93.0/tags/n/no-qa-in-changelog.tag lintian-2.89.0ubuntu1/tags/n/no-qa-in-changelog.tag --- lintian-2.93.0/tags/n/no-qa-in-changelog.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/no-qa-in-changelog.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: no-qa-in-changelog -Severity: warning -Check: nmu -Renamed-From: changelog-should-mention-qa -Explanation: If this upload is to orphan this package, please mention this fact on - the first line of the changelog. If this is a QA upload, please mention "QA - (group) upload" there. diff -Nru lintian-2.93.0/tags/n/no-shlibs.desc lintian-2.89.0ubuntu1/tags/n/no-shlibs.desc --- lintian-2.93.0/tags/n/no-shlibs.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/no-shlibs.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: no-shlibs +Severity: error +Certainty: possible +Check: shared-libs +Renamed-From: no-shlibs-control-file +Info: Although the package includes a shared library, the package does not + have a shlibs control file. If this is intentional, please override this + error. +Ref: policy 8.6 diff -Nru lintian-2.93.0/tags/n/no-shlibs.tag lintian-2.89.0ubuntu1/tags/n/no-shlibs.tag --- lintian-2.93.0/tags/n/no-shlibs.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/no-shlibs.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: no-shlibs -Severity: error -Check: shared-libs -Renamed-From: no-shlibs-control-file -Explanation: Although the package includes a shared library, the package does not - have a shlibs control file. If this is intentional, please override this - error. -See-Also: policy 8.6 diff -Nru lintian-2.93.0/tags/n/no-strong-digests-in-dsc.desc lintian-2.89.0ubuntu1/tags/n/no-strong-digests-in-dsc.desc --- lintian-2.93.0/tags/n/no-strong-digests-in-dsc.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/no-strong-digests-in-dsc.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,14 @@ +Tag: no-strong-digests-in-dsc +Severity: error +Check: fields/checksums +Info: This .dsc file contains no Checksum-Sha256 field and hence only + weak digests. + . + This issue will only show up for source packages built with + dpkg-source before 1.14.17 (March 2008) and hence will probably never + show up when you run Lintian locally but only on + https://lintian.debian.org/ for source packages in the archive. + . + Accordingly it can be fixed by simply rebuilding the source package + with a more recent dpkg-source version, i.e. by uploading a new + Debian release of the package. diff -Nru lintian-2.93.0/tags/n/no-strong-digests-in-dsc.tag lintian-2.89.0ubuntu1/tags/n/no-strong-digests-in-dsc.tag --- lintian-2.93.0/tags/n/no-strong-digests-in-dsc.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/no-strong-digests-in-dsc.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,14 +0,0 @@ -Tag: no-strong-digests-in-dsc -Severity: error -Check: fields/checksums -Explanation: This .dsc file contains no Checksum-Sha256 field and hence only - weak digests. - . - This issue will only show up for source packages built with - dpkg-source before 1.14.17 (March 2008) and hence will probably never - show up when you run Lintian locally but only on - https://lintian.debian.org/ for source packages in the archive. - . - Accordingly it can be fixed by simply rebuilding the source package - with a more recent dpkg-source version, i.e. by uploading a new - Debian release of the package. diff -Nru lintian-2.93.0/tags/n/no-symbols-control-file.desc lintian-2.89.0ubuntu1/tags/n/no-symbols-control-file.desc --- lintian-2.93.0/tags/n/no-symbols-control-file.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/no-symbols-control-file.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: no-symbols-control-file +Severity: info +Check: shared-libs +Info: Although the package includes a shared library, the package does not + have a symbols control file. + . + dpkg can use symbols files in order to generate more accurate library + dependencies for applications, based on the symbols from the library that + are actually used by the application. +Ref: dpkg-gensymbols(1), https://wiki.debian.org/UsingSymbolsFiles diff -Nru lintian-2.93.0/tags/n/no-symbols-control-file.tag lintian-2.89.0ubuntu1/tags/n/no-symbols-control-file.tag --- lintian-2.93.0/tags/n/no-symbols-control-file.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/no-symbols-control-file.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,10 +0,0 @@ -Tag: no-symbols-control-file -Severity: info -Check: shared-libs -Explanation: Although the package includes a shared library, the package does not - have a symbols control file. - . - dpkg can use symbols files in order to generate more accurate library - dependencies for applications, based on the symbols from the library that - are actually used by the application. -See-Also: dpkg-gensymbols(1), https://wiki.debian.org/UsingSymbolsFiles diff -Nru lintian-2.93.0/tags/n/not-allowed-control-file.desc lintian-2.89.0ubuntu1/tags/n/not-allowed-control-file.desc --- lintian-2.93.0/tags/n/not-allowed-control-file.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/not-allowed-control-file.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: not-allowed-control-file +Severity: error +Check: control-files +Info: The package contains a control file that is not allowed in this + type of package. Some control files are only allowed in either .deb + or .udeb packages and must not be included in packages of the other + type. You should probably just remove the file. diff -Nru lintian-2.93.0/tags/n/not-allowed-control-file.tag lintian-2.89.0ubuntu1/tags/n/not-allowed-control-file.tag --- lintian-2.93.0/tags/n/not-allowed-control-file.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/not-allowed-control-file.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: not-allowed-control-file -Severity: error -Check: control-files -Explanation: The package contains a control file that is not allowed in this - type of package. Some control files are only allowed in either .deb - or .udeb packages and must not be included in packages of the other - type. You should probably just remove the file. diff -Nru lintian-2.93.0/tags/n/not-binnmuable-all-depends-any.desc lintian-2.89.0ubuntu1/tags/n/not-binnmuable-all-depends-any.desc --- lintian-2.93.0/tags/n/not-binnmuable-all-depends-any.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/not-binnmuable-all-depends-any.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,14 @@ +Tag: not-binnmuable-all-depends-any +Severity: error +Check: debian/version-substvars +Info: The package is not safely binNMUable because an arch:all package + depends on an arch:any package with a strict (= ${source:Version}), or + similar, relationship. + . + It is not possible for arch:all packages to depend so strictly on + arch:any packages while having the package binNMUable, so please use + one of these, whichever is more appropriate: + . + Depends: arch_any (>= ${source:Version}) + Depends: arch_any (>= ${source:Version}), + arch_any (<< ${source:Version}.1~) diff -Nru lintian-2.93.0/tags/n/not-binnmuable-all-depends-any.tag lintian-2.89.0ubuntu1/tags/n/not-binnmuable-all-depends-any.tag --- lintian-2.93.0/tags/n/not-binnmuable-all-depends-any.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/not-binnmuable-all-depends-any.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,14 +0,0 @@ -Tag: not-binnmuable-all-depends-any -Severity: error -Check: debian/version-substvars -Explanation: The package is not safely binNMUable because an arch:all package - depends on an arch:any package with a strict (= ${source:Version}), or - similar, relationship. - . - It is not possible for arch:all packages to depend so strictly on - arch:any packages while having the package binNMUable, so please use - one of these, whichever is more appropriate: - . - Depends: arch_any (>= ${source:Version}) - Depends: arch_any (>= ${source:Version}), - arch_any (<< ${source:Version}.1~) diff -Nru lintian-2.93.0/tags/n/not-binnmuable-any-depends-all.desc lintian-2.89.0ubuntu1/tags/n/not-binnmuable-any-depends-all.desc --- lintian-2.93.0/tags/n/not-binnmuable-any-depends-all.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/not-binnmuable-any-depends-all.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: not-binnmuable-any-depends-all +Severity: error +Check: debian/version-substvars +Info: The package is not safely binNMUable because an arch:any package + depends on an arch:all package with a (= ${binary:Version}) + relationship. Please use (= ${source:Version}) instead. + . + Note this is also triggered if the dependency uses (>= ${var}), + since that has the same issue. diff -Nru lintian-2.93.0/tags/n/not-binnmuable-any-depends-all.tag lintian-2.89.0ubuntu1/tags/n/not-binnmuable-any-depends-all.tag --- lintian-2.93.0/tags/n/not-binnmuable-any-depends-all.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/not-binnmuable-any-depends-all.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: not-binnmuable-any-depends-all -Severity: error -Check: debian/version-substvars -Explanation: The package is not safely binNMUable because an arch:any package - depends on an arch:all package with a (= ${binary:Version}) - relationship. Please use (= ${source:Version}) instead. - . - Note this is also triggered if the dependency uses (>= ${var}), - since that has the same issue. diff -Nru lintian-2.93.0/tags/n/not-binnmuable-any-depends-any.desc lintian-2.89.0ubuntu1/tags/n/not-binnmuable-any-depends-any.desc --- lintian-2.93.0/tags/n/not-binnmuable-any-depends-any.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/not-binnmuable-any-depends-any.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: not-binnmuable-any-depends-any +Severity: error +Check: debian/version-substvars +Info: The package is not safely binNMUable because an arch:any package + depends on another arch:any package with a (= ${source:Version}) + relationship. Please use (= ${binary:Version}) instead. diff -Nru lintian-2.93.0/tags/n/not-binnmuable-any-depends-any.tag lintian-2.89.0ubuntu1/tags/n/not-binnmuable-any-depends-any.tag --- lintian-2.93.0/tags/n/not-binnmuable-any-depends-any.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/not-binnmuable-any-depends-any.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: not-binnmuable-any-depends-any -Severity: error -Check: debian/version-substvars -Explanation: The package is not safely binNMUable because an arch:any package - depends on another arch:any package with a (= ${source:Version}) - relationship. Please use (= ${binary:Version}) instead. diff -Nru lintian-2.93.0/tags/n/no-template-description.desc lintian-2.89.0ubuntu1/tags/n/no-template-description.desc --- lintian-2.93.0/tags/n/no-template-description.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/no-template-description.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,5 @@ +Tag: no-template-description +Severity: error +Check: debian/debconf +Info: The templates file contains a template without a "Description:" field. +Ref: debconf-spec 3, debconf-devel(7) diff -Nru lintian-2.93.0/tags/n/no-template-description.tag lintian-2.89.0ubuntu1/tags/n/no-template-description.tag --- lintian-2.93.0/tags/n/no-template-description.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/no-template-description.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,5 +0,0 @@ -Tag: no-template-description -Severity: error -Check: debian/debconf -Explanation: The templates file contains a template without a "Description:" field. -See-Also: debconf-spec 3, debconf-devel(7) diff -Nru lintian-2.93.0/tags/n/no-template-name.desc lintian-2.89.0ubuntu1/tags/n/no-template-name.desc --- lintian-2.93.0/tags/n/no-template-name.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/no-template-name.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,4 @@ +Tag: no-template-name +Severity: error +Check: debian/debconf +Info: The templates file contains a template without a "Template:" field. diff -Nru lintian-2.93.0/tags/n/no-template-name.tag lintian-2.89.0ubuntu1/tags/n/no-template-name.tag --- lintian-2.93.0/tags/n/no-template-name.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/no-template-name.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,4 +0,0 @@ -Tag: no-template-name -Severity: error -Check: debian/debconf -Explanation: The templates file contains a template without a "Template:" field. diff -Nru lintian-2.93.0/tags/n/no-template-type.desc lintian-2.89.0ubuntu1/tags/n/no-template-type.desc --- lintian-2.93.0/tags/n/no-template-type.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/no-template-type.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,4 @@ +Tag: no-template-type +Severity: error +Check: debian/debconf +Info: The templates file contains a template without a "Type:" field. diff -Nru lintian-2.93.0/tags/n/no-template-type.tag lintian-2.89.0ubuntu1/tags/n/no-template-type.tag --- lintian-2.93.0/tags/n/no-template-type.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/no-template-type.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,4 +0,0 @@ -Tag: no-template-type -Severity: error -Check: debian/debconf -Explanation: The templates file contains a template without a "Type:" field. diff -Nru lintian-2.93.0/tags/n/no-tests.desc lintian-2.89.0ubuntu1/tags/n/no-tests.desc --- lintian-2.93.0/tags/n/no-tests.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/no-tests.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: no-tests +Severity: warning +Check: testsuite +Info: The autopackage test suite does not define any tests via + either the Tests field or the Test-Command + field. +Ref: https://salsa.debian.org/ci-team/autopkgtest/tree/master/doc/README.package-tests.rst diff -Nru lintian-2.93.0/tags/n/no-tests.tag lintian-2.89.0ubuntu1/tags/n/no-tests.tag --- lintian-2.93.0/tags/n/no-tests.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/no-tests.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: no-tests -Severity: warning -Check: testsuite -Explanation: The autopackage test suite does not define any tests via - either the Tests field or the Test-Command - field. -See-Also: https://salsa.debian.org/ci-team/autopkgtest/tree/master/doc/README.package-tests.rst diff -Nru lintian-2.93.0/tags/n/not-using-po-debconf.desc lintian-2.89.0ubuntu1/tags/n/not-using-po-debconf.desc --- lintian-2.93.0/tags/n/not-using-po-debconf.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/not-using-po-debconf.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: not-using-po-debconf +Severity: error +Check: debian/po-debconf +Info: This package seems to be using debconf templates, but it does not + use po-debconf to make translations possible (debian/po doesn't + exist). Debian Policy requires that all packages using debconf use a + gettext-based translation system. +Ref: policy 3.9.1 diff -Nru lintian-2.93.0/tags/n/not-using-po-debconf.tag lintian-2.89.0ubuntu1/tags/n/not-using-po-debconf.tag --- lintian-2.93.0/tags/n/not-using-po-debconf.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/n/not-using-po-debconf.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: not-using-po-debconf -Severity: error -Check: debian/po-debconf -Explanation: This package seems to be using debconf templates, but it does not - use po-debconf to make translations possible (debian/po doesn't - exist). Debian Policy requires that all packages using debconf use a - gettext-based translation system. -See-Also: policy 3.9.1 diff -Nru lintian-2.93.0/tags/o/obsolete-command-in-modprobe.d-file.desc lintian-2.89.0ubuntu1/tags/o/obsolete-command-in-modprobe.d-file.desc --- lintian-2.93.0/tags/o/obsolete-command-in-modprobe.d-file.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/o/obsolete-command-in-modprobe.d-file.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: obsolete-command-in-modprobe.d-file +Severity: warning +Check: modprobe +Info: Use of 'install' and 'remove' commands in module files in + /etc/modprobe.d and /etc/modules-load.d is + deprecated and should be replaced with 'softdep' commands. diff -Nru lintian-2.93.0/tags/o/obsolete-command-in-modprobe.d-file.tag lintian-2.89.0ubuntu1/tags/o/obsolete-command-in-modprobe.d-file.tag --- lintian-2.93.0/tags/o/obsolete-command-in-modprobe.d-file.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/o/obsolete-command-in-modprobe.d-file.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: obsolete-command-in-modprobe.d-file -Severity: warning -Check: modprobe -Explanation: Use of 'install' and 'remove' commands in module files in - /etc/modprobe.d and /etc/modules-load.d is - deprecated and should be replaced with 'softdep' commands. diff -Nru lintian-2.93.0/tags/o/obsolete-comments-style-in-php-ini.desc lintian-2.89.0ubuntu1/tags/o/obsolete-comments-style-in-php-ini.desc --- lintian-2.93.0/tags/o/obsolete-comments-style-in-php-ini.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/o/obsolete-comments-style-in-php-ini.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: obsolete-comments-style-in-php-ini +Severity: warning +Check: languages/php +Info: This package ships a .ini file used to configure php but + it has comments using the old-style comment separator #. + Instead, the ; separator should be used. + . + Since version 5.3, the PHP interpreter warns about the use of the + old style of comment separator. diff -Nru lintian-2.93.0/tags/o/obsolete-comments-style-in-php-ini.tag lintian-2.89.0ubuntu1/tags/o/obsolete-comments-style-in-php-ini.tag --- lintian-2.93.0/tags/o/obsolete-comments-style-in-php-ini.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/o/obsolete-comments-style-in-php-ini.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: obsolete-comments-style-in-php-ini -Severity: warning -Check: languages/php -Explanation: This package ships a .ini file used to configure php but - it has comments using the old-style comment separator #. - Instead, the ; separator should be used. - . - Since version 5.3, the PHP interpreter warns about the use of the - old style of comment separator. diff -Nru lintian-2.93.0/tags/o/obsolete-crypt-alias.desc lintian-2.89.0ubuntu1/tags/o/obsolete-crypt-alias.desc --- lintian-2.93.0/tags/o/obsolete-crypt-alias.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/o/obsolete-crypt-alias.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,16 @@ +Tag: obsolete-crypt-alias +Severity: error +Certainty: possible +Check: binaries +Info: The listed ELF binary appears to use the C library function + fcrypt, which is a less-portable alias for crypt. + Programs that use this function cannot be linked against the + libcrypt.so provided by glibc 2.28 and higher. + . + The program should be changed to use crypt instead. + . + A false positive for this check is possible if the binary expects + the definition of fcrypt to come from some shared library + other than libcrypt.so, and that shared library + defines this function to do something other than hash passphrases. + If this is the case it is appropriate to override this tag. diff -Nru lintian-2.93.0/tags/o/obsolete-crypt-alias.tag lintian-2.89.0ubuntu1/tags/o/obsolete-crypt-alias.tag --- lintian-2.93.0/tags/o/obsolete-crypt-alias.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/o/obsolete-crypt-alias.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,15 +0,0 @@ -Tag: obsolete-crypt-alias -Severity: error -Check: binaries -Explanation: The listed ELF binary appears to use the C library function - fcrypt, which is a less-portable alias for crypt. - Programs that use this function cannot be linked against the - libcrypt.so provided by glibc 2.28 and higher. - . - The program should be changed to use crypt instead. - . - A false positive for this check is possible if the binary expects - the definition of fcrypt to come from some shared library - other than libcrypt.so, *and* that shared library - defines this function to do something other than hash passphrases. - If this is the case it is appropriate to override this tag. diff -Nru lintian-2.93.0/tags/o/obsolete-des-encryption.desc lintian-2.89.0ubuntu1/tags/o/obsolete-des-encryption.desc --- lintian-2.93.0/tags/o/obsolete-des-encryption.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/o/obsolete-des-encryption.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,29 @@ +Tag: obsolete-des-encryption +Severity: error +Certainty: possible +Check: binaries +Info: The listed ELF binary appears to use a C library function that + performs DES encryption and/or decryption (encrypt, + encrypt_r, setkey, and/or setkey_r). + The DES block cipher can be broken by brute force on modern hardware, + which makes any use of these functions insecure. Also, programs that + use these functions cannot be linked against the libcrypt.so + provided by glibc 2.28 and higher. + . + The program will need to be revised to use modern cryptographic + primitives and protocols. Depending on how the program uses these + functions, it may be necessary to continue using DES under some + circumstances (e.g. for protocol compatibility, or to retain the + ability to decrypt old data on disk) but this should be done using + the DES functions in a modern cryptographic library + (e.g. libgcrypt). + . + This is almost certainly an upstream bug, and should be addressed + in coordination with the upstream maintainers of the software. + . + A false positive for this check is possible if the binary expects the + definition of encrypt, encrypt_r, setkey, + and/or setkey_r to come from some shared library other than + libcrypt.so, and that shared library defines these + functions to do something other than perform DES encryption. If this + is the case it is appropriate to override this tag. diff -Nru lintian-2.93.0/tags/o/obsolete-des-encryption.tag lintian-2.89.0ubuntu1/tags/o/obsolete-des-encryption.tag --- lintian-2.93.0/tags/o/obsolete-des-encryption.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/o/obsolete-des-encryption.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,28 +0,0 @@ -Tag: obsolete-des-encryption -Severity: error -Check: binaries -Explanation: The listed ELF binary appears to use a C library function that - performs DES encryption and/or decryption (encrypt, - encrypt_r, setkey, and/or setkey_r). - The DES block cipher can be broken by brute force on modern hardware, - which makes any use of these functions insecure. Also, programs that - use these functions cannot be linked against the libcrypt.so - provided by glibc 2.28 and higher. - . - The program will need to be revised to use modern cryptographic - primitives and protocols. Depending on how the program uses these - functions, it may be necessary to continue using DES under some - circumstances (e.g. for protocol compatibility, or to retain the - ability to decrypt old data on disk) but this should be done using - the DES functions in a modern cryptographic *library* - (e.g. libgcrypt). - . - This is almost certainly an upstream bug, and should be addressed - in coordination with the upstream maintainers of the software. - . - A false positive for this check is possible if the binary expects the - definition of encrypt, encrypt_r, setkey, - and/or setkey_r to come from some shared library other than - libcrypt.so, *and* that shared library defines these - functions to do something other than perform DES encryption. If this - is the case it is appropriate to override this tag. diff -Nru lintian-2.93.0/tags/o/obsolete-field-in-dep5-copyright.desc lintian-2.89.0ubuntu1/tags/o/obsolete-field-in-dep5-copyright.desc --- lintian-2.93.0/tags/o/obsolete-field-in-dep5-copyright.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/o/obsolete-field-in-dep5-copyright.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,13 @@ +Tag: obsolete-field-in-dep5-copyright +Severity: warning +Certainty: possible +Check: debian/copyright/dep5 +Ref: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ +Info: The machine-readable copyright file uses a field, that used to be defined + by the specification, but has been renamed since then. + . + Please use Format instead of Format-Specification. + . + Please use Upstream-Contact instead of Contact, Maintainer or Upstream-Maintainer. + . + Please use Upstream-Name instead of Name. diff -Nru lintian-2.93.0/tags/o/obsolete-field-in-dep5-copyright.tag lintian-2.89.0ubuntu1/tags/o/obsolete-field-in-dep5-copyright.tag --- lintian-2.93.0/tags/o/obsolete-field-in-dep5-copyright.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/o/obsolete-field-in-dep5-copyright.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,12 +0,0 @@ -Tag: obsolete-field-in-dep5-copyright -Severity: warning -Check: debian/copyright/dep5 -See-Also: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ -Explanation: The machine-readable copyright file uses a field, that used to be defined - by the specification, but has been renamed since then. - . - Please use Format instead of Format-Specification. - . - Please use Upstream-Contact instead of Contact, Maintainer or Upstream-Maintainer. - . - Please use Upstream-Name instead of Name. diff -Nru lintian-2.93.0/tags/o/obsolete-relation-form.desc lintian-2.89.0ubuntu1/tags/o/obsolete-relation-form.desc --- lintian-2.93.0/tags/o/obsolete-relation-form.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/o/obsolete-relation-form.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: obsolete-relation-form +Ref: policy 7.1 +Severity: warning +Check: fields/package-relations +Info: The forms "<" and ">" mean "<=" and ">=", not "<<" + and ">>" as one might expect. For that reason these forms are + obsolete, and should not be used in new packages. Use the longer forms + instead. diff -Nru lintian-2.93.0/tags/o/obsolete-relation-form-in-source.desc lintian-2.89.0ubuntu1/tags/o/obsolete-relation-form-in-source.desc --- lintian-2.93.0/tags/o/obsolete-relation-form-in-source.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/o/obsolete-relation-form-in-source.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: obsolete-relation-form-in-source +Ref: policy 7.1 +Severity: error +Check: debian/control +Info: The forms "<" and ">" mean "<=" and ">=", not "<<" + and ">>" as one might expect. These forms were marked obsolete and + must no longer be used. Use the longer forms instead. diff -Nru lintian-2.93.0/tags/o/obsolete-relation-form-in-source.tag lintian-2.89.0ubuntu1/tags/o/obsolete-relation-form-in-source.tag --- lintian-2.93.0/tags/o/obsolete-relation-form-in-source.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/o/obsolete-relation-form-in-source.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: obsolete-relation-form-in-source -See-Also: policy 7.1 -Severity: error -Check: debian/control -Explanation: The forms "<" and ">" mean "<=" and ">=", not "<<" - and ">>" as one might expect. These forms were marked obsolete and - must no longer be used. Use the longer forms instead. diff -Nru lintian-2.93.0/tags/o/obsolete-relation-form.tag lintian-2.89.0ubuntu1/tags/o/obsolete-relation-form.tag --- lintian-2.93.0/tags/o/obsolete-relation-form.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/o/obsolete-relation-form.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: obsolete-relation-form -See-Also: policy 7.1 -Severity: warning -Check: fields/package-relations -Explanation: The forms "<" and ">" mean "<=" and ">=", not "<<" - and ">>" as one might expect. For that reason these forms are - obsolete, and should not be used in new packages. Use the longer forms - instead. diff -Nru lintian-2.93.0/tags/o/obsolete-runtime-tests-restriction.desc lintian-2.89.0ubuntu1/tags/o/obsolete-runtime-tests-restriction.desc --- lintian-2.93.0/tags/o/obsolete-runtime-tests-restriction.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/o/obsolete-runtime-tests-restriction.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: obsolete-runtime-tests-restriction +Severity: warning +Check: testsuite +Info: A paragraph in debian/tests/control mentions an obsolete + value for the Restrictions field. Though still allowed, this will + become unsupported in the future and the whole paragraph will be + ignored. +Ref: https://salsa.debian.org/ci-team/autopkgtest/tree/master/doc/README.package-tests.rst diff -Nru lintian-2.93.0/tags/o/obsolete-runtime-tests-restriction.tag lintian-2.89.0ubuntu1/tags/o/obsolete-runtime-tests-restriction.tag --- lintian-2.93.0/tags/o/obsolete-runtime-tests-restriction.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/o/obsolete-runtime-tests-restriction.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: obsolete-runtime-tests-restriction -Severity: warning -Check: testsuite -Explanation: A paragraph in debian/tests/control mentions an obsolete - value for the Restrictions field. Though still allowed, this will - become unsupported in the future and the whole paragraph will be - ignored. -See-Also: https://salsa.debian.org/ci-team/autopkgtest/tree/master/doc/README.package-tests.rst diff -Nru lintian-2.93.0/tags/o/obsolete-url-in-packaging.desc lintian-2.89.0ubuntu1/tags/o/obsolete-url-in-packaging.desc --- lintian-2.93.0/tags/o/obsolete-url-in-packaging.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/o/obsolete-url-in-packaging.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,14 @@ +Tag: obsolete-url-in-packaging +Severity: warning +Check: obsolete-sites +Info: One of the package's packaging files points to a website or code + hoster known to have frozen contents, to be closed soon or to have + already closed. + . + Please look for the new upstream home of the package and update the + packaging accordingly. + . + Sites previously hosted on code.google.com and codeplex.com were offered a + migration to github.com, sites previously on gitorious.org were offered a + migration to gitlab.com, sites previously hosted on fedorahosted.org were + offered a migration to pagure.io. You might want to look there first. diff -Nru lintian-2.93.0/tags/o/obsolete-url-in-packaging.tag lintian-2.89.0ubuntu1/tags/o/obsolete-url-in-packaging.tag --- lintian-2.93.0/tags/o/obsolete-url-in-packaging.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/o/obsolete-url-in-packaging.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,14 +0,0 @@ -Tag: obsolete-url-in-packaging -Severity: warning -Check: obsolete-sites -Explanation: One of the package's packaging files points to a website or code - hoster known to have frozen contents, to be closed soon or to have - already closed. - . - Please look for the new upstream home of the package and update the - packaging accordingly. - . - Sites previously hosted on code.google.com and codeplex.com were offered a - migration to github.com, sites previously on gitorious.org were offered a - migration to gitlab.com, sites previously hosted on fedorahosted.org were - offered a migration to pagure.io. You might want to look there first. diff -Nru lintian-2.93.0/tags/o/ocaml-custom-executable.desc lintian-2.89.0ubuntu1/tags/o/ocaml-custom-executable.desc --- lintian-2.93.0/tags/o/ocaml-custom-executable.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/o/ocaml-custom-executable.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: ocaml-custom-executable +Severity: warning +Certainty: possible +Check: binaries +Info: This package provides an OCaml bytecode executable linked with a + custom runtime. Such executables cannot be stripped and require + special care. Their usage is deprecated in favour of shared libraries + for C stubs (dll*.so). diff -Nru lintian-2.93.0/tags/o/ocaml-custom-executable.tag lintian-2.89.0ubuntu1/tags/o/ocaml-custom-executable.tag --- lintian-2.93.0/tags/o/ocaml-custom-executable.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/o/ocaml-custom-executable.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: ocaml-custom-executable -Severity: warning -Check: binaries -Explanation: This package provides an OCaml bytecode executable linked with a - custom runtime. Such executables cannot be stripped and require - special care. Their usage is deprecated in favour of shared libraries - for C stubs (dll*.so). diff -Nru lintian-2.93.0/tags/o/ocaml-dangling-cmi.desc lintian-2.89.0ubuntu1/tags/o/ocaml-dangling-cmi.desc --- lintian-2.93.0/tags/o/ocaml-dangling-cmi.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/o/ocaml-dangling-cmi.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: ocaml-dangling-cmi +Severity: info +Certainty: possible +Check: languages/ocaml +Info: This package installs a compiled interface (.cmi) without + its text version (.mli). The text version should also be + installed for documentation purpose. If the module involved doesn't have + a .mli, its source code (.ml) should be installed + instead. diff -Nru lintian-2.93.0/tags/o/ocaml-dangling-cmi.tag lintian-2.89.0ubuntu1/tags/o/ocaml-dangling-cmi.tag --- lintian-2.93.0/tags/o/ocaml-dangling-cmi.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/o/ocaml-dangling-cmi.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: ocaml-dangling-cmi -Severity: info -Check: languages/ocaml -Explanation: This package installs a compiled interface (.cmi) without - its text version (.mli). The text version should also be - installed for documentation purpose. If the module involved doesn't have - a .mli, its source code (.ml) should be installed - instead. diff -Nru lintian-2.93.0/tags/o/ocaml-dangling-cmxa.desc lintian-2.89.0ubuntu1/tags/o/ocaml-dangling-cmxa.desc --- lintian-2.93.0/tags/o/ocaml-dangling-cmxa.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/o/ocaml-dangling-cmxa.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,5 @@ +Tag: ocaml-dangling-cmxa +Severity: error +Check: languages/ocaml +Info: This package provides a .cmxa library without its + implementation (.a static library). diff -Nru lintian-2.93.0/tags/o/ocaml-dangling-cmxa.tag lintian-2.89.0ubuntu1/tags/o/ocaml-dangling-cmxa.tag --- lintian-2.93.0/tags/o/ocaml-dangling-cmxa.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/o/ocaml-dangling-cmxa.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,5 +0,0 @@ -Tag: ocaml-dangling-cmxa -Severity: error -Check: languages/ocaml -Explanation: This package provides a .cmxa library without its - implementation (.a static library). diff -Nru lintian-2.93.0/tags/o/ocaml-dangling-cmx.desc lintian-2.89.0ubuntu1/tags/o/ocaml-dangling-cmx.desc --- lintian-2.93.0/tags/o/ocaml-dangling-cmx.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/o/ocaml-dangling-cmx.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: ocaml-dangling-cmx +Severity: error +Check: languages/ocaml +Info: This package provides a .cmx module without its + implementation (.o object file which may be embedded in a + .a static library installed in the same directory). diff -Nru lintian-2.93.0/tags/o/ocaml-dangling-cmxs.desc lintian-2.89.0ubuntu1/tags/o/ocaml-dangling-cmxs.desc --- lintian-2.93.0/tags/o/ocaml-dangling-cmxs.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/o/ocaml-dangling-cmxs.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: ocaml-dangling-cmxs +Severity: warning +Certainty: possible +Check: languages/ocaml +Info: This package seems to be a library package, and provides a native + plugin (.cmxs). If the plugin is meant to be used as a library + for other plugins, it should be shipped as bytecode (.cma or + .cmo) as well. diff -Nru lintian-2.93.0/tags/o/ocaml-dangling-cmxs.tag lintian-2.89.0ubuntu1/tags/o/ocaml-dangling-cmxs.tag --- lintian-2.93.0/tags/o/ocaml-dangling-cmxs.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/o/ocaml-dangling-cmxs.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: ocaml-dangling-cmxs -Severity: warning -Check: languages/ocaml -Explanation: This package seems to be a library package, and provides a native - plugin (.cmxs). If the plugin is meant to be used as a library - for other plugins, it should be shipped as bytecode (.cma or - .cmo) as well. diff -Nru lintian-2.93.0/tags/o/ocaml-dangling-cmx.tag lintian-2.89.0ubuntu1/tags/o/ocaml-dangling-cmx.tag --- lintian-2.93.0/tags/o/ocaml-dangling-cmx.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/o/ocaml-dangling-cmx.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: ocaml-dangling-cmx -Severity: error -Check: languages/ocaml -Explanation: This package provides a .cmx module without its - implementation (.o object file which may be embedded in a - .a static library installed in the same directory). diff -Nru lintian-2.93.0/tags/o/ocaml-dev-file-in-nondev-package.desc lintian-2.89.0ubuntu1/tags/o/ocaml-dev-file-in-nondev-package.desc --- lintian-2.93.0/tags/o/ocaml-dev-file-in-nondev-package.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/o/ocaml-dev-file-in-nondev-package.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: ocaml-dev-file-in-nondev-package +Severity: pedantic +Certainty: possible +Check: languages/ocaml +Info: This package doesn't appear to be a development package, but + installs OCaml development files (.cmi, .cmx or + .cmxa). These files should be moved to a development package. diff -Nru lintian-2.93.0/tags/o/ocaml-dev-file-in-nondev-package.tag lintian-2.89.0ubuntu1/tags/o/ocaml-dev-file-in-nondev-package.tag --- lintian-2.93.0/tags/o/ocaml-dev-file-in-nondev-package.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/o/ocaml-dev-file-in-nondev-package.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: ocaml-dev-file-in-nondev-package -Severity: pedantic -Check: languages/ocaml -Explanation: This package doesn't appear to be a development package, but - installs OCaml development files (.cmi, .cmx or - .cmxa). These files should be moved to a development package. diff -Nru lintian-2.93.0/tags/o/ocaml-dev-file-not-in-usr-lib-ocaml.desc lintian-2.89.0ubuntu1/tags/o/ocaml-dev-file-not-in-usr-lib-ocaml.desc --- lintian-2.93.0/tags/o/ocaml-dev-file-not-in-usr-lib-ocaml.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/o/ocaml-dev-file-not-in-usr-lib-ocaml.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: ocaml-dev-file-not-in-usr-lib-ocaml +Severity: pedantic +Certainty: possible +Check: languages/ocaml +Info: This development package installs OCaml development files + (.cmi, .cmx or .cmxa) outside + /usr/lib/ocaml. Such files are used only by compilation and + should be in a subdirectory of OCaml standard library path. diff -Nru lintian-2.93.0/tags/o/ocaml-dev-file-not-in-usr-lib-ocaml.tag lintian-2.89.0ubuntu1/tags/o/ocaml-dev-file-not-in-usr-lib-ocaml.tag --- lintian-2.93.0/tags/o/ocaml-dev-file-not-in-usr-lib-ocaml.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/o/ocaml-dev-file-not-in-usr-lib-ocaml.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: ocaml-dev-file-not-in-usr-lib-ocaml -Severity: pedantic -Check: languages/ocaml -Explanation: This development package installs OCaml development files - (.cmi, .cmx or .cmxa) outside - /usr/lib/ocaml. Such files are used only by compilation and - should be in a subdirectory of OCaml standard library path. diff -Nru lintian-2.93.0/tags/o/ocaml-meta-without-suggesting-findlib.desc lintian-2.89.0ubuntu1/tags/o/ocaml-meta-without-suggesting-findlib.desc --- lintian-2.93.0/tags/o/ocaml-meta-without-suggesting-findlib.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/o/ocaml-meta-without-suggesting-findlib.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: ocaml-meta-without-suggesting-findlib +Severity: pedantic +Check: languages/ocaml +Info: This development package installs a META file but doesn't depend on + ocaml-findlib. Libraries with META file are easier to use with findlib. + The package should at least suggest ocaml-findlib. diff -Nru lintian-2.93.0/tags/o/ocaml-meta-without-suggesting-findlib.tag lintian-2.89.0ubuntu1/tags/o/ocaml-meta-without-suggesting-findlib.tag --- lintian-2.93.0/tags/o/ocaml-meta-without-suggesting-findlib.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/o/ocaml-meta-without-suggesting-findlib.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: ocaml-meta-without-suggesting-findlib -Severity: pedantic -Check: languages/ocaml -Explanation: This development package installs a META file but doesn't depend on - ocaml-findlib. Libraries with META file are easier to use with findlib. - The package should at least suggest ocaml-findlib. diff -Nru lintian-2.93.0/tags/o/ocaml-stray-cmo.desc lintian-2.89.0ubuntu1/tags/o/ocaml-stray-cmo.desc --- lintian-2.93.0/tags/o/ocaml-stray-cmo.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/o/ocaml-stray-cmo.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: ocaml-stray-cmo +Severity: info +Certainty: wild-guess +Check: languages/ocaml +Info: This package installs a .cma file and a .cmo file + with the same base name. Most of the time, the module provided by the + .cmo file is also linked in the .cma file, so the + .cmo file is useless. diff -Nru lintian-2.93.0/tags/o/ocaml-stray-cmo.tag lintian-2.89.0ubuntu1/tags/o/ocaml-stray-cmo.tag --- lintian-2.93.0/tags/o/ocaml-stray-cmo.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/o/ocaml-stray-cmo.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: ocaml-stray-cmo -Severity: info -Check: languages/ocaml -Explanation: This package installs a .cma file and a .cmo file - with the same base name. Most of the time, the module provided by the - .cmo file is also linked in the .cma file, so the - .cmo file is useless. diff -Nru lintian-2.93.0/tags/o/octal-permissions.desc lintian-2.89.0ubuntu1/tags/o/octal-permissions.desc --- lintian-2.93.0/tags/o/octal-permissions.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/o/octal-permissions.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,5 @@ +Tag: octal-permissions +Severity: classification +Check: files/permissions +Info: The named file has the octal permissions shown. +Ref: Bug#945869, Bug#796257 diff -Nru lintian-2.93.0/tags/o/octal-permissions.tag lintian-2.89.0ubuntu1/tags/o/octal-permissions.tag --- lintian-2.93.0/tags/o/octal-permissions.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/o/octal-permissions.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,5 +0,0 @@ -Tag: octal-permissions -Severity: classification -Check: files/permissions -Explanation: The named file has the octal permissions shown. -See-Also: Bug#945869, Bug#796257 diff -Nru lintian-2.93.0/tags/o/odd-historical-debian-changelog-version.desc lintian-2.89.0ubuntu1/tags/o/odd-historical-debian-changelog-version.desc --- lintian-2.93.0/tags/o/odd-historical-debian-changelog-version.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/o/odd-historical-debian-changelog-version.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,15 @@ +Tag: odd-historical-debian-changelog-version +Severity: warning +Check: debian/changelog +Info: The version string in a historical changelog entry was not parsed + correctly. Usually, that means it does not conform to policy. + . + It can also happen when a package changes from native to non-native + (or the other way around). Historical entries are then in a nonconforming + format. + . + As a side note, Lintian cannot tell whether a package changed from + naive to non-native, or the other way around. It can only say whether + the historical changelog entries comply with the current nativeness of a + package. +Ref: policy 5.6.12 diff -Nru lintian-2.93.0/tags/o/odd-historical-debian-changelog-version.tag lintian-2.89.0ubuntu1/tags/o/odd-historical-debian-changelog-version.tag --- lintian-2.93.0/tags/o/odd-historical-debian-changelog-version.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/o/odd-historical-debian-changelog-version.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,15 +0,0 @@ -Tag: odd-historical-debian-changelog-version -Severity: warning -Check: debian/changelog -Explanation: The version string in a historical changelog entry was not parsed - correctly. Usually, that means it does not conform to policy. - . - It can also happen when a package changes from native to non-native - (or the other way around). Historical entries are then in a nonconforming - format. - . - As a side note, Lintian cannot tell whether a package changed from - naive to non-native, or the other way around. It can only say whether - the historical changelog entries comply with the current nativeness of a - package. -See-Also: policy 5.6.12 diff -Nru lintian-2.93.0/tags/o/odd-mark-in-description.desc lintian-2.89.0ubuntu1/tags/o/odd-mark-in-description.desc --- lintian-2.93.0/tags/o/odd-mark-in-description.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/o/odd-mark-in-description.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: odd-mark-in-description +Severity: pedantic +Check: fields/description +Info: A punction mark was placed oddly in the description. + . + This tag is currently only issued for a comman that is + followed by a non-whitespace character. +Ref: Bug#591665, Bug#591664 diff -Nru lintian-2.93.0/tags/o/odd-mark-in-description.tag lintian-2.89.0ubuntu1/tags/o/odd-mark-in-description.tag --- lintian-2.93.0/tags/o/odd-mark-in-description.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/o/odd-mark-in-description.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: odd-mark-in-description -Severity: pedantic -Check: fields/description -Explanation: A punction mark was placed oddly in the description. - . - This tag is currently only issued for a comman that is - followed by a non-whitespace character. -See-Also: Bug#591665, Bug#591664 diff -Nru lintian-2.93.0/tags/o/odd-permissions-on-shared-library.desc lintian-2.89.0ubuntu1/tags/o/odd-permissions-on-shared-library.desc --- lintian-2.93.0/tags/o/odd-permissions-on-shared-library.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/o/odd-permissions-on-shared-library.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: odd-permissions-on-shared-library +Severity: warning +Check: shared-libs +Renamed-From: shlib-with-bad-permissions +Info: Shared libraries should be mode 0644. +Ref: policy 8.1 diff -Nru lintian-2.93.0/tags/o/odd-permissions-on-shared-library.tag lintian-2.89.0ubuntu1/tags/o/odd-permissions-on-shared-library.tag --- lintian-2.93.0/tags/o/odd-permissions-on-shared-library.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/o/odd-permissions-on-shared-library.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: odd-permissions-on-shared-library -Severity: warning -Check: shared-libs -Renamed-From: shlib-with-bad-permissions -Explanation: Shared libraries should be mode 0644. -See-Also: policy 8.1 diff -Nru lintian-2.93.0/tags/o/odd-place-for-manual-page.desc lintian-2.89.0ubuntu1/tags/o/odd-place-for-manual-page.desc --- lintian-2.93.0/tags/o/odd-place-for-manual-page.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/o/odd-place-for-manual-page.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,11 @@ +Tag: odd-place-for-manual-page +Severity: error +Check: documentation/manual +Renamed-From: manpage-in-wrong-directory +Info: The manual page should be installed in the correct directory below + /usr/share/man/ or /usr/share/man/locale. + Only sections 1 through 9 should be used. + . + The section number in the filename should correspond with the section + number in the directory name. +Ref: policy 12.1 diff -Nru lintian-2.93.0/tags/o/odd-place-for-manual-page.tag lintian-2.89.0ubuntu1/tags/o/odd-place-for-manual-page.tag --- lintian-2.93.0/tags/o/odd-place-for-manual-page.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/o/odd-place-for-manual-page.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,11 +0,0 @@ -Tag: odd-place-for-manual-page -Severity: error -Check: documentation/manual -Renamed-From: manpage-in-wrong-directory -Explanation: The manual page should be installed in the correct directory below - /usr/share/man/ or /usr/share/man/*locale*. - Only sections 1 through 9 should be used. - . - The section number in the filename should correspond with the section - number in the directory name. -See-Also: policy 12.1 diff -Nru lintian-2.93.0/tags/o/older-source-format.desc lintian-2.89.0ubuntu1/tags/o/older-source-format.desc --- lintian-2.93.0/tags/o/older-source-format.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/o/older-source-format.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,15 @@ +Tag: older-source-format +Severity: info +Check: debian/source-dir +Info: + This package uses an older source format. Please consider migrating + to a more modern format. + . + The 3.x series of source formats have a number of advantages including + superior compression formats, native patch handling, binary file + support, multiple upstream tarballs, etc. + . + More information is available here: + . + https://wiki.debian.org/Projects/DebSrc3.0 +Ref: #884498, dpkg-source(1) diff -Nru lintian-2.93.0/tags/o/older-source-format.tag lintian-2.89.0ubuntu1/tags/o/older-source-format.tag --- lintian-2.93.0/tags/o/older-source-format.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/o/older-source-format.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,15 +0,0 @@ -Tag: older-source-format -Severity: info -Check: debian/source-dir -Explanation: - This package uses an older source format. Please consider migrating - to a more modern format. - . - The 3.x series of source formats have a number of advantages including - superior compression formats, native patch handling, binary file - support, multiple upstream tarballs, etc. - . - More information is available here: - . - https://wiki.debian.org/Projects/DebSrc3.0 -See-Also: Bug#884498, dpkg-source(1) diff -Nru lintian-2.93.0/tags/o/old-fsf-address-in-copyright-file.desc lintian-2.89.0ubuntu1/tags/o/old-fsf-address-in-copyright-file.desc --- lintian-2.93.0/tags/o/old-fsf-address-in-copyright-file.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/o/old-fsf-address-in-copyright-file.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: old-fsf-address-in-copyright-file +Severity: warning +Check: debian/copyright +Info: The /usr/share/doc/pkg/copyright file refers to the old postal + address of the Free Software Foundation (FSF). The new address is: + . + Free Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, + MA 02110-1301, USA. diff -Nru lintian-2.93.0/tags/o/old-fsf-address-in-copyright-file.tag lintian-2.89.0ubuntu1/tags/o/old-fsf-address-in-copyright-file.tag --- lintian-2.93.0/tags/o/old-fsf-address-in-copyright-file.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/o/old-fsf-address-in-copyright-file.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: old-fsf-address-in-copyright-file -Severity: warning -Check: debian/copyright -Explanation: The /usr/share/doc/*pkg*/copyright file refers to the old postal - address of the Free Software Foundation (FSF). The new address is: - . - Free Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, - MA 02110-1301, USA. diff -Nru lintian-2.93.0/tags/o/old-python-version-field.desc lintian-2.89.0ubuntu1/tags/o/old-python-version-field.desc --- lintian-2.93.0/tags/o/old-python-version-field.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/o/old-python-version-field.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,15 @@ +Tag: old-python-version-field +Severity: pedantic +Check: languages/python +Ref: python-policy 3.4 +Info: The specified Python-Version or Python3-Version field is used to + specify the version(s) of Python the package supports. However, the + associated Python version is satisfied by the current "stable" + distribution of Debian and may be unnecessary. + . + Please remove or update the reference. This warning should be ignored + if you wish to support "sloppy" backports. If removing, please also check + for the use of py3versions -r in debian/rules, and + debian/tests/. Without an operative Python3-Version + field py3versions will fall back to all supported versions + which may not be appropriate. diff -Nru lintian-2.93.0/tags/o/old-python-version-field.tag lintian-2.89.0ubuntu1/tags/o/old-python-version-field.tag --- lintian-2.93.0/tags/o/old-python-version-field.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/o/old-python-version-field.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,15 +0,0 @@ -Tag: old-python-version-field -Severity: pedantic -Check: languages/python -See-Also: python-policy 3.4 -Explanation: The specified Python-Version or Python3-Version field is used to - specify the version(s) of Python the package supports. However, the - associated Python version is satisfied by the current "stable" - distribution of Debian and may be unnecessary. - . - Please remove or update the reference. This warning should be ignored - if you wish to support "sloppy" backports. If removing, please also check - for the use of py3versions -r in debian/rules, and - debian/tests/. Without an operative Python3-Version - field py3versions will fall back to all supported versions - which may not be appropriate. diff -Nru lintian-2.93.0/tags/o/old-source-override-location.desc lintian-2.89.0ubuntu1/tags/o/old-source-override-location.desc --- lintian-2.93.0/tags/o/old-source-override-location.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/o/old-source-override-location.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,11 @@ +Tag: old-source-override-location +Severity: pedantic +Check: debian/lintian-overrides +Renamed-From: package-uses-deprecated-source-override-location +Info: This Debian package ships Lintian source-level overrides in the + debian/source.lintian-overrides file. + . + Please use debian/source/lintian-overrides instead; the + debian/source directory is preferred to hold "source"-specific + files. +Ref: lintian 2.4 diff -Nru lintian-2.93.0/tags/o/old-source-override-location.tag lintian-2.89.0ubuntu1/tags/o/old-source-override-location.tag --- lintian-2.93.0/tags/o/old-source-override-location.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/o/old-source-override-location.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,11 +0,0 @@ -Tag: old-source-override-location -Severity: pedantic -Check: debian/lintian-overrides -Renamed-From: package-uses-deprecated-source-override-location -Explanation: This Debian package ships Lintian source-level overrides in the - debian/source.lintian-overrides file. - . - Please use debian/source/lintian-overrides instead; the - debian/source directory is preferred to hold "source"-specific - files. -See-Also: lintian 2.4 diff -Nru lintian-2.93.0/tags/o/old-style-config-script.desc lintian-2.89.0ubuntu1/tags/o/old-style-config-script.desc --- lintian-2.93.0/tags/o/old-style-config-script.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/o/old-style-config-script.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,27 @@ +Tag: old-style-config-script +Severity: pedantic +Certainty: possible +Check: files/config-scripts +Info: The following file is an old style config file, + used to retrieve information about installed libraries in the system. + It is typically used to compile and link against one or more libraries. + . + Using this kind of system to pass compile file is obsolete and + will likely introduce bugs in a multi-arch system. Particularly, + this kind of script could only belong to a package that is not + Multi-Arch. + . + You should consider to move to pkg-config file and + warn your user to not use this script, and open a bug upstream. + . + You should also consider to implement this file as a compatibility + wrapper over pkg-config. + . + After fixing every reverse depends of your package and use + pkg-config reverse depends makefile, you should + consider to put this script, as a temporary convenience of your users, + under /usr/lib/$DEB_HOST_MULTIARCH/$PACKAGE/bin where + $DEB_HOST_MULTIARCH is the multi-arch triplet and $PACKAGE is the + package name. You should also consider to add a NEWS.Debian entry. +Ref: pkg-config(1), + http://sources.debian.net/src/imagemagick/8:6.8.9.9-6/debian/NEWS/ diff -Nru lintian-2.93.0/tags/o/old-style-config-script-multiarch-path-arch-all.desc lintian-2.89.0ubuntu1/tags/o/old-style-config-script-multiarch-path-arch-all.desc --- lintian-2.93.0/tags/o/old-style-config-script-multiarch-path-arch-all.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/o/old-style-config-script-multiarch-path-arch-all.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,12 @@ +Tag: old-style-config-script-multiarch-path-arch-all +Severity: error +Certainty: possible +Check: files/config-scripts +Info: The following file is an old style config file, + used to retrieve information about installed libraries in the system. + It is typically used to compile and link against one or more libraries. + . + This old style config file contains a multi-arch path and the package + is arch: all. + . + You should change the package to arch: any. diff -Nru lintian-2.93.0/tags/o/old-style-config-script-multiarch-path-arch-all.tag lintian-2.89.0ubuntu1/tags/o/old-style-config-script-multiarch-path-arch-all.tag --- lintian-2.93.0/tags/o/old-style-config-script-multiarch-path-arch-all.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/o/old-style-config-script-multiarch-path-arch-all.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,11 +0,0 @@ -Tag: old-style-config-script-multiarch-path-arch-all -Severity: error -Check: files/config-scripts -Explanation: The following file is an old style config file, - used to retrieve information about installed libraries in the system. - It is typically used to compile and link against one or more libraries. - . - This old style config file contains a multi-arch path and the package - is arch: all. - . - You should change the package to arch: any. diff -Nru lintian-2.93.0/tags/o/old-style-config-script-multiarch-path.desc lintian-2.89.0ubuntu1/tags/o/old-style-config-script-multiarch-path.desc --- lintian-2.93.0/tags/o/old-style-config-script-multiarch-path.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/o/old-style-config-script-multiarch-path.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: old-style-config-script-multiarch-path +Severity: error +Certainty: possible +Check: files/config-scripts +Info: The following file is an old style config file, used + to retrieve information about installed libraries in the system. + It is typically used to compile and link against one or more libraries. + . + This old style config file contains a multi-arch path and the package + is declared Multi-arch. diff -Nru lintian-2.93.0/tags/o/old-style-config-script-multiarch-path.tag lintian-2.89.0ubuntu1/tags/o/old-style-config-script-multiarch-path.tag --- lintian-2.93.0/tags/o/old-style-config-script-multiarch-path.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/o/old-style-config-script-multiarch-path.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: old-style-config-script-multiarch-path -Severity: error -Check: files/config-scripts -Explanation: The following file is an old style config file, used - to retrieve information about installed libraries in the system. - It is typically used to compile and link against one or more libraries. - . - This old style config file contains a multi-arch path and the package - is declared Multi-arch. diff -Nru lintian-2.93.0/tags/o/old-style-config-script.tag lintian-2.89.0ubuntu1/tags/o/old-style-config-script.tag --- lintian-2.93.0/tags/o/old-style-config-script.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/o/old-style-config-script.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,26 +0,0 @@ -Tag: old-style-config-script -Severity: pedantic -Check: files/config-scripts -Explanation: The following file is an old style config file, - used to retrieve information about installed libraries in the system. - It is typically used to compile and link against one or more libraries. - . - Using this kind of system to pass compile file is obsolete and - will likely introduce bugs in a multi-arch system. Particularly, - this kind of script could only belong to a package that is not - Multi-Arch. - . - You should consider to move to pkg-config file and - warn your user to not use this script, and open a bug upstream. - . - You should also consider to implement this file as a compatibility - wrapper over pkg-config. - . - After fixing every reverse depends of your package and use - pkg-config reverse depends makefile, you should - consider to put this script, as a temporary convenience of your users, - under /usr/lib/$DEB_HOST_MULTIARCH/$PACKAGE/bin where - $DEB_HOST_MULTIARCH is the multi-arch triplet and $PACKAGE is the - package name. You should also consider to add a NEWS.Debian entry. -See-Also: pkg-config(1), - http://sources.debian.net/src/imagemagick/8:6.8.9.9-6/debian/NEWS/ diff -Nru lintian-2.93.0/tags/o/omitted-systemd-service-for-init.d-script.desc lintian-2.89.0ubuntu1/tags/o/omitted-systemd-service-for-init.d-script.desc --- lintian-2.93.0/tags/o/omitted-systemd-service-for-init.d-script.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/o/omitted-systemd-service-for-init.d-script.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,16 @@ +Tag: omitted-systemd-service-for-init.d-script +Severity: error +Check: systemd +Info: The specified init.d script has no systemd equivalent and the + package ships other units. + . + This typically occurs when a maintainer missed script when adding + systemd integration, or a new init script was added in a new upstream + version. + . + Systemd has a SysV init.d script compatibility mode. It provides access to + each SysV init.d script as long as there is no native service file with the + same name (e.g. /lib/systemd/system/rsyslog.service corresponds to + /etc/init.d/rsyslog). +Renamed-From: + systemd-no-service-for-init-script diff -Nru lintian-2.93.0/tags/o/omitted-systemd-service-for-init.d-script.tag lintian-2.89.0ubuntu1/tags/o/omitted-systemd-service-for-init.d-script.tag --- lintian-2.93.0/tags/o/omitted-systemd-service-for-init.d-script.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/o/omitted-systemd-service-for-init.d-script.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,16 +0,0 @@ -Tag: omitted-systemd-service-for-init.d-script -Severity: error -Check: systemd -Explanation: The specified init.d script has no systemd equivalent and the - package ships other units. - . - This typically occurs when a maintainer missed script when adding - systemd integration, or a new init script was added in a new upstream - version. - . - Systemd has a SysV init.d script compatibility mode. It provides access to - each SysV init.d script as long as there is no native service file with the - same name (e.g. /lib/systemd/system/rsyslog.service corresponds to - /etc/init.d/rsyslog). -Renamed-From: - systemd-no-service-for-init-script diff -Nru lintian-2.93.0/tags/o/opentype-font-prohibits-installable-embedding.desc lintian-2.89.0ubuntu1/tags/o/opentype-font-prohibits-installable-embedding.desc --- lintian-2.93.0/tags/o/opentype-font-prohibits-installable-embedding.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/o/opentype-font-prohibits-installable-embedding.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: opentype-font-prohibits-installable-embedding +Severity: warning +Check: fonts/opentype +Info: This package installs an OpenType font with restrictive license + terms. The font does not permit installable embedding, as defined by + the OpenType standard. +Ref: https://docs.microsoft.com/en-us/typography/opentype/spec/os2#fstype diff -Nru lintian-2.93.0/tags/o/opentype-font-prohibits-installable-embedding.tag lintian-2.89.0ubuntu1/tags/o/opentype-font-prohibits-installable-embedding.tag --- lintian-2.93.0/tags/o/opentype-font-prohibits-installable-embedding.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/o/opentype-font-prohibits-installable-embedding.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: opentype-font-prohibits-installable-embedding -Severity: warning -Check: fonts/opentype -Explanation: This package installs an OpenType font with restrictive license - terms. The font does not permit installable embedding, as defined by - the OpenType standard. -See-Also: https://docs.microsoft.com/en-us/typography/opentype/spec/os2#fstype diff -Nru lintian-2.93.0/tags/o/opentype-font-wrong-filename.desc lintian-2.89.0ubuntu1/tags/o/opentype-font-wrong-filename.desc --- lintian-2.93.0/tags/o/opentype-font-wrong-filename.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/o/opentype-font-wrong-filename.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,5 @@ +Tag: opentype-font-wrong-filename +Severity: warning +Check: fonts/opentype +Info: This package installs an OpenType font with an extension other than + .otf. The check is case-insensitive. diff -Nru lintian-2.93.0/tags/o/opentype-font-wrong-filename.tag lintian-2.89.0ubuntu1/tags/o/opentype-font-wrong-filename.tag --- lintian-2.93.0/tags/o/opentype-font-wrong-filename.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/o/opentype-font-wrong-filename.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,5 +0,0 @@ -Tag: opentype-font-wrong-filename -Severity: warning -Check: fonts/opentype -Explanation: This package installs an OpenType font with an extension other than - .otf. The check is case-insensitive. diff -Nru lintian-2.93.0/tags/o/ored-build-depends-on-obsolete-package.desc lintian-2.89.0ubuntu1/tags/o/ored-build-depends-on-obsolete-package.desc --- lintian-2.93.0/tags/o/ored-build-depends-on-obsolete-package.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/o/ored-build-depends-on-obsolete-package.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: ored-build-depends-on-obsolete-package +Severity: info +Certainty: possible +Check: fields/package-relations +Info: The package build-depends on an ORed group of packages which includes + a package that has been superseded. diff -Nru lintian-2.93.0/tags/o/ored-build-depends-on-obsolete-package.tag lintian-2.89.0ubuntu1/tags/o/ored-build-depends-on-obsolete-package.tag --- lintian-2.93.0/tags/o/ored-build-depends-on-obsolete-package.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/o/ored-build-depends-on-obsolete-package.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,5 +0,0 @@ -Tag: ored-build-depends-on-obsolete-package -Severity: info -Check: fields/package-relations -Explanation: The package build-depends on an ORed group of packages which includes - a package that has been superseded. diff -Nru lintian-2.93.0/tags/o/ored-depends-on-obsolete-package.desc lintian-2.89.0ubuntu1/tags/o/ored-depends-on-obsolete-package.desc --- lintian-2.93.0/tags/o/ored-depends-on-obsolete-package.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/o/ored-depends-on-obsolete-package.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: ored-depends-on-obsolete-package +Severity: info +Certainty: possible +Check: fields/package-relations +Info: The package depends on an ORed group of packages which includes + a package that has been superseded. diff -Nru lintian-2.93.0/tags/o/ored-depends-on-obsolete-package.tag lintian-2.89.0ubuntu1/tags/o/ored-depends-on-obsolete-package.tag --- lintian-2.93.0/tags/o/ored-depends-on-obsolete-package.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/o/ored-depends-on-obsolete-package.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,5 +0,0 @@ -Tag: ored-depends-on-obsolete-package -Severity: info -Check: fields/package-relations -Explanation: The package depends on an ORed group of packages which includes - a package that has been superseded. diff -Nru lintian-2.93.0/tags/o/orig-tarball-missing-upstream-signature.desc lintian-2.89.0ubuntu1/tags/o/orig-tarball-missing-upstream-signature.desc --- lintian-2.93.0/tags/o/orig-tarball-missing-upstream-signature.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/o/orig-tarball-missing-upstream-signature.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,23 @@ +Tag: orig-tarball-missing-upstream-signature +Severity: warning +Check: upstream-signature +Info: The packaging includes an upstream signing key but the corresponding + .asc signature for one or more source tarballs are not included + in your .changes file. + . + Please ensure a + <package>_<version>.orig.tar.<ext>.asc file + exists in the same directory as your + <package>_<version>.orig.tar.<ext> tarball prior + to dpkg-source --build being called. + . + If you are repackaging your source tarballs for Debian Free Software + Guidelines compliance reasons, ensure that your package version includes + dfsg or similar. + . + Sometimes, an upstream signature must be added for an orig.tar.gz + that is already present in the archive. Please include the upstream sources + again with dpkg-genchanges -sa while the signature is also present. + Your upload will be accepted as long as the new orig.tar.gz file + is identical to the old one. +Ref: Bug#954743, Bug#872864 diff -Nru lintian-2.93.0/tags/o/orig-tarball-missing-upstream-signature.tag lintian-2.89.0ubuntu1/tags/o/orig-tarball-missing-upstream-signature.tag --- lintian-2.93.0/tags/o/orig-tarball-missing-upstream-signature.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/o/orig-tarball-missing-upstream-signature.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,23 +0,0 @@ -Tag: orig-tarball-missing-upstream-signature -Severity: warning -Check: upstream-signature -Explanation: The packaging includes an upstream signing key but the corresponding - .asc signature for one or more source tarballs are not included - in your .changes file. - . - Please ensure a - <package>_<version>.orig.tar.<ext>.asc file - exists in the same directory as your - <package>_<version>.orig.tar.<ext> tarball prior - to dpkg-source --build being called. - . - If you are repackaging your source tarballs for Debian Free Software - Guidelines compliance reasons, ensure that your package version includes - dfsg or similar. - . - Sometimes, an upstream signature must be added for an orig.tar.gz - that is already present in the archive. Please include the upstream sources - again with dpkg-genchanges -sa while the signature is also present. - Your upload will be accepted as long as the new orig.tar.gz file - is identical to the old one. -See-Also: Bug#954743, Bug#872864 diff -Nru lintian-2.93.0/tags/o/orphaned-diversion.desc lintian-2.89.0ubuntu1/tags/o/orphaned-diversion.desc --- lintian-2.93.0/tags/o/orphaned-diversion.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/o/orphaned-diversion.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,5 @@ +Tag: orphaned-diversion +Severity: error +Check: scripts +Info: A diversion was added for the file, but not removed. This means + your package doesn't restore the previous state after removal. diff -Nru lintian-2.93.0/tags/o/orphaned-diversion.tag lintian-2.89.0ubuntu1/tags/o/orphaned-diversion.tag --- lintian-2.93.0/tags/o/orphaned-diversion.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/o/orphaned-diversion.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,5 +0,0 @@ -Tag: orphaned-diversion -Severity: error -Check: scripts -Explanation: A diversion was added for the file, but not removed. This means - your package doesn't restore the previous state after removal. diff -Nru lintian-2.93.0/tags/o/orphaned-package-maintained-in-private-space.desc lintian-2.89.0ubuntu1/tags/o/orphaned-package-maintained-in-private-space.desc --- lintian-2.93.0/tags/o/orphaned-package-maintained-in-private-space.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/o/orphaned-package-maintained-in-private-space.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,13 @@ +Tag: orphaned-package-maintained-in-private-space +Severity: warning +Check: fields/vcs +Info: + This package is orphaned and the specified VCS field points to a private + space in the *.debian.org infrastructure. The sources are probably not + accessible to the Quality Assurance (QA) Team, which prepares uploads + in the interim. + . + Please move the source repository to a location in + https://salsa.debian.org/debian/ or https://git.dgit.debian.org/ + or update the specified VCS field if the information is incorrect. +Ref: #947671 diff -Nru lintian-2.93.0/tags/o/orphaned-package-maintained-in-private-space.tag lintian-2.89.0ubuntu1/tags/o/orphaned-package-maintained-in-private-space.tag --- lintian-2.93.0/tags/o/orphaned-package-maintained-in-private-space.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/o/orphaned-package-maintained-in-private-space.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,13 +0,0 @@ -Tag: orphaned-package-maintained-in-private-space -Severity: warning -Check: fields/vcs -Explanation: - This package is orphaned and the specified VCS field points to a private - space in the *.debian.org infrastructure. The sources are probably not - accessible to the Quality Assurance (QA) Team, which prepares uploads - in the interim. - . - Please move the source repository to a location in - https://salsa.debian.org/debian/ or https://git.dgit.debian.org/ - or update the specified VCS field if the information is incorrect. -See-Also: Bug#947671 diff -Nru lintian-2.93.0/tags/o/orphaned-package-not-maintained-in-debian-infrastructure.desc lintian-2.89.0ubuntu1/tags/o/orphaned-package-not-maintained-in-debian-infrastructure.desc --- lintian-2.93.0/tags/o/orphaned-package-not-maintained-in-debian-infrastructure.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/o/orphaned-package-not-maintained-in-debian-infrastructure.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,12 @@ +Tag: orphaned-package-not-maintained-in-debian-infrastructure +Severity: warning +Check: fields/vcs +Info: + This package is orphaned but the specified VCS field does not point to + an area within the *.debian.org infrastructure + . + This prevents other developers and external contributors to collaborate + on its maintenance. + . + Please move the packaging to under the *.debian.org umbrella or update + the specified VCS field if it is otherwise wrong. diff -Nru lintian-2.93.0/tags/o/orphaned-package-not-maintained-in-debian-infrastructure.tag lintian-2.89.0ubuntu1/tags/o/orphaned-package-not-maintained-in-debian-infrastructure.tag --- lintian-2.93.0/tags/o/orphaned-package-not-maintained-in-debian-infrastructure.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/o/orphaned-package-not-maintained-in-debian-infrastructure.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,12 +0,0 @@ -Tag: orphaned-package-not-maintained-in-debian-infrastructure -Severity: warning -Check: fields/vcs -Explanation: - This package is orphaned but the specified VCS field does not point to - an area within the *.debian.org infrastructure - . - This prevents other developers and external contributors to collaborate - on its maintenance. - . - Please move the packaging to under the *.debian.org umbrella or update - the specified VCS field if it is otherwise wrong. diff -Nru lintian-2.93.0/tags/o/outdated-relation-in-shlibs.desc lintian-2.89.0ubuntu1/tags/o/outdated-relation-in-shlibs.desc --- lintian-2.93.0/tags/o/outdated-relation-in-shlibs.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/o/outdated-relation-in-shlibs.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: outdated-relation-in-shlibs +Ref: policy 7.1 +Severity: warning +Check: shared-libs +Renamed-From: shlibs-uses-obsolete-relation +Info: The forms "<" and ">" mean "<=" and ">=", not "<<" + and ">>" as one might expect. For that reason these forms are + obsolete, and should not be used in new packages. Use the longer forms + instead. diff -Nru lintian-2.93.0/tags/o/outdated-relation-in-shlibs.tag lintian-2.89.0ubuntu1/tags/o/outdated-relation-in-shlibs.tag --- lintian-2.93.0/tags/o/outdated-relation-in-shlibs.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/o/outdated-relation-in-shlibs.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: outdated-relation-in-shlibs -See-Also: policy 7.1 -Severity: warning -Check: shared-libs -Renamed-From: shlibs-uses-obsolete-relation -Explanation: The forms "<" and ">" mean "<=" and ">=", not "<<" - and ">>" as one might expect. For that reason these forms are - obsolete, and should not be used in new packages. Use the longer forms - instead. diff -Nru lintian-2.93.0/tags/o/out-of-date-copyright-format-uri.desc lintian-2.89.0ubuntu1/tags/o/out-of-date-copyright-format-uri.desc --- lintian-2.93.0/tags/o/out-of-date-copyright-format-uri.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/o/out-of-date-copyright-format-uri.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: out-of-date-copyright-format-uri +Severity: pedantic +Certainty: possible +Check: debian/copyright/dep5 +Ref: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ +Info: A newer version of the machine-readable copyright file specification, + than the one referenced by the copyright file, is available. + . + This problem may have prevented Lintian from performing other checks. diff -Nru lintian-2.93.0/tags/o/out-of-date-copyright-format-uri.tag lintian-2.89.0ubuntu1/tags/o/out-of-date-copyright-format-uri.tag --- lintian-2.93.0/tags/o/out-of-date-copyright-format-uri.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/o/out-of-date-copyright-format-uri.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: out-of-date-copyright-format-uri -Severity: pedantic -Check: debian/copyright/dep5 -See-Also: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ -Explanation: A newer version of the machine-readable copyright file specification, - than the one referenced by the copyright file, is available. - . - This problem may have prevented Lintian from performing other checks. diff -Nru lintian-2.93.0/tags/o/out-of-date-standards-version.desc lintian-2.89.0ubuntu1/tags/o/out-of-date-standards-version.desc --- lintian-2.93.0/tags/o/out-of-date-standards-version.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/o/out-of-date-standards-version.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,18 @@ +Tag: out-of-date-standards-version +Severity: info +Check: fields/standards-version +Ref: https://www.debian.org/doc/debian-policy/upgrading-checklist.html +Info: The source package refers to a Standards-Version older than the one + that was current at the time the package was created (according to the + timestamp of the latest debian/changelog entry). Please + consider updating the package to current Policy and setting this control + field appropriately. + . + If the package is already compliant with the current standards, you don't + have to re-upload the package just to adjust the Standards-Version + control field. However, please remember to update this field next time + you upload the package. + . + See /usr/share/doc/debian-policy/upgrading-checklist.txt.gz in + the debian-policy package for a summary of changes in newer versions of + Policy. diff -Nru lintian-2.93.0/tags/o/out-of-date-standards-version.tag lintian-2.89.0ubuntu1/tags/o/out-of-date-standards-version.tag --- lintian-2.93.0/tags/o/out-of-date-standards-version.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/o/out-of-date-standards-version.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,18 +0,0 @@ -Tag: out-of-date-standards-version -Severity: info -Check: fields/standards-version -See-Also: https://www.debian.org/doc/debian-policy/upgrading-checklist.html -Explanation: The source package refers to a Standards-Version older than the one - that was current at the time the package was created (according to the - timestamp of the latest debian/changelog entry). Please - consider updating the package to current Policy and setting this control - field appropriately. - . - If the package is already compliant with the current standards, you don't - have to re-upload the package just to adjust the Standards-Version - control field. However, please remember to update this field next time - you upload the package. - . - See /usr/share/doc/debian-policy/upgrading-checklist.txt.gz in - the debian-policy package for a summary of changes in newer versions of - Policy. diff -Nru lintian-2.93.0/tags/o/output-of-updaterc.d-not-redirected-to-dev-null.desc lintian-2.89.0ubuntu1/tags/o/output-of-updaterc.d-not-redirected-to-dev-null.desc --- lintian-2.93.0/tags/o/output-of-updaterc.d-not-redirected-to-dev-null.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/o/output-of-updaterc.d-not-redirected-to-dev-null.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: output-of-updaterc.d-not-redirected-to-dev-null +Severity: info +Check: init.d +Info: The output messages of the update-rc.d command should be + redirected to /dev/null because it is currently very chatty + per default. diff -Nru lintian-2.93.0/tags/o/output-of-updaterc.d-not-redirected-to-dev-null.tag lintian-2.89.0ubuntu1/tags/o/output-of-updaterc.d-not-redirected-to-dev-null.tag --- lintian-2.93.0/tags/o/output-of-updaterc.d-not-redirected-to-dev-null.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/o/output-of-updaterc.d-not-redirected-to-dev-null.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: output-of-updaterc.d-not-redirected-to-dev-null -Severity: info -Check: init.d -Explanation: The output messages of the update-rc.d command should be - redirected to /dev/null because it is currently very chatty - per default. diff -Nru lintian-2.93.0/tags/o/override_dh_auto_test-does-not-check-DEB_BUILD_OPTIONS.desc lintian-2.89.0ubuntu1/tags/o/override_dh_auto_test-does-not-check-DEB_BUILD_OPTIONS.desc --- lintian-2.93.0/tags/o/override_dh_auto_test-does-not-check-DEB_BUILD_OPTIONS.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/o/override_dh_auto_test-does-not-check-DEB_BUILD_OPTIONS.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,30 @@ +Tag: override_dh_auto_test-does-not-check-DEB_BUILD_OPTIONS +Severity: info +Certainty: wild-guess +Check: debian/rules +Info: The debian/rules file for this package has an + override_dh_auto_test target that does not appear to + check DEB_BUILD_OPTIONS against nocheck. + . + As this check is not automatically performed by debhelper(1), the + specified testsuite is run regardless of another maintainer using + the nocheck build option. + . + Please add a check such as: + . + override_dh_auto_test: + ifeq (,$(filter nocheck,$(DEB_BUILD_OPTIONS))) + ./run-upstream-testsuite + endif + . + Lintian will ignore comments and other lines such as: + . + # Disabled + : Disabled + echo "Disabled" + mkdir foo/ + ENV=var dh_auto_test -- ARG=value + . + This check is not required in Debhelper compat level 13 or greater + (see #568897). +Ref: policy 4.9.1, https://wiki.debian.org/BuildProfileSpec#Registered_profile_names diff -Nru lintian-2.93.0/tags/o/override_dh_auto_test-does-not-check-DEB_BUILD_OPTIONS.tag lintian-2.89.0ubuntu1/tags/o/override_dh_auto_test-does-not-check-DEB_BUILD_OPTIONS.tag --- lintian-2.93.0/tags/o/override_dh_auto_test-does-not-check-DEB_BUILD_OPTIONS.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/o/override_dh_auto_test-does-not-check-DEB_BUILD_OPTIONS.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,29 +0,0 @@ -Tag: override_dh_auto_test-does-not-check-DEB_BUILD_OPTIONS -Severity: info -Check: debian/rules -Explanation: The debian/rules file for this package has an - override_dh_auto_test target that does not appear to - check DEB_BUILD_OPTIONS against nocheck. - . - As this check is not automatically performed by debhelper(1), the - specified testsuite is run regardless of another maintainer using - the nocheck build option. - . - Please add a check such as: - . - override_dh_auto_test: - ifeq (,$(filter nocheck,$(DEB_BUILD_OPTIONS))) - ./run-upstream-testsuite - endif - . - Lintian will ignore comments and other lines such as: - . - # Disabled - : Disabled - echo "Disabled" - mkdir foo/ - ENV=var dh_auto_test -- ARG=value - . - This check is not required in Debhelper compat level 13 or greater - (see Bug#568897). -See-Also: policy 4.9.1, https://wiki.debian.org/BuildProfileSpec#Registered_profile_names diff -Nru lintian-2.93.0/tags/o/override_dh_clean-does-not-call-dh_clean.desc lintian-2.89.0ubuntu1/tags/o/override_dh_clean-does-not-call-dh_clean.desc --- lintian-2.93.0/tags/o/override_dh_clean-does-not-call-dh_clean.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/o/override_dh_clean-does-not-call-dh_clean.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,11 @@ +Tag: override_dh_clean-does-not-call-dh_clean +Severity: warning +Check: debian/rules +Info: The debian/rules file for this package has an + override_dh_clean target that does not reference dh_clean. + . + This can result in packages not cleaning up properly via debian/rules + clean. + . + Please add a call to dh_clean. +Ref: #884419, #884815 diff -Nru lintian-2.93.0/tags/o/override_dh_clean-does-not-call-dh_clean.tag lintian-2.89.0ubuntu1/tags/o/override_dh_clean-does-not-call-dh_clean.tag --- lintian-2.93.0/tags/o/override_dh_clean-does-not-call-dh_clean.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/o/override_dh_clean-does-not-call-dh_clean.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,11 +0,0 @@ -Tag: override_dh_clean-does-not-call-dh_clean -Severity: warning -Check: debian/rules -Explanation: The debian/rules file for this package has an - override_dh_clean target that does not reference dh_clean. - . - This can result in packages not cleaning up properly via debian/rules - clean. - . - Please add a call to dh_clean. -See-Also: Bug#884419, Bug#884815 diff -Nru lintian-2.93.0/tags/o/override_dh_fixperms-does-not-call-dh_fixperms.desc lintian-2.89.0ubuntu1/tags/o/override_dh_fixperms-does-not-call-dh_fixperms.desc --- lintian-2.93.0/tags/o/override_dh_fixperms-does-not-call-dh_fixperms.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/o/override_dh_fixperms-does-not-call-dh_fixperms.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,12 @@ +Tag: override_dh_fixperms-does-not-call-dh_fixperms +Severity: warning +Check: debian/rules +Info: The debian/rules file for this package has an + override_dh_fixperms target that does not reference + dh_fixperms. + . + This can result in packages inheriting the umask(2) of the build + process, rendering the package unreproducible. + . + Please add a call to dh_fixperms. +Ref: #885909 diff -Nru lintian-2.93.0/tags/o/override_dh_fixperms-does-not-call-dh_fixperms.tag lintian-2.89.0ubuntu1/tags/o/override_dh_fixperms-does-not-call-dh_fixperms.tag --- lintian-2.93.0/tags/o/override_dh_fixperms-does-not-call-dh_fixperms.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/o/override_dh_fixperms-does-not-call-dh_fixperms.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,12 +0,0 @@ -Tag: override_dh_fixperms-does-not-call-dh_fixperms -Severity: warning -Check: debian/rules -Explanation: The debian/rules file for this package has an - override_dh_fixperms target that does not reference - dh_fixperms. - . - This can result in packages inheriting the umask(2) of the build - process, rendering the package unreproducible. - . - Please add a call to dh_fixperms. -See-Also: Bug#885909 diff -Nru lintian-2.93.0/tags/o/override-file-in-wrong-location.desc lintian-2.89.0ubuntu1/tags/o/override-file-in-wrong-location.desc --- lintian-2.93.0/tags/o/override-file-in-wrong-location.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/o/override-file-in-wrong-location.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: override-file-in-wrong-location +Severity: error +Check: debian/lintian-overrides +Info: Lintian overrides should be put in a regular file named + /usr/share/lintian/overrides/package, not in a subdirectory + named for the package or in the obsolete location under /usr/share/doc. + See the Lintian documentation for more information on proper naming and + format. +Ref: lintian 2.4 diff -Nru lintian-2.93.0/tags/o/override-file-in-wrong-location.tag lintian-2.89.0ubuntu1/tags/o/override-file-in-wrong-location.tag --- lintian-2.93.0/tags/o/override-file-in-wrong-location.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/o/override-file-in-wrong-location.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: override-file-in-wrong-location -Severity: error -Check: debian/lintian-overrides -Explanation: Lintian overrides should be put in a regular file named - /usr/share/lintian/overrides/package, not in a subdirectory - named for the package or in the obsolete location under /usr/share/doc. - See the Lintian documentation for more information on proper naming and - format. -See-Also: lintian 2.4 diff -Nru lintian-2.93.0/tags/o/override-file-in-wrong-package.desc lintian-2.89.0ubuntu1/tags/o/override-file-in-wrong-package.desc --- lintian-2.93.0/tags/o/override-file-in-wrong-package.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/o/override-file-in-wrong-package.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: override-file-in-wrong-package +Severity: error +Check: debian/lintian-overrides +Info: This package includes Lintian overrides intended for another package. + Lintian overrides should be put in a regular file named + /usr/share/lintian/overrides/package +Ref: lintian 2.4 diff -Nru lintian-2.93.0/tags/o/override-file-in-wrong-package.tag lintian-2.89.0ubuntu1/tags/o/override-file-in-wrong-package.tag --- lintian-2.93.0/tags/o/override-file-in-wrong-package.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/o/override-file-in-wrong-package.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: override-file-in-wrong-package -Severity: error -Check: debian/lintian-overrides -Explanation: This package includes Lintian overrides intended for another package. - Lintian overrides should be put in a regular file named - /usr/share/lintian/overrides/package -See-Also: lintian 2.4 diff -Nru lintian-2.93.0/tags/p/package-builds-dbg-and-dbgsym-variants.desc lintian-2.89.0ubuntu1/tags/p/package-builds-dbg-and-dbgsym-variants.desc --- lintian-2.93.0/tags/p/package-builds-dbg-and-dbgsym-variants.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-builds-dbg-and-dbgsym-variants.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: package-builds-dbg-and-dbgsym-variants +Severity: warning +Check: changes-file +Ref: dh_strip(1), https://wiki.debian.org/AutomaticDebugPackages +Info: This package appears to build both -dbg and -dbgsym variants of a + package. Only one package should contain the debug symbols + . + Usually the -dbg should be dropped in favour of the -dbgsym. However, + in some cases (e.g. Python modules) the -dbg contains more than just + the debug symbols. In these cases the -dbgsym should not be built. diff -Nru lintian-2.93.0/tags/p/package-builds-dbg-and-dbgsym-variants.tag lintian-2.89.0ubuntu1/tags/p/package-builds-dbg-and-dbgsym-variants.tag --- lintian-2.93.0/tags/p/package-builds-dbg-and-dbgsym-variants.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-builds-dbg-and-dbgsym-variants.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,10 +0,0 @@ -Tag: package-builds-dbg-and-dbgsym-variants -Severity: warning -Check: changes-file -See-Also: dh_strip(1), https://wiki.debian.org/AutomaticDebugPackages -Explanation: This package appears to build both -dbg and -dbgsym variants of a - package. Only one package should contain the debug symbols - . - Usually the -dbg should be dropped in favour of the -dbgsym. However, - in some cases (e.g. Python modules) the -dbg contains more than just - the debug symbols. In these cases the -dbgsym should not be built. diff -Nru lintian-2.93.0/tags/p/package-contains-ancient-file.desc lintian-2.89.0ubuntu1/tags/p/package-contains-ancient-file.desc --- lintian-2.93.0/tags/p/package-contains-ancient-file.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-contains-ancient-file.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: package-contains-ancient-file +Severity: error +Check: files/date +Info: Your package contains a file that claims to have been generated + more than 20 years ago. This is most probably an error. Your package + will be rejected by the Debian archive scripts if it contains a file + with such a timestamp. diff -Nru lintian-2.93.0/tags/p/package-contains-ancient-file.tag lintian-2.89.0ubuntu1/tags/p/package-contains-ancient-file.tag --- lintian-2.93.0/tags/p/package-contains-ancient-file.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-contains-ancient-file.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: package-contains-ancient-file -Severity: error -Check: files/date -Explanation: Your package contains a file that claims to have been generated - more than 20 years ago. This is most probably an error. Your package - will be rejected by the Debian archive scripts if it contains a file - with such a timestamp. diff -Nru lintian-2.93.0/tags/p/package-contains-broken-symlink-wildcard.desc lintian-2.89.0ubuntu1/tags/p/package-contains-broken-symlink-wildcard.desc --- lintian-2.93.0/tags/p/package-contains-broken-symlink-wildcard.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-contains-broken-symlink-wildcard.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: package-contains-broken-symlink-wildcard +Severity: warning +Certainty: possible +Check: files/symbolic-links/broken +Info: The package contains a symlink with a target that + appears to be a "failed" wildcard expansion. Furthermore + the target does not exists in the package or any of its + direct dependencies (built from the same source package). diff -Nru lintian-2.93.0/tags/p/package-contains-broken-symlink-wildcard.tag lintian-2.89.0ubuntu1/tags/p/package-contains-broken-symlink-wildcard.tag --- lintian-2.93.0/tags/p/package-contains-broken-symlink-wildcard.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-contains-broken-symlink-wildcard.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: package-contains-broken-symlink-wildcard -Severity: warning -Check: files/symbolic-links/broken -Explanation: The package contains a symlink with a target that - appears to be a "failed" wildcard expansion. Furthermore - the target does not exists in the package or any of its - direct dependencies (built from the same source package). diff -Nru lintian-2.93.0/tags/p/package-contains-bts-control-dir.desc lintian-2.89.0ubuntu1/tags/p/package-contains-bts-control-dir.desc --- lintian-2.93.0/tags/p/package-contains-bts-control-dir.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-contains-bts-control-dir.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: package-contains-bts-control-dir +Severity: warning +Check: files/bugs +Info: The package contains a control directory for a bug tracking system. + It was most likely installed by accident, since bug tracking directories + usually don't belong in packages. diff -Nru lintian-2.93.0/tags/p/package-contains-bts-control-dir.tag lintian-2.89.0ubuntu1/tags/p/package-contains-bts-control-dir.tag --- lintian-2.93.0/tags/p/package-contains-bts-control-dir.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-contains-bts-control-dir.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: package-contains-bts-control-dir -Severity: warning -Check: files/bugs -Explanation: The package contains a control directory for a bug tracking system. - It was most likely installed by accident, since bug tracking directories - usually don't belong in packages. diff -Nru lintian-2.93.0/tags/p/package-contains-cmake-private-file.desc lintian-2.89.0ubuntu1/tags/p/package-contains-cmake-private-file.desc --- lintian-2.93.0/tags/p/package-contains-cmake-private-file.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-contains-cmake-private-file.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,13 @@ +Tag: package-contains-cmake-private-file +Severity: error +Check: build-systems/cmake +Info: The package ships a file in a location reserved for CMake. + It usually means you shipped a Find module. + . + Libraries should not ship Find modules Config files. Config files should + be installed in the unversioned path + usr/(lib/<arch>|lib|share)/cmake/<name>*/ + . + When CMake Config files are installed in an unversioned path, your + package will continue to work when a new version of CMake is uploaded. +Ref: https://wiki.debian.org/CMake, https://cmake.org/cmake/help/v3.10/manual/cmake-packages.7.html#config-file-packages diff -Nru lintian-2.93.0/tags/p/package-contains-cmake-private-file.tag lintian-2.89.0ubuntu1/tags/p/package-contains-cmake-private-file.tag --- lintian-2.93.0/tags/p/package-contains-cmake-private-file.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-contains-cmake-private-file.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,13 +0,0 @@ -Tag: package-contains-cmake-private-file -Severity: error -Check: build-systems/cmake -Explanation: The package ships a file in a location reserved for CMake. - It usually means you shipped a Find module. - . - Libraries should not ship Find modules Config files. Config files should - be installed in the unversioned path - usr/(lib/<arch>|lib|share)/cmake/<name>*/ - . - When CMake Config files are installed in an unversioned path, your - package will continue to work when a new version of CMake is uploaded. -See-Also: https://wiki.debian.org/CMake, https://cmake.org/cmake/help/v3.10/manual/cmake-packages.7.html#config-file-packages diff -Nru lintian-2.93.0/tags/p/package-contains-compiled-font-file.desc lintian-2.89.0ubuntu1/tags/p/package-contains-compiled-font-file.desc --- lintian-2.93.0/tags/p/package-contains-compiled-font-file.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-contains-compiled-font-file.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: package-contains-compiled-font-file +Severity: error +Check: desktop/x11 +Info: This package appears to contain a compiled font file. These files + should be generated automatically by triggers and it must not be shipped + in any package. diff -Nru lintian-2.93.0/tags/p/package-contains-compiled-font-file.tag lintian-2.89.0ubuntu1/tags/p/package-contains-compiled-font-file.tag --- lintian-2.93.0/tags/p/package-contains-compiled-font-file.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-contains-compiled-font-file.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: package-contains-compiled-font-file -Severity: error -Check: desktop/x11 -Explanation: This package appears to contain a compiled font file. These files - should be generated automatically by triggers and it must not be shipped - in any package. diff -Nru lintian-2.93.0/tags/p/package-contains-compiled-glib-schema.desc lintian-2.89.0ubuntu1/tags/p/package-contains-compiled-glib-schema.desc --- lintian-2.93.0/tags/p/package-contains-compiled-glib-schema.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-contains-compiled-glib-schema.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: package-contains-compiled-glib-schema +Severity: error +Check: files/names +Info: This package contains a file named gschemas.compiled. This + file is generated automatically by triggers and it must not be shipped in + any package. +Ref: Bug#883801 diff -Nru lintian-2.93.0/tags/p/package-contains-compiled-glib-schema.tag lintian-2.89.0ubuntu1/tags/p/package-contains-compiled-glib-schema.tag --- lintian-2.93.0/tags/p/package-contains-compiled-glib-schema.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-contains-compiled-glib-schema.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: package-contains-compiled-glib-schema -Severity: error -Check: files/names -Explanation: This package contains a file named gschemas.compiled. This - file is generated automatically by triggers and it must not be shipped in - any package. -See-Also: Bug#883801 diff -Nru lintian-2.93.0/tags/p/package-contains-devhelp-file-without-symlink.desc lintian-2.89.0ubuntu1/tags/p/package-contains-devhelp-file-without-symlink.desc --- lintian-2.93.0/tags/p/package-contains-devhelp-file-without-symlink.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-contains-devhelp-file-without-symlink.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,12 @@ +Tag: package-contains-devhelp-file-without-symlink +Severity: warning +Check: files/devhelp +Info: This package contains a *.devhelp or *.devhelp2 file which is not in + the devhelp search path (/usr/share/devhelp/books and + /usr/share/gtk-doc/html) and is apparently not in a directory + linked into the devhelp search path. This will prevent devhelp from + finding the documentation. + . + If the devhelp documentation is installed in a path outside the devhelp + search path (such as /usr/share/doc), create a symlink in + /usr/share/gtk-doc/html pointing to the documentation directory. diff -Nru lintian-2.93.0/tags/p/package-contains-devhelp-file-without-symlink.tag lintian-2.89.0ubuntu1/tags/p/package-contains-devhelp-file-without-symlink.tag --- lintian-2.93.0/tags/p/package-contains-devhelp-file-without-symlink.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-contains-devhelp-file-without-symlink.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,12 +0,0 @@ -Tag: package-contains-devhelp-file-without-symlink -Severity: warning -Check: files/devhelp -Explanation: This package contains a *.devhelp or *.devhelp2 file which is not in - the devhelp search path (/usr/share/devhelp/books and - /usr/share/gtk-doc/html) and is apparently not in a directory - linked into the devhelp search path. This will prevent devhelp from - finding the documentation. - . - If the devhelp documentation is installed in a path outside the devhelp - search path (such as /usr/share/doc), create a symlink in - /usr/share/gtk-doc/html pointing to the documentation directory. diff -Nru lintian-2.93.0/tags/p/package-contains-documentation-outside-usr-share-doc.desc lintian-2.89.0ubuntu1/tags/p/package-contains-documentation-outside-usr-share-doc.desc --- lintian-2.93.0/tags/p/package-contains-documentation-outside-usr-share-doc.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-contains-documentation-outside-usr-share-doc.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,11 @@ +Tag: package-contains-documentation-outside-usr-share-doc +Severity: info +Certainty: wild-guess +Check: documentation +Info: This package ships a documentation file outside /usr/share/doc + Documentation files are normally installed inside /usr/share/doc. + . + If this file doesn't describe the contents or purpose of the directory + it is in, please consider moving this file to /usr/share/doc/ + or maybe even removing it. If this file does describe the contents + or purpose of the directory it is in, please add a lintian override. diff -Nru lintian-2.93.0/tags/p/package-contains-documentation-outside-usr-share-doc.tag lintian-2.89.0ubuntu1/tags/p/package-contains-documentation-outside-usr-share-doc.tag --- lintian-2.93.0/tags/p/package-contains-documentation-outside-usr-share-doc.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-contains-documentation-outside-usr-share-doc.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,10 +0,0 @@ -Tag: package-contains-documentation-outside-usr-share-doc -Severity: info -Check: documentation -Explanation: This package ships a documentation file outside /usr/share/doc - Documentation files are normally installed inside /usr/share/doc. - . - If this file doesn't describe the contents or purpose of the directory - it is in, please consider moving this file to /usr/share/doc/ - or maybe even removing it. If this file does describe the contents - or purpose of the directory it is in, please add a lintian override. diff -Nru lintian-2.93.0/tags/p/package-contains-empty-directory.desc lintian-2.89.0ubuntu1/tags/p/package-contains-empty-directory.desc --- lintian-2.93.0/tags/p/package-contains-empty-directory.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-contains-empty-directory.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,11 @@ +Tag: package-contains-empty-directory +Severity: info +Certainty: possible +Check: files/empty-directories +Info: This package installs an empty directory. This might be intentional + but it's normally a mistake. If it is intentional, add a Lintian override. + . + If a package ships with or installs empty directories, you can remove them + in debian/rules by calling: + . + $ find path/to/base/dir -type d -empty -delete diff -Nru lintian-2.93.0/tags/p/package-contains-empty-directory.tag lintian-2.89.0ubuntu1/tags/p/package-contains-empty-directory.tag --- lintian-2.93.0/tags/p/package-contains-empty-directory.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-contains-empty-directory.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,10 +0,0 @@ -Tag: package-contains-empty-directory -Severity: info -Check: files/empty-directories -Explanation: This package installs an empty directory. This might be intentional - but it's normally a mistake. If it is intentional, add a Lintian override. - . - If a package ships with or installs empty directories, you can remove them - in debian/rules by calling: - . - $ find path/to/base/dir -type d -empty -delete diff -Nru lintian-2.93.0/tags/p/package-contains-eslint-config-file.desc lintian-2.89.0ubuntu1/tags/p/package-contains-eslint-config-file.desc --- lintian-2.93.0/tags/p/package-contains-eslint-config-file.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-contains-eslint-config-file.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,11 @@ +Tag: package-contains-eslint-config-file +Severity: error +Check: files/names +Info: This package ships an ESLint config file. This file is + a configuration file for the ESLint pluggable linting utility + for JavaScript. + . + Even if these files are useful for modifying the source, + they do not belong in installed packages. + . + Please remove this file from your package. diff -Nru lintian-2.93.0/tags/p/package-contains-eslint-config-file.tag lintian-2.89.0ubuntu1/tags/p/package-contains-eslint-config-file.tag --- lintian-2.93.0/tags/p/package-contains-eslint-config-file.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-contains-eslint-config-file.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,11 +0,0 @@ -Tag: package-contains-eslint-config-file -Severity: error -Check: files/names -Explanation: This package ships an ESLint config file. This file is - a configuration file for the ESLint pluggable linting utility - for JavaScript. - . - Even if these files are useful for modifying the source, - they do not belong in installed packages. - . - Please remove this file from your package. diff -Nru lintian-2.93.0/tags/p/package-contains-file-in-etc-skel.desc lintian-2.89.0ubuntu1/tags/p/package-contains-file-in-etc-skel.desc --- lintian-2.93.0/tags/p/package-contains-file-in-etc-skel.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-contains-file-in-etc-skel.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,13 @@ +Tag: package-contains-file-in-etc-skel +Severity: error +Check: files/names +Info: This package ships the specified file under /etc/skel. Files + in this directory are copied into new user accounts by adduser(8). + . + However, /etc/skel should be empty as possible as there is no + mechanism for ensuring files are copied into the accounts of existing + users when the package is installed. + . + Please remove the installation of this file, ensuring this package + can automatically create them or can otherwise function without them. +Ref: policy 10.7.5 diff -Nru lintian-2.93.0/tags/p/package-contains-file-in-etc-skel.tag lintian-2.89.0ubuntu1/tags/p/package-contains-file-in-etc-skel.tag --- lintian-2.93.0/tags/p/package-contains-file-in-etc-skel.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-contains-file-in-etc-skel.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,13 +0,0 @@ -Tag: package-contains-file-in-etc-skel -Severity: error -Check: files/names -Explanation: This package ships the specified file under /etc/skel. Files - in this directory are copied into new user accounts by adduser(8). - . - However, /etc/skel should be empty as possible as there is no - mechanism for ensuring files are copied into the accounts of existing - users when the package is installed. - . - Please remove the installation of this file, ensuring this package - can automatically create them or can otherwise function without them. -See-Also: policy 10.7.5 diff -Nru lintian-2.93.0/tags/p/package-contains-file-in-usr-share-hal.desc lintian-2.89.0ubuntu1/tags/p/package-contains-file-in-usr-share-hal.desc --- lintian-2.93.0/tags/p/package-contains-file-in-usr-share-hal.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-contains-file-in-usr-share-hal.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: package-contains-file-in-usr-share-hal +Severity: warning +Check: files/names +Info: This package installs the specified file under + /usr/share/hal/ but this directory is no longer looked at + by any package in Debian since the removal of the hal package + in 2014. + . + Please remove or otherwise prevent the installation of this file. diff -Nru lintian-2.93.0/tags/p/package-contains-file-in-usr-share-hal.tag lintian-2.89.0ubuntu1/tags/p/package-contains-file-in-usr-share-hal.tag --- lintian-2.93.0/tags/p/package-contains-file-in-usr-share-hal.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-contains-file-in-usr-share-hal.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: package-contains-file-in-usr-share-hal -Severity: warning -Check: files/names -Explanation: This package installs the specified file under - /usr/share/hal/ but this directory is no longer looked at - by any package in Debian since the removal of the hal package - in 2014. - . - Please remove or otherwise prevent the installation of this file. diff -Nru lintian-2.93.0/tags/p/package-contains-hardlink.desc lintian-2.89.0ubuntu1/tags/p/package-contains-hardlink.desc --- lintian-2.93.0/tags/p/package-contains-hardlink.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-contains-hardlink.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,14 @@ +Tag: package-contains-hardlink +Severity: warning +Check: files/hard-links +Info: The package contains a hardlink in /etc or across different + directories. This might not work at all if directories are on different + filesystems (which can happen anytime as the system administrator sees fit), + certain filesystems such as AFS don't even support cross-directory hardlinks + at all. + . + For configuration files, certain editors might break hardlinks, and so + does dpkg in certain cases. + . + A better solution might be using symlinks here. +Ref: policy 10.7.3 diff -Nru lintian-2.93.0/tags/p/package-contains-hardlink.tag lintian-2.89.0ubuntu1/tags/p/package-contains-hardlink.tag --- lintian-2.93.0/tags/p/package-contains-hardlink.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-contains-hardlink.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,14 +0,0 @@ -Tag: package-contains-hardlink -Severity: warning -Check: files/hard-links -Explanation: The package contains a hardlink in /etc or across different - directories. This might not work at all if directories are on different - filesystems (which can happen anytime as the system administrator sees fit), - certain filesystems such as AFS don't even support cross-directory hardlinks - at all. - . - For configuration files, certain editors might break hardlinks, and so - does dpkg in certain cases. - . - A better solution might be using symlinks here. -See-Also: policy 10.7.3 diff -Nru lintian-2.93.0/tags/p/package-contains-icon-cache-in-generic-dir.desc lintian-2.89.0ubuntu1/tags/p/package-contains-icon-cache-in-generic-dir.desc --- lintian-2.93.0/tags/p/package-contains-icon-cache-in-generic-dir.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-contains-icon-cache-in-generic-dir.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: package-contains-icon-cache-in-generic-dir +Severity: warning +Check: files/names +Info: This package installs the specified icon cache in a generic + location such as /usr/share/icons/hicolor which will + invariably clash with other packages. + . + Please remove or otherwise prevent the installation of this file. diff -Nru lintian-2.93.0/tags/p/package-contains-icon-cache-in-generic-dir.tag lintian-2.89.0ubuntu1/tags/p/package-contains-icon-cache-in-generic-dir.tag --- lintian-2.93.0/tags/p/package-contains-icon-cache-in-generic-dir.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-contains-icon-cache-in-generic-dir.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: package-contains-icon-cache-in-generic-dir -Severity: warning -Check: files/names -Explanation: This package installs the specified icon cache in a generic - location such as /usr/share/icons/hicolor which will - invariably clash with other packages. - . - Please remove or otherwise prevent the installation of this file. diff -Nru lintian-2.93.0/tags/p/package-contains-info-dir-file.desc lintian-2.89.0ubuntu1/tags/p/package-contains-info-dir-file.desc --- lintian-2.93.0/tags/p/package-contains-info-dir-file.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-contains-info-dir-file.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: package-contains-info-dir-file +Severity: error +Check: documentation +Info: This package contains a file named dir or dir.old, + possibly compressed, in /usr/share/info. This is the directory + (or backup) of info pages and is generated automatically by install-info + when a package containing info documentation is installed. Some upstream + build systems create it automatically, but it must not be included in a + package since it needs to be generated dynamically based on the installed + info files on the system. diff -Nru lintian-2.93.0/tags/p/package-contains-info-dir-file.tag lintian-2.89.0ubuntu1/tags/p/package-contains-info-dir-file.tag --- lintian-2.93.0/tags/p/package-contains-info-dir-file.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-contains-info-dir-file.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,10 +0,0 @@ -Tag: package-contains-info-dir-file -Severity: error -Check: documentation -Explanation: This package contains a file named dir or dir.old, - possibly compressed, in /usr/share/info. This is the directory - (or backup) of info pages and is generated automatically by install-info - when a package containing info documentation is installed. Some upstream - build systems create it automatically, but it must not be included in a - package since it needs to be generated dynamically based on the installed - info files on the system. diff -Nru lintian-2.93.0/tags/p/package-contains-linda-override.desc lintian-2.89.0ubuntu1/tags/p/package-contains-linda-override.desc --- lintian-2.93.0/tags/p/package-contains-linda-override.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-contains-linda-override.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: package-contains-linda-override +Severity: warning +Check: linda +Info: This package contains a linda override file in + /usr/share/linda/overrides. Linda is obsolete and has been + removed from the archive as of 2008-03-04. Linda overrides should + probably be dropped from packages. diff -Nru lintian-2.93.0/tags/p/package-contains-linda-override.tag lintian-2.89.0ubuntu1/tags/p/package-contains-linda-override.tag --- lintian-2.93.0/tags/p/package-contains-linda-override.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-contains-linda-override.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: package-contains-linda-override -Severity: warning -Check: linda -Explanation: This package contains a linda override file in - /usr/share/linda/overrides. Linda is obsolete and has been - removed from the archive as of 2008-03-04. Linda overrides should - probably be dropped from packages. diff -Nru lintian-2.93.0/tags/p/package-contains-mime-cache-file.desc lintian-2.89.0ubuntu1/tags/p/package-contains-mime-cache-file.desc --- lintian-2.93.0/tags/p/package-contains-mime-cache-file.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-contains-mime-cache-file.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: package-contains-mime-cache-file +Severity: error +Check: mimeinfo +Info: This package contains a cache file generated automatically by + update-mime-database when a package containing MIME-Info Database + files is installed. Some upstream build systems create them + automatically, but they must not be included in a package since they need + to be generated dynamically based on the installed MIME-Info Database + files on the system. diff -Nru lintian-2.93.0/tags/p/package-contains-mime-cache-file.tag lintian-2.89.0ubuntu1/tags/p/package-contains-mime-cache-file.tag --- lintian-2.93.0/tags/p/package-contains-mime-cache-file.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-contains-mime-cache-file.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: package-contains-mime-cache-file -Severity: error -Check: mimeinfo -Explanation: This package contains a cache file generated automatically by - update-mime-database when a package containing MIME-Info Database - files is installed. Some upstream build systems create them - automatically, but they must not be included in a package since they need - to be generated dynamically based on the installed MIME-Info Database - files on the system. diff -Nru lintian-2.93.0/tags/p/package-contains-mime-file-outside-package-dir.desc lintian-2.89.0ubuntu1/tags/p/package-contains-mime-file-outside-package-dir.desc --- lintian-2.93.0/tags/p/package-contains-mime-file-outside-package-dir.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-contains-mime-file-outside-package-dir.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: package-contains-mime-file-outside-package-dir +Severity: error +Check: mimeinfo +Ref: #761649, /usr/share/doc/shared-mime-info/ +Info: This package contains a file in a path reserved solely for + mime cache file. + . + /usr/share/mime/ files are cache generated from + /usr/share/mime/packages/. Thus file under /usr/share/mime/ + should not be installed diff -Nru lintian-2.93.0/tags/p/package-contains-mime-file-outside-package-dir.tag lintian-2.89.0ubuntu1/tags/p/package-contains-mime-file-outside-package-dir.tag --- lintian-2.93.0/tags/p/package-contains-mime-file-outside-package-dir.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-contains-mime-file-outside-package-dir.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,10 +0,0 @@ -Tag: package-contains-mime-file-outside-package-dir -Severity: error -Check: mimeinfo -See-Also: Bug#761649, /usr/share/doc/shared-mime-info/ -Explanation: This package contains a file in a path reserved solely for - mime cache file. - . - /usr/share/mime/ files are cache generated from - /usr/share/mime/packages/. Thus file under /usr/share/mime/ - should not be installed diff -Nru lintian-2.93.0/tags/p/package-contains-mimeinfo.cache-file.desc lintian-2.89.0ubuntu1/tags/p/package-contains-mimeinfo.cache-file.desc --- lintian-2.93.0/tags/p/package-contains-mimeinfo.cache-file.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-contains-mimeinfo.cache-file.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: package-contains-mimeinfo.cache-file +Severity: error +Check: mimeinfo +Info: This package contains a file named mimeinfo.cache, + possibly compressed, in /usr/share/applications. This file is + generated automatically by update-desktop-database when a package + containing .desktop files associated to MIME types is installed. + Some upstream build systems create it automatically, but it must not be + included in a package since it needs to be generated dynamically based on + the installed .desktop files on the system. diff -Nru lintian-2.93.0/tags/p/package-contains-mimeinfo.cache-file.tag lintian-2.89.0ubuntu1/tags/p/package-contains-mimeinfo.cache-file.tag --- lintian-2.93.0/tags/p/package-contains-mimeinfo.cache-file.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-contains-mimeinfo.cache-file.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,10 +0,0 @@ -Tag: package-contains-mimeinfo.cache-file -Severity: error -Check: mimeinfo -Explanation: This package contains a file named mimeinfo.cache, - possibly compressed, in /usr/share/applications. This file is - generated automatically by update-desktop-database when a package - containing .desktop files associated to MIME types is installed. - Some upstream build systems create it automatically, but it must not be - included in a package since it needs to be generated dynamically based on - the installed .desktop files on the system. diff -Nru lintian-2.93.0/tags/p/package-contains-multiple-dpi-fonts.desc lintian-2.89.0ubuntu1/tags/p/package-contains-multiple-dpi-fonts.desc --- lintian-2.93.0/tags/p/package-contains-multiple-dpi-fonts.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-contains-multiple-dpi-fonts.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: package-contains-multiple-dpi-fonts +Severity: warning +Check: desktop/x11 +Ref: policy 11.8.5 +Info: This package contains both 100dpi and 75dpi bitmapped fonts. Both + versions should not be included in a single package. If both resolutions + are available, they should be provided in separate binary packages with + -75dpi or -100dpi appended to the package name for the + corresponding fonts. diff -Nru lintian-2.93.0/tags/p/package-contains-multiple-dpi-fonts.tag lintian-2.89.0ubuntu1/tags/p/package-contains-multiple-dpi-fonts.tag --- lintian-2.93.0/tags/p/package-contains-multiple-dpi-fonts.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-contains-multiple-dpi-fonts.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: package-contains-multiple-dpi-fonts -Severity: warning -Check: desktop/x11 -See-Also: policy 11.8.5 -Explanation: This package contains both 100dpi and 75dpi bitmapped fonts. Both - versions should not be included in a single package. If both resolutions - are available, they should be provided in separate binary packages with - -75dpi or -100dpi appended to the package name for the - corresponding fonts. diff -Nru lintian-2.93.0/tags/p/package-contains-no-arch-dependent-files.desc lintian-2.89.0ubuntu1/tags/p/package-contains-no-arch-dependent-files.desc --- lintian-2.93.0/tags/p/package-contains-no-arch-dependent-files.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-contains-no-arch-dependent-files.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,11 @@ +Tag: package-contains-no-arch-dependent-files +Severity: info +Certainty: possible +Check: files/architecture +Experimental: yes +Info: The package is not marked architecture all, but all the files it + ships are installed in /usr/share. + . + Most likely this package should be marked architecture all, but there + is a chance that the package is missing files. +Ref: policy 5.6.8 diff -Nru lintian-2.93.0/tags/p/package-contains-no-arch-dependent-files.tag lintian-2.89.0ubuntu1/tags/p/package-contains-no-arch-dependent-files.tag --- lintian-2.93.0/tags/p/package-contains-no-arch-dependent-files.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-contains-no-arch-dependent-files.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,10 +0,0 @@ -Tag: package-contains-no-arch-dependent-files -Severity: info -Check: files/architecture -Experimental: yes -Explanation: The package is not marked architecture all, but all the files it - ships are installed in /usr/share. - . - Most likely this package should be marked architecture all, but there - is a chance that the package is missing files. -See-Also: policy 5.6.8 diff -Nru lintian-2.93.0/tags/p/package-contains-npm-ignore-file.desc lintian-2.89.0ubuntu1/tags/p/package-contains-npm-ignore-file.desc --- lintian-2.93.0/tags/p/package-contains-npm-ignore-file.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-contains-npm-ignore-file.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: package-contains-npm-ignore-file +Severity: error +Check: files/names +Info: The package ships an .npmignore file. It is a + configuration file for the Node.js package manager. + It is not needed in a Debian package. + . + The file tells the npm command to keep files out of + a node package. Please remove it from your package. diff -Nru lintian-2.93.0/tags/p/package-contains-npm-ignore-file.tag lintian-2.89.0ubuntu1/tags/p/package-contains-npm-ignore-file.tag --- lintian-2.93.0/tags/p/package-contains-npm-ignore-file.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-contains-npm-ignore-file.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: package-contains-npm-ignore-file -Severity: error -Check: files/names -Explanation: The package ships an .npmignore file. It is a - configuration file for the Node.js package manager. - It is not needed in a Debian package. - . - The file tells the npm command to keep files out of - a node package. Please remove it from your package. diff -Nru lintian-2.93.0/tags/p/package-contains-python-coverage-file.desc lintian-2.89.0ubuntu1/tags/p/package-contains-python-coverage-file.desc --- lintian-2.93.0/tags/p/package-contains-python-coverage-file.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-contains-python-coverage-file.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,11 @@ +Tag: package-contains-python-coverage-file +Severity: warning +Check: files/names +Info: The package contains a file that looks like output from the Python + coverage.py tool. These are generated by python{,3}-coverage during a test + run, noting which parts of the code have been executed. They can then be + subsequently analyzed to identify code that could have been executed but was + not. + . + As they are unlikely to be of utility to end-users, these files should not + be shipped in the final binary package. diff -Nru lintian-2.93.0/tags/p/package-contains-python-coverage-file.tag lintian-2.89.0ubuntu1/tags/p/package-contains-python-coverage-file.tag --- lintian-2.93.0/tags/p/package-contains-python-coverage-file.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-contains-python-coverage-file.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,11 +0,0 @@ -Tag: package-contains-python-coverage-file -Severity: warning -Check: files/names -Explanation: The package contains a file that looks like output from the Python - coverage.py tool. These are generated by python{,3}-coverage during a test - run, noting which parts of the code have been executed. They can then be - subsequently analyzed to identify code that could have been executed but was - not. - . - As they are unlikely to be of utility to end-users, these files should not - be shipped in the final binary package. diff -Nru lintian-2.93.0/tags/p/package-contains-python-doctree-file.desc lintian-2.89.0ubuntu1/tags/p/package-contains-python-doctree-file.desc --- lintian-2.93.0/tags/p/package-contains-python-doctree-file.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-contains-python-doctree-file.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,24 @@ +Tag: package-contains-python-doctree-file +Severity: warning +Check: files/names +Info: This package appears to contain a pickled cache of reStructuredText + (*.rst) documentation in a .doctree file. + . + These are not needed to display the documentation correctly and as they can + contain absolute build paths can affect the reproducibility of the package. + . + Either prevent the installation of the .doctree file (or parent + doctrees directory if there is one) or pass the -d + option to sphinx-build(1) to create the caches elsewhere. + . + For example: + . + override_dh_auto_build: + dh_auto_build + PYTHONPATH=. sphinx-build -bman docs/ -d debian/doctrees docs/build/html + PYTHONPATH=. sphinx-build -bhtml docs/ -d debian/doctrees docs/build/html + . + override_dh_auto_clean: + dh_auto_clean + rm -rf debian/doctrees +Ref: http://sphinx-doc.org/invocation.html#cmdoption-sphinx-build-d diff -Nru lintian-2.93.0/tags/p/package-contains-python-doctree-file.tag lintian-2.89.0ubuntu1/tags/p/package-contains-python-doctree-file.tag --- lintian-2.93.0/tags/p/package-contains-python-doctree-file.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-contains-python-doctree-file.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,24 +0,0 @@ -Tag: package-contains-python-doctree-file -Severity: warning -Check: files/names -Explanation: This package appears to contain a pickled cache of reStructuredText - (*.rst) documentation in a .doctree file. - . - These are not needed to display the documentation correctly and as they can - contain absolute build paths can affect the reproducibility of the package. - . - Either prevent the installation of the .doctree file (or parent - doctrees directory if there is one) or pass the -d - option to sphinx-build(1) to create the caches elsewhere. - . - For example: - . - override_dh_auto_build: - dh_auto_build - PYTHONPATH=. sphinx-build -bman docs/ -d debian/doctrees docs/build/html - PYTHONPATH=. sphinx-build -bhtml docs/ -d debian/doctrees docs/build/html - . - override_dh_auto_clean: - dh_auto_clean - rm -rf debian/doctrees -See-Also: http://sphinx-doc.org/invocation.html#cmdoption-sphinx-build-d diff -Nru lintian-2.93.0/tags/p/package-contains-python-dot-directory.desc lintian-2.89.0ubuntu1/tags/p/package-contains-python-dot-directory.desc --- lintian-2.93.0/tags/p/package-contains-python-dot-directory.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-contains-python-dot-directory.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,12 @@ +Tag: package-contains-python-dot-directory +Severity: warning +Check: files/names +Info: The package contains files left over from a Python build + process, such as cached output from pytest. + . + Users of your package probably do not need the files. Please rebuild + your package with a newer version of pybuild/dh-python. + Many of the files will disappear. + . + Usually, the files contain time-stamped data. They will prevent your + package from being reproducible. diff -Nru lintian-2.93.0/tags/p/package-contains-python-dot-directory.tag lintian-2.89.0ubuntu1/tags/p/package-contains-python-dot-directory.tag --- lintian-2.93.0/tags/p/package-contains-python-dot-directory.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-contains-python-dot-directory.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,12 +0,0 @@ -Tag: package-contains-python-dot-directory -Severity: warning -Check: files/names -Explanation: The package contains files left over from a Python build - process, such as cached output from pytest. - . - Users of your package probably do not need the files. Please rebuild - your package with a newer version of pybuild/dh-python. - Many of the files will disappear. - . - Usually, the files contain time-stamped data. They will prevent your - package from being reproducible. diff -Nru lintian-2.93.0/tags/p/package-contains-python-header-in-incorrect-directory.desc lintian-2.89.0ubuntu1/tags/p/package-contains-python-header-in-incorrect-directory.desc --- lintian-2.93.0/tags/p/package-contains-python-header-in-incorrect-directory.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-contains-python-header-in-incorrect-directory.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,14 @@ +Tag: package-contains-python-header-in-incorrect-directory +Severity: error +Check: files/names +Info: This package ships a header file such as + /usr/include/python3.7/foo/bar.h. However, + /usr/include/python3.7 is a symlink to python3.7m in + libpython3.7-dev. + . + This may result in silent file overwrites or, depending on the unpacking + order (if /usr/include/python3.7 is a directory), separating + the headers into two independent trees. + . + These header files should be shipped in + /usr/include/python3.7m instead. diff -Nru lintian-2.93.0/tags/p/package-contains-python-header-in-incorrect-directory.tag lintian-2.89.0ubuntu1/tags/p/package-contains-python-header-in-incorrect-directory.tag --- lintian-2.93.0/tags/p/package-contains-python-header-in-incorrect-directory.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-contains-python-header-in-incorrect-directory.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,14 +0,0 @@ -Tag: package-contains-python-header-in-incorrect-directory -Severity: error -Check: files/names -Explanation: This package ships a header file such as - /usr/include/python3.7/foo/bar.h. However, - /usr/include/python3.7 is a symlink to python3.7m in - libpython3.7-dev. - . - This may result in silent file overwrites or, depending on the unpacking - order (if /usr/include/python3.7 is a directory), separating - the headers into two independent trees. - . - These header files should be shipped in - /usr/include/python3.7m instead. diff -Nru lintian-2.93.0/tags/p/package-contains-python-hypothesis-example.desc lintian-2.89.0ubuntu1/tags/p/package-contains-python-hypothesis-example.desc --- lintian-2.93.0/tags/p/package-contains-python-hypothesis-example.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-contains-python-hypothesis-example.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,17 @@ +Tag: package-contains-python-hypothesis-example +Severity: warning +Check: files/names +Info: This package appears to contain the output of running a Python + "Hypothesis" testsuite. + . + These are not useful in the binary package or to end-users. In addition, + as they contain random/non-determinstic contents, they can affect the + reproducibility of the package. + . + You can disable generation of these files by, for example: + . + export HYPOTHESIS_DATABASE_FILE = $(CURDIR)/debian/hypothesis + . + override_dh_auto_clean: + dh_auto_clean + rm -rf $(CURDIR)/debian/hypothesis diff -Nru lintian-2.93.0/tags/p/package-contains-python-hypothesis-example.tag lintian-2.89.0ubuntu1/tags/p/package-contains-python-hypothesis-example.tag --- lintian-2.93.0/tags/p/package-contains-python-hypothesis-example.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-contains-python-hypothesis-example.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,17 +0,0 @@ -Tag: package-contains-python-hypothesis-example -Severity: warning -Check: files/names -Explanation: This package appears to contain the output of running a Python - "Hypothesis" testsuite. - . - These are not useful in the binary package or to end-users. In addition, - as they contain random/non-determinstic contents, they can affect the - reproducibility of the package. - . - You can disable generation of these files by, for example: - . - export HYPOTHESIS_DATABASE_FILE = $(CURDIR)/debian/hypothesis - . - override_dh_auto_clean: - dh_auto_clean - rm -rf $(CURDIR)/debian/hypothesis diff -Nru lintian-2.93.0/tags/p/package-contains-python-tests-in-global-namespace.desc lintian-2.89.0ubuntu1/tags/p/package-contains-python-tests-in-global-namespace.desc --- lintian-2.93.0/tags/p/package-contains-python-tests-in-global-namespace.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-contains-python-tests-in-global-namespace.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,12 @@ +Tag: package-contains-python-tests-in-global-namespace +Severity: warning +Check: files/names +Info: This package appears to contain Python test files such as + test_foo.py or test_foo/ in the global module + namespace. + . + Whilst the tests may be useful in the binary package, it is probably a + mistake to pollute the "top-level" namespace in this way. + . + Please install them to a subdirectory of the module being tested + instead or simply omit from the binary package entirely. diff -Nru lintian-2.93.0/tags/p/package-contains-python-tests-in-global-namespace.tag lintian-2.89.0ubuntu1/tags/p/package-contains-python-tests-in-global-namespace.tag --- lintian-2.93.0/tags/p/package-contains-python-tests-in-global-namespace.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-contains-python-tests-in-global-namespace.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,12 +0,0 @@ -Tag: package-contains-python-tests-in-global-namespace -Severity: warning -Check: files/names -Explanation: This package appears to contain Python test files such as - test_foo.py or test_foo/ in the global module - namespace. - . - Whilst the tests may be useful in the binary package, it is probably a - mistake to pollute the "top-level" namespace in this way. - . - Please install them to a subdirectory of the module being tested - instead or simply omit from the binary package entirely. diff -Nru lintian-2.93.0/tags/p/package-contains-readme-for-other-platform-or-distro.desc lintian-2.89.0ubuntu1/tags/p/package-contains-readme-for-other-platform-or-distro.desc --- lintian-2.93.0/tags/p/package-contains-readme-for-other-platform-or-distro.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-contains-readme-for-other-platform-or-distro.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: package-contains-readme-for-other-platform-or-distro +Severity: warning +Check: documentation +Info: package contains a README.(platform) file that contains instructions + specific to a platform or distribution other than Debian and thus can + most likely be removed. If it contains information that pertains to + Debian, please consider renaming it, or including it in an already + existing README file. diff -Nru lintian-2.93.0/tags/p/package-contains-readme-for-other-platform-or-distro.tag lintian-2.89.0ubuntu1/tags/p/package-contains-readme-for-other-platform-or-distro.tag --- lintian-2.93.0/tags/p/package-contains-readme-for-other-platform-or-distro.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-contains-readme-for-other-platform-or-distro.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: package-contains-readme-for-other-platform-or-distro -Severity: warning -Check: documentation -Explanation: package contains a README.(platform) file that contains instructions - specific to a platform or distribution other than Debian and thus can - most likely be removed. If it contains information that pertains to - Debian, please consider renaming it, or including it in an already - existing README file. diff -Nru lintian-2.93.0/tags/p/package-contains-sass-cache-directory.desc lintian-2.89.0ubuntu1/tags/p/package-contains-sass-cache-directory.desc --- lintian-2.93.0/tags/p/package-contains-sass-cache-directory.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-contains-sass-cache-directory.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,17 @@ +Tag: package-contains-sass-cache-directory +Severity: warning +Check: files/names +Info: This package appears to ship a .sass-cache/ directory, + the result of running a the "Sass" utility that compiles CSS from SASS + or SCSS files. + . + These are not useful in the binary package or to end-users. In + addition, as they contain random/non-determinstic contents or + filenames they can affect the reproducibility of the package. + . + Please ensure they are removed prior to final package build. For + example, with: + . + override_dh_install: + dh_install -X.sass-cache +Ref: https://reproducible-builds.org/, #920595 diff -Nru lintian-2.93.0/tags/p/package-contains-sass-cache-directory.tag lintian-2.89.0ubuntu1/tags/p/package-contains-sass-cache-directory.tag --- lintian-2.93.0/tags/p/package-contains-sass-cache-directory.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-contains-sass-cache-directory.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,17 +0,0 @@ -Tag: package-contains-sass-cache-directory -Severity: warning -Check: files/names -Explanation: This package appears to ship a .sass-cache/ directory, - the result of running a the "Sass" utility that compiles CSS from SASS - or SCSS files. - . - These are not useful in the binary package or to end-users. In - addition, as they contain random/non-determinstic contents or - filenames they can affect the reproducibility of the package. - . - Please ensure they are removed prior to final package build. For - example, with: - . - override_dh_install: - dh_install -X.sass-cache -See-Also: https://reproducible-builds.org/, Bug#920595 diff -Nru lintian-2.93.0/tags/p/package-contains-thumbnails-dir.desc lintian-2.89.0ubuntu1/tags/p/package-contains-thumbnails-dir.desc --- lintian-2.93.0/tags/p/package-contains-thumbnails-dir.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-contains-thumbnails-dir.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: package-contains-thumbnails-dir +Severity: error +Check: images/thumbnails +Info: Package contains a .thumbnails directory. It was most likely installed by + accident, since thumbnails usually don't belong in packages. +Ref: https://specifications.freedesktop.org/thumbnail-spec/thumbnail-spec-latest.html diff -Nru lintian-2.93.0/tags/p/package-contains-thumbnails-dir.tag lintian-2.89.0ubuntu1/tags/p/package-contains-thumbnails-dir.tag --- lintian-2.93.0/tags/p/package-contains-thumbnails-dir.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-contains-thumbnails-dir.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: package-contains-thumbnails-dir -Severity: error -Check: images/thumbnails -Explanation: Package contains a .thumbnails directory. It was most likely installed by - accident, since thumbnails usually don't belong in packages. -See-Also: https://specifications.freedesktop.org/thumbnail-spec/thumbnail-spec-latest.html diff -Nru lintian-2.93.0/tags/p/package-contains-timestamped-gzip.desc lintian-2.89.0ubuntu1/tags/p/package-contains-timestamped-gzip.desc --- lintian-2.93.0/tags/p/package-contains-timestamped-gzip.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-contains-timestamped-gzip.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: package-contains-timestamped-gzip +Severity: warning +Check: files/compressed/gz +Info: The package contains a gzip-compressed file that has timestamps. + Such files make the packages unreproducible, because their + contents depend on the time when the package was built. + . + Please consider passing the "-n" flag to gzip to avoid this. +Ref: https://wiki.debian.org/ReproducibleBuilds diff -Nru lintian-2.93.0/tags/p/package-contains-timestamped-gzip.tag lintian-2.89.0ubuntu1/tags/p/package-contains-timestamped-gzip.tag --- lintian-2.93.0/tags/p/package-contains-timestamped-gzip.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-contains-timestamped-gzip.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: package-contains-timestamped-gzip -Severity: warning -Check: files/compressed/gz -Explanation: The package contains a gzip-compressed file that has timestamps. - Such files make the packages unreproducible, because their - contents depend on the time when the package was built. - . - Please consider passing the "-n" flag to gzip to avoid this. -See-Also: https://wiki.debian.org/ReproducibleBuilds diff -Nru lintian-2.93.0/tags/p/package-contains-unsafe-symlink.desc lintian-2.89.0ubuntu1/tags/p/package-contains-unsafe-symlink.desc --- lintian-2.93.0/tags/p/package-contains-unsafe-symlink.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-contains-unsafe-symlink.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: package-contains-unsafe-symlink +Severity: error +Check: files/symbolic-links/broken +Info: The package contains an unsafe symlink. If followed, + the link will escape the package root. +Ref: policy 10.5 diff -Nru lintian-2.93.0/tags/p/package-contains-unsafe-symlink.tag lintian-2.89.0ubuntu1/tags/p/package-contains-unsafe-symlink.tag --- lintian-2.93.0/tags/p/package-contains-unsafe-symlink.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-contains-unsafe-symlink.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: package-contains-unsafe-symlink -Severity: error -Check: files/symbolic-links/broken -Explanation: The package contains an unsafe symlink. If followed, - the link will escape the package root. -See-Also: policy 10.5 diff -Nru lintian-2.93.0/tags/p/package-contains-upstream-installation-documentation.desc lintian-2.89.0ubuntu1/tags/p/package-contains-upstream-installation-documentation.desc --- lintian-2.93.0/tags/p/package-contains-upstream-installation-documentation.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-contains-upstream-installation-documentation.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: package-contains-upstream-installation-documentation +Severity: warning +Certainty: possible +Check: documentation +Ref: policy 12.3 +Info: Binary packages do not need to contain the instructions for building + and installing the package as this info is not needed by package users. + If the info contained is important for configuration perhaps it could be + summarized in README.Debian, otherwise an override may be added. diff -Nru lintian-2.93.0/tags/p/package-contains-upstream-installation-documentation.tag lintian-2.89.0ubuntu1/tags/p/package-contains-upstream-installation-documentation.tag --- lintian-2.93.0/tags/p/package-contains-upstream-installation-documentation.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-contains-upstream-installation-documentation.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: package-contains-upstream-installation-documentation -Severity: warning -Check: documentation -See-Also: policy 12.3 -Explanation: Binary packages do not need to contain the instructions for building - and installing the package as this info is not needed by package users. - If the info contained is important for configuration perhaps it could be - summarized in README.Debian, otherwise an override may be added. diff -Nru lintian-2.93.0/tags/p/package-contains-usr-unmerged-pathnames.desc lintian-2.89.0ubuntu1/tags/p/package-contains-usr-unmerged-pathnames.desc --- lintian-2.93.0/tags/p/package-contains-usr-unmerged-pathnames.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-contains-usr-unmerged-pathnames.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,17 @@ +Tag: package-contains-usr-unmerged-pathnames +Severity: classification +Check: files/usr-merge +Info: The package installs the listed file to a directory in / (the + filesystem root) rather than to the corresponding directory inside /usr. + . + Debian requires systems to mount /usr prior to invoking init (using an + initramfs if necessary) so any executables, libraries, or other files + placed in / for use by early portions of the system init no longer need + to do so. + . + Moving a file from / to /usr (especially an executable in /bin or + /sbin) will often require a compatibility symlink to the new location, + as other software may invoke it by absolute path. + . + A compatibility symlink to the corresponding file in /usr will not + trigger this warning but a symlink to anywhere else will. diff -Nru lintian-2.93.0/tags/p/package-contains-usr-unmerged-pathnames.tag lintian-2.89.0ubuntu1/tags/p/package-contains-usr-unmerged-pathnames.tag --- lintian-2.93.0/tags/p/package-contains-usr-unmerged-pathnames.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-contains-usr-unmerged-pathnames.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,17 +0,0 @@ -Tag: package-contains-usr-unmerged-pathnames -Severity: classification -Check: files/usr-merge -Explanation: The package installs the listed file to a directory in / (the - filesystem root) rather than to the corresponding directory inside /usr. - . - Debian requires systems to mount /usr prior to invoking init (using an - initramfs if necessary) so any executables, libraries, or other files - placed in / for use by early portions of the system init no longer need - to do so. - . - Moving a file from / to /usr (especially an executable in /bin or - /sbin) will often require a compatibility symlink to the new location, - as other software may invoke it by absolute path. - . - A compatibility symlink to the corresponding file in /usr will not - trigger this warning but a symlink to anywhere else will. diff -Nru lintian-2.93.0/tags/p/package-contains-vcs-control-dir.desc lintian-2.89.0ubuntu1/tags/p/package-contains-vcs-control-dir.desc --- lintian-2.93.0/tags/p/package-contains-vcs-control-dir.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-contains-vcs-control-dir.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: package-contains-vcs-control-dir +Severity: warning +Check: files/vcs +Info: The package contains a control directory for a version control system. + It was most likely installed by accident, since version control directories + usually don't belong in packages. diff -Nru lintian-2.93.0/tags/p/package-contains-vcs-control-dir.tag lintian-2.89.0ubuntu1/tags/p/package-contains-vcs-control-dir.tag --- lintian-2.93.0/tags/p/package-contains-vcs-control-dir.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-contains-vcs-control-dir.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: package-contains-vcs-control-dir -Severity: warning -Check: files/vcs -Explanation: The package contains a control directory for a version control system. - It was most likely installed by accident, since version control directories - usually don't belong in packages. diff -Nru lintian-2.93.0/tags/p/package-contains-vcs-control-file.desc lintian-2.89.0ubuntu1/tags/p/package-contains-vcs-control-file.desc --- lintian-2.93.0/tags/p/package-contains-vcs-control-file.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-contains-vcs-control-file.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: package-contains-vcs-control-file +Severity: warning +Check: files/vcs +Info: The package contains a VCS control file such as .(cvs|git|hg)ignore. + Files such as these are used by revision control systems to, for example, + specify untracked files it should ignore or inventory files. This file + is generally useless in an installed package and was probably installed + by accident. diff -Nru lintian-2.93.0/tags/p/package-contains-vcs-control-file.tag lintian-2.89.0ubuntu1/tags/p/package-contains-vcs-control-file.tag --- lintian-2.93.0/tags/p/package-contains-vcs-control-file.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-contains-vcs-control-file.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: package-contains-vcs-control-file -Severity: warning -Check: files/vcs -Explanation: The package contains a VCS control file such as .(cvs|git|hg)ignore. - Files such as these are used by revision control systems to, for example, - specify untracked files it should ignore or inventory files. This file - is generally useless in an installed package and was probably installed - by accident. diff -Nru lintian-2.93.0/tags/p/package-contains-xvpics-dir.desc lintian-2.89.0ubuntu1/tags/p/package-contains-xvpics-dir.desc --- lintian-2.93.0/tags/p/package-contains-xvpics-dir.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-contains-xvpics-dir.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,5 @@ +Tag: package-contains-xvpics-dir +Severity: error +Check: images/thumbnails +Info: Package contains a .xvpics directory. It was most likely installed by + accident, since thumbnails usually don't belong in packages. diff -Nru lintian-2.93.0/tags/p/package-contains-xvpics-dir.tag lintian-2.89.0ubuntu1/tags/p/package-contains-xvpics-dir.tag --- lintian-2.93.0/tags/p/package-contains-xvpics-dir.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-contains-xvpics-dir.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,5 +0,0 @@ -Tag: package-contains-xvpics-dir -Severity: error -Check: images/thumbnails -Explanation: Package contains a .xvpics directory. It was most likely installed by - accident, since thumbnails usually don't belong in packages. diff -Nru lintian-2.93.0/tags/p/package-depends-on-an-x-font-package.desc lintian-2.89.0ubuntu1/tags/p/package-depends-on-an-x-font-package.desc --- lintian-2.93.0/tags/p/package-depends-on-an-x-font-package.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-depends-on-an-x-font-package.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: package-depends-on-an-x-font-package +Severity: error +Check: fields/package-relations +Info: Packages must not depend on X Window System font packages. + . + If one or more of the fonts so packaged are necessary for proper operation + of the package with which they are associated the font package may be + Recommended; if the fonts merely provide an enhancement, a Suggests + relationship may be used. +Ref: policy 11.8.5 diff -Nru lintian-2.93.0/tags/p/package-depends-on-an-x-font-package.tag lintian-2.89.0ubuntu1/tags/p/package-depends-on-an-x-font-package.tag --- lintian-2.93.0/tags/p/package-depends-on-an-x-font-package.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-depends-on-an-x-font-package.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,10 +0,0 @@ -Tag: package-depends-on-an-x-font-package -Severity: error -Check: fields/package-relations -Explanation: Packages must not depend on X Window System font packages. - . - If one or more of the fonts so packaged are necessary for proper operation - of the package with which they are associated the font package may be - Recommended; if the fonts merely provide an enhancement, a Suggests - relationship may be used. -See-Also: policy 11.8.5 diff -Nru lintian-2.93.0/tags/p/package-depends-on-hardcoded-libc.desc lintian-2.89.0ubuntu1/tags/p/package-depends-on-hardcoded-libc.desc --- lintian-2.93.0/tags/p/package-depends-on-hardcoded-libc.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-depends-on-hardcoded-libc.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,5 @@ +Tag: package-depends-on-hardcoded-libc +Severity: warning +Check: debian/control +Info: The given package declares a dependency on libc directly instead + of using ${shlibs:Depends} in its debian/control stanza. diff -Nru lintian-2.93.0/tags/p/package-depends-on-hardcoded-libc.tag lintian-2.89.0ubuntu1/tags/p/package-depends-on-hardcoded-libc.tag --- lintian-2.93.0/tags/p/package-depends-on-hardcoded-libc.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-depends-on-hardcoded-libc.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,5 +0,0 @@ -Tag: package-depends-on-hardcoded-libc -Severity: warning -Check: debian/control -Explanation: The given package declares a dependency on libc directly instead - of using ${shlibs:Depends} in its debian/control stanza. diff -Nru lintian-2.93.0/tags/p/package-depends-on-itself.desc lintian-2.89.0ubuntu1/tags/p/package-depends-on-itself.desc --- lintian-2.93.0/tags/p/package-depends-on-itself.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-depends-on-itself.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: package-depends-on-itself +Severity: warning +Check: debian/control +Ref: policy 7.2 +Info: The given package declares a dependency on itself in its + debian/control stanza. Current versions of dpkg-gencontrol will + silently fix this problem by removing the dependency, but it may indicate + a more subtle bug (misspelling or cutting and pasting the wrong package + name). diff -Nru lintian-2.93.0/tags/p/package-depends-on-itself.tag lintian-2.89.0ubuntu1/tags/p/package-depends-on-itself.tag --- lintian-2.93.0/tags/p/package-depends-on-itself.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-depends-on-itself.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: package-depends-on-itself -Severity: warning -Check: debian/control -See-Also: policy 7.2 -Explanation: The given package declares a dependency on itself in its - debian/control stanza. Current versions of dpkg-gencontrol will - silently fix this problem by removing the dependency, but it may indicate - a more subtle bug (misspelling or cutting and pasting the wrong package - name). diff -Nru lintian-2.93.0/tags/p/package-depends-on-multiple-libpng-versions.desc lintian-2.89.0ubuntu1/tags/p/package-depends-on-multiple-libpng-versions.desc --- lintian-2.93.0/tags/p/package-depends-on-multiple-libpng-versions.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-depends-on-multiple-libpng-versions.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: package-depends-on-multiple-libpng-versions +Severity: error +Certainty: possible +Check: fields/package-relations +Info: The package seems to declare several relations to a libpng version. + This is not only sloppy but in the case of libraries, it may well break + the runtime execution of programs. diff -Nru lintian-2.93.0/tags/p/package-depends-on-multiple-libpng-versions.tag lintian-2.89.0ubuntu1/tags/p/package-depends-on-multiple-libpng-versions.tag --- lintian-2.93.0/tags/p/package-depends-on-multiple-libpng-versions.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-depends-on-multiple-libpng-versions.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: package-depends-on-multiple-libpng-versions -Severity: error -Check: fields/package-relations -Explanation: The package seems to declare several relations to a libpng version. - This is not only sloppy but in the case of libraries, it may well break - the runtime execution of programs. diff -Nru lintian-2.93.0/tags/p/package-depends-on-multiple-libstdc-versions.desc lintian-2.89.0ubuntu1/tags/p/package-depends-on-multiple-libstdc-versions.desc --- lintian-2.93.0/tags/p/package-depends-on-multiple-libstdc-versions.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-depends-on-multiple-libstdc-versions.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: package-depends-on-multiple-libstdc-versions +Severity: error +Certainty: possible +Check: fields/package-relations +Info: The package seems to declare several relations to a libstdc version. + This is not only sloppy but in the case of libraries, it may well break + the runtime execution of programs. diff -Nru lintian-2.93.0/tags/p/package-depends-on-multiple-libstdc-versions.tag lintian-2.89.0ubuntu1/tags/p/package-depends-on-multiple-libstdc-versions.tag --- lintian-2.93.0/tags/p/package-depends-on-multiple-libstdc-versions.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-depends-on-multiple-libstdc-versions.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: package-depends-on-multiple-libstdc-versions -Severity: error -Check: fields/package-relations -Explanation: The package seems to declare several relations to a libstdc version. - This is not only sloppy but in the case of libraries, it may well break - the runtime execution of programs. diff -Nru lintian-2.93.0/tags/p/package-depends-on-multiple-tcl-versions.desc lintian-2.89.0ubuntu1/tags/p/package-depends-on-multiple-tcl-versions.desc --- lintian-2.93.0/tags/p/package-depends-on-multiple-tcl-versions.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-depends-on-multiple-tcl-versions.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: package-depends-on-multiple-tcl-versions +Severity: error +Certainty: possible +Check: fields/package-relations +Info: The package seems to declare several relations to a tcl version. + This is not only sloppy but in the case of libraries, it may well break + the runtime execution of programs. diff -Nru lintian-2.93.0/tags/p/package-depends-on-multiple-tcl-versions.tag lintian-2.89.0ubuntu1/tags/p/package-depends-on-multiple-tcl-versions.tag --- lintian-2.93.0/tags/p/package-depends-on-multiple-tcl-versions.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-depends-on-multiple-tcl-versions.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: package-depends-on-multiple-tcl-versions -Severity: error -Check: fields/package-relations -Explanation: The package seems to declare several relations to a tcl version. - This is not only sloppy but in the case of libraries, it may well break - the runtime execution of programs. diff -Nru lintian-2.93.0/tags/p/package-depends-on-multiple-tclx-versions.desc lintian-2.89.0ubuntu1/tags/p/package-depends-on-multiple-tclx-versions.desc --- lintian-2.93.0/tags/p/package-depends-on-multiple-tclx-versions.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-depends-on-multiple-tclx-versions.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: package-depends-on-multiple-tclx-versions +Severity: error +Certainty: possible +Check: fields/package-relations +Info: The package seems to declare several relations to a tclx version. + This is not only sloppy but in the case of libraries, it may well break + the runtime execution of programs. diff -Nru lintian-2.93.0/tags/p/package-depends-on-multiple-tclx-versions.tag lintian-2.89.0ubuntu1/tags/p/package-depends-on-multiple-tclx-versions.tag --- lintian-2.93.0/tags/p/package-depends-on-multiple-tclx-versions.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-depends-on-multiple-tclx-versions.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: package-depends-on-multiple-tclx-versions -Severity: error -Check: fields/package-relations -Explanation: The package seems to declare several relations to a tclx version. - This is not only sloppy but in the case of libraries, it may well break - the runtime execution of programs. diff -Nru lintian-2.93.0/tags/p/package-depends-on-multiple-tk-versions.desc lintian-2.89.0ubuntu1/tags/p/package-depends-on-multiple-tk-versions.desc --- lintian-2.93.0/tags/p/package-depends-on-multiple-tk-versions.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-depends-on-multiple-tk-versions.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: package-depends-on-multiple-tk-versions +Severity: error +Certainty: possible +Check: fields/package-relations +Info: The package seems to declare several relations to a tk version. + This is not only sloppy but in the case of libraries, it may well break + the runtime execution of programs. diff -Nru lintian-2.93.0/tags/p/package-depends-on-multiple-tk-versions.tag lintian-2.89.0ubuntu1/tags/p/package-depends-on-multiple-tk-versions.tag --- lintian-2.93.0/tags/p/package-depends-on-multiple-tk-versions.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-depends-on-multiple-tk-versions.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: package-depends-on-multiple-tk-versions -Severity: error -Check: fields/package-relations -Explanation: The package seems to declare several relations to a tk version. - This is not only sloppy but in the case of libraries, it may well break - the runtime execution of programs. diff -Nru lintian-2.93.0/tags/p/package-does-not-install-examples.desc lintian-2.89.0ubuntu1/tags/p/package-does-not-install-examples.desc --- lintian-2.93.0/tags/p/package-does-not-install-examples.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-does-not-install-examples.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,14 @@ +Tag: package-does-not-install-examples +Severity: pedantic +Certainty: possible +Check: cruft +Info: The original source tarball contains the specified examples + directory. However, no examples are installed in any binary packages. + . + Please use dh_installexamples to install these to the most + relevant package, for example by adding the directory name followed + by a wildcard to a debian/pkgname.examples file. + . + Lintian looks for any directory called examples under + /usr/share/doc in all binary packages. +Ref: dh_installexamples(1) diff -Nru lintian-2.93.0/tags/p/package-does-not-install-examples.tag lintian-2.89.0ubuntu1/tags/p/package-does-not-install-examples.tag --- lintian-2.93.0/tags/p/package-does-not-install-examples.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-does-not-install-examples.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,13 +0,0 @@ -Tag: package-does-not-install-examples -Severity: pedantic -Check: cruft -Explanation: The original source tarball contains the specified examples - directory. However, no examples are installed in any binary packages. - . - Please use dh_installexamples to install these to the most - relevant package, for example by adding the directory name followed - by a wildcard to a debian/pkgname.examples file. - . - Lintian looks for any directory called examples under - /usr/share/doc in all binary packages. -See-Also: dh_installexamples(1) diff -Nru lintian-2.93.0/tags/p/package-does-not-use-debhelper-or-cdbs.desc lintian-2.89.0ubuntu1/tags/p/package-does-not-use-debhelper-or-cdbs.desc --- lintian-2.93.0/tags/p/package-does-not-use-debhelper-or-cdbs.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-does-not-use-debhelper-or-cdbs.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,11 @@ +Tag: package-does-not-use-debhelper-or-cdbs +Severity: pedantic +Check: debhelper +Info: This package does not appear to use a build system helper such as + debhelper or cdbs. + . + It is recommended that packages use such tools as they avoid a large + number of common errors and tedious boilerplate as well as permit + distribution-wide changes to packages and reduce the "bus factor" & + barriers to entry from external contributors. +Ref: debhelper(7), dh(1), https://build-common.alioth.debian.org/ diff -Nru lintian-2.93.0/tags/p/package-does-not-use-debhelper-or-cdbs.tag lintian-2.89.0ubuntu1/tags/p/package-does-not-use-debhelper-or-cdbs.tag --- lintian-2.93.0/tags/p/package-does-not-use-debhelper-or-cdbs.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-does-not-use-debhelper-or-cdbs.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,11 +0,0 @@ -Tag: package-does-not-use-debhelper-or-cdbs -Severity: pedantic -Check: debhelper -Explanation: This package does not appear to use a build system helper such as - debhelper or cdbs. - . - It is recommended that packages use such tools as they avoid a large - number of common errors and tedious boilerplate as well as permit - distribution-wide changes to packages and reduce the "bus factor" & - barriers to entry from external contributors. -See-Also: debhelper(7), dh(1), https://build-common.alioth.debian.org/ diff -Nru lintian-2.93.0/tags/p/package-file-is-executable.desc lintian-2.89.0ubuntu1/tags/p/package-file-is-executable.desc --- lintian-2.93.0/tags/p/package-file-is-executable.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-file-is-executable.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: package-file-is-executable +Severity: warning +Check: debhelper +Info: The packaging file is marked executable. For control, changelog and + copyright there is no reason for them to be executable. + . + This tag is also emitted if a debhelper file is marked executable without + using compat level 9, since debhelper does not execute them at lower + compat levels. diff -Nru lintian-2.93.0/tags/p/package-file-is-executable.tag lintian-2.89.0ubuntu1/tags/p/package-file-is-executable.tag --- lintian-2.93.0/tags/p/package-file-is-executable.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-file-is-executable.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: package-file-is-executable -Severity: warning -Check: debhelper -Explanation: The packaging file is marked executable. For control, changelog and - copyright there is no reason for them to be executable. - . - This tag is also emitted if a debhelper file is marked executable without - using compat level 9, since debhelper does not execute them at lower - compat levels. diff -Nru lintian-2.93.0/tags/p/package-has-a-duplicate-build-relation.desc lintian-2.89.0ubuntu1/tags/p/package-has-a-duplicate-build-relation.desc --- lintian-2.93.0/tags/p/package-has-a-duplicate-build-relation.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-has-a-duplicate-build-relation.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: package-has-a-duplicate-build-relation +Severity: warning +Certainty: possible +Check: fields/package-relations +Info: The package declares the given build relations on the same package + in either Build-Depends or Build-Depends-Indep, but the build relations + imply each other and are therefore redundant. diff -Nru lintian-2.93.0/tags/p/package-has-a-duplicate-build-relation.tag lintian-2.89.0ubuntu1/tags/p/package-has-a-duplicate-build-relation.tag --- lintian-2.93.0/tags/p/package-has-a-duplicate-build-relation.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-has-a-duplicate-build-relation.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: package-has-a-duplicate-build-relation -Severity: warning -Check: fields/package-relations -Explanation: The package declares the given build relations on the same package - in either Build-Depends or Build-Depends-Indep, but the build relations - imply each other and are therefore redundant. diff -Nru lintian-2.93.0/tags/p/package-has-long-file-name.desc lintian-2.89.0ubuntu1/tags/p/package-has-long-file-name.desc --- lintian-2.93.0/tags/p/package-has-long-file-name.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-has-long-file-name.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,13 @@ +Tag: package-has-long-file-name +Severity: warning +Check: filename-length +Info: The package has a very long filename. This may complicate + shipping the package on some media that put restrictions on the + length of the filenames (such as CDs). + . + For architecture dependent packages, the tag is emitted based on the + length of the longest architecture name rather than the name of the + current architecture. + . + This length will be written in brackets after the actual length. +Ref: https://lists.debian.org/debian-devel/2011/03/msg00943.html diff -Nru lintian-2.93.0/tags/p/package-has-long-file-name.tag lintian-2.89.0ubuntu1/tags/p/package-has-long-file-name.tag --- lintian-2.93.0/tags/p/package-has-long-file-name.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-has-long-file-name.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,13 +0,0 @@ -Tag: package-has-long-file-name -Severity: warning -Check: filename-length -Explanation: The package has a very long filename. This may complicate - shipping the package on some media that put restrictions on the - length of the filenames (such as CDs). - . - For architecture dependent packages, the tag is emitted based on the - length of the longest architecture name rather than the name of the - current architecture. - . - This length will be written in brackets after the actual length. -See-Also: https://lists.debian.org/debian-devel/2011/03/msg00943.html diff -Nru lintian-2.93.0/tags/p/package-has-unnecessary-activation-of-ldconfig-trigger.desc lintian-2.89.0ubuntu1/tags/p/package-has-unnecessary-activation-of-ldconfig-trigger.desc --- lintian-2.93.0/tags/p/package-has-unnecessary-activation-of-ldconfig-trigger.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-has-unnecessary-activation-of-ldconfig-trigger.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: package-has-unnecessary-activation-of-ldconfig-trigger +Severity: warning +Check: shared-libs +Info: The package activates the ldconfig trigger even though no shared + libraries are installed in a directory controlled by the dynamic + library loader. + . + Note this may be triggered by a bug in debhelper, that causes it to + auto-generate an ldconfig trigger for packages that do not need it. +Ref: policy 8.1.1, #204975 diff -Nru lintian-2.93.0/tags/p/package-has-unnecessary-activation-of-ldconfig-trigger.tag lintian-2.89.0ubuntu1/tags/p/package-has-unnecessary-activation-of-ldconfig-trigger.tag --- lintian-2.93.0/tags/p/package-has-unnecessary-activation-of-ldconfig-trigger.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-has-unnecessary-activation-of-ldconfig-trigger.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,10 +0,0 @@ -Tag: package-has-unnecessary-activation-of-ldconfig-trigger -Severity: warning -Check: shared-libs -Explanation: The package activates the ldconfig trigger even though no shared - libraries are installed in a directory controlled by the dynamic - library loader. - . - Note this may be triggered by a bug in debhelper, that causes it to - auto-generate an ldconfig trigger for packages that do not need it. -See-Also: policy 8.1.1, Bug#204975 diff -Nru lintian-2.93.0/tags/p/package-installs-apt-keyring.desc lintian-2.89.0ubuntu1/tags/p/package-installs-apt-keyring.desc --- lintian-2.93.0/tags/p/package-installs-apt-keyring.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-installs-apt-keyring.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,14 @@ +Tag: package-installs-apt-keyring +Severity: error +Certainty: possible +Check: apt +Ref: apt-key(8) +Info: Debian packages should not install files under + /etc/apt/trusted.gpg.d/ or install an + /etc/apt/trusted.gpg file. + . + Trusted keyrings are under the control of the local administrator and + packages should not override local administrator choices. + . + Packages whose names end in -apt-source or + -archive-keyring are permitted to install such files. diff -Nru lintian-2.93.0/tags/p/package-installs-apt-keyring.tag lintian-2.89.0ubuntu1/tags/p/package-installs-apt-keyring.tag --- lintian-2.93.0/tags/p/package-installs-apt-keyring.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-installs-apt-keyring.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,13 +0,0 @@ -Tag: package-installs-apt-keyring -Severity: error -Check: apt -See-Also: apt-key(8) -Explanation: Debian packages should not install files under - /etc/apt/trusted.gpg.d/ or install an - /etc/apt/trusted.gpg file. - . - Trusted keyrings are under the control of the local administrator and - packages should not override local administrator choices. - . - Packages whose names end in -apt-source or - -archive-keyring are permitted to install such files. diff -Nru lintian-2.93.0/tags/p/package-installs-apt-preferences.desc lintian-2.89.0ubuntu1/tags/p/package-installs-apt-preferences.desc --- lintian-2.93.0/tags/p/package-installs-apt-preferences.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-installs-apt-preferences.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,11 @@ +Tag: package-installs-apt-preferences +Severity: error +Certainty: possible +Check: apt +Ref: apt_preferences(5) +Info: Debian packages should not install files under /etc/apt/preferences.d/ or install an /etc/apt/preferences file. + This directory is under the control of the local administrator. + . + Package should not override local administrator choices. +Renamed-From: + package-install-apt-preferences diff -Nru lintian-2.93.0/tags/p/package-installs-apt-preferences.tag lintian-2.89.0ubuntu1/tags/p/package-installs-apt-preferences.tag --- lintian-2.93.0/tags/p/package-installs-apt-preferences.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-installs-apt-preferences.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,10 +0,0 @@ -Tag: package-installs-apt-preferences -Severity: error -Check: apt -See-Also: apt_preferences(5) -Explanation: Debian packages should not install files under /etc/apt/preferences.d/ or install an /etc/apt/preferences file. - This directory is under the control of the local administrator. - . - Package should not override local administrator choices. -Renamed-From: - package-install-apt-preferences diff -Nru lintian-2.93.0/tags/p/package-installs-apt-sources.desc lintian-2.89.0ubuntu1/tags/p/package-installs-apt-sources.desc --- lintian-2.93.0/tags/p/package-installs-apt-sources.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-installs-apt-sources.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,16 @@ +Tag: package-installs-apt-sources +Severity: error +Certainty: possible +Check: apt +Ref: sources.list(5) +Info: Debian packages should not install files under + /etc/apt/sources.list.d/ or install an + /etc/apt/sources.list file. + . + Package sources are under the control of the local administrator and + packages should not override local administrator choices. + . + Packages whose names end in -apt-source or + -archive-keyring are permitted to install such files. +Renamed-From: + package-install-apt-sources diff -Nru lintian-2.93.0/tags/p/package-installs-apt-sources.tag lintian-2.89.0ubuntu1/tags/p/package-installs-apt-sources.tag --- lintian-2.93.0/tags/p/package-installs-apt-sources.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-installs-apt-sources.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,15 +0,0 @@ -Tag: package-installs-apt-sources -Severity: error -Check: apt -See-Also: sources.list(5) -Explanation: Debian packages should not install files under - /etc/apt/sources.list.d/ or install an - /etc/apt/sources.list file. - . - Package sources are under the control of the local administrator and - packages should not override local administrator choices. - . - Packages whose names end in -apt-source or - -archive-keyring are permitted to install such files. -Renamed-From: - package-install-apt-sources diff -Nru lintian-2.93.0/tags/p/package-installs-deprecated-upstart-configuration.desc lintian-2.89.0ubuntu1/tags/p/package-installs-deprecated-upstart-configuration.desc --- lintian-2.93.0/tags/p/package-installs-deprecated-upstart-configuration.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-installs-deprecated-upstart-configuration.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: package-installs-deprecated-upstart-configuration +Severity: warning +Check: files/init +Info: The package installs files into the /etc/init + directory which is used by Upstart, a replacement for the /sbin/init + daemon which handles starting of tasks and services during boot, etc. + . + However, Upstart was removed in Debian "stretch" and these files are thus no + longer useful and should be removed. diff -Nru lintian-2.93.0/tags/p/package-installs-deprecated-upstart-configuration.tag lintian-2.89.0ubuntu1/tags/p/package-installs-deprecated-upstart-configuration.tag --- lintian-2.93.0/tags/p/package-installs-deprecated-upstart-configuration.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-installs-deprecated-upstart-configuration.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: package-installs-deprecated-upstart-configuration -Severity: warning -Check: files/init -Explanation: The package installs files into the /etc/init - directory which is used by Upstart, a replacement for the /sbin/init - daemon which handles starting of tasks and services during boot, etc. - . - However, Upstart was removed in Debian "stretch" and these files are thus no - longer useful and should be removed. diff -Nru lintian-2.93.0/tags/p/package-installs-file-to-usr-x11r6.desc lintian-2.89.0ubuntu1/tags/p/package-installs-file-to-usr-x11r6.desc --- lintian-2.93.0/tags/p/package-installs-file-to-usr-x11r6.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-installs-file-to-usr-x11r6.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,12 @@ +Tag: package-installs-file-to-usr-x11r6 +Severity: error +Check: desktop/x11 +Info: Packages using the X Window System should not be configured to install + files under the /usr/X11R6/ directory. Debian has switched to the modular + X tree which now uses regular FHS paths and all packages should follow. + . + Programs that use GNU autoconf and automake are usually easily configured + at compile time to use /usr/ instead of /usr/X11R6/. Packages that use + imake must build-depend on xutils-dev (>= 1:1.0.2-2) for the correct + paths. +Ref: policy 11.8.7 diff -Nru lintian-2.93.0/tags/p/package-installs-file-to-usr-x11r6.tag lintian-2.89.0ubuntu1/tags/p/package-installs-file-to-usr-x11r6.tag --- lintian-2.93.0/tags/p/package-installs-file-to-usr-x11r6.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-installs-file-to-usr-x11r6.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,12 +0,0 @@ -Tag: package-installs-file-to-usr-x11r6 -Severity: error -Check: desktop/x11 -Explanation: Packages using the X Window System should not be configured to install - files under the /usr/X11R6/ directory. Debian has switched to the modular - X tree which now uses regular FHS paths and all packages should follow. - . - Programs that use GNU autoconf and automake are usually easily configured - at compile time to use /usr/ instead of /usr/X11R6/. Packages that use - imake must build-depend on xutils-dev (>= 1:1.0.2-2) for the correct - paths. -See-Also: policy 11.8.7 diff -Nru lintian-2.93.0/tags/p/package-installs-ieee-data.desc lintian-2.89.0ubuntu1/tags/p/package-installs-ieee-data.desc --- lintian-2.93.0/tags/p/package-installs-ieee-data.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-installs-ieee-data.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,14 @@ +Tag: package-installs-ieee-data +Severity: error +Certainty: possible +Check: files/ieee-data +Ref: #785662 +Info: Debian package should not install ieee oui.txt or iab.txt file + These files are shipped in the package ieee-data and package should + depends on the ieee-data instead of shipping these files. + . + Package should symlinks to /usr/share/ieee-data/iab.txt or + /usr/share/ieee-data/oui.txt. Moreover, you should also + depends on ieee-data package. +Renamed-From: + package-install-ieee-data diff -Nru lintian-2.93.0/tags/p/package-installs-ieee-data.tag lintian-2.89.0ubuntu1/tags/p/package-installs-ieee-data.tag --- lintian-2.93.0/tags/p/package-installs-ieee-data.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-installs-ieee-data.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,13 +0,0 @@ -Tag: package-installs-ieee-data -Severity: error -Check: files/ieee-data -See-Also: Bug#785662 -Explanation: Debian package should not install ieee oui.txt or iab.txt file - These files are shipped in the package ieee-data and package should - depends on the ieee-data instead of shipping these files. - . - Package should symlinks to /usr/share/ieee-data/iab.txt or - /usr/share/ieee-data/oui.txt. Moreover, you should also - depends on ieee-data package. -Renamed-From: - package-install-ieee-data diff -Nru lintian-2.93.0/tags/p/package-installs-into-etc-gconf-schemas.desc lintian-2.89.0ubuntu1/tags/p/package-installs-into-etc-gconf-schemas.desc --- lintian-2.93.0/tags/p/package-installs-into-etc-gconf-schemas.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-installs-into-etc-gconf-schemas.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: package-installs-into-etc-gconf-schemas +Severity: warning +Check: desktop/gnome +Info: The package installs files into the /etc/gconf/schemas + directory. No package should do this; this directory is reserved for + local overrides. Instead, schemas should be installed into + /usr/share/gconf/schemas. diff -Nru lintian-2.93.0/tags/p/package-installs-into-etc-gconf-schemas.tag lintian-2.89.0ubuntu1/tags/p/package-installs-into-etc-gconf-schemas.tag --- lintian-2.93.0/tags/p/package-installs-into-etc-gconf-schemas.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-installs-into-etc-gconf-schemas.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: package-installs-into-etc-gconf-schemas -Severity: warning -Check: desktop/gnome -Explanation: The package installs files into the /etc/gconf/schemas - directory. No package should do this; this directory is reserved for - local overrides. Instead, schemas should be installed into - /usr/share/gconf/schemas. diff -Nru lintian-2.93.0/tags/p/package-installs-into-etc-rc.boot.desc lintian-2.89.0ubuntu1/tags/p/package-installs-into-etc-rc.boot.desc --- lintian-2.93.0/tags/p/package-installs-into-etc-rc.boot.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-installs-into-etc-rc.boot.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: package-installs-into-etc-rc.boot +Severity: error +Check: files/init +Info: The package installs files in the /etc/rc.boot directory, + which is obsolete. +Ref: policy 9.3.4 diff -Nru lintian-2.93.0/tags/p/package-installs-into-etc-rc.boot.tag lintian-2.89.0ubuntu1/tags/p/package-installs-into-etc-rc.boot.tag --- lintian-2.93.0/tags/p/package-installs-into-etc-rc.boot.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-installs-into-etc-rc.boot.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: package-installs-into-etc-rc.boot -Severity: error -Check: files/init -Explanation: The package installs files in the /etc/rc.boot directory, - which is obsolete. -See-Also: policy 9.3.4 diff -Nru lintian-2.93.0/tags/p/package-installs-into-etc-rc.d.desc lintian-2.89.0ubuntu1/tags/p/package-installs-into-etc-rc.d.desc --- lintian-2.93.0/tags/p/package-installs-into-etc-rc.d.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-installs-into-etc-rc.d.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: package-installs-into-etc-rc.d +Severity: error +Check: files/init +Info: The package installs files into the /etc/rc.d or + /etc/rc?.d which is not allowed. +Ref: policy 9.3.3 diff -Nru lintian-2.93.0/tags/p/package-installs-into-etc-rc.d.tag lintian-2.89.0ubuntu1/tags/p/package-installs-into-etc-rc.d.tag --- lintian-2.93.0/tags/p/package-installs-into-etc-rc.d.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-installs-into-etc-rc.d.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: package-installs-into-etc-rc.d -Severity: error -Check: files/init -Explanation: The package installs files into the /etc/rc.d or - /etc/rc?.d which is not allowed. -See-Also: policy 9.3.3 diff -Nru lintian-2.93.0/tags/p/package-installs-into-obsolete-dir.desc lintian-2.89.0ubuntu1/tags/p/package-installs-into-obsolete-dir.desc --- lintian-2.93.0/tags/p/package-installs-into-obsolete-dir.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-installs-into-obsolete-dir.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: package-installs-into-obsolete-dir +Severity: warning +Check: files/obsolete-paths +Info: The package installs files to an obsolete directory. + Please use a newer path. +Renamed-From: + package-install-into-obsolete-dir diff -Nru lintian-2.93.0/tags/p/package-installs-into-obsolete-dir.tag lintian-2.89.0ubuntu1/tags/p/package-installs-into-obsolete-dir.tag --- lintian-2.93.0/tags/p/package-installs-into-obsolete-dir.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-installs-into-obsolete-dir.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: package-installs-into-obsolete-dir -Severity: warning -Check: files/obsolete-paths -Explanation: The package installs files to an obsolete directory. - Please use a newer path. -Renamed-From: - package-install-into-obsolete-dir diff -Nru lintian-2.93.0/tags/p/package-installs-java-bytecode.desc lintian-2.89.0ubuntu1/tags/p/package-installs-java-bytecode.desc --- lintian-2.93.0/tags/p/package-installs-java-bytecode.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-installs-java-bytecode.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: package-installs-java-bytecode +Severity: warning +Check: languages/java/bytecode +Ref: java-policy 2 +Info: Compiled Java source files must not be included in the package. + This is likely due to a packaging mistake. These files should be + removed from the installed package or included in .jar + archives to save space. diff -Nru lintian-2.93.0/tags/p/package-installs-java-bytecode.tag lintian-2.89.0ubuntu1/tags/p/package-installs-java-bytecode.tag --- lintian-2.93.0/tags/p/package-installs-java-bytecode.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-installs-java-bytecode.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: package-installs-java-bytecode -Severity: warning -Check: languages/java/bytecode -See-Also: java-policy 2 -Explanation: Compiled Java source files must not be included in the package. - This is likely due to a packaging mistake. These files should be - removed from the installed package or included in .jar - archives to save space. diff -Nru lintian-2.93.0/tags/p/package-installs-nonbinary-perl-in-usr-lib-perl5.desc lintian-2.89.0ubuntu1/tags/p/package-installs-nonbinary-perl-in-usr-lib-perl5.desc --- lintian-2.93.0/tags/p/package-installs-nonbinary-perl-in-usr-lib-perl5.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-installs-nonbinary-perl-in-usr-lib-perl5.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: package-installs-nonbinary-perl-in-usr-lib-perl5 +Severity: warning +Check: languages/perl +Info: Architecture-independent Perl code should be placed in + /usr/share/perl5, not /usr/lib/.../perl5 + unless there is at least one architecture-dependent file + in the module. +Ref: perl-policy 2.3 diff -Nru lintian-2.93.0/tags/p/package-installs-nonbinary-perl-in-usr-lib-perl5.tag lintian-2.89.0ubuntu1/tags/p/package-installs-nonbinary-perl-in-usr-lib-perl5.tag --- lintian-2.93.0/tags/p/package-installs-nonbinary-perl-in-usr-lib-perl5.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-installs-nonbinary-perl-in-usr-lib-perl5.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: package-installs-nonbinary-perl-in-usr-lib-perl5 -Severity: warning -Check: languages/perl -Explanation: Architecture-independent Perl code should be placed in - /usr/share/perl5, not /usr/lib/.../perl5 - unless there is at least one architecture-dependent file - in the module. -See-Also: perl-policy 2.3 diff -Nru lintian-2.93.0/tags/p/package-installs-packlist.desc lintian-2.89.0ubuntu1/tags/p/package-installs-packlist.desc --- lintian-2.93.0/tags/p/package-installs-packlist.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-installs-packlist.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,15 @@ +Tag: package-installs-packlist +Severity: error +Check: languages/perl +Info: Packages built using the perl MakeMaker package will have a file + named .packlist in them. Those files are useless, and (in some cases) + have the additional problem of creating an architecture-specific + directory name in an architecture-independent package. + . + They can be suppressed by adding the following to debian/rules: + . + find debian/pkg -type f -name .packlist -delete + . + or by telling MakeMaker to use vendor install dirs; consult a recent + version of Perl policy. Perl 5.6.0-12 or higher supports this. +Ref: perl-policy 4.1 diff -Nru lintian-2.93.0/tags/p/package-installs-packlist.tag lintian-2.89.0ubuntu1/tags/p/package-installs-packlist.tag --- lintian-2.93.0/tags/p/package-installs-packlist.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-installs-packlist.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,15 +0,0 @@ -Tag: package-installs-packlist -Severity: error -Check: languages/perl -Explanation: Packages built using the perl MakeMaker package will have a file - named .packlist in them. Those files are useless, and (in some cases) - have the additional problem of creating an architecture-specific - directory name in an architecture-independent package. - . - They can be suppressed by adding the following to debian/rules: - . - find debian/*pkg* -type f -name .packlist -delete - . - or by telling MakeMaker to use vendor install dirs; consult a recent - version of Perl policy. Perl 5.6.0-12 or higher supports this. -See-Also: perl-policy 4.1 diff -Nru lintian-2.93.0/tags/p/package-installs-perllocal-pod.desc lintian-2.89.0ubuntu1/tags/p/package-installs-perllocal-pod.desc --- lintian-2.93.0/tags/p/package-installs-perllocal-pod.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-installs-perllocal-pod.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: package-installs-perllocal-pod +Severity: warning +Check: languages/perl +Info: This package installs a file perllocal.pod. Since that + file is intended for local documentation, it is not likely that it is + a good place for documentation supplied by a Debian package. In fact, + installing this package will wipe out whatever local documentation + existed there. diff -Nru lintian-2.93.0/tags/p/package-installs-perllocal-pod.tag lintian-2.89.0ubuntu1/tags/p/package-installs-perllocal-pod.tag --- lintian-2.93.0/tags/p/package-installs-perllocal-pod.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-installs-perllocal-pod.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: package-installs-perllocal-pod -Severity: warning -Check: languages/perl -Explanation: This package installs a file perllocal.pod. Since that - file is intended for local documentation, it is not likely that it is - a good place for documentation supplied by a Debian package. In fact, - installing this package will wipe out whatever local documentation - existed there. diff -Nru lintian-2.93.0/tags/p/package-installs-python-bytecode.desc lintian-2.89.0ubuntu1/tags/p/package-installs-python-bytecode.desc --- lintian-2.93.0/tags/p/package-installs-python-bytecode.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-installs-python-bytecode.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: package-installs-python-bytecode +Severity: error +Check: languages/python +Ref: python-policy 3.7 +Info: Compiled Python source files must not be included in the package. + These files should be removed from the package and created at package + installation time in the postinst. diff -Nru lintian-2.93.0/tags/p/package-installs-python-bytecode.tag lintian-2.89.0ubuntu1/tags/p/package-installs-python-bytecode.tag --- lintian-2.93.0/tags/p/package-installs-python-bytecode.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-installs-python-bytecode.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: package-installs-python-bytecode -Severity: error -Check: languages/python -See-Also: python-policy 3.7 -Explanation: Compiled Python source files must not be included in the package. - These files should be removed from the package and created at package - installation time in the postinst. diff -Nru lintian-2.93.0/tags/p/package-installs-python-egg.desc lintian-2.89.0ubuntu1/tags/p/package-installs-python-egg.desc --- lintian-2.93.0/tags/p/package-installs-python-egg.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-installs-python-egg.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: package-installs-python-egg +Severity: error +Certainty: possible +Check: languages/python +Ref: python-policy 3.7 +Info: Python eggs should not be installed, since the Debian package is + supposed to do the required steps for installing the Python code. + . + The egg may contain pre-compiled Python bytecode or shared libraries. diff -Nru lintian-2.93.0/tags/p/package-installs-python-egg.tag lintian-2.89.0ubuntu1/tags/p/package-installs-python-egg.tag --- lintian-2.93.0/tags/p/package-installs-python-egg.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-installs-python-egg.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: package-installs-python-egg -Severity: error -Check: languages/python -See-Also: python-policy 3.7 -Explanation: Python eggs should not be installed, since the Debian package is - supposed to do the required steps for installing the Python code. - . - The egg may contain pre-compiled Python bytecode or shared libraries. diff -Nru lintian-2.93.0/tags/p/package-installs-python-pycache-dir.desc lintian-2.89.0ubuntu1/tags/p/package-installs-python-pycache-dir.desc --- lintian-2.93.0/tags/p/package-installs-python-pycache-dir.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-installs-python-pycache-dir.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: package-installs-python-pycache-dir +Severity: error +Check: languages/python +Ref: python-policy 3.7 +Info: The package installs a __pycache__ directory, which is normally + only used to store compiled Python source files. Compiled Python + source files must not be included in the package, instead they + should be generated at installation time in the postinst. + . + Note this tag is issues even if the directory is empty. diff -Nru lintian-2.93.0/tags/p/package-installs-python-pycache-dir.tag lintian-2.89.0ubuntu1/tags/p/package-installs-python-pycache-dir.tag --- lintian-2.93.0/tags/p/package-installs-python-pycache-dir.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-installs-python-pycache-dir.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,11 +0,0 @@ -Tag: package-installs-python-pycache-dir -Severity: error -Check: languages/python -See-Also: python-policy 3.7 -Explanation: The package installs a __pycache__ - directory, which is normally - only used to store compiled Python source files. Compiled Python - source files must not be included in the package, instead they - should be generated at installation time in the postinst. - . - Note this tag is issues even if the directory is empty. diff -Nru lintian-2.93.0/tags/p/package-is-co-maintained.desc lintian-2.89.0ubuntu1/tags/p/package-is-co-maintained.desc --- lintian-2.93.0/tags/p/package-is-co-maintained.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-is-co-maintained.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: package-is-co-maintained +Severity: classification +Check: fields/vcs +Info: The package is co-maintained but not team-maintained + according to the maintainer/uploaders fields in the + debian/control file. diff -Nru lintian-2.93.0/tags/p/package-is-co-maintained.tag lintian-2.89.0ubuntu1/tags/p/package-is-co-maintained.tag --- lintian-2.93.0/tags/p/package-is-co-maintained.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-is-co-maintained.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: package-is-co-maintained -Severity: classification -Check: fields/vcs -Explanation: The package is co-maintained but not team-maintained - according to the maintainer/uploaders fields in the - debian/control file. diff -Nru lintian-2.93.0/tags/p/package-is-maintained-by-individual.desc lintian-2.89.0ubuntu1/tags/p/package-is-maintained-by-individual.desc --- lintian-2.93.0/tags/p/package-is-maintained-by-individual.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-is-maintained-by-individual.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,5 @@ +Tag: package-is-maintained-by-individual +Severity: classification +Check: fields/vcs +Info: The package is maintained by an individual according to the + maintainer/uploaders fields in the debian/control file. diff -Nru lintian-2.93.0/tags/p/package-is-maintained-by-individual.tag lintian-2.89.0ubuntu1/tags/p/package-is-maintained-by-individual.tag --- lintian-2.93.0/tags/p/package-is-maintained-by-individual.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-is-maintained-by-individual.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,5 +0,0 @@ -Tag: package-is-maintained-by-individual -Severity: classification -Check: fields/vcs -Explanation: The package is maintained by an individual according to the - maintainer/uploaders fields in the debian/control file. diff -Nru lintian-2.93.0/tags/p/package-is-team-maintained.desc lintian-2.89.0ubuntu1/tags/p/package-is-team-maintained.desc --- lintian-2.93.0/tags/p/package-is-team-maintained.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-is-team-maintained.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,5 @@ +Tag: package-is-team-maintained +Severity: classification +Check: fields/vcs +Info: The package is team-maintained according to the + maintainer/uploaders fields in the debian/control file. diff -Nru lintian-2.93.0/tags/p/package-is-team-maintained.tag lintian-2.89.0ubuntu1/tags/p/package-is-team-maintained.tag --- lintian-2.93.0/tags/p/package-is-team-maintained.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-is-team-maintained.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,5 +0,0 @@ -Tag: package-is-team-maintained -Severity: classification -Check: fields/vcs -Explanation: The package is team-maintained according to the - maintainer/uploaders fields in the debian/control file. diff -Nru lintian-2.93.0/tags/p/package-lacks-versioned-build-depends-on-debhelper.desc lintian-2.89.0ubuntu1/tags/p/package-lacks-versioned-build-depends-on-debhelper.desc --- lintian-2.93.0/tags/p/package-lacks-versioned-build-depends-on-debhelper.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-lacks-versioned-build-depends-on-debhelper.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,13 @@ +Tag: package-lacks-versioned-build-depends-on-debhelper +Severity: pedantic +Check: debhelper +Info: The package either doesn't declare a versioned build dependency on + debhelper or does not declare a versioned build dependency on a new + enough version of debhelper to satisfy the declared compatibility level. + . + Recommended practice is to always declare an explicit versioned + dependency on debhelper equal to or greater than the compatibility level + used by the package, even if the versioned dependency isn't strictly + necessary. Having a versioned dependency also helps with backports to + older releases and correct builds on partially updated systems. +Ref: debhelper(7) diff -Nru lintian-2.93.0/tags/p/package-lacks-versioned-build-depends-on-debhelper.tag lintian-2.89.0ubuntu1/tags/p/package-lacks-versioned-build-depends-on-debhelper.tag --- lintian-2.93.0/tags/p/package-lacks-versioned-build-depends-on-debhelper.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-lacks-versioned-build-depends-on-debhelper.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,13 +0,0 @@ -Tag: package-lacks-versioned-build-depends-on-debhelper -Severity: pedantic -Check: debhelper -Explanation: The package either doesn't declare a versioned build dependency on - debhelper or does not declare a versioned build dependency on a new - enough version of debhelper to satisfy the declared compatibility level. - . - Recommended practice is to always declare an explicit versioned - dependency on debhelper equal to or greater than the compatibility level - used by the package, even if the versioned dependency isn't strictly - necessary. Having a versioned dependency also helps with backports to - older releases and correct builds on partially updated systems. -See-Also: debhelper(7) diff -Nru lintian-2.93.0/tags/p/package-mixes-misc-and-dpi-fonts.desc lintian-2.89.0ubuntu1/tags/p/package-mixes-misc-and-dpi-fonts.desc --- lintian-2.93.0/tags/p/package-mixes-misc-and-dpi-fonts.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-mixes-misc-and-dpi-fonts.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: package-mixes-misc-and-dpi-fonts +Severity: warning +Check: desktop/x11 +Ref: policy 11.8.5 +Info: This package contains both bitmapped fonts for a specific DPI + (100dpi or 75dpi) and misc bitmapped fonts. These should not be combined + in the same package. Instead, the misc bitmapped fonts should be + provided in a separate package with -misc appended to its name. diff -Nru lintian-2.93.0/tags/p/package-mixes-misc-and-dpi-fonts.tag lintian-2.89.0ubuntu1/tags/p/package-mixes-misc-and-dpi-fonts.tag --- lintian-2.93.0/tags/p/package-mixes-misc-and-dpi-fonts.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-mixes-misc-and-dpi-fonts.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: package-mixes-misc-and-dpi-fonts -Severity: warning -Check: desktop/x11 -See-Also: policy 11.8.5 -Explanation: This package contains both bitmapped fonts for a specific DPI - (100dpi or 75dpi) and misc bitmapped fonts. These should not be combined - in the same package. Instead, the misc bitmapped fonts should be - provided in a separate package with -misc appended to its name. diff -Nru lintian-2.93.0/tags/p/package-modifies-ld.so-search-path.desc lintian-2.89.0ubuntu1/tags/p/package-modifies-ld.so-search-path.desc --- lintian-2.93.0/tags/p/package-modifies-ld.so-search-path.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-modifies-ld.so-search-path.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,15 @@ +Tag: package-modifies-ld.so-search-path +Severity: error +Check: files/ld-so +Info: The package changes the search path for the runtime linker, but is + not part of libc. The offending file is in + /etc/ld.so.conf.d. + . + It is not okay to install libraries in a different directory and then + modify the run-time link path. Shared libraries should go into + /usr/lib. Alternatively, they can require binaries to set the + RPATH to find the library. + . + Without this precaution, conflicting libraries may trigger segmentation + faults for what should have been a conflict in the package manager. +Ref: policy 10.2 diff -Nru lintian-2.93.0/tags/p/package-modifies-ld.so-search-path.tag lintian-2.89.0ubuntu1/tags/p/package-modifies-ld.so-search-path.tag --- lintian-2.93.0/tags/p/package-modifies-ld.so-search-path.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-modifies-ld.so-search-path.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,15 +0,0 @@ -Tag: package-modifies-ld.so-search-path -Severity: error -Check: files/ld-so -Explanation: The package changes the search path for the runtime linker, but is - not part of libc. The offending file is in - /etc/ld.so.conf.d. - . - It is not okay to install libraries in a different directory and then - modify the run-time link path. Shared libraries should go into - /usr/lib. Alternatively, they can require binaries to set the - RPATH to find the library. - . - Without this precaution, conflicting libraries may trigger segmentation - faults for what should have been a conflict in the package manager. -See-Also: policy 10.2 diff -Nru lintian-2.93.0/tags/p/package-name-defined-in-config-h.desc lintian-2.89.0ubuntu1/tags/p/package-name-defined-in-config-h.desc --- lintian-2.93.0/tags/p/package-name-defined-in-config-h.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-name-defined-in-config-h.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: package-name-defined-in-config-h +Severity: warning +Check: includes/config-h +Info: This package installs a header file named config.h that + uses the identifier PACKAGE_NAME. It is probably incompatible with + packages using autoconf. + . + Please remove the file or rename the identifier. +Ref: #733598 diff -Nru lintian-2.93.0/tags/p/package-name-defined-in-config-h.tag lintian-2.89.0ubuntu1/tags/p/package-name-defined-in-config-h.tag --- lintian-2.93.0/tags/p/package-name-defined-in-config-h.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-name-defined-in-config-h.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: package-name-defined-in-config-h -Severity: warning -Check: includes/config-h -Explanation: This package installs a header file named config.h that - uses the identifier PACKAGE_NAME. It is probably incompatible with - packages using autoconf. - . - Please remove the file or rename the identifier. -See-Also: Bug#733598 diff -Nru lintian-2.93.0/tags/p/package-name-doesnt-match-sonames.desc lintian-2.89.0ubuntu1/tags/p/package-name-doesnt-match-sonames.desc --- lintian-2.93.0/tags/p/package-name-doesnt-match-sonames.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-name-doesnt-match-sonames.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: package-name-doesnt-match-sonames +Severity: warning +Certainty: possible +Check: binaries +Info: The package name of a library package should usually reflect + the soname of the included library. The package name can determined + from the library file name with the following code snippet: + . + $ objdump -p /path/to/libfoo-bar.so.1.2.3 | sed -n -e's/^[[:space:]]*SONAME[[:space:]]*//p' | \ + sed -r -e's/([0-9])\.so\./\1-/; s/\.so(\.|$)//; y/_/-/; s/(.*)/\L&/' diff -Nru lintian-2.93.0/tags/p/package-name-doesnt-match-sonames.tag lintian-2.89.0ubuntu1/tags/p/package-name-doesnt-match-sonames.tag --- lintian-2.93.0/tags/p/package-name-doesnt-match-sonames.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-name-doesnt-match-sonames.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: package-name-doesnt-match-sonames -Severity: warning -Check: binaries -Explanation: The package name of a library package should usually reflect - the soname of the included library. The package name can determined - from the library file name with the following code snippet: - . - $ objdump -p /path/to/libfoo-bar.so.1.2.3 | sed -n -e's/^[[:space:]]*SONAME[[:space:]]*//p' | \ - sed -r -e's/([0-9])\.so\./\1-/; s/\.so(\.|$)//; y/_/-/; s/(.*)/\L&/' diff -Nru lintian-2.93.0/tags/p/package-needs-versioned-debhelper-build-depends.desc lintian-2.89.0ubuntu1/tags/p/package-needs-versioned-debhelper-build-depends.desc --- lintian-2.93.0/tags/p/package-needs-versioned-debhelper-build-depends.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-needs-versioned-debhelper-build-depends.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,26 @@ +Tag: package-needs-versioned-debhelper-build-depends +Severity: warning +Check: debhelper +Info: The package either doesn't declare a versioned build dependency on + debhelper or does not declare a versioned build dependency on a new + enough version of debhelper to satisfy the declared compatibility level. + . + The required version of debhelper is not guaranteed to be satisfied + in all supported releases of Debian and therefore this may lead to + a build failure. + . + The recommended practice is to always declare an explicit versioned + dependency on debhelper equal to or greater than the compatibility level + used by the package, even if the versioned dependency isn't strictly + necessary. Having a versioned dependency also helps with backports to + older releases and correct builds on partially updated systems. + . + Packages not using an experimental or beta compatibility level may + alternatively Build-Depend on the debhelper-compat virtual package, for + example: + . + Build-Depends: debhelper-compat (= 13) + . + Note if you are using a compat level marked as experimental (such as + compat 12 in debhelper 11.4~) please explicitly override this tag. +Ref: debhelper(7) diff -Nru lintian-2.93.0/tags/p/package-needs-versioned-debhelper-build-depends.tag lintian-2.89.0ubuntu1/tags/p/package-needs-versioned-debhelper-build-depends.tag --- lintian-2.93.0/tags/p/package-needs-versioned-debhelper-build-depends.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-needs-versioned-debhelper-build-depends.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,26 +0,0 @@ -Tag: package-needs-versioned-debhelper-build-depends -Severity: warning -Check: debhelper -Explanation: The package either doesn't declare a versioned build dependency on - debhelper or does not declare a versioned build dependency on a new - enough version of debhelper to satisfy the declared compatibility level. - . - The required version of debhelper is not guaranteed to be satisfied - in all supported releases of Debian and therefore this may lead to - a build failure. - . - The recommended practice is to always declare an explicit versioned - dependency on debhelper equal to or greater than the compatibility level - used by the package, even if the versioned dependency isn't strictly - necessary. Having a versioned dependency also helps with backports to - older releases and correct builds on partially updated systems. - . - Packages not using an experimental or beta compatibility level may - alternatively Build-Depend on the debhelper-compat virtual package, for - example: - . - Build-Depends: debhelper-compat (= 13) - . - Note if you are using a compat level marked as experimental (such as - compat 12 in debhelper 11.4~) please explicitly override this tag. -See-Also: debhelper(7) diff -Nru lintian-2.93.0/tags/p/package-not-lowercase.desc lintian-2.89.0ubuntu1/tags/p/package-not-lowercase.desc --- lintian-2.93.0/tags/p/package-not-lowercase.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-not-lowercase.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,5 @@ +Tag: package-not-lowercase +Severity: error +Check: fields/package +Info: New packages should not use uppercase characters in their names. +Ref: policy 5.6.7 diff -Nru lintian-2.93.0/tags/p/package-not-lowercase.tag lintian-2.89.0ubuntu1/tags/p/package-not-lowercase.tag --- lintian-2.93.0/tags/p/package-not-lowercase.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-not-lowercase.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,5 +0,0 @@ -Tag: package-not-lowercase -Severity: error -Check: fields/package -Explanation: New packages should not use uppercase characters in their names. -See-Also: policy 5.6.7 diff -Nru lintian-2.93.0/tags/p/package-placeholder-in-symbols-file.desc lintian-2.89.0ubuntu1/tags/p/package-placeholder-in-symbols-file.desc --- lintian-2.93.0/tags/p/package-placeholder-in-symbols-file.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-placeholder-in-symbols-file.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,17 @@ +Tag: package-placeholder-in-symbols-file +Severity: warning +Check: debian/symbols +Info: The symbols file contains the placeholder #PACKAGE# + in the Build-Depends-Package field. During the build process, it + will be replaced with the wrong value. There is no placeholder that works. + . + The development package for your shared library must be stated explicitly. + . + With the information, dpkg-shlibdeps(1) can calculate the + installation prerequisites for your package from the build prerequisites. +Ref: + policy 8.6.3.2, + deb-symbols(5), + dpkg-shlibdeps(1), + https://www.debian.org/doc/manuals/maint-guide/advanced.en.html#librarysymbols, + #944047 diff -Nru lintian-2.93.0/tags/p/package-placeholder-in-symbols-file.tag lintian-2.89.0ubuntu1/tags/p/package-placeholder-in-symbols-file.tag --- lintian-2.93.0/tags/p/package-placeholder-in-symbols-file.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-placeholder-in-symbols-file.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,17 +0,0 @@ -Tag: package-placeholder-in-symbols-file -Severity: warning -Check: debian/symbols -Explanation: The symbols file contains the placeholder #PACKAGE# - in the Build-Depends-Package field. During the build process, it - will be replaced with the wrong value. There is no placeholder that works. - . - The development package for your shared library must be stated explicitly. - . - With the information, dpkg-shlibdeps(1) can calculate the - installation prerequisites for your package from the build prerequisites. -See-Also: - policy 8.6.3.2, - deb-symbols(5), - dpkg-shlibdeps(1), - https://www.debian.org/doc/manuals/maint-guide/advanced.en.html#librarysymbols, - Bug#944047 diff -Nru lintian-2.93.0/tags/p/package-relation-with-perl-modules.desc lintian-2.89.0ubuntu1/tags/p/package-relation-with-perl-modules.desc --- lintian-2.93.0/tags/p/package-relation-with-perl-modules.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-relation-with-perl-modules.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +# Imported from pkg-perl-tools (named depends-on-perl-modules there) +Tag: package-relation-with-perl-modules +Severity: error +Check: fields/package-relations +Info: No package should (build-) depend on 'perl-modules'. Instead, a + suitable dependency on 'perl' should be used. The existence of the + perl-modules package is an implementation detail of the perl + packaging. diff -Nru lintian-2.93.0/tags/p/package-relation-with-perl-modules.tag lintian-2.89.0ubuntu1/tags/p/package-relation-with-perl-modules.tag --- lintian-2.93.0/tags/p/package-relation-with-perl-modules.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-relation-with-perl-modules.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -# Imported from pkg-perl-tools (named depends-on-perl-modules there) -Tag: package-relation-with-perl-modules -Severity: error -Check: fields/package-relations -Explanation: No package should (build-) depend on 'perl-modules'. Instead, a - suitable dependency on 'perl' should be used. The existence of the - perl-modules package is an implementation detail of the perl - packaging. diff -Nru lintian-2.93.0/tags/p/package-relation-with-self.desc lintian-2.89.0ubuntu1/tags/p/package-relation-with-self.desc --- lintian-2.93.0/tags/p/package-relation-with-self.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-relation-with-self.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: package-relation-with-self +Severity: warning +Certainty: possible +Check: fields/package-relations +Info: The package declares a relationship with itself. This is not very + useful except in the case of a package Conflicting with itself if its + package name doubles as a virtual package. diff -Nru lintian-2.93.0/tags/p/package-relation-with-self.tag lintian-2.89.0ubuntu1/tags/p/package-relation-with-self.tag --- lintian-2.93.0/tags/p/package-relation-with-self.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-relation-with-self.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: package-relation-with-self -Severity: warning -Check: fields/package-relations -Explanation: The package declares a relationship with itself. This is not very - useful except in the case of a package Conflicting with itself if its - package name doubles as a virtual package. diff -Nru lintian-2.93.0/tags/p/package-section-games-but-contains-no-game.desc lintian-2.89.0ubuntu1/tags/p/package-section-games-but-contains-no-game.desc --- lintian-2.93.0/tags/p/package-section-games-but-contains-no-game.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-section-games-but-contains-no-game.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: package-section-games-but-contains-no-game +Severity: error +Check: games +Ref: policy 11.11 +Info: This package is marked as part of the section games, but doesn't + contain files in /usr/games. Binaries of games must be installed + in /usr/games. diff -Nru lintian-2.93.0/tags/p/package-section-games-but-contains-no-game.tag lintian-2.89.0ubuntu1/tags/p/package-section-games-but-contains-no-game.tag --- lintian-2.93.0/tags/p/package-section-games-but-contains-no-game.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-section-games-but-contains-no-game.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: package-section-games-but-contains-no-game -Severity: error -Check: games -See-Also: policy 11.11 -Explanation: This package is marked as part of the section games, but doesn't - contain files in /usr/games. Binaries of games must be installed - in /usr/games. diff -Nru lintian-2.93.0/tags/p/package-section-games-but-has-usr-bin.desc lintian-2.89.0ubuntu1/tags/p/package-section-games-but-has-usr-bin.desc --- lintian-2.93.0/tags/p/package-section-games-but-has-usr-bin.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-section-games-but-has-usr-bin.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: package-section-games-but-has-usr-bin +Severity: warning +Certainty: possible +Check: games +Ref: policy 11.11 +Info: This package is marked as part of the section games, but contains + executables in /bin or /usr/bin/. This can be intentional, + but is usually a mistake. diff -Nru lintian-2.93.0/tags/p/package-section-games-but-has-usr-bin.tag lintian-2.89.0ubuntu1/tags/p/package-section-games-but-has-usr-bin.tag --- lintian-2.93.0/tags/p/package-section-games-but-has-usr-bin.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-section-games-but-has-usr-bin.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: package-section-games-but-has-usr-bin -Severity: warning -Check: games -See-Also: policy 11.11 -Explanation: This package is marked as part of the section games, but contains - executables in /bin or /usr/bin/. This can be intentional, - but is usually a mistake. diff -Nru lintian-2.93.0/tags/p/package-superseded-by-perl.desc lintian-2.89.0ubuntu1/tags/p/package-superseded-by-perl.desc --- lintian-2.93.0/tags/p/package-superseded-by-perl.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-superseded-by-perl.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,23 @@ +Tag: package-superseded-by-perl +Severity: warning +Check: fields/version +Info: This package is also provided by one of the Perl core packages + (perl, perl-base, perl-modules), and the core version is at least + as new as this one. + . + The package should either be upgraded to a newer upstream version + or removed from the archive as unnecessary. In the removal case, any + versioned dependencies on this package must first be changed to include + the Perl core package (because versioned dependencies are not satisfied + by provided packages). + . + The recommended way to express the dependency without needless + complications on backporting packages is to use alternative dependencies. + The perl package should be the preferred alternative and the + versioned dependency a secondary one. + . + Example: perl (>= 5.10.0) | libmodule-build-perl (>= 0.26) + . + Running cme fix dpkg -from control -filter Depends should be able + to update these dependencies. +Ref: policy 7.5 diff -Nru lintian-2.93.0/tags/p/package-superseded-by-perl.tag lintian-2.89.0ubuntu1/tags/p/package-superseded-by-perl.tag --- lintian-2.93.0/tags/p/package-superseded-by-perl.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-superseded-by-perl.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,23 +0,0 @@ -Tag: package-superseded-by-perl -Severity: warning -Check: fields/version -Explanation: This package is also provided by one of the Perl core packages - (perl, perl-base, perl-modules), and the core version is at least - as new as this one. - . - The package should either be upgraded to a newer upstream version - or removed from the archive as unnecessary. In the removal case, any - versioned dependencies on this package must first be changed to include - the Perl core package (because versioned dependencies are not satisfied - by provided packages). - . - The recommended way to express the dependency without needless - complications on backporting packages is to use alternative dependencies. - The perl package should be the preferred alternative and the - versioned dependency a secondary one. - . - Example: perl (>= 5.10.0) | libmodule-build-perl (>= 0.26) - . - Running cme fix dpkg -from control -filter Depends should be able - to update these dependencies. -See-Also: policy 7.5 diff -Nru lintian-2.93.0/tags/p/package-supports-alternative-init-but-no-init.d-script.desc lintian-2.89.0ubuntu1/tags/p/package-supports-alternative-init-but-no-init.d-script.desc --- lintian-2.93.0/tags/p/package-supports-alternative-init-but-no-init.d-script.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-supports-alternative-init-but-no-init.d-script.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,15 @@ +Tag: package-supports-alternative-init-but-no-init.d-script +Severity: info +Certainty: possible +Check: init.d +Ref: policy 9.11 +Info: The package provides daemon, but contains no init.d script + Packages that provide services (daemons), like cron daemon or web servers, + must provide init.d script for starting that services with sysvinit. + Optionally, packages can also provide integration with alternative init + systems. + . + Package in question provides integration with some alternative init system, + but corresponding init.d script is absent. + . + See init-d-script(5) for one of possible ways writing init.d scripts. diff -Nru lintian-2.93.0/tags/p/package-supports-alternative-init-but-no-init.d-script.tag lintian-2.89.0ubuntu1/tags/p/package-supports-alternative-init-but-no-init.d-script.tag --- lintian-2.93.0/tags/p/package-supports-alternative-init-but-no-init.d-script.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-supports-alternative-init-but-no-init.d-script.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,14 +0,0 @@ -Tag: package-supports-alternative-init-but-no-init.d-script -Severity: info -Check: init.d -See-Also: policy 9.11 -Explanation: The package provides daemon, but contains no init.d script - Packages that provide services (daemons), like cron daemon or web servers, - must provide init.d script for starting that services with sysvinit. - Optionally, packages can also provide integration with alternative init - systems. - . - Package in question provides integration with some alternative init system, - but corresponding init.d script is absent. - . - See init-d-script(5) for one of possible ways writing init.d scripts. diff -Nru lintian-2.93.0/tags/p/package-uses-debhelper-but-lacks-build-depends.desc lintian-2.89.0ubuntu1/tags/p/package-uses-debhelper-but-lacks-build-depends.desc --- lintian-2.93.0/tags/p/package-uses-debhelper-but-lacks-build-depends.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-uses-debhelper-but-lacks-build-depends.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: package-uses-debhelper-but-lacks-build-depends +Severity: error +Certainty: possible +Check: debhelper +Info: If a package uses debhelper, it must declare a Build-Depends + on debhelper or on the debhelper-compat virtual package. For example: + . + Build-Depends: debhelper (>= 13~) + . + Build-Depends: debhelper-compat (= 13) diff -Nru lintian-2.93.0/tags/p/package-uses-debhelper-but-lacks-build-depends.tag lintian-2.89.0ubuntu1/tags/p/package-uses-debhelper-but-lacks-build-depends.tag --- lintian-2.93.0/tags/p/package-uses-debhelper-but-lacks-build-depends.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-uses-debhelper-but-lacks-build-depends.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: package-uses-debhelper-but-lacks-build-depends -Severity: error -Check: debhelper -Explanation: If a package uses debhelper, it must declare a Build-Depends - on debhelper or on the debhelper-compat virtual package. For example: - . - Build-Depends: debhelper (>= 13~) - . - Build-Depends: debhelper-compat (= 13) diff -Nru lintian-2.93.0/tags/p/package-uses-deprecated-debhelper-compat-version.desc lintian-2.89.0ubuntu1/tags/p/package-uses-deprecated-debhelper-compat-version.desc --- lintian-2.93.0/tags/p/package-uses-deprecated-debhelper-compat-version.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-uses-deprecated-debhelper-compat-version.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,14 @@ +Tag: package-uses-deprecated-debhelper-compat-version +Severity: warning +Check: debhelper +Ref: debhelper(7) +Info: The debhelper compatibility version used by this package is marked + as deprecated by the debhelper developer. You should really consider + using a newer compatibility version. + . + The compatibility version can be set by specifying + debhelper-compat (= 12) in your package's + Build-Depends, by the legacy debian/compat file or + even by setting and exporting DH_COMPAT in debian/rules. If it + is not set in either place, debhelper defaults to the deprecated + compatibility version 1. diff -Nru lintian-2.93.0/tags/p/package-uses-deprecated-debhelper-compat-version.tag lintian-2.89.0ubuntu1/tags/p/package-uses-deprecated-debhelper-compat-version.tag --- lintian-2.93.0/tags/p/package-uses-deprecated-debhelper-compat-version.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-uses-deprecated-debhelper-compat-version.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,14 +0,0 @@ -Tag: package-uses-deprecated-debhelper-compat-version -Severity: warning -Check: debhelper -See-Also: debhelper(7) -Explanation: The debhelper compatibility version used by this package is marked - as deprecated by the debhelper developer. You should really consider - using a newer compatibility version. - . - The compatibility version can be set by specifying - debhelper-compat (= 12) in your package's - Build-Depends, by the legacy debian/compat file or - even by setting and exporting DH_COMPAT in debian/rules. If it - is not set in either place, debhelper defaults to the deprecated - compatibility version 1. diff -Nru lintian-2.93.0/tags/p/package-uses-deprecated-dpatch-patch-system.desc lintian-2.89.0ubuntu1/tags/p/package-uses-deprecated-dpatch-patch-system.desc --- lintian-2.93.0/tags/p/package-uses-deprecated-dpatch-patch-system.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-uses-deprecated-dpatch-patch-system.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: package-uses-deprecated-dpatch-patch-system +Severity: pedantic +Check: debian/patches/dpatch +Info: The dpatch patch system has been deprecated and superceded by the + "3.0 (quilt)" source format. + . + Please migrate the patches in the debian/patches directory and + the 00list file to use this source format. +Ref: dpatch(1), dpkg-source(1) diff -Nru lintian-2.93.0/tags/p/package-uses-deprecated-dpatch-patch-system.tag lintian-2.89.0ubuntu1/tags/p/package-uses-deprecated-dpatch-patch-system.tag --- lintian-2.93.0/tags/p/package-uses-deprecated-dpatch-patch-system.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-uses-deprecated-dpatch-patch-system.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: package-uses-deprecated-dpatch-patch-system -Severity: pedantic -Check: debian/patches/dpatch -Explanation: The dpatch patch system has been deprecated and superceded by the - "3.0 (quilt)" source format. - . - Please migrate the patches in the debian/patches directory and - the 00list file to use this source format. -See-Also: dpatch(1), dpkg-source(1) diff -Nru lintian-2.93.0/tags/p/package-uses-dh-exec-but-lacks-build-depends.desc lintian-2.89.0ubuntu1/tags/p/package-uses-dh-exec-but-lacks-build-depends.desc --- lintian-2.93.0/tags/p/package-uses-dh-exec-but-lacks-build-depends.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-uses-dh-exec-but-lacks-build-depends.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: package-uses-dh-exec-but-lacks-build-depends +Severity: error +Certainty: possible +Check: debhelper +Info: If a package uses dh-exec, it must declare a Build-Depends + on it. diff -Nru lintian-2.93.0/tags/p/package-uses-dh-exec-but-lacks-build-depends.tag lintian-2.89.0ubuntu1/tags/p/package-uses-dh-exec-but-lacks-build-depends.tag --- lintian-2.93.0/tags/p/package-uses-dh-exec-but-lacks-build-depends.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-uses-dh-exec-but-lacks-build-depends.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,5 +0,0 @@ -Tag: package-uses-dh-exec-but-lacks-build-depends -Severity: error -Check: debhelper -Explanation: If a package uses dh-exec, it must declare a Build-Depends - on it. diff -Nru lintian-2.93.0/tags/p/package-uses-dh-runit-but-lacks-breaks-substvar.desc lintian-2.89.0ubuntu1/tags/p/package-uses-dh-runit-but-lacks-breaks-substvar.desc --- lintian-2.93.0/tags/p/package-uses-dh-runit-but-lacks-breaks-substvar.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-uses-dh-runit-but-lacks-breaks-substvar.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,13 @@ +Tag: package-uses-dh-runit-but-lacks-breaks-substvar +Severity: warning +Certainty: possible +Check: debhelper +Info: This source package appears to use dh_runit(1) but the + specified binary package does not define a Breaks: including + the ${runit:Breaks} substitution variable. + . + dh_runit(1) may generate scripts that make assumptions about + the version of runit in use. + . + Please add the corresponding Breaks relation. +Ref: dh_runit(1) diff -Nru lintian-2.93.0/tags/p/package-uses-dh-runit-but-lacks-breaks-substvar.tag lintian-2.89.0ubuntu1/tags/p/package-uses-dh-runit-but-lacks-breaks-substvar.tag --- lintian-2.93.0/tags/p/package-uses-dh-runit-but-lacks-breaks-substvar.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-uses-dh-runit-but-lacks-breaks-substvar.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,12 +0,0 @@ -Tag: package-uses-dh-runit-but-lacks-breaks-substvar -Severity: warning -Check: debhelper -Explanation: This source package appears to use dh_runit(1) but the - specified binary package does not define a Breaks: including - the ${runit:Breaks} substitution variable. - . - dh_runit(1) may generate scripts that make assumptions about - the version of runit in use. - . - Please add the corresponding Breaks relation. -See-Also: dh_runit(1) diff -Nru lintian-2.93.0/tags/p/package-uses-experimental-debhelper-compat-version.desc lintian-2.89.0ubuntu1/tags/p/package-uses-experimental-debhelper-compat-version.desc --- lintian-2.93.0/tags/p/package-uses-experimental-debhelper-compat-version.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-uses-experimental-debhelper-compat-version.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,14 @@ +Tag: package-uses-experimental-debhelper-compat-version +Severity: pedantic +Check: debhelper +Ref: debhelper(7) +Info: The debhelper compatibility version used by this package is marked + as experimental by the debhelper developer. You should consider using a + stable compatibility version instead. + . + The compatibility version can be set by specifying + debhelper-compat (= 12) in your package's + Build-Depends, by the legacy debian/compat file or + even by setting and exporting DH_COMPAT in debian/rules. If it + is not set in either place, debhelper defaults to the deprecated + compatibility version 1. diff -Nru lintian-2.93.0/tags/p/package-uses-experimental-debhelper-compat-version.tag lintian-2.89.0ubuntu1/tags/p/package-uses-experimental-debhelper-compat-version.tag --- lintian-2.93.0/tags/p/package-uses-experimental-debhelper-compat-version.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-uses-experimental-debhelper-compat-version.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,14 +0,0 @@ -Tag: package-uses-experimental-debhelper-compat-version -Severity: pedantic -Check: debhelper -See-Also: debhelper(7) -Explanation: The debhelper compatibility version used by this package is marked - as experimental by the debhelper developer. You should consider using a - stable compatibility version instead. - . - The compatibility version can be set by specifying - debhelper-compat (= 12) in your package's - Build-Depends, by the legacy debian/compat file or - even by setting and exporting DH_COMPAT in debian/rules. If it - is not set in either place, debhelper defaults to the deprecated - compatibility version 1. diff -Nru lintian-2.93.0/tags/p/package-uses-local-diversion.desc lintian-2.89.0ubuntu1/tags/p/package-uses-local-diversion.desc --- lintian-2.93.0/tags/p/package-uses-local-diversion.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-uses-local-diversion.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: package-uses-local-diversion +Severity: error +Check: scripts +Ref: policy 3.9 +Info: The maintainer script calls dpkg-divert with --local or + without --package. This option is reserved for local + administrators and must never be used by a Debian package. diff -Nru lintian-2.93.0/tags/p/package-uses-local-diversion.tag lintian-2.89.0ubuntu1/tags/p/package-uses-local-diversion.tag --- lintian-2.93.0/tags/p/package-uses-local-diversion.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-uses-local-diversion.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: package-uses-local-diversion -Severity: error -Check: scripts -See-Also: policy 3.9 -Explanation: The maintainer script calls dpkg-divert with --local or - without --package. This option is reserved for local - administrators and must never be used by a Debian package. diff -Nru lintian-2.93.0/tags/p/package-uses-old-debhelper-compat-version.desc lintian-2.89.0ubuntu1/tags/p/package-uses-old-debhelper-compat-version.desc --- lintian-2.93.0/tags/p/package-uses-old-debhelper-compat-version.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-uses-old-debhelper-compat-version.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,13 @@ +Tag: package-uses-old-debhelper-compat-version +Severity: pedantic +Check: debhelper +Info: This package uses a debhelper compatibility level that is no + longer recommended. Please consider using a recommended level. + . + For most packages, the best way to set the compatibility level is + to specify debhelper-compat (= X) as a Build-Depends + in debian/control. You can also use the debian/compat + file or export DH_COMPAT in debian/rules. + . + If no level is selected debhelper defaults to level 1, which is deprecated. +Ref: debhelper(7) diff -Nru lintian-2.93.0/tags/p/package-uses-old-debhelper-compat-version.tag lintian-2.89.0ubuntu1/tags/p/package-uses-old-debhelper-compat-version.tag --- lintian-2.93.0/tags/p/package-uses-old-debhelper-compat-version.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-uses-old-debhelper-compat-version.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,13 +0,0 @@ -Tag: package-uses-old-debhelper-compat-version -Severity: pedantic -Check: debhelper -Explanation: This package uses a debhelper compatibility level that is no - longer recommended. Please consider using the recommended level. - . - For most packages, the best way to set the compatibility level is - to specify debhelper-compat (= X) as a Build-Depends - in debian/control. You can also use the debian/compat - file or export DH_COMPAT in debian/rules. - . - If no level is selected debhelper defaults to level 1, which is deprecated. -See-Also: debhelper(7) diff -Nru lintian-2.93.0/tags/p/package-uses-vendor-specific-patch-series.desc lintian-2.89.0ubuntu1/tags/p/package-uses-vendor-specific-patch-series.desc --- lintian-2.93.0/tags/p/package-uses-vendor-specific-patch-series.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-uses-vendor-specific-patch-series.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,25 @@ +Tag: package-uses-vendor-specific-patch-series +Severity: error +Check: debian/patches/quilt +Info: The specified series file for patches is vendor-specific. + . + Source packages may contain vendor (i.e. distribution) specific patches, + but such packages must not be uploaded to the Debian archive if they + are used in conjunction with vendor-specific series files. + . + Vendor specific series files were carefully implemented as a dpkg + feature. Unfortunately, they currently conflict with some workflow goals + in Debian. They are presently disallowed in Debian. + . + The preferred approach for distributions other than Debian is now to + apply such patches programmatically via debian/rules. You can + also create multiple, vendor-specific sources and upload them separately + for each distribution. + . + The decision to prohibit the use of that particular dpkg feature + in Debian was made by the project's technical committee in consideration of + other planned workflow modifications, and may be revisited. + . + You should only see this tag in Debian or other distributions when + targeting an upload for Debian. +Ref: #904302, #922531, https://lists.debian.org/debian-devel-announce/2018/11/msg00004.html diff -Nru lintian-2.93.0/tags/p/package-uses-vendor-specific-patch-series.tag lintian-2.89.0ubuntu1/tags/p/package-uses-vendor-specific-patch-series.tag --- lintian-2.93.0/tags/p/package-uses-vendor-specific-patch-series.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/package-uses-vendor-specific-patch-series.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,25 +0,0 @@ -Tag: package-uses-vendor-specific-patch-series -Severity: error -Check: debian/patches/quilt -Explanation: The specified series file for patches is vendor-specific. - . - Source packages may contain vendor (i.e. distribution) specific patches, - but such packages must not be uploaded to the Debian archive if they - are used in conjunction with vendor-specific series files. - . - Vendor specific series files were carefully implemented as a dpkg - feature. Unfortunately, they currently conflict with some workflow goals - in Debian. They are presently disallowed in Debian. - . - The preferred approach for distributions other than Debian is now to - apply such patches programmatically via debian/rules. You can - also create multiple, vendor-specific sources and upload them separately - for each distribution. - . - The decision to prohibit the use of that particular dpkg feature - in Debian was made by the project's technical committee in consideration of - other planned workflow modifications, and may be revisited. - . - You should only see this tag in Debian or other distributions when - targeting an upload for Debian. -See-Also: Bug#904302, Bug#922531, https://lists.debian.org/debian-devel-announce/2018/11/msg00004.html diff -Nru lintian-2.93.0/tags/p/patched-file-without-utf8-name.desc lintian-2.89.0ubuntu1/tags/p/patched-file-without-utf8-name.desc --- lintian-2.93.0/tags/p/patched-file-without-utf8-name.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/patched-file-without-utf8-name.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,12 @@ +Tag: patched-file-without-utf8-name +Severity: error +Check: files/names +Ref: policy 10.10 +Info: The file name in the patched source tree is not valid UTF-8. + The file does not appear in the upstream files. Its appearance is + considered the responsibility of the package maintainer. Please + rename the file. + . + Unlike other file names in Lintian, which are printed in UTF-8, the + attached reference shows the bytes used by the file system. + Unprintable characters may have been replaced. diff -Nru lintian-2.93.0/tags/p/patched-file-without-utf8-name.tag lintian-2.89.0ubuntu1/tags/p/patched-file-without-utf8-name.tag --- lintian-2.93.0/tags/p/patched-file-without-utf8-name.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/patched-file-without-utf8-name.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,12 +0,0 @@ -Tag: patched-file-without-utf8-name -Severity: error -Check: files/names -See-Also: policy 10.10 -Explanation: The file name in the patched source tree is not valid UTF-8. - The file does not appear in the upstream files. Its appearance is - considered the responsibility of the package maintainer. Please - rename the file. - . - Unlike other file names in Lintian, which are printed in UTF-8, the - attached reference shows the bytes used by the file system. - Unprintable characters may have been replaced. diff -Nru lintian-2.93.0/tags/p/patch-file-present-but-not-mentioned-in-series.desc lintian-2.89.0ubuntu1/tags/p/patch-file-present-but-not-mentioned-in-series.desc --- lintian-2.93.0/tags/p/patch-file-present-but-not-mentioned-in-series.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/patch-file-present-but-not-mentioned-in-series.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,14 @@ +Tag: patch-file-present-but-not-mentioned-in-series +Severity: warning +Check: debian/patches/quilt +Info: The specified patch is present under the debian/patches + directory but is not mentioned in any "series" or "00list" file. + . + This may mean that a patch was created with the intention of modifying + the package but is not being applied. + . + Please either add the filename to the series file, or ensure it is + commented-out in a form that Lintian can recognise, for example: + . + 0001_fix-foo.patch + # 0002_fix-bar.patch diff -Nru lintian-2.93.0/tags/p/patch-file-present-but-not-mentioned-in-series.tag lintian-2.89.0ubuntu1/tags/p/patch-file-present-but-not-mentioned-in-series.tag --- lintian-2.93.0/tags/p/patch-file-present-but-not-mentioned-in-series.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/patch-file-present-but-not-mentioned-in-series.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,14 +0,0 @@ -Tag: patch-file-present-but-not-mentioned-in-series -Severity: warning -Check: debian/patches/quilt -Explanation: The specified patch is present under the debian/patches - directory but is not mentioned in any "series" or "00list" file. - . - This may mean that a patch was created with the intention of modifying - the package but is not being applied. - . - Please either add the filename to the series file, or ensure it is - commented-out in a form that Lintian can recognise, for example: - . - 0001_fix-foo.patch - # 0002_fix-bar.patch diff -Nru lintian-2.93.0/tags/p/patch-modifying-debian-files.desc lintian-2.89.0ubuntu1/tags/p/patch-modifying-debian-files.desc --- lintian-2.93.0/tags/p/patch-modifying-debian-files.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/patch-modifying-debian-files.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: patch-modifying-debian-files +Severity: error +Check: debian/patches/quilt +Info: A patch stored in debian/patches/ modifies or creates files + in the debian folder, but that folder is already under the + maintainer's exclusive control. + . + It may be more appropriate to patch or create files in the upstream + directory hierarchy, but often it is easier to place a copy in the + debian folder. diff -Nru lintian-2.93.0/tags/p/patch-modifying-debian-files.tag lintian-2.89.0ubuntu1/tags/p/patch-modifying-debian-files.tag --- lintian-2.93.0/tags/p/patch-modifying-debian-files.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/patch-modifying-debian-files.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,10 +0,0 @@ -Tag: patch-modifying-debian-files -Severity: error -Check: debian/patches/quilt -Explanation: A patch stored in debian/patches/ modifies or creates files - in the debian folder, but that folder is already under the - maintainer's exclusive control. - . - It may be more appropriate to patch or create files in the upstream - directory hierarchy, but often it is easier to place a copy in the - debian folder. diff -Nru lintian-2.93.0/tags/p/patch-not-forwarded-upstream.desc lintian-2.89.0ubuntu1/tags/p/patch-not-forwarded-upstream.desc --- lintian-2.93.0/tags/p/patch-not-forwarded-upstream.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/patch-not-forwarded-upstream.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,15 @@ +Tag: patch-not-forwarded-upstream +Severity: info +Check: debian/patches/dep3 +Renamed-From: send-patch +Info: According to the DEP-3 headers, this patch has not been forwarded + upstream. Please forward the patch upstream and work with them to ensure + the patch is included in the version control system and in the next + upstream release of your package. + . + If this patch should not be forwarded upstream please put not-needed in + the Forwarded header. +Ref: social contract item 2, + devref 3.1.4, + policy 4.3, + Bug#755153 diff -Nru lintian-2.93.0/tags/p/patch-not-forwarded-upstream.tag lintian-2.89.0ubuntu1/tags/p/patch-not-forwarded-upstream.tag --- lintian-2.93.0/tags/p/patch-not-forwarded-upstream.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/patch-not-forwarded-upstream.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,15 +0,0 @@ -Tag: patch-not-forwarded-upstream -Severity: info -Check: debian/patches/dep3 -Renamed-From: send-patch -Explanation: According to the DEP-3 headers, this patch has not been forwarded - upstream. Please forward the patch upstream and work with them to ensure - the patch is included in the version control system and in the next - upstream release of your package. - . - If this patch should not be forwarded upstream please put not-needed in - the Forwarded header. -See-Also: social contract item 2, - devref 3.1.4, - policy 4.3, - Bug#755153 diff -Nru lintian-2.93.0/tags/p/patch-system-but-direct-changes-in-diff.desc lintian-2.89.0ubuntu1/tags/p/patch-system-but-direct-changes-in-diff.desc --- lintian-2.93.0/tags/p/patch-system-but-direct-changes-in-diff.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/patch-system-but-direct-changes-in-diff.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: patch-system-but-direct-changes-in-diff +Severity: warning +Check: debian/patches +Info: The package uses a patch system, but the Debian diff.gz contains + changes to files or creation of additional files outside of the + debian directory. This often indicates accidental changes that + weren't meant to be in the package or changes that were supposed to be + separated out into a patch. The package will also more easily support + possible future source package formats if all changes outside the + debian directory are stored as patches. diff -Nru lintian-2.93.0/tags/p/patch-system-but-direct-changes-in-diff.tag lintian-2.89.0ubuntu1/tags/p/patch-system-but-direct-changes-in-diff.tag --- lintian-2.93.0/tags/p/patch-system-but-direct-changes-in-diff.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/patch-system-but-direct-changes-in-diff.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,10 +0,0 @@ -Tag: patch-system-but-direct-changes-in-diff -Severity: warning -Check: debian/patches -Explanation: The package uses a patch system, but the Debian diff.gz contains - changes to files or creation of additional files outside of the - debian directory. This often indicates accidental changes that - weren't meant to be in the package or changes that were supposed to be - separated out into a patch. The package will also more easily support - possible future source package formats if all changes outside the - debian directory are stored as patches. diff -Nru lintian-2.93.0/tags/p/patch-system-but-no-source-readme.desc lintian-2.89.0ubuntu1/tags/p/patch-system-but-no-source-readme.desc --- lintian-2.93.0/tags/p/patch-system-but-no-source-readme.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/patch-system-but-no-source-readme.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,13 @@ +Tag: patch-system-but-no-source-readme +Severity: warning +Check: debian/patches +Info: This package build-depends on a patch system such as dpatch or + quilt, but there is no debian/README.source file. This file is + recommended for any package where dpkg-source -x does not result + in the preferred form for making modifications to the package. + . + If you are using quilt and the package needs no other special handling + instructions, you may want to add a debian/README.source + referring to /usr/share/doc/quilt/README.source. Similarly, you + can refer to /usr/share/doc/dpatch/README.source.gz for dpatch. +Ref: policy 4.14 diff -Nru lintian-2.93.0/tags/p/patch-system-but-no-source-readme.tag lintian-2.89.0ubuntu1/tags/p/patch-system-but-no-source-readme.tag --- lintian-2.93.0/tags/p/patch-system-but-no-source-readme.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/patch-system-but-no-source-readme.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,13 +0,0 @@ -Tag: patch-system-but-no-source-readme -Severity: warning -Check: debian/patches -Explanation: This package build-depends on a patch system such as dpatch or - quilt, but there is no debian/README.source file. This file is - recommended for any package where dpkg-source -x does not result - in the preferred form for making modifications to the package. - . - If you are using quilt and the package needs no other special handling - instructions, you may want to add a debian/README.source - referring to /usr/share/doc/quilt/README.source. Similarly, you - can refer to /usr/share/doc/dpatch/README.source.gz for dpatch. -See-Also: policy 4.14 diff -Nru lintian-2.93.0/tags/p/patch-system.desc lintian-2.89.0ubuntu1/tags/p/patch-system.desc --- lintian-2.93.0/tags/p/patch-system.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/patch-system.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,5 @@ +Tag: patch-system +Severity: classification +Check: debian/patches +Info: This package uses the specified patch system (eg. "quilt" or + "dpatch"). diff -Nru lintian-2.93.0/tags/p/patch-system.tag lintian-2.89.0ubuntu1/tags/p/patch-system.tag --- lintian-2.93.0/tags/p/patch-system.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/patch-system.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,5 +0,0 @@ -Tag: patch-system -Severity: classification -Check: debian/patches -Explanation: This package uses the specified patch system (eg. "quilt" or - "dpatch"). diff -Nru lintian-2.93.0/tags/p/pear-channel-without-pkg-php-tools-builddep.desc lintian-2.89.0ubuntu1/tags/p/pear-channel-without-pkg-php-tools-builddep.desc --- lintian-2.93.0/tags/p/pear-channel-without-pkg-php-tools-builddep.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/pear-channel-without-pkg-php-tools-builddep.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: pear-channel-without-pkg-php-tools-builddep +Severity: warning +Certainty: possible +Check: languages/php/pear +Info: The package contains a channel.xml file but doesn't build-depend on + pkg-php-tools. + . + pkg-php-tools is the recommended tool for building PEAR and PECL packages. For + more information, install it and read the included README.PEAR. diff -Nru lintian-2.93.0/tags/p/pear-channel-without-pkg-php-tools-builddep.tag lintian-2.89.0ubuntu1/tags/p/pear-channel-without-pkg-php-tools-builddep.tag --- lintian-2.93.0/tags/p/pear-channel-without-pkg-php-tools-builddep.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/pear-channel-without-pkg-php-tools-builddep.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: pear-channel-without-pkg-php-tools-builddep -Severity: warning -Check: languages/php/pear -Explanation: The package contains a channel.xml file but doesn't build-depend on - pkg-php-tools. - . - pkg-php-tools is the recommended tool for building PEAR and PECL packages. For - more information, install it and read the included README.PEAR. diff -Nru lintian-2.93.0/tags/p/pear-package-but-missing-dependency.desc lintian-2.89.0ubuntu1/tags/p/pear-package-but-missing-dependency.desc --- lintian-2.93.0/tags/p/pear-package-but-missing-dependency.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/pear-package-but-missing-dependency.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: pear-package-but-missing-dependency +Severity: warning +Certainty: possible +Check: languages/php/pear +Info: The package is a PEAR package but its control file doesn't have + ${phppear:Debian-Depends} in Depends or ${phppear:Debian-Recommends}. diff -Nru lintian-2.93.0/tags/p/pear-package-but-missing-dependency.tag lintian-2.89.0ubuntu1/tags/p/pear-package-but-missing-dependency.tag --- lintian-2.93.0/tags/p/pear-package-but-missing-dependency.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/pear-package-but-missing-dependency.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,5 +0,0 @@ -Tag: pear-package-but-missing-dependency -Severity: warning -Check: languages/php/pear -Explanation: The package is a PEAR package but its control file doesn't have - ${phppear:Debian-Depends} in Depends or ${phppear:Debian-Recommends}. diff -Nru lintian-2.93.0/tags/p/pear-package-not-using-substvar.desc lintian-2.89.0ubuntu1/tags/p/pear-package-not-using-substvar.desc --- lintian-2.93.0/tags/p/pear-package-not-using-substvar.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/pear-package-not-using-substvar.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: pear-package-not-using-substvar +Severity: info +Certainty: possible +Check: languages/php/pear +Info: The package is a PEAR package but the control file does not use + ${phppear:summary} or ${phppear:description} in its description fields. + . + The substitution variables should be used when the description in the + PEAR package is suitable and respects best packaging practices. +Ref: https://www.debian.org/doc/manuals/developers-reference/best-pkging-practices.html#bpp-desc-basics diff -Nru lintian-2.93.0/tags/p/pear-package-not-using-substvar.tag lintian-2.89.0ubuntu1/tags/p/pear-package-not-using-substvar.tag --- lintian-2.93.0/tags/p/pear-package-not-using-substvar.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/pear-package-not-using-substvar.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: pear-package-not-using-substvar -Severity: info -Check: languages/php/pear -Explanation: The package is a PEAR package but the control file does not use - ${phppear:summary} or ${phppear:description} in its description fields. - . - The substitution variables should be used when the description in the - PEAR package is suitable and respects best packaging practices. -See-Also: https://www.debian.org/doc/manuals/developers-reference/best-pkging-practices.html#bpp-desc-basics diff -Nru lintian-2.93.0/tags/p/pear-package-without-pkg-php-tools-builddep.desc lintian-2.89.0ubuntu1/tags/p/pear-package-without-pkg-php-tools-builddep.desc --- lintian-2.93.0/tags/p/pear-package-without-pkg-php-tools-builddep.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/pear-package-without-pkg-php-tools-builddep.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: pear-package-without-pkg-php-tools-builddep +Severity: warning +Certainty: possible +Check: languages/php/pear +Info: The package contains a package.xml or package2.xml file but doesn't + build-depend on pkg-php-tools. + . + pkg-php-tools is the recommended tool for building PEAR and PECL packages. For + more information, install it and read the included README.PEAR. diff -Nru lintian-2.93.0/tags/p/pear-package-without-pkg-php-tools-builddep.tag lintian-2.89.0ubuntu1/tags/p/pear-package-without-pkg-php-tools-builddep.tag --- lintian-2.93.0/tags/p/pear-package-without-pkg-php-tools-builddep.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/pear-package-without-pkg-php-tools-builddep.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: pear-package-without-pkg-php-tools-builddep -Severity: warning -Check: languages/php/pear -Explanation: The package contains a package.xml or package2.xml file but doesn't - build-depend on pkg-php-tools. - . - pkg-php-tools is the recommended tool for building PEAR and PECL packages. For - more information, install it and read the included README.PEAR. diff -Nru lintian-2.93.0/tags/p/pecl-package-requires-build-dependency.desc lintian-2.89.0ubuntu1/tags/p/pecl-package-requires-build-dependency.desc --- lintian-2.93.0/tags/p/pecl-package-requires-build-dependency.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/pecl-package-requires-build-dependency.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: pecl-package-requires-build-dependency +Severity: warning +Certainty: possible +Check: languages/php/pear +Info: The package is a PECL package but its control file doesn't have + php-dev or dh-php as a build dependency. diff -Nru lintian-2.93.0/tags/p/pecl-package-requires-build-dependency.tag lintian-2.89.0ubuntu1/tags/p/pecl-package-requires-build-dependency.tag --- lintian-2.93.0/tags/p/pecl-package-requires-build-dependency.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/pecl-package-requires-build-dependency.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,5 +0,0 @@ -Tag: pecl-package-requires-build-dependency -Severity: warning -Check: languages/php/pear -Explanation: The package is a PECL package but its control file doesn't have - php-dev or dh-php as a build dependency. diff -Nru lintian-2.93.0/tags/p/perl-module-in-core-directory.desc lintian-2.89.0ubuntu1/tags/p/perl-module-in-core-directory.desc --- lintian-2.93.0/tags/p/perl-module-in-core-directory.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/perl-module-in-core-directory.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: perl-module-in-core-directory +Severity: error +Check: languages/perl +Info: Packaged modules must not be installed into the core perl + directories as those directories change with each upstream perl + revision. The vendor directories are provided for this purpose. +Ref: perl-policy 3.1 diff -Nru lintian-2.93.0/tags/p/perl-module-in-core-directory.tag lintian-2.89.0ubuntu1/tags/p/perl-module-in-core-directory.tag --- lintian-2.93.0/tags/p/perl-module-in-core-directory.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/perl-module-in-core-directory.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: perl-module-in-core-directory -Severity: error -Check: languages/perl -Explanation: Packaged modules must not be installed into the core perl - directories as those directories change with each upstream perl - revision. The vendor directories are provided for this purpose. -See-Also: perl-policy 3.1 diff -Nru lintian-2.93.0/tags/p/perl-module-name-not-mentioned-in-description.desc lintian-2.89.0ubuntu1/tags/p/perl-module-name-not-mentioned-in-description.desc --- lintian-2.93.0/tags/p/perl-module-name-not-mentioned-in-description.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/perl-module-name-not-mentioned-in-description.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +# Imported from pkg-perl-tools (named no-module-name-in-description there) +Tag: perl-module-name-not-mentioned-in-description +Severity: warning +Check: fields/description +Experimental: yes +Info: Debian users are likely to look for perl modules by their name, e.g. + Foo::Bar, not by package name (libfoo-bar-perl). To make this easier, the main + module name should be present in the long package description. diff -Nru lintian-2.93.0/tags/p/perl-module-name-not-mentioned-in-description.tag lintian-2.89.0ubuntu1/tags/p/perl-module-name-not-mentioned-in-description.tag --- lintian-2.93.0/tags/p/perl-module-name-not-mentioned-in-description.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/perl-module-name-not-mentioned-in-description.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -# Imported from pkg-perl-tools (named no-module-name-in-description there) -Tag: perl-module-name-not-mentioned-in-description -Severity: warning -Check: fields/description -Experimental: yes -Explanation: Debian users are likely to look for perl modules by their name, e.g. - Foo::Bar, not by package name (libfoo-bar-perl). To make this easier, the main - module name should be present in the long package description. diff -Nru lintian-2.93.0/tags/p/perl-module-uses-perl4-libs-without-dep.desc lintian-2.89.0ubuntu1/tags/p/perl-module-uses-perl4-libs-without-dep.desc --- lintian-2.93.0/tags/p/perl-module-uses-perl4-libs-without-dep.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/perl-module-uses-perl4-libs-without-dep.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: perl-module-uses-perl4-libs-without-dep +Severity: warning +Certainty: possible +Check: languages/perl +Info: This package includes perl modules using obsoleted perl 4-era + libraries. These libraries have been deprecated in perl in 5.14, and + are likely to be removed from the core in perl 5.16. Please either + remove references to these libraries, or add a dependency on + libperl4-corelibs-perl | perl (<< 5.12.3-7) to this package. diff -Nru lintian-2.93.0/tags/p/perl-module-uses-perl4-libs-without-dep.tag lintian-2.89.0ubuntu1/tags/p/perl-module-uses-perl4-libs-without-dep.tag --- lintian-2.93.0/tags/p/perl-module-uses-perl4-libs-without-dep.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/perl-module-uses-perl4-libs-without-dep.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: perl-module-uses-perl4-libs-without-dep -Severity: warning -Check: languages/perl -Explanation: This package includes perl modules using obsoleted perl 4-era - libraries. These libraries have been deprecated in perl in 5.14, and - are likely to be removed from the core in perl 5.16. Please either - remove references to these libraries, or add a dependency on - libperl4-corelibs-perl | perl (<< 5.12.3-7) to this package. diff -Nru lintian-2.93.0/tags/p/php-script-but-no-php-cli-dep.desc lintian-2.89.0ubuntu1/tags/p/php-script-but-no-php-cli-dep.desc --- lintian-2.93.0/tags/p/php-script-but-no-php-cli-dep.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/php-script-but-no-php-cli-dep.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: php-script-but-no-php-cli-dep +Severity: error +Check: scripts +Info: Packages with PHP scripts must depend on the php-cli package. + Note that a dependency on a php-cgi package (such as php-cgi or php7.0-cgi) + is needlessly strict and forces the user to install a package that isn't + needed. + . + In some cases a weaker relationship, such as Suggests or Recommends, will + be more appropriate. diff -Nru lintian-2.93.0/tags/p/php-script-but-no-php-cli-dep.tag lintian-2.89.0ubuntu1/tags/p/php-script-but-no-php-cli-dep.tag --- lintian-2.93.0/tags/p/php-script-but-no-php-cli-dep.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/php-script-but-no-php-cli-dep.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,10 +0,0 @@ -Tag: php-script-but-no-php-cli-dep -Severity: error -Check: scripts -Explanation: Packages with PHP scripts must depend on the php-cli package. - Note that a dependency on a php-cgi package (such as php-cgi or php7.0-cgi) - is needlessly strict and forces the user to install a package that isn't - needed. - . - In some cases a weaker relationship, such as Suggests or Recommends, will - be more appropriate. diff -Nru lintian-2.93.0/tags/p/php-script-with-unusual-interpreter.desc lintian-2.89.0ubuntu1/tags/p/php-script-with-unusual-interpreter.desc --- lintian-2.93.0/tags/p/php-script-with-unusual-interpreter.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/php-script-with-unusual-interpreter.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: php-script-with-unusual-interpreter +Severity: warning +Certainty: possible +Check: scripts +Info: This package contains a php script using an unusual interpreter in the + shebang line. The recommended shebang line is either #!/usr/bin/php + or #!/usr/bin/env php without any version number. diff -Nru lintian-2.93.0/tags/p/php-script-with-unusual-interpreter.tag lintian-2.89.0ubuntu1/tags/p/php-script-with-unusual-interpreter.tag --- lintian-2.93.0/tags/p/php-script-with-unusual-interpreter.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/php-script-with-unusual-interpreter.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: php-script-with-unusual-interpreter -Severity: warning -Check: scripts -Explanation: This package contains a php script using an unusual interpreter in the - shebang line. The recommended shebang line is either #!/usr/bin/php - or #!/usr/bin/env php without any version number. diff -Nru lintian-2.93.0/tags/p/pipe-symbol-used-as-license-disjunction.desc lintian-2.89.0ubuntu1/tags/p/pipe-symbol-used-as-license-disjunction.desc --- lintian-2.93.0/tags/p/pipe-symbol-used-as-license-disjunction.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/pipe-symbol-used-as-license-disjunction.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: pipe-symbol-used-as-license-disjunction +Severity: warning +Certainty: possible +Check: debian/copyright/dep5 +Info: A vertical bar &vert (also known as a pipe symbol) does not stand for + a logical OR relationship in debian/copyright. + . + To describe dual licensing, please use the word "or" between license + names. +Ref: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ diff -Nru lintian-2.93.0/tags/p/pipe-symbol-used-as-license-disjunction.tag lintian-2.89.0ubuntu1/tags/p/pipe-symbol-used-as-license-disjunction.tag --- lintian-2.93.0/tags/p/pipe-symbol-used-as-license-disjunction.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/pipe-symbol-used-as-license-disjunction.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: pipe-symbol-used-as-license-disjunction -Severity: warning -Check: debian/copyright/dep5 -Explanation: A vertical bar &vert (also known as a pipe symbol) does not stand for - a logical OR relationship in debian/copyright. - . - To describe dual licensing, please use the word "or" between license - names. -See-Also: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ diff -Nru lintian-2.93.0/tags/p/pkg-config-bad-directive.desc lintian-2.89.0ubuntu1/tags/p/pkg-config-bad-directive.desc --- lintian-2.93.0/tags/p/pkg-config-bad-directive.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/pkg-config-bad-directive.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: pkg-config-bad-directive +Severity: error +Certainty: possible +Check: files/pkgconfig +Info: The pkg-config file contains a wrong directive. + . + The following file includes a wrong directive. This could lead to + FTBFS or leak private compile flags to another package. diff -Nru lintian-2.93.0/tags/p/pkg-config-bad-directive.tag lintian-2.89.0ubuntu1/tags/p/pkg-config-bad-directive.tag --- lintian-2.93.0/tags/p/pkg-config-bad-directive.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/pkg-config-bad-directive.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: pkg-config-bad-directive -Severity: error -Check: files/pkgconfig -Explanation: The pkg-config file contains a wrong directive. - . - The following file includes a wrong directive. This could lead to - FTBFS or leak private compile flags to another package. diff -Nru lintian-2.93.0/tags/p/pkg-config-multi-arch-wrong-dir.desc lintian-2.89.0ubuntu1/tags/p/pkg-config-multi-arch-wrong-dir.desc --- lintian-2.93.0/tags/p/pkg-config-multi-arch-wrong-dir.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/pkg-config-multi-arch-wrong-dir.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,16 @@ +Tag: pkg-config-multi-arch-wrong-dir +Severity: error +Certainty: possible +Check: files/pkgconfig +Info: The arch all pkg-config file contains a reference to a multi-arch path. + . + This can be usually be fixed by moving this file to a multi-arch path. + . + Another likely cause is using debhelper 9 or newer (thus enabling + multi-arch paths by default) on a package without multi-arch support. + The usual cure in this case is to update it for multi-arch. + . + Last but not least, this file could contain a reference to a cross + architecture (like for instance an x86_64-linux-gnu pkg-config file + referencing an i386-linux-gnu file). In this case the usual cure is to + fix this path. diff -Nru lintian-2.93.0/tags/p/pkg-config-multi-arch-wrong-dir.tag lintian-2.89.0ubuntu1/tags/p/pkg-config-multi-arch-wrong-dir.tag --- lintian-2.93.0/tags/p/pkg-config-multi-arch-wrong-dir.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/pkg-config-multi-arch-wrong-dir.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,15 +0,0 @@ -Tag: pkg-config-multi-arch-wrong-dir -Severity: error -Check: files/pkgconfig -Explanation: The arch all pkg-config file contains a reference to a multi-arch path. - . - This can be usually be fixed by moving this file to a multi-arch path. - . - Another likely cause is using debhelper 9 or newer (thus enabling - multi-arch paths by default) on a package without multi-arch support. - The usual cure in this case is to update it for multi-arch. - . - Last but not least, this file could contain a reference to a cross - architecture (like for instance an x86_64-linux-gnu pkg-config file - referencing an i386-linux-gnu file). In this case the usual cure is to - fix this path. diff -Nru lintian-2.93.0/tags/p/pkg-config-unavailable-for-cross-compilation.desc lintian-2.89.0ubuntu1/tags/p/pkg-config-unavailable-for-cross-compilation.desc --- lintian-2.93.0/tags/p/pkg-config-unavailable-for-cross-compilation.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/pkg-config-unavailable-for-cross-compilation.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,14 @@ +Tag: pkg-config-unavailable-for-cross-compilation +Severity: warning +Check: files/pkgconfig +Info: The specified pkg-config(1) file is installed to + /usr/lib/pkgconfig. As the cross-compilation wrapper of pkg-config + does not search this directory the file is unavailable under + cross-compilation. + . + Please install the file to /usr/lib/${DEB_HOST_MULTIARCH}/pkgconfig + instead. + . + For projects that use GNU Autotools, a simple method is moving to a debhelper + compat level of 9 or higher. In the rare case that this file is architecture + independent it can be installed to /usr/share/pkgconfig instead. diff -Nru lintian-2.93.0/tags/p/pkg-config-unavailable-for-cross-compilation.tag lintian-2.89.0ubuntu1/tags/p/pkg-config-unavailable-for-cross-compilation.tag --- lintian-2.93.0/tags/p/pkg-config-unavailable-for-cross-compilation.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/pkg-config-unavailable-for-cross-compilation.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,14 +0,0 @@ -Tag: pkg-config-unavailable-for-cross-compilation -Severity: warning -Check: files/pkgconfig -Explanation: The specified pkg-config(1) file is installed to - /usr/lib/pkgconfig. As the cross-compilation wrapper of pkg-config - does not search this directory the file is unavailable under - cross-compilation. - . - Please install the file to /usr/lib/${DEB_HOST_MULTIARCH}/pkgconfig - instead. - . - For projects that use GNU Autotools, a simple method is moving to a debhelper - compat level of 9 or higher. In the rare case that this file is architecture - independent it can be installed to /usr/share/pkgconfig instead. diff -Nru lintian-2.93.0/tags/p/pkg-js-autopkgtest-file-does-not-exist.desc lintian-2.89.0ubuntu1/tags/p/pkg-js-autopkgtest-file-does-not-exist.desc --- lintian-2.93.0/tags/p/pkg-js-autopkgtest-file-does-not-exist.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/pkg-js-autopkgtest-file-does-not-exist.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: pkg-js-autopkgtest-file-does-not-exist +Severity: error +Check: languages/javascript/nodejs +Info: One of the files referenced the specified file does not exist in sources + and thus pkg-js-autopkgtest will likely fail. + . + Please update the debian/tests/pkg-fs/files file + (see /usr/share/doc/pkg-js-autopkgtest/README.md). diff -Nru lintian-2.93.0/tags/p/pkg-js-autopkgtest-file-does-not-exist.tag lintian-2.89.0ubuntu1/tags/p/pkg-js-autopkgtest-file-does-not-exist.tag --- lintian-2.93.0/tags/p/pkg-js-autopkgtest-file-does-not-exist.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/pkg-js-autopkgtest-file-does-not-exist.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: pkg-js-autopkgtest-file-does-not-exist -Severity: error -Check: languages/javascript/nodejs -Explanation: One of the files referenced the specified file does not exist in sources - and thus pkg-js-autopkgtest will likely fail. - . - Please update the debian/tests/pkg-fs/files file - (see /usr/share/doc/pkg-js-autopkgtest/README.md). diff -Nru lintian-2.93.0/tags/p/pkg-js-autopkgtest-test-is-empty.desc lintian-2.89.0ubuntu1/tags/p/pkg-js-autopkgtest-test-is-empty.desc --- lintian-2.93.0/tags/p/pkg-js-autopkgtest-test-is-empty.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/pkg-js-autopkgtest-test-is-empty.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: pkg-js-autopkgtest-test-is-empty +Severity: error +Check: languages/javascript/nodejs +Info: The specified file is empty. This will produce erroneous autopkgtest + success reports. + . + Please set a significant test in this file + (see /usr/share/doc/pkg-js-autopkgtest/README.md). diff -Nru lintian-2.93.0/tags/p/pkg-js-autopkgtest-test-is-empty.tag lintian-2.89.0ubuntu1/tags/p/pkg-js-autopkgtest-test-is-empty.tag --- lintian-2.93.0/tags/p/pkg-js-autopkgtest-test-is-empty.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/pkg-js-autopkgtest-test-is-empty.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: pkg-js-autopkgtest-test-is-empty -Severity: error -Check: languages/javascript/nodejs -Explanation: The specified file is empty. This will produce erroneous autopkgtest - success reports. - . - Please set a significant test in this file - (see /usr/share/doc/pkg-js-autopkgtest/README.md). diff -Nru lintian-2.93.0/tags/p/pkg-js-autopkgtest-test-is-missing.desc lintian-2.89.0ubuntu1/tags/p/pkg-js-autopkgtest-test-is-missing.desc --- lintian-2.93.0/tags/p/pkg-js-autopkgtest-test-is-missing.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/pkg-js-autopkgtest-test-is-missing.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,11 @@ +Tag: pkg-js-autopkgtest-test-is-missing +Severity: warning +Check: languages/javascript/nodejs +Info: The Testsuite: field for this package points to + autopkgtest-pkg-nodejs which attempts to execute + the specified file during autopkgtests. + . + When this file is missing, only a simple node require("<module + name>") is launched. This may be insufficient to really test this + nodejs module + (see /usr/share/doc/pkg-js-autopkgtest/README.md). diff -Nru lintian-2.93.0/tags/p/pkg-js-autopkgtest-test-is-missing.tag lintian-2.89.0ubuntu1/tags/p/pkg-js-autopkgtest-test-is-missing.tag --- lintian-2.93.0/tags/p/pkg-js-autopkgtest-test-is-missing.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/pkg-js-autopkgtest-test-is-missing.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,11 +0,0 @@ -Tag: pkg-js-autopkgtest-test-is-missing -Severity: warning -Check: languages/javascript/nodejs -Explanation: The Testsuite: field for this package points to - autopkgtest-pkg-nodejs which attempts to execute - the specified file during autopkgtests. - . - When this file is missing, only a simple node require("<module - name>") is launched. This may be insufficient to really test this - nodejs module - (see /usr/share/doc/pkg-js-autopkgtest/README.md). diff -Nru lintian-2.93.0/tags/p/pkg-js-tools-test-is-empty.desc lintian-2.89.0ubuntu1/tags/p/pkg-js-tools-test-is-empty.desc --- lintian-2.93.0/tags/p/pkg-js-tools-test-is-empty.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/pkg-js-tools-test-is-empty.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: pkg-js-tools-test-is-empty +Severity: warning +Check: languages/javascript/nodejs +Info: The specified file is empty. This means that no test is played during + build. + . + Please set a significant test in this file + (see /usr/share/doc/pkg-js-tools/README.md.gz). diff -Nru lintian-2.93.0/tags/p/pkg-js-tools-test-is-empty.tag lintian-2.89.0ubuntu1/tags/p/pkg-js-tools-test-is-empty.tag --- lintian-2.93.0/tags/p/pkg-js-tools-test-is-empty.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/pkg-js-tools-test-is-empty.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: pkg-js-tools-test-is-empty -Severity: warning -Check: languages/javascript/nodejs -Explanation: The specified file is empty. This means that no test is played during - build. - . - Please set a significant test in this file - (see /usr/share/doc/pkg-js-tools/README.md.gz). diff -Nru lintian-2.93.0/tags/p/pkg-js-tools-test-is-missing.desc lintian-2.89.0ubuntu1/tags/p/pkg-js-tools-test-is-missing.desc --- lintian-2.93.0/tags/p/pkg-js-tools-test-is-missing.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/pkg-js-tools-test-is-missing.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,13 @@ +Tag: pkg-js-tools-test-is-missing +Severity: warning +Check: languages/javascript/nodejs +Info: The debian/rules file for this package uses --with + nodejs which attempts to execute the specified file when running + autopkgtests. + . + When this file is missing, only a simple node require(".") is + launched which may be insufficient to really test this nodejs module. + . + Please specify the upstream testsuite (or a custom one) in + debian/tests/pkg-js/test + (see /usr/share/doc/pkg-js-tools/README.md.gz). diff -Nru lintian-2.93.0/tags/p/pkg-js-tools-test-is-missing.tag lintian-2.89.0ubuntu1/tags/p/pkg-js-tools-test-is-missing.tag --- lintian-2.93.0/tags/p/pkg-js-tools-test-is-missing.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/pkg-js-tools-test-is-missing.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,13 +0,0 @@ -Tag: pkg-js-tools-test-is-missing -Severity: warning -Check: languages/javascript/nodejs -Explanation: The debian/rules file for this package uses --with - nodejs which attempts to execute the specified file when running - autopkgtests. - . - When this file is missing, only a simple node require(".") is - launched which may be insufficient to really test this nodejs module. - . - Please specify the upstream testsuite (or a custom one) in - debian/tests/pkg-js/test - (see /usr/share/doc/pkg-js-tools/README.md.gz). diff -Nru lintian-2.93.0/tags/p/pkg-not-in-package-test.desc lintian-2.89.0ubuntu1/tags/p/pkg-not-in-package-test.desc --- lintian-2.93.0/tags/p/pkg-not-in-package-test.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/pkg-not-in-package-test.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,15 @@ +Tag: pkg-not-in-package-test +Severity: warning +Certainty: possible +Check: menu-format +Info: This menu item doesn't test to see if the package containing it is + installed. The start of any menu item is a conditional testing whether + the required packages are installed. Normally this conditional should + always check at least the package containing it, since menu items should + be included in the package that provides the application the menu refers + to. + . + This error usually indicates a misspelling of the package name in the + menu entry or a copied menu entry from another package that doesn't apply + to this one. +Ref: menu 3.2 diff -Nru lintian-2.93.0/tags/p/pkg-not-in-package-test.tag lintian-2.89.0ubuntu1/tags/p/pkg-not-in-package-test.tag --- lintian-2.93.0/tags/p/pkg-not-in-package-test.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/pkg-not-in-package-test.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,14 +0,0 @@ -Tag: pkg-not-in-package-test -Severity: warning -Check: menu-format -Explanation: This menu item doesn't test to see if the package containing it is - installed. The start of any menu item is a conditional testing whether - the required packages are installed. Normally this conditional should - always check at least the package containing it, since menu items should - be included in the package that provides the application the menu refers - to. - . - This error usually indicates a misspelling of the package name in the - menu entry or a copied menu entry from another package that doesn't apply - to this one. -See-Also: menu 3.2 diff -Nru lintian-2.93.0/tags/p/pod-conversion-message.desc lintian-2.89.0ubuntu1/tags/p/pod-conversion-message.desc --- lintian-2.93.0/tags/p/pod-conversion-message.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/pod-conversion-message.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: pod-conversion-message +Severity: warning +Check: documentation/manual +Renamed-From: manpage-has-errors-from-pod2man +Info: A manual page contains a section POD ERRORS. This tag show + the contents. + . + The section was generated by pod2man. It shows any errors that + were found in the POD documentation when the page was generated. diff -Nru lintian-2.93.0/tags/p/pod-conversion-message.tag lintian-2.89.0ubuntu1/tags/p/pod-conversion-message.tag --- lintian-2.93.0/tags/p/pod-conversion-message.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/pod-conversion-message.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: pod-conversion-message -Severity: warning -Check: documentation/manual -Renamed-From: manpage-has-errors-from-pod2man -Explanation: A manual page contains a section POD ERRORS. This tag show - the contents. - . - The section was generated by pod2man. It shows any errors that - were found in the POD documentation when the page was generated. diff -Nru lintian-2.93.0/tags/p/poor-compression-in-manual-page.desc lintian-2.89.0ubuntu1/tags/p/poor-compression-in-manual-page.desc --- lintian-2.93.0/tags/p/poor-compression-in-manual-page.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/poor-compression-in-manual-page.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: poor-compression-in-manual-page +Severity: error +Check: documentation/manual +Renamed-From: manpage-not-compressed-with-max-compression +Info: Manual pages should be compressed with gzip -9n. It + selects the highest compression available. +Ref: policy 12.1 diff -Nru lintian-2.93.0/tags/p/poor-compression-in-manual-page.tag lintian-2.89.0ubuntu1/tags/p/poor-compression-in-manual-page.tag --- lintian-2.93.0/tags/p/poor-compression-in-manual-page.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/poor-compression-in-manual-page.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: poor-compression-in-manual-page -Severity: error -Check: documentation/manual -Renamed-From: manpage-not-compressed-with-max-compression -Explanation: Manual pages should be compressed with gzip -9n. It - selects the highest compression available. -See-Also: policy 12.1 diff -Nru lintian-2.93.0/tags/p/portable-executable-missing-security-features.desc lintian-2.89.0ubuntu1/tags/p/portable-executable-missing-security-features.desc --- lintian-2.93.0/tags/p/portable-executable-missing-security-features.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/portable-executable-missing-security-features.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,40 @@ +Tag: portable-executable-missing-security-features +Severity: pedantic +Check: pe +Experimental: yes +Info: A portable executable (PE32+) file lacks security features. + . + Due to changes in binutils-mingw-w64 the historical + advice is incorrect. Current tools do not create safe binaries, + and advertising such settings with genpeimg is pointless. + . + In short, the flags alone do nothing unless a binary is built + specifically to support a missing flag. Merely setting the flag, + as recommended below, can actually make a file less secure. + . + More information can be found via the link in the references. + . + The following advice is historical. PLEASE DO NOT FOLLOW IT. + . + The package ships a Microsoft Windows Portable Executable (PE) file + that appears to be lacking security hardening features. You can see + which are missing using the pesec tool from the + pev package. + . + EFI binaries also often trigger this tag. The security flags are + probably meaningless for them, but the flags are easily changed + using the genpeimg tool from the mingw-w64-tools + package. + . + $ genpeimg -d +d -d +n -d +s $file + . + Then, to verify that it worked: + . + $ genpeimg -x $file + ... + Optional Characteristics: + dynamic-base nx-compatible no-SEH + . + Please change the flags, if possible, instead of overriding the tag. + . +Ref: https://www.kb.cert.org/vuls/id/307144/, Bug#953212 diff -Nru lintian-2.93.0/tags/p/portable-executable-missing-security-features.tag lintian-2.89.0ubuntu1/tags/p/portable-executable-missing-security-features.tag --- lintian-2.93.0/tags/p/portable-executable-missing-security-features.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/portable-executable-missing-security-features.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,40 +0,0 @@ -Tag: portable-executable-missing-security-features -Severity: pedantic -Check: pe -Experimental: yes -Explanation: A portable executable (PE32+) file lacks security features. - . - Due to changes in binutils-mingw-w64 the historical - advice is incorrect. Current tools do not create safe binaries, - and advertising such settings with genpeimg is pointless. - . - In short, the flags alone do nothing unless a binary is built - specifically to support a missing flag. Merely setting the flag, - as recommended below, can actually make a file less secure. - . - More information can be found via the link in the references. - . - The following advice is historical. PLEASE DO NOT FOLLOW IT. - . - The package ships a Microsoft Windows Portable Executable (PE) file - that appears to be lacking security hardening features. You can see - which are missing using the pesec tool from the - pev package. - . - EFI binaries also often trigger this tag. The security flags are - probably meaningless for them, but the flags are easily changed - using the genpeimg tool from the mingw-w64-tools - package. - . - $ genpeimg -d +d -d +n -d +s $file - . - Then, to verify that it worked: - . - $ genpeimg -x $file - ... - Optional Characteristics: - dynamic-base nx-compatible no-SEH - . - Please change the flags, if possible, instead of overriding the tag. - . -See-Also: https://www.kb.cert.org/vuls/id/307144/, Bug#953212 diff -Nru lintian-2.93.0/tags/p/possible-bashism-in-maintainer-script.desc lintian-2.89.0ubuntu1/tags/p/possible-bashism-in-maintainer-script.desc --- lintian-2.93.0/tags/p/possible-bashism-in-maintainer-script.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/possible-bashism-in-maintainer-script.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,18 @@ +Tag: possible-bashism-in-maintainer-script +Severity: warning +Certainty: possible +Check: scripts +Ref: policy 10.4 +Info: This script is marked as running under /bin/sh, but it seems + to use a feature found in bash but not in the SUSv3 or POSIX shell + specification. + . + Examples: + '==' in a test, it should use '=' instead + 'read' without a variable in the argument + 'function' to define a function + 'source' instead of '.' + '. command args', passing arguments to commands via 'source' is not supported + '{foo,bar}' instead of 'foo bar' + '[[ test ]]' instead of '[ test ]' (requires a Korn shell) + 'type' instead of 'which' or 'command -v' diff -Nru lintian-2.93.0/tags/p/possible-bashism-in-maintainer-script.tag lintian-2.89.0ubuntu1/tags/p/possible-bashism-in-maintainer-script.tag --- lintian-2.93.0/tags/p/possible-bashism-in-maintainer-script.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/possible-bashism-in-maintainer-script.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,17 +0,0 @@ -Tag: possible-bashism-in-maintainer-script -Severity: warning -Check: scripts -See-Also: policy 10.4 -Explanation: This script is marked as running under /bin/sh, but it seems - to use a feature found in bash but not in the SUSv3 or POSIX shell - specification. - . - Examples: - '==' in a test, it should use '=' instead - 'read' without a variable in the argument - 'function' to define a function - 'source' instead of '.' - '. command args', passing arguments to commands via 'source' is not supported - '{foo,bar}' instead of 'foo bar' - '[[ test ]]' instead of '[ test ]' (requires a Korn shell) - 'type' instead of 'which' or 'command -v' diff -Nru lintian-2.93.0/tags/p/possible-debconf-note-abuse.desc lintian-2.89.0ubuntu1/tags/p/possible-debconf-note-abuse.desc --- lintian-2.93.0/tags/p/possible-debconf-note-abuse.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/possible-debconf-note-abuse.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,19 @@ +Tag: possible-debconf-note-abuse +Severity: warning +Certainty: possible +Check: debian/debconf +Info: Debconf notes should be used only for important notes that the + user really should see, since debconf will go to great pains to make + sure the user sees it. + . + Displaying a note with a low priority is conflicting with this statement, + since using a low or medium priority shows that the note is not + important. + . + The right fix is NOT to increase the priority of the note, but to move + it somewhere else in the inline documentation, for example in a + README.Debian file for notes about package usability or NEWS.Debian for + changes in the package behavior, or to simply drop it if it is not + needed (e.g. "welcome" notes). Changing the templates type to "error" + can also be appropriate, such as for input validation errors. +Ref: policy 3.9.1 diff -Nru lintian-2.93.0/tags/p/possible-debconf-note-abuse.tag lintian-2.89.0ubuntu1/tags/p/possible-debconf-note-abuse.tag --- lintian-2.93.0/tags/p/possible-debconf-note-abuse.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/possible-debconf-note-abuse.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,18 +0,0 @@ -Tag: possible-debconf-note-abuse -Severity: warning -Check: debian/debconf -Explanation: Debconf notes should be used only for important notes that the - user really should see, since debconf will go to great pains to make - sure the user sees it. - . - Displaying a note with a low priority is conflicting with this statement, - since using a low or medium priority shows that the note is not - important. - . - The right fix is NOT to increase the priority of the note, but to move - it somewhere else in the inline documentation, for example in a - README.Debian file for notes about package usability or NEWS.Debian for - changes in the package behavior, or to simply drop it if it is not - needed (e.g. "welcome" notes). Changing the templates type to "error" - can also be appropriate, such as for input validation errors. -See-Also: policy 3.9.1 diff -Nru lintian-2.93.0/tags/p/possible-documentation-but-no-doc-base-registration.desc lintian-2.89.0ubuntu1/tags/p/possible-documentation-but-no-doc-base-registration.desc --- lintian-2.93.0/tags/p/possible-documentation-but-no-doc-base-registration.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/possible-documentation-but-no-doc-base-registration.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: possible-documentation-but-no-doc-base-registration +Severity: info +Certainty: possible +Check: menus +Info: The package ships a .html or .pdf file under + /usr/share/doc/, which are usually documentation, but it does + not register anything in doc-base. (Files under an examples + directory are excluded.) +Ref: policy 9.10 diff -Nru lintian-2.93.0/tags/p/possible-documentation-but-no-doc-base-registration.tag lintian-2.89.0ubuntu1/tags/p/possible-documentation-but-no-doc-base-registration.tag --- lintian-2.93.0/tags/p/possible-documentation-but-no-doc-base-registration.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/possible-documentation-but-no-doc-base-registration.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: possible-documentation-but-no-doc-base-registration -Severity: info -Check: menus -Explanation: The package ships a .html or .pdf file under - /usr/share/doc/, which are usually documentation, but it does - not register anything in doc-base. (Files under an examples - directory are excluded.) -See-Also: policy 9.10 diff -Nru lintian-2.93.0/tags/p/possible-gpl-code-linked-with-openssl.desc lintian-2.89.0ubuntu1/tags/p/possible-gpl-code-linked-with-openssl.desc --- lintian-2.93.0/tags/p/possible-gpl-code-linked-with-openssl.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/possible-gpl-code-linked-with-openssl.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,15 @@ +Tag: possible-gpl-code-linked-with-openssl +Severity: error +Certainty: wild-guess +Check: debian/copyright +Info: This package appears to be covered by the GNU GPL but depends on + the OpenSSL libssl package and does not mention a license exemption or + exception for OpenSSL in its copyright file. The GPL (including version + 3) is incompatible with some terms of the OpenSSL license, and therefore + Debian does not allow GPL-licensed code linked with OpenSSL libraries + unless there is a license exception explicitly permitting this. + . + If only the Debian packaging, or some other part of the package not + linked with OpenSSL, is covered by the GNU GPL, please add a Lintian + override for this tag. Lintian currently has no good way of + distinguishing between that case and problematic packages. diff -Nru lintian-2.93.0/tags/p/possible-gpl-code-linked-with-openssl.tag lintian-2.89.0ubuntu1/tags/p/possible-gpl-code-linked-with-openssl.tag --- lintian-2.93.0/tags/p/possible-gpl-code-linked-with-openssl.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/possible-gpl-code-linked-with-openssl.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,14 +0,0 @@ -Tag: possible-gpl-code-linked-with-openssl -Severity: error -Check: debian/copyright -Explanation: This package appears to be covered by the GNU GPL but depends on - the OpenSSL libssl package and does not mention a license exemption or - exception for OpenSSL in its copyright file. The GPL (including version - 3) is incompatible with some terms of the OpenSSL license, and therefore - Debian does not allow GPL-licensed code linked with OpenSSL libraries - unless there is a license exception explicitly permitting this. - . - If only the Debian packaging, or some other part of the package not - linked with OpenSSL, is covered by the GNU GPL, please add a Lintian - override for this tag. Lintian currently has no good way of - distinguishing between that case and problematic packages. diff -Nru lintian-2.93.0/tags/p/possible-missing-colon-in-closes.desc lintian-2.89.0ubuntu1/tags/p/possible-missing-colon-in-closes.desc --- lintian-2.93.0/tags/p/possible-missing-colon-in-closes.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/possible-missing-colon-in-closes.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: possible-missing-colon-in-closes +Severity: error +Certainty: possible +Check: debian/changelog +Info: To close a bug in the Debian changelog, the word "closes" must be + followed by a colon. This entry looked like it was intended to close a + bug, but there's no colon after "closes". +Ref: policy 4.4 diff -Nru lintian-2.93.0/tags/p/possible-missing-colon-in-closes.tag lintian-2.89.0ubuntu1/tags/p/possible-missing-colon-in-closes.tag --- lintian-2.93.0/tags/p/possible-missing-colon-in-closes.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/possible-missing-colon-in-closes.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: possible-missing-colon-in-closes -Severity: error -Check: debian/changelog -Explanation: To close a bug in the Debian changelog, the word "closes" must be - followed by a colon. This entry looked like it was intended to close a - bug, but there's no colon after "closes". -See-Also: policy 4.4 diff -Nru lintian-2.93.0/tags/p/possible-new-upstream-release-without-new-version.desc lintian-2.89.0ubuntu1/tags/p/possible-new-upstream-release-without-new-version.desc --- lintian-2.93.0/tags/p/possible-new-upstream-release-without-new-version.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/possible-new-upstream-release-without-new-version.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: possible-new-upstream-release-without-new-version +Severity: warning +Certainty: possible +Check: debian/changelog +Info: The most recent changelog entry contains an entry that appears to + say this is a new upstream release (a comment similar to "new upstream + release," possibly with a word between "upstream" and "release"), but the + upstream portion of the package version number didn't change. This may + indicate that the package version was not updated properly in + debian/changelog. diff -Nru lintian-2.93.0/tags/p/possible-new-upstream-release-without-new-version.tag lintian-2.89.0ubuntu1/tags/p/possible-new-upstream-release-without-new-version.tag --- lintian-2.93.0/tags/p/possible-new-upstream-release-without-new-version.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/possible-new-upstream-release-without-new-version.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: possible-new-upstream-release-without-new-version -Severity: warning -Check: debian/changelog -Explanation: The most recent changelog entry contains an entry that appears to - say this is a new upstream release (a comment similar to "new upstream - release," possibly with a word between "upstream" and "release"), but the - upstream portion of the package version number didn't change. This may - indicate that the package version was not updated properly in - debian/changelog. diff -Nru lintian-2.93.0/tags/p/possible-unindented-list-in-extended-description.desc lintian-2.89.0ubuntu1/tags/p/possible-unindented-list-in-extended-description.desc --- lintian-2.93.0/tags/p/possible-unindented-list-in-extended-description.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/possible-unindented-list-in-extended-description.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: possible-unindented-list-in-extended-description +Severity: warning +Certainty: possible +Check: fields/description +Info: The package "Description:" contains an unindented line which + starts with a dash (-) or asterisk (*). If this was meant to be a + list of items these lines need to be indented (dselect would + word-wrap these lines otherwise). +Ref: policy 5.6.13 diff -Nru lintian-2.93.0/tags/p/possible-unindented-list-in-extended-description.tag lintian-2.89.0ubuntu1/tags/p/possible-unindented-list-in-extended-description.tag --- lintian-2.93.0/tags/p/possible-unindented-list-in-extended-description.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/possible-unindented-list-in-extended-description.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: possible-unindented-list-in-extended-description -Severity: warning -Check: fields/description -Explanation: The package "Description:" contains an unindented line which - starts with a dash (-) or asterisk (*). If this was meant to be a - list of items these lines need to be indented (dselect would - word-wrap these lines otherwise). -See-Also: policy 5.6.13 diff -Nru lintian-2.93.0/tags/p/possibly-insecure-handling-of-tmp-files-in-maintainer-script.desc lintian-2.89.0ubuntu1/tags/p/possibly-insecure-handling-of-tmp-files-in-maintainer-script.desc --- lintian-2.93.0/tags/p/possibly-insecure-handling-of-tmp-files-in-maintainer-script.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/possibly-insecure-handling-of-tmp-files-in-maintainer-script.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: possibly-insecure-handling-of-tmp-files-in-maintainer-script +Severity: warning +Certainty: possible +Check: scripts +Info: The maintainer script seems to access a file in /tmp or + some other temporary directory. Since creating temporary files in a + world-writable directory is very dangerous, this is likely to be a + security bug. Use the tempfile or mktemp utilities to + create temporary files in these directories. +Ref: policy 10.4 diff -Nru lintian-2.93.0/tags/p/possibly-insecure-handling-of-tmp-files-in-maintainer-script.tag lintian-2.89.0ubuntu1/tags/p/possibly-insecure-handling-of-tmp-files-in-maintainer-script.tag --- lintian-2.93.0/tags/p/possibly-insecure-handling-of-tmp-files-in-maintainer-script.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/possibly-insecure-handling-of-tmp-files-in-maintainer-script.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: possibly-insecure-handling-of-tmp-files-in-maintainer-script -Severity: warning -Check: scripts -Explanation: The maintainer script seems to access a file in /tmp or - some other temporary directory. Since creating temporary files in a - world-writable directory is very dangerous, this is likely to be a - security bug. Use the tempfile or mktemp utilities to - create temporary files in these directories. -See-Also: policy 10.4 diff -Nru lintian-2.93.0/tags/p/postinst-does-not-call-updatemenus.desc lintian-2.89.0ubuntu1/tags/p/postinst-does-not-call-updatemenus.desc --- lintian-2.93.0/tags/p/postinst-does-not-call-updatemenus.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/postinst-does-not-call-updatemenus.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,12 @@ +Tag: postinst-does-not-call-updatemenus +Severity: error +Check: menus +Info: Since the package installs a file in /etc/menu-methods, + /usr/share/menu, or /usr/lib/menu, the package should + probably call the update-menus command in it's postinst + script. + . + For example, use the following code in your maintainer script: + . + if which update-menus > /dev/null; then update-menus ; fi +Ref: menu 4.2 diff -Nru lintian-2.93.0/tags/p/postinst-does-not-call-updatemenus.tag lintian-2.89.0ubuntu1/tags/p/postinst-does-not-call-updatemenus.tag --- lintian-2.93.0/tags/p/postinst-does-not-call-updatemenus.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/postinst-does-not-call-updatemenus.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,12 +0,0 @@ -Tag: postinst-does-not-call-updatemenus -Severity: error -Check: menus -Explanation: Since the package installs a file in /etc/menu-methods, - /usr/share/menu, or /usr/lib/menu, the package should - probably call the update-menus command in it's postinst - script. - . - For example, use the following code in your maintainer script: - . - if which update-menus > /dev/null; then update-menus ; fi -See-Also: menu 4.2 diff -Nru lintian-2.93.0/tags/p/postinst-does-not-load-confmodule.desc lintian-2.89.0ubuntu1/tags/p/postinst-does-not-load-confmodule.desc --- lintian-2.93.0/tags/p/postinst-does-not-load-confmodule.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/postinst-does-not-load-confmodule.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: postinst-does-not-load-confmodule +Severity: warning +Check: debian/debconf +Info: Even if your postinst does not involve debconf, you currently need to + make sure it loads one of the debconf libraries. This will be changed in + the future. diff -Nru lintian-2.93.0/tags/p/postinst-does-not-load-confmodule.tag lintian-2.89.0ubuntu1/tags/p/postinst-does-not-load-confmodule.tag --- lintian-2.93.0/tags/p/postinst-does-not-load-confmodule.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/postinst-does-not-load-confmodule.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: postinst-does-not-load-confmodule -Severity: warning -Check: debian/debconf -Explanation: Even if your postinst does not involve debconf, you currently need to - make sure it loads one of the debconf libraries. This will be changed in - the future. diff -Nru lintian-2.93.0/tags/p/postinst-has-useless-call-to-install-docs.desc lintian-2.89.0ubuntu1/tags/p/postinst-has-useless-call-to-install-docs.desc --- lintian-2.93.0/tags/p/postinst-has-useless-call-to-install-docs.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/postinst-has-useless-call-to-install-docs.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: postinst-has-useless-call-to-install-docs +Severity: warning +Check: menus +Info: Explicitly calling install-docs in postinst is no + longer required since doc-base file processing is handled by triggers. + If the install-docs call was added by debhelper, rebuilding the + package with debhelper 7.2.3 or later will fix this problem. diff -Nru lintian-2.93.0/tags/p/postinst-has-useless-call-to-install-docs.tag lintian-2.89.0ubuntu1/tags/p/postinst-has-useless-call-to-install-docs.tag --- lintian-2.93.0/tags/p/postinst-has-useless-call-to-install-docs.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/postinst-has-useless-call-to-install-docs.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: postinst-has-useless-call-to-install-docs -Severity: warning -Check: menus -Explanation: Explicitly calling install-docs in postinst is no - longer required since doc-base file processing is handled by triggers. - If the install-docs call was added by debhelper, rebuilding the - package with debhelper 7.2.3 or later will fix this problem. diff -Nru lintian-2.93.0/tags/p/postinst-has-useless-call-to-update-menus.desc lintian-2.89.0ubuntu1/tags/p/postinst-has-useless-call-to-update-menus.desc --- lintian-2.93.0/tags/p/postinst-has-useless-call-to-update-menus.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/postinst-has-useless-call-to-update-menus.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: postinst-has-useless-call-to-update-menus +Severity: warning +Check: menus +Info: The postinst script calls the update-menus program + though no file is installed in /etc/menu-methods, + /usr/share/menu, or /usr/lib/menu. diff -Nru lintian-2.93.0/tags/p/postinst-has-useless-call-to-update-menus.tag lintian-2.89.0ubuntu1/tags/p/postinst-has-useless-call-to-update-menus.tag --- lintian-2.93.0/tags/p/postinst-has-useless-call-to-update-menus.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/postinst-has-useless-call-to-update-menus.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: postinst-has-useless-call-to-update-menus -Severity: warning -Check: menus -Explanation: The postinst script calls the update-menus program - though no file is installed in /etc/menu-methods, - /usr/share/menu, or /usr/lib/menu. diff -Nru lintian-2.93.0/tags/p/postinst-uses-db-input.desc lintian-2.89.0ubuntu1/tags/p/postinst-uses-db-input.desc --- lintian-2.93.0/tags/p/postinst-uses-db-input.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/postinst-uses-db-input.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: postinst-uses-db-input +Severity: warning +Certainty: possible +Check: debian/debconf +Info: It is generally not a good idea for postinst scripts to use debconf + commands like db_input. Typically, they should restrict themselves + to db_get to request previously acquired information, and have the + config script do the actual prompting. diff -Nru lintian-2.93.0/tags/p/postinst-uses-db-input.tag lintian-2.89.0ubuntu1/tags/p/postinst-uses-db-input.tag --- lintian-2.93.0/tags/p/postinst-uses-db-input.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/postinst-uses-db-input.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: postinst-uses-db-input -Severity: warning -Check: debian/debconf -Explanation: It is generally not a good idea for postinst scripts to use debconf - commands like db_input. Typically, they should restrict themselves - to db_get to request previously acquired information, and have the - config script do the actual prompting. diff -Nru lintian-2.93.0/tags/p/postrm-calls-installdocs.desc lintian-2.89.0ubuntu1/tags/p/postrm-calls-installdocs.desc --- lintian-2.93.0/tags/p/postrm-calls-installdocs.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/postrm-calls-installdocs.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,5 @@ +Tag: postrm-calls-installdocs +Severity: error +Check: menus +Info: The postrm script calls the install-docs command. Usually, + this command should be called from the prerm maintainer script. diff -Nru lintian-2.93.0/tags/p/postrm-calls-installdocs.tag lintian-2.89.0ubuntu1/tags/p/postrm-calls-installdocs.tag --- lintian-2.93.0/tags/p/postrm-calls-installdocs.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/postrm-calls-installdocs.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,5 +0,0 @@ -Tag: postrm-calls-installdocs -Severity: error -Check: menus -Explanation: The postrm script calls the install-docs command. Usually, - this command should be called from the prerm maintainer script. diff -Nru lintian-2.93.0/tags/p/postrm-contains-additional-updaterc.d-calls.desc lintian-2.89.0ubuntu1/tags/p/postrm-contains-additional-updaterc.d-calls.desc --- lintian-2.93.0/tags/p/postrm-contains-additional-updaterc.d-calls.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/postrm-contains-additional-updaterc.d-calls.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,5 @@ +Tag: postrm-contains-additional-updaterc.d-calls +Severity: error +Check: init.d +Info: The postrm de-registers an /etc/init.d script which + has not been registered in the postinst script before. diff -Nru lintian-2.93.0/tags/p/postrm-contains-additional-updaterc.d-calls.tag lintian-2.89.0ubuntu1/tags/p/postrm-contains-additional-updaterc.d-calls.tag --- lintian-2.93.0/tags/p/postrm-contains-additional-updaterc.d-calls.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/postrm-contains-additional-updaterc.d-calls.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,5 +0,0 @@ -Tag: postrm-contains-additional-updaterc.d-calls -Severity: error -Check: init.d -Explanation: The postrm de-registers an /etc/init.d script which - has not been registered in the postinst script before. diff -Nru lintian-2.93.0/tags/p/postrm-does-not-call-updatemenus.desc lintian-2.89.0ubuntu1/tags/p/postrm-does-not-call-updatemenus.desc --- lintian-2.93.0/tags/p/postrm-does-not-call-updatemenus.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/postrm-does-not-call-updatemenus.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,12 @@ +Tag: postrm-does-not-call-updatemenus +Severity: error +Check: menus +Info: Since the package installs a file in /etc/menu-methods, + /usr/share/menu, or /usr/lib/menu, the package should + probably call the update-menus command in it's postrm + script. + . + For example, use the following code in your maintainer script: + . + if which update-menus > /dev/null; then update-menus ; fi +Ref: menu 4.2 diff -Nru lintian-2.93.0/tags/p/postrm-does-not-call-updatemenus.tag lintian-2.89.0ubuntu1/tags/p/postrm-does-not-call-updatemenus.tag --- lintian-2.93.0/tags/p/postrm-does-not-call-updatemenus.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/postrm-does-not-call-updatemenus.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,12 +0,0 @@ -Tag: postrm-does-not-call-updatemenus -Severity: error -Check: menus -Explanation: Since the package installs a file in /etc/menu-methods, - /usr/share/menu, or /usr/lib/menu, the package should - probably call the update-menus command in it's postrm - script. - . - For example, use the following code in your maintainer script: - . - if which update-menus > /dev/null; then update-menus ; fi -See-Also: menu 4.2 diff -Nru lintian-2.93.0/tags/p/postrm-does-not-call-updaterc.d-for-init.d-script.desc lintian-2.89.0ubuntu1/tags/p/postrm-does-not-call-updaterc.d-for-init.d-script.desc --- lintian-2.93.0/tags/p/postrm-does-not-call-updaterc.d-for-init.d-script.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/postrm-does-not-call-updaterc.d-for-init.d-script.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: postrm-does-not-call-updaterc.d-for-init.d-script +Severity: error +Check: init.d +Info: An /etc/init.d script which has been registered in the + postinst script is not de-registered in the + postrm script. +Ref: policy 9.3.3.1 diff -Nru lintian-2.93.0/tags/p/postrm-does-not-call-updaterc.d-for-init.d-script.tag lintian-2.89.0ubuntu1/tags/p/postrm-does-not-call-updaterc.d-for-init.d-script.tag --- lintian-2.93.0/tags/p/postrm-does-not-call-updaterc.d-for-init.d-script.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/postrm-does-not-call-updaterc.d-for-init.d-script.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: postrm-does-not-call-updaterc.d-for-init.d-script -Severity: error -Check: init.d -Explanation: An /etc/init.d script which has been registered in the - postinst script is not de-registered in the - postrm script. -See-Also: policy 9.3.3.1 diff -Nru lintian-2.93.0/tags/p/postrm-does-not-purge-debconf.desc lintian-2.89.0ubuntu1/tags/p/postrm-does-not-purge-debconf.desc --- lintian-2.93.0/tags/p/postrm-does-not-purge-debconf.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/postrm-does-not-purge-debconf.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: postrm-does-not-purge-debconf +Severity: warning +Check: debian/debconf +Info: Packages using debconf should call db_purge or its equivalent + in their postrm. If the package uses debhelper, dh_installdebconf(1) should + take care of this. diff -Nru lintian-2.93.0/tags/p/postrm-does-not-purge-debconf.tag lintian-2.89.0ubuntu1/tags/p/postrm-does-not-purge-debconf.tag --- lintian-2.93.0/tags/p/postrm-does-not-purge-debconf.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/postrm-does-not-purge-debconf.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: postrm-does-not-purge-debconf -Severity: warning -Check: debian/debconf -Explanation: Packages using debconf should call db_purge or its equivalent - in their postrm. If the package uses debhelper, dh_installdebconf(1) should - take care of this. diff -Nru lintian-2.93.0/tags/p/postrm-has-useless-call-to-update-menus.desc lintian-2.89.0ubuntu1/tags/p/postrm-has-useless-call-to-update-menus.desc --- lintian-2.93.0/tags/p/postrm-has-useless-call-to-update-menus.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/postrm-has-useless-call-to-update-menus.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: postrm-has-useless-call-to-update-menus +Severity: warning +Check: menus +Info: The postrm script calls the update-menus program + though no file is installed in /etc/menu-methods, + /usr/share/menu, or /usr/lib/menu. diff -Nru lintian-2.93.0/tags/p/postrm-has-useless-call-to-update-menus.tag lintian-2.89.0ubuntu1/tags/p/postrm-has-useless-call-to-update-menus.tag --- lintian-2.93.0/tags/p/postrm-has-useless-call-to-update-menus.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/postrm-has-useless-call-to-update-menus.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: postrm-has-useless-call-to-update-menus -Severity: warning -Check: menus -Explanation: The postrm script calls the update-menus program - though no file is installed in /etc/menu-methods, - /usr/share/menu, or /usr/lib/menu. diff -Nru lintian-2.93.0/tags/p/postrm-removes-alternative.desc lintian-2.89.0ubuntu1/tags/p/postrm-removes-alternative.desc --- lintian-2.93.0/tags/p/postrm-removes-alternative.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/postrm-removes-alternative.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,17 @@ +Tag: postrm-removes-alternative +Severity: warning +Check: scripts +Renamed-From: maintainer-script-should-not-use-update-alternatives-remove +Info: update-alternatives --remove <alternative> foo is + called in the postrm. This can be dangerous because at the time the + postrm is executed foo has already been deleted and update-alternatives + will ignore it while constructing its list of available alternatives. + Then, if the /etc/alternatives symlink points at foo, update-alternatives + won't recognize it and will mark the symlink as something site-specific. + As such, the symlink will no longer be updated automatically and will be + left dangling until update-alternatives --auto + <alternative> is run by hand. + . + update-alternatives --remove should be called in the prerm + instead. +Ref: policy 6*, update-alternatives(8) diff -Nru lintian-2.93.0/tags/p/postrm-removes-alternative.tag lintian-2.89.0ubuntu1/tags/p/postrm-removes-alternative.tag --- lintian-2.93.0/tags/p/postrm-removes-alternative.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/postrm-removes-alternative.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,17 +0,0 @@ -Tag: postrm-removes-alternative -Severity: warning -Check: scripts -Renamed-From: maintainer-script-should-not-use-update-alternatives-remove -Explanation: update-alternatives --remove <alternative> foo is - called in the postrm. This can be dangerous because at the time the - postrm is executed foo has already been deleted and update-alternatives - will ignore it while constructing its list of available alternatives. - Then, if the /etc/alternatives symlink points at foo, update-alternatives - won't recognize it and will mark the symlink as something site-specific. - As such, the symlink will no longer be updated automatically and will be - left dangling until update-alternatives --auto - <alternative> is run by hand. - . - update-alternatives --remove should be called in the prerm - instead. -See-Also: policy 6*, update-alternatives(8) diff -Nru lintian-2.93.0/tags/p/preinst-calls-installdocs.desc lintian-2.89.0ubuntu1/tags/p/preinst-calls-installdocs.desc --- lintian-2.93.0/tags/p/preinst-calls-installdocs.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/preinst-calls-installdocs.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,5 @@ +Tag: preinst-calls-installdocs +Severity: error +Check: menus +Info: The preinst script calls the install-docs command. Usually, + this command should be called from the postinst maintainer script. diff -Nru lintian-2.93.0/tags/p/preinst-calls-installdocs.tag lintian-2.89.0ubuntu1/tags/p/preinst-calls-installdocs.tag --- lintian-2.93.0/tags/p/preinst-calls-installdocs.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/preinst-calls-installdocs.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,5 +0,0 @@ -Tag: preinst-calls-installdocs -Severity: error -Check: menus -Explanation: The preinst script calls the install-docs command. Usually, - this command should be called from the postinst maintainer script. diff -Nru lintian-2.93.0/tags/p/preinst-calls-updatemenus.desc lintian-2.89.0ubuntu1/tags/p/preinst-calls-updatemenus.desc --- lintian-2.93.0/tags/p/preinst-calls-updatemenus.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/preinst-calls-updatemenus.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,5 @@ +Tag: preinst-calls-updatemenus +Severity: error +Check: menus +Info: The preinst script calls the update-menus command. Usually, + this command should be called from the postinst maintainer script. diff -Nru lintian-2.93.0/tags/p/preinst-calls-updatemenus.tag lintian-2.89.0ubuntu1/tags/p/preinst-calls-updatemenus.tag --- lintian-2.93.0/tags/p/preinst-calls-updatemenus.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/preinst-calls-updatemenus.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,5 +0,0 @@ -Tag: preinst-calls-updatemenus -Severity: error -Check: menus -Explanation: The preinst script calls the update-menus command. Usually, - this command should be called from the postinst maintainer script. diff -Nru lintian-2.93.0/tags/p/preinst-calls-updaterc.d.desc lintian-2.89.0ubuntu1/tags/p/preinst-calls-updaterc.d.desc --- lintian-2.93.0/tags/p/preinst-calls-updaterc.d.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/preinst-calls-updaterc.d.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: preinst-calls-updaterc.d +Severity: error +Check: init.d +Info: The preinst package calls update-rc.d. Instead, + you should call it in the postinst script. +Ref: policy 9.3.3.1 diff -Nru lintian-2.93.0/tags/p/preinst-calls-updaterc.d.tag lintian-2.89.0ubuntu1/tags/p/preinst-calls-updaterc.d.tag --- lintian-2.93.0/tags/p/preinst-calls-updaterc.d.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/preinst-calls-updaterc.d.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: preinst-calls-updaterc.d -Severity: error -Check: init.d -Explanation: The preinst package calls update-rc.d. Instead, - you should call it in the postinst script. -See-Also: policy 9.3.3.1 diff -Nru lintian-2.93.0/tags/p/preinst-interpreter-without-predepends.desc lintian-2.89.0ubuntu1/tags/p/preinst-interpreter-without-predepends.desc --- lintian-2.93.0/tags/p/preinst-interpreter-without-predepends.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/preinst-interpreter-without-predepends.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,12 @@ +Tag: preinst-interpreter-without-predepends +Severity: error +Check: scripts +Info: The package contains a preinst maintainer script that uses + an unusual and non-essential interpreter but does not declare a + pre-dependency on the package that provides this interpreter. + . + preinst scripts should be written using only essential + interpreters to avoid additional dependency complexity. Please do not + add a pre-dependency without following the policy for doing so (Policy + section 3.5). +Ref: policy 7.2 diff -Nru lintian-2.93.0/tags/p/preinst-interpreter-without-predepends.tag lintian-2.89.0ubuntu1/tags/p/preinst-interpreter-without-predepends.tag --- lintian-2.93.0/tags/p/preinst-interpreter-without-predepends.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/preinst-interpreter-without-predepends.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,12 +0,0 @@ -Tag: preinst-interpreter-without-predepends -Severity: error -Check: scripts -Explanation: The package contains a preinst maintainer script that uses - an unusual and non-essential interpreter but does not declare a - pre-dependency on the package that provides this interpreter. - . - preinst scripts should be written using only essential - interpreters to avoid additional dependency complexity. Please do not - add a pre-dependency without following the policy for doing so (Policy - section 3.5). -See-Also: policy 7.2 diff -Nru lintian-2.93.0/tags/p/prerm-calls-updatemenus.desc lintian-2.89.0ubuntu1/tags/p/prerm-calls-updatemenus.desc --- lintian-2.93.0/tags/p/prerm-calls-updatemenus.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/prerm-calls-updatemenus.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,5 @@ +Tag: prerm-calls-updatemenus +Severity: error +Check: menus +Info: The prerm script calls the update-menus command. Usually, + this command should be called from the postrm maintainer script. diff -Nru lintian-2.93.0/tags/p/prerm-calls-updatemenus.tag lintian-2.89.0ubuntu1/tags/p/prerm-calls-updatemenus.tag --- lintian-2.93.0/tags/p/prerm-calls-updatemenus.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/prerm-calls-updatemenus.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,5 +0,0 @@ -Tag: prerm-calls-updatemenus -Severity: error -Check: menus -Explanation: The prerm script calls the update-menus command. Usually, - this command should be called from the postrm maintainer script. diff -Nru lintian-2.93.0/tags/p/prerm-calls-updaterc.d.desc lintian-2.89.0ubuntu1/tags/p/prerm-calls-updaterc.d.desc --- lintian-2.93.0/tags/p/prerm-calls-updaterc.d.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/prerm-calls-updaterc.d.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: prerm-calls-updaterc.d +Severity: error +Check: init.d +Info: The prerm package calls update-rc.d. Instead, + you should call it in the postrm script. +Ref: policy 9.3.3.1 diff -Nru lintian-2.93.0/tags/p/prerm-calls-updaterc.d.tag lintian-2.89.0ubuntu1/tags/p/prerm-calls-updaterc.d.tag --- lintian-2.93.0/tags/p/prerm-calls-updaterc.d.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/prerm-calls-updaterc.d.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: prerm-calls-updaterc.d -Severity: error -Check: init.d -Explanation: The prerm package calls update-rc.d. Instead, - you should call it in the postrm script. -See-Also: policy 9.3.3.1 diff -Nru lintian-2.93.0/tags/p/prerm-has-useless-call-to-install-docs.desc lintian-2.89.0ubuntu1/tags/p/prerm-has-useless-call-to-install-docs.desc --- lintian-2.93.0/tags/p/prerm-has-useless-call-to-install-docs.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/prerm-has-useless-call-to-install-docs.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: prerm-has-useless-call-to-install-docs +Severity: warning +Check: menus +Info: Explicitly calling install-docs in prerm is no + longer required since doc-base file processing is handled by triggers. + If the install-docs call was added by debhelper, rebuilding the + package with debhelper 7.2.3 or later will fix this problem. diff -Nru lintian-2.93.0/tags/p/prerm-has-useless-call-to-install-docs.tag lintian-2.89.0ubuntu1/tags/p/prerm-has-useless-call-to-install-docs.tag --- lintian-2.93.0/tags/p/prerm-has-useless-call-to-install-docs.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/prerm-has-useless-call-to-install-docs.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: prerm-has-useless-call-to-install-docs -Severity: warning -Check: menus -Explanation: Explicitly calling install-docs in prerm is no - longer required since doc-base file processing is handled by triggers. - If the install-docs call was added by debhelper, rebuilding the - package with debhelper 7.2.3 or later will fix this problem. diff -Nru lintian-2.93.0/tags/p/priority-extra-is-replaced-by-priority-optional.desc lintian-2.89.0ubuntu1/tags/p/priority-extra-is-replaced-by-priority-optional.desc --- lintian-2.93.0/tags/p/priority-extra-is-replaced-by-priority-optional.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/priority-extra-is-replaced-by-priority-optional.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: priority-extra-is-replaced-by-priority-optional +Severity: warning +Check: fields/priority +Info: Since Debian Policy version 4.0.1, the priority extra + has been deprecated. + . + Please update debian/control and replace all instances of + Priority: extra with Priority: optional. +Ref: policy 2.5 diff -Nru lintian-2.93.0/tags/p/priority-extra-is-replaced-by-priority-optional.tag lintian-2.89.0ubuntu1/tags/p/priority-extra-is-replaced-by-priority-optional.tag --- lintian-2.93.0/tags/p/priority-extra-is-replaced-by-priority-optional.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/priority-extra-is-replaced-by-priority-optional.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: priority-extra-is-replaced-by-priority-optional -Severity: warning -Check: fields/priority -Explanation: Since Debian Policy version 4.0.1, the priority extra - has been deprecated. - . - Please update debian/control and replace all instances of - Priority: extra with Priority: optional. -See-Also: policy 2.5 diff -Nru lintian-2.93.0/tags/p/privacy-breach-donation.desc lintian-2.89.0ubuntu1/tags/p/privacy-breach-donation.desc --- lintian-2.93.0/tags/p/privacy-breach-donation.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/privacy-breach-donation.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,17 @@ +Tag: privacy-breach-donation +Severity: error +Certainty: possible +Check: files/privacy-breach +Ref: https://wiki.debian.org/UpstreamMetadata +Info: This package create a potential privacy breach by fetching data + from a donation website at runtime. + . + Please remove this privacy problem and add a note to the + debian/upstream/metadata file using the donation field. + . + Please replace any scripts, images, or other remote resources with + non-remote resources. It is preferable to replace them with text and + links but local copies of the remote resources are also acceptable as + long as they don't also make calls to remote services. Please ensure + that the remote resources are suitable for Debian main before making + local copies of them. diff -Nru lintian-2.93.0/tags/p/privacy-breach-donation.tag lintian-2.89.0ubuntu1/tags/p/privacy-breach-donation.tag --- lintian-2.93.0/tags/p/privacy-breach-donation.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/privacy-breach-donation.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,16 +0,0 @@ -Tag: privacy-breach-donation -Severity: error -Check: files/privacy-breach -See-Also: https://wiki.debian.org/UpstreamMetadata -Explanation: This package create a potential privacy breach by fetching data - from a donation website at runtime. - . - Please remove this privacy problem and add a note to the - debian/upstream/metadata file using the donation field. - . - Please replace any scripts, images, or other remote resources with - non-remote resources. It is preferable to replace them with text and - links but local copies of the remote resources are also acceptable as - long as they don't also make calls to remote services. Please ensure - that the remote resources are suitable for Debian main before making - local copies of them. diff -Nru lintian-2.93.0/tags/p/privacy-breach-facebook.desc lintian-2.89.0ubuntu1/tags/p/privacy-breach-facebook.desc --- lintian-2.93.0/tags/p/privacy-breach-facebook.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/privacy-breach-facebook.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,13 @@ +Tag: privacy-breach-facebook +Severity: error +Certainty: possible +Check: files/privacy-breach +Info: This package creates a privacy breach by exchanging data with + Facebook at runtime via plugins such as "Share" or "Like" buttons. + . + Please replace any scripts, images, or other remote resources with + non-remote resources. It is preferable to replace them with text and + links but local copies of the remote resources are also acceptable as + long as they don't also make calls to remote services. Please ensure + that the remote resources are suitable for Debian main before making + local copies of them. diff -Nru lintian-2.93.0/tags/p/privacy-breach-facebook.tag lintian-2.89.0ubuntu1/tags/p/privacy-breach-facebook.tag --- lintian-2.93.0/tags/p/privacy-breach-facebook.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/privacy-breach-facebook.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,12 +0,0 @@ -Tag: privacy-breach-facebook -Severity: error -Check: files/privacy-breach -Explanation: This package creates a privacy breach by exchanging data with - Facebook at runtime via plugins such as "Share" or "Like" buttons. - . - Please replace any scripts, images, or other remote resources with - non-remote resources. It is preferable to replace them with text and - links but local copies of the remote resources are also acceptable as - long as they don't also make calls to remote services. Please ensure - that the remote resources are suitable for Debian main before making - local copies of them. diff -Nru lintian-2.93.0/tags/p/privacy-breach-generic.desc lintian-2.89.0ubuntu1/tags/p/privacy-breach-generic.desc --- lintian-2.93.0/tags/p/privacy-breach-generic.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/privacy-breach-generic.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,14 @@ +Tag: privacy-breach-generic +Severity: warning +Certainty: wild-guess +Check: files/privacy-breach +Info: This package creates a potential privacy breach by fetching data + from an external website at runtime. Please remove these scripts or + external HTML resources. + . + Please replace any scripts, images, or other remote resources with + non-remote resources. It is preferable to replace them with text and + links but local copies of the remote resources are also acceptable as + long as they don't also make calls to remote services. Please ensure + that the remote resources are suitable for Debian main before making + local copies of them. diff -Nru lintian-2.93.0/tags/p/privacy-breach-generic.tag lintian-2.89.0ubuntu1/tags/p/privacy-breach-generic.tag --- lintian-2.93.0/tags/p/privacy-breach-generic.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/privacy-breach-generic.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,13 +0,0 @@ -Tag: privacy-breach-generic -Severity: warning -Check: files/privacy-breach -Explanation: This package creates a potential privacy breach by fetching data - from an external website at runtime. Please remove these scripts or - external HTML resources. - . - Please replace any scripts, images, or other remote resources with - non-remote resources. It is preferable to replace them with text and - links but local copies of the remote resources are also acceptable as - long as they don't also make calls to remote services. Please ensure - that the remote resources are suitable for Debian main before making - local copies of them. diff -Nru lintian-2.93.0/tags/p/privacy-breach-google-adsense.desc lintian-2.89.0ubuntu1/tags/p/privacy-breach-google-adsense.desc --- lintian-2.93.0/tags/p/privacy-breach-google-adsense.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/privacy-breach-google-adsense.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,22 @@ +Tag: privacy-breach-google-adsense +Severity: error +Certainty: possible +Check: files/privacy-breach +Info: This package creates a privacy breach by using Google AdSense. + Google AdSense is a service run by Google that allows publishers + of websites to automatically serve advertisements. Unfortunately, it + requires tracking and breaching the privacy of web users. + . + This tag can also indicate the use of the related obsolete privacy + breaching software, Urchin WebAnalytics. + . + Note that using Google AdSense in a local copy of a page is a violation of + the Google AdSense terms of use. This violation renders this package not + distributable in Debian, and is thus a serious bug. + . + Please replace any scripts, images or other remote resources with + non-remote resources. It is preferable to replace them with text and + links but local copies of the remote resources are also acceptable as + long as they don't also make calls to remote services. Please ensure + that the remote resources are suitable for Debian main before making + local copies of them. diff -Nru lintian-2.93.0/tags/p/privacy-breach-google-adsense.tag lintian-2.89.0ubuntu1/tags/p/privacy-breach-google-adsense.tag --- lintian-2.93.0/tags/p/privacy-breach-google-adsense.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/privacy-breach-google-adsense.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,21 +0,0 @@ -Tag: privacy-breach-google-adsense -Severity: error -Check: files/privacy-breach -Explanation: This package creates a privacy breach by using Google AdSense. - Google AdSense is a service run by Google that allows publishers - of websites to automatically serve advertisements. Unfortunately, it - requires tracking and breaching the privacy of web users. - . - This tag can also indicate the use of the related obsolete privacy - breaching software, Urchin WebAnalytics. - . - Note that using Google AdSense in a local copy of a page is a violation of - the Google AdSense terms of use. This violation renders this package not - distributable in Debian, and is thus a serious bug. - . - Please replace any scripts, images or other remote resources with - non-remote resources. It is preferable to replace them with text and - links but local copies of the remote resources are also acceptable as - long as they don't also make calls to remote services. Please ensure - that the remote resources are suitable for Debian main before making - local copies of them. diff -Nru lintian-2.93.0/tags/p/privacy-breach-google-cse.desc lintian-2.89.0ubuntu1/tags/p/privacy-breach-google-cse.desc --- lintian-2.93.0/tags/p/privacy-breach-google-cse.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/privacy-breach-google-cse.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,14 @@ +Tag: privacy-breach-google-cse +Severity: error +Certainty: possible +Check: files/privacy-breach +Info: This package creates a potential privacy breach by fetching + data from Google at runtime, and may feed private data to Google via + Custom Search Engine queries. + . + Please replace any scripts, images, or other remote resources with + non-remote resources. It is preferable to replace them with text and + links but local copies of the remote resources are also acceptable as + long as they don't also make calls to remote services. Please ensure + that the remote resources are suitable for Debian main before making + local copies of them. diff -Nru lintian-2.93.0/tags/p/privacy-breach-google-cse.tag lintian-2.89.0ubuntu1/tags/p/privacy-breach-google-cse.tag --- lintian-2.93.0/tags/p/privacy-breach-google-cse.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/privacy-breach-google-cse.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,13 +0,0 @@ -Tag: privacy-breach-google-cse -Severity: error -Check: files/privacy-breach -Explanation: This package creates a potential privacy breach by fetching - data from Google at runtime, and may feed private data to Google via - Custom Search Engine queries. - . - Please replace any scripts, images, or other remote resources with - non-remote resources. It is preferable to replace them with text and - links but local copies of the remote resources are also acceptable as - long as they don't also make calls to remote services. Please ensure - that the remote resources are suitable for Debian main before making - local copies of them. diff -Nru lintian-2.93.0/tags/p/privacy-breach-google-plus.desc lintian-2.89.0ubuntu1/tags/p/privacy-breach-google-plus.desc --- lintian-2.93.0/tags/p/privacy-breach-google-plus.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/privacy-breach-google-plus.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,14 @@ +Tag: privacy-breach-google-plus +Severity: error +Certainty: possible +Check: files/privacy-breach +Info: This package creates a potential privacy breach by + exchanging data with Google+ at runtime via plugins such + as "+1" buttons. + . + Please replace any scripts, images, or other remote resources with + non-remote resources. It is preferable to replace them with text and + links but local copies of the remote resources are also acceptable as + long as they don't also make calls to remote services. Please ensure + that the remote resources are suitable for Debian main before making + local copies of them. diff -Nru lintian-2.93.0/tags/p/privacy-breach-google-plus.tag lintian-2.89.0ubuntu1/tags/p/privacy-breach-google-plus.tag --- lintian-2.93.0/tags/p/privacy-breach-google-plus.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/privacy-breach-google-plus.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,13 +0,0 @@ -Tag: privacy-breach-google-plus -Severity: error -Check: files/privacy-breach -Explanation: This package creates a potential privacy breach by - exchanging data with Google+ at runtime via plugins such - as "+1" buttons. - . - Please replace any scripts, images, or other remote resources with - non-remote resources. It is preferable to replace them with text and - links but local copies of the remote resources are also acceptable as - long as they don't also make calls to remote services. Please ensure - that the remote resources are suitable for Debian main before making - local copies of them. diff -Nru lintian-2.93.0/tags/p/privacy-breach-logo.desc lintian-2.89.0ubuntu1/tags/p/privacy-breach-logo.desc --- lintian-2.93.0/tags/p/privacy-breach-logo.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/privacy-breach-logo.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,18 @@ +Tag: privacy-breach-logo +Severity: error +Certainty: possible +Check: files/privacy-breach +Info: This package creates a potential privacy breach by fetching a + logo at runtime. + . + Before using a local copy you should check that the logo is suitable + for main. You can get help with determining this by posting a link to + the logo and a copy of, or a link to, the logo copyright and license + information to the debian-legal mailing list. + . + Please replace any scripts, images, or other remote resources with + non-remote resources. It is preferable to replace them with text and + links but local copies of the remote resources are also acceptable as + long as they don't also make calls to remote services. Please ensure + that the remote resources are suitable for Debian main before making + local copies of them. diff -Nru lintian-2.93.0/tags/p/privacy-breach-logo.tag lintian-2.89.0ubuntu1/tags/p/privacy-breach-logo.tag --- lintian-2.93.0/tags/p/privacy-breach-logo.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/privacy-breach-logo.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,17 +0,0 @@ -Tag: privacy-breach-logo -Severity: error -Check: files/privacy-breach -Explanation: This package creates a potential privacy breach by fetching a - logo at runtime. - . - Before using a local copy you should check that the logo is suitable - for main. You can get help with determining this by posting a link to - the logo and a copy of, or a link to, the logo copyright and license - information to the debian-legal mailing list. - . - Please replace any scripts, images, or other remote resources with - non-remote resources. It is preferable to replace them with text and - links but local copies of the remote resources are also acceptable as - long as they don't also make calls to remote services. Please ensure - that the remote resources are suitable for Debian main before making - local copies of them. diff -Nru lintian-2.93.0/tags/p/privacy-breach-piwik.desc lintian-2.89.0ubuntu1/tags/p/privacy-breach-piwik.desc --- lintian-2.93.0/tags/p/privacy-breach-piwik.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/privacy-breach-piwik.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,20 @@ +Tag: privacy-breach-piwik +Severity: error +Certainty: possible +Check: files/privacy-breach +Info: This package creates a privacy breach by using an online + Piwik module. + . + Piwik is a free and open source web analytics application, designed to + allow publishers of websites to track visitors. + . + Even though Piwik is free and respects the "Do Not Track" browser + option, it is nevertheless breaches the privacy of local users + by fetching data from internet. + . + Please replace any scripts, images, or other remote resources with + non-remote resources. It is preferable to replace them with text and + links but local copies of the remote resources are also acceptable as + long as they don't also make calls to remote services. Please ensure + that the remote resources are suitable for Debian main before making + local copies of them. diff -Nru lintian-2.93.0/tags/p/privacy-breach-piwik.tag lintian-2.89.0ubuntu1/tags/p/privacy-breach-piwik.tag --- lintian-2.93.0/tags/p/privacy-breach-piwik.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/privacy-breach-piwik.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,19 +0,0 @@ -Tag: privacy-breach-piwik -Severity: error -Check: files/privacy-breach -Explanation: This package creates a privacy breach by using an online - Piwik module. - . - Piwik is a free and open source web analytics application, designed to - allow publishers of websites to track visitors. - . - Even though Piwik is free and respects the "Do Not Track" browser - option, it is nevertheless breaches the privacy of local users - by fetching data from internet. - . - Please replace any scripts, images, or other remote resources with - non-remote resources. It is preferable to replace them with text and - links but local copies of the remote resources are also acceptable as - long as they don't also make calls to remote services. Please ensure - that the remote resources are suitable for Debian main before making - local copies of them. diff -Nru lintian-2.93.0/tags/p/privacy-breach-statistics-website.desc lintian-2.89.0ubuntu1/tags/p/privacy-breach-statistics-website.desc --- lintian-2.93.0/tags/p/privacy-breach-statistics-website.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/privacy-breach-statistics-website.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,25 @@ +Tag: privacy-breach-statistics-website +Severity: error +Certainty: possible +Check: files/privacy-breach +Info: This package creates a privacy breach by fetching data from + an external website in order to compile visitor statistics. + . + Please ask upstream to use the free software web analytics engine + Piwik, which respects the "Do Not Track" browser option. + . + This tag covers the following websites: + * cruel-carlota.pagodabox.com + * linkexchange.com (defunct) + * nedstatbasic.net + * onestat.com + * statcounter.com + * sitemeter.com + * webstats.motigo.com + . + Please replace any scripts, images, or other remote resources with + non-remote resources. It is preferable to replace them with text and + links but local copies of the remote resources are also acceptable as + long as they don't also make calls to remote services. Please ensure + that the remote resources are suitable for Debian main before making + local copies of them. diff -Nru lintian-2.93.0/tags/p/privacy-breach-statistics-website.tag lintian-2.89.0ubuntu1/tags/p/privacy-breach-statistics-website.tag --- lintian-2.93.0/tags/p/privacy-breach-statistics-website.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/privacy-breach-statistics-website.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,25 +0,0 @@ -Tag: privacy-breach-statistics-website -Severity: error -Check: files/privacy-breach -Explanation: This package creates a privacy breach by fetching data from - an external website in order to compile visitor statistics. - . - Please ask upstream to use the free software web analytics engine - Piwik, which respects the "Do Not Track" browser option. - . - This tag covers the following websites: - . - - cruel-carlota.pagodabox.com - - linkexchange.com (defunct) - - nedstatbasic.net - - onestat.com - - statcounter.com - - sitemeter.com - - webstats.motigo.com - . - Please replace any scripts, images, or other remote resources with - non-remote resources. It is preferable to replace them with text and - links but local copies of the remote resources are also acceptable as - long as they don't also make calls to remote services. Please ensure - that the remote resources are suitable for Debian main before making - local copies of them. diff -Nru lintian-2.93.0/tags/p/privacy-breach-twitter.desc lintian-2.89.0ubuntu1/tags/p/privacy-breach-twitter.desc --- lintian-2.93.0/tags/p/privacy-breach-twitter.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/privacy-breach-twitter.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,13 @@ +Tag: privacy-breach-twitter +Severity: error +Certainty: possible +Check: files/privacy-breach +Info: This package creates a potential privacy breach by + exchanging data with Twitter at runtime via plugins. + . + Please replace any scripts, images, or other remote resources with + non-remote resources. It is preferable to replace them with text and + links but local copies of the remote resources are also acceptable as + long as they don't also make calls to remote services. Please ensure + that the remote resources are suitable for Debian main before making + local copies of them. diff -Nru lintian-2.93.0/tags/p/privacy-breach-twitter.tag lintian-2.89.0ubuntu1/tags/p/privacy-breach-twitter.tag --- lintian-2.93.0/tags/p/privacy-breach-twitter.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/privacy-breach-twitter.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,12 +0,0 @@ -Tag: privacy-breach-twitter -Severity: error -Check: files/privacy-breach -Explanation: This package creates a potential privacy breach by - exchanging data with Twitter at runtime via plugins. - . - Please replace any scripts, images, or other remote resources with - non-remote resources. It is preferable to replace them with text and - links but local copies of the remote resources are also acceptable as - long as they don't also make calls to remote services. Please ensure - that the remote resources are suitable for Debian main before making - local copies of them. diff -Nru lintian-2.93.0/tags/p/privacy-breach-uses-embedded-file.desc lintian-2.89.0ubuntu1/tags/p/privacy-breach-uses-embedded-file.desc --- lintian-2.93.0/tags/p/privacy-breach-uses-embedded-file.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/privacy-breach-uses-embedded-file.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,12 @@ +Tag: privacy-breach-uses-embedded-file +Severity: error +Certainty: possible +Check: files/privacy-breach +Info: This package creates a potential privacy breach by fetching data + from an external website at runtime. Please remove these scripts or + external HTML resources. + . + Instead you can use the Debian package indicated in the context if it + is compatible. +Renamed-From: + privacy-breach-may-use-debian-package diff -Nru lintian-2.93.0/tags/p/privacy-breach-uses-embedded-file.tag lintian-2.89.0ubuntu1/tags/p/privacy-breach-uses-embedded-file.tag --- lintian-2.93.0/tags/p/privacy-breach-uses-embedded-file.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/privacy-breach-uses-embedded-file.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,11 +0,0 @@ -Tag: privacy-breach-uses-embedded-file -Severity: error -Check: files/privacy-breach -Explanation: This package creates a potential privacy breach by fetching data - from an external website at runtime. Please remove these scripts or - external HTML resources. - . - Instead you can use the Debian package indicated in the context if it - is compatible. -Renamed-From: - privacy-breach-may-use-debian-package diff -Nru lintian-2.93.0/tags/p/privacy-breach-w3c-valid-html.desc lintian-2.89.0ubuntu1/tags/p/privacy-breach-w3c-valid-html.desc --- lintian-2.93.0/tags/p/privacy-breach-w3c-valid-html.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/privacy-breach-w3c-valid-html.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,16 @@ +Tag: privacy-breach-w3c-valid-html +Severity: error +Certainty: possible +Check: files/privacy-breach +Ref: http://validator.w3.org/docs/help.html#icon, + http://www.w3.org/Consortium/Legal/logo-usage-20000308 +Info: This package creates a potential privacy breach by fetching W3C + validation icons. + . + These badges may be displayed to tell readers that care has been + taken to make a page compliant with W3C standards. Unfortunately, + downloading the image from www.w3.org might expose the reader's IP + address to potential tracking. + . + Note that these icons are non-free and must not be copied into the + package. You could safely delete this W3C validation badge. diff -Nru lintian-2.93.0/tags/p/privacy-breach-w3c-valid-html.tag lintian-2.89.0ubuntu1/tags/p/privacy-breach-w3c-valid-html.tag --- lintian-2.93.0/tags/p/privacy-breach-w3c-valid-html.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/privacy-breach-w3c-valid-html.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,15 +0,0 @@ -Tag: privacy-breach-w3c-valid-html -Severity: error -Check: files/privacy-breach -See-Also: http://validator.w3.org/docs/help.html#icon, - http://www.w3.org/Consortium/Legal/logo-usage-20000308 -Explanation: This package creates a potential privacy breach by fetching W3C - validation icons. - . - These badges may be displayed to tell readers that care has been - taken to make a page compliant with W3C standards. Unfortunately, - downloading the image from www.w3.org might expose the reader's IP - address to potential tracking. - . - Note that these icons are non-free and must not be copied into the - package. You could safely delete this W3C validation badge. diff -Nru lintian-2.93.0/tags/p/program-not-linked-against-libc.desc lintian-2.89.0ubuntu1/tags/p/program-not-linked-against-libc.desc --- lintian-2.93.0/tags/p/program-not-linked-against-libc.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/program-not-linked-against-libc.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,11 @@ +Tag: program-not-linked-against-libc +Severity: error +Certainty: possible +Check: binaries +Ref: #698720 +Info: The package installs a binary which is not dynamically linked + against libc. + . + It is theoretically possible to have a program which doesn't use any + symbols from libc, but it is far more likely that this binary simply + isn't linked correctly. diff -Nru lintian-2.93.0/tags/p/program-not-linked-against-libc.tag lintian-2.89.0ubuntu1/tags/p/program-not-linked-against-libc.tag --- lintian-2.93.0/tags/p/program-not-linked-against-libc.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/program-not-linked-against-libc.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,10 +0,0 @@ -Tag: program-not-linked-against-libc -Severity: error -Check: binaries -See-Also: Bug#698720 -Explanation: The package installs a binary which is not dynamically linked - against libc. - . - It is theoretically possible to have a program which doesn't use any - symbols from libc, but it is far more likely that this binary simply - isn't linked correctly. diff -Nru lintian-2.93.0/tags/p/public-upstream-key-in-native-package.desc lintian-2.89.0ubuntu1/tags/p/public-upstream-key-in-native-package.desc --- lintian-2.93.0/tags/p/public-upstream-key-in-native-package.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/public-upstream-key-in-native-package.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: public-upstream-key-in-native-package +Severity: info +Check: debian/upstream/signing-key +Ref: uscan(1) +Info: The source package contains a public upstream signing key even + though there is no upstream as the package is native. + . + Please remove the key. diff -Nru lintian-2.93.0/tags/p/public-upstream-key-in-native-package.tag lintian-2.89.0ubuntu1/tags/p/public-upstream-key-in-native-package.tag --- lintian-2.93.0/tags/p/public-upstream-key-in-native-package.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/public-upstream-key-in-native-package.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: public-upstream-key-in-native-package -Severity: info -Check: debian/upstream/signing-key -See-Also: uscan(1) -Explanation: The source package contains a public upstream signing key even - though there is no upstream as the package is native. - . - Please remove the key. diff -Nru lintian-2.93.0/tags/p/public-upstream-key-not-minimal.desc lintian-2.89.0ubuntu1/tags/p/public-upstream-key-not-minimal.desc --- lintian-2.93.0/tags/p/public-upstream-key-not-minimal.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/public-upstream-key-not-minimal.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,13 @@ +Tag: public-upstream-key-not-minimal +Severity: info +Check: debian/upstream/signing-key +Ref: uscan(1) +Info: The package contains a public upstream signing key with extra + signatures. The signatures are unnecessary and take up space in + the archive. + . + Please export the upstream key again with the command: + . + $ gpg --armor --export --export-options export-minimal,export-clean + . + and use that key instead of the key currently in the source package. diff -Nru lintian-2.93.0/tags/p/public-upstream-key-not-minimal.tag lintian-2.89.0ubuntu1/tags/p/public-upstream-key-not-minimal.tag --- lintian-2.93.0/tags/p/public-upstream-key-not-minimal.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/public-upstream-key-not-minimal.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,13 +0,0 @@ -Tag: public-upstream-key-not-minimal -Severity: info -Check: debian/upstream/signing-key -See-Also: uscan(1) -Explanation: The package contains a public upstream signing key with extra - signatures. The signatures are unnecessary and take up space in - the archive. - . - Please export the upstream key again with the command: - . - $ gpg --armor --export --export-options export-minimal,export-clean - . - and use that key instead of the key currently in the source package. diff -Nru lintian-2.93.0/tags/p/public-upstream-keys-in-multiple-locations.desc lintian-2.89.0ubuntu1/tags/p/public-upstream-keys-in-multiple-locations.desc --- lintian-2.93.0/tags/p/public-upstream-keys-in-multiple-locations.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/public-upstream-keys-in-multiple-locations.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,11 @@ +Tag: public-upstream-keys-in-multiple-locations +Severity: info +Check: debian/upstream/signing-key +Ref: uscan(1) +Info: The source package contains public upstream signing keys + (or keyrings) in multiple locations. This situation is potentially + confusing for uscan(1) or any other tool hoping to verify the + integrity and authenticity of upstream sources. + . + Please remove all keys (or keyrings) except one at the recommended + location debian/upstream/signing-key.asc. diff -Nru lintian-2.93.0/tags/p/public-upstream-keys-in-multiple-locations.tag lintian-2.89.0ubuntu1/tags/p/public-upstream-keys-in-multiple-locations.tag --- lintian-2.93.0/tags/p/public-upstream-keys-in-multiple-locations.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/public-upstream-keys-in-multiple-locations.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,11 +0,0 @@ -Tag: public-upstream-keys-in-multiple-locations -Severity: info -Check: debian/upstream/signing-key -See-Also: uscan(1) -Explanation: The source package contains public upstream signing keys - (or keyrings) in multiple locations. This situation is potentially - confusing for uscan(1) or any other tool hoping to verify the - integrity and authenticity of upstream sources. - . - Please remove all keys (or keyrings) except one at the recommended - location debian/upstream/signing-key.asc. diff -Nru lintian-2.93.0/tags/p/public-upstream-key-unusable.desc lintian-2.89.0ubuntu1/tags/p/public-upstream-key-unusable.desc --- lintian-2.93.0/tags/p/public-upstream-key-unusable.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/public-upstream-key-unusable.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: public-upstream-key-unusable +Severity: info +Check: debian/upstream/signing-key +Ref: uscan(1) +Info: The source package contains a public upstream signing key that + contains bogus, unexpected or unsuitable data. + . + Please obtain the correct key from upstream. diff -Nru lintian-2.93.0/tags/p/public-upstream-key-unusable.tag lintian-2.89.0ubuntu1/tags/p/public-upstream-key-unusable.tag --- lintian-2.93.0/tags/p/public-upstream-key-unusable.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/public-upstream-key-unusable.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: public-upstream-key-unusable -Severity: info -Check: debian/upstream/signing-key -See-Also: uscan(1) -Explanation: The source package contains a public upstream signing key that - contains bogus, unexpected or unsuitable data. - . - Please obtain the correct key from upstream. diff -Nru lintian-2.93.0/tags/p/python3-depends-but-no-python3-helper.desc lintian-2.89.0ubuntu1/tags/p/python3-depends-but-no-python3-helper.desc --- lintian-2.93.0/tags/p/python3-depends-but-no-python3-helper.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/python3-depends-but-no-python3-helper.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: python3-depends-but-no-python3-helper +Severity: error +Certainty: possible +Check: debhelper +Info: The source package declares a dependency on ${python3:Depends} in the + given binary package's debian/control entry. However, debian/rules doesn't + call any helper that would generate this substitution variable. diff -Nru lintian-2.93.0/tags/p/python3-depends-but-no-python3-helper.tag lintian-2.89.0ubuntu1/tags/p/python3-depends-but-no-python3-helper.tag --- lintian-2.93.0/tags/p/python3-depends-but-no-python3-helper.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/python3-depends-but-no-python3-helper.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: python3-depends-but-no-python3-helper -Severity: error -Check: debhelper -Explanation: The source package declares a dependency on ${python3:Depends} in the - given binary package's debian/control entry. However, debian/rules doesn't - call any helper that would generate this substitution variable. diff -Nru lintian-2.93.0/tags/p/python-debug-in-wrong-location.desc lintian-2.89.0ubuntu1/tags/p/python-debug-in-wrong-location.desc --- lintian-2.93.0/tags/p/python-debug-in-wrong-location.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/python-debug-in-wrong-location.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: python-debug-in-wrong-location +Severity: warning +Certainty: possible +Check: languages/python +Ref: #576014 +Info: The package appears to be installing debug modules in + /usr/lib/debug/usr/lib/pyshared/pythonX.Y/. However, gdb(1) + will not look for it there, making it less useful. The file + should be installed in /usr/lib/debug/usr/lib/pymodules/pythonX.Y/ + instead. diff -Nru lintian-2.93.0/tags/p/python-debug-in-wrong-location.tag lintian-2.89.0ubuntu1/tags/p/python-debug-in-wrong-location.tag --- lintian-2.93.0/tags/p/python-debug-in-wrong-location.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/python-debug-in-wrong-location.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: python-debug-in-wrong-location -Severity: warning -Check: languages/python -See-Also: Bug#576014 -Explanation: The package appears to be installing debug modules in - /usr/lib/debug/usr/lib/pyshared/pythonX.Y/. However, gdb(1) - will not look for it there, making it less useful. The file - should be installed in /usr/lib/debug/usr/lib/pymodules/pythonX.Y/ - instead. diff -Nru lintian-2.93.0/tags/p/python-depends-but-no-python-helper.desc lintian-2.89.0ubuntu1/tags/p/python-depends-but-no-python-helper.desc --- lintian-2.93.0/tags/p/python-depends-but-no-python-helper.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/python-depends-but-no-python-helper.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: python-depends-but-no-python-helper +Severity: error +Certainty: possible +Check: debhelper +Info: The source package declares a dependency on ${python:Depends} in the + given binary package's debian/control entry. However, debian/rules doesn't + call any helper that would generate this substitution variable. + . + The source package probably needs a call to dh_python2 (possibly via the + python2 dh add-on) in the debian/rules file. diff -Nru lintian-2.93.0/tags/p/python-depends-but-no-python-helper.tag lintian-2.89.0ubuntu1/tags/p/python-depends-but-no-python-helper.tag --- lintian-2.93.0/tags/p/python-depends-but-no-python-helper.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/python-depends-but-no-python-helper.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: python-depends-but-no-python-helper -Severity: error -Check: debhelper -Explanation: The source package declares a dependency on ${python:Depends} in the - given binary package's debian/control entry. However, debian/rules doesn't - call any helper that would generate this substitution variable. - . - The source package probably needs a call to dh_python2 (possibly via the - python2 dh add-on) in the debian/rules file. diff -Nru lintian-2.93.0/tags/p/python-foo-but-no-python3-foo.desc lintian-2.89.0ubuntu1/tags/p/python-foo-but-no-python3-foo.desc --- lintian-2.93.0/tags/p/python-foo-but-no-python3-foo.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/python-foo-but-no-python3-foo.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,16 @@ +Tag: python-foo-but-no-python3-foo +Severity: warning +Check: languages/python +Info: This source package appears to generate the specified Python 2 package + without creating a variant for Python 3. + . + The 2.x series of Python is due for deprecation and will not be maintained + by upstream past 2020 and will likely be dropped after the release of + Debian "buster". + . + If upstream have not moved or have no intention to move to Python 3, please + be certain that Debian would benefit from the continued inclusion of this + package and, if not, consider removing it. + . + Alternatively, ensure that the corresponding package specifies the + ${python3:Depends} substvar in its binary dependencies. diff -Nru lintian-2.93.0/tags/p/python-foo-but-no-python3-foo.tag lintian-2.89.0ubuntu1/tags/p/python-foo-but-no-python3-foo.tag --- lintian-2.93.0/tags/p/python-foo-but-no-python3-foo.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/python-foo-but-no-python3-foo.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,16 +0,0 @@ -Tag: python-foo-but-no-python3-foo -Severity: warning -Check: languages/python -Explanation: This source package appears to generate the specified Python 2 package - without creating a variant for Python 3. - . - The 2.x series of Python is due for deprecation and will not be maintained - by upstream past 2020 and will likely be dropped after the release of - Debian "buster". - . - If upstream have not moved or have no intention to move to Python 3, please - be certain that Debian would benefit from the continued inclusion of this - package and, if not, consider removing it. - . - Alternatively, ensure that the corresponding package specifies the - ${python3:Depends} substvar in its binary dependencies. diff -Nru lintian-2.93.0/tags/p/python-module-has-overly-generic-name.desc lintian-2.89.0ubuntu1/tags/p/python-module-has-overly-generic-name.desc --- lintian-2.93.0/tags/p/python-module-has-overly-generic-name.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/python-module-has-overly-generic-name.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: python-module-has-overly-generic-name +Severity: error +Check: languages/python +Info: This package installs a Python module with an overly generic name to + a global namespace. + . + This was either a mistake and/or likely to cause conflicts with other + packages. diff -Nru lintian-2.93.0/tags/p/python-module-has-overly-generic-name.tag lintian-2.89.0ubuntu1/tags/p/python-module-has-overly-generic-name.tag --- lintian-2.93.0/tags/p/python-module-has-overly-generic-name.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/python-module-has-overly-generic-name.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: python-module-has-overly-generic-name -Severity: error -Check: languages/python -Explanation: This package installs a Python module with an overly generic name to - a global namespace. - . - This was either a mistake and/or likely to cause conflicts with other - packages. diff -Nru lintian-2.93.0/tags/p/python-module-in-wrong-location.desc lintian-2.89.0ubuntu1/tags/p/python-module-in-wrong-location.desc --- lintian-2.93.0/tags/p/python-module-in-wrong-location.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/python-module-in-wrong-location.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: python-module-in-wrong-location +Severity: warning +Certainty: possible +Check: languages/python +Ref: python-policy 2.5, #576012 +Info: The package installs a Python module or debug information for a Python + module in the wrong location for the given version of Python. + . + dh_python3 can be used to fix this for Python 3 modules. diff -Nru lintian-2.93.0/tags/p/python-module-in-wrong-location.tag lintian-2.89.0ubuntu1/tags/p/python-module-in-wrong-location.tag --- lintian-2.93.0/tags/p/python-module-in-wrong-location.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/python-module-in-wrong-location.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: python-module-in-wrong-location -Severity: warning -Check: languages/python -See-Also: python-policy 2.5, Bug#576012 -Explanation: The package installs a Python module or debug information for a Python - module in the wrong location for the given version of Python. - . - dh_python3 can be used to fix this for Python 3 modules. diff -Nru lintian-2.93.0/tags/p/python-package-depends-on-package-from-other-python-variant.desc lintian-2.89.0ubuntu1/tags/p/python-package-depends-on-package-from-other-python-variant.desc --- lintian-2.93.0/tags/p/python-package-depends-on-package-from-other-python-variant.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/python-package-depends-on-package-from-other-python-variant.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: python-package-depends-on-package-from-other-python-variant +Severity: warning +Check: languages/python +Info: Either the specified Python 3.x package declares a dependency on a + Python 2.x package, or the specified Python 2.x package depends on a Python + 3.x package. + . + This is likely a typo in debian/control or due to misconfigured + calls to, for example, dh_installdocs --link-doc=PKG. +Ref: #884692 diff -Nru lintian-2.93.0/tags/p/python-package-depends-on-package-from-other-python-variant.tag lintian-2.89.0ubuntu1/tags/p/python-package-depends-on-package-from-other-python-variant.tag --- lintian-2.93.0/tags/p/python-package-depends-on-package-from-other-python-variant.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/python-package-depends-on-package-from-other-python-variant.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,10 +0,0 @@ -Tag: python-package-depends-on-package-from-other-python-variant -Severity: warning -Check: languages/python -Explanation: Either the specified Python 3.x package declares a dependency on a - Python 2.x package, or the specified Python 2.x package depends on a Python - 3.x package. - . - This is likely a typo in debian/control or due to misconfigured - calls to, for example, dh_installdocs --link-doc=PKG. -See-Also: Bug#884692 diff -Nru lintian-2.93.0/tags/p/python-package-missing-depends-on-python.desc lintian-2.89.0ubuntu1/tags/p/python-package-missing-depends-on-python.desc --- lintian-2.93.0/tags/p/python-package-missing-depends-on-python.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/python-package-missing-depends-on-python.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: python-package-missing-depends-on-python +Severity: error +Check: languages/python +Info: The specified Python package ships Python modules under + /usr/lib but does not specify any dependency on Python. + . + This is likely an omission, the result of a typo in + debian/control or the file should not be installed. diff -Nru lintian-2.93.0/tags/p/python-package-missing-depends-on-python.tag lintian-2.89.0ubuntu1/tags/p/python-package-missing-depends-on-python.tag --- lintian-2.93.0/tags/p/python-package-missing-depends-on-python.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/python-package-missing-depends-on-python.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: python-package-missing-depends-on-python -Severity: error -Check: languages/python -Explanation: The specified Python package ships Python modules under - /usr/lib but does not specify any dependency on Python. - . - This is likely an omission, the result of a typo in - debian/control or the file should not be installed. diff -Nru lintian-2.93.0/tags/p/python-script-but-no-python-dep.desc lintian-2.89.0ubuntu1/tags/p/python-script-but-no-python-dep.desc --- lintian-2.93.0/tags/p/python-script-but-no-python-dep.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/python-script-but-no-python-dep.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,22 @@ +Tag: python-script-but-no-python-dep +Severity: error +Check: scripts +Info: Packages with Python scripts should depend on the package + python. Those with scripts that specify a specific version of + Python must depend, recommend or suggest on that version of Python + (exactly). + . + For example, if a script in the package uses #!/usr/bin/python, + the package needs a dependency on python. If a script uses + #!/usr/bin/python2.6, the package needs a dependency on + python2.6. A dependency on python (>= 2.6) is not + correct, since later versions of Python may not provide the + /usr/bin/python2.6 binary. + . + If you are using debhelper, adding ${python3:Depends} or + ${python:Depends} to the Depends field and ensuring dh_python2 or + dh_python3 are run during the build should take care of adding the correct + dependency. + . + In some cases a weaker relationship, such as Suggests or Recommends, will + be more appropriate. diff -Nru lintian-2.93.0/tags/p/python-script-but-no-python-dep.tag lintian-2.89.0ubuntu1/tags/p/python-script-but-no-python-dep.tag --- lintian-2.93.0/tags/p/python-script-but-no-python-dep.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/python-script-but-no-python-dep.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,22 +0,0 @@ -Tag: python-script-but-no-python-dep -Severity: error -Check: scripts -Explanation: Packages with Python scripts should depend on the package - python. Those with scripts that specify a specific version of - Python must depend, recommend or suggest on that version of Python - (exactly). - . - For example, if a script in the package uses #!/usr/bin/python, - the package needs a dependency on python. If a script uses - #!/usr/bin/python2.6, the package needs a dependency on - python2.6. A dependency on python (>= 2.6) is not - correct, since later versions of Python may not provide the - /usr/bin/python2.6 binary. - . - If you are using debhelper, adding ${python3:Depends} or - ${python:Depends} to the Depends field and ensuring dh_python2 or - dh_python3 are run during the build should take care of adding the correct - dependency. - . - In some cases a weaker relationship, such as Suggests or Recommends, will - be more appropriate. diff -Nru lintian-2.93.0/tags/p/python-version-current-is-deprecated.desc lintian-2.89.0ubuntu1/tags/p/python-version-current-is-deprecated.desc --- lintian-2.93.0/tags/p/python-version-current-is-deprecated.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/python-version-current-is-deprecated.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: python-version-current-is-deprecated +Severity: warning +Check: languages/python +Info: The use of "current" in the Python-Version or Python3-Version + field is deprecated. +Ref: python-policy 3.4 diff -Nru lintian-2.93.0/tags/p/python-version-current-is-deprecated.tag lintian-2.89.0ubuntu1/tags/p/python-version-current-is-deprecated.tag --- lintian-2.93.0/tags/p/python-version-current-is-deprecated.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/p/python-version-current-is-deprecated.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: python-version-current-is-deprecated -Severity: warning -Check: languages/python -Explanation: The use of "current" in the Python-Version or Python3-Version - field is deprecated. -See-Also: python-policy 3.4 diff -Nru lintian-2.93.0/tags/q/qa-upload-has-incorrect-version-number.desc lintian-2.89.0ubuntu1/tags/q/qa-upload-has-incorrect-version-number.desc --- lintian-2.93.0/tags/q/qa-upload-has-incorrect-version-number.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/q/qa-upload-has-incorrect-version-number.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,5 @@ +Tag: qa-upload-has-incorrect-version-number +Severity: warning +Check: nmu +Info: A QA upload (uploading an orphaned package without adopting it) is + always a maintainer upload: it should not get a NMU revision number. diff -Nru lintian-2.93.0/tags/q/qa-upload-has-incorrect-version-number.tag lintian-2.89.0ubuntu1/tags/q/qa-upload-has-incorrect-version-number.tag --- lintian-2.93.0/tags/q/qa-upload-has-incorrect-version-number.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/q/qa-upload-has-incorrect-version-number.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,5 +0,0 @@ -Tag: qa-upload-has-incorrect-version-number -Severity: warning -Check: nmu -Explanation: A QA upload (uploading an orphaned package without adopting it) is - always a maintainer upload: it should not get a NMU revision number. diff -Nru lintian-2.93.0/tags/q/quilt-build-dep-but-no-series-file.desc lintian-2.89.0ubuntu1/tags/q/quilt-build-dep-but-no-series-file.desc --- lintian-2.93.0/tags/q/quilt-build-dep-but-no-series-file.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/q/quilt-build-dep-but-no-series-file.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,11 @@ +Tag: quilt-build-dep-but-no-series-file +Severity: warning +Check: debian/patches/quilt +Info: Using quilt requires you to explicitly list all patches you want + to apply in debian/patches/series. This package build-depends on quilt, + but does not provide a patch list. You should either remove the quilt + build dependency or add a series file. + . + Note that an empty file cannot be represented in the Debian diff, so an + empty series file will disappear in the source package. If you intended + for the series file to be empty, add a comment line. diff -Nru lintian-2.93.0/tags/q/quilt-build-dep-but-no-series-file.tag lintian-2.89.0ubuntu1/tags/q/quilt-build-dep-but-no-series-file.tag --- lintian-2.93.0/tags/q/quilt-build-dep-but-no-series-file.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/q/quilt-build-dep-but-no-series-file.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,11 +0,0 @@ -Tag: quilt-build-dep-but-no-series-file -Severity: warning -Check: debian/patches/quilt -Explanation: Using quilt requires you to explicitly list all patches you want - to apply in debian/patches/series. This package build-depends on quilt, - but does not provide a patch list. You should either remove the quilt - build dependency or add a series file. - . - Note that an empty file cannot be represented in the Debian diff, so an - empty series file will disappear in the source package. If you intended - for the series file to be empty, add a comment line. diff -Nru lintian-2.93.0/tags/q/quilt-patch-missing-description.desc lintian-2.89.0ubuntu1/tags/q/quilt-patch-missing-description.desc --- lintian-2.93.0/tags/q/quilt-patch-missing-description.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/q/quilt-patch-missing-description.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,16 @@ +Tag: quilt-patch-missing-description +Severity: info +Check: debian/patches/quilt +Info: quilt patch files should start with a description of patch. All + lines before the start of the patch itself are considered part of the + description. You can edit the description with quilt header -e + when the patch is at the top of the stack. + . + As well as a description of the purpose and function of the patch, the + description should ideally contain author information, a URL for the bug + report (if any), Debian or upstream bugs fixed by it, upstream status, + the Debian version and date the patch was first included, and any other + information that would be useful if someone were investigating the + patch and underlying problem. Please consider using the DEP 3 format for + this information. +Ref: https://dep-team.pages.debian.net/deps/dep3/ diff -Nru lintian-2.93.0/tags/q/quilt-patch-missing-description.tag lintian-2.89.0ubuntu1/tags/q/quilt-patch-missing-description.tag --- lintian-2.93.0/tags/q/quilt-patch-missing-description.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/q/quilt-patch-missing-description.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,16 +0,0 @@ -Tag: quilt-patch-missing-description -Severity: info -Check: debian/patches/quilt -Explanation: quilt patch files should start with a description of patch. All - lines before the start of the patch itself are considered part of the - description. You can edit the description with quilt header -e - when the patch is at the top of the stack. - . - As well as a description of the purpose and function of the patch, the - description should ideally contain author information, a URL for the bug - report (if any), Debian or upstream bugs fixed by it, upstream status, - the Debian version and date the patch was first included, and any other - information that would be useful if someone were investigating the - patch and underlying problem. Please consider using the DEP 3 format for - this information. -See-Also: https://dep-team.pages.debian.net/deps/dep3/ diff -Nru lintian-2.93.0/tags/q/quilt-patch-using-template-description.desc lintian-2.89.0ubuntu1/tags/q/quilt-patch-using-template-description.desc --- lintian-2.93.0/tags/q/quilt-patch-using-template-description.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/q/quilt-patch-using-template-description.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: quilt-patch-using-template-description +Severity: info +Check: debian/patches/quilt +Info: The patch contains a standard DEP 3 template description + included by dpkg-source(1). Please consider replacing the template + with a real description. You can edit the description by using + quilt header -e when the patch is at the top of the stack. + Alternatively, editing the patch in most text editors should work + as well. +Ref: https://dep-team.pages.debian.net/deps/dep3/ diff -Nru lintian-2.93.0/tags/q/quilt-patch-using-template-description.tag lintian-2.89.0ubuntu1/tags/q/quilt-patch-using-template-description.tag --- lintian-2.93.0/tags/q/quilt-patch-using-template-description.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/q/quilt-patch-using-template-description.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,10 +0,0 @@ -Tag: quilt-patch-using-template-description -Severity: info -Check: debian/patches/quilt -Explanation: The patch contains a standard DEP 3 template description - included by dpkg-source(1). Please consider replacing the template - with a real description. You can edit the description by using - quilt header -e when the patch is at the top of the stack. - Alternatively, editing the patch in most text editors should work - as well. -See-Also: https://dep-team.pages.debian.net/deps/dep3/ diff -Nru lintian-2.93.0/tags/q/quilt-patch-with-non-standard-options.desc lintian-2.89.0ubuntu1/tags/q/quilt-patch-with-non-standard-options.desc --- lintian-2.93.0/tags/q/quilt-patch-with-non-standard-options.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/q/quilt-patch-with-non-standard-options.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,12 @@ +Tag: quilt-patch-with-non-standard-options +Severity: warning +Check: debian/patches/quilt +Info: The quilt series file contains non-standard options to apply some of + the listed patches. Quilt uses '-p1' by default if nothing is specified + after the name of the patch and the current series file specify something + else for some of the patches listed. + . + For compatibility with the source "3.0 (quilt)" source package format, + you should avoid using any option at all and make sure that your patches + apply with "-p1". This can be done by refreshing all patches like this: + quilt pop -a; while quilt push; do quilt refresh -pab; done diff -Nru lintian-2.93.0/tags/q/quilt-patch-with-non-standard-options.tag lintian-2.89.0ubuntu1/tags/q/quilt-patch-with-non-standard-options.tag --- lintian-2.93.0/tags/q/quilt-patch-with-non-standard-options.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/q/quilt-patch-with-non-standard-options.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,12 +0,0 @@ -Tag: quilt-patch-with-non-standard-options -Severity: warning -Check: debian/patches/quilt -Explanation: The quilt series file contains non-standard options to apply some of - the listed patches. Quilt uses '-p1' by default if nothing is specified - after the name of the patch and the current series file specify something - else for some of the patches listed. - . - For compatibility with the source "3.0 (quilt)" source package format, - you should avoid using any option at all and make sure that your patches - apply with "-p1". This can be done by refreshing all patches like this: - quilt pop -a; while quilt push; do quilt refresh -pab; done diff -Nru lintian-2.93.0/tags/q/quilt-series-but-no-build-dep.desc lintian-2.89.0ubuntu1/tags/q/quilt-series-but-no-build-dep.desc --- lintian-2.93.0/tags/q/quilt-series-but-no-build-dep.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/q/quilt-series-but-no-build-dep.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,14 @@ +Tag: quilt-series-but-no-build-dep +Severity: warning +Certainty: possible +Check: debian/patches/quilt +Info: The package contains a debian/patches/series file usually used by + quilt to apply patches at build time, but quilt is not listed in the + build dependencies. + . + You should either remove the series file if it's effectively not useful + or add quilt to the build-dependencies if quilt is used during the build + process. + . + If you don't need quilt during build but only during maintenance work, + then you can override this warning. diff -Nru lintian-2.93.0/tags/q/quilt-series-but-no-build-dep.tag lintian-2.89.0ubuntu1/tags/q/quilt-series-but-no-build-dep.tag --- lintian-2.93.0/tags/q/quilt-series-but-no-build-dep.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/q/quilt-series-but-no-build-dep.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,13 +0,0 @@ -Tag: quilt-series-but-no-build-dep -Severity: warning -Check: debian/patches/quilt -Explanation: The package contains a debian/patches/series file usually used by - quilt to apply patches at build time, but quilt is not listed in the - build dependencies. - . - You should either remove the series file if it's effectively not useful - or add quilt to the build-dependencies if quilt is used during the build - process. - . - If you don't need quilt during build but only during maintenance work, - then you can override this warning. diff -Nru lintian-2.93.0/tags/q/quilt-series-references-non-existent-patch.desc lintian-2.89.0ubuntu1/tags/q/quilt-series-references-non-existent-patch.desc --- lintian-2.93.0/tags/q/quilt-series-references-non-existent-patch.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/q/quilt-series-references-non-existent-patch.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,5 @@ +Tag: quilt-series-references-non-existent-patch +Severity: error +Check: debian/patches/quilt +Info: In the series file listing all your quilt patches, you referenced a + file that does not exist. This will lead to a fatal error when calling quilt. diff -Nru lintian-2.93.0/tags/q/quilt-series-references-non-existent-patch.tag lintian-2.89.0ubuntu1/tags/q/quilt-series-references-non-existent-patch.tag --- lintian-2.93.0/tags/q/quilt-series-references-non-existent-patch.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/q/quilt-series-references-non-existent-patch.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,5 +0,0 @@ -Tag: quilt-series-references-non-existent-patch -Severity: error -Check: debian/patches/quilt -Explanation: In the series file listing all your quilt patches, you referenced a - file that does not exist. This will lead to a fatal error when calling quilt. diff -Nru lintian-2.93.0/tags/q/quilt-series-without-trailing-newline.desc lintian-2.89.0ubuntu1/tags/q/quilt-series-without-trailing-newline.desc --- lintian-2.93.0/tags/q/quilt-series-without-trailing-newline.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/q/quilt-series-without-trailing-newline.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: quilt-series-without-trailing-newline +Severity: error +Certainty: possible +Check: debian/patches/quilt +Info: The package contains a debian/patches/series file + that doesn't end with a newline. dpkg-source may silently + corrupt this file. +Ref: #584233 diff -Nru lintian-2.93.0/tags/q/quilt-series-without-trailing-newline.tag lintian-2.89.0ubuntu1/tags/q/quilt-series-without-trailing-newline.tag --- lintian-2.93.0/tags/q/quilt-series-without-trailing-newline.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/q/quilt-series-without-trailing-newline.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: quilt-series-without-trailing-newline -Severity: error -Check: debian/patches/quilt -Explanation: The package contains a debian/patches/series file - that doesn't end with a newline. dpkg-source may silently - corrupt this file. -See-Also: Bug#584233 diff -Nru lintian-2.93.0/tags/q/quoted-placeholder-in-mailcap-entry.desc lintian-2.89.0ubuntu1/tags/q/quoted-placeholder-in-mailcap-entry.desc --- lintian-2.93.0/tags/q/quoted-placeholder-in-mailcap-entry.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/q/quoted-placeholder-in-mailcap-entry.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,14 @@ +Tag: quoted-placeholder-in-mailcap-entry +Severity: warning +Check: mailcap +Info: The %s placeholder in a mailcap entry is quoted. That is + considered unsafe. Proper escaping should be left to the programs using + the entry. + . + Please remove the single or double quotes around %s. +Ref: #33486, + #90483, + #745141, + https://tools.ietf.org/rfc/rfc1524.txt, + http://bugs.debian.org/745141#17, + https://lists.debian.org/debian-user/2005/04/msg01185.html diff -Nru lintian-2.93.0/tags/q/quoted-placeholder-in-mailcap-entry.tag lintian-2.89.0ubuntu1/tags/q/quoted-placeholder-in-mailcap-entry.tag --- lintian-2.93.0/tags/q/quoted-placeholder-in-mailcap-entry.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/q/quoted-placeholder-in-mailcap-entry.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,14 +0,0 @@ -Tag: quoted-placeholder-in-mailcap-entry -Severity: warning -Check: mailcap -Explanation: The %s placeholder in a mailcap entry is quoted. That is - considered unsafe. Proper escaping should be left to the programs using - the entry. - . - Please remove the single or double quotes around %s. -See-Also: Bug#33486, - Bug#90483, - Bug#745141, - https://tools.ietf.org/rfc/rfc1524.txt, - http://bugs.debian.org/745141#17, - https://lists.debian.org/debian-user/2005/04/msg01185.html diff -Nru lintian-2.93.0/tags/r/raster-image-in-scalable-directory.desc lintian-2.89.0ubuntu1/tags/r/raster-image-in-scalable-directory.desc --- lintian-2.93.0/tags/r/raster-image-in-scalable-directory.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/r/raster-image-in-scalable-directory.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,5 @@ +Tag: raster-image-in-scalable-directory +Severity: warning +Check: desktop/icons +Info: The given raster image was installed into a "scalable" icon directory. + Only vector graphics (e.g. SVG) should be installed into those directories. diff -Nru lintian-2.93.0/tags/r/raster-image-in-scalable-directory.tag lintian-2.89.0ubuntu1/tags/r/raster-image-in-scalable-directory.tag --- lintian-2.93.0/tags/r/raster-image-in-scalable-directory.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/r/raster-image-in-scalable-directory.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,5 +0,0 @@ -Tag: raster-image-in-scalable-directory -Severity: warning -Check: desktop/icons -Explanation: The given raster image was installed into a "scalable" icon directory. - Only vector graphics (e.g. SVG) should be installed into those directories. diff -Nru lintian-2.93.0/tags/r/rc-version-greater-than-expected-version.desc lintian-2.89.0ubuntu1/tags/r/rc-version-greater-than-expected-version.desc --- lintian-2.93.0/tags/r/rc-version-greater-than-expected-version.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/r/rc-version-greater-than-expected-version.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: rc-version-greater-than-expected-version +Severity: warning +Certainty: possible +Check: debian/changelog +Ref: policy 5.6.12 +Info: The package appears to be a release candidate or preview release, but + the version sorts higher than the expected final release. + . + For non-native packages, the check examines the upstream version. + For native packages, it looks at the Debian maintainer's revision. diff -Nru lintian-2.93.0/tags/r/rc-version-greater-than-expected-version.tag lintian-2.89.0ubuntu1/tags/r/rc-version-greater-than-expected-version.tag --- lintian-2.93.0/tags/r/rc-version-greater-than-expected-version.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/r/rc-version-greater-than-expected-version.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: rc-version-greater-than-expected-version -Severity: warning -Check: debian/changelog -See-Also: policy 5.6.12 -Explanation: The package appears to be a release candidate or preview release, but - the version sorts higher than the expected final release. - . - For non-native packages, the check examines the upstream version. - For native packages, it looks at the Debian maintainer's revision. diff -Nru lintian-2.93.0/tags/r/r-data-without-readme-source.desc lintian-2.89.0ubuntu1/tags/r/r-data-without-readme-source.desc --- lintian-2.93.0/tags/r/r-data-without-readme-source.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/r/r-data-without-readme-source.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,11 @@ +Tag: r-data-without-readme-source +Severity: error +Check: cruft +Info: Many modules packaged for the R Project for Statistical Computing contain + data files with names as *.rda, *.Rda, *.rdata, *.Rdata, etc. + . + When such files exist, the FTP masters expect them to be explained in + debian/README.source, which this package is missing. + . + Please add a README.source documenting the origins of these files. +Ref: https://lists.debian.org/debian-devel/2013/09/msg00332.html diff -Nru lintian-2.93.0/tags/r/r-data-without-readme-source.tag lintian-2.89.0ubuntu1/tags/r/r-data-without-readme-source.tag --- lintian-2.93.0/tags/r/r-data-without-readme-source.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/r/r-data-without-readme-source.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,11 +0,0 @@ -Tag: r-data-without-readme-source -Severity: error -Check: cruft -Explanation: Many modules packaged for the R Project for Statistical Computing contain - data files with names as *.rda, *.Rda, *.rdata, *.Rdata, etc. - . - When such files exist, the FTP masters expect them to be explained in - debian/README.source, which this package is missing. - . - Please add a README.source documenting the origins of these files. -See-Also: https://lists.debian.org/debian-devel/2013/09/msg00332.html diff -Nru lintian-2.93.0/tags/r/read-in-maintainer-script.desc lintian-2.89.0ubuntu1/tags/r/read-in-maintainer-script.desc --- lintian-2.93.0/tags/r/read-in-maintainer-script.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/r/read-in-maintainer-script.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,14 @@ +Tag: read-in-maintainer-script +Severity: error +Certainty: possible +Check: scripts +Ref: policy 3.9.1 +Info: This maintainer script appears to use read to get information from + the user. Prompting in maintainer scripts must be done by communicating + through a program such as debconf which conforms to the Debian + Configuration management specification, version 2 or higher. + . + This check can have false positives if read is used in a block with a + redirection, in a function run in a pipe, or in other ways where + standard input is provided in inobvious ways. If this is the case, please + add an override for this tag. diff -Nru lintian-2.93.0/tags/r/read-in-maintainer-script.tag lintian-2.89.0ubuntu1/tags/r/read-in-maintainer-script.tag --- lintian-2.93.0/tags/r/read-in-maintainer-script.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/r/read-in-maintainer-script.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,13 +0,0 @@ -Tag: read-in-maintainer-script -Severity: error -Check: scripts -See-Also: policy 3.9.1 -Explanation: This maintainer script appears to use read to get information from - the user. Prompting in maintainer scripts must be done by communicating - through a program such as debconf which conforms to the Debian - Configuration management specification, version 2 or higher. - . - This check can have false positives if read is used in a block with a - redirection, in a function run in a pipe, or in other ways where - standard input is provided in inobvious ways. If this is the case, please - add an override for this tag. diff -Nru lintian-2.93.0/tags/r/readme-debian-contains-debmake-template.desc lintian-2.89.0ubuntu1/tags/r/readme-debian-contains-debmake-template.desc --- lintian-2.93.0/tags/r/readme-debian-contains-debmake-template.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/r/readme-debian-contains-debmake-template.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,14 @@ +Tag: readme-debian-contains-debmake-template +Severity: warning +Check: debian/readme +Info: The README.Debian file installed by this package contains one of the + template phrases from the README.Debian provided by deb-make or dh_make: + . + Comments regarding the package + So far nothing to say + <possible notes regarding this package - if none, delete this file> + Automatically generated by debmake + . + If there is real information in the file, please delete any generic + template phrases. If there is nothing to say in the file, it is best + removed. diff -Nru lintian-2.93.0/tags/r/readme-debian-contains-debmake-template.tag lintian-2.89.0ubuntu1/tags/r/readme-debian-contains-debmake-template.tag --- lintian-2.93.0/tags/r/readme-debian-contains-debmake-template.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/r/readme-debian-contains-debmake-template.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,14 +0,0 @@ -Tag: readme-debian-contains-debmake-template -Severity: warning -Check: debian/readme -Explanation: The README.Debian file installed by this package contains one of the - template phrases from the README.Debian provided by deb-make or dh_make: - . - Comments regarding the package - So far nothing to say - <possible notes regarding this package - if none, delete this file> - Automatically generated by debmake - . - If there is real information in the file, please delete any generic - template phrases. If there is nothing to say in the file, it is best - removed. diff -Nru lintian-2.93.0/tags/r/readme-debian-contains-invalid-email-address.desc lintian-2.89.0ubuntu1/tags/r/readme-debian-contains-invalid-email-address.desc --- lintian-2.93.0/tags/r/readme-debian-contains-invalid-email-address.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/r/readme-debian-contains-invalid-email-address.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,5 @@ +Tag: readme-debian-contains-invalid-email-address +Severity: warning +Check: debian/readme +Info: The README.Debian file contains an invalid email address: the domain + needs at least one dot. This looks like a mistake. diff -Nru lintian-2.93.0/tags/r/readme-debian-contains-invalid-email-address.tag lintian-2.89.0ubuntu1/tags/r/readme-debian-contains-invalid-email-address.tag --- lintian-2.93.0/tags/r/readme-debian-contains-invalid-email-address.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/r/readme-debian-contains-invalid-email-address.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,5 +0,0 @@ -Tag: readme-debian-contains-invalid-email-address -Severity: warning -Check: debian/readme -Explanation: The README.Debian file contains an invalid email address: the domain - needs at least one dot. This looks like a mistake. diff -Nru lintian-2.93.0/tags/r/readme-debian-mentions-usr-doc.desc lintian-2.89.0ubuntu1/tags/r/readme-debian-mentions-usr-doc.desc --- lintian-2.93.0/tags/r/readme-debian-mentions-usr-doc.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/r/readme-debian-mentions-usr-doc.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: readme-debian-mentions-usr-doc +Severity: warning +Certainty: possible +Check: debian/readme +Info: The README.Debian file installed by this package apparently points + users at /usr/doc. /usr/doc has been retired and all documentation + migrated to /usr/share/doc. This reference should probably also be + updated. diff -Nru lintian-2.93.0/tags/r/readme-debian-mentions-usr-doc.tag lintian-2.89.0ubuntu1/tags/r/readme-debian-mentions-usr-doc.tag --- lintian-2.93.0/tags/r/readme-debian-mentions-usr-doc.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/r/readme-debian-mentions-usr-doc.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: readme-debian-mentions-usr-doc -Severity: warning -Check: debian/readme -Explanation: The README.Debian file installed by this package apparently points - users at /usr/doc. /usr/doc has been retired and all documentation - migrated to /usr/share/doc. This reference should probably also be - updated. diff -Nru lintian-2.93.0/tags/r/readme-source-is-dh_make-template.desc lintian-2.89.0ubuntu1/tags/r/readme-source-is-dh_make-template.desc --- lintian-2.93.0/tags/r/readme-source-is-dh_make-template.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/r/readme-source-is-dh_make-template.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: readme-source-is-dh_make-template +Severity: error +Check: cruft +Info: The debian/README.source file appears to be an unmodified or insufficiently + modified copy of the dh_make template. + . + Please double-check the README.source page and replace it with information + about this source package or simply remove the file completely. diff -Nru lintian-2.93.0/tags/r/readme-source-is-dh_make-template.tag lintian-2.89.0ubuntu1/tags/r/readme-source-is-dh_make-template.tag --- lintian-2.93.0/tags/r/readme-source-is-dh_make-template.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/r/readme-source-is-dh_make-template.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: readme-source-is-dh_make-template -Severity: error -Check: cruft -Explanation: The debian/README.source file appears to be an unmodified or insufficiently - modified copy of the dh_make template. - . - Please double-check the README.source page and replace it with information - about this source package or simply remove the file completely. diff -Nru lintian-2.93.0/tags/r/recommended-field.desc lintian-2.89.0ubuntu1/tags/r/recommended-field.desc --- lintian-2.93.0/tags/r/recommended-field.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/r/recommended-field.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,13 @@ +Tag: recommended-field +Severity: warning +Check: fields/recommended +Renamed-From: + no-priority-field + no-section-field-for-source + no-section-field + no-urgency-in-changes-file +Info: The named field is recommended by policy but not present in the + package's primary control file. +Ref: policy 5.2, + policy 5.3, + policy 5.5 diff -Nru lintian-2.93.0/tags/r/recommended-field.tag lintian-2.89.0ubuntu1/tags/r/recommended-field.tag --- lintian-2.93.0/tags/r/recommended-field.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/r/recommended-field.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,13 +0,0 @@ -Tag: recommended-field -Severity: warning -Check: fields/recommended -Renamed-From: - no-priority-field - no-section-field-for-source - no-section-field - no-urgency-in-changes-file -Explanation: The named field is recommended by policy but not present in the - package's primary control file. -See-Also: policy 5.2, - policy 5.3, - policy 5.5 diff -Nru lintian-2.93.0/tags/r/recursive-privilege-change.desc lintian-2.89.0ubuntu1/tags/r/recursive-privilege-change.desc --- lintian-2.93.0/tags/r/recursive-privilege-change.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/r/recursive-privilege-change.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,27 @@ +Tag: recursive-privilege-change +Severity: warning +Check: scripts +Renamed-From: maintainer-script-should-not-use-recursive-chown-or-chmod +Info: The named maintainer script appears to call chmod or + chown with a --recursive/-R argument, or + it uses find(1) with similar intent. + . + All such uses are vulnerable to hardlink attacks on mainline (i.e. + non-Debian) kernels that do not set fs.protected_hardlinks=1. + . + The security risk arises when when a non-privileged user set links + to files they do not own, such as such as /etc/shadow or + files in /var/lib/dpkg/. A superuser's recursive call to + chown or chmod on behalf of a role user account + would then modify the non-owned files in ways that allow the + non-privileged user to manipulate them later. + . + There are several ways to mitigate the issue in maintainer scripts: + . + - For a static role user, please call chown at build time + and not during the installation. + - If that is too complicated, use runuser(1) in the + relevant build parts to create files with correct ownership. + - Given a static list of files to change, use non-recursive calls + for each file. (Please do not generate the list with find.) +Ref: Bug#895597, Bug#889060, Bug#889488, runuser(1) diff -Nru lintian-2.93.0/tags/r/recursive-privilege-change.tag lintian-2.89.0ubuntu1/tags/r/recursive-privilege-change.tag --- lintian-2.93.0/tags/r/recursive-privilege-change.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/r/recursive-privilege-change.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,27 +0,0 @@ -Tag: recursive-privilege-change -Severity: warning -Check: scripts -Renamed-From: maintainer-script-should-not-use-recursive-chown-or-chmod -Explanation: The named maintainer script appears to call chmod or - chown with a --recursive/-R argument, or - it uses find(1) with similar intent. - . - All such uses are vulnerable to hardlink attacks on mainline (i.e. - non-Debian) kernels that do not set fs.protected_hardlinks=1. - . - The security risk arises when when a non-privileged user set links - to files they do not own, such as such as /etc/shadow or - files in /var/lib/dpkg/. A superuser's recursive call to - chown or chmod on behalf of a role user account - would then modify the non-owned files in ways that allow the - non-privileged user to manipulate them later. - . - There are several ways to mitigate the issue in maintainer scripts: - . - - For a static role user, please call chown at build time - and not during the installation. - - If that is too complicated, use runuser(1) in the - relevant build parts to create files with correct ownership. - - Given a static list of files to change, use non-recursive calls - for each file. (Please do not generate the list with find.) -See-Also: Bug#895597, Bug#889060, Bug#889488, runuser(1) diff -Nru lintian-2.93.0/tags/r/redundant-bugs-field.desc lintian-2.89.0ubuntu1/tags/r/redundant-bugs-field.desc --- lintian-2.93.0/tags/r/redundant-bugs-field.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/r/redundant-bugs-field.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: redundant-bugs-field +Severity: warning +Check: fields/bugs +Info: You use the Bugs field though the field value is the default + (debbugs://bugs.debian.org/). In this case the field is redundant and + should be removed. diff -Nru lintian-2.93.0/tags/r/redundant-bugs-field.tag lintian-2.89.0ubuntu1/tags/r/redundant-bugs-field.tag --- lintian-2.93.0/tags/r/redundant-bugs-field.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/r/redundant-bugs-field.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: redundant-bugs-field -Severity: warning -Check: fields/bugs -Explanation: You use the Bugs field though the field value is the default - (debbugs://bugs.debian.org/). In this case the field is redundant and - should be removed. diff -Nru lintian-2.93.0/tags/r/redundant-globbing-patterns.desc lintian-2.89.0ubuntu1/tags/r/redundant-globbing-patterns.desc --- lintian-2.93.0/tags/r/redundant-globbing-patterns.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/r/redundant-globbing-patterns.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,12 @@ +Tag: redundant-globbing-patterns +Severity: error +Check: debian/copyright/dep5 +Info: Two globbing patterns in the same Files section in + debian/copyright match the same file. + . + This situation can occur when a narrow pattern should apply the same license + as a broader pattern. Please create another Files section for the + narrow pattern and place it below other patterns that compete for the same + files. +Ref: Bug#905747, + https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ diff -Nru lintian-2.93.0/tags/r/redundant-globbing-patterns.tag lintian-2.89.0ubuntu1/tags/r/redundant-globbing-patterns.tag --- lintian-2.93.0/tags/r/redundant-globbing-patterns.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/r/redundant-globbing-patterns.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,12 +0,0 @@ -Tag: redundant-globbing-patterns -Severity: pedantic -Check: debian/copyright/dep5 -Explanation: Two globbing patterns in the same Files section in - debian/copyright match the same file. - . - This situation can occur when a narrow pattern should apply the same license - as a broader pattern. Please create another Files section for the - narrow pattern and place it below other patterns that compete for the same - files. -See-Also: Bug#905747, - https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ diff -Nru lintian-2.93.0/tags/r/redundant-origin-field.desc lintian-2.89.0ubuntu1/tags/r/redundant-origin-field.desc --- lintian-2.93.0/tags/r/redundant-origin-field.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/r/redundant-origin-field.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,5 @@ +Tag: redundant-origin-field +Severity: warning +Check: fields/origin +Info: You use the Origin field though the field value is the default (Debian). + In this case the field is redundant and should be removed. diff -Nru lintian-2.93.0/tags/r/redundant-origin-field.tag lintian-2.89.0ubuntu1/tags/r/redundant-origin-field.tag --- lintian-2.93.0/tags/r/redundant-origin-field.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/r/redundant-origin-field.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,5 +0,0 @@ -Tag: redundant-origin-field -Severity: warning -Check: fields/origin -Explanation: You use the Origin field though the field value is the default (Debian). - In this case the field is redundant and should be removed. diff -Nru lintian-2.93.0/tags/r/relative-conffile.desc lintian-2.89.0ubuntu1/tags/r/relative-conffile.desc --- lintian-2.93.0/tags/r/relative-conffile.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/r/relative-conffile.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: relative-conffile +Severity: error +Check: conffiles +Ref: policy 5.1* +Info: All entries in the debian/conffiles control file should + have an absolute path specification. diff -Nru lintian-2.93.0/tags/r/relative-conffile.tag lintian-2.89.0ubuntu1/tags/r/relative-conffile.tag --- lintian-2.93.0/tags/r/relative-conffile.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/r/relative-conffile.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: relative-conffile -Severity: error -Check: conffiles -See-Also: policy 5.1* -Explanation: All entries in the debian/conffiles control file should - have an absolute path specification. diff -Nru lintian-2.93.0/tags/r/relative-symlink.desc lintian-2.89.0ubuntu1/tags/r/relative-symlink.desc --- lintian-2.93.0/tags/r/relative-symlink.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/r/relative-symlink.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: relative-symlink +Severity: error +Check: files/symbolic-links +Renamed-From: symlink-should-be-absolute +Info: Symbolic links between different top-level directories should be + absolute. + . + If you use debhelper, running dh_link after creating the package structure + will fix this problem for you. +Ref: policy 10.5 diff -Nru lintian-2.93.0/tags/r/relative-symlink.tag lintian-2.89.0ubuntu1/tags/r/relative-symlink.tag --- lintian-2.93.0/tags/r/relative-symlink.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/r/relative-symlink.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,10 +0,0 @@ -Tag: relative-symlink -Severity: error -Check: files/symbolic-links -Renamed-From: symlink-should-be-absolute -Explanation: Symbolic links between different top-level directories should be - absolute. - . - If you use debhelper, running dh_link after creating the package structure - will fix this problem for you. -See-Also: policy 10.5 diff -Nru lintian-2.93.0/tags/r/remove-of-unknown-diversion.desc lintian-2.89.0ubuntu1/tags/r/remove-of-unknown-diversion.desc --- lintian-2.93.0/tags/r/remove-of-unknown-diversion.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/r/remove-of-unknown-diversion.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: remove-of-unknown-diversion +Severity: error +Check: scripts +Info: The maintainer script removes a diversion that it didn't add. If + you're cleaning up unnecessary diversions from older versions of the + package, remove them in preinst or postinst instead of + waiting for postrm to do it. diff -Nru lintian-2.93.0/tags/r/remove-of-unknown-diversion.tag lintian-2.89.0ubuntu1/tags/r/remove-of-unknown-diversion.tag --- lintian-2.93.0/tags/r/remove-of-unknown-diversion.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/r/remove-of-unknown-diversion.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: remove-of-unknown-diversion -Severity: error -Check: scripts -Explanation: The maintainer script removes a diversion that it didn't add. If - you're cleaning up unnecessary diversions from older versions of the - package, remove them in preinst or postinst instead of - waiting for postrm to do it. diff -Nru lintian-2.93.0/tags/r/renamed-tag.desc lintian-2.89.0ubuntu1/tags/r/renamed-tag.desc --- lintian-2.93.0/tags/r/renamed-tag.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/r/renamed-tag.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: renamed-tag +Severity: pedantic +Check: lintian +Info: The package has an override for a tag that was renamed. + Lintian tag are sometime renamed in order to improve their name. + . + Override file is dynamically translated by Lintian. Nevertheless + please replace the old name by the new name. diff -Nru lintian-2.93.0/tags/r/renamed-tag.tag lintian-2.89.0ubuntu1/tags/r/renamed-tag.tag --- lintian-2.93.0/tags/r/renamed-tag.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/r/renamed-tag.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: renamed-tag -Severity: pedantic -Check: lintian -Explanation: The package has an override for a tag that was renamed. - Lintian tag are sometime renamed in order to improve their name. - . - Override file is dynamically translated by Lintian. Nevertheless - please replace the old name by the new name. diff -Nru lintian-2.93.0/tags/r/repackaged-source-not-advertised.desc lintian-2.89.0ubuntu1/tags/r/repackaged-source-not-advertised.desc --- lintian-2.93.0/tags/r/repackaged-source-not-advertised.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/r/repackaged-source-not-advertised.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,26 @@ +Tag: repackaged-source-not-advertised +Severity: info +Check: debian/copyright/dep5 +Info: The debian/copyright file mentions Files-Excluded + but the source version has no repack suffix. + . + Repackaged sources are expected to indicate in their version number + that they are different from the upstream release. It is commonly + done by adding a repack suffix to the upstream version. + . + The choice of repack suffix depends on the reason for repackaging. + When some files were excluded because licensing was a concern, the + suffix +dfsg may be appropriate. In more generic cases, one + could chose +ds. + . + Upstream sources are sometimes repackaged by accident when using old + versions of dh_make. It can also happen when a maintainer + invokes the dh_make option --createorig even though it is + not needed. + . + According to the Debian Developer's Reference 6.7.8.2, the repack + suffix is not required. + . + Please include such a suffix in the changelog version number to avoid + this warning. +Ref: #471537, https://www.debian.org/doc/manuals/developers-reference/best-pkging-practices.html diff -Nru lintian-2.93.0/tags/r/repackaged-source-not-advertised.tag lintian-2.89.0ubuntu1/tags/r/repackaged-source-not-advertised.tag --- lintian-2.93.0/tags/r/repackaged-source-not-advertised.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/r/repackaged-source-not-advertised.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,26 +0,0 @@ -Tag: repackaged-source-not-advertised -Severity: info -Check: debian/copyright/dep5 -Explanation: The debian/copyright file mentions Files-Excluded - but the source version has no repack suffix. - . - Repackaged sources are expected to indicate in their version number - that they are different from the upstream release. It is commonly - done by adding a repack suffix to the upstream version. - . - The choice of repack suffix depends on the reason for repackaging. - When some files were excluded because licensing was a concern, the - suffix +dfsg may be appropriate. In more generic cases, one - could chose +ds. - . - Upstream sources are sometimes repackaged by accident when using old - versions of dh_make. It can also happen when a maintainer - invokes the dh_make option --createorig even though it is - not needed. - . - According to the Debian Developer's Reference 6.7.8.2, the repack - suffix is not required. - . - Please include such a suffix in the changelog version number to avoid - this warning. -See-Also: Bug#471537, https://www.debian.org/doc/manuals/developers-reference/best-pkging-practices.html diff -Nru lintian-2.93.0/tags/r/repeated-path-segment.desc lintian-2.89.0ubuntu1/tags/r/repeated-path-segment.desc --- lintian-2.93.0/tags/r/repeated-path-segment.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/r/repeated-path-segment.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: repeated-path-segment +Severity: pedantic +Check: files/hierarchy/path-segments +Info: The file is installed into a location that repeats the given + path segment. An example would be /usr/lib/lib or + /usr/share/myprogram/share. + . + More often than not this is unintended. +Ref: Bug#950052, Bug#950027 diff -Nru lintian-2.93.0/tags/r/repeated-path-segment.tag lintian-2.89.0ubuntu1/tags/r/repeated-path-segment.tag --- lintian-2.93.0/tags/r/repeated-path-segment.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/r/repeated-path-segment.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: repeated-path-segment -Severity: pedantic -Check: files/hierarchy/path-segments -Explanation: The file is installed into a location that repeats the given - path segment. An example would be /usr/lib/lib or - /usr/share/myprogram/share. - . - More often than not this is unintended. -See-Also: Bug#950052, Bug#950027 diff -Nru lintian-2.93.0/tags/r/repeated-trigger-name.desc lintian-2.89.0ubuntu1/tags/r/repeated-trigger-name.desc --- lintian-2.93.0/tags/r/repeated-trigger-name.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/r/repeated-trigger-name.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,18 @@ +Tag: repeated-trigger-name +Severity: error +Check: triggers +Info: The package repeats the same trigger. There should be no reason to + do this and it may lead to confusing results or errors. + . + For the same "base" type of trigger (e.g. two interest-type triggers) + the last declaration will be the effective one. + . + This tag is also triggered if the package has an activate trigger + for something on which it also declares an interest. The only (but + rather unlikely) reason to do this is if another package also + declares an interest and this package needs to activate that + other package. If the package is using it for this exact purpose, then + please use a Lintian override to state this. + . + Please remove any duplicate definitions. +Ref: deb-triggers(5), #698723 diff -Nru lintian-2.93.0/tags/r/repeated-trigger-name.tag lintian-2.89.0ubuntu1/tags/r/repeated-trigger-name.tag --- lintian-2.93.0/tags/r/repeated-trigger-name.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/r/repeated-trigger-name.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,18 +0,0 @@ -Tag: repeated-trigger-name -Severity: error -Check: triggers -Explanation: The package repeats the same trigger. There should be no reason to - do this and it may lead to confusing results or errors. - . - For the same "base" type of trigger (e.g. two interest-type triggers) - the last declaration will be the effective one. - . - This tag is also triggered if the package has an activate trigger - for something on which it also declares an interest. The only (but - rather unlikely) reason to do this is if another package *also* - declares an interest and this package needs to activate that - other package. If the package is using it for this exact purpose, then - please use a Lintian override to state this. - . - Please remove any duplicate definitions. -See-Also: deb-triggers(5), Bug#698723 diff -Nru lintian-2.93.0/tags/r/required-field.desc lintian-2.89.0ubuntu1/tags/r/required-field.desc --- lintian-2.93.0/tags/r/required-field.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/r/required-field.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,16 @@ +Tag: required-field +Severity: error +Check: fields/required +Renamed-From: + no-maintainer-field + no-architecture-field + no-description-in-changes-file + no-package-name + no-standards-version-field + no-version-field + package-has-no-description +Info: The named field is required by policy but not present in the + package's primary control file. +Ref: policy 5.3, + policy 5.5, + policy 5.6.11 diff -Nru lintian-2.93.0/tags/r/required-field.tag lintian-2.89.0ubuntu1/tags/r/required-field.tag --- lintian-2.93.0/tags/r/required-field.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/r/required-field.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,16 +0,0 @@ -Tag: required-field -Severity: error -Check: fields/required -Renamed-From: - no-maintainer-field - no-architecture-field - no-description-in-changes-file - no-package-name - no-standards-version-field - no-version-field - package-has-no-description -Explanation: The named field is required by policy but not present in the - package's primary control file. -See-Also: policy 5.3, - policy 5.5, - policy 5.6.11 diff -Nru lintian-2.93.0/tags/r/requires-r-api.desc lintian-2.89.0ubuntu1/tags/r/requires-r-api.desc --- lintian-2.93.0/tags/r/requires-r-api.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/r/requires-r-api.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,13 @@ +Tag: requires-r-api +Severity: error +Check: languages/r/site-library +Info: This package ships a site library for the R + programming language package but does not declare the + R API r-api-N as a package + prerequisite. + . + With the dh sequencer, please use --buildsystem=R in + debian/rules and add the substitution variable + ${R:Depends} to the Depends field in + debian/control. +Ref: https://wiki.debian.org/Teams/r-pkg-team diff -Nru lintian-2.93.0/tags/r/requires-r-api.tag lintian-2.89.0ubuntu1/tags/r/requires-r-api.tag --- lintian-2.93.0/tags/r/requires-r-api.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/r/requires-r-api.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,13 +0,0 @@ -Tag: requires-r-api -Severity: error -Check: languages/r/site-library -Explanation: This package ships a site library for the R - programming language package but does not declare the - R API r-api-*N* as a package - prerequisite. - . - With the dh sequencer, please use --buildsystem=R in - debian/rules and add the substitution variable - ${R:Depends} to the Depends field in - debian/control. -See-Also: https://wiki.debian.org/Teams/r-pkg-team diff -Nru lintian-2.93.0/tags/r/root-in-contact.desc lintian-2.89.0ubuntu1/tags/r/root-in-contact.desc --- lintian-2.93.0/tags/r/root-in-contact.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/r/root-in-contact.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,11 @@ +Tag: root-in-contact +Severity: error +Check: fields/mail-address +Renamed-From: + maintainer-address-is-root-user + uploader-address-is-root-user + changed-by-address-is-root-user +Info: The named contact includes root as a name or as part of + the mail address, which is invalid. + . + The package may not have been built in a sane environment. diff -Nru lintian-2.93.0/tags/r/root-in-contact.tag lintian-2.89.0ubuntu1/tags/r/root-in-contact.tag --- lintian-2.93.0/tags/r/root-in-contact.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/r/root-in-contact.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,11 +0,0 @@ -Tag: root-in-contact -Severity: error -Check: fields/mail-address -Renamed-From: - maintainer-address-is-root-user - uploader-address-is-root-user - changed-by-address-is-root-user -Explanation: The named contact includes root as a name or as part of - the mail address, which is invalid. - . - The package may not have been built in a sane environment. diff -Nru lintian-2.93.0/tags/r/r-package-not-arch-all.desc lintian-2.89.0ubuntu1/tags/r/r-package-not-arch-all.desc --- lintian-2.93.0/tags/r/r-package-not-arch-all.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/r/r-package-not-arch-all.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: r-package-not-arch-all +Severity: warning +Check: fields/architecture +Info: The package for an R language package ships a + DESCRIPTION file that states NeedsCompilation: No + but is not marked Architecture: all. + . + The package does not require compilation and should be + architecture-independent. +Ref: https://cran.r-project.org/doc/manuals/r-devel/R-exts.html diff -Nru lintian-2.93.0/tags/r/r-package-not-arch-all.tag lintian-2.89.0ubuntu1/tags/r/r-package-not-arch-all.tag --- lintian-2.93.0/tags/r/r-package-not-arch-all.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/r/r-package-not-arch-all.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,10 +0,0 @@ -Tag: r-package-not-arch-all -Severity: warning -Check: fields/architecture -Explanation: The package for an R language package ships a - DESCRIPTION file that states NeedsCompilation: No - but is not marked Architecture: all. - . - The package does not require compilation and should be - architecture-independent. -See-Also: https://cran.r-project.org/doc/manuals/r-devel/R-exts.html diff -Nru lintian-2.93.0/tags/r/ruby-script-but-no-ruby-dep.desc lintian-2.89.0ubuntu1/tags/r/ruby-script-but-no-ruby-dep.desc --- lintian-2.93.0/tags/r/ruby-script-but-no-ruby-dep.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/r/ruby-script-but-no-ruby-dep.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,18 @@ +Tag: ruby-script-but-no-ruby-dep +Severity: error +Check: scripts +Info: Packages with Ruby scripts must depend on a valid Ruby interpreter. + Those that have Ruby scripts that run under a specific version of Ruby need a + dependency on the equivalent version of Ruby. + . + If a script in the package uses #!/usr/bin/ruby, the package needs a + dependency on "ruby | ruby-interpreter". This allows users to choose which + interpreter to use by default. If the package is intended to be used with a + specific Ruby version, its scripts should use that version directly, such + as #!/usr/bin/ruby1.8 + . + If a script uses #!/usr/bin/ruby1.9, then the package needs a + dependency on "ruby1.9". + . + In some cases a weaker relationship, such as Suggests or Recommends, will + be more appropriate. diff -Nru lintian-2.93.0/tags/r/ruby-script-but-no-ruby-dep.tag lintian-2.89.0ubuntu1/tags/r/ruby-script-but-no-ruby-dep.tag --- lintian-2.93.0/tags/r/ruby-script-but-no-ruby-dep.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/r/ruby-script-but-no-ruby-dep.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,18 +0,0 @@ -Tag: ruby-script-but-no-ruby-dep -Severity: error -Check: scripts -Explanation: Packages with Ruby scripts must depend on a valid Ruby interpreter. - Those that have Ruby scripts that run under a specific version of Ruby need a - dependency on the equivalent version of Ruby. - . - If a script in the package uses #!/usr/bin/ruby, the package needs a - dependency on "ruby | ruby-interpreter". This allows users to choose which - interpreter to use by default. If the package is intended to be used with a - specific Ruby version, its scripts should use that version directly, such - as #!/usr/bin/ruby1.8 - . - If a script uses #!/usr/bin/ruby1.9, then the package needs a - dependency on "ruby1.9". - . - In some cases a weaker relationship, such as Suggests or Recommends, will - be more appropriate. diff -Nru lintian-2.93.0/tags/r/rules-does-not-require-root.desc lintian-2.89.0ubuntu1/tags/r/rules-does-not-require-root.desc --- lintian-2.93.0/tags/r/rules-does-not-require-root.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/r/rules-does-not-require-root.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,5 @@ +Tag: rules-does-not-require-root +Severity: classification +Check: debian/control +Info: Package supports building without fakeroot or similar +Ref: /usr/share/doc/dpkg-dev/rootless-builds.txt.gz, policy 4.9.2, policy 5.6.31 diff -Nru lintian-2.93.0/tags/r/rules-does-not-require-root.tag lintian-2.89.0ubuntu1/tags/r/rules-does-not-require-root.tag --- lintian-2.93.0/tags/r/rules-does-not-require-root.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/r/rules-does-not-require-root.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,5 +0,0 @@ -Tag: rules-does-not-require-root -Severity: classification -Check: debian/control -Explanation: Package supports building without fakeroot or similar -See-Also: /usr/share/doc/dpkg-dev/rootless-builds.txt.gz, policy 4.9.2, policy 5.6.31 diff -Nru lintian-2.93.0/tags/r/rules-requires-root-explicitly.desc lintian-2.89.0ubuntu1/tags/r/rules-requires-root-explicitly.desc --- lintian-2.93.0/tags/r/rules-requires-root-explicitly.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/r/rules-requires-root-explicitly.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,5 @@ +Tag: rules-requires-root-explicitly +Severity: classification +Check: debian/control +Info: Package requires fakeroot or similar to build binary targets and explicitly declares it. +Ref: /usr/share/doc/dpkg-dev/rootless-builds.txt.gz, policy 4.9.2, policy 5.6.31 diff -Nru lintian-2.93.0/tags/r/rules-requires-root-explicitly.tag lintian-2.89.0ubuntu1/tags/r/rules-requires-root-explicitly.tag --- lintian-2.93.0/tags/r/rules-requires-root-explicitly.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/r/rules-requires-root-explicitly.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,5 +0,0 @@ -Tag: rules-requires-root-explicitly -Severity: classification -Check: debian/control -Explanation: Package requires fakeroot or similar to build binary targets and explicitly declares it. -See-Also: /usr/share/doc/dpkg-dev/rootless-builds.txt.gz, policy 4.9.2, policy 5.6.31 diff -Nru lintian-2.93.0/tags/r/rules-silently-require-root.desc lintian-2.89.0ubuntu1/tags/r/rules-silently-require-root.desc --- lintian-2.93.0/tags/r/rules-silently-require-root.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/r/rules-silently-require-root.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,21 @@ +Tag: rules-silently-require-root +Severity: info +Check: debian/control +Renamed-From: + should-specify-rules-requires-root +Info: This package builds a binary package containing at least one path + with a UNIX ownership other than "root:root". It therefore requires + fakeroot(1) or similar to build its binary targets. + . + Traditionally, Debian packages have required root privileges for some + debian/rules target requiring a split between build and binary targets. + This makes the builds slower due to the increased amount of invocations + as well as the overhead of fakeroot itself. + . + By declaring when a package really does require root privileges the + default, archive-wide, behaviour can be switched, optimising packaging + build times in the common case. + . + Please specify (eg.) Rules-Requires-Root: binary-targets in + the debian/control source stanza. +Ref: /usr/share/doc/dpkg-dev/rootless-builds.txt.gz, policy 4.9.2, policy 5.6.31 diff -Nru lintian-2.93.0/tags/r/rules-silently-require-root.tag lintian-2.89.0ubuntu1/tags/r/rules-silently-require-root.tag --- lintian-2.93.0/tags/r/rules-silently-require-root.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/r/rules-silently-require-root.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,21 +0,0 @@ -Tag: rules-silently-require-root -Severity: info -Check: debian/control -Renamed-From: - should-specify-rules-requires-root -Explanation: This package builds a binary package containing at least one path - with a UNIX ownership other than "root:root". It therefore requires - fakeroot(1) or similar to build its binary targets. - . - Traditionally, Debian packages have required root privileges for some - debian/rules target requiring a split between build and binary targets. - This makes the builds slower due to the increased amount of invocations - as well as the overhead of fakeroot itself. - . - By declaring when a package really does require root privileges the - default, archive-wide, behaviour can be switched, optimising packaging - build times in the common case. - . - Please specify (eg.) Rules-Requires-Root: binary-targets in - the debian/control source stanza. -See-Also: /usr/share/doc/dpkg-dev/rootless-builds.txt.gz, policy 4.9.2, policy 5.6.31 diff -Nru lintian-2.93.0/tags/r/run-parts-cron-filename-contains-illegal-chars.desc lintian-2.89.0ubuntu1/tags/r/run-parts-cron-filename-contains-illegal-chars.desc --- lintian-2.93.0/tags/r/run-parts-cron-filename-contains-illegal-chars.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/r/run-parts-cron-filename-contains-illegal-chars.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: run-parts-cron-filename-contains-illegal-chars +Severity: warning +Check: cron +Info: The script in /etc/cron.<time-interval> will not be executed by + run-parts(8) because the filename contains a "." (full stop) or "+" (plus). + . + It is recommended to use "_" (underscores) instead of these symbols. +Ref: run-parts(8), policy 9.5.1 diff -Nru lintian-2.93.0/tags/r/run-parts-cron-filename-contains-illegal-chars.tag lintian-2.89.0ubuntu1/tags/r/run-parts-cron-filename-contains-illegal-chars.tag --- lintian-2.93.0/tags/r/run-parts-cron-filename-contains-illegal-chars.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/r/run-parts-cron-filename-contains-illegal-chars.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: run-parts-cron-filename-contains-illegal-chars -Severity: warning -Check: cron -Explanation: The script in /etc/cron.<time-interval> will not be executed by - run-parts(8) because the filename contains a "." (full stop) or "+" (plus). - . - It is recommended to use "_" (underscores) instead of these symbols. -See-Also: run-parts(8), policy 9.5.1 diff -Nru lintian-2.93.0/tags/r/runtime-test-file-is-not-a-regular-file.desc lintian-2.89.0ubuntu1/tags/r/runtime-test-file-is-not-a-regular-file.desc --- lintian-2.93.0/tags/r/runtime-test-file-is-not-a-regular-file.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/r/runtime-test-file-is-not-a-regular-file.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: runtime-test-file-is-not-a-regular-file +Severity: info +Check: testsuite +Info: A runtime test listed by debian/tests/control is not a regular + file or a relative symbolic link to a regular file in the source + package. +Ref: https://salsa.debian.org/ci-team/autopkgtest/tree/master/doc/README.package-tests.rst diff -Nru lintian-2.93.0/tags/r/runtime-test-file-is-not-a-regular-file.tag lintian-2.89.0ubuntu1/tags/r/runtime-test-file-is-not-a-regular-file.tag --- lintian-2.93.0/tags/r/runtime-test-file-is-not-a-regular-file.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/r/runtime-test-file-is-not-a-regular-file.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: runtime-test-file-is-not-a-regular-file -Severity: info -Check: testsuite -Explanation: A runtime test listed by debian/tests/control is not a regular - file or a relative symbolic link to a regular file in the source - package. -See-Also: https://salsa.debian.org/ci-team/autopkgtest/tree/master/doc/README.package-tests.rst diff -Nru lintian-2.93.0/tags/r/runtime-test-file-uses-installed-python-versions.desc lintian-2.89.0ubuntu1/tags/r/runtime-test-file-uses-installed-python-versions.desc --- lintian-2.93.0/tags/r/runtime-test-file-uses-installed-python-versions.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/r/runtime-test-file-uses-installed-python-versions.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,17 @@ +Tag: runtime-test-file-uses-installed-python-versions +Severity: warning +Check: testsuite +Info: The specified file appears to use py3versions -i + to determine the "installed" Python versions. + . + However, this can cause issues if a Python transition is in progress + as the -minimal variant of the previous version + (eg. python3.X-minimal) remains installed in many environments. + This variant then provides enough of an interpreter to count as being + "installed" but not enough for the tests themselves to succeed in most + cases. This then prevents the overall transition from taking place. + . + Please replace this will a call to all "supported" packages instead + (eg. py3versions -s and ensure python3-all is listed + in the test dependencies. +Ref: https://lists.debian.org/debian-devel/2020/03/msg00280.html diff -Nru lintian-2.93.0/tags/r/runtime-test-file-uses-installed-python-versions.tag lintian-2.89.0ubuntu1/tags/r/runtime-test-file-uses-installed-python-versions.tag --- lintian-2.93.0/tags/r/runtime-test-file-uses-installed-python-versions.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/r/runtime-test-file-uses-installed-python-versions.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,17 +0,0 @@ -Tag: runtime-test-file-uses-installed-python-versions -Severity: warning -Check: testsuite -Explanation: The specified file appears to use py3versions -i - to determine the "installed" Python versions. - . - However, this can cause issues if a Python transition is in progress - as the -minimal variant of the previous version - (eg. python3.X-minimal) remains installed in many environments. - This variant then provides enough of an interpreter to count as being - "installed" but not enough for the tests themselves to succeed in most - cases. This then prevents the overall transition from taking place. - . - Please replace this will a call to all "supported" packages instead - (eg. py3versions -s and ensure python3-all is listed - in the test dependencies. -See-Also: https://lists.debian.org/debian-devel/2020/03/msg00280.html diff -Nru lintian-2.93.0/tags/r/runtime-test-file-uses-supported-python-versions-without-python-all-build-depends.desc lintian-2.89.0ubuntu1/tags/r/runtime-test-file-uses-supported-python-versions-without-python-all-build-depends.desc --- lintian-2.93.0/tags/r/runtime-test-file-uses-supported-python-versions-without-python-all-build-depends.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/r/runtime-test-file-uses-supported-python-versions-without-python-all-build-depends.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,12 @@ +Tag: runtime-test-file-uses-supported-python-versions-without-python-all-build-depends +Severity: warning +Check: testsuite +Info: The specified file appears to use py3versions -s to + determine the "supported" Python versions without specifying + python3-all (or equivalent) as a build-dependency. + . + With only the default version of Python installed, the autopkgtests may + pass but the package subsequently faisl at runtime when another, + non-default, Python version is present. + . + Please add python3-all as a build-dependency. diff -Nru lintian-2.93.0/tags/r/runtime-test-file-uses-supported-python-versions-without-python-all-build-depends.tag lintian-2.89.0ubuntu1/tags/r/runtime-test-file-uses-supported-python-versions-without-python-all-build-depends.tag --- lintian-2.93.0/tags/r/runtime-test-file-uses-supported-python-versions-without-python-all-build-depends.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/r/runtime-test-file-uses-supported-python-versions-without-python-all-build-depends.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,12 +0,0 @@ -Tag: runtime-test-file-uses-supported-python-versions-without-python-all-build-depends -Severity: warning -Check: testsuite -Explanation: The specified file appears to use py3versions -s to - determine the "supported" Python versions without specifying - python3-all (or equivalent) as a build-dependency. - . - With only the default version of Python installed, the autopkgtests may - pass but the package subsequently faisl at runtime when another, - non-default, Python version is present. - . - Please add python3-all as a build-dependency. diff -Nru lintian-2.93.0/tags/s/script-in-etc-init.d-not-registered-via-update-rc.d.desc lintian-2.89.0ubuntu1/tags/s/script-in-etc-init.d-not-registered-via-update-rc.d.desc --- lintian-2.93.0/tags/s/script-in-etc-init.d-not-registered-via-update-rc.d.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/script-in-etc-init.d-not-registered-via-update-rc.d.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: script-in-etc-init.d-not-registered-via-update-rc.d +Severity: warning +Certainty: possible +Check: init.d +Info: The package installs an /etc/init.d script which is + not registered in the postinst script. This is usually a bug + (such as omitting the #DEBHELPER# token) unless you omit the links + intentionally for some reason or create the links some other way. diff -Nru lintian-2.93.0/tags/s/script-in-etc-init.d-not-registered-via-update-rc.d.tag lintian-2.89.0ubuntu1/tags/s/script-in-etc-init.d-not-registered-via-update-rc.d.tag --- lintian-2.93.0/tags/s/script-in-etc-init.d-not-registered-via-update-rc.d.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/script-in-etc-init.d-not-registered-via-update-rc.d.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: script-in-etc-init.d-not-registered-via-update-rc.d -Severity: warning -Check: init.d -Explanation: The package installs an /etc/init.d script which is - not registered in the postinst script. This is usually a bug - (such as omitting the #DEBHELPER# token) unless you omit the links - intentionally for some reason or create the links some other way. diff -Nru lintian-2.93.0/tags/s/script-in-usr-share-doc.desc lintian-2.89.0ubuntu1/tags/s/script-in-usr-share-doc.desc --- lintian-2.93.0/tags/s/script-in-usr-share-doc.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/script-in-usr-share-doc.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: script-in-usr-share-doc +Severity: info +Check: documentation +Info: Scripts are usually not documentation files, unless they are + examples, in which case they should be in the + /usr/share/doc/pkg/examples directory. diff -Nru lintian-2.93.0/tags/s/script-in-usr-share-doc.tag lintian-2.89.0ubuntu1/tags/s/script-in-usr-share-doc.tag --- lintian-2.93.0/tags/s/script-in-usr-share-doc.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/script-in-usr-share-doc.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: script-in-usr-share-doc -Severity: info -Check: documentation -Explanation: Scripts are usually not documentation files, unless they are - examples, in which case they should be in the - /usr/share/doc/*pkg*/examples directory. diff -Nru lintian-2.93.0/tags/s/script-not-executable.desc lintian-2.89.0ubuntu1/tags/s/script-not-executable.desc --- lintian-2.93.0/tags/s/script-not-executable.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/script-not-executable.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: script-not-executable +Severity: warning +Check: scripts +Info: This file starts with the #! sequence that marks interpreted scripts, + but it is not executable. + . + There has been some discussion to allow such files in paths other than + /usr/bin but there was ultimately no broad support for it. +Ref: Bug#368792 diff -Nru lintian-2.93.0/tags/s/script-not-executable.tag lintian-2.89.0ubuntu1/tags/s/script-not-executable.tag --- lintian-2.93.0/tags/s/script-not-executable.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/script-not-executable.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: script-not-executable -Severity: warning -Check: scripts -Explanation: This file starts with the #! sequence that marks interpreted scripts, - but it is not executable. - . - There has been some discussion to allow such files in paths other than - /usr/bin but there was ultimately no broad support for it. -See-Also: Bug#368792 diff -Nru lintian-2.93.0/tags/s/script-uses-bin-env.desc lintian-2.89.0ubuntu1/tags/s/script-uses-bin-env.desc --- lintian-2.93.0/tags/s/script-uses-bin-env.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/script-uses-bin-env.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: script-uses-bin-env +Severity: warning +Check: scripts +Info: This script uses /bin/env as its interpreter (used to find the + actual interpreter on the user's path). There is no /bin/env on Debian + systems; env is instead installed as /usr/bin/env. Usually, the path to + env in the script should be changed. diff -Nru lintian-2.93.0/tags/s/script-uses-bin-env.tag lintian-2.89.0ubuntu1/tags/s/script-uses-bin-env.tag --- lintian-2.93.0/tags/s/script-uses-bin-env.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/script-uses-bin-env.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: script-uses-bin-env -Severity: warning -Check: scripts -Explanation: This script uses /bin/env as its interpreter (used to find the - actual interpreter on the user's path). There is no /bin/env on Debian - systems; env is instead installed as /usr/bin/env. Usually, the path to - env in the script should be changed. diff -Nru lintian-2.93.0/tags/s/script-uses-deprecated-nodejs-location.desc lintian-2.89.0ubuntu1/tags/s/script-uses-deprecated-nodejs-location.desc --- lintian-2.93.0/tags/s/script-uses-deprecated-nodejs-location.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/script-uses-deprecated-nodejs-location.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,15 @@ +Tag: script-uses-deprecated-nodejs-location +Severity: warning +Certainty: possible +Check: scripts +Info: You used /usr/bin/nodejs or /usr/bin/env nodejs as an + interpreter for a script. + . + The /usr/bin/node binary was previously provided by + ax25-node and packages were required to use /usr/bin/nodejs + instead. ax25-node has since been removed from the archive and the + nodejs package now ships the /usr/bin/node binary to match + the rest of the Node.js ecosystem. + . + Please update your package to use the node variant. +Ref: #614907, #862051 diff -Nru lintian-2.93.0/tags/s/script-uses-deprecated-nodejs-location.tag lintian-2.89.0ubuntu1/tags/s/script-uses-deprecated-nodejs-location.tag --- lintian-2.93.0/tags/s/script-uses-deprecated-nodejs-location.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/script-uses-deprecated-nodejs-location.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,14 +0,0 @@ -Tag: script-uses-deprecated-nodejs-location -Severity: warning -Check: scripts -Explanation: You used /usr/bin/nodejs or /usr/bin/env nodejs as an - interpreter for a script. - . - The /usr/bin/node binary was previously provided by - ax25-node and packages were required to use /usr/bin/nodejs - instead. ax25-node has since been removed from the archive and the - nodejs package now ships the /usr/bin/node binary to match - the rest of the Node.js ecosystem. - . - Please update your package to use the node variant. -See-Also: Bug#614907, Bug#862051 diff -Nru lintian-2.93.0/tags/s/script-uses-perl4-libs-without-dep.desc lintian-2.89.0ubuntu1/tags/s/script-uses-perl4-libs-without-dep.desc --- lintian-2.93.0/tags/s/script-uses-perl4-libs-without-dep.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/script-uses-perl4-libs-without-dep.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: script-uses-perl4-libs-without-dep +Severity: warning +Certainty: possible +Check: scripts +Info: This package includes perl scripts using obsoleted perl 4-era + libraries. These libraries have been deprecated in perl in 5.14, and + are likely to be removed from the core in perl 5.16. Please either + remove references to these libraries, or add a dependency on + libperl4-corelibs-perl | perl (<< 5.12.3-7) to this package. diff -Nru lintian-2.93.0/tags/s/script-uses-perl4-libs-without-dep.tag lintian-2.89.0ubuntu1/tags/s/script-uses-perl4-libs-without-dep.tag --- lintian-2.93.0/tags/s/script-uses-perl4-libs-without-dep.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/script-uses-perl4-libs-without-dep.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: script-uses-perl4-libs-without-dep -Severity: warning -Check: scripts -Explanation: This package includes perl scripts using obsoleted perl 4-era - libraries. These libraries have been deprecated in perl in 5.14, and - are likely to be removed from the core in perl 5.16. Please either - remove references to these libraries, or add a dependency on - libperl4-corelibs-perl | perl (<< 5.12.3-7) to this package. diff -Nru lintian-2.93.0/tags/s/script-uses-unversioned-python-in-shebang.desc lintian-2.89.0ubuntu1/tags/s/script-uses-unversioned-python-in-shebang.desc --- lintian-2.93.0/tags/s/script-uses-unversioned-python-in-shebang.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/script-uses-unversioned-python-in-shebang.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,13 @@ +Tag: script-uses-unversioned-python-in-shebang +Severity: pedantic +Check: languages/python/scripts +Info: This package contains a script with unversioned Python shebang. + . + The 2.x series of Python is due for deprecation and will not be + maintained by upstream past 2020. As part of this, there is an on-going + discussion in Python community to recommend soft-linking python to + python3 on newer distributions. + . + If/when Debian starts following this recommendation, the specified + script will be broken. However, please do not update this script for + the time being. diff -Nru lintian-2.93.0/tags/s/script-uses-unversioned-python-in-shebang.tag lintian-2.89.0ubuntu1/tags/s/script-uses-unversioned-python-in-shebang.tag --- lintian-2.93.0/tags/s/script-uses-unversioned-python-in-shebang.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/script-uses-unversioned-python-in-shebang.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,13 +0,0 @@ -Tag: script-uses-unversioned-python-in-shebang -Severity: pedantic -Check: languages/python/scripts -Explanation: This package contains a script with unversioned Python shebang. - . - The 2.x series of Python is due for deprecation and will not be - maintained by upstream past 2020. As part of this, there is an on-going - discussion in Python community to recommend soft-linking python to - python3 on newer distributions. - . - If/when Debian starts following this recommendation, the specified - script will be broken. However, please do not update this script for - the time being. diff -Nru lintian-2.93.0/tags/s/script-with-language-extension.desc lintian-2.89.0ubuntu1/tags/s/script-with-language-extension.desc --- lintian-2.93.0/tags/s/script-with-language-extension.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/script-with-language-extension.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: script-with-language-extension +Severity: warning +Check: files/scripts +Info: When scripts are installed into a directory in the system PATH, the + script name should not include an extension such as .sh or + .pl that denotes the scripting language currently used to + implement it. The implementation language may change; if it does, + leaving the name the same would be confusing and changing it would be + disruptive. +Ref: policy 10.4 diff -Nru lintian-2.93.0/tags/s/script-with-language-extension.tag lintian-2.89.0ubuntu1/tags/s/script-with-language-extension.tag --- lintian-2.93.0/tags/s/script-with-language-extension.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/script-with-language-extension.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,10 +0,0 @@ -Tag: script-with-language-extension -Severity: warning -Check: files/scripts -Explanation: When scripts are installed into a directory in the system PATH, the - script name should not include an extension such as .sh or - .pl that denotes the scripting language currently used to - implement it. The implementation language may change; if it does, - leaving the name the same would be confusing and changing it would be - disruptive. -See-Also: policy 10.4 diff -Nru lintian-2.93.0/tags/s/script-without-interpreter.desc lintian-2.89.0ubuntu1/tags/s/script-without-interpreter.desc --- lintian-2.93.0/tags/s/script-without-interpreter.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/script-without-interpreter.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,5 @@ +Tag: script-without-interpreter +Severity: error +Check: scripts +Info: This file starts with the #! sequence that identifies scripts, but + it does not name an interpreter. diff -Nru lintian-2.93.0/tags/s/script-without-interpreter.tag lintian-2.89.0ubuntu1/tags/s/script-without-interpreter.tag --- lintian-2.93.0/tags/s/script-without-interpreter.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/script-without-interpreter.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,5 +0,0 @@ -Tag: script-without-interpreter -Severity: error -Check: scripts -Explanation: This file starts with the #! sequence that identifies scripts, but - it does not name an interpreter. diff -Nru lintian-2.93.0/tags/s/section-area-mismatch.desc lintian-2.89.0ubuntu1/tags/s/section-area-mismatch.desc --- lintian-2.93.0/tags/s/section-area-mismatch.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/section-area-mismatch.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: section-area-mismatch +Severity: error +Check: debian/control +Info: The debian/control file places the indicated binary package + in a different archive area (main, contrib, non-free) than its source + package or other binary packages built from the same source package. The + source package and any binary packages it builds must be in the same + area of the archive, with the single exception that source packages in + main may also build binary packages in contrib if they build binary + packages in main. diff -Nru lintian-2.93.0/tags/s/section-area-mismatch.tag lintian-2.89.0ubuntu1/tags/s/section-area-mismatch.tag --- lintian-2.93.0/tags/s/section-area-mismatch.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/section-area-mismatch.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,10 +0,0 @@ -Tag: section-area-mismatch -Severity: error -Check: debian/control -Explanation: The debian/control file places the indicated binary package - in a different archive area (main, contrib, non-free) than its source - package or other binary packages built from the same source package. The - source package and any binary packages it builds must be in the same - area of the archive, with the single exception that source packages in - main may also build binary packages in contrib if they build binary - packages in main. diff -Nru lintian-2.93.0/tags/s/section-is-dh_make-template.desc lintian-2.89.0ubuntu1/tags/s/section-is-dh_make-template.desc --- lintian-2.93.0/tags/s/section-is-dh_make-template.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/section-is-dh_make-template.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: section-is-dh_make-template +Severity: error +Check: fields/section +Info: The "Section:" field in this package's control file is set to + unknown. This is not a valid section, and usually means a dh_make + template control file was used and never modified to set the correct + section. +Ref: policy 2.4 diff -Nru lintian-2.93.0/tags/s/section-is-dh_make-template.tag lintian-2.89.0ubuntu1/tags/s/section-is-dh_make-template.tag --- lintian-2.93.0/tags/s/section-is-dh_make-template.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/section-is-dh_make-template.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: section-is-dh_make-template -Severity: error -Check: fields/section -Explanation: The "Section:" field in this package's control file is set to - unknown. This is not a valid section, and usually means a dh_make - template control file was used and never modified to set the correct - section. -See-Also: policy 2.4 diff -Nru lintian-2.93.0/tags/s/select-with-boolean-choices.desc lintian-2.89.0ubuntu1/tags/s/select-with-boolean-choices.desc --- lintian-2.93.0/tags/s/select-with-boolean-choices.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/select-with-boolean-choices.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: select-with-boolean-choices +Severity: warning +Certainty: possible +Check: debian/debconf +Info: Select templates with only yes and no choices should use the boolean + type instead. +Ref: debconf-devel(7) diff -Nru lintian-2.93.0/tags/s/select-with-boolean-choices.tag lintian-2.89.0ubuntu1/tags/s/select-with-boolean-choices.tag --- lintian-2.93.0/tags/s/select-with-boolean-choices.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/select-with-boolean-choices.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: select-with-boolean-choices -Severity: warning -Check: debian/debconf -Explanation: Select templates with only yes and no choices should use the boolean - type instead. -See-Also: debconf-devel(7) diff -Nru lintian-2.93.0/tags/s/select-without-choices.desc lintian-2.89.0ubuntu1/tags/s/select-without-choices.desc --- lintian-2.93.0/tags/s/select-without-choices.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/select-without-choices.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: select-without-choices +Severity: error +Check: debian/debconf +Info: Templates using the "select" or "multiselect" data types must provide + a "Choices:" field listing the possible values of the template. +Ref: debconf-spec 3.1, debconf-devel(7) diff -Nru lintian-2.93.0/tags/s/select-without-choices.tag lintian-2.89.0ubuntu1/tags/s/select-without-choices.tag --- lintian-2.93.0/tags/s/select-without-choices.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/select-without-choices.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: select-without-choices -Severity: error -Check: debian/debconf -Explanation: Templates using the "select" or "multiselect" data types must provide - a "Choices:" field listing the possible values of the template. -See-Also: debconf-spec 3.1, debconf-devel(7) diff -Nru lintian-2.93.0/tags/s/service-file-is-not-a-file.desc lintian-2.89.0ubuntu1/tags/s/service-file-is-not-a-file.desc --- lintian-2.93.0/tags/s/service-file-is-not-a-file.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/service-file-is-not-a-file.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,5 @@ +Tag: service-file-is-not-a-file +Severity: error +Check: systemd +Info: The package contains a service file that is not a regular file or + resolvable symlink. diff -Nru lintian-2.93.0/tags/s/service-file-is-not-a-file.tag lintian-2.89.0ubuntu1/tags/s/service-file-is-not-a-file.tag --- lintian-2.93.0/tags/s/service-file-is-not-a-file.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/service-file-is-not-a-file.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,5 +0,0 @@ -Tag: service-file-is-not-a-file -Severity: error -Check: systemd -Explanation: The package contains a service file that is not a regular file or - resolvable symlink. diff -Nru lintian-2.93.0/tags/s/setgid-binary.desc lintian-2.89.0ubuntu1/tags/s/setgid-binary.desc --- lintian-2.93.0/tags/s/setgid-binary.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/setgid-binary.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: setgid-binary +Severity: warning +Certainty: possible +Check: files/permissions +Info: The file is tagged SETGID. In some cases this is intentional, but in + other cases this is a bug. If this is intentional, please add a Lintian + override to document this fact. diff -Nru lintian-2.93.0/tags/s/setgid-binary.tag lintian-2.89.0ubuntu1/tags/s/setgid-binary.tag --- lintian-2.93.0/tags/s/setgid-binary.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/setgid-binary.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: setgid-binary -Severity: warning -Check: files/permissions -Explanation: The file is tagged SETGID. In some cases this is intentional, but in - other cases this is a bug. If this is intentional, please add a Lintian - override to document this fact. diff -Nru lintian-2.93.0/tags/s/setuid-binary.desc lintian-2.89.0ubuntu1/tags/s/setuid-binary.desc --- lintian-2.93.0/tags/s/setuid-binary.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/setuid-binary.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: setuid-binary +Severity: warning +Certainty: possible +Check: files/permissions +Info: The file is tagged SETUID. In some cases this is intentional, but in + other cases this is a bug. If this is intentional, please add a Lintian + override to document this fact. diff -Nru lintian-2.93.0/tags/s/setuid-binary.tag lintian-2.89.0ubuntu1/tags/s/setuid-binary.tag --- lintian-2.93.0/tags/s/setuid-binary.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/setuid-binary.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: setuid-binary -Severity: warning -Check: files/permissions -Explanation: The file is tagged SETUID. In some cases this is intentional, but in - other cases this is a bug. If this is intentional, please add a Lintian - override to document this fact. diff -Nru lintian-2.93.0/tags/s/setuid-gid-binary.desc lintian-2.89.0ubuntu1/tags/s/setuid-gid-binary.desc --- lintian-2.93.0/tags/s/setuid-gid-binary.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/setuid-gid-binary.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: setuid-gid-binary +Severity: warning +Certainty: possible +Check: files/permissions +Info: The file is tagged SETUID and SETGID. In some cases this is + intentional, but in other cases this is a bug. If this is intentional, + please add a Lintian override to document this fact. diff -Nru lintian-2.93.0/tags/s/setuid-gid-binary.tag lintian-2.89.0ubuntu1/tags/s/setuid-gid-binary.tag --- lintian-2.93.0/tags/s/setuid-gid-binary.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/setuid-gid-binary.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: setuid-gid-binary -Severity: warning -Check: files/permissions -Explanation: The file is tagged SETUID and SETGID. In some cases this is - intentional, but in other cases this is a bug. If this is intentional, - please add a Lintian override to document this fact. diff -Nru lintian-2.93.0/tags/s/shared-library-is-executable.desc lintian-2.89.0ubuntu1/tags/s/shared-library-is-executable.desc --- lintian-2.93.0/tags/s/shared-library-is-executable.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/shared-library-is-executable.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: shared-library-is-executable +Severity: error +Check: shared-libs +Renamed-From: shlib-with-executable-bit +Info: Shared libraries should be mode 0644. +Ref: policy 8.1 diff -Nru lintian-2.93.0/tags/s/shared-library-is-executable.tag lintian-2.89.0ubuntu1/tags/s/shared-library-is-executable.tag --- lintian-2.93.0/tags/s/shared-library-is-executable.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/shared-library-is-executable.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: shared-library-is-executable -Severity: error -Check: shared-libs -Renamed-From: shlib-with-executable-bit -Explanation: Shared libraries should be mode 0644. -See-Also: policy 8.1 diff -Nru lintian-2.93.0/tags/s/shared-library-is-multi-arch-foreign.desc lintian-2.89.0ubuntu1/tags/s/shared-library-is-multi-arch-foreign.desc --- lintian-2.93.0/tags/s/shared-library-is-multi-arch-foreign.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/shared-library-is-multi-arch-foreign.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: shared-library-is-multi-arch-foreign +Severity: error +Check: shared-libs +Renamed-From: shlib-in-multi-arch-foreign-package +Ref: https://wiki.ubuntu.com/MultiarchSpec +Info: The package is marked as Multi-Arch: foreign, but it includes a shared + library in a public library directory. diff -Nru lintian-2.93.0/tags/s/shared-library-is-multi-arch-foreign.tag lintian-2.89.0ubuntu1/tags/s/shared-library-is-multi-arch-foreign.tag --- lintian-2.93.0/tags/s/shared-library-is-multi-arch-foreign.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/shared-library-is-multi-arch-foreign.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: shared-library-is-multi-arch-foreign -Severity: error -Check: shared-libs -Renamed-From: shlib-in-multi-arch-foreign-package -See-Also: https://wiki.ubuntu.com/MultiarchSpec -Explanation: The package is marked as Multi-Arch: foreign, but it includes a shared - library in a public library directory. diff -Nru lintian-2.93.0/tags/s/shared-library-lacks-prerequisites.desc lintian-2.89.0ubuntu1/tags/s/shared-library-lacks-prerequisites.desc --- lintian-2.93.0/tags/s/shared-library-lacks-prerequisites.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/shared-library-lacks-prerequisites.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,12 @@ +Tag: shared-library-lacks-prerequisites +Severity: warning +Check: binaries +Renamed-From: shared-lib-without-dependency-information +Info: The listed shared library doesn't include information about the + other libraries against which it was linked. + . + More specifically, "ldd foo.so" should report such other + libraries. In your case, it reports "statically linked". + . + The fix is to specify the libraries. One way to do so is to add + something like "-lc" to the command-line options for "ld". diff -Nru lintian-2.93.0/tags/s/shared-library-lacks-prerequisites.tag lintian-2.89.0ubuntu1/tags/s/shared-library-lacks-prerequisites.tag --- lintian-2.93.0/tags/s/shared-library-lacks-prerequisites.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/shared-library-lacks-prerequisites.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,12 +0,0 @@ -Tag: shared-library-lacks-prerequisites -Severity: warning -Check: binaries -Renamed-From: shared-lib-without-dependency-information -Explanation: The listed shared library doesn't include information about the - other libraries against which it was linked. - . - More specifically, "ldd foo.so" should report such other - libraries. In your case, it reports "statically linked". - . - The fix is to specify the libraries. One way to do so is to add - something like "-lc" to the command-line options for "ld". diff -Nru lintian-2.93.0/tags/s/shared-library-lacks-stack-section.desc lintian-2.89.0ubuntu1/tags/s/shared-library-lacks-stack-section.desc --- lintian-2.93.0/tags/s/shared-library-lacks-stack-section.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/shared-library-lacks-stack-section.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,12 @@ +Tag: shared-library-lacks-stack-section +Severity: error +Check: shared-libs +Renamed-From: shlib-without-PT_GNU_STACK-section +Info: The listed shared library lacks a PT_GNU_STACK section. This forces + the dynamic linker to make the stack executable. + . + The shared lib is linked either with a non-GNU linker or a linker which is + very old. This problem can be fixed with a rebuild. + . + To see whether a shared library has this section, run readelf -l + on it and look for a program header of type GNU_STACK. diff -Nru lintian-2.93.0/tags/s/shared-library-lacks-stack-section.tag lintian-2.89.0ubuntu1/tags/s/shared-library-lacks-stack-section.tag --- lintian-2.93.0/tags/s/shared-library-lacks-stack-section.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/shared-library-lacks-stack-section.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,12 +0,0 @@ -Tag: shared-library-lacks-stack-section -Severity: error -Check: shared-libs -Renamed-From: shlib-without-PT_GNU_STACK-section -Explanation: The listed shared library lacks a PT_GNU_STACK section. This forces - the dynamic linker to make the stack executable. - . - The shared lib is linked either with a non-GNU linker or a linker which is - very old. This problem can be fixed with a rebuild. - . - To see whether a shared library has this section, run readelf -l - on it and look for a program header of type GNU_STACK. diff -Nru lintian-2.93.0/tags/s/shared-library-lacks-version.desc lintian-2.89.0ubuntu1/tags/s/shared-library-lacks-version.desc --- lintian-2.93.0/tags/s/shared-library-lacks-version.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/shared-library-lacks-version.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,24 @@ +Tag: shared-library-lacks-version +Severity: warning +Certainty: possible +Check: shared-libs +Renamed-From: shlib-without-versioned-soname +Ref: policy 10.2, policy 8.6 +Info: The listed shared library in a public library directory has an + SONAME that does not contain any versioning information, either after the + .so or before it and set off by a hyphen. It cannot therefore + be represented in the shlibs system, and if linked by binaries its + interface cannot safely change. There is no backward-compatible way to + migrate programs linked against it to a new ABI. + . + Normally, this means the shared library is a private library for a + particular application and is not meant for general use. Policy + recommends that such libraries be installed in a subdirectory of + /usr/lib rather than in a public shared library directory. + . + To view the SONAME of a shared library, run readelf -d on the + shared library and look for the tag of type SONAME. + . + There are some special stub libraries or special-purpose shared objects + for which an ABI version is not meaningful. If this is one of those + cases, please add an override. diff -Nru lintian-2.93.0/tags/s/shared-library-lacks-version.tag lintian-2.89.0ubuntu1/tags/s/shared-library-lacks-version.tag --- lintian-2.93.0/tags/s/shared-library-lacks-version.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/shared-library-lacks-version.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,23 +0,0 @@ -Tag: shared-library-lacks-version -Severity: warning -Check: shared-libs -Renamed-From: shlib-without-versioned-soname -See-Also: policy 10.2, policy 8.6 -Explanation: The listed shared library in a public library directory has an - SONAME that does not contain any versioning information, either after the - .so or before it and set off by a hyphen. It cannot therefore - be represented in the shlibs system, and if linked by binaries its - interface cannot safely change. There is no backward-compatible way to - migrate programs linked against it to a new ABI. - . - Normally, this means the shared library is a private library for a - particular application and is not meant for general use. Policy - recommends that such libraries be installed in a subdirectory of - /usr/lib rather than in a public shared library directory. - . - To view the SONAME of a shared library, run readelf -d on the - shared library and look for the tag of type SONAME. - . - There are some special stub libraries or special-purpose shared objects - for which an ABI version is not meaningful. If this is one of those - cases, please add an override. diff -Nru lintian-2.93.0/tags/s/shared-library-not-shipped.desc lintian-2.89.0ubuntu1/tags/s/shared-library-not-shipped.desc --- lintian-2.93.0/tags/s/shared-library-not-shipped.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/shared-library-not-shipped.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: shared-library-not-shipped +Severity: warning +Check: shared-libs +Renamed-From: unused-shlib-entry-in-control-file +Info: The shlibs control file contains an entry for a shared library that + is not installed by this package. +Ref: policy 8.6 diff -Nru lintian-2.93.0/tags/s/shared-library-not-shipped.tag lintian-2.89.0ubuntu1/tags/s/shared-library-not-shipped.tag --- lintian-2.93.0/tags/s/shared-library-not-shipped.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/shared-library-not-shipped.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: shared-library-not-shipped -Severity: warning -Check: shared-libs -Renamed-From: unused-shlib-entry-in-control-file -Explanation: The shlibs control file contains an entry for a shared library that - is not installed by this package. -See-Also: policy 8.6 diff -Nru lintian-2.93.0/tags/s/shared-library-symbols-not-tracked.desc lintian-2.89.0ubuntu1/tags/s/shared-library-symbols-not-tracked.desc --- lintian-2.93.0/tags/s/shared-library-symbols-not-tracked.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/shared-library-symbols-not-tracked.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: shared-library-symbols-not-tracked +Severity: warning +Certainty: possible +Check: shared-libs +Renamed-From: shlib-missing-in-symbols-control-file +Info: The package contains a shared library that is not listed in the + symbols control file. This may not be a problem if, for example, + the library is a C++ library. diff -Nru lintian-2.93.0/tags/s/shared-library-symbols-not-tracked.tag lintian-2.89.0ubuntu1/tags/s/shared-library-symbols-not-tracked.tag --- lintian-2.93.0/tags/s/shared-library-symbols-not-tracked.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/shared-library-symbols-not-tracked.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: shared-library-symbols-not-tracked -Severity: warning -Check: shared-libs -Renamed-From: shlib-missing-in-symbols-control-file -Explanation: The package contains a shared library that is not listed in the - symbols control file. This may not be a problem if, for example, - the library is a C++ library. diff -Nru lintian-2.93.0/tags/s/sharedobject-in-library-directory-missing-soname.desc lintian-2.89.0ubuntu1/tags/s/sharedobject-in-library-directory-missing-soname.desc --- lintian-2.93.0/tags/s/sharedobject-in-library-directory-missing-soname.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/sharedobject-in-library-directory-missing-soname.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,14 @@ +Tag: sharedobject-in-library-directory-missing-soname +Severity: error +Certainty: possible +Check: shared-libs +Info: A shared object was identified in a library directory (a directory + in the standard linker path) which doesn't have a SONAME. This is + usually an error. + . + SONAMEs are set with something like gcc -Wl,-soname,libfoo.so.0, + where 0 is the major version of the library. If your package uses libtool, + then libtool invoked with the right options should be doing this. + . + To view the SONAME of a shared library, run readelf -d on the + shared library and look for the tag of type SONAME. diff -Nru lintian-2.93.0/tags/s/sharedobject-in-library-directory-missing-soname.tag lintian-2.89.0ubuntu1/tags/s/sharedobject-in-library-directory-missing-soname.tag --- lintian-2.93.0/tags/s/sharedobject-in-library-directory-missing-soname.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/sharedobject-in-library-directory-missing-soname.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,13 +0,0 @@ -Tag: sharedobject-in-library-directory-missing-soname -Severity: error -Check: shared-libs -Explanation: A shared object was identified in a library directory (a directory - in the standard linker path) which doesn't have a SONAME. This is - usually an error. - . - SONAMEs are set with something like gcc -Wl,-soname,libfoo.so.0, - where 0 is the major version of the library. If your package uses libtool, - then libtool invoked with the right options should be doing this. - . - To view the SONAME of a shared library, run readelf -d on the - shared library and look for the tag of type SONAME. diff -Nru lintian-2.93.0/tags/s/shell-script-fails-syntax-check.desc lintian-2.89.0ubuntu1/tags/s/shell-script-fails-syntax-check.desc --- lintian-2.93.0/tags/s/shell-script-fails-syntax-check.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/shell-script-fails-syntax-check.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,13 @@ +Tag: shell-script-fails-syntax-check +Severity: error +Certainty: possible +Check: scripts +Info: Running this shell script with the shell's -n option set fails, + which means that the script has syntax errors. The most common cause of + this problem is a script expecting /bin/sh to be bash checked on + a system using dash as /bin/sh. + . + Run e.g. sh -n yourscript to see the errors yourself. + . + Note this can have false-positives, for an example with bash scripts + using "extglob". diff -Nru lintian-2.93.0/tags/s/shell-script-fails-syntax-check.tag lintian-2.89.0ubuntu1/tags/s/shell-script-fails-syntax-check.tag --- lintian-2.93.0/tags/s/shell-script-fails-syntax-check.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/shell-script-fails-syntax-check.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,12 +0,0 @@ -Tag: shell-script-fails-syntax-check -Severity: error -Check: scripts -Explanation: Running this shell script with the shell's -n option set fails, - which means that the script has syntax errors. The most common cause of - this problem is a script expecting /bin/sh to be bash checked on - a system using dash as /bin/sh. - . - Run e.g. sh -n yourscript to see the errors yourself. - . - Note this can have false-positives, for an example with bash scripts - using "extglob". diff -Nru lintian-2.93.0/tags/s/shipped-file-without-utf8-name.desc lintian-2.89.0ubuntu1/tags/s/shipped-file-without-utf8-name.desc --- lintian-2.93.0/tags/s/shipped-file-without-utf8-name.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/shipped-file-without-utf8-name.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,13 @@ +Tag: shipped-file-without-utf8-name +Severity: error +Check: files/names +Ref: policy 10.10 +Info: The file name in the installed tree is not valid UTF-8. + As a shipped file in an installation package, the name of this file is + considered the responsibility of the package maintainer. Please + rename the file. + . + Unlike other file names in Lintian, which are printed in UTF-8, the + attached reference shows the bytes used by the file system. + Unprintable characters may have been replaced. +Renamed-From: file-name-is-not-valid-UTF-8 diff -Nru lintian-2.93.0/tags/s/shipped-file-without-utf8-name.tag lintian-2.89.0ubuntu1/tags/s/shipped-file-without-utf8-name.tag --- lintian-2.93.0/tags/s/shipped-file-without-utf8-name.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/shipped-file-without-utf8-name.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,13 +0,0 @@ -Tag: shipped-file-without-utf8-name -Severity: error -Check: files/names -See-Also: policy 10.10 -Explanation: The file name in the installed tree is not valid UTF-8. - As a shipped file in an installation package, the name of this file is - considered the responsibility of the package maintainer. Please - rename the file. - . - Unlike other file names in Lintian, which are printed in UTF-8, the - attached reference shows the bytes used by the file system. - Unprintable characters may have been replaced. -Renamed-From: file-name-is-not-valid-UTF-8 diff -Nru lintian-2.93.0/tags/s/ships-r-site-library.desc lintian-2.89.0ubuntu1/tags/s/ships-r-site-library.desc --- lintian-2.93.0/tags/s/ships-r-site-library.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/ships-r-site-library.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: ships-r-site-library +Severity: classification +Check: languages/r/site-library +Info: This package ships the named R programming + language site library. +Ref: https://wiki.debian.org/Teams/r-pkg-team diff -Nru lintian-2.93.0/tags/s/ships-r-site-library.tag lintian-2.89.0ubuntu1/tags/s/ships-r-site-library.tag --- lintian-2.93.0/tags/s/ships-r-site-library.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/ships-r-site-library.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: ships-r-site-library -Severity: classification -Check: languages/r/site-library -Explanation: This package ships the named R programming - language site library. -See-Also: https://wiki.debian.org/Teams/r-pkg-team diff -Nru lintian-2.93.0/tags/s/ships-undeclared-shared-library.desc lintian-2.89.0ubuntu1/tags/s/ships-undeclared-shared-library.desc --- lintian-2.93.0/tags/s/ships-undeclared-shared-library.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/ships-undeclared-shared-library.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: ships-undeclared-shared-library +Severity: error +Certainty: possible +Check: shared-libs +Renamed-From: shlib-missing-in-control-file +Info: The package contains a shared library that is not listed in the + shlibs control file. If this is intentional, please override this error. +Ref: policy 8.6 diff -Nru lintian-2.93.0/tags/s/ships-undeclared-shared-library.tag lintian-2.89.0ubuntu1/tags/s/ships-undeclared-shared-library.tag --- lintian-2.93.0/tags/s/ships-undeclared-shared-library.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/ships-undeclared-shared-library.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: ships-undeclared-shared-library -Severity: error -Check: shared-libs -Renamed-From: shlib-missing-in-control-file -Explanation: The package contains a shared library that is not listed in the - shlibs control file. If this is intentional, please override this error. -See-Also: policy 8.6 diff -Nru lintian-2.93.0/tags/s/silent-on-rules-requiring-root.desc lintian-2.89.0ubuntu1/tags/s/silent-on-rules-requiring-root.desc --- lintian-2.93.0/tags/s/silent-on-rules-requiring-root.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/silent-on-rules-requiring-root.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,18 @@ +Tag: silent-on-rules-requiring-root +Severity: pedantic +Check: debian/control +Renamed-From: + rules-requires-root-missing +Info: The debian/control file is missing an explicit + Rules-Requires-Root field. + . + Traditionally, Debian packages have required root privileges for some + debian/rules target requiring a split between build and binary targets. + This makes the builds slower due to the increased amount of invocations + as well as the overhead of fakeroot itself. + . + Please specify (eg.) Rules-Requires-Root: no in the + debian/control source stanza, but packagers should + verify using diffoscope(1) that the binaries built with this + field present are identical. +Ref: /usr/share/doc/dpkg-dev/rootless-builds.txt.gz, policy 4.9.2, policy 5.6.31 diff -Nru lintian-2.93.0/tags/s/silent-on-rules-requiring-root.tag lintian-2.89.0ubuntu1/tags/s/silent-on-rules-requiring-root.tag --- lintian-2.93.0/tags/s/silent-on-rules-requiring-root.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/silent-on-rules-requiring-root.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,18 +0,0 @@ -Tag: silent-on-rules-requiring-root -Severity: pedantic -Check: debian/control -Renamed-From: - rules-requires-root-missing -Explanation: The debian/control file is missing an explicit - Rules-Requires-Root field. - . - Traditionally, Debian packages have required root privileges for some - debian/rules target requiring a split between build and binary targets. - This makes the builds slower due to the increased amount of invocations - as well as the overhead of fakeroot itself. - . - Please specify (eg.) Rules-Requires-Root: no in the - debian/control source stanza, but packagers should - verify using diffoscope(1) that the binaries built with this - field present are identical. -See-Also: /usr/share/doc/dpkg-dev/rootless-builds.txt.gz, policy 4.9.2, policy 5.6.31 diff -Nru lintian-2.93.0/tags/s/skip-systemd-native-flag-missing-pre-depends.desc lintian-2.89.0ubuntu1/tags/s/skip-systemd-native-flag-missing-pre-depends.desc --- lintian-2.93.0/tags/s/skip-systemd-native-flag-missing-pre-depends.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/skip-systemd-native-flag-missing-pre-depends.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,16 @@ +Tag: skip-systemd-native-flag-missing-pre-depends +Severity: warning +Certainty: possible +Check: scripts +Ref: invoke-rc.d(8), deb-systemd-invoke(1p) +Info: This package uses the --skip-systemd-native + invoke-rc.d flag in the specified maintainer script but does + not specify a Pre-Depends dependency on a recent version of + init-system-helpers. + . + This flag is useful for maintainer scripts that want to defer systemd + actions to deb-systemd-invoke(1p). However, it was only added + in init-system-helpers version 1.58. + . + Please add Pre-Depends: ${misc:Pre-Depends} to your + debian/control file. diff -Nru lintian-2.93.0/tags/s/skip-systemd-native-flag-missing-pre-depends.tag lintian-2.89.0ubuntu1/tags/s/skip-systemd-native-flag-missing-pre-depends.tag --- lintian-2.93.0/tags/s/skip-systemd-native-flag-missing-pre-depends.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/skip-systemd-native-flag-missing-pre-depends.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,15 +0,0 @@ -Tag: skip-systemd-native-flag-missing-pre-depends -Severity: warning -Check: scripts -See-Also: invoke-rc.d(8), deb-systemd-invoke(1p) -Explanation: This package uses the --skip-systemd-native - invoke-rc.d flag in the specified maintainer script but does - not specify a Pre-Depends dependency on a recent version of - init-system-helpers. - . - This flag is useful for maintainer scripts that want to defer systemd - actions to deb-systemd-invoke(1p). However, it was only added - in init-system-helpers version 1.58. - . - Please add Pre-Depends: ${misc:Pre-Depends} to your - debian/control file. diff -Nru lintian-2.93.0/tags/s/source-contains-arch-control-dir.desc lintian-2.89.0ubuntu1/tags/s/source-contains-arch-control-dir.desc --- lintian-2.93.0/tags/s/source-contains-arch-control-dir.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/source-contains-arch-control-dir.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: source-contains-arch-control-dir +Severity: pedantic +Check: cruft +Info: The upstream source contains an {arch} or .arch-ids directory or a + directory starting with ,, (used by baz for debugging traces). + It was most likely included by accident since Arch version control + directories usually don't belong in releases. If an upstream release + tarball contains these directories, you should usually report this as a + bug upstream. diff -Nru lintian-2.93.0/tags/s/source-contains-arch-control-dir.tag lintian-2.89.0ubuntu1/tags/s/source-contains-arch-control-dir.tag --- lintian-2.93.0/tags/s/source-contains-arch-control-dir.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/source-contains-arch-control-dir.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: source-contains-arch-control-dir -Severity: pedantic -Check: cruft -Explanation: The upstream source contains an {arch} or .arch-ids directory or a - directory starting with ,, (used by baz for debugging traces). - It was most likely included by accident since Arch version control - directories usually don't belong in releases. If an upstream release - tarball contains these directories, you should usually report this as a - bug upstream. diff -Nru lintian-2.93.0/tags/s/source-contains-arch-inventory-file.desc lintian-2.89.0ubuntu1/tags/s/source-contains-arch-inventory-file.desc --- lintian-2.93.0/tags/s/source-contains-arch-inventory-file.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/source-contains-arch-inventory-file.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: source-contains-arch-inventory-file +Severity: pedantic +Check: cruft +Info: The upstream source contains an .arch-inventory file. This + is Arch metadata that should normally not be distributed. You may want + to report this as an upstream bug. diff -Nru lintian-2.93.0/tags/s/source-contains-arch-inventory-file.tag lintian-2.89.0ubuntu1/tags/s/source-contains-arch-inventory-file.tag --- lintian-2.93.0/tags/s/source-contains-arch-inventory-file.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/source-contains-arch-inventory-file.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: source-contains-arch-inventory-file -Severity: pedantic -Check: cruft -Explanation: The upstream source contains an .arch-inventory file. This - is Arch metadata that should normally not be distributed. You may want - to report this as an upstream bug. diff -Nru lintian-2.93.0/tags/s/source-contains-autogenerated-gperf-data.desc lintian-2.89.0ubuntu1/tags/s/source-contains-autogenerated-gperf-data.desc --- lintian-2.93.0/tags/s/source-contains-autogenerated-gperf-data.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/source-contains-autogenerated-gperf-data.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,12 @@ +Tag: source-contains-autogenerated-gperf-data +Severity: pedantic +Certainty: possible +Check: cruft +Info: The following file is autogenerated by gperf + . + They are usually provided for the convenience of users. These files + usually just take up space in the tarball. + . + Check if upstream also provides source-only tarballs that you can use as + the upstream distribution instead. If not, you may want to ask upstream + to provide source-only tarballs. diff -Nru lintian-2.93.0/tags/s/source-contains-autogenerated-gperf-data.tag lintian-2.89.0ubuntu1/tags/s/source-contains-autogenerated-gperf-data.tag --- lintian-2.93.0/tags/s/source-contains-autogenerated-gperf-data.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/source-contains-autogenerated-gperf-data.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,11 +0,0 @@ -Tag: source-contains-autogenerated-gperf-data -Severity: pedantic -Check: cruft -Explanation: The following file is autogenerated by gperf - . - They are usually provided for the convenience of users. These files - usually just take up space in the tarball. - . - Check if upstream also provides source-only tarballs that you can use as - the upstream distribution instead. If not, you may want to ask upstream - to provide source-only tarballs. diff -Nru lintian-2.93.0/tags/s/source-contains-autogenerated-visual-c++-file.desc lintian-2.89.0ubuntu1/tags/s/source-contains-autogenerated-visual-c++-file.desc --- lintian-2.93.0/tags/s/source-contains-autogenerated-visual-c++-file.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/source-contains-autogenerated-visual-c++-file.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,12 @@ +Tag: source-contains-autogenerated-visual-c++-file +Severity: pedantic +Certainty: possible +Check: cruft +Info: The following file is autogenerated by Microsoft Visual C++. + . + They are usually provided for the convenience of users. These files + usually just take up space in the tarball and are of no use in Debian. + . + Check if upstream also provides source-only tarballs that you can use as + the upstream distribution instead. If not, you may want to ask upstream + to provide source-only tarballs. diff -Nru lintian-2.93.0/tags/s/source-contains-autogenerated-visual-c++-file.tag lintian-2.89.0ubuntu1/tags/s/source-contains-autogenerated-visual-c++-file.tag --- lintian-2.93.0/tags/s/source-contains-autogenerated-visual-c++-file.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/source-contains-autogenerated-visual-c++-file.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,11 +0,0 @@ -Tag: source-contains-autogenerated-visual-c++-file -Severity: pedantic -Check: cruft -Explanation: The following file is autogenerated by Microsoft Visual C++. - . - They are usually provided for the convenience of users. These files - usually just take up space in the tarball and are of no use in Debian. - . - Check if upstream also provides source-only tarballs that you can use as - the upstream distribution instead. If not, you may want to ask upstream - to provide source-only tarballs. diff -Nru lintian-2.93.0/tags/s/source-contains-browserified-javascript.desc lintian-2.89.0ubuntu1/tags/s/source-contains-browserified-javascript.desc --- lintian-2.93.0/tags/s/source-contains-browserified-javascript.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/source-contains-browserified-javascript.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: source-contains-browserified-javascript +Severity: pedantic +Certainty: possible +Check: cruft +Info: The following file contains javascript built from browserify + . + This file may contain javascript that is build with the help of browserify + or webpack tools. + . + You should rebuilt this file from source. diff -Nru lintian-2.93.0/tags/s/source-contains-browserified-javascript.tag lintian-2.89.0ubuntu1/tags/s/source-contains-browserified-javascript.tag --- lintian-2.93.0/tags/s/source-contains-browserified-javascript.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/source-contains-browserified-javascript.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: source-contains-browserified-javascript -Severity: pedantic -Check: cruft -Explanation: The following file contains javascript built from browserify - . - This file may contain javascript that is build with the help of browserify - or webpack tools. - . - You should rebuilt this file from source. diff -Nru lintian-2.93.0/tags/s/source-contains-bts-control-dir.desc lintian-2.89.0ubuntu1/tags/s/source-contains-bts-control-dir.desc --- lintian-2.93.0/tags/s/source-contains-bts-control-dir.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/source-contains-bts-control-dir.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: source-contains-bts-control-dir +Severity: pedantic +Check: cruft +Info: The upstream source contains a directory used by a bug tracking + system. It was most likely included by accident since bug tracking system + directories usually don't belong in releases. diff -Nru lintian-2.93.0/tags/s/source-contains-bts-control-dir.tag lintian-2.89.0ubuntu1/tags/s/source-contains-bts-control-dir.tag --- lintian-2.93.0/tags/s/source-contains-bts-control-dir.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/source-contains-bts-control-dir.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: source-contains-bts-control-dir -Severity: pedantic -Check: cruft -Explanation: The upstream source contains a directory used by a bug tracking - system. It was most likely included by accident since bug tracking system - directories usually don't belong in releases. diff -Nru lintian-2.93.0/tags/s/source-contains-bzr-control-dir.desc lintian-2.89.0ubuntu1/tags/s/source-contains-bzr-control-dir.desc --- lintian-2.93.0/tags/s/source-contains-bzr-control-dir.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/source-contains-bzr-control-dir.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: source-contains-bzr-control-dir +Severity: pedantic +Check: cruft +Info: The upstream source contains a .bzr directory. It was most likely + included by accident since bazaar-ng version control directories usually + don't belong in releases and may contain the entire repository. When + packaging a bzr snapshot, use bzr export to create a clean tree. If an + upstream release tarball contains .bzr directories, you should usually + report this as a bug upstream. diff -Nru lintian-2.93.0/tags/s/source-contains-bzr-control-dir.tag lintian-2.89.0ubuntu1/tags/s/source-contains-bzr-control-dir.tag --- lintian-2.93.0/tags/s/source-contains-bzr-control-dir.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/source-contains-bzr-control-dir.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: source-contains-bzr-control-dir -Severity: pedantic -Check: cruft -Explanation: The upstream source contains a .bzr directory. It was most likely - included by accident since bazaar-ng version control directories usually - don't belong in releases and may contain the entire repository. When - packaging a bzr snapshot, use bzr export to create a clean tree. If an - upstream release tarball contains .bzr directories, you should usually - report this as a bug upstream. diff -Nru lintian-2.93.0/tags/s/source-contains-cvs-conflict-copy.desc lintian-2.89.0ubuntu1/tags/s/source-contains-cvs-conflict-copy.desc --- lintian-2.93.0/tags/s/source-contains-cvs-conflict-copy.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/source-contains-cvs-conflict-copy.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: source-contains-cvs-conflict-copy +Severity: pedantic +Check: cruft +Info: The upstream source contains a CVS conflict copy. These have file + names like .#file.version and are generated by CVS when a + conflict was detected when merging local changes with updates from a + source repository. They're useful only while resolving the conflict and + were probably included by accident. You may want to report this as an + upstream bug. diff -Nru lintian-2.93.0/tags/s/source-contains-cvs-conflict-copy.tag lintian-2.89.0ubuntu1/tags/s/source-contains-cvs-conflict-copy.tag --- lintian-2.93.0/tags/s/source-contains-cvs-conflict-copy.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/source-contains-cvs-conflict-copy.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: source-contains-cvs-conflict-copy -Severity: pedantic -Check: cruft -Explanation: The upstream source contains a CVS conflict copy. These have file - names like .#file.version and are generated by CVS when a - conflict was detected when merging local changes with updates from a - source repository. They're useful only while resolving the conflict and - were probably included by accident. You may want to report this as an - upstream bug. diff -Nru lintian-2.93.0/tags/s/source-contains-cvs-control-dir.desc lintian-2.89.0ubuntu1/tags/s/source-contains-cvs-control-dir.desc --- lintian-2.93.0/tags/s/source-contains-cvs-control-dir.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/source-contains-cvs-control-dir.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: source-contains-cvs-control-dir +Severity: pedantic +Check: cruft +Info: The upstream source contains a CVS directory. It was most likely + included by accident since CVS directories usually don't belong in + releases. When packaging a CVS snapshot, export from CVS rather than use + a checkout. If an upstream release tarball contains CVS directories, you + usually should report this as a bug to upstream. diff -Nru lintian-2.93.0/tags/s/source-contains-cvs-control-dir.tag lintian-2.89.0ubuntu1/tags/s/source-contains-cvs-control-dir.tag --- lintian-2.93.0/tags/s/source-contains-cvs-control-dir.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/source-contains-cvs-control-dir.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: source-contains-cvs-control-dir -Severity: pedantic -Check: cruft -Explanation: The upstream source contains a CVS directory. It was most likely - included by accident since CVS directories usually don't belong in - releases. When packaging a CVS snapshot, export from CVS rather than use - a checkout. If an upstream release tarball contains CVS directories, you - usually should report this as a bug to upstream. diff -Nru lintian-2.93.0/tags/s/source-contains-data-from-ieee-data-oui-db.desc lintian-2.89.0ubuntu1/tags/s/source-contains-data-from-ieee-data-oui-db.desc --- lintian-2.93.0/tags/s/source-contains-data-from-ieee-data-oui-db.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/source-contains-data-from-ieee-data-oui-db.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: source-contains-data-from-ieee-data-oui-db +Severity: pedantic +Certainty: possible +Check: cruft +Info: The following file contains data from the OUI database + . + This file contains a likely outdated copy of + Organizationally Unique Identifier (OUI) database from IEEE. + . + Please use the files from ieee-data package instead. diff -Nru lintian-2.93.0/tags/s/source-contains-data-from-ieee-data-oui-db.tag lintian-2.89.0ubuntu1/tags/s/source-contains-data-from-ieee-data-oui-db.tag --- lintian-2.93.0/tags/s/source-contains-data-from-ieee-data-oui-db.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/source-contains-data-from-ieee-data-oui-db.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: source-contains-data-from-ieee-data-oui-db -Severity: pedantic -Check: cruft -Explanation: The following file contains data from the OUI database - . - This file contains a likely outdated copy of - Organizationally Unique Identifier (OUI) database from IEEE. - . - Please use the files from ieee-data package instead. diff -Nru lintian-2.93.0/tags/s/source-contains-git-control-dir.desc lintian-2.89.0ubuntu1/tags/s/source-contains-git-control-dir.desc --- lintian-2.93.0/tags/s/source-contains-git-control-dir.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/source-contains-git-control-dir.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: source-contains-git-control-dir +Severity: pedantic +Check: cruft +Info: The upstream source contains a .git directory. It was most likely + included by accident since git version control directories usually don't + belong in releases and may contain a complete copy of the repository. If + an upstream release tarball contains .git directories, you should usually + report this as a bug upstream. diff -Nru lintian-2.93.0/tags/s/source-contains-git-control-dir.tag lintian-2.89.0ubuntu1/tags/s/source-contains-git-control-dir.tag --- lintian-2.93.0/tags/s/source-contains-git-control-dir.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/source-contains-git-control-dir.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: source-contains-git-control-dir -Severity: pedantic -Check: cruft -Explanation: The upstream source contains a .git directory. It was most likely - included by accident since git version control directories usually don't - belong in releases and may contain a complete copy of the repository. If - an upstream release tarball contains .git directories, you should usually - report this as a bug upstream. diff -Nru lintian-2.93.0/tags/s/source-contains-hg-control-dir.desc lintian-2.89.0ubuntu1/tags/s/source-contains-hg-control-dir.desc --- lintian-2.93.0/tags/s/source-contains-hg-control-dir.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/source-contains-hg-control-dir.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: source-contains-hg-control-dir +Severity: pedantic +Check: cruft +Info: The upstream source contains a .hg directory. It was most likely + included by accident since hg version control directories usually don't + belong in releases and may contain a complete copy of the repository. If + an upstream release tarball contains .hg directories, you should usually + report this as a bug upstream. diff -Nru lintian-2.93.0/tags/s/source-contains-hg-control-dir.tag lintian-2.89.0ubuntu1/tags/s/source-contains-hg-control-dir.tag --- lintian-2.93.0/tags/s/source-contains-hg-control-dir.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/source-contains-hg-control-dir.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: source-contains-hg-control-dir -Severity: pedantic -Check: cruft -Explanation: The upstream source contains a .hg directory. It was most likely - included by accident since hg version control directories usually don't - belong in releases and may contain a complete copy of the repository. If - an upstream release tarball contains .hg directories, you should usually - report this as a bug upstream. diff -Nru lintian-2.93.0/tags/s/source-contains-hg-tags-file.desc lintian-2.89.0ubuntu1/tags/s/source-contains-hg-tags-file.desc --- lintian-2.93.0/tags/s/source-contains-hg-tags-file.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/source-contains-hg-tags-file.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: source-contains-hg-tags-file +Severity: pedantic +Check: cruft +Info: The upstream source contains an .hgtags file. This file is + Mercurial metadata that should normally not be distributed. It stores + hashes of tagged commits in a Mercurial repository and isn't therefore + useful without the repository. You may want to report this as an + upstream bug. diff -Nru lintian-2.93.0/tags/s/source-contains-hg-tags-file.tag lintian-2.89.0ubuntu1/tags/s/source-contains-hg-tags-file.tag --- lintian-2.93.0/tags/s/source-contains-hg-tags-file.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/source-contains-hg-tags-file.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: source-contains-hg-tags-file -Severity: pedantic -Check: cruft -Explanation: The upstream source contains an .hgtags file. This file is - Mercurial metadata that should normally not be distributed. It stores - hashes of tagged commits in a Mercurial repository and isn't therefore - useful without the repository. You may want to report this as an - upstream bug. diff -Nru lintian-2.93.0/tags/s/source-contains-prebuilt-binary.desc lintian-2.89.0ubuntu1/tags/s/source-contains-prebuilt-binary.desc --- lintian-2.93.0/tags/s/source-contains-prebuilt-binary.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/source-contains-prebuilt-binary.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: source-contains-prebuilt-binary +Severity: pedantic +Check: cruft +Info: The source tarball contains a prebuilt ELF object. They are usually + left by mistake when generating the tarball by not cleaning the source + directory first. You may want to report this as an upstream bug, in case + there is no sign that this was intended. diff -Nru lintian-2.93.0/tags/s/source-contains-prebuilt-binary.tag lintian-2.89.0ubuntu1/tags/s/source-contains-prebuilt-binary.tag --- lintian-2.93.0/tags/s/source-contains-prebuilt-binary.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/source-contains-prebuilt-binary.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: source-contains-prebuilt-binary -Severity: pedantic -Check: cruft -Explanation: The source tarball contains a prebuilt ELF object. They are usually - left by mistake when generating the tarball by not cleaning the source - directory first. You may want to report this as an upstream bug, in case - there is no sign that this was intended. diff -Nru lintian-2.93.0/tags/s/source-contains-prebuilt-doxygen-documentation.desc lintian-2.89.0ubuntu1/tags/s/source-contains-prebuilt-doxygen-documentation.desc --- lintian-2.93.0/tags/s/source-contains-prebuilt-doxygen-documentation.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/source-contains-prebuilt-doxygen-documentation.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: source-contains-prebuilt-doxygen-documentation +Severity: pedantic +Certainty: possible +Check: cruft +Info: The source tarball contains prebuilt doxygen documentation. + This is usually left by mistake when generating the tarball without + first cleaning the source directory. You may want to report this as + an upstream bug if there is no sign that this was intended. + . + It is preferable to rebuild documentation directly from source. diff -Nru lintian-2.93.0/tags/s/source-contains-prebuilt-doxygen-documentation.tag lintian-2.89.0ubuntu1/tags/s/source-contains-prebuilt-doxygen-documentation.tag --- lintian-2.93.0/tags/s/source-contains-prebuilt-doxygen-documentation.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/source-contains-prebuilt-doxygen-documentation.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: source-contains-prebuilt-doxygen-documentation -Severity: pedantic -Check: cruft -Explanation: The source tarball contains prebuilt doxygen documentation. - This is usually left by mistake when generating the tarball without - first cleaning the source directory. You may want to report this as - an upstream bug if there is no sign that this was intended. - . - It is preferable to rebuild documentation directly from source. diff -Nru lintian-2.93.0/tags/s/source-contains-prebuilt-flash-object.desc lintian-2.89.0ubuntu1/tags/s/source-contains-prebuilt-flash-object.desc --- lintian-2.93.0/tags/s/source-contains-prebuilt-flash-object.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/source-contains-prebuilt-flash-object.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,16 @@ +Tag: source-contains-prebuilt-flash-object +Severity: pedantic +Certainty: possible +Check: cruft +Info: The source tarball contains a prebuilt file in the Shockwave Flash (SWF) + or Flash Video (FLV) format. These are often included by mistake when + developers generate a tarball without cleaning the source directory + first. An exception is simple video files, which are their own + source. + . + If there is no sign this was intended, consider reporting it as an + upstream bug. + . + If the Flash file is not meant to be modified directly, please make + sure the package includes the source for the file and that the + packaging rebuilds it. diff -Nru lintian-2.93.0/tags/s/source-contains-prebuilt-flash-object.tag lintian-2.89.0ubuntu1/tags/s/source-contains-prebuilt-flash-object.tag --- lintian-2.93.0/tags/s/source-contains-prebuilt-flash-object.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/source-contains-prebuilt-flash-object.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,15 +0,0 @@ -Tag: source-contains-prebuilt-flash-object -Severity: pedantic -Check: cruft -Explanation: The source tarball contains a prebuilt file in the Shockwave Flash (SWF) - or Flash Video (FLV) format. These are often included by mistake when - developers generate a tarball without cleaning the source directory - first. An exception is simple video files, which are their own - source. - . - If there is no sign this was intended, consider reporting it as an - upstream bug. - . - If the Flash file is not meant to be modified directly, please make - sure the package includes the source for the file and that the - packaging rebuilds it. diff -Nru lintian-2.93.0/tags/s/source-contains-prebuilt-flash-project.desc lintian-2.89.0ubuntu1/tags/s/source-contains-prebuilt-flash-project.desc --- lintian-2.93.0/tags/s/source-contains-prebuilt-flash-project.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/source-contains-prebuilt-flash-project.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,15 @@ +Tag: source-contains-prebuilt-flash-project +Severity: pedantic +Certainty: possible +Check: cruft +Info: The source tarball contains a prebuilt file in the Shockwave Flash + project (FLA) format. These are often included by mistake when + developers generate a tarball without cleaning the source directory + first. + . + If there is no sign this was intended, consider reporting it as an + upstream bug. + . + If the Flash file is not meant to be modified directly, please make + sure the package includes the source for the file and that the + packaging rebuilds it. diff -Nru lintian-2.93.0/tags/s/source-contains-prebuilt-flash-project.tag lintian-2.89.0ubuntu1/tags/s/source-contains-prebuilt-flash-project.tag --- lintian-2.93.0/tags/s/source-contains-prebuilt-flash-project.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/source-contains-prebuilt-flash-project.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,14 +0,0 @@ -Tag: source-contains-prebuilt-flash-project -Severity: pedantic -Check: cruft -Explanation: The source tarball contains a prebuilt file in the Shockwave Flash - project (FLA) format. These are often included by mistake when - developers generate a tarball without cleaning the source directory - first. - . - If there is no sign this was intended, consider reporting it as an - upstream bug. - . - If the Flash file is not meant to be modified directly, please make - sure the package includes the source for the file and that the - packaging rebuilds it. diff -Nru lintian-2.93.0/tags/s/source-contains-prebuilt-java-object.desc lintian-2.89.0ubuntu1/tags/s/source-contains-prebuilt-java-object.desc --- lintian-2.93.0/tags/s/source-contains-prebuilt-java-object.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/source-contains-prebuilt-java-object.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: source-contains-prebuilt-java-object +Severity: pedantic +Certainty: possible +Check: languages/java +Info: The source tarball contains a prebuilt Java class file. These are often + included by mistake when developers generate a tarball without cleaning + the source directory first. If there is no sign this was intended, + consider reporting it as an upstream bug as it may be a DFSG violation. diff -Nru lintian-2.93.0/tags/s/source-contains-prebuilt-java-object.tag lintian-2.89.0ubuntu1/tags/s/source-contains-prebuilt-java-object.tag --- lintian-2.93.0/tags/s/source-contains-prebuilt-java-object.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/source-contains-prebuilt-java-object.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: source-contains-prebuilt-java-object -Severity: pedantic -Check: languages/java -Explanation: The source tarball contains a prebuilt Java class file. These are often - included by mistake when developers generate a tarball without cleaning - the source directory first. If there is no sign this was intended, - consider reporting it as an upstream bug as it may be a DFSG violation. diff -Nru lintian-2.93.0/tags/s/source-contains-prebuilt-javascript-object.desc lintian-2.89.0ubuntu1/tags/s/source-contains-prebuilt-javascript-object.desc --- lintian-2.93.0/tags/s/source-contains-prebuilt-javascript-object.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/source-contains-prebuilt-javascript-object.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: source-contains-prebuilt-javascript-object +Severity: pedantic +Certainty: possible +Check: cruft +Info: The source tarball contains a prebuilt (minified) JavaScript object. + They are usually left by mistake when generating the tarball by not + cleaning the source directory first. You may want to report this as + an upstream bug, in case there is no sign that this was intended. diff -Nru lintian-2.93.0/tags/s/source-contains-prebuilt-javascript-object.tag lintian-2.89.0ubuntu1/tags/s/source-contains-prebuilt-javascript-object.tag --- lintian-2.93.0/tags/s/source-contains-prebuilt-javascript-object.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/source-contains-prebuilt-javascript-object.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: source-contains-prebuilt-javascript-object -Severity: pedantic -Check: cruft -Explanation: The source tarball contains a prebuilt (minified) JavaScript object. - They are usually left by mistake when generating the tarball by not - cleaning the source directory first. You may want to report this as - an upstream bug, in case there is no sign that this was intended. diff -Nru lintian-2.93.0/tags/s/source-contains-prebuilt-ms-help-file.desc lintian-2.89.0ubuntu1/tags/s/source-contains-prebuilt-ms-help-file.desc --- lintian-2.93.0/tags/s/source-contains-prebuilt-ms-help-file.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/source-contains-prebuilt-ms-help-file.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,18 @@ +Tag: source-contains-prebuilt-ms-help-file +Severity: error +Certainty: possible +Check: cruft +Info: The source tarball contains a prebuilt Microsoft precompiled help + file (CHM file). These are often included by mistake when developers generate + a tarball without cleaning the source directory first. + . + CHM files are mainly produced by proprietary, Windows-specific software. + They are also mainly consumed by the Microsoft HTML Help Workshop. + . + Whilst there is free software to read and write them, any + examples existing in source packages are likely to be created + by the proprietary Microsoft software and are probably missing + the source HTML and associated files. + . + If there is no sign this was intended, consider reporting it as + an upstream bug. diff -Nru lintian-2.93.0/tags/s/source-contains-prebuilt-ms-help-file.tag lintian-2.89.0ubuntu1/tags/s/source-contains-prebuilt-ms-help-file.tag --- lintian-2.93.0/tags/s/source-contains-prebuilt-ms-help-file.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/source-contains-prebuilt-ms-help-file.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,17 +0,0 @@ -Tag: source-contains-prebuilt-ms-help-file -Severity: error -Check: cruft -Explanation: The source tarball contains a prebuilt Microsoft precompiled help - file (CHM file). These are often included by mistake when developers generate - a tarball without cleaning the source directory first. - . - CHM files are mainly produced by proprietary, Windows-specific software. - They are also mainly consumed by the Microsoft HTML Help Workshop. - . - Whilst there is free software to read and write them, any - examples existing in source packages are likely to be created - by the proprietary Microsoft software and are probably missing - the source HTML and associated files. - . - If there is no sign this was intended, consider reporting it as - an upstream bug. diff -Nru lintian-2.93.0/tags/s/source-contains-prebuilt-pandoc-documentation.desc lintian-2.89.0ubuntu1/tags/s/source-contains-prebuilt-pandoc-documentation.desc --- lintian-2.93.0/tags/s/source-contains-prebuilt-pandoc-documentation.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/source-contains-prebuilt-pandoc-documentation.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: source-contains-prebuilt-pandoc-documentation +Severity: pedantic +Certainty: possible +Check: cruft +Info: The source tarball contains prebuilt pandoc documentation. + This is usually left by mistake when generating the tarball without + first cleaning the source directory. You may want to report this as + an upstream bug if there is no sign that this was intended. + . + It is preferable to rebuild documentation directly from source. diff -Nru lintian-2.93.0/tags/s/source-contains-prebuilt-pandoc-documentation.tag lintian-2.89.0ubuntu1/tags/s/source-contains-prebuilt-pandoc-documentation.tag --- lintian-2.93.0/tags/s/source-contains-prebuilt-pandoc-documentation.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/source-contains-prebuilt-pandoc-documentation.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: source-contains-prebuilt-pandoc-documentation -Severity: pedantic -Check: cruft -Explanation: The source tarball contains prebuilt pandoc documentation. - This is usually left by mistake when generating the tarball without - first cleaning the source directory. You may want to report this as - an upstream bug if there is no sign that this was intended. - . - It is preferable to rebuild documentation directly from source. diff -Nru lintian-2.93.0/tags/s/source-contains-prebuilt-python-object.desc lintian-2.89.0ubuntu1/tags/s/source-contains-prebuilt-python-object.desc --- lintian-2.93.0/tags/s/source-contains-prebuilt-python-object.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/source-contains-prebuilt-python-object.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: source-contains-prebuilt-python-object +Severity: pedantic +Certainty: possible +Check: cruft +Info: The source tarball contains a prebuilt Python object. They are + usually left by mistake when generating the tarball by not cleaning the + source directory first. You may want to report this as an upstream bug, + in case there is no sign that this was intended. diff -Nru lintian-2.93.0/tags/s/source-contains-prebuilt-python-object.tag lintian-2.89.0ubuntu1/tags/s/source-contains-prebuilt-python-object.tag --- lintian-2.93.0/tags/s/source-contains-prebuilt-python-object.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/source-contains-prebuilt-python-object.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: source-contains-prebuilt-python-object -Severity: pedantic -Check: cruft -Explanation: The source tarball contains a prebuilt Python object. They are - usually left by mistake when generating the tarball by not cleaning the - source directory first. You may want to report this as an upstream bug, - in case there is no sign that this was intended. diff -Nru lintian-2.93.0/tags/s/source-contains-prebuilt-silverlight-object.desc lintian-2.89.0ubuntu1/tags/s/source-contains-prebuilt-silverlight-object.desc --- lintian-2.93.0/tags/s/source-contains-prebuilt-silverlight-object.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/source-contains-prebuilt-silverlight-object.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: source-contains-prebuilt-silverlight-object +Severity: error +Certainty: possible +Check: cruft +Info: The source tarball contains a prebuilt Silverlight control. + Unfortunately, the tools used to build such files have non-free + dependencies and are not present in Debian. This file must be + completely removed. diff -Nru lintian-2.93.0/tags/s/source-contains-prebuilt-silverlight-object.tag lintian-2.89.0ubuntu1/tags/s/source-contains-prebuilt-silverlight-object.tag --- lintian-2.93.0/tags/s/source-contains-prebuilt-silverlight-object.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/source-contains-prebuilt-silverlight-object.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: source-contains-prebuilt-silverlight-object -Severity: error -Check: cruft -Explanation: The source tarball contains a prebuilt Silverlight control. - Unfortunately, the tools used to build such files have non-free - dependencies and are not present in Debian. This file must be - completely removed. diff -Nru lintian-2.93.0/tags/s/source-contains-prebuilt-sphinx-documentation.desc lintian-2.89.0ubuntu1/tags/s/source-contains-prebuilt-sphinx-documentation.desc --- lintian-2.93.0/tags/s/source-contains-prebuilt-sphinx-documentation.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/source-contains-prebuilt-sphinx-documentation.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: source-contains-prebuilt-sphinx-documentation +Severity: pedantic +Certainty: possible +Check: cruft +Info: The source tarball contains prebuilt Sphinx documentation. + This is usually left by mistake when generating the tarball without + first cleaning the source directory. You may want to report this as + an upstream bug if there is no sign that this was intended. + . + It is preferable to rebuild documentation directly from source. diff -Nru lintian-2.93.0/tags/s/source-contains-prebuilt-sphinx-documentation.tag lintian-2.89.0ubuntu1/tags/s/source-contains-prebuilt-sphinx-documentation.tag --- lintian-2.93.0/tags/s/source-contains-prebuilt-sphinx-documentation.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/source-contains-prebuilt-sphinx-documentation.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: source-contains-prebuilt-sphinx-documentation -Severity: pedantic -Check: cruft -Explanation: The source tarball contains prebuilt Sphinx documentation. - This is usually left by mistake when generating the tarball without - first cleaning the source directory. You may want to report this as - an upstream bug if there is no sign that this was intended. - . - It is preferable to rebuild documentation directly from source. diff -Nru lintian-2.93.0/tags/s/source-contains-prebuilt-wasm-binary.desc lintian-2.89.0ubuntu1/tags/s/source-contains-prebuilt-wasm-binary.desc --- lintian-2.93.0/tags/s/source-contains-prebuilt-wasm-binary.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/source-contains-prebuilt-wasm-binary.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,11 @@ +Tag: source-contains-prebuilt-wasm-binary +Severity: pedantic +Check: cruft +Info: The source tarball contains a prebuilt binary wasm object. + They are usually provided for the convenience of users. These files + usually just take up space in the tarball and need to be rebuilt from + source. + . + Check if upstream also provides source-only tarballs that you can use as + the upstream distribution instead. If not, you may want to ask upstream + to provide source-only tarballs. diff -Nru lintian-2.93.0/tags/s/source-contains-prebuilt-wasm-binary.tag lintian-2.89.0ubuntu1/tags/s/source-contains-prebuilt-wasm-binary.tag --- lintian-2.93.0/tags/s/source-contains-prebuilt-wasm-binary.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/source-contains-prebuilt-wasm-binary.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,11 +0,0 @@ -Tag: source-contains-prebuilt-wasm-binary -Severity: pedantic -Check: cruft -Explanation: The source tarball contains a prebuilt binary wasm object. - They are usually provided for the convenience of users. These files - usually just take up space in the tarball and need to be rebuilt from - source. - . - Check if upstream also provides source-only tarballs that you can use as - the upstream distribution instead. If not, you may want to ask upstream - to provide source-only tarballs. diff -Nru lintian-2.93.0/tags/s/source-contains-prebuilt-windows-binary.desc lintian-2.89.0ubuntu1/tags/s/source-contains-prebuilt-windows-binary.desc --- lintian-2.93.0/tags/s/source-contains-prebuilt-windows-binary.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/source-contains-prebuilt-windows-binary.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,13 @@ +Tag: source-contains-prebuilt-windows-binary +Severity: warning +Check: cruft +Info: The source tarball contains a prebuilt binary for Microsoft Windows. + They are usually provided for the convenience of users. These files + usually just take up space in the tarball. + . + However, they may be a DFSG violation in that the corresponding source + and build system are not available. + . + Check if upstream also provides source-only tarballs that you can use as + the upstream distribution instead. If not, you may want to ask upstream + to provide source-only tarballs. diff -Nru lintian-2.93.0/tags/s/source-contains-prebuilt-windows-binary.tag lintian-2.89.0ubuntu1/tags/s/source-contains-prebuilt-windows-binary.tag --- lintian-2.93.0/tags/s/source-contains-prebuilt-windows-binary.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/source-contains-prebuilt-windows-binary.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,13 +0,0 @@ -Tag: source-contains-prebuilt-windows-binary -Severity: warning -Check: cruft -Explanation: The source tarball contains a prebuilt binary for Microsoft Windows. - They are usually provided for the convenience of users. These files - usually just take up space in the tarball. - . - However, they may be a DFSG violation in that the corresponding source - and build system are not available. - . - Check if upstream also provides source-only tarballs that you can use as - the upstream distribution instead. If not, you may want to ask upstream - to provide source-only tarballs. diff -Nru lintian-2.93.0/tags/s/source-contains-prebuilt-yapp-parser.desc lintian-2.89.0ubuntu1/tags/s/source-contains-prebuilt-yapp-parser.desc --- lintian-2.93.0/tags/s/source-contains-prebuilt-yapp-parser.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/source-contains-prebuilt-yapp-parser.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: source-contains-prebuilt-yapp-parser +Severity: pedantic +Check: languages/perl/yapp +Info: The source tarball contains a prebuilt Parse::Yapp parser. + This is usually left by mistake when generating the tarball without + first cleaning the source directory. You may want to report this as + an upstream bug if there is no sign that this was intended. + . + Please build the parser from source. +Ref: #921080 diff -Nru lintian-2.93.0/tags/s/source-contains-prebuilt-yapp-parser.tag lintian-2.89.0ubuntu1/tags/s/source-contains-prebuilt-yapp-parser.tag --- lintian-2.93.0/tags/s/source-contains-prebuilt-yapp-parser.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/source-contains-prebuilt-yapp-parser.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,10 +0,0 @@ -Tag: source-contains-prebuilt-yapp-parser -Severity: pedantic -Check: languages/perl/yapp -Explanation: The source tarball contains a prebuilt Parse::Yapp parser. - This is usually left by mistake when generating the tarball without - first cleaning the source directory. You may want to report this as - an upstream bug if there is no sign that this was intended. - . - Please build the parser from source. -See-Also: Bug#921080 diff -Nru lintian-2.93.0/tags/s/source-contains-svk-commit-file.desc lintian-2.89.0ubuntu1/tags/s/source-contains-svk-commit-file.desc --- lintian-2.93.0/tags/s/source-contains-svk-commit-file.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/source-contains-svk-commit-file.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: source-contains-svk-commit-file +Severity: pedantic +Check: cruft +Info: The upstream source contains an svk-commitNNN.tmp, + almost certainly a left-over from a failed Subversion commit. You may + want to report this as an upstream bug. diff -Nru lintian-2.93.0/tags/s/source-contains-svk-commit-file.tag lintian-2.89.0ubuntu1/tags/s/source-contains-svk-commit-file.tag --- lintian-2.93.0/tags/s/source-contains-svk-commit-file.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/source-contains-svk-commit-file.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: source-contains-svk-commit-file -Severity: pedantic -Check: cruft -Explanation: The upstream source contains an svk-commitNNN.tmp, - almost certainly a left-over from a failed Subversion commit. You may - want to report this as an upstream bug. diff -Nru lintian-2.93.0/tags/s/source-contains-svn-commit-file.desc lintian-2.89.0ubuntu1/tags/s/source-contains-svn-commit-file.desc --- lintian-2.93.0/tags/s/source-contains-svn-commit-file.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/source-contains-svn-commit-file.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: source-contains-svn-commit-file +Severity: pedantic +Check: cruft +Info: The upstream source contains an svn-commit(.NNN).tmp, + almost certainly a left-over from a failed Subversion commit. You may + want to report this as an upstream bug. diff -Nru lintian-2.93.0/tags/s/source-contains-svn-commit-file.tag lintian-2.89.0ubuntu1/tags/s/source-contains-svn-commit-file.tag --- lintian-2.93.0/tags/s/source-contains-svn-commit-file.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/source-contains-svn-commit-file.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: source-contains-svn-commit-file -Severity: pedantic -Check: cruft -Explanation: The upstream source contains an svn-commit(.NNN).tmp, - almost certainly a left-over from a failed Subversion commit. You may - want to report this as an upstream bug. diff -Nru lintian-2.93.0/tags/s/source-contains-svn-conflict-file.desc lintian-2.89.0ubuntu1/tags/s/source-contains-svn-conflict-file.desc --- lintian-2.93.0/tags/s/source-contains-svn-conflict-file.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/source-contains-svn-conflict-file.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: source-contains-svn-conflict-file +Severity: pedantic +Check: cruft +Info: The upstream source contains a file that looks like a Subversion + conflict file. These are generated by Subversion when a conflict was + detected while merging local changes with updates from a source + repository. They're useful only while resolving the conflict and + were probably included by accident. You may want to report this as an + upstream bug. diff -Nru lintian-2.93.0/tags/s/source-contains-svn-conflict-file.tag lintian-2.89.0ubuntu1/tags/s/source-contains-svn-conflict-file.tag --- lintian-2.93.0/tags/s/source-contains-svn-conflict-file.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/source-contains-svn-conflict-file.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: source-contains-svn-conflict-file -Severity: pedantic -Check: cruft -Explanation: The upstream source contains a file that looks like a Subversion - conflict file. These are generated by Subversion when a conflict was - detected while merging local changes with updates from a source - repository. They're useful only while resolving the conflict and - were probably included by accident. You may want to report this as an - upstream bug. diff -Nru lintian-2.93.0/tags/s/source-contains-svn-control-dir.desc lintian-2.89.0ubuntu1/tags/s/source-contains-svn-control-dir.desc --- lintian-2.93.0/tags/s/source-contains-svn-control-dir.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/source-contains-svn-control-dir.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: source-contains-svn-control-dir +Severity: pedantic +Check: cruft +Info: The upstream source contains an .svn directory. It was most likely + included by accident since Subversion version control directories + usually don't belong in releases. When packaging a Subversion snapshot, + export from Subversion rather than checkout. If an upstream release + tarball contains .svn directories, this should be reported as a bug to + upstream since it can double the size of the tarball to no purpose. diff -Nru lintian-2.93.0/tags/s/source-contains-svn-control-dir.tag lintian-2.89.0ubuntu1/tags/s/source-contains-svn-control-dir.tag --- lintian-2.93.0/tags/s/source-contains-svn-control-dir.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/source-contains-svn-control-dir.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: source-contains-svn-control-dir -Severity: pedantic -Check: cruft -Explanation: The upstream source contains an .svn directory. It was most likely - included by accident since Subversion version control directories - usually don't belong in releases. When packaging a Subversion snapshot, - export from Subversion rather than checkout. If an upstream release - tarball contains .svn directories, this should be reported as a bug to - upstream since it can double the size of the tarball to no purpose. diff -Nru lintian-2.93.0/tags/s/source-contains-waf-binary.desc lintian-2.89.0ubuntu1/tags/s/source-contains-waf-binary.desc --- lintian-2.93.0/tags/s/source-contains-waf-binary.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/source-contains-waf-binary.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,14 @@ +Tag: source-contains-waf-binary +Severity: error +Check: cruft +Info: The source tarball contains a waf binary. This file is a Python + script with an embedded bzip2 archive, which is uncompressed and unpacked + at runtime. + . + Although corresponding sources can be easily extracted, FTP Team does not + consider waf binary as the preferred form of modification; it should be + provided unpacked instead, or completely removed, if possible. + . + You might want to follow these guidelines to obtain an unpacked waf: + https://wiki.debian.org/UnpackWaf +Ref: https://wiki.debian.org/UnpackWaf, #654523 diff -Nru lintian-2.93.0/tags/s/source-contains-waf-binary.tag lintian-2.89.0ubuntu1/tags/s/source-contains-waf-binary.tag --- lintian-2.93.0/tags/s/source-contains-waf-binary.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/source-contains-waf-binary.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,14 +0,0 @@ -Tag: source-contains-waf-binary -Severity: error -Check: cruft -Explanation: The source tarball contains a waf binary. This file is a Python - script with an embedded bzip2 archive, which is uncompressed and unpacked - at runtime. - . - Although corresponding sources can be easily extracted, FTP Team does not - consider waf binary as the preferred form of modification; it should be - provided unpacked instead, or completely removed, if possible. - . - You might want to follow these guidelines to obtain an unpacked waf: - https://wiki.debian.org/UnpackWaf -See-Also: https://wiki.debian.org/UnpackWaf, Bug#654523 diff -Nru lintian-2.93.0/tags/s/source-field-malformed.desc lintian-2.89.0ubuntu1/tags/s/source-field-malformed.desc --- lintian-2.93.0/tags/s/source-field-malformed.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/source-field-malformed.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,12 @@ +Tag: source-field-malformed +Severity: error +Check: fields/source +Info: In debian/control or a .dsc file, the Source field + must contain only the name of the source package. In a binary package, + the Source field may also optionally contain the version number of the + corresponding source package in parentheses. + . + Source package names must consist only of lowercase letters, digits, + plus and minus signs, and periods. They must be at least two characters + long and must start with an alphanumeric character. +Ref: policy 5.6.1 diff -Nru lintian-2.93.0/tags/s/source-field-malformed.tag lintian-2.89.0ubuntu1/tags/s/source-field-malformed.tag --- lintian-2.93.0/tags/s/source-field-malformed.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/source-field-malformed.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,12 +0,0 @@ -Tag: source-field-malformed -Severity: error -Check: fields/source -Explanation: In debian/control or a .dsc file, the Source field - must contain only the name of the source package. In a binary package, - the Source field may also optionally contain the version number of the - corresponding source package in parentheses. - . - Source package names must consist only of lowercase letters, digits, - plus and minus signs, and periods. They must be at least two characters - long and must start with an alphanumeric character. -See-Also: policy 5.6.1 diff -Nru lintian-2.93.0/tags/s/source-format.desc lintian-2.89.0ubuntu1/tags/s/source-format.desc --- lintian-2.93.0/tags/s/source-format.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/source-format.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,4 @@ +Tag: source-format +Severity: classification +Check: debian/source-dir +Info: This is the source format declared in the package. diff -Nru lintian-2.93.0/tags/s/source-format.tag lintian-2.89.0ubuntu1/tags/s/source-format.tag --- lintian-2.93.0/tags/s/source-format.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/source-format.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,4 +0,0 @@ -Tag: source-format -Severity: classification -Check: debian/source-dir -Explanation: This is the source format declared in the package. diff -Nru lintian-2.93.0/tags/s/source-includes-file-in-files-excluded.desc lintian-2.89.0ubuntu1/tags/s/source-includes-file-in-files-excluded.desc --- lintian-2.93.0/tags/s/source-includes-file-in-files-excluded.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/source-includes-file-in-files-excluded.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,13 @@ +Tag: source-includes-file-in-files-excluded +Severity: error +Certainty: possible +Check: debian/copyright/dep5 +Info: A file specified in the Files-Excluded field in + debian/copyright exists in the source tree. + . + This might be a DFSG violation, the referenced files are probably not + attributed in debian/copyright, or the upstream tarball was simply + not repacked as intended. Alternatively, the field is simply out of date. + . + mk-origtargz(1) is typically responsible for removing such files. Support + in git-buildpackage is being tracked in #812721. diff -Nru lintian-2.93.0/tags/s/source-includes-file-in-files-excluded.tag lintian-2.89.0ubuntu1/tags/s/source-includes-file-in-files-excluded.tag --- lintian-2.93.0/tags/s/source-includes-file-in-files-excluded.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/source-includes-file-in-files-excluded.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,12 +0,0 @@ -Tag: source-includes-file-in-files-excluded -Severity: error -Check: debian/copyright/dep5 -Explanation: A file specified in the Files-Excluded field in - debian/copyright exists in the source tree. - . - This might be a DFSG violation, the referenced files are probably not - attributed in debian/copyright, or the upstream tarball was simply - not repacked as intended. Alternatively, the field is simply out of date. - . - mk-origtargz(1) is typically responsible for removing such files. Support - in git-buildpackage is being tracked in Bug#812721. diff -Nru lintian-2.93.0/tags/s/source-is-missing.desc lintian-2.89.0ubuntu1/tags/s/source-is-missing.desc --- lintian-2.93.0/tags/s/source-is-missing.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/source-is-missing.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,13 @@ +Tag: source-is-missing +Severity: error +Certainty: possible +Check: cruft +Info: The source of the following file is missing. Lintian checked a few + possible paths to find the source, and did not find it. + . + Please repack your package to include the source or add it to + "debian/missing-sources" directory. + . + Please note, that very-long-line-length-in-source-file tagged files + are likely tagged source-is-missing. It is a feature not + a bug. diff -Nru lintian-2.93.0/tags/s/source-is-missing.tag lintian-2.89.0ubuntu1/tags/s/source-is-missing.tag --- lintian-2.93.0/tags/s/source-is-missing.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/source-is-missing.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,12 +0,0 @@ -Tag: source-is-missing -Severity: error -Check: cruft -Explanation: The source of the following file is missing. Lintian checked a few - possible paths to find the source, and did not find it. - . - Please repack your package to include the source or add it to - "debian/missing-sources" directory. - . - Please note, that very-long-line-length-in-source-file tagged files - are likely tagged source-is-missing. It is a feature not - a bug. diff -Nru lintian-2.93.0/tags/s/source-nmu-has-incorrect-version-number.desc lintian-2.89.0ubuntu1/tags/s/source-nmu-has-incorrect-version-number.desc --- lintian-2.93.0/tags/s/source-nmu-has-incorrect-version-number.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/source-nmu-has-incorrect-version-number.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,14 @@ +Tag: source-nmu-has-incorrect-version-number +Severity: warning +Check: nmu +Info: A source NMU should have a Debian revision of "-x.x" (or "+nmuX" for a + native package). This is to prevent stealing version numbers from the + maintainer. + . + Maybe you didn't intend this upload to be a NMU, in that case, please + double-check that the most recent entry in the changelog is byte-for-byte + identical to the maintainer or one of the uploaders. If this is a local + package (not intended for Debian), you can suppress this warning by + putting "local" in the version number or "local package" on the first + line of the changelog entry. +Ref: devref 5.11.2 diff -Nru lintian-2.93.0/tags/s/source-nmu-has-incorrect-version-number.tag lintian-2.89.0ubuntu1/tags/s/source-nmu-has-incorrect-version-number.tag --- lintian-2.93.0/tags/s/source-nmu-has-incorrect-version-number.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/source-nmu-has-incorrect-version-number.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,14 +0,0 @@ -Tag: source-nmu-has-incorrect-version-number -Severity: warning -Check: nmu -Explanation: A source NMU should have a Debian revision of "-x.x" (or "+nmuX" for a - native package). This is to prevent stealing version numbers from the - maintainer. - . - Maybe you didn't intend this upload to be a NMU, in that case, please - double-check that the most recent entry in the changelog is byte-for-byte - identical to the maintainer or one of the uploaders. If this is a local - package (not intended for Debian), you can suppress this warning by - putting "local" in the version number or "local package" on the first - line of the changelog entry. -See-Also: devref 5.11.2 diff -Nru lintian-2.93.0/tags/s/source-only-upload-to-non-free-without-autobuild.desc lintian-2.89.0ubuntu1/tags/s/source-only-upload-to-non-free-without-autobuild.desc --- lintian-2.93.0/tags/s/source-only-upload-to-non-free-without-autobuild.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/source-only-upload-to-non-free-without-autobuild.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,11 @@ +Tag: source-only-upload-to-non-free-without-autobuild +Severity: error +Check: debian/control +Info: For licensing reasons packages from the non-free section are not + built by the autobuilders by default, so this source-upload to + "non-free" will result in the package never appearing in the archive. + . + Please either perform a regular binary upload or (after checking the + license) add XS-Autobuild: yes into the header part of + debian/control and get the package added to the "autobuild" whitelist. +Ref: devref 5.10.5 diff -Nru lintian-2.93.0/tags/s/source-only-upload-to-non-free-without-autobuild.tag lintian-2.89.0ubuntu1/tags/s/source-only-upload-to-non-free-without-autobuild.tag --- lintian-2.93.0/tags/s/source-only-upload-to-non-free-without-autobuild.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/source-only-upload-to-non-free-without-autobuild.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,11 +0,0 @@ -Tag: source-only-upload-to-non-free-without-autobuild -Severity: error -Check: debian/control -Explanation: For licensing reasons packages from the non-free section are not - built by the autobuilders by default, so this source-upload to - "non-free" will result in the package never appearing in the archive. - . - Please either perform a regular binary upload or (after checking the - license) add XS-Autobuild: yes into the header part of - debian/control and get the package added to the "autobuild" whitelist. -See-Also: devref 5.10.5 diff -Nru lintian-2.93.0/tags/s/source-package-component-has-long-file-name.desc lintian-2.89.0ubuntu1/tags/s/source-package-component-has-long-file-name.desc --- lintian-2.93.0/tags/s/source-package-component-has-long-file-name.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/source-package-component-has-long-file-name.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: source-package-component-has-long-file-name +Severity: warning +Check: filename-length +Info: The source package has a component with a very long filename. + This may complicate shipping the package on some media that put + restrictions on the length of the filenames (such as CDs). + . + Lintian only checks emits this tag once per source package based + on the component with the longest filename. +Ref: https://lists.debian.org/debian-devel/2011/03/msg00943.html diff -Nru lintian-2.93.0/tags/s/source-package-component-has-long-file-name.tag lintian-2.89.0ubuntu1/tags/s/source-package-component-has-long-file-name.tag --- lintian-2.93.0/tags/s/source-package-component-has-long-file-name.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/source-package-component-has-long-file-name.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,10 +0,0 @@ -Tag: source-package-component-has-long-file-name -Severity: warning -Check: filename-length -Explanation: The source package has a component with a very long filename. - This may complicate shipping the package on some media that put - restrictions on the length of the filenames (such as CDs). - . - Lintian only checks emits this tag once per source package based - on the component with the longest filename. -See-Also: https://lists.debian.org/debian-devel/2011/03/msg00943.html diff -Nru lintian-2.93.0/tags/s/source-package-encodes-python-version.desc lintian-2.89.0ubuntu1/tags/s/source-package-encodes-python-version.desc --- lintian-2.93.0/tags/s/source-package-encodes-python-version.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/source-package-encodes-python-version.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,12 @@ +Tag: source-package-encodes-python-version +Severity: warning +Check: languages/python +Info: This source package encodes a Python version in its name such + as python2-foo or python3-bar. + . + This could result in a misleading future situation where this source + package supports multiple versions as well unnecessary given that the + binary package names will typically encode the supported versions. + . + Please override this tag with a suitably-commented override if + there is no single upstream codebase that supports both versions. diff -Nru lintian-2.93.0/tags/s/source-package-encodes-python-version.tag lintian-2.89.0ubuntu1/tags/s/source-package-encodes-python-version.tag --- lintian-2.93.0/tags/s/source-package-encodes-python-version.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/source-package-encodes-python-version.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,12 +0,0 @@ -Tag: source-package-encodes-python-version -Severity: warning -Check: languages/python -Explanation: This source package encodes a Python version in its name such - as python2-foo or python3-bar. - . - This could result in a misleading future situation where this source - package supports multiple versions as well unnecessary given that the - binary package names will typically encode the supported versions. - . - Please override this tag with a suitably-commented override if - there is no single upstream codebase that supports both versions. diff -Nru lintian-2.93.0/tags/s/space-in-std-shortname-in-dep5-copyright.desc lintian-2.89.0ubuntu1/tags/s/space-in-std-shortname-in-dep5-copyright.desc --- lintian-2.93.0/tags/s/space-in-std-shortname-in-dep5-copyright.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/space-in-std-shortname-in-dep5-copyright.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: space-in-std-shortname-in-dep5-copyright +Severity: warning +Check: debian/copyright/dep5 +Ref: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ +Info: The “License” field contains a short name with a space, which + does not conform to the specification. diff -Nru lintian-2.93.0/tags/s/space-in-std-shortname-in-dep5-copyright.tag lintian-2.89.0ubuntu1/tags/s/space-in-std-shortname-in-dep5-copyright.tag --- lintian-2.93.0/tags/s/space-in-std-shortname-in-dep5-copyright.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/space-in-std-shortname-in-dep5-copyright.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: space-in-std-shortname-in-dep5-copyright -Severity: warning -Check: debian/copyright/dep5 -See-Also: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ -Explanation: The “License” field contains a short name with a space, which - does not conform to the specification. diff -Nru lintian-2.93.0/tags/s/spare-manual-page.desc lintian-2.89.0ubuntu1/tags/s/spare-manual-page.desc --- lintian-2.93.0/tags/s/spare-manual-page.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/spare-manual-page.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,11 @@ +Tag: spare-manual-page +Severity: info +Check: documentation/manual +Renamed-From: manpage-without-executable +Info: Each manual page in /usr/share/man should have a reason to be + there. This manual page does not appear to have a valid reason to be shipped. + . + For manual pages in sections 1 and 8, an executable (or a link to one) should + exist. This check currently considers all installation packages created + by the same sources, as long as they are present. +Ref: policy 12.1, #583125 diff -Nru lintian-2.93.0/tags/s/spare-manual-page.tag lintian-2.89.0ubuntu1/tags/s/spare-manual-page.tag --- lintian-2.93.0/tags/s/spare-manual-page.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/spare-manual-page.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,11 +0,0 @@ -Tag: spare-manual-page -Severity: info -Check: documentation/manual -Renamed-From: manpage-without-executable -Explanation: Each manual page in /usr/share/man should have a reason to be - there. This manual page does not appear to have a valid reason to be shipped. - . - For manual pages in sections 1 and 8, an executable (or a link to one) should - exist. This check currently considers all installation packages created - by the same sources, as long as they are present. -See-Also: policy 12.1, Bug#583125 diff -Nru lintian-2.93.0/tags/s/special-file.desc lintian-2.89.0ubuntu1/tags/s/special-file.desc --- lintian-2.93.0/tags/s/special-file.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/special-file.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: special-file +Severity: error +Check: files/special +Info: The package contains a special file (e.g., a device file). + This is forbidden by current policy. If your program needs this device, + you should create it by calling makedev from the postinst + script. +Ref: policy 10.6 diff -Nru lintian-2.93.0/tags/s/special-file.tag lintian-2.89.0ubuntu1/tags/s/special-file.tag --- lintian-2.93.0/tags/s/special-file.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/special-file.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: special-file -Severity: error -Check: files/special -Explanation: The package contains a *special* file (e.g., a device file). - This is forbidden by current policy. If your program needs this device, - you should create it by calling makedev from the postinst - script. -See-Also: policy 10.6 diff -Nru lintian-2.93.0/tags/s/specific-address-in-shared-library.desc lintian-2.89.0ubuntu1/tags/s/specific-address-in-shared-library.desc --- lintian-2.93.0/tags/s/specific-address-in-shared-library.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/specific-address-in-shared-library.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,20 @@ +Tag: specific-address-in-shared-library +Severity: error +Certainty: possible +Check: shared-libs +Ref: policy 10.2 +Renamed-From: shlib-with-non-pic-code +Info: The listed shared libraries contain object code that was compiled + without -fPIC. All object code in shared libraries should be recompiled + separately from the static libraries with the -fPIC option. + . + Another common mistake that causes this problem is linking with + gcc -Wl,-shared instead of gcc -shared. + . + In some cases, exceptions to this rule are warranted. If this is such a + case, follow the procedure outlined in Policy and then please document + the exception by adding a Lintian override to this package. + . + To check whether a shared library has this problem, run readelf + -d on the shared library. If a tag of type TEXTREL is present, the + shared library contains non-PIC code. diff -Nru lintian-2.93.0/tags/s/specific-address-in-shared-library.tag lintian-2.89.0ubuntu1/tags/s/specific-address-in-shared-library.tag --- lintian-2.93.0/tags/s/specific-address-in-shared-library.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/specific-address-in-shared-library.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,19 +0,0 @@ -Tag: specific-address-in-shared-library -Severity: error -Check: shared-libs -See-Also: policy 10.2 -Renamed-From: shlib-with-non-pic-code -Explanation: The listed shared libraries contain object code that was compiled - without -fPIC. All object code in shared libraries should be recompiled - separately from the static libraries with the -fPIC option. - . - Another common mistake that causes this problem is linking with - gcc -Wl,-shared instead of gcc -shared. - . - In some cases, exceptions to this rule are warranted. If this is such a - case, follow the procedure outlined in Policy and then please document - the exception by adding a Lintian override to this package. - . - To check whether a shared library has this problem, run readelf - -d on the shared library. If a tag of type TEXTREL is present, the - shared library contains non-PIC code. diff -Nru lintian-2.93.0/tags/s/spelling-error-in-binary.desc lintian-2.89.0ubuntu1/tags/s/spelling-error-in-binary.desc --- lintian-2.93.0/tags/s/spelling-error-in-binary.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/spelling-error-in-binary.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,20 @@ +Tag: spelling-error-in-binary +Severity: info +Certainty: wild-guess +Check: binaries +Info: Lintian found a spelling error in the given binary. Lintian has a + list of common misspellings that it looks for. It does not have a + dictionary like a spelling checker does. + . + If the string containing the spelling error is translated with the help + of gettext or a similar tool, please fix the error in the translations as + well as the English text to avoid making the translations fuzzy. With + gettext, for example, this means you should also fix the spelling mistake + in the corresponding msgids in the *.po files. + . + You can often find the word in the source code by running: + . + grep -rw <word> <source-tree> + . + This tag may produce false positives for words that contain non-ASCII + characters due to limitations in strings. diff -Nru lintian-2.93.0/tags/s/spelling-error-in-binary.tag lintian-2.89.0ubuntu1/tags/s/spelling-error-in-binary.tag --- lintian-2.93.0/tags/s/spelling-error-in-binary.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/spelling-error-in-binary.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,19 +0,0 @@ -Tag: spelling-error-in-binary -Severity: info -Check: binaries -Explanation: Lintian found a spelling error in the given binary. Lintian has a - list of common misspellings that it looks for. It does not have a - dictionary like a spelling checker does. - . - If the string containing the spelling error is translated with the help - of gettext or a similar tool, please fix the error in the translations as - well as the English text to avoid making the translations fuzzy. With - gettext, for example, this means you should also fix the spelling mistake - in the corresponding msgids in the *.po files. - . - You can often find the word in the source code by running: - . - grep -rw <word> <source-tree> - . - This tag may produce false positives for words that contain non-ASCII - characters due to limitations in strings. diff -Nru lintian-2.93.0/tags/s/spelling-error-in-changelog.desc lintian-2.89.0ubuntu1/tags/s/spelling-error-in-changelog.desc --- lintian-2.93.0/tags/s/spelling-error-in-changelog.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/spelling-error-in-changelog.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: spelling-error-in-changelog +Severity: warning +Check: debian/changelog +Info: Lintian found a spelling error in the latest entry of the Debian + changelog. Lintian has a list of common misspellings that it looks for. + It does not have a dictionary like a spelling checker does. + . + When writing a changelog entry for a spelling fix that includes the + misspelling, ensure the word "spelling" is on the same line as the + misspelled word to avoid triggering this warning. diff -Nru lintian-2.93.0/tags/s/spelling-error-in-changelog.tag lintian-2.89.0ubuntu1/tags/s/spelling-error-in-changelog.tag --- lintian-2.93.0/tags/s/spelling-error-in-changelog.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/spelling-error-in-changelog.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,10 +0,0 @@ -Tag: spelling-error-in-changelog -Severity: warning -Check: debian/changelog -Explanation: Lintian found a spelling error in the latest entry of the Debian - changelog. Lintian has a list of common misspellings that it looks for. - It does not have a dictionary like a spelling checker does. - . - When writing a changelog entry for a spelling fix that includes the - misspelling, ensure the word "spelling" is on the same line as the - misspelled word to avoid triggering this warning. diff -Nru lintian-2.93.0/tags/s/spelling-error-in-copyright.desc lintian-2.89.0ubuntu1/tags/s/spelling-error-in-copyright.desc --- lintian-2.93.0/tags/s/spelling-error-in-copyright.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/spelling-error-in-copyright.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: spelling-error-in-copyright +Severity: info +Certainty: possible +Check: debian/copyright +Info: Lintian found a spelling error in the copyright file. Lintian has a + list of common misspellings that it looks for. It does not have a + dictionary like a spelling checker does. If this is a spelling error in + the upstream license, in supporting email messages, or a case of Lintian + being confused by non-English text, add an override. diff -Nru lintian-2.93.0/tags/s/spelling-error-in-copyright.tag lintian-2.89.0ubuntu1/tags/s/spelling-error-in-copyright.tag --- lintian-2.93.0/tags/s/spelling-error-in-copyright.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/spelling-error-in-copyright.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: spelling-error-in-copyright -Severity: pedantic -Check: debian/copyright -Explanation: Lintian found a spelling error in the copyright file. Lintian has a - list of common misspellings that it looks for. It does not have a - dictionary like a spelling checker does. If this is a spelling error in - the upstream license, in supporting email messages, or a case of Lintian - being confused by non-English text, add an override. diff -Nru lintian-2.93.0/tags/s/spelling-error-in-description.desc lintian-2.89.0ubuntu1/tags/s/spelling-error-in-description.desc --- lintian-2.93.0/tags/s/spelling-error-in-description.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/spelling-error-in-description.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: spelling-error-in-description +Severity: warning +Check: fields/description +Info: Lintian found a spelling error in the package description. Lintian + has a list of common misspellings that it looks for. It does not have a + dictionary like a spelling checker does. It is particularly picky about + spelling and capitalization in package descriptions since they're very + visible to end users. diff -Nru lintian-2.93.0/tags/s/spelling-error-in-description-synopsis.desc lintian-2.89.0ubuntu1/tags/s/spelling-error-in-description-synopsis.desc --- lintian-2.93.0/tags/s/spelling-error-in-description-synopsis.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/spelling-error-in-description-synopsis.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: spelling-error-in-description-synopsis +Severity: warning +Check: fields/description +Info: Lintian found a spelling error in the package synopsis. Lintian + has a list of common misspellings that it looks for. It does not have a + dictionary like a spelling checker does. It is particularly picky about + spelling and capitalization in package descriptions since they're very + visible to end users. diff -Nru lintian-2.93.0/tags/s/spelling-error-in-description-synopsis.tag lintian-2.89.0ubuntu1/tags/s/spelling-error-in-description-synopsis.tag --- lintian-2.93.0/tags/s/spelling-error-in-description-synopsis.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/spelling-error-in-description-synopsis.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: spelling-error-in-description-synopsis -Severity: info -Check: fields/description -Explanation: Lintian found a spelling error in the package synopsis. Lintian - has a list of common misspellings that it looks for. It does not have a - dictionary like a spelling checker does. It is particularly picky about - spelling and capitalization in package descriptions since they're very - visible to end users. diff -Nru lintian-2.93.0/tags/s/spelling-error-in-description.tag lintian-2.89.0ubuntu1/tags/s/spelling-error-in-description.tag --- lintian-2.93.0/tags/s/spelling-error-in-description.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/spelling-error-in-description.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: spelling-error-in-description -Severity: info -Check: fields/description -Explanation: Lintian found a spelling error in the package description. Lintian - has a list of common misspellings that it looks for. It does not have a - dictionary like a spelling checker does. It is particularly picky about - spelling and capitalization in package descriptions since they're very - visible to end users. diff -Nru lintian-2.93.0/tags/s/spelling-error-in-doc-base-abstract-field.desc lintian-2.89.0ubuntu1/tags/s/spelling-error-in-doc-base-abstract-field.desc --- lintian-2.93.0/tags/s/spelling-error-in-doc-base-abstract-field.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/spelling-error-in-doc-base-abstract-field.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: spelling-error-in-doc-base-abstract-field +Severity: warning +Check: menus +Info: Lintian found a spelling, grammar or capitalization error in the + Abstract field of this doc-base control file. Lintian has a list of + common misspellings that looks for. It does not have a dictionary like a + spelling checker does. diff -Nru lintian-2.93.0/tags/s/spelling-error-in-doc-base-abstract-field.tag lintian-2.89.0ubuntu1/tags/s/spelling-error-in-doc-base-abstract-field.tag --- lintian-2.93.0/tags/s/spelling-error-in-doc-base-abstract-field.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/spelling-error-in-doc-base-abstract-field.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: spelling-error-in-doc-base-abstract-field -Severity: pedantic -Check: menus -Explanation: Lintian found a spelling, grammar or capitalization error in the - Abstract field of this doc-base control file. Lintian has a list of - common misspellings that looks for. It does not have a dictionary like a - spelling checker does. diff -Nru lintian-2.93.0/tags/s/spelling-error-in-doc-base-title-field.desc lintian-2.89.0ubuntu1/tags/s/spelling-error-in-doc-base-title-field.desc --- lintian-2.93.0/tags/s/spelling-error-in-doc-base-title-field.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/spelling-error-in-doc-base-title-field.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: spelling-error-in-doc-base-title-field +Severity: warning +Check: menus +Info: Lintian found a spelling, grammar or capitalization error in the + Title field of this doc-base control file. Lintian has a list of common + misspellings that it looks for. It does not have a dictionary like a + spelling checker does. diff -Nru lintian-2.93.0/tags/s/spelling-error-in-doc-base-title-field.tag lintian-2.89.0ubuntu1/tags/s/spelling-error-in-doc-base-title-field.tag --- lintian-2.93.0/tags/s/spelling-error-in-doc-base-title-field.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/spelling-error-in-doc-base-title-field.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: spelling-error-in-doc-base-title-field -Severity: pedantic -Check: menus -Explanation: Lintian found a spelling, grammar or capitalization error in the - Title field of this doc-base control file. Lintian has a list of common - misspellings that it looks for. It does not have a dictionary like a - spelling checker does. diff -Nru lintian-2.93.0/tags/s/spelling-error-in-news-debian.desc lintian-2.89.0ubuntu1/tags/s/spelling-error-in-news-debian.desc --- lintian-2.93.0/tags/s/spelling-error-in-news-debian.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/spelling-error-in-news-debian.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: spelling-error-in-news-debian +Severity: warning +Check: debian/changelog +Info: Lintian found a spelling error in the latest entry of the + NEWS.Debian file. Lintian has a list of common misspellings that it + looks for. It does not have a dictionary like a spelling checker does. diff -Nru lintian-2.93.0/tags/s/spelling-error-in-news-debian.tag lintian-2.89.0ubuntu1/tags/s/spelling-error-in-news-debian.tag --- lintian-2.93.0/tags/s/spelling-error-in-news-debian.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/spelling-error-in-news-debian.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: spelling-error-in-news-debian -Severity: pedantic -Check: debian/changelog -Explanation: Lintian found a spelling error in the latest entry of the - NEWS.Debian file. Lintian has a list of common misspellings that it - looks for. It does not have a dictionary like a spelling checker does. diff -Nru lintian-2.93.0/tags/s/spelling-error-in-patch-description.desc lintian-2.89.0ubuntu1/tags/s/spelling-error-in-patch-description.desc --- lintian-2.93.0/tags/s/spelling-error-in-patch-description.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/spelling-error-in-patch-description.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: spelling-error-in-patch-description +Severity: warning +Check: debian/patches/quilt +Info: Lintian found a spelling, grammar or capitalization error in the + description for this patch. Lintian has a list of common misspellings + that it looks for. It does not have a dictionary like a spelling checker + does. + . + Patch filenames or descriptions that refer to "spelling" or "typo" (or + similar) are ignored by Lintian. diff -Nru lintian-2.93.0/tags/s/spelling-error-in-patch-description.tag lintian-2.89.0ubuntu1/tags/s/spelling-error-in-patch-description.tag --- lintian-2.93.0/tags/s/spelling-error-in-patch-description.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/spelling-error-in-patch-description.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,10 +0,0 @@ -Tag: spelling-error-in-patch-description -Severity: pedantic -Check: debian/patches/quilt -Explanation: Lintian found a spelling, grammar or capitalization error in the - description for this patch. Lintian has a list of common misspellings - that it looks for. It does not have a dictionary like a spelling checker - does. - . - Patch filenames or descriptions that refer to "spelling" or "typo" (or - similar) are ignored by Lintian. diff -Nru lintian-2.93.0/tags/s/spelling-error-in-readme-debian.desc lintian-2.89.0ubuntu1/tags/s/spelling-error-in-readme-debian.desc --- lintian-2.93.0/tags/s/spelling-error-in-readme-debian.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/spelling-error-in-readme-debian.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: spelling-error-in-readme-debian +Severity: warning +Check: debian/readme +Info: Lintian found a spelling error in the README.Debian file. Lintian + has a list of common misspellings that it looks for. It does not have a + dictionary like a spelling checker does. diff -Nru lintian-2.93.0/tags/s/spelling-error-in-readme-debian.tag lintian-2.89.0ubuntu1/tags/s/spelling-error-in-readme-debian.tag --- lintian-2.93.0/tags/s/spelling-error-in-readme-debian.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/spelling-error-in-readme-debian.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: spelling-error-in-readme-debian -Severity: pedantic -Check: debian/readme -Explanation: Lintian found a spelling error in the README.Debian file. Lintian - has a list of common misspellings that it looks for. It does not have a - dictionary like a spelling checker does. diff -Nru lintian-2.93.0/tags/s/spelling-error-in-rules-requires-root.desc lintian-2.89.0ubuntu1/tags/s/spelling-error-in-rules-requires-root.desc --- lintian-2.93.0/tags/s/spelling-error-in-rules-requires-root.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/spelling-error-in-rules-requires-root.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: spelling-error-in-rules-requires-root +Severity: warning +Check: debian/control +Info: This source package attempts to specify a + Rules-Requires-Root field but appears to mispell the field. + . + Please rename the field to Rules-Requires-Root. diff -Nru lintian-2.93.0/tags/s/spelling-error-in-rules-requires-root.tag lintian-2.89.0ubuntu1/tags/s/spelling-error-in-rules-requires-root.tag --- lintian-2.93.0/tags/s/spelling-error-in-rules-requires-root.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/spelling-error-in-rules-requires-root.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: spelling-error-in-rules-requires-root -Severity: warning -Check: debian/control -Explanation: This source package attempts to specify a - Rules-Requires-Root field but appears to mispell the field. - . - Please rename the field to Rules-Requires-Root. diff -Nru lintian-2.93.0/tags/s/spelling-in-override-comment.desc lintian-2.89.0ubuntu1/tags/s/spelling-in-override-comment.desc --- lintian-2.93.0/tags/s/spelling-in-override-comment.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/spelling-in-override-comment.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: spelling-in-override-comment +Severity: warning +Check: debian/lintian-overrides/comments +Info: The comment attached to a Lintian override contains a spelling + error. + . + Lintian looks for common misspelling. It does not have a dictionary. diff -Nru lintian-2.93.0/tags/s/spelling-in-override-comment.tag lintian-2.89.0ubuntu1/tags/s/spelling-in-override-comment.tag --- lintian-2.93.0/tags/s/spelling-in-override-comment.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/spelling-in-override-comment.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: spelling-in-override-comment -Severity: pedantic -Check: debian/lintian-overrides/comments -Explanation: The comment attached to a Lintian override contains a spelling - error. - . - Lintian looks for common misspelling. It does not have a dictionary. diff -Nru lintian-2.93.0/tags/s/sphinxdoc-but-no-sphinxdoc-depends.desc lintian-2.89.0ubuntu1/tags/s/sphinxdoc-but-no-sphinxdoc-depends.desc --- lintian-2.93.0/tags/s/sphinxdoc-but-no-sphinxdoc-depends.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/sphinxdoc-but-no-sphinxdoc-depends.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,15 @@ +Tag: sphinxdoc-but-no-sphinxdoc-depends +Severity: warning +Certainty: possible +Check: debhelper +Ref: dh_sphinxdoc(1) +Info: The source package uses Sphinx via --with sphinxdoc or + dh_sphinxdoc but no binary package specifies + ${sphinxdoc:Depends} as a dependency. + . + The sphinxdoc helper is being used to make links to various + common files from other binary packages that are injected via the + ${sphinxdoc:Depends} substitution variable. + . + Please add ${sphinxdoc:Depends} to the relevant binary + package. diff -Nru lintian-2.93.0/tags/s/sphinxdoc-but-no-sphinxdoc-depends.tag lintian-2.89.0ubuntu1/tags/s/sphinxdoc-but-no-sphinxdoc-depends.tag --- lintian-2.93.0/tags/s/sphinxdoc-but-no-sphinxdoc-depends.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/sphinxdoc-but-no-sphinxdoc-depends.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,14 +0,0 @@ -Tag: sphinxdoc-but-no-sphinxdoc-depends -Severity: warning -Check: debhelper -See-Also: dh_sphinxdoc(1) -Explanation: The source package uses Sphinx via --with sphinxdoc or - dh_sphinxdoc but no binary package specifies - ${sphinxdoc:Depends} as a dependency. - . - The sphinxdoc helper is being used to make links to various - common files from other binary packages that are injected via the - ${sphinxdoc:Depends} substitution variable. - . - Please add ${sphinxdoc:Depends} to the relevant binary - package. diff -Nru lintian-2.93.0/tags/s/spurious-fields-in-upstream-signature.desc lintian-2.89.0ubuntu1/tags/s/spurious-fields-in-upstream-signature.desc --- lintian-2.93.0/tags/s/spurious-fields-in-upstream-signature.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/spurious-fields-in-upstream-signature.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: spurious-fields-in-upstream-signature +Severity: info +Check: upstream-signature +Info: The packaging includes a detached upstream signature file that contains + spurious fields like Comment: or Version:. They are + sometimes added by gpg --enarmor, especially if you have an older + version. Modern versions only add a Comment: field. + . + Please generate the signature with gpg --armor --detach-sig using a + modern version instead. diff -Nru lintian-2.93.0/tags/s/spurious-fields-in-upstream-signature.tag lintian-2.89.0ubuntu1/tags/s/spurious-fields-in-upstream-signature.tag --- lintian-2.93.0/tags/s/spurious-fields-in-upstream-signature.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/spurious-fields-in-upstream-signature.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,10 +0,0 @@ -Tag: spurious-fields-in-upstream-signature -Severity: info -Check: upstream-signature -Explanation: The packaging includes a detached upstream signature file that contains - spurious fields like Comment: or Version:. They are - sometimes added by gpg --enarmor, especially if you have an older - version. Modern versions only add a Comment: field. - . - Please generate the signature with gpg --armor --detach-sig using a - modern version instead. diff -Nru lintian-2.93.0/tags/s/standards-version.desc lintian-2.89.0ubuntu1/tags/s/standards-version.desc --- lintian-2.93.0/tags/s/standards-version.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/standards-version.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,5 @@ +Tag: standards-version +Severity: classification +Check: fields/standards-version +Info: The standards version of the package according to + Standards-Version field in the debian/control file. diff -Nru lintian-2.93.0/tags/s/standards-version.tag lintian-2.89.0ubuntu1/tags/s/standards-version.tag --- lintian-2.93.0/tags/s/standards-version.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/standards-version.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,5 +0,0 @@ -Tag: standards-version -Severity: classification -Check: fields/standards-version -Explanation: The standards version of the package according to - Standards-Version field in the debian/control file. diff -Nru lintian-2.93.0/tags/s/star-file.desc lintian-2.89.0ubuntu1/tags/s/star-file.desc --- lintian-2.93.0/tags/s/star-file.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/star-file.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: star-file +Severity: error +Certainty: possible +Check: files/names +Info: The given file is literally installed as * (star + symbol). Normally this indicates a mistake in the installation + process of the package either when creating symlinks or renaming files. diff -Nru lintian-2.93.0/tags/s/star-file.tag lintian-2.89.0ubuntu1/tags/s/star-file.tag --- lintian-2.93.0/tags/s/star-file.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/star-file.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: star-file -Severity: error -Check: files/names -Explanation: The given file is literally installed as * (star - symbol). Normally this indicates a mistake in the installation - process of the package either when creating symlinks or renaming files. diff -Nru lintian-2.93.0/tags/s/statically-linked-binary.desc lintian-2.89.0ubuntu1/tags/s/statically-linked-binary.desc --- lintian-2.93.0/tags/s/statically-linked-binary.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/statically-linked-binary.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: statically-linked-binary +Severity: error +Certainty: possible +Check: binaries +Info: The package installs a statically linked binary or object file. + . + Usually this is a bug. Otherwise, please add an override if your package + is an exception. Binaries named *-static and *.static are automatically + excluded, as are any binaries in packages named *-static. diff -Nru lintian-2.93.0/tags/s/statically-linked-binary.tag lintian-2.89.0ubuntu1/tags/s/statically-linked-binary.tag --- lintian-2.93.0/tags/s/statically-linked-binary.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/statically-linked-binary.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: statically-linked-binary -Severity: error -Check: binaries -Explanation: The package installs a statically linked binary or object file. - . - Usually this is a bug. Otherwise, please add an override if your package - is an exception. Binaries named *-static and *.static are automatically - excluded, as are any binaries in packages named *-static. diff -Nru lintian-2.93.0/tags/s/static-library-has-unneeded-section.desc lintian-2.89.0ubuntu1/tags/s/static-library-has-unneeded-section.desc --- lintian-2.93.0/tags/s/static-library-has-unneeded-section.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/static-library-has-unneeded-section.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,11 @@ +Tag: static-library-has-unneeded-section +Severity: info +Check: binaries +Info: The static library is stripped, but still contains a section + that is not useful. You should call strip with + --remove-section=.comment --remove-section=.note to remove the + .note and .comment sections. + . + dh_strip (after debhelper/9.20150811) will do this + automatically for you, but install -s will not because it calls + strip without any arguments. diff -Nru lintian-2.93.0/tags/s/static-library-has-unneeded-section.tag lintian-2.89.0ubuntu1/tags/s/static-library-has-unneeded-section.tag --- lintian-2.93.0/tags/s/static-library-has-unneeded-section.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/static-library-has-unneeded-section.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,11 +0,0 @@ -Tag: static-library-has-unneeded-section -Severity: info -Check: binaries -Explanation: The static library is stripped, but still contains a section - that is not useful. You should call strip with - --remove-section=.comment --remove-section=.note to remove the - .note and .comment sections. - . - dh_strip (after debhelper/9.20150811) will do this - automatically for you, but install -s will not because it calls - strip without any arguments. diff -Nru lintian-2.93.0/tags/s/stray-folder-in-manual.desc lintian-2.89.0ubuntu1/tags/s/stray-folder-in-manual.desc --- lintian-2.93.0/tags/s/stray-folder-in-manual.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/stray-folder-in-manual.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: stray-folder-in-manual +Severity: error +Check: documentation/manual +Renamed-Tag: stray-directory-in-manpage-directory +Info: This package installs a directory under /usr/share/man + that is not a manual section directory or locale directory. +Ref: fhs usrsharemanmanualpages diff -Nru lintian-2.93.0/tags/s/stray-folder-in-manual.tag lintian-2.89.0ubuntu1/tags/s/stray-folder-in-manual.tag --- lintian-2.93.0/tags/s/stray-folder-in-manual.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/stray-folder-in-manual.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: stray-folder-in-manual -Severity: error -Check: documentation/manual -Renamed-Tag: stray-directory-in-manpage-directory -Explanation: This package installs a directory under /usr/share/man - that is not a manual section directory or locale directory. -See-Also: fhs usrsharemanmanualpages diff -Nru lintian-2.93.0/tags/s/stray-translated-debconf-templates.desc lintian-2.89.0ubuntu1/tags/s/stray-translated-debconf-templates.desc --- lintian-2.93.0/tags/s/stray-translated-debconf-templates.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/stray-translated-debconf-templates.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: stray-translated-debconf-templates +Severity: warning +Check: debian/po-debconf +Info: This package contains a file named *templates.XX or + *templates.XX_XX. This was the naming convention for the translated + templates merged using debconf-mergetemplate. Since the package is using + po-debconf, these files should be replaced by language-specific files in + the debian/po directory and should no longer be needed. diff -Nru lintian-2.93.0/tags/s/stray-translated-debconf-templates.tag lintian-2.89.0ubuntu1/tags/s/stray-translated-debconf-templates.tag --- lintian-2.93.0/tags/s/stray-translated-debconf-templates.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/stray-translated-debconf-templates.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: stray-translated-debconf-templates -Severity: warning -Check: debian/po-debconf -Explanation: This package contains a file named *templates.XX or - *templates.XX_XX. This was the naming convention for the translated - templates merged using debconf-mergetemplate. Since the package is using - po-debconf, these files should be replaced by language-specific files in - the debian/po directory and should no longer be needed. diff -Nru lintian-2.93.0/tags/s/stripped-library.desc lintian-2.89.0ubuntu1/tags/s/stripped-library.desc --- lintian-2.93.0/tags/s/stripped-library.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/stripped-library.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: stripped-library +Severity: error +Check: binaries +Renamed-From: library-in-debug-or-profile-should-not-be-stripped +Info: Libraries in .../lib/debug or in + .../lib/profile must not be stripped; this defeats the whole + point of the separate library. diff -Nru lintian-2.93.0/tags/s/stripped-library.tag lintian-2.89.0ubuntu1/tags/s/stripped-library.tag --- lintian-2.93.0/tags/s/stripped-library.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/stripped-library.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: stripped-library -Severity: error -Check: binaries -Renamed-From: library-in-debug-or-profile-should-not-be-stripped -Explanation: Libraries in .../lib/debug or in - .../lib/profile must not be stripped; this defeats the whole - point of the separate library. diff -Nru lintian-2.93.0/tags/s/stronger-dependency-implies-weaker.desc lintian-2.89.0ubuntu1/tags/s/stronger-dependency-implies-weaker.desc --- lintian-2.93.0/tags/s/stronger-dependency-implies-weaker.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/stronger-dependency-implies-weaker.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,14 @@ +Tag: stronger-dependency-implies-weaker +Severity: warning +Check: debian/control +Ref: policy 7.2 +Info: In the debian/control stanza for the given package, a + stronger dependency field implies one of the dependencies in a weaker + dependency field. In other words, the Depends field of the package + requires that one of the packages listed in Recommends or Suggests be + installed, or a package is listed in Recommends as well as Suggests. + . + Current versions of dpkg-gencontrol will silently fix this problem by + removing the weaker dependency, but it may indicate a more subtle bug + (misspelling or forgetting to remove the stronger dependency when it was + moved to the weaker field). diff -Nru lintian-2.93.0/tags/s/stronger-dependency-implies-weaker.tag lintian-2.89.0ubuntu1/tags/s/stronger-dependency-implies-weaker.tag --- lintian-2.93.0/tags/s/stronger-dependency-implies-weaker.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/stronger-dependency-implies-weaker.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,14 +0,0 @@ -Tag: stronger-dependency-implies-weaker -Severity: warning -Check: debian/control -See-Also: policy 7.2 -Explanation: In the debian/control stanza for the given package, a - stronger dependency field implies one of the dependencies in a weaker - dependency field. In other words, the Depends field of the package - requires that one of the packages listed in Recommends or Suggests be - installed, or a package is listed in Recommends as well as Suggests. - . - Current versions of dpkg-gencontrol will silently fix this problem by - removing the weaker dependency, but it may indicate a more subtle bug - (misspelling or forgetting to remove the stronger dependency when it was - moved to the weaker field). diff -Nru lintian-2.93.0/tags/s/subdir-in-bin.desc lintian-2.89.0ubuntu1/tags/s/subdir-in-bin.desc --- lintian-2.93.0/tags/s/subdir-in-bin.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/subdir-in-bin.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: subdir-in-bin +Severity: error +Check: files/hierarchy/standard +Info: The Filesystem Hierarchy Standard forbids the installation of new + directories in /bin. +Ref: fhs binessentialusercommandbinaries diff -Nru lintian-2.93.0/tags/s/subdir-in-bin.tag lintian-2.89.0ubuntu1/tags/s/subdir-in-bin.tag --- lintian-2.93.0/tags/s/subdir-in-bin.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/subdir-in-bin.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: subdir-in-bin -Severity: error -Check: files/hierarchy/standard -Explanation: The Filesystem Hierarchy Standard forbids the installation of new - directories in /bin. -See-Also: fhs binessentialusercommandbinaries diff -Nru lintian-2.93.0/tags/s/subdir-in-usr-bin.desc lintian-2.89.0ubuntu1/tags/s/subdir-in-usr-bin.desc --- lintian-2.93.0/tags/s/subdir-in-usr-bin.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/subdir-in-usr-bin.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: subdir-in-usr-bin +Severity: error +Check: files/hierarchy/standard +Info: The Filesystem Hierarchy Standard forbids the installation of new + directories in /usr/bin other than /usr/bin/mh. +Ref: fhs usrbinmostusercommands diff -Nru lintian-2.93.0/tags/s/subdir-in-usr-bin.tag lintian-2.89.0ubuntu1/tags/s/subdir-in-usr-bin.tag --- lintian-2.93.0/tags/s/subdir-in-usr-bin.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/subdir-in-usr-bin.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: subdir-in-usr-bin -Severity: error -Check: files/hierarchy/standard -Explanation: The Filesystem Hierarchy Standard forbids the installation of new - directories in /usr/bin other than /usr/bin/mh. -See-Also: fhs usrbinmostusercommands diff -Nru lintian-2.93.0/tags/s/substvar-source-version-is-deprecated.desc lintian-2.89.0ubuntu1/tags/s/substvar-source-version-is-deprecated.desc --- lintian-2.93.0/tags/s/substvar-source-version-is-deprecated.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/substvar-source-version-is-deprecated.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: substvar-source-version-is-deprecated +Severity: warning +Check: debian/version-substvars +Info: The package uses the now deprecated ${Source-Version} substvar, + which has misleading semantics. Please switch to ${binary:Version} or + ${source:Version} as appropriate (introduced in dpkg 1.13.19, released + with etch). Support for ${Source-Version} may be removed from dpkg-dev + in the future. diff -Nru lintian-2.93.0/tags/s/substvar-source-version-is-deprecated.tag lintian-2.89.0ubuntu1/tags/s/substvar-source-version-is-deprecated.tag --- lintian-2.93.0/tags/s/substvar-source-version-is-deprecated.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/substvar-source-version-is-deprecated.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: substvar-source-version-is-deprecated -Severity: warning -Check: debian/version-substvars -Explanation: The package uses the now deprecated ${Source-Version} substvar, - which has misleading semantics. Please switch to ${binary:Version} or - ${source:Version} as appropriate (introduced in dpkg 1.13.19, released - with etch). Support for ${Source-Version} may be removed from dpkg-dev - in the future. diff -Nru lintian-2.93.0/tags/s/superfluous-clutter-in-homepage.desc lintian-2.89.0ubuntu1/tags/s/superfluous-clutter-in-homepage.desc --- lintian-2.93.0/tags/s/superfluous-clutter-in-homepage.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/superfluous-clutter-in-homepage.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: superfluous-clutter-in-homepage +Severity: warning +Check: fields/homepage +Info: The "Homepage:" field in this package's control file contains + superfluous markup around the URL, like enclosing < and >. + This is unnecessary and needlessly complicates using this information. +Ref: policy 5.6.23 diff -Nru lintian-2.93.0/tags/s/superfluous-clutter-in-homepage.tag lintian-2.89.0ubuntu1/tags/s/superfluous-clutter-in-homepage.tag --- lintian-2.93.0/tags/s/superfluous-clutter-in-homepage.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/superfluous-clutter-in-homepage.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: superfluous-clutter-in-homepage -Severity: warning -Check: fields/homepage -Explanation: The "Homepage:" field in this package's control file contains - superfluous markup around the URL, like enclosing < and >. - This is unnecessary and needlessly complicates using this information. -See-Also: policy 5.6.23 diff -Nru lintian-2.93.0/tags/s/surplus-shared-library-symbols.desc lintian-2.89.0ubuntu1/tags/s/surplus-shared-library-symbols.desc --- lintian-2.93.0/tags/s/surplus-shared-library-symbols.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/surplus-shared-library-symbols.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: surplus-shared-library-symbols +Severity: warning +Check: shared-libs +Renamed-From: unused-shlib-entry-in-symbols-control-file +Info: The symbols control file contains an entry for a shared library that + is not installed by this package. diff -Nru lintian-2.93.0/tags/s/surplus-shared-library-symbols.tag lintian-2.89.0ubuntu1/tags/s/surplus-shared-library-symbols.tag --- lintian-2.93.0/tags/s/surplus-shared-library-symbols.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/surplus-shared-library-symbols.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: surplus-shared-library-symbols -Severity: warning -Check: shared-libs -Renamed-From: unused-shlib-entry-in-symbols-control-file -Explanation: The symbols control file contains an entry for a shared library that - is not installed by this package. diff -Nru lintian-2.93.0/tags/s/su-to-root-with-usr-sbin.desc lintian-2.89.0ubuntu1/tags/s/su-to-root-with-usr-sbin.desc --- lintian-2.93.0/tags/s/su-to-root-with-usr-sbin.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/su-to-root-with-usr-sbin.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: su-to-root-with-usr-sbin +Severity: warning +Check: menu-format +Info: The menu item or desktop file command uses su-to-root as + /usr/sbin/su-to-root. Since sarge su-to-root is located in /usr/bin and + /usr/sbin/su-to-root is only a compatibility symlink that may get dropped + in the future. + . + Since su-to-root is now located in /usr/bin you can use it without + absolute path now. diff -Nru lintian-2.93.0/tags/s/su-to-root-with-usr-sbin.tag lintian-2.89.0ubuntu1/tags/s/su-to-root-with-usr-sbin.tag --- lintian-2.93.0/tags/s/su-to-root-with-usr-sbin.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/su-to-root-with-usr-sbin.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,10 +0,0 @@ -Tag: su-to-root-with-usr-sbin -Severity: warning -Check: menu-format -Explanation: The menu item or desktop file command uses su-to-root as - /usr/sbin/su-to-root. Since sarge su-to-root is located in /usr/bin and - /usr/sbin/su-to-root is only a compatibility symlink that may get dropped - in the future. - . - Since su-to-root is now located in /usr/bin you can use it without - absolute path now. diff -Nru lintian-2.93.0/tags/s/su-wrapper-not-su-to-root.desc lintian-2.89.0ubuntu1/tags/s/su-wrapper-not-su-to-root.desc --- lintian-2.93.0/tags/s/su-wrapper-not-su-to-root.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/su-wrapper-not-su-to-root.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: su-wrapper-not-su-to-root +Severity: warning +Check: menu-format +Info: The menu item or desktop file command uses an su wrapper other than + su-to-root. On Debian systems, please use su-to-root -X, which + will pick the correct wrapper based on what's installed on the system and + the current desktop environment. Using su-to-root is also important for + Live CD systems which need to use sudo rather than su. su-to-root + permits global configuration to use sudo. diff -Nru lintian-2.93.0/tags/s/su-wrapper-not-su-to-root.tag lintian-2.89.0ubuntu1/tags/s/su-wrapper-not-su-to-root.tag --- lintian-2.93.0/tags/s/su-wrapper-not-su-to-root.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/su-wrapper-not-su-to-root.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: su-wrapper-not-su-to-root -Severity: warning -Check: menu-format -Explanation: The menu item or desktop file command uses an su wrapper other than - su-to-root. On Debian systems, please use su-to-root -X, which - will pick the correct wrapper based on what's installed on the system and - the current desktop environment. Using su-to-root is also important for - Live CD systems which need to use sudo rather than su. su-to-root - permits global configuration to use sudo. diff -Nru lintian-2.93.0/tags/s/su-wrapper-without--c.desc lintian-2.89.0ubuntu1/tags/s/su-wrapper-without--c.desc --- lintian-2.93.0/tags/s/su-wrapper-without--c.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/su-wrapper-without--c.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: su-wrapper-without--c +Severity: error +Check: menu-format +Info: The menu item command or desktop file uses an su wrapper such as + su-to-root without the -c flag. This is a syntax error. +Ref: su-to-root(1) diff -Nru lintian-2.93.0/tags/s/su-wrapper-without--c.tag lintian-2.89.0ubuntu1/tags/s/su-wrapper-without--c.tag --- lintian-2.93.0/tags/s/su-wrapper-without--c.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/su-wrapper-without--c.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: su-wrapper-without--c -Severity: error -Check: menu-format -Explanation: The menu item command or desktop file uses an su wrapper such as - su-to-root without the -c flag. This is a syntax error. -See-Also: su-to-root(1) diff -Nru lintian-2.93.0/tags/s/svk-commit-file-in-package.desc lintian-2.89.0ubuntu1/tags/s/svk-commit-file-in-package.desc --- lintian-2.93.0/tags/s/svk-commit-file-in-package.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/svk-commit-file-in-package.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: svk-commit-file-in-package +Severity: warning +Check: files/vcs +Info: The package contains an svk-commitNNN.tmp file. This file is almost + certainly a left-over from a failed Subversion commit, and does not + belong in a Debian package. diff -Nru lintian-2.93.0/tags/s/svk-commit-file-in-package.tag lintian-2.89.0ubuntu1/tags/s/svk-commit-file-in-package.tag --- lintian-2.93.0/tags/s/svk-commit-file-in-package.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/svk-commit-file-in-package.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: svk-commit-file-in-package -Severity: warning -Check: files/vcs -Explanation: The package contains an svk-commitNNN.tmp file. This file is almost - certainly a left-over from a failed Subversion commit, and does not - belong in a Debian package. diff -Nru lintian-2.93.0/tags/s/svn-commit-file-in-package.desc lintian-2.89.0ubuntu1/tags/s/svn-commit-file-in-package.desc --- lintian-2.93.0/tags/s/svn-commit-file-in-package.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/svn-commit-file-in-package.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: svn-commit-file-in-package +Severity: warning +Check: files/vcs +Info: The package contains an svn-commit(.NNN).tmp file. This file is + almost certainly a left-over from a failed Subversion commit, and does + not belong in a Debian package. diff -Nru lintian-2.93.0/tags/s/svn-commit-file-in-package.tag lintian-2.89.0ubuntu1/tags/s/svn-commit-file-in-package.tag --- lintian-2.93.0/tags/s/svn-commit-file-in-package.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/svn-commit-file-in-package.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: svn-commit-file-in-package -Severity: warning -Check: files/vcs -Explanation: The package contains an svn-commit(.NNN).tmp file. This file is - almost certainly a left-over from a failed Subversion commit, and does - not belong in a Debian package. diff -Nru lintian-2.93.0/tags/s/symbols-declares-dependency-on-other-package.desc lintian-2.89.0ubuntu1/tags/s/symbols-declares-dependency-on-other-package.desc --- lintian-2.93.0/tags/s/symbols-declares-dependency-on-other-package.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/symbols-declares-dependency-on-other-package.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,16 @@ +Tag: symbols-declares-dependency-on-other-package +Severity: warning +Certainty: possible +Check: shared-libs +Info: This package declares in its symbols control file a dependency on + some other package (and not one listed in the Provides of this package). + . + Packages should normally only list in their symbols control file the + shared libraries included in that package, and therefore the dependencies + listed there should normally be satisfied by either the package itself or + one of its Provides. + . + In unusual circumstances where it's necessary to declare more complex + dependencies in the symbols control file, please add a Lintian override + for this warning. +Ref: policy 8.6 diff -Nru lintian-2.93.0/tags/s/symbols-declares-dependency-on-other-package.tag lintian-2.89.0ubuntu1/tags/s/symbols-declares-dependency-on-other-package.tag --- lintian-2.93.0/tags/s/symbols-declares-dependency-on-other-package.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/symbols-declares-dependency-on-other-package.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,15 +0,0 @@ -Tag: symbols-declares-dependency-on-other-package -Severity: warning -Check: shared-libs -Explanation: This package declares in its symbols control file a dependency on - some other package (and not one listed in the Provides of this package). - . - Packages should normally only list in their symbols control file the - shared libraries included in that package, and therefore the dependencies - listed there should normally be satisfied by either the package itself or - one of its Provides. - . - In unusual circumstances where it's necessary to declare more complex - dependencies in the symbols control file, please add a Lintian override - for this warning. -See-Also: policy 8.6 diff -Nru lintian-2.93.0/tags/s/symbols-file-contains-current-version-with-debian-revision.desc lintian-2.89.0ubuntu1/tags/s/symbols-file-contains-current-version-with-debian-revision.desc --- lintian-2.93.0/tags/s/symbols-file-contains-current-version-with-debian-revision.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/symbols-file-contains-current-version-with-debian-revision.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,15 @@ +Tag: symbols-file-contains-current-version-with-debian-revision +Severity: error +Check: shared-libs +Info: Debian revisions should be stripped from versions in symbols files. + Not doing so leads to dependencies unsatisfiable by backports (1.0-1~bpo + << 1.0-1 while 1.0-1~bpo >= 1.0). If the Debian revision can't + be stripped because the symbol really appeared between two specific + Debian revisions, you should postfix the version with a single "~" + (example: 1.0-3~ if the symbol appeared in 1.0-3). + . + This problem normally means that the symbols were added automatically by + dpkg-gensymbols. dpkg-gensymbols uses the full version number for the + dependency associated to any new symbol that it detects. The maintainer + must update the debian/<package>.symbols file by adding + the new symbols with the corresponding upstream version. diff -Nru lintian-2.93.0/tags/s/symbols-file-contains-current-version-with-debian-revision.tag lintian-2.89.0ubuntu1/tags/s/symbols-file-contains-current-version-with-debian-revision.tag --- lintian-2.93.0/tags/s/symbols-file-contains-current-version-with-debian-revision.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/symbols-file-contains-current-version-with-debian-revision.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,15 +0,0 @@ -Tag: symbols-file-contains-current-version-with-debian-revision -Severity: error -Check: shared-libs -Explanation: Debian revisions should be stripped from versions in symbols files. - Not doing so leads to dependencies unsatisfiable by backports (1.0-1~bpo - << 1.0-1 while 1.0-1~bpo >= 1.0). If the Debian revision can't - be stripped because the symbol really appeared between two specific - Debian revisions, you should postfix the version with a single "~" - (example: 1.0-3~ if the symbol appeared in 1.0-3). - . - This problem normally means that the symbols were added automatically by - dpkg-gensymbols. dpkg-gensymbols uses the full version number for the - dependency associated to any new symbol that it detects. The maintainer - must update the debian/<package>.symbols file by adding - the new symbols with the corresponding upstream version. diff -Nru lintian-2.93.0/tags/s/symbols-file-contains-debian-revision.desc lintian-2.89.0ubuntu1/tags/s/symbols-file-contains-debian-revision.desc --- lintian-2.93.0/tags/s/symbols-file-contains-debian-revision.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/symbols-file-contains-debian-revision.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: symbols-file-contains-debian-revision +Severity: warning +Check: shared-libs +Info: Debian revisions should be stripped from versions in symbols files. + Not doing so leads to dependencies unsatisfiable by backports (1.0-1~bpo + << 1.0-1 while 1.0-1~bpo >= 1.0). If the Debian revision can't + be stripped because the symbol really appeared between two specific + Debian revisions, you should postfix the version with a single "~" + (example: 1.0-3~ if the symbol appeared in 1.0-3). +Ref: dpkg-gensymbols(1), https://wiki.debian.org/UsingSymbolsFiles diff -Nru lintian-2.93.0/tags/s/symbols-file-contains-debian-revision.tag lintian-2.89.0ubuntu1/tags/s/symbols-file-contains-debian-revision.tag --- lintian-2.93.0/tags/s/symbols-file-contains-debian-revision.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/symbols-file-contains-debian-revision.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,10 +0,0 @@ -Tag: symbols-file-contains-debian-revision -Severity: warning -Check: shared-libs -Explanation: Debian revisions should be stripped from versions in symbols files. - Not doing so leads to dependencies unsatisfiable by backports (1.0-1~bpo - << 1.0-1 while 1.0-1~bpo >= 1.0). If the Debian revision can't - be stripped because the symbol really appeared between two specific - Debian revisions, you should postfix the version with a single "~" - (example: 1.0-3~ if the symbol appeared in 1.0-3). -See-Also: dpkg-gensymbols(1), https://wiki.debian.org/UsingSymbolsFiles diff -Nru lintian-2.93.0/tags/s/symbols-file-missing-build-depends-package-field.desc lintian-2.89.0ubuntu1/tags/s/symbols-file-missing-build-depends-package-field.desc --- lintian-2.93.0/tags/s/symbols-file-missing-build-depends-package-field.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/symbols-file-missing-build-depends-package-field.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,25 @@ +Tag: symbols-file-missing-build-depends-package-field +Severity: info +Check: shared-libs +Info: The symbols file for this package does not contain a + Build-Depends-Package meta-information field. + . + This field specifies the name of the -dev package associated + to the library and is used by dpkg-shlibdeps(1) to make sure + that the dependency generated is at least as strict as the + corresponding build dependency. + . + This is useful as allows packages to not hardcode this information + multiple times. + . + Note that the format of deb-symbols(5) files requires that the + * Build-Depends-Package: line should start in column one of + the file and not be indented to align with the symbols themselves. + Please do not use the placeholder #PACKAGE#. The + development package for your shared library must be stated explicitly. +Ref: + policy 8.6.3.2, + deb-symbols(5), + dpkg-shlibdeps(1), + https://www.debian.org/doc/manuals/maint-guide/advanced.en.html#librarysymbols, + #944047 diff -Nru lintian-2.93.0/tags/s/symbols-file-missing-build-depends-package-field.tag lintian-2.89.0ubuntu1/tags/s/symbols-file-missing-build-depends-package-field.tag --- lintian-2.93.0/tags/s/symbols-file-missing-build-depends-package-field.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/symbols-file-missing-build-depends-package-field.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,25 +0,0 @@ -Tag: symbols-file-missing-build-depends-package-field -Severity: info -Check: shared-libs -Explanation: The symbols file for this package does not contain a - Build-Depends-Package meta-information field. - . - This field specifies the name of the -dev package associated - to the library and is used by dpkg-shlibdeps(1) to make sure - that the dependency generated is at least as strict as the - corresponding build dependency. - . - This is useful as allows packages to not hardcode this information - multiple times. - . - Note that the format of deb-symbols(5) files requires that the - * Build-Depends-Package: line should start in column one of - the file and not be indented to align with the symbols themselves. - Please do not use the placeholder #PACKAGE#. The - development package for your shared library must be stated explicitly. -See-Also: - policy 8.6.3.2, - deb-symbols(5), - dpkg-shlibdeps(1), - https://www.debian.org/doc/manuals/maint-guide/advanced.en.html#librarysymbols, - Bug#944047 diff -Nru lintian-2.93.0/tags/s/symbols-for-undeclared-shared-library.desc lintian-2.89.0ubuntu1/tags/s/symbols-for-undeclared-shared-library.desc --- lintian-2.93.0/tags/s/symbols-for-undeclared-shared-library.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/symbols-for-undeclared-shared-library.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: symbols-for-undeclared-shared-library +Severity: error +Check: shared-libs +Renamed-From: symbols-declared-but-not-shlib +Info: The symbols control file contains dependency and symbol information + for a shared library which is not listed in the shlibs control file. diff -Nru lintian-2.93.0/tags/s/symbols-for-undeclared-shared-library.tag lintian-2.89.0ubuntu1/tags/s/symbols-for-undeclared-shared-library.tag --- lintian-2.93.0/tags/s/symbols-for-undeclared-shared-library.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/symbols-for-undeclared-shared-library.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: symbols-for-undeclared-shared-library -Severity: error -Check: shared-libs -Renamed-From: symbols-declared-but-not-shlib -Explanation: The symbols control file contains dependency and symbol information - for a shared library which is not listed in the shlibs control file. diff -Nru lintian-2.93.0/tags/s/symlink-contains-spurious-segments.desc lintian-2.89.0ubuntu1/tags/s/symlink-contains-spurious-segments.desc --- lintian-2.93.0/tags/s/symlink-contains-spurious-segments.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/symlink-contains-spurious-segments.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,11 @@ +Tag: symlink-contains-spurious-segments +Severity: error +Check: files/symbolic-links +Info: The symbolic link has needless segments like ".." and "." in the + middle. These are unneeded and make the link longer than it could be, + which is in violation of policy. They can also cause problems in the + presence of symlinked directories. + . + If you use debhelper, running dh_link after creating the package structure + will fix this problem for you. +Ref: policy 10.5 diff -Nru lintian-2.93.0/tags/s/symlink-contains-spurious-segments.tag lintian-2.89.0ubuntu1/tags/s/symlink-contains-spurious-segments.tag --- lintian-2.93.0/tags/s/symlink-contains-spurious-segments.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/symlink-contains-spurious-segments.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,11 +0,0 @@ -Tag: symlink-contains-spurious-segments -Severity: error -Check: files/symbolic-links -Explanation: The symbolic link has needless segments like ".." and "." in the - middle. These are unneeded and make the link longer than it could be, - which is in violation of policy. They can also cause problems in the - presence of symlinked directories. - . - If you use debhelper, running dh_link after creating the package structure - will fix this problem for you. -See-Also: policy 10.5 diff -Nru lintian-2.93.0/tags/s/symlink-ends-with-slash.desc lintian-2.89.0ubuntu1/tags/s/symlink-ends-with-slash.desc --- lintian-2.93.0/tags/s/symlink-ends-with-slash.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/symlink-ends-with-slash.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: symlink-ends-with-slash +Severity: warning +Check: files/symbolic-links +Info: This symlink ends with a slash (/). This is in violation + of policy, where it is stated that symlinks should be as short as possible + . + If you use debhelper, running dh_link after creating the package structure + will fix this problem for you. +Ref: policy 10.5 diff -Nru lintian-2.93.0/tags/s/symlink-ends-with-slash.tag lintian-2.89.0ubuntu1/tags/s/symlink-ends-with-slash.tag --- lintian-2.93.0/tags/s/symlink-ends-with-slash.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/symlink-ends-with-slash.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: symlink-ends-with-slash -Severity: warning -Check: files/symbolic-links -Explanation: This symlink ends with a slash (/). This is in violation - of policy, where it is stated that symlinks should be as short as possible - . - If you use debhelper, running dh_link after creating the package structure - will fix this problem for you. -See-Also: policy 10.5 diff -Nru lintian-2.93.0/tags/s/symlink-has-double-slash.desc lintian-2.89.0ubuntu1/tags/s/symlink-has-double-slash.desc --- lintian-2.93.0/tags/s/symlink-has-double-slash.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/symlink-has-double-slash.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: symlink-has-double-slash +Severity: warning +Check: files/symbolic-links +Info: This symlink contains two successive slashes (//). This is in violation + of policy, where it is stated that symlinks should be as short as possible + . + If you use debhelper, running dh_link after creating the package structure + will fix this problem for you. +Ref: policy 10.5 diff -Nru lintian-2.93.0/tags/s/symlink-has-double-slash.tag lintian-2.89.0ubuntu1/tags/s/symlink-has-double-slash.tag --- lintian-2.93.0/tags/s/symlink-has-double-slash.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/symlink-has-double-slash.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: symlink-has-double-slash -Severity: warning -Check: files/symbolic-links -Explanation: This symlink contains two successive slashes (//). This is in violation - of policy, where it is stated that symlinks should be as short as possible - . - If you use debhelper, running dh_link after creating the package structure - will fix this problem for you. -See-Also: policy 10.5 diff -Nru lintian-2.93.0/tags/s/symlink-has-too-many-up-segments.desc lintian-2.89.0ubuntu1/tags/s/symlink-has-too-many-up-segments.desc --- lintian-2.93.0/tags/s/symlink-has-too-many-up-segments.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/symlink-has-too-many-up-segments.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,5 @@ +Tag: symlink-has-too-many-up-segments +Severity: error +Check: files/symbolic-links +Ref: policy 10.5 +Info: The symlink references a directory beyond the root directory "/". diff -Nru lintian-2.93.0/tags/s/symlink-has-too-many-up-segments.tag lintian-2.89.0ubuntu1/tags/s/symlink-has-too-many-up-segments.tag --- lintian-2.93.0/tags/s/symlink-has-too-many-up-segments.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/symlink-has-too-many-up-segments.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,5 +0,0 @@ -Tag: symlink-has-too-many-up-segments -Severity: error -Check: files/symbolic-links -See-Also: policy 10.5 -Explanation: The symlink references a directory beyond the root directory "/". diff -Nru lintian-2.93.0/tags/s/symlink-is-self-recursive.desc lintian-2.89.0ubuntu1/tags/s/symlink-is-self-recursive.desc --- lintian-2.93.0/tags/s/symlink-is-self-recursive.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/symlink-is-self-recursive.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: symlink-is-self-recursive +Severity: warning +Certainty: possible +Check: files/symbolic-links +Info: The symbolic link is recursive to a higher directory of the symlink + itself. This means, that you can infinitely chdir with this symlink. This is + usually not okay, but sometimes wanted behaviour. diff -Nru lintian-2.93.0/tags/s/symlink-is-self-recursive.tag lintian-2.89.0ubuntu1/tags/s/symlink-is-self-recursive.tag --- lintian-2.93.0/tags/s/symlink-is-self-recursive.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/symlink-is-self-recursive.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: symlink-is-self-recursive -Severity: warning -Check: files/symbolic-links -Explanation: The symbolic link is recursive to a higher directory of the symlink - itself. This means, that you can infinitely chdir with this symlink. This is - usually not okay, but sometimes wanted behaviour. diff -Nru lintian-2.93.0/tags/s/symlink-target-in-build-tree.desc lintian-2.89.0ubuntu1/tags/s/symlink-target-in-build-tree.desc --- lintian-2.93.0/tags/s/symlink-target-in-build-tree.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/symlink-target-in-build-tree.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: symlink-target-in-build-tree +Severity: error +Certainty: possible +Check: files/symbolic-links +Info: The package sets a link with a target pointing to common + build paths. + . + This often occurs if the package uses regular expressions to + strip the build path without properly regex quoting the build + path. diff -Nru lintian-2.93.0/tags/s/symlink-target-in-build-tree.tag lintian-2.89.0ubuntu1/tags/s/symlink-target-in-build-tree.tag --- lintian-2.93.0/tags/s/symlink-target-in-build-tree.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/symlink-target-in-build-tree.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: symlink-target-in-build-tree -Severity: error -Check: files/symbolic-links -Explanation: The package sets a link with a target pointing to common - build paths. - . - This often occurs if the package uses regular expressions to - strip the build path without properly regex quoting the build - path. diff -Nru lintian-2.93.0/tags/s/symlink-target-in-tmp.desc lintian-2.89.0ubuntu1/tags/s/symlink-target-in-tmp.desc --- lintian-2.93.0/tags/s/symlink-target-in-tmp.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/symlink-target-in-tmp.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: symlink-target-in-tmp +Severity: error +Check: files/symbolic-links +Info: Packages must not set links with targets pointing into /tmp or + /var/tmp. The File Hierarchy Standard specifies that such files + may be removed by the administrator and that programs may not depend on + any files in /tmp being preserved across invocations, which + combined mean that it makes no sense to ship files in these directories. +Ref: fhs tmptemporaryfiles, fhs vartmptemporaryfilespreservedbetwee diff -Nru lintian-2.93.0/tags/s/symlink-target-in-tmp.tag lintian-2.89.0ubuntu1/tags/s/symlink-target-in-tmp.tag --- lintian-2.93.0/tags/s/symlink-target-in-tmp.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/symlink-target-in-tmp.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: symlink-target-in-tmp -Severity: error -Check: files/symbolic-links -Explanation: Packages must not set links with targets pointing into /tmp or - /var/tmp. The File Hierarchy Standard specifies that such files - may be removed by the administrator and that programs may not depend on - any files in /tmp being preserved across invocations, which - combined mean that it makes no sense to ship files in these directories. -See-Also: fhs tmptemporaryfiles, fhs vartmptemporaryfilespreservedbetwee diff -Nru lintian-2.93.0/tags/s/synopsis-is-a-sentence.desc lintian-2.89.0ubuntu1/tags/s/synopsis-is-a-sentence.desc --- lintian-2.93.0/tags/s/synopsis-is-a-sentence.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/synopsis-is-a-sentence.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,16 @@ +Tag: synopsis-is-a-sentence +Severity: info +Certainty: possible +Check: fields/description +Renamed-From: description-synopsis-might-not-be-phrased-properly +Info: The package synopsis (also known as the "short" description, ie. the + first line in the package's "Description:" field) either ends with a full + stop "." character or starts another sentence. + . + This is not necessary as the synopsis does not need to be a full + sentence. It is recommended that a single descriptive phrase is used + instead. + . + Note also that the synopsis is not part of the rest of the "long" + Description: field. +Ref: devref 6.2.2 diff -Nru lintian-2.93.0/tags/s/synopsis-is-a-sentence.tag lintian-2.89.0ubuntu1/tags/s/synopsis-is-a-sentence.tag --- lintian-2.93.0/tags/s/synopsis-is-a-sentence.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/synopsis-is-a-sentence.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,15 +0,0 @@ -Tag: synopsis-is-a-sentence -Severity: info -Check: fields/description -Renamed-From: description-synopsis-might-not-be-phrased-properly -Explanation: The package synopsis (also known as the "short" description, ie. the - first line in the package's "Description:" field) either ends with a full - stop "." character or starts another sentence. - . - This is not necessary as the synopsis does not need to be a full - sentence. It is recommended that a single descriptive phrase is used - instead. - . - Note also that the synopsis is not part of the rest of the "long" - Description: field. -See-Also: devref 6.2.2 diff -Nru lintian-2.93.0/tags/s/synopsis-too-long.desc lintian-2.89.0ubuntu1/tags/s/synopsis-too-long.desc --- lintian-2.93.0/tags/s/synopsis-too-long.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/synopsis-too-long.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: synopsis-too-long +Severity: warning +Check: fields/description +Renamed-From: description-too-long +Info: The first line of the "Description:" must be less than 80 characters long. +Ref: policy 3.4.1 diff -Nru lintian-2.93.0/tags/s/synopsis-too-long.tag lintian-2.89.0ubuntu1/tags/s/synopsis-too-long.tag --- lintian-2.93.0/tags/s/synopsis-too-long.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/synopsis-too-long.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: synopsis-too-long -Severity: warning -Check: fields/description -Renamed-From: description-too-long -Explanation: The first line of the "Description:" must be less than 80 characters long. -See-Also: policy 3.4.1 diff -Nru lintian-2.93.0/tags/s/syntax-error-in-debconf-template.desc lintian-2.89.0ubuntu1/tags/s/syntax-error-in-debconf-template.desc --- lintian-2.93.0/tags/s/syntax-error-in-debconf-template.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/syntax-error-in-debconf-template.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: syntax-error-in-debconf-template +Severity: error +Certainty: possible +Check: debian/debconf +Info: The template file contains a syntax error. + . + This issue may hide other issues as Lintian skips some checks on the + file in this case. diff -Nru lintian-2.93.0/tags/s/syntax-error-in-debconf-template.tag lintian-2.89.0ubuntu1/tags/s/syntax-error-in-debconf-template.tag --- lintian-2.93.0/tags/s/syntax-error-in-debconf-template.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/syntax-error-in-debconf-template.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: syntax-error-in-debconf-template -Severity: error -Check: debian/debconf -Explanation: The template file contains a syntax error. - . - This issue may hide other issues as Lintian skips some checks on the - file in this case. diff -Nru lintian-2.93.0/tags/s/syntax-error-in-debian-changelog.desc lintian-2.89.0ubuntu1/tags/s/syntax-error-in-debian-changelog.desc --- lintian-2.93.0/tags/s/syntax-error-in-debian-changelog.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/syntax-error-in-debian-changelog.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,13 @@ +Tag: syntax-error-in-debian-changelog +Severity: warning +Certainty: possible +Check: debian/changelog +Info: While parsing the Debian changelog, a syntax error was found. If + you have old changelog entries that don't follow the current syntax but + that you want to keep as-is for the historical record, add the line: + . + Old Changelog: + . + with no leading whitespace before the legacy entries. This line and + everything after it will be ignored. +Ref: policy 4.4 diff -Nru lintian-2.93.0/tags/s/syntax-error-in-debian-changelog.tag lintian-2.89.0ubuntu1/tags/s/syntax-error-in-debian-changelog.tag --- lintian-2.93.0/tags/s/syntax-error-in-debian-changelog.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/syntax-error-in-debian-changelog.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,12 +0,0 @@ -Tag: syntax-error-in-debian-changelog -Severity: warning -Check: debian/changelog -Explanation: While parsing the Debian changelog, a syntax error was found. If - you have old changelog entries that don't follow the current syntax but - that you want to keep as-is for the historical record, add the line: - . - Old Changelog: - . - with no leading whitespace before the legacy entries. This line and - everything after it will be ignored. -See-Also: policy 4.4 diff -Nru lintian-2.93.0/tags/s/syntax-error-in-debian-news-file.desc lintian-2.89.0ubuntu1/tags/s/syntax-error-in-debian-news-file.desc --- lintian-2.93.0/tags/s/syntax-error-in-debian-news-file.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/syntax-error-in-debian-news-file.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: syntax-error-in-debian-news-file +Severity: warning +Certainty: possible +Check: debian/changelog +Info: While parsing the NEWS.Debian file, a syntax error was found. +Ref: devref 6.3.4 diff -Nru lintian-2.93.0/tags/s/syntax-error-in-debian-news-file.tag lintian-2.89.0ubuntu1/tags/s/syntax-error-in-debian-news-file.tag --- lintian-2.93.0/tags/s/syntax-error-in-debian-news-file.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/syntax-error-in-debian-news-file.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,5 +0,0 @@ -Tag: syntax-error-in-debian-news-file -Severity: warning -Check: debian/changelog -Explanation: While parsing the NEWS.Debian file, a syntax error was found. -See-Also: devref 6.3.4 diff -Nru lintian-2.93.0/tags/s/syntax-error-in-dep5-copyright.desc lintian-2.89.0ubuntu1/tags/s/syntax-error-in-dep5-copyright.desc --- lintian-2.93.0/tags/s/syntax-error-in-dep5-copyright.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/syntax-error-in-dep5-copyright.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: syntax-error-in-dep5-copyright +Severity: warning +Certainty: possible +Check: debian/copyright/dep5 +Ref: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ +Info: The machine-readable copyright file didn't pass Debian control file + syntax check. + . + This issue may hide other issues as Lintian skips some checks on the + file in this case. diff -Nru lintian-2.93.0/tags/s/syntax-error-in-dep5-copyright.tag lintian-2.89.0ubuntu1/tags/s/syntax-error-in-dep5-copyright.tag --- lintian-2.93.0/tags/s/syntax-error-in-dep5-copyright.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/syntax-error-in-dep5-copyright.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: syntax-error-in-dep5-copyright -Severity: warning -Check: debian/copyright/dep5 -See-Also: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ -Explanation: The machine-readable copyright file didn't pass Debian control file - syntax check. - . - This issue may hide other issues as Lintian skips some checks on the - file in this case. diff -Nru lintian-2.93.0/tags/s/syntax-error-in-symbols-file.desc lintian-2.89.0ubuntu1/tags/s/syntax-error-in-symbols-file.desc --- lintian-2.93.0/tags/s/syntax-error-in-symbols-file.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/syntax-error-in-symbols-file.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: syntax-error-in-symbols-file +Severity: error +Check: shared-libs +Info: The symbols file contains an entry that does not follow the syntax + rules for symbols files. + . + This may be due to the entry appearing out of sequence. +Ref: deb-symbols(5) diff -Nru lintian-2.93.0/tags/s/syntax-error-in-symbols-file.tag lintian-2.89.0ubuntu1/tags/s/syntax-error-in-symbols-file.tag --- lintian-2.93.0/tags/s/syntax-error-in-symbols-file.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/syntax-error-in-symbols-file.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: syntax-error-in-symbols-file -Severity: error -Check: shared-libs -Explanation: The symbols file contains an entry that does not follow the syntax - rules for symbols files. - . - This may be due to the entry appearing out of sequence. -See-Also: deb-symbols(5) diff -Nru lintian-2.93.0/tags/s/systemd-service-alias-without-extension.desc lintian-2.89.0ubuntu1/tags/s/systemd-service-alias-without-extension.desc --- lintian-2.93.0/tags/s/systemd-service-alias-without-extension.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/systemd-service-alias-without-extension.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: systemd-service-alias-without-extension +Severity: warning +Check: systemd +Ref: http://www.freedesktop.org/software/systemd/man/systemd.unit.html#Alias= +Info: The service file lists an alias without a file extension. + . + The spec mandates that the extension of the listed alias matches + the extension of the unit itself. diff -Nru lintian-2.93.0/tags/s/systemd-service-alias-without-extension.tag lintian-2.89.0ubuntu1/tags/s/systemd-service-alias-without-extension.tag --- lintian-2.93.0/tags/s/systemd-service-alias-without-extension.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/systemd-service-alias-without-extension.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: systemd-service-alias-without-extension -Severity: warning -Check: systemd -See-Also: http://www.freedesktop.org/software/systemd/man/systemd.unit.html#Alias= -Explanation: The service file lists an alias without a file extension. - . - The spec mandates that the extension of the listed alias matches - the extension of the unit itself. diff -Nru lintian-2.93.0/tags/s/systemd-service-file-missing-documentation-key.desc lintian-2.89.0ubuntu1/tags/s/systemd-service-file-missing-documentation-key.desc --- lintian-2.93.0/tags/s/systemd-service-file-missing-documentation-key.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/systemd-service-file-missing-documentation-key.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: systemd-service-file-missing-documentation-key +Severity: info +Check: systemd +Info: The systemd service file does not contain a Documentation key. + . + Documentation for systemd service files can be automatically viewed using + systemctl help servicename if this field is present. +Ref: systemd.unit(5) diff -Nru lintian-2.93.0/tags/s/systemd-service-file-missing-documentation-key.tag lintian-2.89.0ubuntu1/tags/s/systemd-service-file-missing-documentation-key.tag --- lintian-2.93.0/tags/s/systemd-service-file-missing-documentation-key.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/systemd-service-file-missing-documentation-key.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: systemd-service-file-missing-documentation-key -Severity: info -Check: systemd -Explanation: The systemd service file does not contain a Documentation key. - . - Documentation for systemd service files can be automatically viewed using - systemctl help servicename if this field is present. -See-Also: systemd.unit(5) diff -Nru lintian-2.93.0/tags/s/systemd-service-file-missing-hardening-features.desc lintian-2.89.0ubuntu1/tags/s/systemd-service-file-missing-hardening-features.desc --- lintian-2.93.0/tags/s/systemd-service-file-missing-hardening-features.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/systemd-service-file-missing-hardening-features.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,16 @@ +Tag: systemd-service-file-missing-hardening-features +Severity: pedantic +Experimental: yes +Certainty: wild-guess +Check: systemd +Info: The specified systemd .service file does not appear to + enable any hardening options. + . + systemd has support for many security-oriented features such as + isolating services from the network, private /tmp directories, + as well as control over making directories appear read-only or even + inaccessible, etc. + . + Please consider supporting some options, collaborating upstream where + necessary about any potential changes. +Ref: systemd.service(5), http://0pointer.de/blog/projects/security.html diff -Nru lintian-2.93.0/tags/s/systemd-service-file-missing-hardening-features.tag lintian-2.89.0ubuntu1/tags/s/systemd-service-file-missing-hardening-features.tag --- lintian-2.93.0/tags/s/systemd-service-file-missing-hardening-features.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/systemd-service-file-missing-hardening-features.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,15 +0,0 @@ -Tag: systemd-service-file-missing-hardening-features -Severity: pedantic -Experimental: yes -Check: systemd -Explanation: The specified systemd .service file does not appear to - enable any hardening options. - . - systemd has support for many security-oriented features such as - isolating services from the network, private /tmp directories, - as well as control over making directories appear read-only or even - inaccessible, etc. - . - Please consider supporting some options, collaborating upstream where - necessary about any potential changes. -See-Also: systemd.service(5), http://0pointer.de/blog/projects/security.html diff -Nru lintian-2.93.0/tags/s/systemd-service-file-missing-install-key.desc lintian-2.89.0ubuntu1/tags/s/systemd-service-file-missing-install-key.desc --- lintian-2.93.0/tags/s/systemd-service-file-missing-install-key.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/systemd-service-file-missing-install-key.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: systemd-service-file-missing-install-key +Severity: info +Certainty: wild-guess +Check: systemd +Info: The systemd service file does not contain a WantedBy= or + RequiredBy= key in its [Install] section. + . + Forgetting to add such a line (e.g. WantedBy=multi-user.target) + results in the service file not being started by default. +Ref: systemd.unit(5) diff -Nru lintian-2.93.0/tags/s/systemd-service-file-missing-install-key.tag lintian-2.89.0ubuntu1/tags/s/systemd-service-file-missing-install-key.tag --- lintian-2.93.0/tags/s/systemd-service-file-missing-install-key.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/systemd-service-file-missing-install-key.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: systemd-service-file-missing-install-key -Severity: info -Check: systemd -Explanation: The systemd service file does not contain a WantedBy= or - RequiredBy= key in its [Install] section. - . - Forgetting to add such a line (e.g. WantedBy=multi-user.target) - results in the service file not being started by default. -See-Also: systemd.unit(5) diff -Nru lintian-2.93.0/tags/s/systemd-service-file-outside-lib.desc lintian-2.89.0ubuntu1/tags/s/systemd-service-file-outside-lib.desc --- lintian-2.93.0/tags/s/systemd-service-file-outside-lib.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/systemd-service-file-outside-lib.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,14 @@ +Tag: systemd-service-file-outside-lib +Severity: error +Check: systemd +Info: The package ships a systemd service file outside + /lib/systemd/system/ + . + Systemd in Debian searches for unit files in /lib/systemd/system/ + and /etc/systemd/system. Notably, it does not look + in /usr/lib/systemd/system/ for service files. + . + System administrators should have the possibility to overwrite a + service file (or parts of it, in newer systemd versions) by placing a + file in /etc/systemd/system, so the canonical location used + for service files is /lib/systemd/system/. diff -Nru lintian-2.93.0/tags/s/systemd-service-file-outside-lib.tag lintian-2.89.0ubuntu1/tags/s/systemd-service-file-outside-lib.tag --- lintian-2.93.0/tags/s/systemd-service-file-outside-lib.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/systemd-service-file-outside-lib.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,14 +0,0 @@ -Tag: systemd-service-file-outside-lib -Severity: error -Check: systemd -Explanation: The package ships a systemd service file outside - /lib/systemd/system/ - . - Systemd in Debian searches for unit files in /lib/systemd/system/ - and /etc/systemd/system. Notably, it does *not* look - in /usr/lib/systemd/system/ for service files. - . - System administrators should have the possibility to overwrite a - service file (or parts of it, in newer systemd versions) by placing a - file in /etc/systemd/system, so the canonical location used - for service files is /lib/systemd/system/. diff -Nru lintian-2.93.0/tags/s/systemd-service-file-refers-to-obsolete-bindto.desc lintian-2.89.0ubuntu1/tags/s/systemd-service-file-refers-to-obsolete-bindto.desc --- lintian-2.93.0/tags/s/systemd-service-file-refers-to-obsolete-bindto.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/systemd-service-file-refers-to-obsolete-bindto.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: systemd-service-file-refers-to-obsolete-bindto +Severity: warning +Check: systemd +Info: The systemd service file refers to the obsolete BindTo= option. + . + The BindTo= option has been deprecated in favour of + BindsTo= which should be used instead. +Ref: https://github.com/systemd/systemd/commit/7f2cddae09fd2579ae24434df577bb5e5a157d86 diff -Nru lintian-2.93.0/tags/s/systemd-service-file-refers-to-obsolete-bindto.tag lintian-2.89.0ubuntu1/tags/s/systemd-service-file-refers-to-obsolete-bindto.tag --- lintian-2.93.0/tags/s/systemd-service-file-refers-to-obsolete-bindto.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/systemd-service-file-refers-to-obsolete-bindto.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: systemd-service-file-refers-to-obsolete-bindto -Severity: warning -Check: systemd -Explanation: The systemd service file refers to the obsolete BindTo= option. - . - The BindTo= option has been deprecated in favour of - BindsTo= which should be used instead. -See-Also: https://github.com/systemd/systemd/commit/7f2cddae09fd2579ae24434df577bb5e5a157d86 diff -Nru lintian-2.93.0/tags/s/systemd-service-file-refers-to-obsolete-target.desc lintian-2.89.0ubuntu1/tags/s/systemd-service-file-refers-to-obsolete-target.desc --- lintian-2.93.0/tags/s/systemd-service-file-refers-to-obsolete-target.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/systemd-service-file-refers-to-obsolete-target.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: systemd-service-file-refers-to-obsolete-target +Severity: warning +Check: systemd +Info: The systemd service file refers to an obsolete target. + . + Some targets are obsolete by now, e.g. syslog.target or dbus.target. For + example, declaring After=syslog.target is unnecessary by now because + syslog is socket-activated and will therefore be started when needed. diff -Nru lintian-2.93.0/tags/s/systemd-service-file-refers-to-obsolete-target.tag lintian-2.89.0ubuntu1/tags/s/systemd-service-file-refers-to-obsolete-target.tag --- lintian-2.93.0/tags/s/systemd-service-file-refers-to-obsolete-target.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/systemd-service-file-refers-to-obsolete-target.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: systemd-service-file-refers-to-obsolete-target -Severity: warning -Check: systemd -Explanation: The systemd service file refers to an obsolete target. - . - Some targets are obsolete by now, e.g. syslog.target or dbus.target. For - example, declaring After=syslog.target is unnecessary by now because - syslog is socket-activated and will therefore be started when needed. diff -Nru lintian-2.93.0/tags/s/systemd-service-file-refers-to-unusual-wantedby-target.desc lintian-2.89.0ubuntu1/tags/s/systemd-service-file-refers-to-unusual-wantedby-target.desc --- lintian-2.93.0/tags/s/systemd-service-file-refers-to-unusual-wantedby-target.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/systemd-service-file-refers-to-unusual-wantedby-target.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,11 @@ +Tag: systemd-service-file-refers-to-unusual-wantedby-target +Severity: warning +Check: systemd +Info: The specified systemd service file declares an unusual + WantedBy= relationship. + . + Most services that want to be started automatically at boot should use + WantedBy=multi-user.target or WantedBy=graphical.target. + Services that want to be started in rescue or single-user mode should + instead use WantedBy=sysinit.target +Ref: https://wiki.debian.org/Teams/pkg-systemd/rcSMigration diff -Nru lintian-2.93.0/tags/s/systemd-service-file-refers-to-unusual-wantedby-target.tag lintian-2.89.0ubuntu1/tags/s/systemd-service-file-refers-to-unusual-wantedby-target.tag --- lintian-2.93.0/tags/s/systemd-service-file-refers-to-unusual-wantedby-target.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/systemd-service-file-refers-to-unusual-wantedby-target.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,11 +0,0 @@ -Tag: systemd-service-file-refers-to-unusual-wantedby-target -Severity: warning -Check: systemd -Explanation: The specified systemd service file declares an unusual - WantedBy= relationship. - . - Most services that want to be started automatically at boot should use - WantedBy=multi-user.target or WantedBy=graphical.target. - Services that want to be started in rescue or single-user mode should - instead use WantedBy=sysinit.target -See-Also: https://wiki.debian.org/Teams/pkg-systemd/rcSMigration diff -Nru lintian-2.93.0/tags/s/systemd-service-file-refers-to-var-run.desc lintian-2.89.0ubuntu1/tags/s/systemd-service-file-refers-to-var-run.desc --- lintian-2.93.0/tags/s/systemd-service-file-refers-to-var-run.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/systemd-service-file-refers-to-var-run.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,13 @@ +Tag: systemd-service-file-refers-to-var-run +Severity: info +Check: systemd +Info: The specified systemd service file declares a PIDFile= + that references /var/run. + . + /var/run is now merely a symlink pointing to /run and + thus it is now considered best practice that packages use /run + directly. + . + Please update the specified service file. +Renamed-From: + systemd-service-file-pidfile-refers-to-var-run diff -Nru lintian-2.93.0/tags/s/systemd-service-file-refers-to-var-run.tag lintian-2.89.0ubuntu1/tags/s/systemd-service-file-refers-to-var-run.tag --- lintian-2.93.0/tags/s/systemd-service-file-refers-to-var-run.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/systemd-service-file-refers-to-var-run.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,13 +0,0 @@ -Tag: systemd-service-file-refers-to-var-run -Severity: info -Check: systemd -Explanation: The specified systemd service file declares a PIDFile= - that references /var/run. - . - /var/run is now merely a symlink pointing to /run and - thus it is now considered best practice that packages use /run - directly. - . - Please update the specified service file. -Renamed-From: - systemd-service-file-pidfile-refers-to-var-run diff -Nru lintian-2.93.0/tags/s/systemd-service-file-shutdown-problems.desc lintian-2.89.0ubuntu1/tags/s/systemd-service-file-shutdown-problems.desc --- lintian-2.93.0/tags/s/systemd-service-file-shutdown-problems.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/systemd-service-file-shutdown-problems.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,18 @@ +Tag: systemd-service-file-shutdown-problems +Severity: warning +Experimental: no +Check: systemd +Ref: https://github.com/systemd/systemd/issues/11821 +Info: The specified systemd .service file contains both + DefaultDependencies=no and Conflicts=shutdown.target + directives without Before=shutdown.target. + . + This can lead to problems during shutdown because the service may + linger until the very end of shutdown sequence as nothing requests to + stop it before (due to DefaultDependencies=no). + . + There is race condition between stopping units and systemd getting a + request to exit the main loop, so it may proceed with shutdown before + all pending stop jobs have been processed. + . + Please add Before=shutdown.target. diff -Nru lintian-2.93.0/tags/s/systemd-service-file-shutdown-problems.tag lintian-2.89.0ubuntu1/tags/s/systemd-service-file-shutdown-problems.tag --- lintian-2.93.0/tags/s/systemd-service-file-shutdown-problems.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/systemd-service-file-shutdown-problems.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,18 +0,0 @@ -Tag: systemd-service-file-shutdown-problems -Severity: warning -Experimental: no -Check: systemd -See-Also: https://github.com/systemd/systemd/issues/11821 -Explanation: The specified systemd .service file contains both - DefaultDependencies=no and Conflicts=shutdown.target - directives without Before=shutdown.target. - . - This can lead to problems during shutdown because the service may - linger until the very end of shutdown sequence as nothing requests to - stop it before (due to DefaultDependencies=no). - . - There is race condition between stopping units and systemd getting a - request to exit the main loop, so it may proceed with shutdown before - all pending stop jobs have been processed. - . - Please add Before=shutdown.target. diff -Nru lintian-2.93.0/tags/s/systemd-service-file-uses-deprecated-syslog-facility.desc lintian-2.89.0ubuntu1/tags/s/systemd-service-file-uses-deprecated-syslog-facility.desc --- lintian-2.93.0/tags/s/systemd-service-file-uses-deprecated-syslog-facility.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/systemd-service-file-uses-deprecated-syslog-facility.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: systemd-service-file-uses-deprecated-syslog-facility +Severity: warning +Check: systemd +Info: The specified systemd service file specifies + StandardOutput= or StandardError= that references + syslog or syslog-console. + . + This is discouraged, and systemd versions 246 and above will log a + warning about this. +Ref: https://github.com/systemd/systemd/blob/master/NEWS#L101 diff -Nru lintian-2.93.0/tags/s/systemd-service-file-uses-deprecated-syslog-facility.tag lintian-2.89.0ubuntu1/tags/s/systemd-service-file-uses-deprecated-syslog-facility.tag --- lintian-2.93.0/tags/s/systemd-service-file-uses-deprecated-syslog-facility.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/systemd-service-file-uses-deprecated-syslog-facility.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,10 +0,0 @@ -Tag: systemd-service-file-uses-deprecated-syslog-facility -Severity: warning -Check: systemd -Explanation: The specified systemd service file specifies - StandardOutput= or StandardError= that references - syslog or syslog-console. - . - This is discouraged, and systemd versions 246 and above will log a - warning about this. -See-Also: https://github.com/systemd/systemd/blob/master/NEWS#L101 diff -Nru lintian-2.93.0/tags/s/systemd-service-file-uses-nobody-or-nogroup.desc lintian-2.89.0ubuntu1/tags/s/systemd-service-file-uses-nobody-or-nogroup.desc --- lintian-2.93.0/tags/s/systemd-service-file-uses-nobody-or-nogroup.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/systemd-service-file-uses-nobody-or-nogroup.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: systemd-service-file-uses-nobody-or-nogroup +Severity: warning +Check: systemd +Info: The specified systemd service file declares a User= + or Group= that references nobody or nogroup. + . + This is discouraged, and systemd versions 246 and above will log a + warning about this. +Ref: https://github.com/systemd/systemd/blob/master/NEWS#L106 diff -Nru lintian-2.93.0/tags/s/systemd-service-file-uses-nobody-or-nogroup.tag lintian-2.89.0ubuntu1/tags/s/systemd-service-file-uses-nobody-or-nogroup.tag --- lintian-2.93.0/tags/s/systemd-service-file-uses-nobody-or-nogroup.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/systemd-service-file-uses-nobody-or-nogroup.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: systemd-service-file-uses-nobody-or-nogroup -Severity: warning -Check: systemd -Explanation: The specified systemd service file declares a User= - or Group= that references nobody or nogroup. - . - This is discouraged, and systemd versions 246 and above will log a - warning about this. -See-Also: https://github.com/systemd/systemd/blob/master/NEWS#L106 diff -Nru lintian-2.93.0/tags/s/systemd-service-file-wraps-init-script.desc lintian-2.89.0ubuntu1/tags/s/systemd-service-file-wraps-init-script.desc --- lintian-2.93.0/tags/s/systemd-service-file-wraps-init-script.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/systemd-service-file-wraps-init-script.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,11 @@ +Tag: systemd-service-file-wraps-init-script +Severity: warning +Check: systemd +Info: The listed service file simply uses ths existing SysV init script + via ExecStart, ExecStop, etc. + . + The main logic of more complex init scripts should be moved into helper + scripts which can be used directly from both the .service file and the + init script. This will also make the init scripts more readable and easier + to support other alternatives. Note that as /etc/init.d/* files are + conffiles, such updates are not guaranteed to reach users. diff -Nru lintian-2.93.0/tags/s/systemd-service-file-wraps-init-script.tag lintian-2.89.0ubuntu1/tags/s/systemd-service-file-wraps-init-script.tag --- lintian-2.93.0/tags/s/systemd-service-file-wraps-init-script.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/systemd-service-file-wraps-init-script.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,11 +0,0 @@ -Tag: systemd-service-file-wraps-init-script -Severity: warning -Check: systemd -Explanation: The listed service file simply uses ths existing SysV init script - via ExecStart, ExecStop, etc. - . - The main logic of more complex init scripts should be moved into helper - scripts which can be used directly from both the .service file and the - init script. This will also make the init scripts more readable and easier - to support other alternatives. Note that as /etc/init.d/* files are - conffiles, such updates are not guaranteed to reach users. diff -Nru lintian-2.93.0/tags/s/systemd-tmpfiles.d-outside-usr-lib.desc lintian-2.89.0ubuntu1/tags/s/systemd-tmpfiles.d-outside-usr-lib.desc --- lintian-2.93.0/tags/s/systemd-tmpfiles.d-outside-usr-lib.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/systemd-tmpfiles.d-outside-usr-lib.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,5 @@ +Tag: systemd-tmpfiles.d-outside-usr-lib +Severity: error +Check: systemd +Info: The package ships a systemd tmpfiles.d(5) conf file outside + /usr/lib/tmpfiles.d/ diff -Nru lintian-2.93.0/tags/s/systemd-tmpfiles.d-outside-usr-lib.tag lintian-2.89.0ubuntu1/tags/s/systemd-tmpfiles.d-outside-usr-lib.tag --- lintian-2.93.0/tags/s/systemd-tmpfiles.d-outside-usr-lib.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/s/systemd-tmpfiles.d-outside-usr-lib.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,5 +0,0 @@ -Tag: systemd-tmpfiles.d-outside-usr-lib -Severity: error -Check: systemd -Explanation: The package ships a systemd tmpfiles.d(5) conf file outside - /usr/lib/tmpfiles.d/ diff -Nru lintian-2.93.0/tags/t/tab-in-license-text.desc lintian-2.89.0ubuntu1/tags/t/tab-in-license-text.desc --- lintian-2.93.0/tags/t/tab-in-license-text.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/t/tab-in-license-text.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: tab-in-license-text +Severity: warning +Check: debian/copyright/dep5 +Info: A long license text in debian/copyright contains + a tab character. It often occurs when a license text is copied + from another source, and not reformatted. + . + DEP-5 disallows the use of tab characters in the license text. + Please remove it. diff -Nru lintian-2.93.0/tags/t/tab-in-license-text.tag lintian-2.89.0ubuntu1/tags/t/tab-in-license-text.tag --- lintian-2.93.0/tags/t/tab-in-license-text.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/t/tab-in-license-text.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: tab-in-license-text -Severity: warning -Check: debian/copyright/dep5 -Explanation: A long license text in debian/copyright contains - a tab character. It often occurs when a license text is copied - from another source, and not reformatted. - . - DEP-5 disallows the use of tab characters in the license text. - Please remove it. diff -Nru lintian-2.93.0/tags/t/tar-errors-from-control.desc lintian-2.89.0ubuntu1/tags/t/tar-errors-from-control.desc --- lintian-2.93.0/tags/t/tar-errors-from-control.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/t/tar-errors-from-control.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: tar-errors-from-control +Severity: error +Certainty: possible +Check: deb-format +Info: tar produced an error while listing the contents of the + control.tar.gz member of this package. This probably means + there's something broken or at least strange about the way the package + was constructed. diff -Nru lintian-2.93.0/tags/t/tar-errors-from-control.tag lintian-2.89.0ubuntu1/tags/t/tar-errors-from-control.tag --- lintian-2.93.0/tags/t/tar-errors-from-control.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/t/tar-errors-from-control.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: tar-errors-from-control -Severity: error -Check: deb-format -Explanation: tar produced an error while listing the contents of the - control.tar.gz member of this package. This probably means - there's something broken or at least strange about the way the package - was constructed. diff -Nru lintian-2.93.0/tags/t/tar-errors-from-data.desc lintian-2.89.0ubuntu1/tags/t/tar-errors-from-data.desc --- lintian-2.93.0/tags/t/tar-errors-from-data.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/t/tar-errors-from-data.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: tar-errors-from-data +Severity: error +Certainty: possible +Check: deb-format +Info: tar produced an error while listing the contents of the data + member of this package. This probably means there's something broken or + at least strange about the way the package was constructed. diff -Nru lintian-2.93.0/tags/t/tar-errors-from-data.tag lintian-2.89.0ubuntu1/tags/t/tar-errors-from-data.tag --- lintian-2.93.0/tags/t/tar-errors-from-data.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/t/tar-errors-from-data.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: tar-errors-from-data -Severity: error -Check: deb-format -Explanation: tar produced an error while listing the contents of the data - member of this package. This probably means there's something broken or - at least strange about the way the package was constructed. diff -Nru lintian-2.93.0/tags/t/tar-errors-from-source.desc lintian-2.89.0ubuntu1/tags/t/tar-errors-from-source.desc --- lintian-2.93.0/tags/t/tar-errors-from-source.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/t/tar-errors-from-source.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: tar-errors-from-source +Severity: info +Check: tar-errors +Info: tar produced an error while unpacking this source package. This + probably means there's something broken or at least strange about the way + the upstream tar file was constructed. You may want to report this as an + upstream bug. diff -Nru lintian-2.93.0/tags/t/tar-errors-from-source.tag lintian-2.89.0ubuntu1/tags/t/tar-errors-from-source.tag --- lintian-2.93.0/tags/t/tar-errors-from-source.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/t/tar-errors-from-source.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: tar-errors-from-source -Severity: info -Check: tar-errors -Explanation: tar produced an error while unpacking this source package. This - probably means there's something broken or at least strange about the way - the upstream tar file was constructed. You may want to report this as an - upstream bug. diff -Nru lintian-2.93.0/tags/t/tclsh-script-but-no-tclsh-dep.desc lintian-2.89.0ubuntu1/tags/t/tclsh-script-but-no-tclsh-dep.desc --- lintian-2.93.0/tags/t/tclsh-script-but-no-tclsh-dep.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/t/tclsh-script-but-no-tclsh-dep.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: tclsh-script-but-no-tclsh-dep +Severity: error +Check: scripts +Info: Packages that include tclsh scripts must depend on the virtual + package tclsh or, if they require a specific version of tcl, that + version of tcl. + . + In some cases a weaker relationship, such as Suggests or Recommends, will + be more appropriate. diff -Nru lintian-2.93.0/tags/t/tclsh-script-but-no-tclsh-dep.tag lintian-2.89.0ubuntu1/tags/t/tclsh-script-but-no-tclsh-dep.tag --- lintian-2.93.0/tags/t/tclsh-script-but-no-tclsh-dep.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/t/tclsh-script-but-no-tclsh-dep.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: tclsh-script-but-no-tclsh-dep -Severity: error -Check: scripts -Explanation: Packages that include tclsh scripts must depend on the virtual - package tclsh or, if they require a specific version of tcl, that - version of tcl. - . - In some cases a weaker relationship, such as Suggests or Recommends, will - be more appropriate. diff -Nru lintian-2.93.0/tags/t/team-upload-has-incorrect-version-number.desc lintian-2.89.0ubuntu1/tags/t/team-upload-has-incorrect-version-number.desc --- lintian-2.93.0/tags/t/team-upload-has-incorrect-version-number.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/t/team-upload-has-incorrect-version-number.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: team-upload-has-incorrect-version-number +Severity: warning +Check: nmu +Info: A team upload (uploading a package from the same team without adding + oneself as maintainer or uploader) is a maintainer upload: it should not + get a NMU revision number. Team uploads are recognized by the string + "team upload" on the first line of the changelog file. diff -Nru lintian-2.93.0/tags/t/team-upload-has-incorrect-version-number.tag lintian-2.89.0ubuntu1/tags/t/team-upload-has-incorrect-version-number.tag --- lintian-2.93.0/tags/t/team-upload-has-incorrect-version-number.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/t/team-upload-has-incorrect-version-number.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: team-upload-has-incorrect-version-number -Severity: warning -Check: nmu -Explanation: A team upload (uploading a package from the same team without adding - oneself as maintainer or uploader) is a maintainer upload: it should not - get a NMU revision number. Team uploads are recognized by the string - "team upload" on the first line of the changelog file. diff -Nru lintian-2.93.0/tags/t/template-uses-unsplit-choices.desc lintian-2.89.0ubuntu1/tags/t/template-uses-unsplit-choices.desc --- lintian-2.93.0/tags/t/template-uses-unsplit-choices.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/t/template-uses-unsplit-choices.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,16 @@ +Tag: template-uses-unsplit-choices +Severity: warning +Certainty: possible +Check: debian/debconf +Info: The use of _Choices in templates is deprecated. + A _Choices field must be translated as a single string. + . + Using __Choices allows each choice to be translated separately, easing + translation and is therefore recommended. + . + Instead of simply replacing all occurrences of "_Choices" by "__Choices", + apply the method described in po-debconf(7) under "SPLITTING CHOICES + LIST", to avoid breaking existing translations. + . + If in doubt, please ask for help on the debian-i18n mailing list. +Ref: po-debconf(7) diff -Nru lintian-2.93.0/tags/t/template-uses-unsplit-choices.tag lintian-2.89.0ubuntu1/tags/t/template-uses-unsplit-choices.tag --- lintian-2.93.0/tags/t/template-uses-unsplit-choices.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/t/template-uses-unsplit-choices.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,15 +0,0 @@ -Tag: template-uses-unsplit-choices -Severity: warning -Check: debian/debconf -Explanation: The use of _Choices in templates is deprecated. - A _Choices field must be translated as a single string. - . - Using __Choices allows each choice to be translated separately, easing - translation and is therefore recommended. - . - Instead of simply replacing all occurrences of "_Choices" by "__Choices", - apply the method described in po-debconf(7) under "SPLITTING CHOICES - LIST", to avoid breaking existing translations. - . - If in doubt, please ask for help on the debian-i18n mailing list. -See-Also: po-debconf(7) diff -Nru lintian-2.93.0/tags/t/temporary-debhelper-file.desc lintian-2.89.0ubuntu1/tags/t/temporary-debhelper-file.desc --- lintian-2.93.0/tags/t/temporary-debhelper-file.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/t/temporary-debhelper-file.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: temporary-debhelper-file +Severity: error +Check: debhelper +Ref: dh_clean(1) +Info: The package contains temporary debhelper files, which are normally + removed by dh_clean. The most common cause for this is that a + binary package has been renamed or removed without cleaning the build + directory first. diff -Nru lintian-2.93.0/tags/t/temporary-debhelper-file.tag lintian-2.89.0ubuntu1/tags/t/temporary-debhelper-file.tag --- lintian-2.93.0/tags/t/temporary-debhelper-file.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/t/temporary-debhelper-file.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: temporary-debhelper-file -Severity: error -Check: debhelper -See-Also: dh_clean(1) -Explanation: The package contains temporary debhelper files, which are normally - removed by dh_clean. The most common cause for this is that a - binary package has been renamed or removed without cleaning the build - directory first. diff -Nru lintian-2.93.0/tags/t/testsuite-dependency-has-unparsable-elements.desc lintian-2.89.0ubuntu1/tags/t/testsuite-dependency-has-unparsable-elements.desc --- lintian-2.93.0/tags/t/testsuite-dependency-has-unparsable-elements.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/t/testsuite-dependency-has-unparsable-elements.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,12 @@ +Tag: testsuite-dependency-has-unparsable-elements +Severity: warning +Certainty: possible +Check: testsuite +Info: Lintian cannot parse the Depends field for the given autopkgtest. + . + Please double check that dependency the syntax is correct. + . + Note that Lintian has a whitelist of known "special" dependencies + permitted by autopkgtest (e.g. @builddeps@). Lintian does not accept + these as a part of an OR-clause. +Ref: https://salsa.debian.org/ci-team/autopkgtest/tree/master/doc/README.package-tests.rst diff -Nru lintian-2.93.0/tags/t/testsuite-dependency-has-unparsable-elements.tag lintian-2.89.0ubuntu1/tags/t/testsuite-dependency-has-unparsable-elements.tag --- lintian-2.93.0/tags/t/testsuite-dependency-has-unparsable-elements.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/t/testsuite-dependency-has-unparsable-elements.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,11 +0,0 @@ -Tag: testsuite-dependency-has-unparsable-elements -Severity: warning -Check: testsuite -Explanation: Lintian cannot parse the Depends field for the given autopkgtest. - . - Please double check that dependency the syntax is correct. - . - Note that Lintian has a whitelist of known "special" dependencies - permitted by autopkgtest (e.g. @builddeps@). Lintian does not accept - these as a part of an OR-clause. -See-Also: https://salsa.debian.org/ci-team/autopkgtest/tree/master/doc/README.package-tests.rst diff -Nru lintian-2.93.0/tags/t/third-party-package-in-python-dir.desc lintian-2.89.0ubuntu1/tags/t/third-party-package-in-python-dir.desc --- lintian-2.93.0/tags/t/third-party-package-in-python-dir.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/t/third-party-package-in-python-dir.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: third-party-package-in-python-dir +Severity: warning +Check: languages/python +Info: Third-party Python packages should install their files in + /usr/lib/pythonVERSION/site-packages for Python versions + before 2.6 and /usr/lib/pythonVERSION/dist-packages + for Python 2.6 and later. All other directories in + /usr/lib/pythonVERSION are for use by the core python + packages. +Ref: python-policy 2.5 diff -Nru lintian-2.93.0/tags/t/third-party-package-in-python-dir.tag lintian-2.89.0ubuntu1/tags/t/third-party-package-in-python-dir.tag --- lintian-2.93.0/tags/t/third-party-package-in-python-dir.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/t/third-party-package-in-python-dir.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,10 +0,0 @@ -Tag: third-party-package-in-python-dir -Severity: warning -Check: languages/python -Explanation: Third-party Python packages should install their files in - /usr/lib/python*VERSION*/site-packages for Python versions - before 2.6 and /usr/lib/python*VERSION*/dist-packages - for Python 2.6 and later. All other directories in - /usr/lib/python*VERSION* are for use by the core python - packages. -See-Also: python-policy 2.5 diff -Nru lintian-2.93.0/tags/t/timewarp-standards-version.desc lintian-2.89.0ubuntu1/tags/t/timewarp-standards-version.desc --- lintian-2.93.0/tags/t/timewarp-standards-version.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/t/timewarp-standards-version.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: timewarp-standards-version +Severity: warning +Check: fields/standards-version +Info: The source package refers to a Standards-Version that was released + after the date of the most recent debian/changelog entry. + Perhaps you forgot to update the timestamp in debian/changelog + before building the package? diff -Nru lintian-2.93.0/tags/t/timewarp-standards-version.tag lintian-2.89.0ubuntu1/tags/t/timewarp-standards-version.tag --- lintian-2.93.0/tags/t/timewarp-standards-version.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/t/timewarp-standards-version.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: timewarp-standards-version -Severity: warning -Check: fields/standards-version -Explanation: The source package refers to a Standards-Version that was released - after the date of the most recent debian/changelog entry. - Perhaps you forgot to update the timestamp in debian/changelog - before building the package? diff -Nru lintian-2.93.0/tags/t/too-long-extended-description-in-templates.desc lintian-2.89.0ubuntu1/tags/t/too-long-extended-description-in-templates.desc --- lintian-2.93.0/tags/t/too-long-extended-description-in-templates.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/t/too-long-extended-description-in-templates.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: too-long-extended-description-in-templates +Severity: warning +Check: debian/debconf +Info: Some debconf interfaces cannot deal very well with descriptions of + more than about 20 lines, so try to keep the extended description below + this limit. +Ref: devref 6.5.3.2 diff -Nru lintian-2.93.0/tags/t/too-long-extended-description-in-templates.tag lintian-2.89.0ubuntu1/tags/t/too-long-extended-description-in-templates.tag --- lintian-2.93.0/tags/t/too-long-extended-description-in-templates.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/t/too-long-extended-description-in-templates.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: too-long-extended-description-in-templates -Severity: warning -Check: debian/debconf -Explanation: Some debconf interfaces cannot deal very well with descriptions of - more than about 20 lines, so try to keep the extended description below - this limit. -See-Also: devref 6.5.3.2 diff -Nru lintian-2.93.0/tags/t/too-long-short-description-in-templates.desc lintian-2.89.0ubuntu1/tags/t/too-long-short-description-in-templates.desc --- lintian-2.93.0/tags/t/too-long-short-description-in-templates.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/t/too-long-short-description-in-templates.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: too-long-short-description-in-templates +Severity: warning +Check: debian/debconf +Info: The short description should be kept short (50 characters or so) so + that it may be accommodated by most debconf interfaces. Keeping it short + also helps translators, as usually translations tend to end up being + longer than the original. +Ref: devref 6.5.3.2 diff -Nru lintian-2.93.0/tags/t/too-long-short-description-in-templates.tag lintian-2.89.0ubuntu1/tags/t/too-long-short-description-in-templates.tag --- lintian-2.93.0/tags/t/too-long-short-description-in-templates.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/t/too-long-short-description-in-templates.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: too-long-short-description-in-templates -Severity: warning -Check: debian/debconf -Explanation: The short description should be kept short (50 characters or so) so - that it may be accommodated by most debconf interfaces. Keeping it short - also helps translators, as usually translations tend to end up being - longer than the original. -See-Also: devref 6.5.3.2 diff -Nru lintian-2.93.0/tags/t/too-many-architectures.desc lintian-2.89.0ubuntu1/tags/t/too-many-architectures.desc --- lintian-2.93.0/tags/t/too-many-architectures.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/t/too-many-architectures.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: too-many-architectures +Severity: error +Check: fields/architecture +Info: A binary package should list exactly one architecture (the one it is + compiled for), or the special value "all" if it is architecture-independent. +Ref: policy 5.6.8 diff -Nru lintian-2.93.0/tags/t/too-many-architectures.tag lintian-2.89.0ubuntu1/tags/t/too-many-architectures.tag --- lintian-2.93.0/tags/t/too-many-architectures.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/t/too-many-architectures.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: too-many-architectures -Severity: error -Check: fields/architecture -Explanation: A binary package should list exactly one architecture (the one it is - compiled for), or the special value "all" if it is architecture-independent. -See-Also: policy 5.6.8 diff -Nru lintian-2.93.0/tags/t/too-many-contacts.desc lintian-2.89.0ubuntu1/tags/t/too-many-contacts.desc --- lintian-2.93.0/tags/t/too-many-contacts.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/t/too-many-contacts.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: too-many-contacts +Severity: error +Check: fields/mail-address +Info: The named field identifying a contact person lists too many people. +Ref: policy 5.6.2, + policy 5.6.3, + policy 5.6.4 diff -Nru lintian-2.93.0/tags/t/too-many-contacts.tag lintian-2.89.0ubuntu1/tags/t/too-many-contacts.tag --- lintian-2.93.0/tags/t/too-many-contacts.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/t/too-many-contacts.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: too-many-contacts -Severity: error -Check: fields/mail-address -Explanation: The named field identifying a contact person lists too many people. -See-Also: policy 5.6.2, - policy 5.6.3, - policy 5.6.4 diff -Nru lintian-2.93.0/tags/t/trailing-slash-for-dpkg-maintscript-helper-symlink_to_dir.desc lintian-2.89.0ubuntu1/tags/t/trailing-slash-for-dpkg-maintscript-helper-symlink_to_dir.desc --- lintian-2.93.0/tags/t/trailing-slash-for-dpkg-maintscript-helper-symlink_to_dir.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/t/trailing-slash-for-dpkg-maintscript-helper-symlink_to_dir.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: trailing-slash-for-dpkg-maintscript-helper-symlink_to_dir +Severity: error +Check: scripts +Info: The maintainer script seems to call dpkg-maintscript-helper + symlink_to_dir with a trailing slash for pathname. This renders the + package uninstallable. +Ref: dpkg-maintscript-helper(1) diff -Nru lintian-2.93.0/tags/t/trailing-slash-for-dpkg-maintscript-helper-symlink_to_dir.tag lintian-2.89.0ubuntu1/tags/t/trailing-slash-for-dpkg-maintscript-helper-symlink_to_dir.tag --- lintian-2.93.0/tags/t/trailing-slash-for-dpkg-maintscript-helper-symlink_to_dir.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/t/trailing-slash-for-dpkg-maintscript-helper-symlink_to_dir.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: trailing-slash-for-dpkg-maintscript-helper-symlink_to_dir -Severity: error -Check: scripts -Explanation: The maintainer script seems to call dpkg-maintscript-helper - symlink_to_dir with a trailing slash for pathname. This renders the - package uninstallable. -See-Also: dpkg-maintscript-helper(1) diff -Nru lintian-2.93.0/tags/t/trailing-whitespace.desc lintian-2.89.0ubuntu1/tags/t/trailing-whitespace.desc --- lintian-2.93.0/tags/t/trailing-whitespace.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/t/trailing-whitespace.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,27 @@ +Tag: trailing-whitespace +Severity: pedantic +Check: debian/trailing-whitespace +Renamed-From: file-contains-trailing-whitespace +Info: This file contains lines with trailing whitespace characters. + . + Whilst often harmless and unsightly, such extra whitespaces can also + cause tools to interpret the whitespace characters literally. The + tool diff(1) does not like them, either. They are best + avoided. + . + Some of these problems can be hard to track down. + . + Whitespace at the end of lines may be removed with the following: + . + $ sed -i -e 's@[[:space:]]*$@@g' debian/control debian/changelog + . + If you use Emacs, you can also use "M-x wh-cl" (whitespace-cleanup). + . + However, if you wish to only remove trailing spaces and leave trailing tabs + (eg. for Makefiles), you can use the following code snippet: + . + $ sed -i -e 's@[ ]*$@@g' debian/rules + . + To remove empty lines from the end of a file, you can use: + . + $ sed -i -e :a -e '/^\n*$/{$d;N;};/\n$/ba' debian/rules diff -Nru lintian-2.93.0/tags/t/trailing-whitespace.tag lintian-2.89.0ubuntu1/tags/t/trailing-whitespace.tag --- lintian-2.93.0/tags/t/trailing-whitespace.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/t/trailing-whitespace.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,27 +0,0 @@ -Tag: trailing-whitespace -Severity: pedantic -Check: debian/trailing-whitespace -Renamed-From: file-contains-trailing-whitespace -Explanation: This file contains lines with trailing whitespace characters. - . - Whilst often harmless and unsightly, such extra whitespaces can also - cause tools to interpret the whitespace characters literally. The - tool diff(1) does not like them, either. They are best - avoided. - . - Some of these problems can be hard to track down. - . - Whitespace at the end of lines may be removed with the following: - . - $ sed -i -e 's@[[:space:]]*$@@g' debian/control debian/changelog - . - If you use Emacs, you can also use "M-x wh-cl" (whitespace-cleanup). - . - However, if you wish to only remove trailing spaces and leave trailing tabs - (eg. for Makefiles), you can use the following code snippet: - . - $ sed -i -e 's@[ ]*$@@g' debian/rules - . - To remove empty lines from the end of a file, you can use: - . - $ sed -i -e :a -e '/^\n*$/{$d;N;};/\n$/ba' debian/rules diff -Nru lintian-2.93.0/tags/t/transitional-package-not-oldlibs-optional.desc lintian-2.89.0ubuntu1/tags/t/transitional-package-not-oldlibs-optional.desc --- lintian-2.93.0/tags/t/transitional-package-not-oldlibs-optional.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/t/transitional-package-not-oldlibs-optional.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,14 @@ +Tag: transitional-package-not-oldlibs-optional +Severity: warning +Certainty: possible +Check: fields/section +Renamed-From: + transitional-package-should-be-oldlibs-extra + transitional-package-should-be-oldlibs-optional +Info: The package appears to be a transitional package, but it is not + priority optional and in the oldlibs section. + . + Using oldlibs/optional assists package managers in handling the + transition package correctly. +Ref: Bug#645438, + devref 6.7.7 diff -Nru lintian-2.93.0/tags/t/transitional-package-not-oldlibs-optional.tag lintian-2.89.0ubuntu1/tags/t/transitional-package-not-oldlibs-optional.tag --- lintian-2.93.0/tags/t/transitional-package-not-oldlibs-optional.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/t/transitional-package-not-oldlibs-optional.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,13 +0,0 @@ -Tag: transitional-package-not-oldlibs-optional -Severity: warning -Check: fields/section -Renamed-From: - transitional-package-should-be-oldlibs-extra - transitional-package-should-be-oldlibs-optional -Explanation: The package appears to be a transitional package, but it is not - priority optional and in the oldlibs section. - . - Using oldlibs/optional assists package managers in handling the - transition package correctly. -See-Also: Bug#645438, - devref 6.7.7 diff -Nru lintian-2.93.0/tags/t/translated-default-field.desc lintian-2.89.0ubuntu1/tags/t/translated-default-field.desc --- lintian-2.93.0/tags/t/translated-default-field.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/t/translated-default-field.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,21 @@ +Tag: translated-default-field +Severity: warning +Certainty: possible +Check: debian/po-debconf +Info: You should not mark as translatable "Default:" or "DefaultChoice:" + fields, unless explicitly needed (e.g. default country, default language, + etc.). If this Default field really should be translated, you should + explain translators how they should translate it by using comments or + brackets. For example: + . + # Translators: Default language name, but not translated + _Default: English + . + Or: + . + _Default: English[ Default language name, but not translated] + . + Note that in the first case, Lintian ignores the comment unless it + explicitly references translators and it is appears directly before + the field in question. +Ref: po-debconf(7), #637881 diff -Nru lintian-2.93.0/tags/t/translated-default-field.tag lintian-2.89.0ubuntu1/tags/t/translated-default-field.tag --- lintian-2.93.0/tags/t/translated-default-field.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/t/translated-default-field.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,20 +0,0 @@ -Tag: translated-default-field -Severity: warning -Check: debian/po-debconf -Explanation: You should not mark as translatable "Default:" or "DefaultChoice:" - fields, unless explicitly needed (e.g. default country, default language, - etc.). If this Default field really should be translated, you should - explain translators how they should translate it by using comments or - brackets. For example: - . - # Translators: Default language name, but not translated - _Default: English - . - Or: - . - _Default: English[ Default language name, but not translated] - . - Note that in the first case, Lintian ignores the comment unless it - explicitly references translators and it is appears directly before - the field in question. -See-Also: po-debconf(7), Bug#637881 diff -Nru lintian-2.93.0/tags/t/trimmed-deb822-field.desc lintian-2.89.0ubuntu1/tags/t/trimmed-deb822-field.desc --- lintian-2.93.0/tags/t/trimmed-deb822-field.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/t/trimmed-deb822-field.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: trimmed-deb822-field +Severity: classification +Check: fields/deb822 +Info: The raw but trimmed contents of the named field in the given + Deb822 file. The number indicates the section from the top, + starting at 1. diff -Nru lintian-2.93.0/tags/t/trimmed-deb822-field.tag lintian-2.89.0ubuntu1/tags/t/trimmed-deb822-field.tag --- lintian-2.93.0/tags/t/trimmed-deb822-field.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/t/trimmed-deb822-field.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: trimmed-deb822-field -Severity: classification -Check: fields/deb822 -Explanation: The raw but trimmed contents of the named field in the given - Deb822 file. The number indicates the section from the top, - starting at 1. diff -Nru lintian-2.93.0/tags/t/trimmed-field.desc lintian-2.89.0ubuntu1/tags/t/trimmed-field.desc --- lintian-2.93.0/tags/t/trimmed-field.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/t/trimmed-field.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,5 @@ +Tag: trimmed-field +Severity: classification +Check: fields/trimmed +Info: These are the raw but trimmed contents of the named field in + the package's primary control file. diff -Nru lintian-2.93.0/tags/t/trimmed-field.tag lintian-2.89.0ubuntu1/tags/t/trimmed-field.tag --- lintian-2.93.0/tags/t/trimmed-field.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/t/trimmed-field.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,5 +0,0 @@ -Tag: trimmed-field -Severity: classification -Check: fields/trimmed -Explanation: These are the raw but trimmed contents of the named field in - the package's primary control file. diff -Nru lintian-2.93.0/tags/t/triplet-dir-and-architecture-mismatch.desc lintian-2.89.0ubuntu1/tags/t/triplet-dir-and-architecture-mismatch.desc --- lintian-2.93.0/tags/t/triplet-dir-and-architecture-mismatch.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/t/triplet-dir-and-architecture-mismatch.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: triplet-dir-and-architecture-mismatch +Severity: error +Certainty: possible +Check: files/architecture +Ref: policy 9.1.1 +Info: This package contains a directory under /lib or + /usr/lib which doesn't match the proper triplet for the + binary package's architecture. This is very likely to be a mistake + when indicating the underlying build system where the files should be + installed. diff -Nru lintian-2.93.0/tags/t/triplet-dir-and-architecture-mismatch.tag lintian-2.89.0ubuntu1/tags/t/triplet-dir-and-architecture-mismatch.tag --- lintian-2.93.0/tags/t/triplet-dir-and-architecture-mismatch.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/t/triplet-dir-and-architecture-mismatch.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: triplet-dir-and-architecture-mismatch -Severity: error -Check: files/architecture -See-Also: policy 9.1.1 -Explanation: This package contains a directory under /lib or - /usr/lib which doesn't match the proper triplet for the - binary package's architecture. This is very likely to be a mistake - when indicating the underlying build system where the files should be - installed. diff -Nru lintian-2.93.0/tags/t/truetype-font-prohibits-installable-embedding.desc lintian-2.89.0ubuntu1/tags/t/truetype-font-prohibits-installable-embedding.desc --- lintian-2.93.0/tags/t/truetype-font-prohibits-installable-embedding.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/t/truetype-font-prohibits-installable-embedding.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: truetype-font-prohibits-installable-embedding +Severity: warning +Check: fonts/truetype +Info: This package installs a TrueType font with restrictive license + terms. The font does not permit installable embedding, as defined by + the TrueType standard. +Ref: https://developer.apple.com/fonts/TrueType-Reference-Manual/RM06/Chap6OS2.html diff -Nru lintian-2.93.0/tags/t/truetype-font-prohibits-installable-embedding.tag lintian-2.89.0ubuntu1/tags/t/truetype-font-prohibits-installable-embedding.tag --- lintian-2.93.0/tags/t/truetype-font-prohibits-installable-embedding.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/t/truetype-font-prohibits-installable-embedding.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: truetype-font-prohibits-installable-embedding -Severity: warning -Check: fonts/truetype -Explanation: This package installs a TrueType font with restrictive license - terms. The font does not permit installable embedding, as defined by - the TrueType standard. -See-Also: https://developer.apple.com/fonts/TrueType-Reference-Manual/RM06/Chap6OS2.html diff -Nru lintian-2.93.0/tags/t/truetype-font-wrong-filename.desc lintian-2.89.0ubuntu1/tags/t/truetype-font-wrong-filename.desc --- lintian-2.93.0/tags/t/truetype-font-wrong-filename.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/t/truetype-font-wrong-filename.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,5 @@ +Tag: truetype-font-wrong-filename +Severity: warning +Check: fonts/truetype +Info: This package installs a TrueType font with an extension other than + .ttf. The check is insensitive to case. diff -Nru lintian-2.93.0/tags/t/truetype-font-wrong-filename.tag lintian-2.89.0ubuntu1/tags/t/truetype-font-wrong-filename.tag --- lintian-2.93.0/tags/t/truetype-font-wrong-filename.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/t/truetype-font-wrong-filename.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,5 +0,0 @@ -Tag: truetype-font-wrong-filename -Severity: warning -Check: fonts/truetype -Explanation: This package installs a TrueType font with an extension other than - .ttf. The check is insensitive to case. diff -Nru lintian-2.93.0/tags/t/typelib-in-arch-all-package.desc lintian-2.89.0ubuntu1/tags/t/typelib-in-arch-all-package.desc --- lintian-2.93.0/tags/t/typelib-in-arch-all-package.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/t/typelib-in-arch-all-package.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: typelib-in-arch-all-package +Severity: error +Check: desktop/gnome/gir +Info: GObject-Introspection binary typelibs + (Foo-23.typelib) are architecture-dependent, therefore + they must appear in architecture-dependent packages. +Ref: /usr/share/doc/gobject-introspection/policy.txt diff -Nru lintian-2.93.0/tags/t/typelib-in-arch-all-package.tag lintian-2.89.0ubuntu1/tags/t/typelib-in-arch-all-package.tag --- lintian-2.93.0/tags/t/typelib-in-arch-all-package.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/t/typelib-in-arch-all-package.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: typelib-in-arch-all-package -Severity: error -Check: desktop/gnome/gir -Explanation: GObject-Introspection binary typelibs - (Foo-23.typelib) are architecture-dependent, therefore - they must appear in architecture-dependent packages. -See-Also: /usr/share/doc/gobject-introspection/policy.txt diff -Nru lintian-2.93.0/tags/t/typelib-missing-gir-depends.desc lintian-2.89.0ubuntu1/tags/t/typelib-missing-gir-depends.desc --- lintian-2.93.0/tags/t/typelib-missing-gir-depends.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/t/typelib-missing-gir-depends.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: typelib-missing-gir-depends +Severity: warning +Check: desktop/gnome/gir +Info: GObject-Introspection binary typelibs + (Foo-23.typelib) can depend on other typelibs. To generate + appropriate dependencies in the binary package, they must have + Depends: ${gir:Depends} in the control file. +Ref: /usr/share/doc/gobject-introspection/policy.txt diff -Nru lintian-2.93.0/tags/t/typelib-missing-gir-depends.tag lintian-2.89.0ubuntu1/tags/t/typelib-missing-gir-depends.tag --- lintian-2.93.0/tags/t/typelib-missing-gir-depends.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/t/typelib-missing-gir-depends.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: typelib-missing-gir-depends -Severity: warning -Check: desktop/gnome/gir -Explanation: GObject-Introspection binary typelibs - (Foo-23.typelib) can depend on other typelibs. To generate - appropriate dependencies in the binary package, they must have - Depends: ${gir:Depends} in the control file. -See-Also: /usr/share/doc/gobject-introspection/policy.txt diff -Nru lintian-2.93.0/tags/t/typelib-not-in-multiarch-directory.desc lintian-2.89.0ubuntu1/tags/t/typelib-not-in-multiarch-directory.desc --- lintian-2.93.0/tags/t/typelib-not-in-multiarch-directory.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/t/typelib-not-in-multiarch-directory.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: typelib-not-in-multiarch-directory +Severity: info +Check: desktop/gnome/gir +Info: Public GObject-Introspection binary typelibs + (Foo-23.typelib) should be installed in the multi-arch + directory /usr/lib/MULTIARCH-TUPLE/girepository-1.0. diff -Nru lintian-2.93.0/tags/t/typelib-not-in-multiarch-directory.tag lintian-2.89.0ubuntu1/tags/t/typelib-not-in-multiarch-directory.tag --- lintian-2.93.0/tags/t/typelib-not-in-multiarch-directory.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/t/typelib-not-in-multiarch-directory.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: typelib-not-in-multiarch-directory -Severity: info -Check: desktop/gnome/gir -Explanation: Public GObject-Introspection binary typelibs - (Foo-23.typelib) should be installed in the multi-arch - directory /usr/lib/MULTIARCH-TUPLE/girepository-1.0. diff -Nru lintian-2.93.0/tags/t/typelib-package-name-does-not-match.desc lintian-2.89.0ubuntu1/tags/t/typelib-package-name-does-not-match.desc --- lintian-2.93.0/tags/t/typelib-package-name-does-not-match.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/t/typelib-package-name-does-not-match.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,18 @@ +Tag: typelib-package-name-does-not-match +Severity: warning +Certainty: possible +Check: desktop/gnome/gir +Info: GObject-Introspection binary typelibs (Foo-23.typelib) + should normally be made available in a package named gir1.2-foo-23. + . + If multiple typelibs are shipped in the same package, then that package + should have versioned Provides for the names that would have been + used for separate packages. This arrangement should only be used if the + included typelibs' versions are expected to remain the same at all times. + . + For example, gir1.2-gtk-3.0 is named for the Gtk-3.0 + typelib, but also contains the Gdk-3.0 and GdkX11-3.0 + typelibs. It should have versioned Provides entries for + gir1.2-gdk-3.0 (= ${binary:Version}) + and gir1.2-gdkx11-3.0 (= ${binary:Version}) to indicate this. +Ref: /usr/share/doc/gobject-introspection/policy.txt diff -Nru lintian-2.93.0/tags/t/typelib-package-name-does-not-match.tag lintian-2.89.0ubuntu1/tags/t/typelib-package-name-does-not-match.tag --- lintian-2.93.0/tags/t/typelib-package-name-does-not-match.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/t/typelib-package-name-does-not-match.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,17 +0,0 @@ -Tag: typelib-package-name-does-not-match -Severity: warning -Check: desktop/gnome/gir -Explanation: GObject-Introspection binary typelibs (Foo-23.typelib) - should normally be made available in a package named gir1.2-foo-23. - . - If multiple typelibs are shipped in the same package, then that package - should have versioned Provides for the names that would have been - used for separate packages. This arrangement should only be used if the - included typelibs' versions are expected to remain the same at all times. - . - For example, gir1.2-gtk-3.0 is named for the Gtk-3.0 - typelib, but also contains the Gdk-3.0 and GdkX11-3.0 - typelibs. It should have versioned Provides entries for - gir1.2-gdk-3.0 (= ${binary:Version}) - and gir1.2-gdkx11-3.0 (= ${binary:Version}) to indicate this. -See-Also: /usr/share/doc/gobject-introspection/policy.txt diff -Nru lintian-2.93.0/tags/t/typelib-section-not-introspection.desc lintian-2.89.0ubuntu1/tags/t/typelib-section-not-introspection.desc --- lintian-2.93.0/tags/t/typelib-section-not-introspection.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/t/typelib-section-not-introspection.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: typelib-section-not-introspection +Severity: warning +Check: desktop/gnome/gir +Info: GObject-Introspection binary typelibs (Foo-23.typelib) + should be made available in a GObject-Introspection package + in the introspection section of the archive, + normally named gir1.2-foo-23. +Ref: /usr/share/doc/gobject-introspection/policy.txt diff -Nru lintian-2.93.0/tags/t/typelib-section-not-introspection.tag lintian-2.89.0ubuntu1/tags/t/typelib-section-not-introspection.tag --- lintian-2.93.0/tags/t/typelib-section-not-introspection.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/t/typelib-section-not-introspection.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: typelib-section-not-introspection -Severity: warning -Check: desktop/gnome/gir -Explanation: GObject-Introspection binary typelibs (Foo-23.typelib) - should be made available in a GObject-Introspection package - in the introspection section of the archive, - normally named gir1.2-foo-23. -See-Also: /usr/share/doc/gobject-introspection/policy.txt diff -Nru lintian-2.93.0/tags/t/typo-in-debhelper-override-target.desc lintian-2.89.0ubuntu1/tags/t/typo-in-debhelper-override-target.desc --- lintian-2.93.0/tags/t/typo-in-debhelper-override-target.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/t/typo-in-debhelper-override-target.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,14 @@ +Tag: typo-in-debhelper-override-target +Severity: warning +Certainty: possible +Check: debhelper +Info: The listed target in debian/rules is a likely misspelling or it is + missing an underscore ("_") between the override_dh, + execute_after_dh etc. and the command name. + . + This can result in (for example) a override_dh_foo-style target + silently not being executed by make. + . + Implementation detail: The typo is detected by using "Levenshtein + edit distance" so if the typo involve several characters Lintian may + not detect it. diff -Nru lintian-2.93.0/tags/t/typo-in-debhelper-override-target.tag lintian-2.89.0ubuntu1/tags/t/typo-in-debhelper-override-target.tag --- lintian-2.93.0/tags/t/typo-in-debhelper-override-target.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/t/typo-in-debhelper-override-target.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,13 +0,0 @@ -Tag: typo-in-debhelper-override-target -Severity: warning -Check: debhelper -Explanation: The listed target in debian/rules is a likely misspelling or it is - missing an underscore ("_") between the override_dh, - execute_after_dh etc. and the command name. - . - This can result in (for example) a override_dh_foo-style target - silently not being executed by make. - . - Implementation detail: The typo is detected by using "Levenshtein - edit distance" so if the typo involve several characters Lintian may - not detect it. diff -Nru lintian-2.93.0/tags/t/typo-in-manual-page.desc lintian-2.89.0ubuntu1/tags/t/typo-in-manual-page.desc --- lintian-2.93.0/tags/t/typo-in-manual-page.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/t/typo-in-manual-page.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,14 @@ +Tag: typo-in-manual-page +Severity: info +Check: documentation/manual +Renamed-From: spelling-error-in-manpage +Info: Lintian found a spelling error in a manual page. Lintian has a list + of common misspellings that it looks for. It does not have a + dictionary like a spelling checker does. + . + If the string containing the spelling error is translated with the help + of gettext (with the help of po4a, for example) or a similar tool, + please fix the error in the translations as well as the English text to + avoid making the translations fuzzy. With gettext, for example, this + means you should also fix the spelling mistake in the corresponding + msgids in the *.po files. diff -Nru lintian-2.93.0/tags/t/typo-in-manual-page.tag lintian-2.89.0ubuntu1/tags/t/typo-in-manual-page.tag --- lintian-2.93.0/tags/t/typo-in-manual-page.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/t/typo-in-manual-page.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,14 +0,0 @@ -Tag: typo-in-manual-page -Severity: info -Check: documentation/manual -Renamed-From: spelling-error-in-manpage -Explanation: Lintian found a spelling error in a manual page. Lintian has a list - of common misspellings that it looks for. It does not have a - dictionary like a spelling checker does. - . - If the string containing the spelling error is translated with the help - of gettext (with the help of po4a, for example) or a similar tool, - please fix the error in the translations as well as the English text to - avoid making the translations fuzzy. With gettext, for example, this - means you should also fix the spelling mistake in the corresponding - msgids in the *.po files. diff -Nru lintian-2.93.0/tags/team/pkg-js/deprecated/nodejs-bad-buffer-usage.desc lintian-2.89.0ubuntu1/tags/team/pkg-js/deprecated/nodejs-bad-buffer-usage.desc --- lintian-2.93.0/tags/team/pkg-js/deprecated/nodejs-bad-buffer-usage.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/team/pkg-js/deprecated/nodejs-bad-buffer-usage.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: nodejs-bad-buffer-usage +Severity: warning +Check: team/pkg-js/deprecated +Name-Spaced: yes +Info: Replace Buffer() by Buffer.from() or + Buffer.alloc() for security reasons. diff -Nru lintian-2.93.0/tags/team/pkg-js/deprecated/nodejs-bad-buffer-usage.tag lintian-2.89.0ubuntu1/tags/team/pkg-js/deprecated/nodejs-bad-buffer-usage.tag --- lintian-2.93.0/tags/team/pkg-js/deprecated/nodejs-bad-buffer-usage.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/team/pkg-js/deprecated/nodejs-bad-buffer-usage.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: nodejs-bad-buffer-usage -Severity: warning -Check: team/pkg-js/deprecated -Name-Spaced: yes -Explanation: Replace Buffer() by Buffer.from() or - Buffer.alloc() for security reasons. diff -Nru lintian-2.93.0/tags/team/pkg-js/testsuite/no-team-tests.desc lintian-2.89.0ubuntu1/tags/team/pkg-js/testsuite/no-team-tests.desc --- lintian-2.93.0/tags/team/pkg-js/testsuite/no-team-tests.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/team/pkg-js/testsuite/no-team-tests.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: no-team-tests +Severity: warning +Check: team/pkg-js/testsuite +Name-Spaced: yes +Info: Source packages maintained by pkg-js should declare a + 'Testsuite: autopkgtest-pkg-js' header instead of + 'Testsuite: autopkgtest' and avoid duplicating the standard + test control file in all the packages. diff -Nru lintian-2.93.0/tags/team/pkg-js/testsuite/no-team-tests.tag lintian-2.89.0ubuntu1/tags/team/pkg-js/testsuite/no-team-tests.tag --- lintian-2.93.0/tags/team/pkg-js/testsuite/no-team-tests.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/team/pkg-js/testsuite/no-team-tests.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: no-team-tests -Severity: warning -Check: team/pkg-js/testsuite -Name-Spaced: yes -Explanation: Source packages maintained by pkg-js should declare a - 'Testsuite: autopkgtest-pkg-js' header instead of - 'Testsuite: autopkgtest' and avoid duplicating the standard - test control file in all the packages. diff -Nru lintian-2.93.0/tags/team/pkg-js/testsuite/no-testsuite-header.desc lintian-2.89.0ubuntu1/tags/team/pkg-js/testsuite/no-testsuite-header.desc --- lintian-2.93.0/tags/team/pkg-js/testsuite/no-testsuite-header.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/team/pkg-js/testsuite/no-testsuite-header.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: no-testsuite-header +Severity: warning +Check: team/pkg-js/testsuite +Name-Spaced: yes +Info: Source packages maintained by pkg-js should declare a + 'Testsuite: autopkgtest-pkg-nodejs' header. diff -Nru lintian-2.93.0/tags/team/pkg-js/testsuite/no-testsuite-header.tag lintian-2.89.0ubuntu1/tags/team/pkg-js/testsuite/no-testsuite-header.tag --- lintian-2.93.0/tags/team/pkg-js/testsuite/no-testsuite-header.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/team/pkg-js/testsuite/no-testsuite-header.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: no-testsuite-header -Severity: warning -Check: team/pkg-js/testsuite -Name-Spaced: yes -Explanation: Source packages maintained by pkg-js should declare a - 'Testsuite: autopkgtest-pkg-nodejs' header. diff -Nru lintian-2.93.0/tags/team/pkg-js/vcs/no-git.desc lintian-2.89.0ubuntu1/tags/team/pkg-js/vcs/no-git.desc --- lintian-2.93.0/tags/team/pkg-js/vcs/no-git.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/team/pkg-js/vcs/no-git.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: no-git +Severity: warning +Check: team/pkg-js/vcs +Name-Spaced: yes +Info: All pkg-js maintained packages moved to git. This package + still has a non-git Vcs-* header. diff -Nru lintian-2.93.0/tags/team/pkg-js/vcs/no-git.tag lintian-2.89.0ubuntu1/tags/team/pkg-js/vcs/no-git.tag --- lintian-2.93.0/tags/team/pkg-js/vcs/no-git.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/team/pkg-js/vcs/no-git.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: no-git -Severity: warning -Check: team/pkg-js/vcs -Name-Spaced: yes -Explanation: All pkg-js maintained packages moved to git. This package - still has a non-git Vcs-* header. diff -Nru lintian-2.93.0/tags/team/pkg-js/vcs/no-team-url.desc lintian-2.89.0ubuntu1/tags/team/pkg-js/vcs/no-team-url.desc --- lintian-2.93.0/tags/team/pkg-js/vcs/no-team-url.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/team/pkg-js/vcs/no-team-url.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: no-team-url +Severity: warning +Check: team/pkg-js/vcs +Name-Spaced: yes +Info: All pkg-js VCS repositories should live under a team-writable + location. diff -Nru lintian-2.93.0/tags/team/pkg-js/vcs/no-team-url.tag lintian-2.89.0ubuntu1/tags/team/pkg-js/vcs/no-team-url.tag --- lintian-2.93.0/tags/team/pkg-js/vcs/no-team-url.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/team/pkg-js/vcs/no-team-url.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: no-team-url -Severity: warning -Check: team/pkg-js/vcs -Name-Spaced: yes -Explanation: All pkg-js VCS repositories should live under a team-writable - location. diff -Nru lintian-2.93.0/tags/team/pkg-perl/testsuite/autopkgtest-needs-use-name.desc lintian-2.89.0ubuntu1/tags/team/pkg-perl/testsuite/autopkgtest-needs-use-name.desc --- lintian-2.93.0/tags/team/pkg-perl/testsuite/autopkgtest-needs-use-name.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/team/pkg-perl/testsuite/autopkgtest-needs-use-name.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,12 @@ +Tag: autopkgtest-needs-use-name +Severity: warning +Check: team/pkg-perl/testsuite +Name-Spaced: yes +Info: The pkg-perl use.t autopkgtest uses META.json or META.yml + to extract the name of the main module in the package, which will + then be checked with 'perl -w -M"module"' and expected to load ok + and without warnings or other output. This package does not have + content in META.{json,yml} and thus should provide the module name + for use.t in debian/tests/pkg-perl/use-name. + . + See https://perl-team.pages.debian.net/autopkgtest.html diff -Nru lintian-2.93.0/tags/team/pkg-perl/testsuite/autopkgtest-needs-use-name.tag lintian-2.89.0ubuntu1/tags/team/pkg-perl/testsuite/autopkgtest-needs-use-name.tag --- lintian-2.93.0/tags/team/pkg-perl/testsuite/autopkgtest-needs-use-name.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/team/pkg-perl/testsuite/autopkgtest-needs-use-name.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,12 +0,0 @@ -Tag: autopkgtest-needs-use-name -Severity: warning -Check: team/pkg-perl/testsuite -Name-Spaced: yes -Explanation: The pkg-perl use.t autopkgtest uses META.json or META.yml - to extract the name of the main module in the package, which will - then be checked with 'perl -w -M"module"' and expected to load ok - and without warnings or other output. This package does not have - content in META.{json,yml} and thus should provide the module name - for use.t in debian/tests/pkg-perl/use-name. - . - See https://perl-team.pages.debian.net/autopkgtest.html diff -Nru lintian-2.93.0/tags/team/pkg-perl/testsuite/no-team-tests.desc lintian-2.89.0ubuntu1/tags/team/pkg-perl/testsuite/no-team-tests.desc --- lintian-2.93.0/tags/team/pkg-perl/testsuite/no-team-tests.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/team/pkg-perl/testsuite/no-team-tests.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: no-team-tests +Severity: warning +Check: team/pkg-perl/testsuite +Name-Spaced: yes +Info: Source packages maintained by pkg-perl should declare a + 'Testsuite: autopkgtest-pkg-perl' header instead of + 'Testsuite: autopkgtest' and avoid duplicating the standard + test control file in all the packages. + . + See https://perl-team.pages.debian.net/autopkgtest.html diff -Nru lintian-2.93.0/tags/team/pkg-perl/testsuite/no-team-tests.tag lintian-2.89.0ubuntu1/tags/team/pkg-perl/testsuite/no-team-tests.tag --- lintian-2.93.0/tags/team/pkg-perl/testsuite/no-team-tests.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/team/pkg-perl/testsuite/no-team-tests.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,10 +0,0 @@ -Tag: no-team-tests -Severity: warning -Check: team/pkg-perl/testsuite -Name-Spaced: yes -Explanation: Source packages maintained by pkg-perl should declare a - 'Testsuite: autopkgtest-pkg-perl' header instead of - 'Testsuite: autopkgtest' and avoid duplicating the standard - test control file in all the packages. - . - See https://perl-team.pages.debian.net/autopkgtest.html diff -Nru lintian-2.93.0/tags/team/pkg-perl/testsuite/no-testsuite-header.desc lintian-2.89.0ubuntu1/tags/team/pkg-perl/testsuite/no-testsuite-header.desc --- lintian-2.93.0/tags/team/pkg-perl/testsuite/no-testsuite-header.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/team/pkg-perl/testsuite/no-testsuite-header.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: no-testsuite-header +Severity: warning +Check: team/pkg-perl/testsuite +Name-Spaced: yes +Info: Source packages maintained by pkg-perl should declare a + 'Testsuite: autopkgtest-pkg-perl' header. + . + See https://perl-team.pages.debian.net/autopkgtest.html diff -Nru lintian-2.93.0/tags/team/pkg-perl/testsuite/no-testsuite-header.tag lintian-2.89.0ubuntu1/tags/team/pkg-perl/testsuite/no-testsuite-header.tag --- lintian-2.93.0/tags/team/pkg-perl/testsuite/no-testsuite-header.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/team/pkg-perl/testsuite/no-testsuite-header.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: no-testsuite-header -Severity: warning -Check: team/pkg-perl/testsuite -Name-Spaced: yes -Explanation: Source packages maintained by pkg-perl should declare a - 'Testsuite: autopkgtest-pkg-perl' header. - . - See https://perl-team.pages.debian.net/autopkgtest.html diff -Nru lintian-2.93.0/tags/team/pkg-perl/vcs/no-git.desc lintian-2.89.0ubuntu1/tags/team/pkg-perl/vcs/no-git.desc --- lintian-2.93.0/tags/team/pkg-perl/vcs/no-git.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/team/pkg-perl/vcs/no-git.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: no-git +Severity: error +Check: team/pkg-perl/vcs +Name-Spaced: yes +Info: All pkg-perl maintained packages moved to git. This package + still has a non-git Vcs-* header. diff -Nru lintian-2.93.0/tags/team/pkg-perl/vcs/no-git.tag lintian-2.89.0ubuntu1/tags/team/pkg-perl/vcs/no-git.tag --- lintian-2.93.0/tags/team/pkg-perl/vcs/no-git.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/team/pkg-perl/vcs/no-git.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: no-git -Severity: error -Check: team/pkg-perl/vcs -Name-Spaced: yes -Explanation: All pkg-perl maintained packages moved to git. This package - still has a non-git Vcs-* header. diff -Nru lintian-2.93.0/tags/team/pkg-perl/vcs/no-team-url.desc lintian-2.89.0ubuntu1/tags/team/pkg-perl/vcs/no-team-url.desc --- lintian-2.93.0/tags/team/pkg-perl/vcs/no-team-url.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/team/pkg-perl/vcs/no-team-url.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: no-team-url +Severity: warning +Check: team/pkg-perl/vcs +Name-Spaced: yes +Info: All pkg-perl VCS repositories should live under a team-writable + location. diff -Nru lintian-2.93.0/tags/team/pkg-perl/vcs/no-team-url.tag lintian-2.89.0ubuntu1/tags/team/pkg-perl/vcs/no-team-url.tag --- lintian-2.93.0/tags/team/pkg-perl/vcs/no-team-url.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/team/pkg-perl/vcs/no-team-url.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: no-team-url -Severity: warning -Check: team/pkg-perl/vcs -Name-Spaced: yes -Explanation: All pkg-perl VCS repositories should live under a team-writable - location. diff -Nru lintian-2.93.0/tags/team/pkg-perl/xs-abi/legacy-vendorarch-directory.desc lintian-2.89.0ubuntu1/tags/team/pkg-perl/xs-abi/legacy-vendorarch-directory.desc --- lintian-2.93.0/tags/team/pkg-perl/xs-abi/legacy-vendorarch-directory.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/team/pkg-perl/xs-abi/legacy-vendorarch-directory.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,11 @@ +Tag: legacy-vendorarch-directory +Severity: error +Check: team/pkg-perl/xs-abi +Name-Spaced: yes +Info: Since 5.20, Debian perl packages use different directory for placing XS + libraries, which varies by API version and possibly architecture. Files + placed in the previously used directory (/usr/lib/perl5) will not be used by + perl. The build system needs to be fixed to use the value $Config{vendorarch} + (available from the Config module) instead of hardcoding the directory. + . + See Perl Policy 4.1. diff -Nru lintian-2.93.0/tags/team/pkg-perl/xs-abi/legacy-vendorarch-directory.tag lintian-2.89.0ubuntu1/tags/team/pkg-perl/xs-abi/legacy-vendorarch-directory.tag --- lintian-2.93.0/tags/team/pkg-perl/xs-abi/legacy-vendorarch-directory.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/team/pkg-perl/xs-abi/legacy-vendorarch-directory.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,11 +0,0 @@ -Tag: legacy-vendorarch-directory -Severity: error -Check: team/pkg-perl/xs-abi -Name-Spaced: yes -Explanation: Since 5.20, Debian perl packages use different directory for placing XS - libraries, which varies by API version and possibly architecture. Files - placed in the previously used directory (/usr/lib/perl5) will not be used by - perl. The build system needs to be fixed to use the value $Config{vendorarch} - (available from the Config module) instead of hardcoding the directory. - . - See Perl Policy 4.1. diff -Nru lintian-2.93.0/tags/u/udeb-contains-documentation-file.desc lintian-2.89.0ubuntu1/tags/u/udeb-contains-documentation-file.desc --- lintian-2.93.0/tags/u/udeb-contains-documentation-file.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/udeb-contains-documentation-file.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,4 @@ +Tag: udeb-contains-documentation-file +Severity: error +Check: documentation +Info: udeb packages should not contain any documentation. diff -Nru lintian-2.93.0/tags/u/udeb-contains-documentation-file.tag lintian-2.89.0ubuntu1/tags/u/udeb-contains-documentation-file.tag --- lintian-2.93.0/tags/u/udeb-contains-documentation-file.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/udeb-contains-documentation-file.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,4 +0,0 @@ -Tag: udeb-contains-documentation-file -Severity: error -Check: documentation -Explanation: udeb packages should not contain any documentation. diff -Nru lintian-2.93.0/tags/u/udeb-postinst-calls-ldconfig.desc lintian-2.89.0ubuntu1/tags/u/udeb-postinst-calls-ldconfig.desc --- lintian-2.93.0/tags/u/udeb-postinst-calls-ldconfig.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/udeb-postinst-calls-ldconfig.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: udeb-postinst-calls-ldconfig +Severity: error +Check: shared-libs +Renamed-From: udeb-postinst-must-not-call-ldconfig +Info: The udeb invokes ldconfig on install, which is an error in udebs. + . + ldconfig is not available and not needed in debian-installer. + . + Note that this tag may (despite what the name suggests) be issued if + the udeb uses a dpkg trigger to invoke ldconfig. diff -Nru lintian-2.93.0/tags/u/udeb-postinst-calls-ldconfig.tag lintian-2.89.0ubuntu1/tags/u/udeb-postinst-calls-ldconfig.tag --- lintian-2.93.0/tags/u/udeb-postinst-calls-ldconfig.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/udeb-postinst-calls-ldconfig.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,10 +0,0 @@ -Tag: udeb-postinst-calls-ldconfig -Severity: error -Check: shared-libs -Renamed-From: udeb-postinst-must-not-call-ldconfig -Explanation: The udeb invokes ldconfig on install, which is an error in udebs. - . - ldconfig is not available and not needed in debian-installer. - . - Note that this tag may (despite what the name suggests) be issued if - the udeb uses a dpkg trigger to invoke ldconfig. diff -Nru lintian-2.93.0/tags/u/udeb-uses-unsupported-compression-for-data-tarball.desc lintian-2.89.0ubuntu1/tags/u/udeb-uses-unsupported-compression-for-data-tarball.desc --- lintian-2.93.0/tags/u/udeb-uses-unsupported-compression-for-data-tarball.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/udeb-uses-unsupported-compression-for-data-tarball.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: udeb-uses-unsupported-compression-for-data-tarball +Severity: error +Check: deb-format +Info: The data tarball of this udeb package is not compressed in format + that udpkg (debian-installer's dpkg equivalent) does not support. Thus + the udeb is likely to be uninstallable and could break daily or weekly + d-i images. + . + Currently, udpkg supports .gz and .xz compressed tarballs. diff -Nru lintian-2.93.0/tags/u/udeb-uses-unsupported-compression-for-data-tarball.tag lintian-2.89.0ubuntu1/tags/u/udeb-uses-unsupported-compression-for-data-tarball.tag --- lintian-2.93.0/tags/u/udeb-uses-unsupported-compression-for-data-tarball.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/udeb-uses-unsupported-compression-for-data-tarball.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: udeb-uses-unsupported-compression-for-data-tarball -Severity: error -Check: deb-format -Explanation: The data tarball of this udeb package is not compressed in format - that udpkg (debian-installer's dpkg equivalent) does not support. Thus - the udeb is likely to be uninstallable and could break daily or weekly - d-i images. - . - Currently, udpkg supports .gz and .xz compressed tarballs. diff -Nru lintian-2.93.0/tags/u/udevadm-called-without-guard.desc lintian-2.89.0ubuntu1/tags/u/udevadm-called-without-guard.desc --- lintian-2.93.0/tags/u/udevadm-called-without-guard.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/udevadm-called-without-guard.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,15 @@ +Tag: udevadm-called-without-guard +Severity: warning +Certainty: possible +Check: scripts +Info: The specified maintainer script uses set -e but seems to + call udevadm(8) without a conditional guard. + . + udevadm can exist but be non-functional (such as inside a + chroot) and thus can result in package installation or upgrade failure + if the call fails. + . + Please guard the return code of the call via wrapping it in a suitable + if construct, appending || true or depending on the + udev package. +Ref: #890224, udevadm(8) diff -Nru lintian-2.93.0/tags/u/udevadm-called-without-guard.tag lintian-2.89.0ubuntu1/tags/u/udevadm-called-without-guard.tag --- lintian-2.93.0/tags/u/udevadm-called-without-guard.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/udevadm-called-without-guard.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,14 +0,0 @@ -Tag: udevadm-called-without-guard -Severity: warning -Check: scripts -Explanation: The specified maintainer script uses set -e but seems to - call udevadm(8) without a conditional guard. - . - udevadm can exist but be non-functional (such as inside a - chroot) and thus can result in package installation or upgrade failure - if the call fails. - . - Please guard the return code of the call via wrapping it in a suitable - if construct, appending || true or depending on the - udev package. -See-Also: Bug#890224, udevadm(8) diff -Nru lintian-2.93.0/tags/u/udev-rule-in-etc.desc lintian-2.89.0ubuntu1/tags/u/udev-rule-in-etc.desc --- lintian-2.93.0/tags/u/udev-rule-in-etc.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/udev-rule-in-etc.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: udev-rule-in-etc +Severity: error +Check: udev +Ref: #559208 +Info: This package ships a udev rule and installs it under + /etc/udev/rules.d, which is reserved for user-installed files. + The correct directory for system rules is /lib/udev/rules.d. diff -Nru lintian-2.93.0/tags/u/udev-rule-in-etc.tag lintian-2.89.0ubuntu1/tags/u/udev-rule-in-etc.tag --- lintian-2.93.0/tags/u/udev-rule-in-etc.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/udev-rule-in-etc.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: udev-rule-in-etc -Severity: error -Check: udev -See-Also: Bug#559208 -Explanation: This package ships a udev rule and installs it under - /etc/udev/rules.d, which is reserved for user-installed files. - The correct directory for system rules is /lib/udev/rules.d. diff -Nru lintian-2.93.0/tags/u/udev-rule-missing-subsystem.desc lintian-2.89.0ubuntu1/tags/u/udev-rule-missing-subsystem.desc --- lintian-2.93.0/tags/u/udev-rule-missing-subsystem.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/udev-rule-missing-subsystem.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: udev-rule-missing-subsystem +Severity: warning +Certainty: possible +Check: udev +Ref: https://wiki.debian.org/USB/GadgetSetup +Info: The package matches vendor/product IDs without specifying + subsystem. The vendor/product IDs are subsystem specific. Matching + rules using those should specify subsystem too, for example by using + SUBSYSTEM=="usb" at the start of the matching rule. diff -Nru lintian-2.93.0/tags/u/udev-rule-missing-subsystem.tag lintian-2.89.0ubuntu1/tags/u/udev-rule-missing-subsystem.tag --- lintian-2.93.0/tags/u/udev-rule-missing-subsystem.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/udev-rule-missing-subsystem.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: udev-rule-missing-subsystem -Severity: warning -Check: udev -See-Also: https://wiki.debian.org/USB/GadgetSetup -Explanation: The package matches vendor/product IDs without specifying - subsystem. The vendor/product IDs are subsystem specific. Matching - rules using those should specify subsystem too, for example by using - SUBSYSTEM=="usb" at the start of the matching rule. diff -Nru lintian-2.93.0/tags/u/udev-rule-missing-uaccess.desc lintian-2.89.0ubuntu1/tags/u/udev-rule-missing-uaccess.desc --- lintian-2.93.0/tags/u/udev-rule-missing-uaccess.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/udev-rule-missing-uaccess.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: udev-rule-missing-uaccess +Severity: warning +Certainty: possible +Check: udev +Ref: https://wiki.debian.org/USB/GadgetSetup +Info: The package set up a device for user access without using the + uaccess tag. Some udev rules get the same effect using other markers + enabling console user access using rules in + /lib/udev/rules.d/70-uaccess.rules. Others should specify + TAG+="uaccess" in the udev rule. diff -Nru lintian-2.93.0/tags/u/udev-rule-missing-uaccess.tag lintian-2.89.0ubuntu1/tags/u/udev-rule-missing-uaccess.tag --- lintian-2.93.0/tags/u/udev-rule-missing-uaccess.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/udev-rule-missing-uaccess.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: udev-rule-missing-uaccess -Severity: warning -Check: udev -See-Also: https://wiki.debian.org/USB/GadgetSetup -Explanation: The package set up a device for user access without using the - uaccess tag. Some udev rules get the same effect using other markers - enabling console user access using rules in - /lib/udev/rules.d/70-uaccess.rules. Others should specify - TAG+="uaccess" in the udev rule. diff -Nru lintian-2.93.0/tags/u/udev-rule-unreadable.desc lintian-2.89.0ubuntu1/tags/u/udev-rule-unreadable.desc --- lintian-2.93.0/tags/u/udev-rule-unreadable.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/udev-rule-unreadable.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: udev-rule-unreadable +Severity: error +Check: udev +Ref: https://wiki.debian.org/USB/GadgetSetup +Info: The udev rule entry should be a file + The package contain a non-file in /lib/udev/rules.d/. The directory + should only contain readable files. diff -Nru lintian-2.93.0/tags/u/udev-rule-unreadable.tag lintian-2.89.0ubuntu1/tags/u/udev-rule-unreadable.tag --- lintian-2.93.0/tags/u/udev-rule-unreadable.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/udev-rule-unreadable.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: udev-rule-unreadable -Severity: error -Check: udev -See-Also: https://wiki.debian.org/USB/GadgetSetup -Explanation: The udev rule entry should be a file - The package contain a non-file in /lib/udev/rules.d/. The directory - should only contain readable files. diff -Nru lintian-2.93.0/tags/u/uncompressed-manual-page.desc lintian-2.89.0ubuntu1/tags/u/uncompressed-manual-page.desc --- lintian-2.93.0/tags/u/uncompressed-manual-page.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/uncompressed-manual-page.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: uncompressed-manual-page +Severity: error +Check: documentation/manual +Renamed-From: manpage-not-compressed +Info: Manual pages have to be installed compressed (using "gzip -9n"). +Ref: policy 12.1 diff -Nru lintian-2.93.0/tags/u/uncompressed-manual-page.tag lintian-2.89.0ubuntu1/tags/u/uncompressed-manual-page.tag --- lintian-2.93.0/tags/u/uncompressed-manual-page.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/uncompressed-manual-page.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: uncompressed-manual-page -Severity: error -Check: documentation/manual -Renamed-From: manpage-not-compressed -Explanation: Manual pages have to be installed compressed (using "gzip -9n"). -See-Also: policy 12.1 diff -Nru lintian-2.93.0/tags/u/unconditional-use-of-dpkg-statoverride.desc lintian-2.89.0ubuntu1/tags/u/unconditional-use-of-dpkg-statoverride.desc --- lintian-2.93.0/tags/u/unconditional-use-of-dpkg-statoverride.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/unconditional-use-of-dpkg-statoverride.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: unconditional-use-of-dpkg-statoverride +Severity: warning +Certainty: possible +Check: scripts +Info: The maintainer script appears to use dpkg-statoverride --add + without a prior call to dpkg-statoverride --list to check the + current status. +Ref: policy 10.9.1 diff -Nru lintian-2.93.0/tags/u/unconditional-use-of-dpkg-statoverride.tag lintian-2.89.0ubuntu1/tags/u/unconditional-use-of-dpkg-statoverride.tag --- lintian-2.93.0/tags/u/unconditional-use-of-dpkg-statoverride.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/unconditional-use-of-dpkg-statoverride.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: unconditional-use-of-dpkg-statoverride -Severity: warning -Check: scripts -Explanation: The maintainer script appears to use dpkg-statoverride --add - without a prior call to dpkg-statoverride --list to check the - current status. -See-Also: policy 10.9.1 diff -Nru lintian-2.93.0/tags/u/undocumented-manual-page.desc lintian-2.89.0ubuntu1/tags/u/undocumented-manual-page.desc --- lintian-2.93.0/tags/u/undocumented-manual-page.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/undocumented-manual-page.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,17 @@ +Tag: undocumented-manual-page +Severity: warning +Check: documentation/manual +Renamed-From: link-to-undocumented-manpage +Info: Symbolic links to the undocumented(7) manual page may be provided + if no manual page is available, but that is deprecated. + . + The lack of a manual page is still a bug, and if at all possible you + should write one yourself. + . + For help with writing manual pages, refer to the Man-Page-HOWTO at + http://www.schweikhardt.net/man_page_howto.html, the examples created + by dh_make, or the + /usr/share/doc/man-db/examples directory. + If the package provides --help output, you might want to use + the help2man utility to generate a simple manual page. +Ref: policy 12.1 diff -Nru lintian-2.93.0/tags/u/undocumented-manual-page.tag lintian-2.89.0ubuntu1/tags/u/undocumented-manual-page.tag --- lintian-2.93.0/tags/u/undocumented-manual-page.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/undocumented-manual-page.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,17 +0,0 @@ -Tag: undocumented-manual-page -Severity: warning -Check: documentation/manual -Renamed-From: link-to-undocumented-manpage -Explanation: Symbolic links to the undocumented(7) manual page may be provided - if no manual page is available, but that is deprecated. - . - The lack of a manual page is still a bug, and if at all possible you - should write one yourself. - . - For help with writing manual pages, refer to the - [Man-Page-HOWTO](http://www.schweikhardt.net/man_page_howto.html), the examples created - by dh_make, or the - /usr/share/doc/man-db/examples directory. - If the package provides --help output, you might want to use - the help2man utility to generate a simple manual page. -See-Also: policy 12.1 diff -Nru lintian-2.93.0/tags/u/unknown-architecture.desc lintian-2.89.0ubuntu1/tags/u/unknown-architecture.desc --- lintian-2.93.0/tags/u/unknown-architecture.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/unknown-architecture.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: unknown-architecture +Severity: warning +Certainty: possible +Check: fields/architecture +Info: This package claims to be for an unknown architecture. The + architecture should be one of the values supported by dpkg or one of the + special values "all" or "any". The special value "source" is only used + in *.changes files and does not make sense in a binary package or a *.dsc + file. diff -Nru lintian-2.93.0/tags/u/unknown-architecture.tag lintian-2.89.0ubuntu1/tags/u/unknown-architecture.tag --- lintian-2.93.0/tags/u/unknown-architecture.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/unknown-architecture.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: unknown-architecture -Severity: warning -Check: fields/architecture -Explanation: This package claims to be for an unknown architecture. The - architecture should be one of the values supported by dpkg or one of the - special values "all" or "any". The special value "source" is only used - in *.changes files and does not make sense in a binary package or a *.dsc - file. diff -Nru lintian-2.93.0/tags/u/unknown-control-file.desc lintian-2.89.0ubuntu1/tags/u/unknown-control-file.desc --- lintian-2.93.0/tags/u/unknown-control-file.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/unknown-control-file.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: unknown-control-file +Severity: warning +Certainty: possible +Check: control-files +Ref: policy 2.2* +Info: The package contains an unknown control file. Policy says that + putting additional files in the package control area is not generally a + good idea. diff -Nru lintian-2.93.0/tags/u/unknown-control-file.tag lintian-2.89.0ubuntu1/tags/u/unknown-control-file.tag --- lintian-2.93.0/tags/u/unknown-control-file.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/unknown-control-file.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: unknown-control-file -Severity: warning -Check: control-files -See-Also: policy 2.2* -Explanation: The package contains an unknown control file. Policy says that - putting additional files in the package control area is not generally a - good idea. diff -Nru lintian-2.93.0/tags/u/unknown-control-interpreter.desc lintian-2.89.0ubuntu1/tags/u/unknown-control-interpreter.desc --- lintian-2.93.0/tags/u/unknown-control-interpreter.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/unknown-control-interpreter.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: unknown-control-interpreter +Severity: error +Certainty: possible +Check: scripts +Info: This package contains a maintainer script that uses an interpreter + that the Lintian maintainers have not heard of. This is usually a typo + for a common interpreter. If not, please file a wishlist bug on Lintian + so that the Lintian maintainers can add this interpreter to their list. diff -Nru lintian-2.93.0/tags/u/unknown-control-interpreter.tag lintian-2.89.0ubuntu1/tags/u/unknown-control-interpreter.tag --- lintian-2.93.0/tags/u/unknown-control-interpreter.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/unknown-control-interpreter.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: unknown-control-interpreter -Severity: error -Check: scripts -Explanation: This package contains a maintainer script that uses an interpreter - that the Lintian maintainers have not heard of. This is usually a typo - for a common interpreter. If not, please file a wishlist bug on Lintian - so that the Lintian maintainers can add this interpreter to their list. diff -Nru lintian-2.93.0/tags/u/unknown-copyright-format-uri.desc lintian-2.89.0ubuntu1/tags/u/unknown-copyright-format-uri.desc --- lintian-2.93.0/tags/u/unknown-copyright-format-uri.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/unknown-copyright-format-uri.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: unknown-copyright-format-uri +Severity: pedantic +Certainty: wild-guess +Check: debian/copyright/dep5 +Info: The copyright file appears to intended as machine-readable, but Lintian + cannot recognize its format URI. It could be a typo for a common URI or a + syntax error in the first paragraph. diff -Nru lintian-2.93.0/tags/u/unknown-copyright-format-uri.tag lintian-2.89.0ubuntu1/tags/u/unknown-copyright-format-uri.tag --- lintian-2.93.0/tags/u/unknown-copyright-format-uri.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/unknown-copyright-format-uri.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: unknown-copyright-format-uri -Severity: pedantic -Check: debian/copyright/dep5 -Explanation: The copyright file appears to intended as machine-readable, but Lintian - cannot recognize its format URI. It could be a typo for a common URI or a - syntax error in the first paragraph. diff -Nru lintian-2.93.0/tags/u/unknown-debconf-priority.desc lintian-2.89.0ubuntu1/tags/u/unknown-debconf-priority.desc --- lintian-2.93.0/tags/u/unknown-debconf-priority.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/unknown-debconf-priority.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: unknown-debconf-priority +Severity: error +Check: debian/debconf +Info: The given maintainer script calls db_input or db_text with a + first argument that doesn't match one of the known priorities. The + supported priorities are low, medium, high, and critical. +Ref: debconf-devel(7) diff -Nru lintian-2.93.0/tags/u/unknown-debconf-priority.tag lintian-2.89.0ubuntu1/tags/u/unknown-debconf-priority.tag --- lintian-2.93.0/tags/u/unknown-debconf-priority.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/unknown-debconf-priority.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: unknown-debconf-priority -Severity: error -Check: debian/debconf -Explanation: The given maintainer script calls db_input or db_text with a - first argument that doesn't match one of the known priorities. The - supported priorities are low, medium, high, and critical. -See-Also: debconf-devel(7) diff -Nru lintian-2.93.0/tags/u/unknown-encoding-in-po-file.desc lintian-2.89.0ubuntu1/tags/u/unknown-encoding-in-po-file.desc --- lintian-2.93.0/tags/u/unknown-encoding-in-po-file.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/unknown-encoding-in-po-file.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,5 @@ +Tag: unknown-encoding-in-po-file +Severity: warning +Check: debian/po-debconf +Info: Encoding must be declared in PO files. Otherwise, charset + conversions cannot be performed. diff -Nru lintian-2.93.0/tags/u/unknown-encoding-in-po-file.tag lintian-2.89.0ubuntu1/tags/u/unknown-encoding-in-po-file.tag --- lintian-2.93.0/tags/u/unknown-encoding-in-po-file.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/unknown-encoding-in-po-file.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,5 +0,0 @@ -Tag: unknown-encoding-in-po-file -Severity: warning -Check: debian/po-debconf -Explanation: Encoding must be declared in PO files. Otherwise, charset - conversions cannot be performed. diff -Nru lintian-2.93.0/tags/u/unknown-essential-value.desc lintian-2.89.0ubuntu1/tags/u/unknown-essential-value.desc --- lintian-2.93.0/tags/u/unknown-essential-value.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/unknown-essential-value.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,5 @@ +Tag: unknown-essential-value +Severity: error +Check: fields/essential +Info: The only valid values for the Essential field are yes and no. +Ref: policy 5.6.9 diff -Nru lintian-2.93.0/tags/u/unknown-essential-value.tag lintian-2.89.0ubuntu1/tags/u/unknown-essential-value.tag --- lintian-2.93.0/tags/u/unknown-essential-value.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/unknown-essential-value.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,5 +0,0 @@ -Tag: unknown-essential-value -Severity: error -Check: fields/essential -Explanation: The only valid values for the Essential field are yes and no. -See-Also: policy 5.6.9 diff -Nru lintian-2.93.0/tags/u/unknown-field.desc lintian-2.89.0ubuntu1/tags/u/unknown-field.desc --- lintian-2.93.0/tags/u/unknown-field.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/unknown-field.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: unknown-field +Severity: warning +Check: fields/unknown +Renamed-From: unknown-field-in-dsc + unknown-field-in-control +Info: See the Policy Manual for a list of the possible fields in + a package control files. +Ref: policy 5.3, policy 5.4 diff -Nru lintian-2.93.0/tags/u/unknown-field-in-templates.desc lintian-2.89.0ubuntu1/tags/u/unknown-field-in-templates.desc --- lintian-2.93.0/tags/u/unknown-field-in-templates.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/unknown-field-in-templates.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: unknown-field-in-templates +Severity: error +Check: debian/debconf +Info: Valid fields are currently "Template:", "Type:", "Choices:", "Default:", + and "Description:". +Ref: debconf-spec 3.1, debconf-devel(7) diff -Nru lintian-2.93.0/tags/u/unknown-field-in-templates.tag lintian-2.89.0ubuntu1/tags/u/unknown-field-in-templates.tag --- lintian-2.93.0/tags/u/unknown-field-in-templates.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/unknown-field-in-templates.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: unknown-field-in-templates -Severity: error -Check: debian/debconf -Explanation: Valid fields are currently "Template:", "Type:", "Choices:", "Default:", - and "Description:". -See-Also: debconf-spec 3.1, debconf-devel(7) diff -Nru lintian-2.93.0/tags/u/unknown-field.tag lintian-2.89.0ubuntu1/tags/u/unknown-field.tag --- lintian-2.93.0/tags/u/unknown-field.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/unknown-field.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: unknown-field -Severity: warning -Check: fields/unknown -Renamed-From: unknown-field-in-dsc - unknown-field-in-control -Explanation: See the Policy Manual for a list of the possible fields in - a package control files. -See-Also: policy 5.3, policy 5.4 diff -Nru lintian-2.93.0/tags/u/unknown-file-in-debian-source.desc lintian-2.89.0ubuntu1/tags/u/unknown-file-in-debian-source.desc --- lintian-2.93.0/tags/u/unknown-file-in-debian-source.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/unknown-file-in-debian-source.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,15 @@ +Tag: unknown-file-in-debian-source +Severity: error +Certainty: possible +Check: debian/source-dir +Info: The source package contains a file in debian/source/ that Lintian + doesn't know about. Currently the following files are recognized: + . + * format + * include-binaries + * lintian-overrides + * options + * patch-header + . + This tag is emitted in case you mistyped the name of one of the above + files. diff -Nru lintian-2.93.0/tags/u/unknown-file-in-debian-source.tag lintian-2.89.0ubuntu1/tags/u/unknown-file-in-debian-source.tag --- lintian-2.93.0/tags/u/unknown-file-in-debian-source.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/unknown-file-in-debian-source.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,14 +0,0 @@ -Tag: unknown-file-in-debian-source -Severity: error -Check: debian/source-dir -Explanation: The source package contains a file in debian/source/ that Lintian - doesn't know about. Currently the following files are recognized: - . - - format - - include-binaries - - lintian-overrides - - options - - patch-header - . - This tag is emitted in case you mistyped the name of one of the above - files. diff -Nru lintian-2.93.0/tags/u/unknown-file-in-python-module-directory.desc lintian-2.89.0ubuntu1/tags/u/unknown-file-in-python-module-directory.desc --- lintian-2.93.0/tags/u/unknown-file-in-python-module-directory.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/unknown-file-in-python-module-directory.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: unknown-file-in-python-module-directory +Severity: error +Check: languages/python +Info: This package installs the specifiied "non-Python" file in the + top-level of a Python library directory. + . + This was either a mistake and/or will likely to cause conflicts with other + packages. diff -Nru lintian-2.93.0/tags/u/unknown-file-in-python-module-directory.tag lintian-2.89.0ubuntu1/tags/u/unknown-file-in-python-module-directory.tag --- lintian-2.93.0/tags/u/unknown-file-in-python-module-directory.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/unknown-file-in-python-module-directory.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: unknown-file-in-python-module-directory -Severity: error -Check: languages/python -Explanation: This package installs the specifiied "non-Python" file in the - top-level of a Python library directory. - . - This was either a mistake and/or will likely to cause conflicts with other - packages. diff -Nru lintian-2.93.0/tags/u/unknown-java-class-version.desc lintian-2.89.0ubuntu1/tags/u/unknown-java-class-version.desc --- lintian-2.93.0/tags/u/unknown-java-class-version.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/unknown-java-class-version.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,5 @@ +Tag: unknown-java-class-version +Severity: warning +Check: languages/java +Info: The package contains a Jar file with Java class files compiled for an + unknown Java version. The class file may be corrupt. diff -Nru lintian-2.93.0/tags/u/unknown-java-class-version.tag lintian-2.89.0ubuntu1/tags/u/unknown-java-class-version.tag --- lintian-2.93.0/tags/u/unknown-java-class-version.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/unknown-java-class-version.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,5 +0,0 @@ -Tag: unknown-java-class-version -Severity: warning -Check: languages/java -Explanation: The package contains a Jar file with Java class files compiled for an - unknown Java version. The class file may be corrupt. diff -Nru lintian-2.93.0/tags/u/unknown-locale-code.desc lintian-2.89.0ubuntu1/tags/u/unknown-locale-code.desc --- lintian-2.93.0/tags/u/unknown-locale-code.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/unknown-locale-code.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,13 @@ +Tag: unknown-locale-code +Severity: warning +Check: files/locales +Ref: http://www.loc.gov/standards/iso639-2/php/code_list.php +Info: The package appears to ship locales for a language but uses an + unknown locale code as a subdirectory of /usr/share/locale. + This usually results in users of the intended target language not + finding the locale. The language codes used in the locale directories + are those from the ISO 639-1 and ISO 639-2 standards, not those + usually used as TLDs (which are from the ISO 3166 standard). + . + It is possible that the language code was mistyped or incorrectly + guessed from the language's or country's name. diff -Nru lintian-2.93.0/tags/u/unknown-locale-code.tag lintian-2.89.0ubuntu1/tags/u/unknown-locale-code.tag --- lintian-2.93.0/tags/u/unknown-locale-code.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/unknown-locale-code.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,13 +0,0 @@ -Tag: unknown-locale-code -Severity: warning -Check: files/locales -See-Also: http://www.loc.gov/standards/iso639-2/php/code_list.php -Explanation: The package appears to ship locales for a language but uses an - unknown locale code as a subdirectory of /usr/share/locale. - This usually results in users of the intended target language not - finding the locale. The language codes used in the locale directories - are those from the ISO 639-1 and ISO 639-2 standards, not those - usually used as TLDs (which are from the ISO 3166 standard). - . - It is possible that the language code was mistyped or incorrectly - guessed from the language's or country's name. diff -Nru lintian-2.93.0/tags/u/unknown-meta-field-in-symbols-file.desc lintian-2.89.0ubuntu1/tags/u/unknown-meta-field-in-symbols-file.desc --- lintian-2.93.0/tags/u/unknown-meta-field-in-symbols-file.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/unknown-meta-field-in-symbols-file.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: unknown-meta-field-in-symbols-file +Severity: error +Check: shared-libs +Info: The symbols control file contains an unknown meta-information field. + . + A list of currently supported fields may be found in deb-symbols(5). +Ref: deb-symbols(5) diff -Nru lintian-2.93.0/tags/u/unknown-meta-field-in-symbols-file.tag lintian-2.89.0ubuntu1/tags/u/unknown-meta-field-in-symbols-file.tag --- lintian-2.93.0/tags/u/unknown-meta-field-in-symbols-file.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/unknown-meta-field-in-symbols-file.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: unknown-meta-field-in-symbols-file -Severity: error -Check: shared-libs -Explanation: The symbols control file contains an unknown meta-information field. - . - A list of currently supported fields may be found in deb-symbols(5). -See-Also: deb-symbols(5) diff -Nru lintian-2.93.0/tags/u/unknown-multi-arch-value.desc lintian-2.89.0ubuntu1/tags/u/unknown-multi-arch-value.desc --- lintian-2.93.0/tags/u/unknown-multi-arch-value.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/unknown-multi-arch-value.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,5 @@ +Tag: unknown-multi-arch-value +Severity: error +Check: fields/multi-arch +Info: The package has an unknown value in its Multi-Arch field. The + value must be one of "no", "same", "foreign" or "allowed". diff -Nru lintian-2.93.0/tags/u/unknown-multi-arch-value.tag lintian-2.89.0ubuntu1/tags/u/unknown-multi-arch-value.tag --- lintian-2.93.0/tags/u/unknown-multi-arch-value.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/unknown-multi-arch-value.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,5 +0,0 @@ -Tag: unknown-multi-arch-value -Severity: error -Check: fields/multi-arch -Explanation: The package has an unknown value in its Multi-Arch field. The - value must be one of "no", "same", "foreign" or "allowed". diff -Nru lintian-2.93.0/tags/u/unknown-paragraph-in-dep5-copyright.desc lintian-2.89.0ubuntu1/tags/u/unknown-paragraph-in-dep5-copyright.desc --- lintian-2.93.0/tags/u/unknown-paragraph-in-dep5-copyright.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/unknown-paragraph-in-dep5-copyright.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: unknown-paragraph-in-dep5-copyright +Severity: warning +Certainty: possible +Check: debian/copyright/dep5 +Ref: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ +Info: The machine-readable copyright file contains a paragraph that is neither + a standalone license paragraph nor a files paragraph. diff -Nru lintian-2.93.0/tags/u/unknown-paragraph-in-dep5-copyright.tag lintian-2.89.0ubuntu1/tags/u/unknown-paragraph-in-dep5-copyright.tag --- lintian-2.93.0/tags/u/unknown-paragraph-in-dep5-copyright.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/unknown-paragraph-in-dep5-copyright.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: unknown-paragraph-in-dep5-copyright -Severity: warning -Check: debian/copyright/dep5 -See-Also: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ -Explanation: The machine-readable copyright file contains a paragraph that is neither - a standalone license paragraph nor a files paragraph. diff -Nru lintian-2.93.0/tags/u/unknown-priority.desc lintian-2.89.0ubuntu1/tags/u/unknown-priority.desc --- lintian-2.93.0/tags/u/unknown-priority.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/unknown-priority.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: unknown-priority +Severity: error +Check: fields/priority +Info: The "Priority:" field in this package's control file is not one of + the priorities defined in the Policy Manual. +Ref: policy 2.5 diff -Nru lintian-2.93.0/tags/u/unknown-priority.tag lintian-2.89.0ubuntu1/tags/u/unknown-priority.tag --- lintian-2.93.0/tags/u/unknown-priority.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/unknown-priority.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: unknown-priority -Severity: error -Check: fields/priority -Explanation: The "Priority:" field in this package's control file is not one of - the priorities defined in the Policy Manual. -See-Also: policy 2.5 diff -Nru lintian-2.93.0/tags/u/unknown-runtime-tests-feature.desc lintian-2.89.0ubuntu1/tags/u/unknown-runtime-tests-feature.desc --- lintian-2.93.0/tags/u/unknown-runtime-tests-feature.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/unknown-runtime-tests-feature.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: unknown-runtime-tests-feature +Severity: pedantic +Certainty: wild-guess +Check: testsuite +Info: A paragraph in debian/tests/control mentions a non-standard + value for the Features field. Though allowed, this may indicate an + error, as the value will be ignored. +Ref: https://salsa.debian.org/ci-team/autopkgtest/tree/master/doc/README.package-tests.rst diff -Nru lintian-2.93.0/tags/u/unknown-runtime-tests-feature.tag lintian-2.89.0ubuntu1/tags/u/unknown-runtime-tests-feature.tag --- lintian-2.93.0/tags/u/unknown-runtime-tests-feature.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/unknown-runtime-tests-feature.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: unknown-runtime-tests-feature -Severity: pedantic -Check: testsuite -Explanation: A paragraph in debian/tests/control mentions a non-standard - value for the Features field. Though allowed, this may indicate an - error, as the value will be ignored. -See-Also: https://salsa.debian.org/ci-team/autopkgtest/tree/master/doc/README.package-tests.rst diff -Nru lintian-2.93.0/tags/u/unknown-runtime-tests-field.desc lintian-2.89.0ubuntu1/tags/u/unknown-runtime-tests-field.desc --- lintian-2.93.0/tags/u/unknown-runtime-tests-field.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/unknown-runtime-tests-field.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: unknown-runtime-tests-field +Severity: pedantic +Certainty: wild-guess +Check: testsuite +Info: A paragraph in debian/tests/control mentions a non-standard + field. Though allowed, this may indicate an error, as the whole + paragraph will be ignored. +Ref: https://salsa.debian.org/ci-team/autopkgtest/tree/master/doc/README.package-tests.rst diff -Nru lintian-2.93.0/tags/u/unknown-runtime-tests-field.tag lintian-2.89.0ubuntu1/tags/u/unknown-runtime-tests-field.tag --- lintian-2.93.0/tags/u/unknown-runtime-tests-field.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/unknown-runtime-tests-field.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: unknown-runtime-tests-field -Severity: pedantic -Check: testsuite -Explanation: A paragraph in debian/tests/control mentions a non-standard - field. Though allowed, this may indicate an error, as the whole - paragraph will be ignored. -See-Also: https://salsa.debian.org/ci-team/autopkgtest/tree/master/doc/README.package-tests.rst diff -Nru lintian-2.93.0/tags/u/unknown-runtime-tests-restriction.desc lintian-2.89.0ubuntu1/tags/u/unknown-runtime-tests-restriction.desc --- lintian-2.93.0/tags/u/unknown-runtime-tests-restriction.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/unknown-runtime-tests-restriction.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: unknown-runtime-tests-restriction +Severity: pedantic +Certainty: wild-guess +Check: testsuite +Info: A paragraph in debian/tests/control mentions a non-standard + value for the Restrictions field. Though allowed, this may indicate an + error, as the whole paragraph will be ignored. +Ref: https://salsa.debian.org/ci-team/autopkgtest/tree/master/doc/README.package-tests.rst diff -Nru lintian-2.93.0/tags/u/unknown-runtime-tests-restriction.tag lintian-2.89.0ubuntu1/tags/u/unknown-runtime-tests-restriction.tag --- lintian-2.93.0/tags/u/unknown-runtime-tests-restriction.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/unknown-runtime-tests-restriction.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: unknown-runtime-tests-restriction -Severity: pedantic -Check: testsuite -Explanation: A paragraph in debian/tests/control mentions a non-standard - value for the Restrictions field. Though allowed, this may indicate an - error, as the whole paragraph will be ignored. -See-Also: https://salsa.debian.org/ci-team/autopkgtest/tree/master/doc/README.package-tests.rst diff -Nru lintian-2.93.0/tags/u/unknown-section.desc lintian-2.89.0ubuntu1/tags/u/unknown-section.desc --- lintian-2.93.0/tags/u/unknown-section.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/unknown-section.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,17 @@ +Tag: unknown-section +Severity: warning +Check: fields/section +Info: The "Section:" field in this package's control file is not one of + the sections in use on the ftp archive. Valid sections are currently + admin, comm, cli-mono, database, debug, devel, doc, + editors, electronics, embedded, fonts, games, gnome, gnu-r, + gnustep, graphics, hamradio, haskell, httpd, interpreters, + java, javascript, kde, libdevel, libs, lisp, localization, kernel, mail, + math, misc, net, news, ocaml, oldlibs, otherosfs, perl, + php, python, ruby, rust, science, shells, sound, tex, text, + utils, vcs, video, web, x11, xfce, zope. + . + The section name should be preceded by "non-free/" if the package + is in the non-free archive area, and by "contrib/" if the package + is in the contrib archive area. +Ref: policy 2.4 diff -Nru lintian-2.93.0/tags/u/unknown-section.tag lintian-2.89.0ubuntu1/tags/u/unknown-section.tag --- lintian-2.93.0/tags/u/unknown-section.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/unknown-section.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,17 +0,0 @@ -Tag: unknown-section -Severity: warning -Check: fields/section -Explanation: The "Section:" field in this package's control file is not one of - the sections in use on the ftp archive. Valid sections are currently - admin, comm, cli-mono, database, debug, devel, doc, - editors, electronics, embedded, fonts, games, gnome, gnu-r, - gnustep, graphics, hamradio, haskell, httpd, interpreters, - java, javascript, kde, libdevel, libs, lisp, localization, kernel, mail, - math, misc, net, news, ocaml, oldlibs, otherosfs, perl, - php, python, ruby, rust, science, shells, sound, tex, text, - utils, vcs, video, web, x11, xfce, zope. - . - The section name should be preceded by "non-free/" if the package - is in the non-free archive area, and by "contrib/" if the package - is in the contrib archive area. -See-Also: policy 2.4 diff -Nru lintian-2.93.0/tags/u/unknown-template-type.desc lintian-2.89.0ubuntu1/tags/u/unknown-template-type.desc --- lintian-2.93.0/tags/u/unknown-template-type.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/unknown-template-type.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: unknown-template-type +Severity: error +Check: debian/debconf +Info: A "Type:" field in a templates file provided by this package uses an + unknown data type. Valid types are currently "string", "boolean", "select", + "multiselect", "note", "text", and "password". diff -Nru lintian-2.93.0/tags/u/unknown-template-type.tag lintian-2.89.0ubuntu1/tags/u/unknown-template-type.tag --- lintian-2.93.0/tags/u/unknown-template-type.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/unknown-template-type.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: unknown-template-type -Severity: error -Check: debian/debconf -Explanation: A "Type:" field in a templates file provided by this package uses an - unknown data type. Valid types are currently "string", "boolean", "select", - "multiselect", "note", "text", and "password". diff -Nru lintian-2.93.0/tags/u/unknown-testsuite.desc lintian-2.89.0ubuntu1/tags/u/unknown-testsuite.desc --- lintian-2.93.0/tags/u/unknown-testsuite.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/unknown-testsuite.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: unknown-testsuite +Severity: warning +Check: testsuite +Info: The dsc file sets Testsuite to an unrecognised value. This + field is most probably copied by dpkg-source from Testsuite in + debian/control. +Ref: https://salsa.debian.org/ci-team/autopkgtest/tree/master/doc/README.package-tests.rst diff -Nru lintian-2.93.0/tags/u/unknown-testsuite.tag lintian-2.89.0ubuntu1/tags/u/unknown-testsuite.tag --- lintian-2.93.0/tags/u/unknown-testsuite.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/unknown-testsuite.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: unknown-testsuite -Severity: warning -Check: testsuite -Explanation: The dsc file sets Testsuite to an unrecognised value. This - field is most probably copied by dpkg-source from Testsuite in - debian/control. -See-Also: https://salsa.debian.org/ci-team/autopkgtest/tree/master/doc/README.package-tests.rst diff -Nru lintian-2.93.0/tags/u/unknown-trigger.desc lintian-2.89.0ubuntu1/tags/u/unknown-trigger.desc --- lintian-2.93.0/tags/u/unknown-trigger.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/unknown-trigger.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: unknown-trigger +Severity: error +Certainty: possible +Check: triggers +Info: The package has a trigger that Lintian does not recognise in its + control file. + . + The package may be uninstallable if dpkg does not support the trigger. +Ref: deb-triggers(5) diff -Nru lintian-2.93.0/tags/u/unknown-trigger.tag lintian-2.89.0ubuntu1/tags/u/unknown-trigger.tag --- lintian-2.93.0/tags/u/unknown-trigger.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/unknown-trigger.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: unknown-trigger -Severity: error -Check: triggers -Explanation: The package has a trigger that Lintian does not recognise in its - control file. - . - The package may be uninstallable if dpkg does not support the trigger. -See-Also: deb-triggers(5) diff -Nru lintian-2.93.0/tags/u/unnecessary-source-date-epoch-assignment.desc lintian-2.89.0ubuntu1/tags/u/unnecessary-source-date-epoch-assignment.desc --- lintian-2.93.0/tags/u/unnecessary-source-date-epoch-assignment.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/unnecessary-source-date-epoch-assignment.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,11 @@ +Tag: unnecessary-source-date-epoch-assignment +Severity: info +Check: debian/rules +Info: There is an assignment to a SOURCE_DATE_EPOCH variable in the + debian/rules file. + . + As of dpkg 1.18.8, this is no longer necessary as dpkg exports this + variable if it is not already set. However, you can also include + /usr/share/dpkg/pkg-info.mk or /usr/share/dpkg/default.mk + to ensure it is exported. +Ref: https://reproducible-builds.org/specs/source-date-epoch/ diff -Nru lintian-2.93.0/tags/u/unnecessary-source-date-epoch-assignment.tag lintian-2.89.0ubuntu1/tags/u/unnecessary-source-date-epoch-assignment.tag --- lintian-2.93.0/tags/u/unnecessary-source-date-epoch-assignment.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/unnecessary-source-date-epoch-assignment.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,11 +0,0 @@ -Tag: unnecessary-source-date-epoch-assignment -Severity: info -Check: debian/rules -Explanation: There is an assignment to a SOURCE_DATE_EPOCH variable in the - debian/rules file. - . - As of dpkg 1.18.8, this is no longer necessary as dpkg exports this - variable if it is not already set. However, you can also include - /usr/share/dpkg/pkg-info.mk or /usr/share/dpkg/default.mk - to ensure it is exported. -See-Also: https://reproducible-builds.org/specs/source-date-epoch/ diff -Nru lintian-2.93.0/tags/u/unnecessary-team-upload.desc lintian-2.89.0ubuntu1/tags/u/unnecessary-team-upload.desc --- lintian-2.93.0/tags/u/unnecessary-team-upload.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/unnecessary-team-upload.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,5 @@ +Tag: unnecessary-team-upload +Severity: warning +Check: nmu +Info: The debian/changelog file refers to a "Team upload" but the + uploader is listed amongst the Maintainer/Uploaders. diff -Nru lintian-2.93.0/tags/u/unnecessary-team-upload.tag lintian-2.89.0ubuntu1/tags/u/unnecessary-team-upload.tag --- lintian-2.93.0/tags/u/unnecessary-team-upload.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/unnecessary-team-upload.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,5 +0,0 @@ -Tag: unnecessary-team-upload -Severity: warning -Check: nmu -Explanation: The debian/changelog file refers to a "Team upload" but the - uploader is listed amongst the Maintainer/Uploaders. diff -Nru lintian-2.93.0/tags/u/unnecessary-testsuite-autopkgtest-field.desc lintian-2.89.0ubuntu1/tags/u/unnecessary-testsuite-autopkgtest-field.desc --- lintian-2.93.0/tags/u/unnecessary-testsuite-autopkgtest-field.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/unnecessary-testsuite-autopkgtest-field.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: unnecessary-testsuite-autopkgtest-field +Severity: warning +Check: testsuite +Info: You do not need to specify a Testsuite: autopkgtest field if + a debian/tests/control file exists. It is automatically added by + dpkg-source(1) since dpkg 1.17.1. + . + Please remove this line from your debian/control file. +Renamed-From: + unnecessary-testsuite-autopkgtest-header diff -Nru lintian-2.93.0/tags/u/unnecessary-testsuite-autopkgtest-field.tag lintian-2.89.0ubuntu1/tags/u/unnecessary-testsuite-autopkgtest-field.tag --- lintian-2.93.0/tags/u/unnecessary-testsuite-autopkgtest-field.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/unnecessary-testsuite-autopkgtest-field.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,10 +0,0 @@ -Tag: unnecessary-testsuite-autopkgtest-field -Severity: warning -Check: testsuite -Explanation: You do not need to specify a Testsuite: autopkgtest field if - a debian/tests/control file exists. It is automatically added by - dpkg-source(1) since dpkg 1.17.1. - . - Please remove this line from your debian/control file. -Renamed-From: - unnecessary-testsuite-autopkgtest-header diff -Nru lintian-2.93.0/tags/u/unparsable-menu-item.desc lintian-2.89.0ubuntu1/tags/u/unparsable-menu-item.desc --- lintian-2.93.0/tags/u/unparsable-menu-item.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/unparsable-menu-item.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: unparsable-menu-item +Severity: error +Check: menu-format +Info: An item of the menu file cannot be parsed as a series of tag=value + pairs. This could be because you didn't close a set of double quotes. +Ref: menu 3.2 diff -Nru lintian-2.93.0/tags/u/unparsable-menu-item.tag lintian-2.89.0ubuntu1/tags/u/unparsable-menu-item.tag --- lintian-2.93.0/tags/u/unparsable-menu-item.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/unparsable-menu-item.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: unparsable-menu-item -Severity: error -Check: menu-format -Explanation: An item of the menu file cannot be parsed as a series of tag=value - pairs. This could be because you didn't close a set of double quotes. -See-Also: menu 3.2 diff -Nru lintian-2.93.0/tags/u/unquoted-string-in-menu-item.desc lintian-2.89.0ubuntu1/tags/u/unquoted-string-in-menu-item.desc --- lintian-2.93.0/tags/u/unquoted-string-in-menu-item.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/unquoted-string-in-menu-item.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: unquoted-string-in-menu-item +Severity: warning +Check: menu-format +Info: The menu item includes a tag with an unquoted string like section=Games + instead of section="Games". This is deprecated. Use a quoted string instead. +Ref: menu 3.2 diff -Nru lintian-2.93.0/tags/u/unquoted-string-in-menu-item.tag lintian-2.89.0ubuntu1/tags/u/unquoted-string-in-menu-item.tag --- lintian-2.93.0/tags/u/unquoted-string-in-menu-item.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/unquoted-string-in-menu-item.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: unquoted-string-in-menu-item -Severity: warning -Check: menu-format -Explanation: The menu item includes a tag with an unquoted string like section=Games - instead of section="Games". This is deprecated. Use a quoted string instead. -See-Also: menu 3.2 diff -Nru lintian-2.93.0/tags/u/unreleased-changelog-distribution.desc lintian-2.89.0ubuntu1/tags/u/unreleased-changelog-distribution.desc --- lintian-2.93.0/tags/u/unreleased-changelog-distribution.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/unreleased-changelog-distribution.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: unreleased-changelog-distribution +Severity: info +Check: debian/changelog +Info: The distribution in the latest Debian changelog entry indicates + that this package was not intended to be released yet. +Ref: #873520 diff -Nru lintian-2.93.0/tags/u/unreleased-changelog-distribution.tag lintian-2.89.0ubuntu1/tags/u/unreleased-changelog-distribution.tag --- lintian-2.93.0/tags/u/unreleased-changelog-distribution.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/unreleased-changelog-distribution.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: unreleased-changelog-distribution -Severity: info -Check: debian/changelog -Explanation: The distribution in the latest Debian changelog entry indicates - that this package was not intended to be released yet. -See-Also: Bug#873520 diff -Nru lintian-2.93.0/tags/u/unreleased-changes.desc lintian-2.89.0ubuntu1/tags/u/unreleased-changes.desc --- lintian-2.93.0/tags/u/unreleased-changes.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/unreleased-changes.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: unreleased-changes +Severity: error +Check: fields/distribution +Info: The distribution in the Changes field copied from + debian/changelog indicates that this package was not intended + to be released yet. +Ref: #542747 diff -Nru lintian-2.93.0/tags/u/unreleased-changes.tag lintian-2.89.0ubuntu1/tags/u/unreleased-changes.tag --- lintian-2.93.0/tags/u/unreleased-changes.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/unreleased-changes.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: unreleased-changes -Severity: error -Check: fields/distribution -Explanation: The distribution in the Changes field copied from - debian/changelog indicates that this package was not intended - to be released yet. -See-Also: Bug#542747 diff -Nru lintian-2.93.0/tags/u/unstripped-binary-or-object.desc lintian-2.89.0ubuntu1/tags/u/unstripped-binary-or-object.desc --- lintian-2.93.0/tags/u/unstripped-binary-or-object.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/unstripped-binary-or-object.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: unstripped-binary-or-object +Severity: error +Check: binaries +Ref: policy 10.1, policy 10.2 +Info: The package installs an unstripped binary or object file. + . + Please note, that shared libraries have to be stripped with the + --strip-unneeded option. diff -Nru lintian-2.93.0/tags/u/unstripped-binary-or-object.tag lintian-2.89.0ubuntu1/tags/u/unstripped-binary-or-object.tag --- lintian-2.93.0/tags/u/unstripped-binary-or-object.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/unstripped-binary-or-object.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: unstripped-binary-or-object -Severity: error -Check: binaries -See-Also: policy 10.1, policy 10.2 -Explanation: The package installs an unstripped binary or object file. - . - Please note, that shared libraries have to be stripped with the - --strip-unneeded option. diff -Nru lintian-2.93.0/tags/u/unstripped-static-library.desc lintian-2.89.0ubuntu1/tags/u/unstripped-static-library.desc --- lintian-2.93.0/tags/u/unstripped-static-library.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/unstripped-static-library.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,12 @@ +Tag: unstripped-static-library +Severity: info +Check: binaries +Info: The package installs an unstripped static library. + . + Please note, that static libraries have to be stripped with the + --strip-debug option. You will probably also want to + use --remove-section=.comment --remove-section=.note + to avoid the static-library-has-unneeded-section tag. + . + dh_strip (after debhelper/9.20150811) will do this + automatically for you. diff -Nru lintian-2.93.0/tags/u/unstripped-static-library.tag lintian-2.89.0ubuntu1/tags/u/unstripped-static-library.tag --- lintian-2.93.0/tags/u/unstripped-static-library.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/unstripped-static-library.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,12 +0,0 @@ -Tag: unstripped-static-library -Severity: info -Check: binaries -Explanation: The package installs an unstripped static library. - . - Please note, that static libraries have to be stripped with the - --strip-debug option. You will probably also want to - use --remove-section=.comment --remove-section=.note - to avoid the static-library-has-unneeded-section tag. - . - dh_strip (after debhelper/9.20150811) will do this - automatically for you. diff -Nru lintian-2.93.0/tags/u/unsupported-source-format.desc lintian-2.89.0ubuntu1/tags/u/unsupported-source-format.desc --- lintian-2.93.0/tags/u/unsupported-source-format.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/unsupported-source-format.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: unsupported-source-format +Severity: error +Check: fields/format +Info: This package uses a different source package format than "1.0", + "3.0 (quilt)" or "3.0 (native)". Other package formats are supported by + dpkg-source, but they are not allowed in the Debian archive. diff -Nru lintian-2.93.0/tags/u/unsupported-source-format.tag lintian-2.89.0ubuntu1/tags/u/unsupported-source-format.tag --- lintian-2.93.0/tags/u/unsupported-source-format.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/unsupported-source-format.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: unsupported-source-format -Severity: error -Check: fields/format -Explanation: This package uses a different source package format than "1.0", - "3.0 (quilt)" or "3.0 (native)". Other package formats are supported by - dpkg-source, but they are not allowed in the Debian archive. diff -Nru lintian-2.93.0/tags/u/untranslatable-debconf-templates.desc lintian-2.89.0ubuntu1/tags/u/untranslatable-debconf-templates.desc --- lintian-2.93.0/tags/u/untranslatable-debconf-templates.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/untranslatable-debconf-templates.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,18 @@ +Tag: untranslatable-debconf-templates +Severity: error +Certainty: possible +Check: debian/po-debconf +Info: This package seems to be using debconf templates, but some + descriptions are not translatable. You should prepend an underscore + before every translatable field, as described in po-debconf(7). This + may mean that translators weren't properly warned about new strings. + . + Translators may be notified of changes using podebconf-report-po, for + example: + . + podebconf-report-po --call --withtranslators --deadline="+10 days" \ + --languageteam + . + If the field is not intended for users to see, ensure the first line + of the description contains "for internal use". +Ref: policy 3.9.1 diff -Nru lintian-2.93.0/tags/u/untranslatable-debconf-templates.tag lintian-2.89.0ubuntu1/tags/u/untranslatable-debconf-templates.tag --- lintian-2.93.0/tags/u/untranslatable-debconf-templates.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/untranslatable-debconf-templates.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,17 +0,0 @@ -Tag: untranslatable-debconf-templates -Severity: error -Check: debian/po-debconf -Explanation: This package seems to be using debconf templates, but some - descriptions are not translatable. You should prepend an underscore - before every translatable field, as described in po-debconf(7). This - may mean that translators weren't properly warned about new strings. - . - Translators may be notified of changes using podebconf-report-po, for - example: - . - podebconf-report-po --call --withtranslators --deadline="+10 days" \ - --languageteam - . - If the field is not intended for users to see, ensure the first line - of the description contains "for internal use". -See-Also: policy 3.9.1 diff -Nru lintian-2.93.0/tags/u/unused-build-dependency-on-cdbs.desc lintian-2.89.0ubuntu1/tags/u/unused-build-dependency-on-cdbs.desc --- lintian-2.93.0/tags/u/unused-build-dependency-on-cdbs.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/unused-build-dependency-on-cdbs.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: unused-build-dependency-on-cdbs +Severity: warning +Certainty: possible +Check: debhelper +Info: The package build-depends on cdbs, but does not include any cdbs + files in debian/rules. diff -Nru lintian-2.93.0/tags/u/unused-build-dependency-on-cdbs.tag lintian-2.89.0ubuntu1/tags/u/unused-build-dependency-on-cdbs.tag --- lintian-2.93.0/tags/u/unused-build-dependency-on-cdbs.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/unused-build-dependency-on-cdbs.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,5 +0,0 @@ -Tag: unused-build-dependency-on-cdbs -Severity: warning -Check: debhelper -Explanation: The package build-depends on cdbs, but does not include any cdbs - files in debian/rules. diff -Nru lintian-2.93.0/tags/u/unused-debconf-template.desc lintian-2.89.0ubuntu1/tags/u/unused-debconf-template.desc --- lintian-2.93.0/tags/u/unused-debconf-template.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/unused-debconf-template.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,24 @@ +Tag: unused-debconf-template +Severity: info +Certainty: possible +Check: debian/debconf +Info: Templates which are not used by the package should be removed from + the templates file. + . + This will reduce the size of the templates database and prevent + translators from unnecessarily translating the template's text. + . + In some cases, the template is used but Lintian is unable to determine + this. Common causes are: + . + - the maintainer scripts embed a variable in the template name in + order to allow a template to be selected from a range of similar + templates (e.g. db_input low start_$service_at_boot) + . + - the template is not used by the maintainer scripts but is used by + a program in the package + . + - the maintainer scripts are written in perl. Lintian currently only + understands the shell script debconf functions. + . + If any of the above apply, please install an override. diff -Nru lintian-2.93.0/tags/u/unused-debconf-template.tag lintian-2.89.0ubuntu1/tags/u/unused-debconf-template.tag --- lintian-2.93.0/tags/u/unused-debconf-template.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/unused-debconf-template.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,23 +0,0 @@ -Tag: unused-debconf-template -Severity: info -Check: debian/debconf -Explanation: Templates which are not used by the package should be removed from - the templates file. - . - This will reduce the size of the templates database and prevent - translators from unnecessarily translating the template's text. - . - In some cases, the template is used but Lintian is unable to determine - this. Common causes are: - . - - the maintainer scripts embed a variable in the template name in - order to allow a template to be selected from a range of similar - templates (e.g. db_input low start_$service_at_boot) - . - - the template is not used by the maintainer scripts but is used by - a program in the package - . - - the maintainer scripts are written in perl. Lintian currently only - understands the shell script debconf functions. - . - If any of the above apply, please install an override. diff -Nru lintian-2.93.0/tags/u/unused-entry-in-debian-source-include-binaries.desc lintian-2.89.0ubuntu1/tags/u/unused-entry-in-debian-source-include-binaries.desc --- lintian-2.93.0/tags/u/unused-entry-in-debian-source-include-binaries.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/unused-entry-in-debian-source-include-binaries.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: unused-entry-in-debian-source-include-binaries +Severity: info +Check: debian/source/include-binaries +Info: An entry in debian/source/include-binaries does not exist + in the patched source tree. Please remove the entry. + . + The format for the file is described in the manual page for + dpkg-source. +Ref: dpkg-source(1), #528001, https://stackoverflow.com/questions/21057015/debian-include-binaries-format diff -Nru lintian-2.93.0/tags/u/unused-entry-in-debian-source-include-binaries.tag lintian-2.89.0ubuntu1/tags/u/unused-entry-in-debian-source-include-binaries.tag --- lintian-2.93.0/tags/u/unused-entry-in-debian-source-include-binaries.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/unused-entry-in-debian-source-include-binaries.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: unused-entry-in-debian-source-include-binaries -Severity: info -Check: debian/source/include-binaries -Explanation: An entry in debian/source/include-binaries does not exist - in the patched source tree. Please remove the entry. - . - The format for the file is described in the manual page for - dpkg-source. -See-Also: dpkg-source(1), Bug#528001, https://stackoverflow.com/questions/21057015/debian-include-binaries-format diff -Nru lintian-2.93.0/tags/u/unused-file-paragraph-in-dep5-copyright.desc lintian-2.89.0ubuntu1/tags/u/unused-file-paragraph-in-dep5-copyright.desc --- lintian-2.93.0/tags/u/unused-file-paragraph-in-dep5-copyright.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/unused-file-paragraph-in-dep5-copyright.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: unused-file-paragraph-in-dep5-copyright +Severity: info +Certainty: possible +Check: debian/copyright/dep5 +Ref: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ +Info: The indicated Files paragraph in debian/copyright is not + needed. It does not match any files. You can probably remove it. + . + False positives can occur when the paragraphs are listed in the wrong + order. diff -Nru lintian-2.93.0/tags/u/unused-file-paragraph-in-dep5-copyright.tag lintian-2.89.0ubuntu1/tags/u/unused-file-paragraph-in-dep5-copyright.tag --- lintian-2.93.0/tags/u/unused-file-paragraph-in-dep5-copyright.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/unused-file-paragraph-in-dep5-copyright.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: unused-file-paragraph-in-dep5-copyright -Severity: info -Check: debian/copyright/dep5 -See-Also: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ -Explanation: The indicated Files paragraph in debian/copyright is not - needed. It does not match any files. You can probably remove it. - . - False positives can occur when the paragraphs are listed in the wrong - order. diff -Nru lintian-2.93.0/tags/u/unused-license-paragraph-in-dep5-copyright.desc lintian-2.89.0ubuntu1/tags/u/unused-license-paragraph-in-dep5-copyright.desc --- lintian-2.93.0/tags/u/unused-license-paragraph-in-dep5-copyright.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/unused-license-paragraph-in-dep5-copyright.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: unused-license-paragraph-in-dep5-copyright +Severity: info +Certainty: possible +Check: debian/copyright/dep5 +Ref: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ +Info: The license paragraph in the machine-readable copyright file is not + referenced by any files paragraph. It could be a typo in the license name or + the license paragraph is simply not needed and can be removed. diff -Nru lintian-2.93.0/tags/u/unused-license-paragraph-in-dep5-copyright.tag lintian-2.89.0ubuntu1/tags/u/unused-license-paragraph-in-dep5-copyright.tag --- lintian-2.93.0/tags/u/unused-license-paragraph-in-dep5-copyright.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/unused-license-paragraph-in-dep5-copyright.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: unused-license-paragraph-in-dep5-copyright -Severity: info -Check: debian/copyright/dep5 -See-Also: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ -Explanation: The license paragraph in the machine-readable copyright file is not - referenced by any files paragraph. It could be a typo in the license name or - the license paragraph is simply not needed and can be removed. diff -Nru lintian-2.93.0/tags/u/unused-override.desc lintian-2.89.0ubuntu1/tags/u/unused-override.desc --- lintian-2.93.0/tags/u/unused-override.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/unused-override.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,19 @@ +Tag: unused-override +Severity: info +Check: lintian +Info: Your package specifies the named override but there were no + tags that could have been silenced by it. + . + Maybe you fixed an underlying condition but forgot to remove the + override. It is also possible that the Lintian maintainers fixed a + false positive. + . + If the override is now unused, please remove it. + . + This tag is similar to mismatched-override except there a + tag could have been silenced if the context had matched. + . + Sometimes, overrides end up not being used because a tag appears + only on some architectures. In that case, overrides can be equipped + with an architecture qualifier. +Ref: lintian 2.4.3 diff -Nru lintian-2.93.0/tags/u/unused-override.tag lintian-2.89.0ubuntu1/tags/u/unused-override.tag --- lintian-2.93.0/tags/u/unused-override.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/unused-override.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,19 +0,0 @@ -Tag: unused-override -Severity: info -Check: lintian -Explanation: Your package specifies the named override but there were no - tags that could have been silenced by it. - . - Maybe you fixed an underlying condition but forgot to remove the - override. It is also possible that the Lintian maintainers fixed a - false positive. - . - If the override is now unused, please remove it. - . - This tag is similar to mismatched-override except there a - tag could have been silenced if the context had matched. - . - Sometimes, overrides end up not being used because a tag appears - only on some architectures. In that case, overrides can be equipped - with an architecture qualifier. -See-Also: lintian 2.4.3 diff -Nru lintian-2.93.0/tags/u/unusual-control-interpreter.desc lintian-2.89.0ubuntu1/tags/u/unusual-control-interpreter.desc --- lintian-2.93.0/tags/u/unusual-control-interpreter.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/unusual-control-interpreter.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: unusual-control-interpreter +Severity: warning +Check: scripts +Info: This package contains a control script for an interpreter that is + not normally used for control scripts. This is permissible but not + recommended. It makes it harder for other developers to understand your + package. diff -Nru lintian-2.93.0/tags/u/unusual-control-interpreter.tag lintian-2.89.0ubuntu1/tags/u/unusual-control-interpreter.tag --- lintian-2.93.0/tags/u/unusual-control-interpreter.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/unusual-control-interpreter.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: unusual-control-interpreter -Severity: warning -Check: scripts -Explanation: This package contains a control script for an interpreter that is - not normally used for control scripts. This is permissible but not - recommended. It makes it harder for other developers to understand your - package. diff -Nru lintian-2.93.0/tags/u/unusual-documentation-package-name.desc lintian-2.89.0ubuntu1/tags/u/unusual-documentation-package-name.desc --- lintian-2.93.0/tags/u/unusual-documentation-package-name.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/unusual-documentation-package-name.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: unusual-documentation-package-name +Severity: info +Check: fields/package +Info: The specified package appears to be a documentation package + that ends with the string "-docs". It is recommended that such + packages use the more usual "-doc" suffix instead. + . + Please remove the superfluous trailing "s" from the package name. +Ref: policy 12.3 diff -Nru lintian-2.93.0/tags/u/unusual-documentation-package-name.tag lintian-2.89.0ubuntu1/tags/u/unusual-documentation-package-name.tag --- lintian-2.93.0/tags/u/unusual-documentation-package-name.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/unusual-documentation-package-name.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: unusual-documentation-package-name -Severity: info -Check: fields/package -Explanation: The specified package appears to be a documentation package - that ends with the string "-docs". It is recommended that such - packages use the more usual "-doc" suffix instead. - . - Please remove the superfluous trailing "s" from the package name. -See-Also: policy 12.3 diff -Nru lintian-2.93.0/tags/u/unusual-interpreter.desc lintian-2.89.0ubuntu1/tags/u/unusual-interpreter.desc --- lintian-2.93.0/tags/u/unusual-interpreter.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/unusual-interpreter.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: unusual-interpreter +Severity: warning +Certainty: possible +Check: scripts +Info: This package contains a script for an interpreter that is not shipped + in the package and is not known to Lintian. It is possible that there is + a typo or the interpreter is not executable. diff -Nru lintian-2.93.0/tags/u/unusual-interpreter.tag lintian-2.89.0ubuntu1/tags/u/unusual-interpreter.tag --- lintian-2.93.0/tags/u/unusual-interpreter.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/unusual-interpreter.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: unusual-interpreter -Severity: warning -Check: scripts -Explanation: This package contains a script for an interpreter that is not shipped - in the package and is not known to Lintian. It is possible that there is - a typo or the interpreter is not executable. diff -Nru lintian-2.93.0/tags/u/unversioned-copyright-format-uri.desc lintian-2.89.0ubuntu1/tags/u/unversioned-copyright-format-uri.desc --- lintian-2.93.0/tags/u/unversioned-copyright-format-uri.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/unversioned-copyright-format-uri.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: unversioned-copyright-format-uri +Severity: pedantic +Certainty: possible +Check: debian/copyright/dep5 +Ref: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ +Info: Format URI of the machine-readable copyright file is not versioned. + . + Please use + https://www.debian.org/doc/packaging-manuals/copyright-format/version/ + as the format URI instead. diff -Nru lintian-2.93.0/tags/u/unversioned-copyright-format-uri.tag lintian-2.89.0ubuntu1/tags/u/unversioned-copyright-format-uri.tag --- lintian-2.93.0/tags/u/unversioned-copyright-format-uri.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/unversioned-copyright-format-uri.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: unversioned-copyright-format-uri -Severity: pedantic -Check: debian/copyright/dep5 -See-Also: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ -Explanation: Format URI of the machine-readable copyright file is not versioned. - . - Please use - https://www.debian.org/doc/packaging-manuals/copyright-format/*version*/ - as the format URI instead. diff -Nru lintian-2.93.0/tags/u/unwanted-path-too-specific.desc lintian-2.89.0ubuntu1/tags/u/unwanted-path-too-specific.desc --- lintian-2.93.0/tags/u/unwanted-path-too-specific.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/unwanted-path-too-specific.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,13 @@ +Tag: unwanted-path-too-specific +Severity: warning +Check: debian/not-installed +Info: The file debian/not-installed lists a path that may + cause unexpected build failures. The path is too specific. + . + A common problem are entries starting with + usr/lib/x86_64-linux-gnu. The sources will build fine + on amd64 but not on other architectures, because the + paths to do exist. + . + Please consider using an asterisk, which will work fine. +Ref: Bug#961104, Bug#961960, Bug#961973 diff -Nru lintian-2.93.0/tags/u/unwanted-path-too-specific.tag lintian-2.89.0ubuntu1/tags/u/unwanted-path-too-specific.tag --- lintian-2.93.0/tags/u/unwanted-path-too-specific.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/unwanted-path-too-specific.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,13 +0,0 @@ -Tag: unwanted-path-too-specific -Severity: warning -Check: debian/not-installed -Explanation: The file debian/not-installed lists a path that may - cause unexpected build failures. The path is too specific. - . - A common problem are entries starting with - usr/lib/x86_64-linux-gnu. The sources will build fine - on amd64 but not on other architectures, because the - paths to do exist. - . - Please consider using an asterisk, which will work fine. -See-Also: Bug#961104, Bug#961960, Bug#961973 diff -Nru lintian-2.93.0/tags/u/uploader-name-missing.desc lintian-2.89.0ubuntu1/tags/u/uploader-name-missing.desc --- lintian-2.93.0/tags/u/uploader-name-missing.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/uploader-name-missing.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: uploader-name-missing +Severity: error +Check: fields/uploaders +Info: The uploader field seems to contain just an email address. It must + contain the package uploader's name and email address. +Ref: policy 5.6.3 diff -Nru lintian-2.93.0/tags/u/uploader-name-missing.tag lintian-2.89.0ubuntu1/tags/u/uploader-name-missing.tag --- lintian-2.93.0/tags/u/uploader-name-missing.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/uploader-name-missing.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: uploader-name-missing -Severity: error -Check: fields/uploaders -Explanation: The uploader field seems to contain just an email address. It must - contain the package uploader's name and email address. -See-Also: policy 5.6.3 diff -Nru lintian-2.93.0/tags/u/uploaders-in-orphan.desc lintian-2.89.0ubuntu1/tags/u/uploaders-in-orphan.desc --- lintian-2.93.0/tags/u/uploaders-in-orphan.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/uploaders-in-orphan.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: uploaders-in-orphan +Severity: error +Check: nmu +Renamed-From: orphaned-package-should-not-have-uploaders +Info: Packages with their maintainer set to packages@qa.debian.org, i.e. + orphaned packages, should not have uploaders. Adopt the package properly if + you want to resume its maintenance. diff -Nru lintian-2.93.0/tags/u/uploaders-in-orphan.tag lintian-2.89.0ubuntu1/tags/u/uploaders-in-orphan.tag --- lintian-2.93.0/tags/u/uploaders-in-orphan.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/uploaders-in-orphan.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: uploaders-in-orphan -Severity: error -Check: nmu -Renamed-From: orphaned-package-should-not-have-uploaders -Explanation: Packages with their maintainer set to packages@qa.debian.org, i.e. - orphaned packages, should not have uploaders. Adopt the package properly if - you want to resume its maintenance. diff -Nru lintian-2.93.0/tags/u/upload-has-backports-version-number.desc lintian-2.89.0ubuntu1/tags/u/upload-has-backports-version-number.desc --- lintian-2.93.0/tags/u/upload-has-backports-version-number.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/upload-has-backports-version-number.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,5 @@ +Tag: upload-has-backports-version-number +Severity: error +Check: fields/distribution +Info: The version number looks like a backport, but the upload's target + distribution is not a backport suite. diff -Nru lintian-2.93.0/tags/u/upload-has-backports-version-number.tag lintian-2.89.0ubuntu1/tags/u/upload-has-backports-version-number.tag --- lintian-2.93.0/tags/u/upload-has-backports-version-number.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/upload-has-backports-version-number.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,5 +0,0 @@ -Tag: upload-has-backports-version-number -Severity: error -Check: fields/distribution -Explanation: The version number looks like a backport, but the upload's target - distribution is not a backport suite. diff -Nru lintian-2.93.0/tags/u/upstart-job-in-etc-init.d-not-registered-via-update-rc.d.desc lintian-2.89.0ubuntu1/tags/u/upstart-job-in-etc-init.d-not-registered-via-update-rc.d.desc --- lintian-2.93.0/tags/u/upstart-job-in-etc-init.d-not-registered-via-update-rc.d.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/upstart-job-in-etc-init.d-not-registered-via-update-rc.d.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,13 @@ +Tag: upstart-job-in-etc-init.d-not-registered-via-update-rc.d +Severity: warning +Certainty: possible +Check: init.d +Info: The package installs an upstart-job in /etc/init.d + which is not registered in the postinst script. On + non-upstart systems this is usually a bug, unless you omit the links + intentionally for some reason or create the links some other way. + . + This tag should only be emitted for vendors that do not use upstart + by default (such as Debian). If this tag is emitted by a vendor + using upstart (e.g. Ubuntu), it may be a misconfiguration of their + Lintian vendor profile. diff -Nru lintian-2.93.0/tags/u/upstart-job-in-etc-init.d-not-registered-via-update-rc.d.tag lintian-2.89.0ubuntu1/tags/u/upstart-job-in-etc-init.d-not-registered-via-update-rc.d.tag --- lintian-2.93.0/tags/u/upstart-job-in-etc-init.d-not-registered-via-update-rc.d.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/upstart-job-in-etc-init.d-not-registered-via-update-rc.d.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,12 +0,0 @@ -Tag: upstart-job-in-etc-init.d-not-registered-via-update-rc.d -Severity: warning -Check: init.d -Explanation: The package installs an upstart-job in /etc/init.d - which is not registered in the postinst script. On - non-upstart systems this is usually a bug, unless you omit the links - intentionally for some reason or create the links some other way. - . - This tag should only be emitted for vendors that do not use upstart - by default (such as Debian). If this tag is emitted by a vendor - using upstart (e.g. Ubuntu), it may be a misconfiguration of their - Lintian vendor profile. diff -Nru lintian-2.93.0/tags/u/upstream-file-without-utf8-name.desc lintian-2.89.0ubuntu1/tags/u/upstream-file-without-utf8-name.desc --- lintian-2.93.0/tags/u/upstream-file-without-utf8-name.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/upstream-file-without-utf8-name.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,14 @@ +Tag: upstream-file-without-utf8-name +Severity: info +Check: files/names +Ref: policy 10.10 +Info: The file name in the upstream source tree is not valid UTF-8. + There is probably not much a maintainer can do other than ask upstream + to package the sources differently. + . + Repacking may by an option, but it often has other drawbacks, such as + the loss of a cryptographic chain of custody. + . + Unlike other file names in Lintian, which are printed in UTF-8, the + attached reference shows the bytes used by the file system. Unprintable + characters may have been replaced. diff -Nru lintian-2.93.0/tags/u/upstream-file-without-utf8-name.tag lintian-2.89.0ubuntu1/tags/u/upstream-file-without-utf8-name.tag --- lintian-2.93.0/tags/u/upstream-file-without-utf8-name.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/upstream-file-without-utf8-name.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,14 +0,0 @@ -Tag: upstream-file-without-utf8-name -Severity: info -Check: files/names -See-Also: policy 10.10 -Explanation: The file name in the upstream source tree is not valid UTF-8. - There is probably not much a maintainer can do other than ask upstream - to package the sources differently. - . - Repacking may by an option, but it often has other drawbacks, such as - the loss of a cryptographic chain of custody. - . - Unlike other file names in Lintian, which are printed in UTF-8, the - attached reference shows the bytes used by the file system. Unprintable - characters may have been replaced. diff -Nru lintian-2.93.0/tags/u/upstream-metadata-exists.desc lintian-2.89.0ubuntu1/tags/u/upstream-metadata-exists.desc --- lintian-2.93.0/tags/u/upstream-metadata-exists.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/upstream-metadata-exists.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,5 @@ +Tag: upstream-metadata-exists +Severity: classification +Check: debian/upstream/metadata +Ref: https://dep-team.pages.debian.net/deps/dep12/ +Info: The sources comtain a DEP 12 metadata file. diff -Nru lintian-2.93.0/tags/u/upstream-metadata-exists.tag lintian-2.89.0ubuntu1/tags/u/upstream-metadata-exists.tag --- lintian-2.93.0/tags/u/upstream-metadata-exists.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/upstream-metadata-exists.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,5 +0,0 @@ -Tag: upstream-metadata-exists -Severity: classification -Check: debian/upstream/metadata -See-Also: https://dep-team.pages.debian.net/deps/dep12/ -Explanation: The sources comtain a DEP 12 metadata file. diff -Nru lintian-2.93.0/tags/u/upstream-metadata-field-present.desc lintian-2.89.0ubuntu1/tags/u/upstream-metadata-field-present.desc --- lintian-2.93.0/tags/u/upstream-metadata-field-present.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/upstream-metadata-field-present.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,5 @@ +Tag: upstream-metadata-field-present +Severity: classification +Check: debian/upstream/metadata +Ref: https://dep-team.pages.debian.net/deps/dep12/ +Info: The DEP 12 metadata contains the field indicated. diff -Nru lintian-2.93.0/tags/u/upstream-metadata-field-present.tag lintian-2.89.0ubuntu1/tags/u/upstream-metadata-field-present.tag --- lintian-2.93.0/tags/u/upstream-metadata-field-present.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/upstream-metadata-field-present.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,5 +0,0 @@ -Tag: upstream-metadata-field-present -Severity: classification -Check: debian/upstream/metadata -See-Also: https://dep-team.pages.debian.net/deps/dep12/ -Explanation: The DEP 12 metadata contains the field indicated. diff -Nru lintian-2.93.0/tags/u/upstream-metadata-file-is-missing.desc lintian-2.89.0ubuntu1/tags/u/upstream-metadata-file-is-missing.desc --- lintian-2.93.0/tags/u/upstream-metadata-file-is-missing.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/upstream-metadata-file-is-missing.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,16 @@ +Tag: upstream-metadata-file-is-missing +Severity: pedantic +Check: debian/upstream/metadata +Experimental: yes +Ref: https://dep-team.pages.debian.net/deps/dep12/, https://wiki.debian.org/UpstreamMetadata +Info: This source package is not Debian-native but it does not have a + debian/upstream/metadata file. + . + The Upstream MEtadata GAthered with YAml (UMEGAYA) project is an effort + to collect meta-information about upstream projects from any source + package. This file is in YAML format and it is used in to feed the data + in the UltimateDebianDatabase. For example, it can contains the way the + authors want their software be cited in publications and some + bibliographic references about the software. + . + Please add a debian/upstream/metadata file. diff -Nru lintian-2.93.0/tags/u/upstream-metadata-file-is-missing.tag lintian-2.89.0ubuntu1/tags/u/upstream-metadata-file-is-missing.tag --- lintian-2.93.0/tags/u/upstream-metadata-file-is-missing.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/upstream-metadata-file-is-missing.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,16 +0,0 @@ -Tag: upstream-metadata-file-is-missing -Severity: pedantic -Check: debian/upstream/metadata -Experimental: yes -See-Also: https://dep-team.pages.debian.net/deps/dep12/, https://wiki.debian.org/UpstreamMetadata -Explanation: This source package is not Debian-native but it does not have a - debian/upstream/metadata file. - . - The Upstream MEtadata GAthered with YAml (UMEGAYA) project is an effort - to collect meta-information about upstream projects from any source - package. This file is in YAML format and it is used in to feed the data - in the UltimateDebianDatabase. For example, it can contains the way the - authors want their software be cited in publications and some - bibliographic references about the software. - . - Please add a debian/upstream/metadata file. diff -Nru lintian-2.93.0/tags/u/upstream-metadata-in-native-source.desc lintian-2.89.0ubuntu1/tags/u/upstream-metadata-in-native-source.desc --- lintian-2.93.0/tags/u/upstream-metadata-in-native-source.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/upstream-metadata-in-native-source.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,15 @@ +Tag: upstream-metadata-in-native-source +Severity: warning +Check: debian/upstream/metadata +Ref: https://dep-team.pages.debian.net/deps/dep12/, https://wiki.debian.org/UpstreamMetadata +Info: This source package is Debian-native and has a + debian/upstream/metadata file. + . + The Upstream MEtadata GAthered with YAml (UMEGAYA) project is an effort + to collect meta-information about upstream projects from any source + package. This file is in YAML format and it is used in to feed the data + in the UltimateDebianDatabase. For example, it can contains the way the + authors want their software be cited in publications and some + bibliographic references about the software. + . + Please remove the debian/upstream/metadata file. diff -Nru lintian-2.93.0/tags/u/upstream-metadata-in-native-source.tag lintian-2.89.0ubuntu1/tags/u/upstream-metadata-in-native-source.tag --- lintian-2.93.0/tags/u/upstream-metadata-in-native-source.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/upstream-metadata-in-native-source.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,15 +0,0 @@ -Tag: upstream-metadata-in-native-source -Severity: warning -Check: debian/upstream/metadata -See-Also: https://dep-team.pages.debian.net/deps/dep12/, https://wiki.debian.org/UpstreamMetadata -Explanation: This source package is Debian-native and has a - debian/upstream/metadata file. - . - The Upstream MEtadata GAthered with YAml (UMEGAYA) project is an effort - to collect meta-information about upstream projects from any source - package. This file is in YAML format and it is used in to feed the data - in the UltimateDebianDatabase. For example, it can contains the way the - authors want their software be cited in publications and some - bibliographic references about the software. - . - Please remove the debian/upstream/metadata file. diff -Nru lintian-2.93.0/tags/u/upstream-metadata-is-not-a-file.desc lintian-2.89.0ubuntu1/tags/u/upstream-metadata-is-not-a-file.desc --- lintian-2.93.0/tags/u/upstream-metadata-is-not-a-file.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/upstream-metadata-is-not-a-file.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: upstream-metadata-is-not-a-file +Severity: warning +Check: debian/upstream/metadata +Ref: https://dep-team.pages.debian.net/deps/dep12/ +Info: The DEP 12 metadata file in the source is not readable. This + could be caused by a dangling symlink, or that the name is used + by some non-file directory entry. diff -Nru lintian-2.93.0/tags/u/upstream-metadata-is-not-a-file.tag lintian-2.89.0ubuntu1/tags/u/upstream-metadata-is-not-a-file.tag --- lintian-2.93.0/tags/u/upstream-metadata-is-not-a-file.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/upstream-metadata-is-not-a-file.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: upstream-metadata-is-not-a-file -Severity: warning -Check: debian/upstream/metadata -See-Also: https://dep-team.pages.debian.net/deps/dep12/ -Explanation: The DEP 12 metadata file in the source is not readable. This - could be caused by a dangling symlink, or that the name is used - by some non-file directory entry. diff -Nru lintian-2.93.0/tags/u/upstream-metadata-missing-bug-tracking.desc lintian-2.89.0ubuntu1/tags/u/upstream-metadata-missing-bug-tracking.desc --- lintian-2.93.0/tags/u/upstream-metadata-missing-bug-tracking.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/upstream-metadata-missing-bug-tracking.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: upstream-metadata-missing-bug-tracking +Severity: info +Check: debian/upstream/metadata +Ref: https://dep-team.pages.debian.net/deps/dep12/ +Info: The DEP 12 metadata file does not specify any upstream bug + tracking information (ie. the Bug-Database or + Bug-Submit fields are missing). + . + The upstream metadata can be found in the source package in the + file debian/upstream/metadata. diff -Nru lintian-2.93.0/tags/u/upstream-metadata-missing-bug-tracking.tag lintian-2.89.0ubuntu1/tags/u/upstream-metadata-missing-bug-tracking.tag --- lintian-2.93.0/tags/u/upstream-metadata-missing-bug-tracking.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/upstream-metadata-missing-bug-tracking.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,10 +0,0 @@ -Tag: upstream-metadata-missing-bug-tracking -Severity: info -Check: debian/upstream/metadata -See-Also: https://dep-team.pages.debian.net/deps/dep12/ -Explanation: The DEP 12 metadata file does not specify any upstream bug - tracking information (ie. the Bug-Database or - Bug-Submit fields are missing). - . - The upstream metadata can be found in the source package in the - file debian/upstream/metadata. diff -Nru lintian-2.93.0/tags/u/upstream-metadata-missing-repository.desc lintian-2.89.0ubuntu1/tags/u/upstream-metadata-missing-repository.desc --- lintian-2.93.0/tags/u/upstream-metadata-missing-repository.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/upstream-metadata-missing-repository.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: upstream-metadata-missing-repository +Severity: info +Check: debian/upstream/metadata +Ref: https://dep-team.pages.debian.net/deps/dep12/ +Info: The DEP 12 metadata file does not specify the location of + upstream's version control repository (ie. the Repository + and Repository-Browse fields are missing). + . + The upstream metadata can be found in the source package in the + file debian/upstream/metadata. diff -Nru lintian-2.93.0/tags/u/upstream-metadata-missing-repository.tag lintian-2.89.0ubuntu1/tags/u/upstream-metadata-missing-repository.tag --- lintian-2.93.0/tags/u/upstream-metadata-missing-repository.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/upstream-metadata-missing-repository.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,10 +0,0 @@ -Tag: upstream-metadata-missing-repository -Severity: info -Check: debian/upstream/metadata -See-Also: https://dep-team.pages.debian.net/deps/dep12/ -Explanation: The DEP 12 metadata file does not specify the location of - upstream's version control repository (ie. the Repository - and Repository-Browse fields are missing). - . - The upstream metadata can be found in the source package in the - file debian/upstream/metadata. diff -Nru lintian-2.93.0/tags/u/upstream-metadata-not-yaml-mapping.desc lintian-2.89.0ubuntu1/tags/u/upstream-metadata-not-yaml-mapping.desc --- lintian-2.93.0/tags/u/upstream-metadata-not-yaml-mapping.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/upstream-metadata-not-yaml-mapping.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,12 @@ +Tag: upstream-metadata-not-yaml-mapping +Severity: warning +Check: debian/upstream/metadata +Ref: https://dep-team.pages.debian.net/deps/dep12/ +Info: The DEP 12 metadata file is not well formed. The document + level must be a YAML mapping: + . + Some-Field: some-value + Another-Field: another-value + . + Sometimes, the fields are mistakenly prefaced with a hyphen, which + makes them a YAML sequence. In that case, please remove the hyphens. diff -Nru lintian-2.93.0/tags/u/upstream-metadata-not-yaml-mapping.tag lintian-2.89.0ubuntu1/tags/u/upstream-metadata-not-yaml-mapping.tag --- lintian-2.93.0/tags/u/upstream-metadata-not-yaml-mapping.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/upstream-metadata-not-yaml-mapping.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,12 +0,0 @@ -Tag: upstream-metadata-not-yaml-mapping -Severity: warning -Check: debian/upstream/metadata -See-Also: https://dep-team.pages.debian.net/deps/dep12/ -Explanation: The DEP 12 metadata file is not well formed. The document - level must be a YAML mapping: - . - Some-Field: some-value - Another-Field: another-value - . - Sometimes, the fields are mistakenly prefaced with a hyphen, which - makes them a YAML sequence. In that case, please remove the hyphens. diff -Nru lintian-2.93.0/tags/u/upstream-metadata-yaml-invalid.desc lintian-2.89.0ubuntu1/tags/u/upstream-metadata-yaml-invalid.desc --- lintian-2.93.0/tags/u/upstream-metadata-yaml-invalid.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/upstream-metadata-yaml-invalid.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: upstream-metadata-yaml-invalid +Severity: warning +Check: debian/upstream/metadata +Ref: https://dep-team.pages.debian.net/deps/dep12/ +Info: The DEP 12 metadata file is not well formed. The formatting + need to be adjusted to match the YAML specification. diff -Nru lintian-2.93.0/tags/u/upstream-metadata-yaml-invalid.tag lintian-2.89.0ubuntu1/tags/u/upstream-metadata-yaml-invalid.tag --- lintian-2.93.0/tags/u/upstream-metadata-yaml-invalid.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/upstream-metadata-yaml-invalid.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: upstream-metadata-yaml-invalid -Severity: warning -Check: debian/upstream/metadata -See-Also: https://dep-team.pages.debian.net/deps/dep12/ -Explanation: The DEP 12 metadata file is not well formed. The formatting - need to be adjusted to match the YAML specification. diff -Nru lintian-2.93.0/tags/u/useless-autogenerated-doxygen-file.desc lintian-2.89.0ubuntu1/tags/u/useless-autogenerated-doxygen-file.desc --- lintian-2.93.0/tags/u/useless-autogenerated-doxygen-file.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/useless-autogenerated-doxygen-file.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,13 @@ +Tag: useless-autogenerated-doxygen-file +Severity: info +Certainty: possible +Check: documentation +Info: The package appears to ship files + from doxygen generated documentation used only + for internal purpose of doxygen. + . + These files are only needed to speed up the + regeneration of the output when this is done + in an incremental fashion (i.e. without first deleting + all output files), and are not needed for + reading the documentation. diff -Nru lintian-2.93.0/tags/u/useless-autogenerated-doxygen-file.tag lintian-2.89.0ubuntu1/tags/u/useless-autogenerated-doxygen-file.tag --- lintian-2.93.0/tags/u/useless-autogenerated-doxygen-file.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/useless-autogenerated-doxygen-file.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,12 +0,0 @@ -Tag: useless-autogenerated-doxygen-file -Severity: info -Check: documentation -Explanation: The package appears to ship files - from doxygen generated documentation used only - for internal purpose of doxygen. - . - These files are only needed to speed up the - regeneration of the output when this is done - in an incremental fashion (i.e. without first deleting - all output files), and are not needed for - reading the documentation. diff -Nru lintian-2.93.0/tags/u/useless-autoreconf-build-depends.desc lintian-2.89.0ubuntu1/tags/u/useless-autoreconf-build-depends.desc --- lintian-2.93.0/tags/u/useless-autoreconf-build-depends.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/useless-autoreconf-build-depends.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: useless-autoreconf-build-depends +Severity: warning +Certainty: possible +Check: debhelper +Info: Since compatibility level 10, debhelper enables the autoreconf + sequence by default. + . + It is therefore not necessary to specify build-dependencies on + dh-autoreconf or autotools-dev and they can be removed. diff -Nru lintian-2.93.0/tags/u/useless-autoreconf-build-depends.tag lintian-2.89.0ubuntu1/tags/u/useless-autoreconf-build-depends.tag --- lintian-2.93.0/tags/u/useless-autoreconf-build-depends.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/useless-autoreconf-build-depends.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: useless-autoreconf-build-depends -Severity: warning -Check: debhelper -Explanation: Since compatibility level 10, debhelper enables the autoreconf - sequence by default. - . - It is therefore not necessary to specify build-dependencies on - dh-autoreconf or autotools-dev and they can be removed. diff -Nru lintian-2.93.0/tags/u/useless-whatis-entry.desc lintian-2.89.0ubuntu1/tags/u/useless-whatis-entry.desc --- lintian-2.93.0/tags/u/useless-whatis-entry.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/useless-whatis-entry.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,16 @@ +Tag: useless-whatis-entry +Severity: warning +Check: documentation/manual +Renamed-From: manpage-has-useless-whatis-entry +Info: The whatis entry for this manual page (the brief description found + in the NAME section) is of the form: + . + program - manual page for program + . + This conveys no information about what the program is for and is + repetitive. The short description should contain brief information about + what the program is for to aid in searching with apropos and similar + programs. + . + If this manual page was generated by help2man, use the -n option to + provide a more meaningful description. diff -Nru lintian-2.93.0/tags/u/useless-whatis-entry.tag lintian-2.89.0ubuntu1/tags/u/useless-whatis-entry.tag --- lintian-2.93.0/tags/u/useless-whatis-entry.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/useless-whatis-entry.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,16 +0,0 @@ -Tag: useless-whatis-entry -Severity: warning -Check: documentation/manual -Renamed-From: manpage-has-useless-whatis-entry -Explanation: The whatis entry for this manual page (the brief description found - in the NAME section) is of the form: - . - program - manual page for program - . - This conveys no information about what the program is for and is - repetitive. The short description should contain brief information about - what the program is for to aid in searching with apropos and similar - programs. - . - If this manual page was generated by help2man, use the -n option to - provide a more meaningful description. diff -Nru lintian-2.93.0/tags/u/use-of-compat-symlink.desc lintian-2.89.0ubuntu1/tags/u/use-of-compat-symlink.desc --- lintian-2.93.0/tags/u/use-of-compat-symlink.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/use-of-compat-symlink.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: use-of-compat-symlink +Severity: error +Check: files/hierarchy/standard +Info: This package uses a directory that, according to the Filesystem + Hierarchy Standard, should exist only as a compatibility symlink. + Packages should not traverse such symlinks when installing files, they + should use the standard directories instead. diff -Nru lintian-2.93.0/tags/u/use-of-compat-symlink.tag lintian-2.89.0ubuntu1/tags/u/use-of-compat-symlink.tag --- lintian-2.93.0/tags/u/use-of-compat-symlink.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/use-of-compat-symlink.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: use-of-compat-symlink -Severity: error -Check: files/hierarchy/standard -Explanation: This package uses a directory that, according to the Filesystem - Hierarchy Standard, should exist only as a compatibility symlink. - Packages should not traverse such symlinks when installing files, they - should use the standard directories instead. diff -Nru lintian-2.93.0/tags/u/uses-debhelper-compat-file.desc lintian-2.89.0ubuntu1/tags/u/uses-debhelper-compat-file.desc --- lintian-2.93.0/tags/u/uses-debhelper-compat-file.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/uses-debhelper-compat-file.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,15 @@ +Tag: uses-debhelper-compat-file +Severity: pedantic +Check: debhelper +Info: This package uses a debian/compat file to denote the + required debhelper compatibility number. + . + However, debhelper has replaced debian/compat with the + debhelper-compat virtual package for most circumstances. + . + Packages not using an experimental or beta compatibility level should + Build-Depend on the debhelper-compat virtual package, for + example: + . + Build-Depends: debhelper-compat (= 13) +Ref: debhelper(7) diff -Nru lintian-2.93.0/tags/u/uses-debhelper-compat-file.tag lintian-2.89.0ubuntu1/tags/u/uses-debhelper-compat-file.tag --- lintian-2.93.0/tags/u/uses-debhelper-compat-file.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/uses-debhelper-compat-file.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,15 +0,0 @@ -Tag: uses-debhelper-compat-file -Severity: pedantic -Check: debhelper -Explanation: This package uses a debian/compat file to denote the - required debhelper compatibility number. - . - However, debhelper has replaced debian/compat with the - debhelper-compat virtual package for most circumstances. - . - Packages not using an experimental or beta compatibility level should - Build-Depend on the debhelper-compat virtual package, for - example: - . - Build-Depends: debhelper-compat (= 13) -See-Also: debhelper(7) diff -Nru lintian-2.93.0/tags/u/uses-deprecated-adttmp.desc lintian-2.89.0ubuntu1/tags/u/uses-deprecated-adttmp.desc --- lintian-2.93.0/tags/u/uses-deprecated-adttmp.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/uses-deprecated-adttmp.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: uses-deprecated-adttmp +Severity: warning +Check: testsuite +Info: The specified test file appears to use the deprecated + ADTTMP variable. + . + Please replace this with AUTOPKGTEST_TMP. diff -Nru lintian-2.93.0/tags/u/uses-deprecated-adttmp.tag lintian-2.89.0ubuntu1/tags/u/uses-deprecated-adttmp.tag --- lintian-2.93.0/tags/u/uses-deprecated-adttmp.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/uses-deprecated-adttmp.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: uses-deprecated-adttmp -Severity: warning -Check: testsuite -Explanation: The specified test file appears to use the deprecated - ADTTMP variable. - . - Please replace this with AUTOPKGTEST_TMP. diff -Nru lintian-2.93.0/tags/u/uses-deprecated-compression-for-data-tarball.desc lintian-2.89.0ubuntu1/tags/u/uses-deprecated-compression-for-data-tarball.desc --- lintian-2.93.0/tags/u/uses-deprecated-compression-for-data-tarball.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/uses-deprecated-compression-for-data-tarball.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,12 @@ +Tag: uses-deprecated-compression-for-data-tarball +Severity: error +Check: deb-format +Info: The data portion of this binary package uses a deprecated compression + format. Although dpkg will support extracting such binary packages for + the foreseeable future, creating them will eventually be disallowed. A + warning is emitted for lzma since dpkg 1.16.4, and for bzip2 since dpkg + 1.17.7. + . + For lzma, xz is the direct replacement. For bzip2 either gzip or xz can + be used as a substitute, depending on the wanted properties: gzip for + maximum compatibility and speed, and xz for maximum compression ratio. diff -Nru lintian-2.93.0/tags/u/uses-deprecated-compression-for-data-tarball.tag lintian-2.89.0ubuntu1/tags/u/uses-deprecated-compression-for-data-tarball.tag --- lintian-2.93.0/tags/u/uses-deprecated-compression-for-data-tarball.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/uses-deprecated-compression-for-data-tarball.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,12 +0,0 @@ -Tag: uses-deprecated-compression-for-data-tarball -Severity: error -Check: deb-format -Explanation: The data portion of this binary package uses a deprecated compression - format. Although dpkg will support extracting such binary packages for - the foreseeable future, creating them will eventually be disallowed. A - warning is emitted for lzma since dpkg 1.16.4, and for bzip2 since dpkg - 1.17.7. - . - For lzma, xz is the direct replacement. For bzip2 either gzip or xz can - be used as a substitute, depending on the wanted properties: gzip for - maximum compatibility and speed, and xz for maximum compression ratio. diff -Nru lintian-2.93.0/tags/u/uses-dpkg-database-directly.desc lintian-2.89.0ubuntu1/tags/u/uses-dpkg-database-directly.desc --- lintian-2.93.0/tags/u/uses-dpkg-database-directly.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/uses-dpkg-database-directly.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,14 @@ +Tag: uses-dpkg-database-directly +Severity: warning +Certainty: possible +Check: files/contents +Info: The listed file or maintainer script appears to access the + internal database(s) of dpkg. + . + The entire dpkg database, its layout and files are an internal + interface and no program or package should be accessing it, other + than dpkg itself and the suite of dpkg tools. + . + Whilst the files may be editable by an admin, that's a supported (but + unrecommended) feature reserved for humans and not for automatic tools. +Ref: https://wiki.debian.org/DpkgConffileHandling diff -Nru lintian-2.93.0/tags/u/uses-dpkg-database-directly.tag lintian-2.89.0ubuntu1/tags/u/uses-dpkg-database-directly.tag --- lintian-2.93.0/tags/u/uses-dpkg-database-directly.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/uses-dpkg-database-directly.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,13 +0,0 @@ -Tag: uses-dpkg-database-directly -Severity: warning -Check: files/contents -Explanation: The listed file or maintainer script appears to access the - internal database(s) of dpkg. - . - The entire dpkg database, its layout and files are an internal - interface and no program or package should be accessing it, other - than dpkg itself and the suite of dpkg tools. - . - Whilst the files may be editable by an admin, that's a supported (but - unrecommended) feature reserved for humans and not for automatic tools. -See-Also: https://wiki.debian.org/DpkgConffileHandling diff -Nru lintian-2.93.0/tags/u/uses-implicit-await-trigger.desc lintian-2.89.0ubuntu1/tags/u/uses-implicit-await-trigger.desc --- lintian-2.93.0/tags/u/uses-implicit-await-trigger.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/uses-implicit-await-trigger.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,18 @@ +Tag: uses-implicit-await-trigger +Severity: warning +Certainty: possible +Check: triggers +Info: The listed trigger is present in the control file of the package. + The trigger is an await trigger, which may not be obvious from its name. + . + Await triggers place rather strong requirements on dpkg that often lead + to trigger cycles due to changes in other packages. + . + If the package does not need the guarantees that dpkg provides to await + triggers, please use the "-noawait" variant of the trigger. This is often + the case for packages that use the trigger to compile a form of cache. + . + If the package does need the guarantees provided by dpkg, then please + document the rationale in a comment above the trigger and use the + "-await" variant of the trigger to avoid this warning. +Ref: deb-triggers(5), #774559 diff -Nru lintian-2.93.0/tags/u/uses-implicit-await-trigger.tag lintian-2.89.0ubuntu1/tags/u/uses-implicit-await-trigger.tag --- lintian-2.93.0/tags/u/uses-implicit-await-trigger.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/uses-implicit-await-trigger.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,17 +0,0 @@ -Tag: uses-implicit-await-trigger -Severity: warning -Check: triggers -Explanation: The listed trigger is present in the control file of the package. - The trigger is an await trigger, which may not be obvious from its name. - . - Await triggers place rather strong requirements on dpkg that often lead - to trigger cycles due to changes in other packages. - . - If the package does not need the guarantees that dpkg provides to await - triggers, please use the "-noawait" variant of the trigger. This is often - the case for packages that use the trigger to compile a form of cache. - . - If the package does need the guarantees provided by dpkg, then please - document the rationale in a comment above the trigger and use the - "-await" variant of the trigger to avoid this warning. -See-Also: deb-triggers(5), Bug#774559 diff -Nru lintian-2.93.0/tags/u/uses-no-compression-for-control-tarball.desc lintian-2.89.0ubuntu1/tags/u/uses-no-compression-for-control-tarball.desc --- lintian-2.93.0/tags/u/uses-no-compression-for-control-tarball.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/uses-no-compression-for-control-tarball.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: uses-no-compression-for-control-tarball +Severity: error +Check: deb-format +Ref: deb(5) +Info: The control portion of this binary package uses a non-compressed + format. Although dpkg will support extracting such binary packages + since dpkg 1.10.24, creating them is not advised except in special + cases. diff -Nru lintian-2.93.0/tags/u/uses-no-compression-for-control-tarball.tag lintian-2.89.0ubuntu1/tags/u/uses-no-compression-for-control-tarball.tag --- lintian-2.93.0/tags/u/uses-no-compression-for-control-tarball.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/uses-no-compression-for-control-tarball.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: uses-no-compression-for-control-tarball -Severity: error -Check: deb-format -See-Also: deb(5) -Explanation: The control portion of this binary package uses a non-compressed - format. Although dpkg will support extracting such binary packages - since dpkg 1.10.24, creating them is not advised except in special - cases. diff -Nru lintian-2.93.0/tags/u/uses-no-compression-for-data-tarball.desc lintian-2.89.0ubuntu1/tags/u/uses-no-compression-for-data-tarball.desc --- lintian-2.93.0/tags/u/uses-no-compression-for-data-tarball.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/uses-no-compression-for-data-tarball.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,11 @@ +Tag: uses-no-compression-for-data-tarball +Severity: error +Check: deb-format +Ref: deb(5) +Info: The data portion of this binary package uses a non-compressed + format. Although dpkg will support extracting such binary packages + since dpkg 1.10.24, creating them is not advised except in special + cases. + . + Except if data is non-compressible, use gzip for + maximum compatibility and speed, and xz for maximum compression ratio. diff -Nru lintian-2.93.0/tags/u/uses-no-compression-for-data-tarball.tag lintian-2.89.0ubuntu1/tags/u/uses-no-compression-for-data-tarball.tag --- lintian-2.93.0/tags/u/uses-no-compression-for-data-tarball.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/uses-no-compression-for-data-tarball.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,11 +0,0 @@ -Tag: uses-no-compression-for-data-tarball -Severity: error -Check: deb-format -See-Also: deb(5) -Explanation: The data portion of this binary package uses a non-compressed - format. Although dpkg will support extracting such binary packages - since dpkg 1.10.24, creating them is not advised except in special - cases. - . - Except if data is non-compressible, use gzip for - maximum compatibility and speed, and xz for maximum compression ratio. diff -Nru lintian-2.93.0/tags/u/using-first-person-in-description.desc lintian-2.89.0ubuntu1/tags/u/using-first-person-in-description.desc --- lintian-2.93.0/tags/u/using-first-person-in-description.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/using-first-person-in-description.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,13 @@ +Tag: using-first-person-in-description +Severity: info +Certainty: possible +Check: fields/description +Info: You should avoid the use of first person ("I will do this..." or + "We recommend..."). The computer is not a person and the description + does not speak for the maintainer or maintainers. Instead, use a more + neutral construction and try to rephrase into factual statements about + the package. + . + For example, rather than saying "I don't recommend this package if you + are short on memory," say something like "this package is not suitable + for low-memory systems." diff -Nru lintian-2.93.0/tags/u/using-first-person-in-description.tag lintian-2.89.0ubuntu1/tags/u/using-first-person-in-description.tag --- lintian-2.93.0/tags/u/using-first-person-in-description.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/using-first-person-in-description.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,12 +0,0 @@ -Tag: using-first-person-in-description -Severity: info -Check: fields/description -Explanation: You should avoid the use of first person ("I will do this..." or - "We recommend..."). The computer is not a person and the description - does not speak for the maintainer or maintainers. Instead, use a more - neutral construction and try to rephrase into factual statements about - the package. - . - For example, rather than saying "I don't recommend this package if you - are short on memory," say something like "this package is not suitable - for low-memory systems." diff -Nru lintian-2.93.0/tags/u/using-first-person-in-templates.desc lintian-2.89.0ubuntu1/tags/u/using-first-person-in-templates.desc --- lintian-2.93.0/tags/u/using-first-person-in-templates.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/using-first-person-in-templates.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,12 @@ +Tag: using-first-person-in-templates +Severity: warning +Certainty: possible +Check: debian/debconf +Info: You should avoid the use of first person ("I will do this..." or + "We recommend..."). The computer is not a person and the Debconf + templates do not speak for the Debian developers. You should use neutral + construction and often the passive form. + . + If this template is only used internally by the package and not displayed + to the user, put "for internal use" in the short description. +Ref: devref 6.5.2.5 diff -Nru lintian-2.93.0/tags/u/using-first-person-in-templates.tag lintian-2.89.0ubuntu1/tags/u/using-first-person-in-templates.tag --- lintian-2.93.0/tags/u/using-first-person-in-templates.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/using-first-person-in-templates.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,11 +0,0 @@ -Tag: using-first-person-in-templates -Severity: warning -Check: debian/debconf -Explanation: You should avoid the use of first person ("I will do this..." or - "We recommend..."). The computer is not a person and the Debconf - templates do not speak for the Debian developers. You should use neutral - construction and often the passive form. - . - If this template is only used internally by the package and not displayed - to the user, put "for internal use" in the short description. -See-Also: devref 6.5.2.5 diff -Nru lintian-2.93.0/tags/u/using-imperative-form-in-templates.desc lintian-2.89.0ubuntu1/tags/u/using-imperative-form-in-templates.desc --- lintian-2.93.0/tags/u/using-imperative-form-in-templates.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/using-imperative-form-in-templates.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: using-imperative-form-in-templates +Severity: warning +Check: debian/debconf +Info: Do not use useless imperative constructions such as "Please choose...", + "Enter...". The interface will make it obvious that the user needs to + choose or enter something. +Ref: devref 6.5.4.2 diff -Nru lintian-2.93.0/tags/u/using-imperative-form-in-templates.tag lintian-2.89.0ubuntu1/tags/u/using-imperative-form-in-templates.tag --- lintian-2.93.0/tags/u/using-imperative-form-in-templates.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/using-imperative-form-in-templates.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: using-imperative-form-in-templates -Severity: warning -Check: debian/debconf -Explanation: Do not use useless imperative constructions such as "Please choose...", - "Enter...". The interface will make it obvious that the user needs to - choose or enter something. -See-Also: devref 6.5.4.2 diff -Nru lintian-2.93.0/tags/u/using-question-in-extended-description-in-templates.desc lintian-2.89.0ubuntu1/tags/u/using-question-in-extended-description-in-templates.desc --- lintian-2.93.0/tags/u/using-question-in-extended-description-in-templates.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/using-question-in-extended-description-in-templates.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: using-question-in-extended-description-in-templates +Severity: warning +Check: debian/debconf +Info: The extended description of a debconf template should never include + a question. + . + If this template is only used internally by the package and not displayed + to the user, put "for internal use" in the short description. +Ref: devref 6.5.3.2 diff -Nru lintian-2.93.0/tags/u/using-question-in-extended-description-in-templates.tag lintian-2.89.0ubuntu1/tags/u/using-question-in-extended-description-in-templates.tag --- lintian-2.93.0/tags/u/using-question-in-extended-description-in-templates.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/using-question-in-extended-description-in-templates.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: using-question-in-extended-description-in-templates -Severity: warning -Check: debian/debconf -Explanation: The extended description of a debconf template should never include - a question. - . - If this template is only used internally by the package and not displayed - to the user, put "for internal use" in the short description. -See-Also: devref 6.5.3.2 diff -Nru lintian-2.93.0/tags/u/usr-share-doc-symlink-points-outside-of-usr-share-doc.desc lintian-2.89.0ubuntu1/tags/u/usr-share-doc-symlink-points-outside-of-usr-share-doc.desc --- lintian-2.93.0/tags/u/usr-share-doc-symlink-points-outside-of-usr-share-doc.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/usr-share-doc-symlink-points-outside-of-usr-share-doc.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: usr-share-doc-symlink-points-outside-of-usr-share-doc +Severity: error +Check: debian/copyright +Info: The /usr/share/doc/pkg symbolic link is pointing to a directory + outside of /usr/share/doc. +Ref: policy 12.5 diff -Nru lintian-2.93.0/tags/u/usr-share-doc-symlink-points-outside-of-usr-share-doc.tag lintian-2.89.0ubuntu1/tags/u/usr-share-doc-symlink-points-outside-of-usr-share-doc.tag --- lintian-2.93.0/tags/u/usr-share-doc-symlink-points-outside-of-usr-share-doc.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/usr-share-doc-symlink-points-outside-of-usr-share-doc.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: usr-share-doc-symlink-points-outside-of-usr-share-doc -Severity: error -Check: debian/copyright -Explanation: The /usr/share/doc/*pkg* symbolic link is pointing to a directory - outside of /usr/share/doc. -See-Also: policy 12.5 diff -Nru lintian-2.93.0/tags/u/usr-share-doc-symlink-to-foreign-package.desc lintian-2.89.0ubuntu1/tags/u/usr-share-doc-symlink-to-foreign-package.desc --- lintian-2.93.0/tags/u/usr-share-doc-symlink-to-foreign-package.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/usr-share-doc-symlink-to-foreign-package.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,13 @@ +Tag: usr-share-doc-symlink-to-foreign-package +Severity: error +Check: debian/copyright +Info: If the package installs a symbolic link + /usr/share/doc/pkg1 -> pkg2, then pkg1 + and pkg2 must both come from the same source package. + . + The best solution is probably to stop symlinking the + /usr/share/doc directory for this package and instead include a + real /usr/share/doc/pkg1 directory within pkg1 with the + appropriate contents (such as the copyright and + changelog.Debian.gz files). +Ref: policy 12.5 diff -Nru lintian-2.93.0/tags/u/usr-share-doc-symlink-to-foreign-package.tag lintian-2.89.0ubuntu1/tags/u/usr-share-doc-symlink-to-foreign-package.tag --- lintian-2.93.0/tags/u/usr-share-doc-symlink-to-foreign-package.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/usr-share-doc-symlink-to-foreign-package.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,13 +0,0 @@ -Tag: usr-share-doc-symlink-to-foreign-package -Severity: error -Check: debian/copyright -Explanation: If the package installs a symbolic link - /usr/share/doc/*pkg1* -> *pkg2*, then *pkg1* - and *pkg2* must both come from the same source package. - . - The best solution is probably to stop symlinking the - /usr/share/doc directory for this package and instead include a - real /usr/share/doc/*pkg1* directory within *pkg1* with the - appropriate contents (such as the copyright and - changelog.Debian.gz files). -See-Also: policy 12.5 diff -Nru lintian-2.93.0/tags/u/usr-share-doc-symlink-without-dependency.desc lintian-2.89.0ubuntu1/tags/u/usr-share-doc-symlink-without-dependency.desc --- lintian-2.93.0/tags/u/usr-share-doc-symlink-without-dependency.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/usr-share-doc-symlink-without-dependency.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,22 @@ +Tag: usr-share-doc-symlink-without-dependency +Severity: error +Certainty: possible +Check: debian/copyright +Info: If the package installs a symbolic link + /usr/share/doc/pkg1 -> pkg2, then pkg1 + must depend on pkg2 directory, with the same version as + pkg1. + . + Adding the dependency just to fix this bug is often not a good solution. + Usually, it's better to include a real /usr/share/doc/pkg1 + directory within pkg1 and copy the copyright file into that + directory. + . + Transitive dependencies are not allowed here. In other words, if the + documentation directory is shipped in pkg3 and pkg1 depends + on pkg2, which in turn depends on pkg3, that's still an + error. Copyright file extractors are not required to go more than one + level deep when resolving dependencies. Each package should have a + direct dependency on the package which includes its documentation + directory. +Ref: policy 12.5 diff -Nru lintian-2.93.0/tags/u/usr-share-doc-symlink-without-dependency.tag lintian-2.89.0ubuntu1/tags/u/usr-share-doc-symlink-without-dependency.tag --- lintian-2.93.0/tags/u/usr-share-doc-symlink-without-dependency.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/u/usr-share-doc-symlink-without-dependency.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,21 +0,0 @@ -Tag: usr-share-doc-symlink-without-dependency -Severity: error -Check: debian/copyright -Explanation: If the package installs a symbolic link - /usr/share/doc/*pkg1* -> *pkg2*, then *pkg1* - must depend on *pkg2* directory, with the same version as - *pkg1*. - . - Adding the dependency just to fix this bug is often not a good solution. - Usually, it's better to include a real /usr/share/doc/*pkg1* - directory within *pkg1* and copy the copyright file into that - directory. - . - Transitive dependencies are not allowed here. In other words, if the - documentation directory is shipped in *pkg3* and *pkg1* depends - on *pkg2*, which in turn depends on *pkg3*, that's still an - error. Copyright file extractors are not required to go more than one - level deep when resolving dependencies. Each package should have a - direct dependency on the package which includes its documentation - directory. -See-Also: policy 12.5 diff -Nru lintian-2.93.0/tags/v/vcs-browser-links-to-empty-view.desc lintian-2.89.0ubuntu1/tags/v/vcs-browser-links-to-empty-view.desc --- lintian-2.93.0/tags/v/vcs-browser-links-to-empty-view.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/v/vcs-browser-links-to-empty-view.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: vcs-browser-links-to-empty-view +Severity: warning +Check: fields/vcs +Info: The VCS-Browser links to an an empty view of the repository due to + it including a suffix such as ?rev=0&sc=0. + . + You should remove this suffix from the field. diff -Nru lintian-2.93.0/tags/v/vcs-browser-links-to-empty-view.tag lintian-2.89.0ubuntu1/tags/v/vcs-browser-links-to-empty-view.tag --- lintian-2.93.0/tags/v/vcs-browser-links-to-empty-view.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/v/vcs-browser-links-to-empty-view.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: vcs-browser-links-to-empty-view -Severity: warning -Check: fields/vcs -Explanation: The VCS-Browser links to an an empty view of the repository due to - it including a suffix such as ?rev=0&sc=0. - . - You should remove this suffix from the field. diff -Nru lintian-2.93.0/tags/v/vcs.desc lintian-2.89.0ubuntu1/tags/v/vcs.desc --- lintian-2.93.0/tags/v/vcs.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/v/vcs.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,5 @@ +Tag: vcs +Severity: classification +Check: fields/vcs +Info: The package uses the specified VCS (eg. "git") according to the + debian/control file. diff -Nru lintian-2.93.0/tags/v/vcs-field-bitrotted.desc lintian-2.89.0ubuntu1/tags/v/vcs-field-bitrotted.desc --- lintian-2.93.0/tags/v/vcs-field-bitrotted.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/v/vcs-field-bitrotted.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: vcs-field-bitrotted +Severity: warning +Check: fields/vcs +Info: The VCS-* field uses an address which no longer works. Please + update it to use the current canonical URI instead. + . + Note that this check is based on a list of known URIs or/and + patterns. Lintian did not send an HTTP request to the URI to test + this. diff -Nru lintian-2.93.0/tags/v/vcs-field-bitrotted.tag lintian-2.89.0ubuntu1/tags/v/vcs-field-bitrotted.tag --- lintian-2.93.0/tags/v/vcs-field-bitrotted.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/v/vcs-field-bitrotted.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: vcs-field-bitrotted -Severity: warning -Check: fields/vcs -Explanation: The VCS-* field uses an address which no longer works. Please - update it to use the current canonical URI instead. - . - Note that this check is based on a list of known URIs or/and - patterns. Lintian did not send an HTTP request to the URI to test - this. diff -Nru lintian-2.93.0/tags/v/vcs-field-has-unexpected-spaces.desc lintian-2.89.0ubuntu1/tags/v/vcs-field-has-unexpected-spaces.desc --- lintian-2.93.0/tags/v/vcs-field-has-unexpected-spaces.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/v/vcs-field-has-unexpected-spaces.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,12 @@ +Tag: vcs-field-has-unexpected-spaces +Severity: warning +Certainty: possible +Check: fields/vcs +Info: The VCS-* field contains more spaces than expected or spaces at + places where they were not expected. Where possible, escape valid + spaces in URIs to avoid any ambiguity with respect to possible future + additional optional fields. + . + This may be caused by incorrect use of the -b branch + separator. +Ref: policy 5.6.26 diff -Nru lintian-2.93.0/tags/v/vcs-field-has-unexpected-spaces.tag lintian-2.89.0ubuntu1/tags/v/vcs-field-has-unexpected-spaces.tag --- lintian-2.93.0/tags/v/vcs-field-has-unexpected-spaces.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/v/vcs-field-has-unexpected-spaces.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,11 +0,0 @@ -Tag: vcs-field-has-unexpected-spaces -Severity: warning -Check: fields/vcs -Explanation: The VCS-* field contains more spaces than expected or spaces at - places where they were not expected. Where possible, escape valid - spaces in URIs to avoid any ambiguity with respect to possible future - additional optional fields. - . - This may be caused by incorrect use of the -b branch - separator. -See-Also: policy 5.6.26 diff -Nru lintian-2.93.0/tags/v/vcs-field-mismatch.desc lintian-2.89.0ubuntu1/tags/v/vcs-field-mismatch.desc --- lintian-2.93.0/tags/v/vcs-field-mismatch.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/v/vcs-field-mismatch.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: vcs-field-mismatch +Severity: warning +Certainty: possible +Check: fields/vcs +Info: The VCS-* field name appears to mismatch the target URI. + . + You might have moved the Debian packaging to another version control + system but have not updated the field name. For example, using the + Vcs-Svn field to point to a Git repository now hosted on + salsa.debian.org. diff -Nru lintian-2.93.0/tags/v/vcs-field-mismatch.tag lintian-2.89.0ubuntu1/tags/v/vcs-field-mismatch.tag --- lintian-2.93.0/tags/v/vcs-field-mismatch.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/v/vcs-field-mismatch.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: vcs-field-mismatch -Severity: warning -Check: fields/vcs -Explanation: The VCS-* field name appears to mismatch the target URI. - . - You might have moved the Debian packaging to another version control - system but have not updated the field name. For example, using the - Vcs-Svn field to point to a Git repository now hosted on - salsa.debian.org. diff -Nru lintian-2.93.0/tags/v/vcs-field-not-canonical.desc lintian-2.89.0ubuntu1/tags/v/vcs-field-not-canonical.desc --- lintian-2.93.0/tags/v/vcs-field-not-canonical.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/v/vcs-field-not-canonical.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,15 @@ +Tag: vcs-field-not-canonical +Severity: info +Certainty: possible +Check: fields/vcs +Info: The VCS-* field contains an uncanonical URI. Please update to use + the current canonical URI instead. This reduces the network bandwidth used + and makes debcheckout work independent of the port forwarding and + redirections properly working. + . + The definition of canonical used here is the URIs announced by the Alioth + admins (see reference). + . + Note that this check is based on a list of known URIs. Lintian did not + send an HTTP request to the URI to test this. +Ref: https://lists.debian.org/debian-devel-announce/2011/05/msg00009.html diff -Nru lintian-2.93.0/tags/v/vcs-field-not-canonical.tag lintian-2.89.0ubuntu1/tags/v/vcs-field-not-canonical.tag --- lintian-2.93.0/tags/v/vcs-field-not-canonical.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/v/vcs-field-not-canonical.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,14 +0,0 @@ -Tag: vcs-field-not-canonical -Severity: info -Check: fields/vcs -Explanation: The VCS-* field contains an uncanonical URI. Please update to use - the current canonical URI instead. This reduces the network bandwidth used - and makes debcheckout work independent of the port forwarding and - redirections properly working. - . - The definition of canonical used here is the URIs announced by the Alioth - admins (see reference). - . - Note that this check is based on a list of known URIs. Lintian did not - send an HTTP request to the URI to test this. -See-Also: https://lists.debian.org/debian-devel-announce/2011/05/msg00009.html diff -Nru lintian-2.93.0/tags/v/vcs-fields-use-more-than-one-vcs.desc lintian-2.89.0ubuntu1/tags/v/vcs-fields-use-more-than-one-vcs.desc --- lintian-2.93.0/tags/v/vcs-fields-use-more-than-one-vcs.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/v/vcs-fields-use-more-than-one-vcs.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,5 @@ +Tag: vcs-fields-use-more-than-one-vcs +Severity: info +Certainty: possible +Check: fields/vcs +Info: The Vcs-* fields mix more than one version control system. diff -Nru lintian-2.93.0/tags/v/vcs-fields-use-more-than-one-vcs.tag lintian-2.89.0ubuntu1/tags/v/vcs-fields-use-more-than-one-vcs.tag --- lintian-2.93.0/tags/v/vcs-fields-use-more-than-one-vcs.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/v/vcs-fields-use-more-than-one-vcs.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,4 +0,0 @@ -Tag: vcs-fields-use-more-than-one-vcs -Severity: info -Check: fields/vcs -Explanation: The Vcs-* fields mix more than one version control system. diff -Nru lintian-2.93.0/tags/v/vcs-field-uses-insecure-uri.desc lintian-2.89.0ubuntu1/tags/v/vcs-field-uses-insecure-uri.desc --- lintian-2.93.0/tags/v/vcs-field-uses-insecure-uri.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/v/vcs-field-uses-insecure-uri.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,11 @@ +Tag: vcs-field-uses-insecure-uri +Severity: info +Check: fields/vcs +Info: The Vcs-* field uses an unencrypted transport protocol for the + URI. It is recommended to use a secure transport such as HTTPS for + anonymous read-only access. + . + Note that you can often just exchange e.g. git:// with https:// for + repositories. Though, in some cases (bzr's "lp:" or CVS's pserver) it + might not be possible to use an alternative url and still have a + working (anonymous read-only) repository. diff -Nru lintian-2.93.0/tags/v/vcs-field-uses-insecure-uri.tag lintian-2.89.0ubuntu1/tags/v/vcs-field-uses-insecure-uri.tag --- lintian-2.93.0/tags/v/vcs-field-uses-insecure-uri.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/v/vcs-field-uses-insecure-uri.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,11 +0,0 @@ -Tag: vcs-field-uses-insecure-uri -Severity: info -Check: fields/vcs -Explanation: The Vcs-* field uses an unencrypted transport protocol for the - URI. It is recommended to use a secure transport such as HTTPS for - anonymous read-only access. - . - Note that you can often just exchange e.g. git:// with https:// for - repositories. Though, in some cases (bzr's "lp:" or CVS's pserver) it - might not be possible to use an alternative url and still have a - working (anonymous read-only) repository. diff -Nru lintian-2.93.0/tags/v/vcs-field-uses-not-recommended-uri-format.desc lintian-2.89.0ubuntu1/tags/v/vcs-field-uses-not-recommended-uri-format.desc --- lintian-2.93.0/tags/v/vcs-field-uses-not-recommended-uri-format.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/v/vcs-field-uses-not-recommended-uri-format.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,11 @@ +Tag: vcs-field-uses-not-recommended-uri-format +Severity: warning +Certainty: possible +Check: fields/vcs +Info: The VCS-* field uses a URI which doesn't match the recommended + format, but still looks valid. Examples for not recommended URI formats + are protocols that require authentication (like SSH). Instead where + possible you should provide a URI that is accessible for everyone + without authentication. + . + This renders debcheckout(1) unusable in these cases. diff -Nru lintian-2.93.0/tags/v/vcs-field-uses-not-recommended-uri-format.tag lintian-2.89.0ubuntu1/tags/v/vcs-field-uses-not-recommended-uri-format.tag --- lintian-2.93.0/tags/v/vcs-field-uses-not-recommended-uri-format.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/v/vcs-field-uses-not-recommended-uri-format.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,10 +0,0 @@ -Tag: vcs-field-uses-not-recommended-uri-format -Severity: warning -Check: fields/vcs -Explanation: The VCS-* field uses a URI which doesn't match the recommended - format, but still looks valid. Examples for not recommended URI formats - are protocols that require authentication (like SSH). Instead where - possible you should provide a URI that is accessible for everyone - without authentication. - . - This renders debcheckout(1) unusable in these cases. diff -Nru lintian-2.93.0/tags/v/vcs-field-uses-unknown-uri-format.desc lintian-2.89.0ubuntu1/tags/v/vcs-field-uses-unknown-uri-format.desc --- lintian-2.93.0/tags/v/vcs-field-uses-unknown-uri-format.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/v/vcs-field-uses-unknown-uri-format.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: vcs-field-uses-unknown-uri-format +Severity: warning +Certainty: possible +Check: fields/vcs +Info: The VCS-* field uses an URI which doesn't match any known format. + You might have forgotten the protocol before the hostname. diff -Nru lintian-2.93.0/tags/v/vcs-field-uses-unknown-uri-format.tag lintian-2.89.0ubuntu1/tags/v/vcs-field-uses-unknown-uri-format.tag --- lintian-2.93.0/tags/v/vcs-field-uses-unknown-uri-format.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/v/vcs-field-uses-unknown-uri-format.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,5 +0,0 @@ -Tag: vcs-field-uses-unknown-uri-format -Severity: warning -Check: fields/vcs -Explanation: The VCS-* field uses an URI which doesn't match any known format. - You might have forgotten the protocol before the hostname. diff -Nru lintian-2.93.0/tags/v/vcs-git-uses-invalid-user-uri.desc lintian-2.89.0ubuntu1/tags/v/vcs-git-uses-invalid-user-uri.desc --- lintian-2.93.0/tags/v/vcs-git-uses-invalid-user-uri.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/v/vcs-git-uses-invalid-user-uri.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: vcs-git-uses-invalid-user-uri +Severity: warning +Check: fields/vcs +Info: The Vcs-Git field is pointing to a personal repository using + a git://(git|anonscm).debian.org/~$LOGIN/$PRJ.git style URI. This is not + recommended since the repository this points is not automatically updated + when pushing to the personal repository. The recommended URI for anonymous + access is https://anonscm.debian.org/git/users/$LOGIN/$PRJ.git. diff -Nru lintian-2.93.0/tags/v/vcs-git-uses-invalid-user-uri.tag lintian-2.89.0ubuntu1/tags/v/vcs-git-uses-invalid-user-uri.tag --- lintian-2.93.0/tags/v/vcs-git-uses-invalid-user-uri.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/v/vcs-git-uses-invalid-user-uri.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: vcs-git-uses-invalid-user-uri -Severity: warning -Check: fields/vcs -Explanation: The Vcs-Git field is pointing to a personal repository using - a git://(git|anonscm).debian.org/~$LOGIN/$PRJ.git style URI. This is not - recommended since the repository this points is not automatically updated - when pushing to the personal repository. The recommended URI for anonymous - access is https://anonscm.debian.org/git/users/$LOGIN/$PRJ.git. diff -Nru lintian-2.93.0/tags/v/vcs-obsolete-in-debian-infrastructure.desc lintian-2.89.0ubuntu1/tags/v/vcs-obsolete-in-debian-infrastructure.desc --- lintian-2.93.0/tags/v/vcs-obsolete-in-debian-infrastructure.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/v/vcs-obsolete-in-debian-infrastructure.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,16 @@ +Tag: vcs-obsolete-in-debian-infrastructure +Severity: warning +Check: fields/vcs +Info: The specified Vcs-* field points to an area within the *.debian.org + infrastructure but refers to a version control system that has been + deprecated. + . + After 1st May 2018, Debian ceased to offer hosting for any version + control system other than Git and the Alioth service became read-only + in May 2018. Packages should migrate to Git hosting on + https://salsa.debian.org. + . + For further information about salsa.debian.org, including how to add + HTTP redirects from alioth, please consult the Debian Wiki. +Ref: https://lists.debian.org/debian-devel-announce/2017/08/msg00008.html, + https://wiki.debian.org/Salsa diff -Nru lintian-2.93.0/tags/v/vcs-obsolete-in-debian-infrastructure.tag lintian-2.89.0ubuntu1/tags/v/vcs-obsolete-in-debian-infrastructure.tag --- lintian-2.93.0/tags/v/vcs-obsolete-in-debian-infrastructure.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/v/vcs-obsolete-in-debian-infrastructure.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,16 +0,0 @@ -Tag: vcs-obsolete-in-debian-infrastructure -Severity: warning -Check: fields/vcs -Explanation: The specified Vcs-* field points to an area within the *.debian.org - infrastructure but refers to a version control system that has been - deprecated. - . - After 1st May 2018, Debian ceased to offer hosting for any version - control system other than Git and the Alioth service became read-only - in May 2018. Packages should migrate to Git hosting on - https://salsa.debian.org. - . - For further information about salsa.debian.org, including how to add - HTTP redirects from alioth, please consult the Debian Wiki. -See-Also: https://lists.debian.org/debian-devel-announce/2017/08/msg00008.html, - https://wiki.debian.org/Salsa diff -Nru lintian-2.93.0/tags/v/vcs.tag lintian-2.89.0ubuntu1/tags/v/vcs.tag --- lintian-2.93.0/tags/v/vcs.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/v/vcs.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,5 +0,0 @@ -Tag: vcs -Severity: classification -Check: fields/vcs -Explanation: The package uses the specified VCS (eg. "git") according to the - debian/control file. diff -Nru lintian-2.93.0/tags/v/vcs-uri.desc lintian-2.89.0ubuntu1/tags/v/vcs-uri.desc --- lintian-2.93.0/tags/v/vcs-uri.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/v/vcs-uri.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,5 @@ +Tag: vcs-uri +Severity: classification +Check: fields/vcs +Info: The package uses the specified VCS URI according to the + debian/control file. diff -Nru lintian-2.93.0/tags/v/vcs-uri.tag lintian-2.89.0ubuntu1/tags/v/vcs-uri.tag --- lintian-2.93.0/tags/v/vcs-uri.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/v/vcs-uri.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,5 +0,0 @@ -Tag: vcs-uri -Severity: classification -Check: fields/vcs -Explanation: The package uses the specified VCS URI according to the - debian/control file. diff -Nru lintian-2.93.0/tags/v/version-refers-to-distribution.desc lintian-2.89.0ubuntu1/tags/v/version-refers-to-distribution.desc --- lintian-2.93.0/tags/v/version-refers-to-distribution.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/v/version-refers-to-distribution.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,14 @@ +Tag: version-refers-to-distribution +Severity: warning +Check: debian/changelog +Info: The Debian portion of the package version contains a reference to a + particular Debian release or distribution. This should only be done for + uploads targeted at a particular release, not at unstable or + experimental, and should refer to the release by version number or code + name. + . + Using "testing" or "stable" in a package version targeted at the current + testing or stable release is less informative than using the code name or + version number and may cause annoying version sequencing issues if the + package doesn't change before the next release cycle starts. +Ref: devref 5.14.3 diff -Nru lintian-2.93.0/tags/v/version-refers-to-distribution.tag lintian-2.89.0ubuntu1/tags/v/version-refers-to-distribution.tag --- lintian-2.93.0/tags/v/version-refers-to-distribution.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/v/version-refers-to-distribution.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,14 +0,0 @@ -Tag: version-refers-to-distribution -Severity: warning -Check: debian/changelog -Explanation: The Debian portion of the package version contains a reference to a - particular Debian release or distribution. This should only be done for - uploads targeted at a particular release, not at unstable or - experimental, and should refer to the release by version number or code - name. - . - Using "testing" or "stable" in a package version targeted at the current - testing or stable release is less informative than using the code name or - version number and may cause annoying version sequencing issues if the - package doesn't change before the next release cycle starts. -See-Also: devref 5.14.3 diff -Nru lintian-2.93.0/tags/v/version-substvar-for-external-package.desc lintian-2.89.0ubuntu1/tags/v/version-substvar-for-external-package.desc --- lintian-2.93.0/tags/v/version-substvar-for-external-package.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/v/version-substvar-for-external-package.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: version-substvar-for-external-package +Severity: error +Check: debian/version-substvars +Info: The first package has a relation on the second package using a + dpkg-control substitution variable to generate the versioned part of + the relation. However the second package is not built from this + source package. Usually this means there is a mistake or typo in the + package name in this dependency. diff -Nru lintian-2.93.0/tags/v/version-substvar-for-external-package.tag lintian-2.89.0ubuntu1/tags/v/version-substvar-for-external-package.tag --- lintian-2.93.0/tags/v/version-substvar-for-external-package.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/v/version-substvar-for-external-package.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: version-substvar-for-external-package -Severity: error -Check: debian/version-substvars -Explanation: The first package has a relation on the second package using a - dpkg-control substitution variable to generate the versioned part of - the relation. However the second package is not built from this - source package. Usually this means there is a mistake or typo in the - package name in this dependency. diff -Nru lintian-2.93.0/tags/v/very-long-line-length-in-source-file.desc lintian-2.89.0ubuntu1/tags/v/very-long-line-length-in-source-file.desc --- lintian-2.93.0/tags/v/very-long-line-length-in-source-file.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/v/very-long-line-length-in-source-file.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,22 @@ +Tag: very-long-line-length-in-source-file +Severity: pedantic +Check: cruft +Info: The source file includes a line length that is well beyond + the normally human made code line length. + . + This very long line length does not allow Lintian to do + correctly some source file checks. + . + This line could also be the result of some text injected by + a computer program, and thus could lead to FTBFS bugs. + . + Last but not least, long line in source code could be used + to obfuscate the source code and to hide stuff like backdoors + or security problems. + . + It could be due to jslint source comments or other build tool + comments. + . + You may report this issue upstream. +Renamed-From: + insane-line-length-in-source-file diff -Nru lintian-2.93.0/tags/v/very-long-line-length-in-source-file.tag lintian-2.89.0ubuntu1/tags/v/very-long-line-length-in-source-file.tag --- lintian-2.93.0/tags/v/very-long-line-length-in-source-file.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/v/very-long-line-length-in-source-file.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,22 +0,0 @@ -Tag: very-long-line-length-in-source-file -Severity: pedantic -Check: cruft -Explanation: The source file includes a line length that is well beyond - the normally human made code line length. - . - This very long line length does not allow Lintian to do - correctly some source file checks. - . - This line could also be the result of some text injected by - a computer program, and thus could lead to FTBFS bugs. - . - Last but not least, long line in source code could be used - to obfuscate the source code and to hide stuff like backdoors - or security problems. - . - It could be due to jslint source comments or other build tool - comments. - . - You may report this issue upstream. -Renamed-From: - insane-line-length-in-source-file diff -Nru lintian-2.93.0/tags/v/vim-addon-within-vim-runtime-path.desc lintian-2.89.0ubuntu1/tags/v/vim-addon-within-vim-runtime-path.desc --- lintian-2.93.0/tags/v/vim-addon-within-vim-runtime-path.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/v/vim-addon-within-vim-runtime-path.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: vim-addon-within-vim-runtime-path +Severity: warning +Check: vim +Info: Vim addons should not be installed directly under a directory contained + in the Vim runtime path. Users shall be given the freedom to choose which + addons they want to have enabled and which they don't. +Ref: vim-policy 3.1 diff -Nru lintian-2.93.0/tags/v/vim-addon-within-vim-runtime-path.tag lintian-2.89.0ubuntu1/tags/v/vim-addon-within-vim-runtime-path.tag --- lintian-2.93.0/tags/v/vim-addon-within-vim-runtime-path.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/v/vim-addon-within-vim-runtime-path.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: vim-addon-within-vim-runtime-path -Severity: warning -Check: vim -Explanation: Vim addons should not be installed directly under a directory contained - in the Vim runtime path. Users shall be given the freedom to choose which - addons they want to have enabled and which they don't. -See-Also: vim-policy 3.1 diff -Nru lintian-2.93.0/tags/v/virtual-package-depends-without-real-package-depends.desc lintian-2.89.0ubuntu1/tags/v/virtual-package-depends-without-real-package-depends.desc --- lintian-2.93.0/tags/v/virtual-package-depends-without-real-package-depends.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/v/virtual-package-depends-without-real-package-depends.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,15 @@ +Tag: virtual-package-depends-without-real-package-depends +Severity: warning +Certainty: possible +Check: fields/package-relations +Info: The package declares a depends on a virtual package without listing a + real package as an alternative first. + . + If this package could ever be a build dependency, it should list a real + package as the first alternative to any virtual package in its Depends. + Otherwise, the build daemons will not be able to provide a consistent + build environment. + . + If it will never be a build dependency, this isn't necessary, but you may + want to consider doing so anyway if there is a real package providing + that virtual package that most users will want to use. diff -Nru lintian-2.93.0/tags/v/virtual-package-depends-without-real-package-depends.tag lintian-2.89.0ubuntu1/tags/v/virtual-package-depends-without-real-package-depends.tag --- lintian-2.93.0/tags/v/virtual-package-depends-without-real-package-depends.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/v/virtual-package-depends-without-real-package-depends.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,14 +0,0 @@ -Tag: virtual-package-depends-without-real-package-depends -Severity: warning -Check: fields/package-relations -Explanation: The package declares a depends on a virtual package without listing a - real package as an alternative first. - . - If this package could ever be a build dependency, it should list a real - package as the first alternative to any virtual package in its Depends. - Otherwise, the build daemons will not be able to provide a consistent - build environment. - . - If it will never be a build dependency, this isn't necessary, but you may - want to consider doing so anyway if there is a real package providing - that virtual package that most users will want to use. diff -Nru lintian-2.93.0/tags/w/wayward-symbolic-link-target-in-source.desc lintian-2.89.0ubuntu1/tags/w/wayward-symbolic-link-target-in-source.desc --- lintian-2.93.0/tags/w/wayward-symbolic-link-target-in-source.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/w/wayward-symbolic-link-target-in-source.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,11 @@ +Tag: wayward-symbolic-link-target-in-source +Severity: error +Check: files/symbolic-links +Renamed-From: source-contains-unsafe-symlink +Info: The named symbolic link in a source package resolves outside + the shipped sources. + . + Please note that this tag is only issued for relative links targets. + Absolute link targets are also disqualified because source packages + are not anchored and can be unpacked anywhere. They triggers another + tag. diff -Nru lintian-2.93.0/tags/w/wayward-symbolic-link-target-in-source.tag lintian-2.89.0ubuntu1/tags/w/wayward-symbolic-link-target-in-source.tag --- lintian-2.93.0/tags/w/wayward-symbolic-link-target-in-source.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/w/wayward-symbolic-link-target-in-source.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,11 +0,0 @@ -Tag: wayward-symbolic-link-target-in-source -Severity: error -Check: files/symbolic-links -Renamed-From: source-contains-unsafe-symlink -Explanation: The named symbolic link in a source package resolves outside - the shipped sources. - . - Please note that this tag is only issued for relative links targets. - Absolute link targets are also disqualified because source packages - are not anchored and can be unpacked anywhere. They triggers another - tag. diff -Nru lintian-2.93.0/tags/w/weak-dependency-on-misc-depends.desc lintian-2.89.0ubuntu1/tags/w/weak-dependency-on-misc-depends.desc --- lintian-2.93.0/tags/w/weak-dependency-on-misc-depends.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/w/weak-dependency-on-misc-depends.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: weak-dependency-on-misc-depends +Severity: warning +Certainty: possible +Check: debhelper +Ref: debhelper(7) +Info: The source package declares a weak dependency on ${misc:Depends} in + the given binary package's debian/control entry. A stronger dependency, that + is one that ensures the package's installation, is required so that the + additional commands are available to the maintainer scripts when they are run. diff -Nru lintian-2.93.0/tags/w/weak-dependency-on-misc-depends.tag lintian-2.89.0ubuntu1/tags/w/weak-dependency-on-misc-depends.tag --- lintian-2.93.0/tags/w/weak-dependency-on-misc-depends.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/w/weak-dependency-on-misc-depends.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: weak-dependency-on-misc-depends -Severity: warning -Check: debhelper -See-Also: debhelper(7) -Explanation: The source package declares a weak dependency on ${misc:Depends} in - the given binary package's debian/control entry. A stronger dependency, that - is one that ensures the package's installation, is required so that the - additional commands are available to the maintainer scripts when they are run. diff -Nru lintian-2.93.0/tags/w/weak-library-dev-dependency.desc lintian-2.89.0ubuntu1/tags/w/weak-library-dev-dependency.desc --- lintian-2.93.0/tags/w/weak-library-dev-dependency.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/w/weak-library-dev-dependency.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,22 @@ +Tag: weak-library-dev-dependency +Severity: error +Certainty: possible +Check: debian/control +Ref: policy 8.5 +Info: The given package appears to be a shared library -dev package, but + the dependency on what seems to be a corresponding shared library package + does not force the same package version. To ensure that compiling and + linking works properly, and that the symlinks in the -dev package point + to the correct files in the shared library package, a -dev package should + normally use (= ${binary:Version}) for the dependency on the + shared library package. + . + Sometimes, such as for -dev packages that are architecture-independent to + not break binNMUs or when one doesn't want to force a tight dependency, a + weaker dependency is warranted. Something like (>= + ${source:Upstream-Version}), (<< + ${source:Upstream-Version}+1~), possibly using + ${source:Version} instead, is the right approach. The goal is to + ensure that a new upstream version of the library package doesn't satisfy + the -dev package dependency, since the minor version of the shared + library may have changed, breaking the *.so links. diff -Nru lintian-2.93.0/tags/w/weak-library-dev-dependency.tag lintian-2.89.0ubuntu1/tags/w/weak-library-dev-dependency.tag --- lintian-2.93.0/tags/w/weak-library-dev-dependency.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/w/weak-library-dev-dependency.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,21 +0,0 @@ -Tag: weak-library-dev-dependency -Severity: error -Check: debian/control -See-Also: policy 8.5 -Explanation: The given package appears to be a shared library -dev package, but - the dependency on what seems to be a corresponding shared library package - does not force the same package version. To ensure that compiling and - linking works properly, and that the symlinks in the -dev package point - to the correct files in the shared library package, a -dev package should - normally use (= ${binary:Version}) for the dependency on the - shared library package. - . - Sometimes, such as for -dev packages that are architecture-independent to - not break binNMUs or when one doesn't want to force a tight dependency, a - weaker dependency is warranted. Something like (>= - ${source:Upstream-Version}), (<< - ${source:Upstream-Version}+1~), possibly using - ${source:Version} instead, is the right approach. The goal is to - ensure that a new upstream version of the library package doesn't satisfy - the -dev package dependency, since the minor version of the shared - library may have changed, breaking the *.so links. diff -Nru lintian-2.93.0/tags/w/web-application-depends-on-apache2-data-package.desc lintian-2.89.0ubuntu1/tags/w/web-application-depends-on-apache2-data-package.desc --- lintian-2.93.0/tags/w/web-application-depends-on-apache2-data-package.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/w/web-application-depends-on-apache2-data-package.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: web-application-depends-on-apache2-data-package +Severity: warning +Check: apache2 +Info: The package appears to be a web application but declares a package + relation with apache2-bin, apache2-data or any of its + transitional packages. However, web applications are rarely bound to a specific + web server version. Thus, they should depend on apache2 only instead. + If a web application is actually tied to a particular binary version of the web + server a dependency against the virtual apache2-api-YYYYMMDD package + is more appropriate. diff -Nru lintian-2.93.0/tags/w/web-application-depends-on-apache2-data-package.tag lintian-2.89.0ubuntu1/tags/w/web-application-depends-on-apache2-data-package.tag --- lintian-2.93.0/tags/w/web-application-depends-on-apache2-data-package.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/w/web-application-depends-on-apache2-data-package.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,10 +0,0 @@ -Tag: web-application-depends-on-apache2-data-package -Severity: warning -Check: apache2 -Explanation: The package appears to be a web application but declares a package - relation with apache2-bin, apache2-data or any of its - transitional packages. However, web applications are rarely bound to a specific - web server version. Thus, they should depend on apache2 only instead. - If a web application is actually tied to a particular binary version of the web - server a dependency against the virtual apache2-api-YYYYMMDD package - is more appropriate. diff -Nru lintian-2.93.0/tags/w/web-application-works-only-with-apache.desc lintian-2.89.0ubuntu1/tags/w/web-application-works-only-with-apache.desc --- lintian-2.93.0/tags/w/web-application-works-only-with-apache.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/w/web-application-works-only-with-apache.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: web-application-works-only-with-apache +Severity: warning +Check: apache2 +Renamed-From: web-application-should-not-depend-unconditionally-on-apache2 +Info: The package appears to be a web application but declares a dependency + against apache2 without any alternative. Most web applications should + work with any decent web server, thus such a package should be satisfied if any + web server providing the virtual "httpd" package is installed. This + can be accomplished by declaring a package relation in the form "apache2 | + httpd". diff -Nru lintian-2.93.0/tags/w/web-application-works-only-with-apache.tag lintian-2.89.0ubuntu1/tags/w/web-application-works-only-with-apache.tag --- lintian-2.93.0/tags/w/web-application-works-only-with-apache.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/w/web-application-works-only-with-apache.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,10 +0,0 @@ -Tag: web-application-works-only-with-apache -Severity: warning -Check: apache2 -Renamed-From: web-application-should-not-depend-unconditionally-on-apache2 -Explanation: The package appears to be a web application but declares a dependency - against apache2 without any alternative. Most web applications should - work with any decent web server, thus such a package should be satisfied if any - web server providing the virtual "httpd" package is installed. This - can be accomplished by declaring a package relation in the form "apache2 | - httpd". diff -Nru lintian-2.93.0/tags/w/whitespace-after-continuation-character.desc lintian-2.89.0ubuntu1/tags/w/whitespace-after-continuation-character.desc --- lintian-2.93.0/tags/w/whitespace-after-continuation-character.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/w/whitespace-after-continuation-character.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: whitespace-after-continuation-character +Severity: error +Check: menu-format +Info: The menu item is split up over 2 or more lines using '\' at the end of + the line to join them together. However, there is some whitespace after + the '\' character, which is not guaranteed to be handled correctly. + The '\' should be at the end of the line. diff -Nru lintian-2.93.0/tags/w/whitespace-after-continuation-character.tag lintian-2.89.0ubuntu1/tags/w/whitespace-after-continuation-character.tag --- lintian-2.93.0/tags/w/whitespace-after-continuation-character.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/w/whitespace-after-continuation-character.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: whitespace-after-continuation-character -Severity: error -Check: menu-format -Explanation: The menu item is split up over 2 or more lines using '\' at the end of - the line to join them together. However, there is some whitespace after - the '\' character, which is not guaranteed to be handled correctly. - The '\' should be at the end of the line. diff -Nru lintian-2.93.0/tags/w/wiki-copyright-format-uri.desc lintian-2.89.0ubuntu1/tags/w/wiki-copyright-format-uri.desc --- lintian-2.93.0/tags/w/wiki-copyright-format-uri.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/w/wiki-copyright-format-uri.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: wiki-copyright-format-uri +Severity: pedantic +Certainty: possible +Check: debian/copyright/dep5 +Ref: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ +Info: Format URI of the machine-readable copyright file refers to Debian Wiki. + . + Debian Wiki is not used for the format development anymore. Please use + https://www.debian.org/doc/packaging-manuals/copyright-format/version/ + as the format URI instead. diff -Nru lintian-2.93.0/tags/w/wiki-copyright-format-uri.tag lintian-2.89.0ubuntu1/tags/w/wiki-copyright-format-uri.tag --- lintian-2.93.0/tags/w/wiki-copyright-format-uri.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/w/wiki-copyright-format-uri.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: wiki-copyright-format-uri -Severity: pedantic -Check: debian/copyright/dep5 -See-Also: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ -Explanation: Format URI of the machine-readable copyright file refers to Debian Wiki. - . - Debian Wiki is not used for the format development anymore. Please use - https://www.debian.org/doc/packaging-manuals/copyright-format/*version*/ - as the format URI instead. diff -Nru lintian-2.93.0/tags/w/wildcard-matches-nothing-in-dep5-copyright.desc lintian-2.89.0ubuntu1/tags/w/wildcard-matches-nothing-in-dep5-copyright.desc --- lintian-2.93.0/tags/w/wildcard-matches-nothing-in-dep5-copyright.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/w/wildcard-matches-nothing-in-dep5-copyright.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: wildcard-matches-nothing-in-dep5-copyright +Severity: info +Certainty: possible +Check: debian/copyright/dep5 +Ref: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ +Info: The wildcard that was specified matches no file in the source tree. + This either indicates that you should fix the wildcard so that it matches + the intended file or that you can remove the wildcard. Notice that in + contrast to shell globs, the "*" (star or asterisk) matches slashes and + leading dots. diff -Nru lintian-2.93.0/tags/w/wildcard-matches-nothing-in-dep5-copyright.tag lintian-2.89.0ubuntu1/tags/w/wildcard-matches-nothing-in-dep5-copyright.tag --- lintian-2.93.0/tags/w/wildcard-matches-nothing-in-dep5-copyright.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/w/wildcard-matches-nothing-in-dep5-copyright.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: wildcard-matches-nothing-in-dep5-copyright -Severity: info -Check: debian/copyright/dep5 -See-Also: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ -Explanation: The wildcard that was specified matches no file in the source tree. - This either indicates that you should fix the wildcard so that it matches - the intended file or that you can remove the wildcard. Notice that in - contrast to shell globs, the "*" (star or asterisk) matches slashes and - leading dots. diff -Nru lintian-2.93.0/tags/w/windows-devel-file-in-package.desc lintian-2.89.0ubuntu1/tags/w/windows-devel-file-in-package.desc --- lintian-2.93.0/tags/w/windows-devel-file-in-package.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/w/windows-devel-file-in-package.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: windows-devel-file-in-package +Severity: warning +Certainty: possible +Check: foreign-operating-systems +Info: This package appears to contain development files only meaningful to + Windows environments. Such files are generally useless in Debian packages and + were usually accidentally included by copying complete directories from the + source tarball. diff -Nru lintian-2.93.0/tags/w/windows-devel-file-in-package.tag lintian-2.89.0ubuntu1/tags/w/windows-devel-file-in-package.tag --- lintian-2.93.0/tags/w/windows-devel-file-in-package.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/w/windows-devel-file-in-package.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: windows-devel-file-in-package -Severity: warning -Check: foreign-operating-systems -Explanation: This package appears to contain development files only meaningful to - Windows environments. Such files are generally useless in Debian packages and - were usually accidentally included by copying complete directories from the - source tarball. diff -Nru lintian-2.93.0/tags/w/windows-thumbnail-database-in-package.desc lintian-2.89.0ubuntu1/tags/w/windows-thumbnail-database-in-package.desc --- lintian-2.93.0/tags/w/windows-thumbnail-database-in-package.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/w/windows-thumbnail-database-in-package.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: windows-thumbnail-database-in-package +Severity: warning +Check: foreign-operating-systems +Info: There is a file in the package named Thumbs.db or + Thumbs.db.gz, which is normally a Windows image thumbnail + database. Such databases are generally useless in Debian packages and + were usually accidentally included by copying complete directories from + the source tarball. diff -Nru lintian-2.93.0/tags/w/windows-thumbnail-database-in-package.tag lintian-2.89.0ubuntu1/tags/w/windows-thumbnail-database-in-package.tag --- lintian-2.93.0/tags/w/windows-thumbnail-database-in-package.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/w/windows-thumbnail-database-in-package.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: windows-thumbnail-database-in-package -Severity: warning -Check: foreign-operating-systems -Explanation: There is a file in the package named Thumbs.db or - Thumbs.db.gz, which is normally a Windows image thumbnail - database. Such databases are generally useless in Debian packages and - were usually accidentally included by copying complete directories from - the source tarball. diff -Nru lintian-2.93.0/tags/w/wish-script-but-no-wish-dep.desc lintian-2.89.0ubuntu1/tags/w/wish-script-but-no-wish-dep.desc --- lintian-2.93.0/tags/w/wish-script-but-no-wish-dep.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/w/wish-script-but-no-wish-dep.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: wish-script-but-no-wish-dep +Severity: error +Check: scripts +Info: Packages that include wish scripts must depend on the virtual + package wish or, if they require a specific version of wish or tk, that + version of tk. + . + In some cases a weaker relationship, such as Suggests or Recommends, will + be more appropriate. diff -Nru lintian-2.93.0/tags/w/wish-script-but-no-wish-dep.tag lintian-2.89.0ubuntu1/tags/w/wish-script-but-no-wish-dep.tag --- lintian-2.93.0/tags/w/wish-script-but-no-wish-dep.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/w/wish-script-but-no-wish-dep.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: wish-script-but-no-wish-dep -Severity: error -Check: scripts -Explanation: Packages that include wish scripts must depend on the virtual - package wish or, if they require a specific version of wish or tk, that - version of tk. - . - In some cases a weaker relationship, such as Suggests or Recommends, will - be more appropriate. diff -Nru lintian-2.93.0/tags/w/wrong-bug-number-in-closes.desc lintian-2.89.0ubuntu1/tags/w/wrong-bug-number-in-closes.desc --- lintian-2.93.0/tags/w/wrong-bug-number-in-closes.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/w/wrong-bug-number-in-closes.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,5 @@ +Tag: wrong-bug-number-in-closes +Severity: warning +Check: debian/changelog +Info: Bug numbers can only contain digits. +Ref: policy 4.4 diff -Nru lintian-2.93.0/tags/w/wrong-bug-number-in-closes.tag lintian-2.89.0ubuntu1/tags/w/wrong-bug-number-in-closes.tag --- lintian-2.93.0/tags/w/wrong-bug-number-in-closes.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/w/wrong-bug-number-in-closes.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,5 +0,0 @@ -Tag: wrong-bug-number-in-closes -Severity: warning -Check: debian/changelog -Explanation: Bug numbers can only contain digits. -See-Also: policy 4.4 diff -Nru lintian-2.93.0/tags/w/wrong-compression-in-manual-page.desc lintian-2.89.0ubuntu1/tags/w/wrong-compression-in-manual-page.desc --- lintian-2.93.0/tags/w/wrong-compression-in-manual-page.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/w/wrong-compression-in-manual-page.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: wrong-compression-in-manual-page +Severity: error +Check: documentation/manual +Renamed-From: manpage-not-compressed-with-gzip +Info: Manual pages should be compressed with gzip -9n. +Ref: policy 12.1 diff -Nru lintian-2.93.0/tags/w/wrong-compression-in-manual-page.tag lintian-2.89.0ubuntu1/tags/w/wrong-compression-in-manual-page.tag --- lintian-2.93.0/tags/w/wrong-compression-in-manual-page.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/w/wrong-compression-in-manual-page.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: wrong-compression-in-manual-page -Severity: error -Check: documentation/manual -Renamed-From: manpage-not-compressed-with-gzip -Explanation: Manual pages should be compressed with gzip -9n. -See-Also: policy 12.1 diff -Nru lintian-2.93.0/tags/w/wrong-file-owner-uid-or-gid.desc lintian-2.89.0ubuntu1/tags/w/wrong-file-owner-uid-or-gid.desc --- lintian-2.93.0/tags/w/wrong-file-owner-uid-or-gid.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/w/wrong-file-owner-uid-or-gid.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,14 @@ +Tag: wrong-file-owner-uid-or-gid +Severity: error +Check: files/ownership +Info: The user or group ID of the owner of the file is invalid. The + owner user and group IDs must be in the set of globally allocated + IDs, because other IDs are dynamically allocated and might be used + for varying purposes on different systems, or are reserved. The set + of the allowed, globally allocated IDs consists of the ranges 0-99, + 64000-64999 and 65534. + . + It's possible for a Policy-compliant package to trigger this tag if the + user is created in the preinst maintainer script, but this is a very rare + case and doesn't appear to be necessary. +Ref: policy 9.2 diff -Nru lintian-2.93.0/tags/w/wrong-file-owner-uid-or-gid.tag lintian-2.89.0ubuntu1/tags/w/wrong-file-owner-uid-or-gid.tag --- lintian-2.93.0/tags/w/wrong-file-owner-uid-or-gid.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/w/wrong-file-owner-uid-or-gid.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,14 +0,0 @@ -Tag: wrong-file-owner-uid-or-gid -Severity: error -Check: files/ownership -Explanation: The user or group ID of the owner of the file is invalid. The - owner user and group IDs must be in the set of globally allocated - IDs, because other IDs are dynamically allocated and might be used - for varying purposes on different systems, or are reserved. The set - of the allowed, globally allocated IDs consists of the ranges 0-99, - 64000-64999 and 65534. - . - It's possible for a Policy-compliant package to trigger this tag if the - user is created in the preinst maintainer script, but this is a very rare - case and doesn't appear to be necessary. -See-Also: policy 9.2 diff -Nru lintian-2.93.0/tags/w/wrong-manual-section.desc lintian-2.89.0ubuntu1/tags/w/wrong-manual-section.desc --- lintian-2.93.0/tags/w/wrong-manual-section.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/w/wrong-manual-section.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: wrong-manual-section +Severity: warning +Check: documentation/manual +Renamed-From: manpage-section-mismatch +Info: A manual page usually should contain a .TH header, specifying the + section. The section in this manual page doesn't match with the section in the + filename. +Ref: groff_man(7), man(1) diff -Nru lintian-2.93.0/tags/w/wrong-manual-section.tag lintian-2.89.0ubuntu1/tags/w/wrong-manual-section.tag --- lintian-2.93.0/tags/w/wrong-manual-section.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/w/wrong-manual-section.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ -Tag: wrong-manual-section -Severity: warning -Check: documentation/manual -Renamed-From: manpage-section-mismatch -Explanation: A manual page usually should contain a .TH header, specifying the - section. The section in this manual page doesn't match with the section in the - filename. -See-Also: groff_man(7), man(1) diff -Nru lintian-2.93.0/tags/w/wrong-name-for-changelog-of-native-package.desc lintian-2.89.0ubuntu1/tags/w/wrong-name-for-changelog-of-native-package.desc --- lintian-2.93.0/tags/w/wrong-name-for-changelog-of-native-package.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/w/wrong-name-for-changelog-of-native-package.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: wrong-name-for-changelog-of-native-package +Severity: warning +Check: debian/changelog +Info: The changelog file of a native Debian package (ie. if there is + no upstream source) should usually be installed as + /usr/share/doc/pkg/changelog.gz +Ref: policy 12.7 diff -Nru lintian-2.93.0/tags/w/wrong-name-for-changelog-of-native-package.tag lintian-2.89.0ubuntu1/tags/w/wrong-name-for-changelog-of-native-package.tag --- lintian-2.93.0/tags/w/wrong-name-for-changelog-of-native-package.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/w/wrong-name-for-changelog-of-native-package.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: wrong-name-for-changelog-of-native-package -Severity: warning -Check: debian/changelog -Explanation: The changelog file of a native Debian package (ie. if there is - no upstream source) should usually be installed as - /usr/share/doc/*pkg*/changelog.gz -See-Also: policy 12.7 diff -Nru lintian-2.93.0/tags/w/wrong-name-for-debian-changelog-file.desc lintian-2.89.0ubuntu1/tags/w/wrong-name-for-debian-changelog-file.desc --- lintian-2.93.0/tags/w/wrong-name-for-debian-changelog-file.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/w/wrong-name-for-debian-changelog-file.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: wrong-name-for-debian-changelog-file +Severity: error +Check: debian/changelog +Info: The Debian changelog file should usually be installed as + /usr/share/doc/pkg/changelog.Debian.gz +Ref: policy 12.7 diff -Nru lintian-2.93.0/tags/w/wrong-name-for-debian-changelog-file.tag lintian-2.89.0ubuntu1/tags/w/wrong-name-for-debian-changelog-file.tag --- lintian-2.93.0/tags/w/wrong-name-for-debian-changelog-file.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/w/wrong-name-for-debian-changelog-file.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: wrong-name-for-debian-changelog-file -Severity: error -Check: debian/changelog -Explanation: The Debian changelog file should usually be installed as - /usr/share/doc/*pkg*/changelog.Debian.gz -See-Also: policy 12.7 diff -Nru lintian-2.93.0/tags/w/wrong-name-for-debian-news-file.desc lintian-2.89.0ubuntu1/tags/w/wrong-name-for-debian-news-file.desc --- lintian-2.93.0/tags/w/wrong-name-for-debian-news-file.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/w/wrong-name-for-debian-news-file.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,8 @@ +Tag: wrong-name-for-debian-news-file +Severity: warning +Certainty: possible +Check: debian/changelog +Info: The Debian news file must be installed as + /usr/share/doc/pkg/NEWS.Debian.gz with exactly that capitalization + or automated tools may not find it correctly. +Ref: devref 6.3.4 diff -Nru lintian-2.93.0/tags/w/wrong-name-for-debian-news-file.tag lintian-2.89.0ubuntu1/tags/w/wrong-name-for-debian-news-file.tag --- lintian-2.93.0/tags/w/wrong-name-for-debian-news-file.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/w/wrong-name-for-debian-news-file.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: wrong-name-for-debian-news-file -Severity: warning -Check: debian/changelog -Explanation: The Debian news file must be installed as - /usr/share/doc/*pkg*/NEWS.Debian.gz with exactly that capitalization - or automated tools may not find it correctly. -See-Also: devref 6.3.4 diff -Nru lintian-2.93.0/tags/w/wrong-name-for-manual-page.desc lintian-2.89.0ubuntu1/tags/w/wrong-name-for-manual-page.desc --- lintian-2.93.0/tags/w/wrong-name-for-manual-page.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/w/wrong-name-for-manual-page.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: wrong-name-for-manual-page +Severity: error +Check: documentation/manual +Renamed-From: manpage-has-wrong-extension +Info: The manual page has an extension other than + "section[program].gz". +Ref: policy 12.1 diff -Nru lintian-2.93.0/tags/w/wrong-name-for-manual-page.tag lintian-2.89.0ubuntu1/tags/w/wrong-name-for-manual-page.tag --- lintian-2.93.0/tags/w/wrong-name-for-manual-page.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/w/wrong-name-for-manual-page.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: wrong-name-for-manual-page -Severity: error -Check: documentation/manual -Renamed-From: manpage-has-wrong-extension -Explanation: The manual page has an extension other than - "*section*[*program*].gz". -See-Also: policy 12.1 diff -Nru lintian-2.93.0/tags/w/wrong-name-for-upstream-changelog.desc lintian-2.89.0ubuntu1/tags/w/wrong-name-for-upstream-changelog.desc --- lintian-2.93.0/tags/w/wrong-name-for-upstream-changelog.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/w/wrong-name-for-upstream-changelog.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: wrong-name-for-upstream-changelog +Severity: warning +Certainty: possible +Check: debian/changelog +Info: If there is an upstream changelog file, it should usually be + installed as /usr/share/doc/pkg/changelog.gz +Ref: policy 12.7 diff -Nru lintian-2.93.0/tags/w/wrong-name-for-upstream-changelog.tag lintian-2.89.0ubuntu1/tags/w/wrong-name-for-upstream-changelog.tag --- lintian-2.93.0/tags/w/wrong-name-for-upstream-changelog.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/w/wrong-name-for-upstream-changelog.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -Tag: wrong-name-for-upstream-changelog -Severity: warning -Check: debian/changelog -Explanation: If there is an upstream changelog file, it should usually be - installed as /usr/share/doc/*pkg*/changelog.gz -See-Also: policy 12.7 diff -Nru lintian-2.93.0/tags/w/wrong-path-for-interpreter.desc lintian-2.89.0ubuntu1/tags/w/wrong-path-for-interpreter.desc --- lintian-2.93.0/tags/w/wrong-path-for-interpreter.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/w/wrong-path-for-interpreter.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: wrong-path-for-interpreter +Severity: error +Check: scripts +Info: The interpreter you used is installed at another location on Debian + systems. + . + Note that, as a particular exception, Debian Policy § 10.4 states that + Perl scripts should use /usr/bin/perl directly and not + /usr/bin/env, etc. +Ref: policy 10.4 diff -Nru lintian-2.93.0/tags/w/wrong-path-for-interpreter.tag lintian-2.89.0ubuntu1/tags/w/wrong-path-for-interpreter.tag --- lintian-2.93.0/tags/w/wrong-path-for-interpreter.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/w/wrong-path-for-interpreter.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,10 +0,0 @@ -Tag: wrong-path-for-interpreter -Severity: error -Check: scripts -Explanation: The interpreter you used is installed at another location on Debian - systems. - . - Note that, as a particular exception, Debian Policy § 10.4 states that - Perl scripts should use /usr/bin/perl directly and not - /usr/bin/env, etc. -See-Also: policy 10.4 diff -Nru lintian-2.93.0/tags/w/wrong-section-according-to-package-name.desc lintian-2.89.0ubuntu1/tags/w/wrong-section-according-to-package-name.desc --- lintian-2.93.0/tags/w/wrong-section-according-to-package-name.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/w/wrong-section-according-to-package-name.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,6 @@ +Tag: wrong-section-according-to-package-name +Severity: info +Certainty: possible +Check: fields/section +Info: This package has a name suggesting that it belongs to a section + other than the one it is currently categorized in. diff -Nru lintian-2.93.0/tags/w/wrong-section-according-to-package-name.tag lintian-2.89.0ubuntu1/tags/w/wrong-section-according-to-package-name.tag --- lintian-2.93.0/tags/w/wrong-section-according-to-package-name.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/w/wrong-section-according-to-package-name.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,5 +0,0 @@ -Tag: wrong-section-according-to-package-name -Severity: info -Check: fields/section -Explanation: This package has a name suggesting that it belongs to a section - other than the one it is currently categorized in. diff -Nru lintian-2.93.0/tags/w/wrong-section-for-udeb.desc lintian-2.89.0ubuntu1/tags/w/wrong-section-for-udeb.desc --- lintian-2.93.0/tags/w/wrong-section-for-udeb.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/w/wrong-section-for-udeb.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,4 @@ +Tag: wrong-section-for-udeb +Severity: warning +Check: fields/section +Info: udeb packages should have "Section: debian-installer". diff -Nru lintian-2.93.0/tags/w/wrong-section-for-udeb.tag lintian-2.89.0ubuntu1/tags/w/wrong-section-for-udeb.tag --- lintian-2.93.0/tags/w/wrong-section-for-udeb.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/w/wrong-section-for-udeb.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,4 +0,0 @@ -Tag: wrong-section-for-udeb -Severity: warning -Check: fields/section -Explanation: udeb packages should have "Section: debian-installer". diff -Nru lintian-2.93.0/tags/w/wrong-vcs-location-for-dpmt.desc lintian-2.89.0ubuntu1/tags/w/wrong-vcs-location-for-dpmt.desc --- lintian-2.93.0/tags/w/wrong-vcs-location-for-dpmt.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/w/wrong-vcs-location-for-dpmt.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: wrong-vcs-location-for-dpmt +Severity: error +Ref: DPMT policy +Check: fields/vcs +Info: This package is maintained within the Debian Python Modules Team (DPMT) + and as such, its VCS should live in Salsa under + https://salsa.debian.org/python-team/modules/. + . + This is not currently the case and the package's VCS should be migrated to the + proper location. diff -Nru lintian-2.93.0/tags/w/wrong-vcs-location-for-dpmt.tag lintian-2.89.0ubuntu1/tags/w/wrong-vcs-location-for-dpmt.tag --- lintian-2.93.0/tags/w/wrong-vcs-location-for-dpmt.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/w/wrong-vcs-location-for-dpmt.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,10 +0,0 @@ -Tag: wrong-vcs-location-for-dpmt -Severity: error -See-Also: DPMT policy -Check: fields/vcs -Explanation: This package is maintained within the Debian Python Modules Team (DPMT) - and as such, its VCS should live in Salsa under - https://salsa.debian.org/python-team/modules/. - . - This is not currently the case and the package's VCS should be migrated to the - proper location. diff -Nru lintian-2.93.0/tags/w/wrong-vcs-location-for-papt.desc lintian-2.89.0ubuntu1/tags/w/wrong-vcs-location-for-papt.desc --- lintian-2.93.0/tags/w/wrong-vcs-location-for-papt.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/w/wrong-vcs-location-for-papt.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: wrong-vcs-location-for-papt +Severity: error +Ref: PAPT policy +Check: fields/vcs +Info: This package is maintained within the Python Applications Packaging Team + (PAPT) and as such, its VCS should live in Salsa under + https://salsa.debian.org/python-team/applications/. + . + This is not currently the case and the package's VCS should be migrated to the + proper location. diff -Nru lintian-2.93.0/tags/w/wrong-vcs-location-for-papt.tag lintian-2.89.0ubuntu1/tags/w/wrong-vcs-location-for-papt.tag --- lintian-2.93.0/tags/w/wrong-vcs-location-for-papt.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/w/wrong-vcs-location-for-papt.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,10 +0,0 @@ -Tag: wrong-vcs-location-for-papt -Severity: error -See-Also: PAPT policy -Check: fields/vcs -Explanation: This package is maintained within the Python Applications Packaging Team - (PAPT) and as such, its VCS should live in Salsa under - https://salsa.debian.org/python-team/applications/. - . - This is not currently the case and the package's VCS should be migrated to the - proper location. diff -Nru lintian-2.93.0/tags/x/xc-package-type-in-debian-control.desc lintian-2.89.0ubuntu1/tags/x/xc-package-type-in-debian-control.desc --- lintian-2.93.0/tags/x/xc-package-type-in-debian-control.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/x/xc-package-type-in-debian-control.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: xc-package-type-in-debian-control +Severity: pedantic +Check: debian/control +Info: The debian/control file contains an XC-Package-Type field. + As of dpkg-dev 1.15.7, the dpkg development utilities recognize + Package-Type as an official field name and do not add it to binary + packages (the previous concern with the dpkg-dev-supported Package-Type + field). XC-Package-Type should generally now be replaced with + Package-Type. diff -Nru lintian-2.93.0/tags/x/xc-package-type-in-debian-control.tag lintian-2.89.0ubuntu1/tags/x/xc-package-type-in-debian-control.tag --- lintian-2.93.0/tags/x/xc-package-type-in-debian-control.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/x/xc-package-type-in-debian-control.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: xc-package-type-in-debian-control -Severity: pedantic -Check: debian/control -Explanation: The debian/control file contains an XC-Package-Type field. - As of dpkg-dev 1.15.7, the dpkg development utilities recognize - Package-Type as an official field name and do not add it to binary - packages (the previous concern with the dpkg-dev-supported Package-Type - field). XC-Package-Type should generally now be replaced with - Package-Type. diff -Nru lintian-2.93.0/tags/x/xs-testsuite-field-in-debian-control.desc lintian-2.89.0ubuntu1/tags/x/xs-testsuite-field-in-debian-control.desc --- lintian-2.93.0/tags/x/xs-testsuite-field-in-debian-control.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/x/xs-testsuite-field-in-debian-control.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,10 @@ +Tag: xs-testsuite-field-in-debian-control +Severity: info +Check: debian/control +Info: There is an XS-Testsuite field in the debian/control file. As + of dpkg 1.17.10, the XS- prefix is no longer necessary. dpkg now + recognizes this field and handles it correctly. As of dpkg 1.17.11 the + field is automatically added by dpkg-source with the value "autopkgtest" if + there is a non-empty debian/tests/control file present. Consider + either removing the XS- prefix for this field or removing the field + altogether if it contains just the "autopkgtest" value. diff -Nru lintian-2.93.0/tags/x/xs-testsuite-field-in-debian-control.tag lintian-2.89.0ubuntu1/tags/x/xs-testsuite-field-in-debian-control.tag --- lintian-2.93.0/tags/x/xs-testsuite-field-in-debian-control.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/x/xs-testsuite-field-in-debian-control.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,10 +0,0 @@ -Tag: xs-testsuite-field-in-debian-control -Severity: info -Check: debian/control -Explanation: There is an XS-Testsuite field in the debian/control file. As - of dpkg 1.17.10, the XS- prefix is no longer necessary. dpkg now - recognizes this field and handles it correctly. As of dpkg 1.17.11 the - field is automatically added by dpkg-source with the value "autopkgtest" if - there is a non-empty debian/tests/control file present. Consider - either removing the XS- prefix for this field or removing the field - altogether if it contains just the "autopkgtest" value. diff -Nru lintian-2.93.0/tags/x/xs-vcs-field-in-debian-control.desc lintian-2.89.0ubuntu1/tags/x/xs-vcs-field-in-debian-control.desc --- lintian-2.93.0/tags/x/xs-vcs-field-in-debian-control.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/x/xs-vcs-field-in-debian-control.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,7 @@ +Tag: xs-vcs-field-in-debian-control +Severity: info +Check: debian/control +Info: There is an XS-Vcs-* field in the debian/control file. As + of dpkg 1.14.6, the XS- prefix is no longer necessary. dpkg now + recognizes these fields and handles them correctly. Consider removing + the XS- prefix for this field. diff -Nru lintian-2.93.0/tags/x/xs-vcs-field-in-debian-control.tag lintian-2.89.0ubuntu1/tags/x/xs-vcs-field-in-debian-control.tag --- lintian-2.93.0/tags/x/xs-vcs-field-in-debian-control.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/x/xs-vcs-field-in-debian-control.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -Tag: xs-vcs-field-in-debian-control -Severity: info -Check: debian/control -Explanation: There is an XS-Vcs-* field in the debian/control file. As - of dpkg 1.14.6, the XS- prefix is no longer necessary. dpkg now - recognizes these fields and handles them correctly. Consider removing - the XS- prefix for this field. diff -Nru lintian-2.93.0/tags/z/zero-byte-executable-in-path.desc lintian-2.89.0ubuntu1/tags/z/zero-byte-executable-in-path.desc --- lintian-2.93.0/tags/z/zero-byte-executable-in-path.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/z/zero-byte-executable-in-path.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,9 @@ +Tag: zero-byte-executable-in-path +Severity: error +Check: files/names +Info: This package installs the specified empty executable file to the + system's PATH. These files do not do anything and produce no error + message when run. + . + This was likely caused by an error in the package build process. +Ref: #919341 diff -Nru lintian-2.93.0/tags/z/zero-byte-executable-in-path.tag lintian-2.89.0ubuntu1/tags/z/zero-byte-executable-in-path.tag --- lintian-2.93.0/tags/z/zero-byte-executable-in-path.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/z/zero-byte-executable-in-path.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Tag: zero-byte-executable-in-path -Severity: error -Check: files/names -Explanation: This package installs the specified empty executable file to the - system's PATH. These files do not do anything and produce no error - message when run. - . - This was likely caused by an error in the package build process. -See-Also: Bug#919341 diff -Nru lintian-2.93.0/tags/z/zero-byte-file-in-doc-directory.desc lintian-2.89.0ubuntu1/tags/z/zero-byte-file-in-doc-directory.desc --- lintian-2.93.0/tags/z/zero-byte-file-in-doc-directory.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/z/zero-byte-file-in-doc-directory.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,12 @@ +Tag: zero-byte-file-in-doc-directory +Severity: warning +Certainty: possible +Check: documentation +Info: The documentation directory for this package contains an empty + file. This is often due to installing an upstream NEWS or README file + without realizing it's empty and hence not useful. + . + Files in the examples subdirectory are excluded from this check, but + there are some cases where empty files are legitimate parts of the + documentation without being examples. In those cases, please add an + override. diff -Nru lintian-2.93.0/tags/z/zero-byte-file-in-doc-directory.tag lintian-2.89.0ubuntu1/tags/z/zero-byte-file-in-doc-directory.tag --- lintian-2.93.0/tags/z/zero-byte-file-in-doc-directory.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/z/zero-byte-file-in-doc-directory.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,11 +0,0 @@ -Tag: zero-byte-file-in-doc-directory -Severity: warning -Check: documentation -Explanation: The documentation directory for this package contains an empty - file. This is often due to installing an upstream NEWS or README file - without realizing it's empty and hence not useful. - . - Files in the examples subdirectory are excluded from this check, but - there are some cases where empty files are legitimate parts of the - documentation without being examples. In those cases, please add an - override. diff -Nru lintian-2.93.0/tags/z/zip-parse-error.desc lintian-2.89.0ubuntu1/tags/z/zip-parse-error.desc --- lintian-2.93.0/tags/z/zip-parse-error.desc 1970-01-01 00:00:00.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/z/zip-parse-error.desc 2020-08-10 09:59:45.000000000 +0000 @@ -0,0 +1,5 @@ +Tag: zip-parse-error +Severity: warning +Check: languages/java +Info: The package contains a Jar file, but Lintian is unable to parse it. + It is possible that the Jar file is corrupt. diff -Nru lintian-2.93.0/tags/z/zip-parse-error.tag lintian-2.89.0ubuntu1/tags/z/zip-parse-error.tag --- lintian-2.93.0/tags/z/zip-parse-error.tag 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/tags/z/zip-parse-error.tag 1970-01-01 00:00:00.000000000 +0000 @@ -1,5 +0,0 @@ -Tag: zip-parse-error -Severity: warning -Check: languages/java -Explanation: The package contains a Jar file, but Lintian is unable to parse it. - It is possible that the Jar file is corrupt. diff -Nru lintian-2.93.0/vendors/ubuntu/main/data/changes-file/known-dists lintian-2.89.0ubuntu1/vendors/ubuntu/main/data/changes-file/known-dists --- lintian-2.93.0/vendors/ubuntu/main/data/changes-file/known-dists 2020-09-03 21:54:58.000000000 +0000 +++ lintian-2.89.0ubuntu1/vendors/ubuntu/main/data/changes-file/known-dists 2021-05-13 21:58:34.000000000 +0000 @@ -28,3 +28,5 @@ eoan focal groovy +hirsute +impish