Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
The format is very simple, and a simple hand-written parser is smaller
and avoids a build dependency.
The reduction in the generated artifacts is non-insignificant. On
linux-amd64 it's an overall reduction of 30KiB on stripped binaries.
|
|
Avoid libkvm-dev to make sure we always use the low-level sysctl(3)
interface.
|
|
This covers docs, code comments and packaging, which includes the dpkg git
repository, copyright format URL and examples in man pages among others.
|
|
Although these are really not needed, as they are available already from
Debian stable, it makes it obvious for people who might want to backport
dpkg to older suites or distributions.
Warned-by; lintian
|
|
This allows building the package without running the test suite, and
not requiring build dependencies specific to the test suite. Which
makes it easier to bootstrap an architecture.
Prompted-by: Helmut Grohne <helmut@subdivi.de>
|
|
|
|
The new module is in the perl core distribution, which reduces the build
and run-time dependencies, helping with architecture bootstrapping.
Prompted-by: Helmut Grohne <helmut@subdivi.de>
|
|
Expose only the functions that are stable and public, the reset should
be considered private for now.
|
|
|
|
|
|
|
|
|
|
This allows us to use the new --add-location option with the file
argument, which will remove a huge amount diff noise on source code
changes, while still retaining the useful origin of the string.
|
|
Switch the conditional loading of the abitable to expect it to always
exist, and bump libdpkg-perl depends on dpkg to 1.16.3, the version
introducing the file.
This will allow some refactoring.
|
|
There are two groups of packages, ones where the old version of the
packages produced trigger cycles as they were using awaiting trigger
directives, but are fixed now, which get a << versioned Breaks on the
fixed version. And packages that are still not fixed that get a <=
versioned Breaks on the broken version.
|
|
The old versions of these packages produced trigger cycles as they
were using awaiting trigger directives.
Closes: #768599
|
|
This guarantees that we get a reproducible behavior, as previous patch
versions did not support git-style diffs.
|
|
Due to the new dpkg-architecture command-line parsing strictness
introduced in 1.17.17.
Closes: #764965
|
|
|
|
|
|
|
|
|
|
Use libkvm instead of relying on linprocfs, which is not the native
procfs on kFreeBSD, and it is usually not mounted as FreeBSD programs
do not expect it to be present.
This stops making the code handle GNU/kFreeBSD as if it was a
Linux-based system.
|
|
|
|
Switch more URLs, now that these services have had SSL enabled.
|
|
This spurious space is unnecessary and takes a non-insignificant amount
of disk space on archive index files for example.
Update dpkg-dev Breaks on devscripts to version << 2.14.4, as previous
versions of debchange expect a trailing space from dpkg-parsechangelog
output.
Closes: #749044
Based-on-patch-by: Johannes Schauer <j.schauer@email.de>
|
|
prerm
These packages have been removed after they were released with lenny
or squeeze, but they may survive dist-upgrades to wheezy and jessie.
Since their prerm uses install-info they cannot be removed any longer
after installing dpkg 1.17.x and there is no upgrade path to a fixed
package version. So use Conflicts, because these packages need to be
removed (with their prerm) before a dpkg that would disallow to
subsequently remove them is upgraded. Breaks would only at most
request to deconfigure them.
All Conflicts have the form PACKAGE (<< VERSION). If the source package
still exists, the VERSION that dropped the problematic PACKAGE was used.
Otherwise the next possible maintainer upload VERSION that could
reintroduce PACKAGE into sid was used.
[guillem@debian.org:
- Replace Breaks with Conflicts.
- Update lintian-overrides. ]
Closes: #735159
Signed-off-by: Guillem Jover <guillem@debian.org>
|
|
|
|
|
|
Add gnupg2 and gpgv2 as alternative Recommends to gnupg and gpgv (to
not pull them by default, as that would change the current default
build environment pulled in by dpkg-dev), but prefer gpgv2 over gpgv,
and gpg2 over gpg at run-time if they are available, so that users
installing the alternatives can benefit from the new implementations.
|
|
The package does not ship the overlapping paths any more.
|
|
Closes: #717983
Reported-by: Andreas Beckmann <anbe@debian.org>
|
|
Let's not confuse possible users of what they might be able to use.
|
|
Reported-by: Alessio Gaeta <alga777@gmail.com>
|
|
The dpkg implementation was replaced by the GNU texinfo implementation
some time ago, through a wrapper used to ease the transition. Now long
complete, it's time to clean up.
|
|
|
|
|
|
|
|
|
|
Use liblzma if available instead of external commands to handle .xz
and .lzma compressed files.
Among other things, this means the xz-utils package no longer has to
be part of the base system.
Based-on-patch-by: Jonathan Nieder <jrnieder@gmail.com>
Signed-off-by: Guillem Jover <guillem@debian.org>
|
|
Fallback to use flock based locking, because libfile-fcntllock-perl
being an XS module makes building a new perl package bumping the perl
ABI impossible, as both packages become uninstallable.
Closes: #675947
Based-on-patch-by: Dominic Hargreaves <dom@earth.li>
|
|
Move libfile-fcntllock-perl dependency from dpkg-dev to libdpkg-perl.
|
|
Do not add it as a hard dependency, as the library can be used on system
where a compiler is really not appropriate.
Closes: #671198
|
|
|
|
Closes: #648217
Signed-off-by: Guillem Jover <guillem@debian.org>
|
|
Reported-by: Steve Langasek <vorlon@debian.org>
|
|
The lock is taken on debian/control as this is a file that we know to
always exist. Without this lock, it's possible that the file is updated
concurrently by two processes when parallel building is enabled (leading
to one of them failing unexpectedly).
Reported-by: James Vega <jamessan@debian.org>
|
|
That's the tar version introducing the ‘--warning=no-timestamp’ option,
which dpkg started to use due to #640298. The version is satisfied in
stable, but making the dependency explicit is useful for systems
upgrading from oldstable directly to testing (or next stable), even if
that's not generally supported.
Closes: #642802
|
|
The po4a --srcdir and --destdir options were introduced in version
0.36.4, but attempts to point --srcdir to a different directory than the
cwd when running po4a produced the message “master file was not found”
instead of doing something useful until version 0.41 (r2317, 2010-11-03).
Signed-off-by: Jonathan Nieder <jrnieder@gmail.com>
Signed-off-by: Guillem Jover <guillem@debian.org>
|