Ignore false positives for localized POD files generated by po4a.

Fixes: commit affb86e4

Use the long version to make the option obvious, as there is no need for
succinctness in scripts, and no portability concerns.

This makes this target available on any directory that contains TAP
tests, and not just the source-tree root.

Add an authorcheck make target. Switch all usages and documentation to
use the new target. Remove DPKG_DEVEL_MODE environment variable support,
and replace with AUTHOR_TESTING where appropriate. Update the usage
documentation.

Do this for both the source tree, and for the installation directory,
to make it clear that these are specifications instead of random
documents.

Give the file a more meaningful name, as frontend.txt is not very clear
on what its purpose is.

Having so much perl logic in an automake file is cumbersome. Use a
proper program to implement this.

The dist-cpan target includes OpenPGP signing the CPAN distribution,
which is problematic on a chroot. It is also not generally helpful,
as we mostly care about generating the CPAN distribution for the latest
releases.

The multicd name does not properly describe what this method is supposed
to be able to handle, as we now have many other media types where
distributions can ship their packages and updates on.

Changelog: silent
Fixes: commit 6a7bfcde

This lists the *.la files that we are not installing.

Rename the TAP automake support file to tap.am to make it explicit this
is just one of the possible test suites we are running. Move from
implicitly hooking into the autotools check machinery to explicitly
hooking into it, so that we can run different test suites from the same
directory.

These are all functional tests for the now unified contents under src/.

- Move dpkg-deb and dpkg-split under src/ as these are part of the dpkg
  toolset.
- Move common source files under src/common/.
- Move program specific source files under subdirectories in src/.
- Rename the various *cmd.c into <tool>/main.c.
- Set automake option subdir-objects.

This unclutters the source tree, and moves the files where they belong
in normal autotools build systems.

This means we can add a trailing «\» to every element, so that they
can be removed without requiring modification of other lines, and can
be easily sorted.

Replace the old usage of $(nil) which could possibly end up with junk
added if such variable is ever defined, in the environment.

Fixes: commit 270ccd99
Changelog: silent

Pass -r and HEAD.

Fixes: commit 6c6efa41
Changelog: silent

We generate dist tarballs with automake, which tells tar to dereference
symlinks. Check whether there is any symlink in the repository that will
degrade to a file and abort the tarball dist generation.

We ignore origins/default as even as a regular file, it works fine, and
it's less trouble to maintain for now.

Use the new shared implementation refactored out from the daily cron
job. And disable the cron daily job when systemd is running.

Closes: #985444

We add two tests, one for normal user and directory root operation, and
another one for unprivileged and DPKG_ROOT operation.

Remove COPYING, already present in the root directory. Remove feature
checks as we can assume all current features are enabled.

This tool will assist in preparing the debian/changelog out of the
git log, by using the specially formatted commit messages and meta
fields.

This field is intended to make it possible to move several of the
current packages marked as Essential, so that they can be removed on
installations where these do not make sense being installed.

Protected packages have some of the properties of Essential, but not
all. These are intended to be used mostly for packages that are involved
in booting the system.

These are supposed to be installed, as some of them are referenced from
the man pages. Update those references to use the new standardized paths.

The name by itself is not very self-descriptive, which can be confusing.

There is no need to duplicate these in all dpkg suite packages.

Fixes: commit 4158d222

This makes it possible to bootstrap an installation w/o requiring
external knowledge of the dpkg internals, as the databases will be
created on write when necessary. We can then remove the code setting
them up from the dpkg postinst.

Closes: #647911

Ref: #930788
Spotted-by: Sven Joachim <svenjoac@gmx.de>

This makes it possible to publish these files so that other dpkg-related
projects can use them, instead of either embedding copies, or
duplicating the macros.

This makes it possible to disable tags that are Debian specific, such as
the controversial tag emitted for vendor-specific patch series files.

Systems deployed with that method bypass the package manager and its
understanding of the filesystem, create aliasing problems, and break
all kinds of expectations for any program that uses pathnames as key
into their database, such as u-a.

These fields have been there mostly to showcase their usage, which
should instead be dynamically added at build-time, and as a reminder
that this should be done.

But there is already a bug filed as a reminder (see #511160), they
are also now documented in the deb-src-control(5) man page, they are
actually wrong in many cases when present on a downstream, and they
generate nagging lintian warnings to boot.

This will execute the functional test suite on the installed system
programs.