Age | Commit message (Collapse) | Author | Files | Lines |
|
The GNU gettext macros used to check for symbols that were only provided
by the GNU gettext implementation, but not by other implementations such
as the one in musl.
Starting with GNU gettext 0.19.8 these internal symbols are not required
anymore.
|
|
|
|
These contain files that are not currently skept, and might contain
spelling errors from external sources.
Warned-by: codespell
|
|
Warned-by: codespell
|
|
The output on log files must not be localized.
Reported-by: Julien Cristau <jcristau@debian.org>
|
|
In some contexts we need output in the C locale, such as log files.
We add a new versiondescribe_c() that wraps the locale-dependant
versiondescribe() function and switches to the C locale and back
to the previous one before returning.
|
|
This will make it possible to select either the current locale or a
specified one, currently only C is selectable.
We use this because the uselocale(3) POSIX API is recent, and the system
might not have it available, so we might need to fallback to use
setlocale(3) instead, which even though is not thread-safe, it's better
than nothing.
|
|
|
|
Closes: #934980
|
|
This was part of the volatile.debian.org archive, which was
decommissioned some time ago.
Ref: https://lists.debian.org/debian-volatile-announce/2012/msg00000.html
|
|
We only use this variable as a sentinel pointer so that we can make
sure the pdep pointer is not NULL in subsequent checks. But cppcheck
gets confused, so let's initialize it to make the code more
future-proof.
Warned-by: cppcheck
|
|
Warned-by: cppcheck
|
|
The variable was being assigned in one side of an if branch, but the
result never used. Let's reduce the scope to the if branch that actually
assigns and uses it.
Warned-by: cppcheck
|
|
The variable was written to but never used.
Warned-by: cppcheck
|
|
This is more future proof, and in this particular case it was tripping
over cppcheck and emitting a false positive for constArgument.
Warned-by: cppcheck
|
|
This is actually due to our local va_copy() compatibility code, which
cppcheck does not understand. Using the same code w/o the local macro
does not emit the false positive.
|
|
This bogus test has been removed from upstream perlcritic, and now the
code complains about an uninstalled check.
Warned-by: perlcritic
|
|
Reported-by: Felix Lechner <felix.lechner@lease-up.com>
|
|
The previous default patch header does not make sense for a conglomerate
patch. Instead provide a more suitable default, that can always be
overridden with either the local-patch-header or patch-header files.
Closes: #933152
|
|
This makes it possible to unset variables, so that they do not get
output by the various tools.
Requested-by: Daniel Schepler <dschepler@gmail.com>
|
|
|
|
Explain what each different pattern means, and what it maps to.
Prompted-by: Christopher Crim <christopher.crim@quoininc.com>
|
|
|
|
|
|
Print the PID of the lock contender, switch the tense to past as the lock
might not be locked anymore by the time we finish, and add a warning
explaining that removing the lock file is never the correct solution.
|
|
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.
|
|
aclocal uses this to determine whether it needs to update m4 files in
local trees.
|
|
When we are building the source package, while detecting whether there
is any original upstream tarball signature to be included in the .dsc,
it's the best time to verify them, so that when the .dsc gets eventually
signed there's a certification path for the maintainer that they are
including what they expected to be there.
|
|
This is needed, for example, to verify original tarball signatures.
|
|
This is required to be able to verify original upstream tarball
signatures, as they are expected to be ASCII armored detached
signatures for the upstream tarballs.
|
|
|
|
We use cp() in Dpkg::Source::Package to preserve the file attributes,
but just move() in dpkg-buildpackage where it does not matter.
|
|
|
|
The current default in Debian and anywhere else is to use unversioned
GnuPG 2.x binaries, so there's no need anymore to try these first or at
all.
|
|
This makes it possible to specify more than one package, which might be
needed during transition periods for example.
Closes: #926669
Based-on-patch-by: Frank Schaefer <kelledin@gmail.com>
|
|
We should not clear the selections for packages that are not already
installed in the system, as they will end up disappearing on the next
operation anyway.
Closes: #927752
|
|
This change is the companion to the one in dpkg-genchanges that lists
only relevant packages, instead of all the ones listed in debian/control,
but for the .buildinfo file instead of the .changes file.
|
|
|
|
Warned-by: codespell
|
|
This code got deprecated before the spec had been finalized, but left in
just to make sure no remaining implementations were still using it.
|
|
This got introduced after a request so that we could switch our tools
to a safe subset of the bundling logic, so let's enable it now that it
is available in the minimum supported perl version.
Bundling is in general unsafe, and not future-proof, as new options
might gain arguments which would then get misinterpreted, we should
not really be using it. But bundling the value into the option is a
common pattern and should be allowed.
|
|
The Perl version in Debian stretch is 5.24.1, which is the release that
will be oldstable once 1.20.x gets uploaded to Debian unstable.
|
|
This file contains information only valid as long as the downloaded
sources are also available. So it is closer to a cache than a database,
and as such, there is no need for an uncompressed backup, which can
take quite some space.
Closes: #343578
|
|
|
|
Update to 2998t.
Improvements from debian-l10n-german
|
|
|
|
|
|
|
|
Closes: #926665
Signed-off-by: Guillem Jover <guillem@debian.org>
|
|
Closes: #929664
Signed-off-by: Guillem Jover <guillem@debian.org>
|