Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
|
|
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>
|
|
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
|
|
And in follow up on debian-l10n-german
|
|
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>
|
|
|
|
Warned-by: codespell
|
|
|
|
Warned-by: lintian
|
|
Closes: #924776, #924777
Signed-off-by: Guillem Jover <guillem@debian.org>
|
|
Update to 2997t1f.
|
|
Using -sA by default means the user might lose data on overwrite if
there is already a directory with the same name laying around.
Closes: #910737
|
|
This makes it possible to disable tags that are Debian specific, such as
the controversial tag emitted for vendor-specific patch series files.
|
|
Update to 2996t1f.
|
|
|
|
Update to 2994t2f1u.
|
|
|
|
Closes: #921942, #921943
Signed-off-by: Guillem Jover <guillem@debian.org>
|
|
[guillem@debian.org:
- Fix markup errors.
- Mark broken translation as fuzzy. ]
Closes: #920905
Signed-off-by: Guillem Jover <guillem@debian.org>
|
|
These will detect problematic files under /usr/local which can taint
the current build.
|
|
This will detect whether the system we are building on contains the
problematic /usr merged via symlinks deployment method.
Suggested-by: Alexander E. Patrakov <patrakov@gmail.com>
|
|
This field will contain a list of tainting reason tags, which can denote
that the current build has potentially been broken.
Suggested-by: Alexander E. Patrakov <patrakov@gmail.com>
|
|
Closes: #922407
|
|
This new option works in both dpkg and dpkg-statoverride. And dpkg will
pass it to its children, which means dpkg-statoverride called from a
maintainer script will automatically pick it up.
Ref: #811037
|
|
Deprecate --force option which will be considered an alias for
--force-all for now.
|
|
|
|
This will make it possible for third-party tools, and also for other
dpkg tools to have access to the force options specified for dpkg.
Closes: #666147
|
|
Describe what to expect from these new checks.
Closes: #921557
|
|
Update to 2970t1f.
|
|
|
|
Closes: #912023, #912024
Signed-off-by: Guillem Jover <guillem@debian.org>
|
|
This will make it possible to access the filesystem entries per package
from anything that queries the database, such as «dpkg-query --show».
|
|
The code was there but commented out. Let's add proper support for
debugging output, controllable at run-time.
|
|
These implement the systemd readiness protocol for services. So that
a service can tell s-s-d when it's ready and then we can return and
callers can assume safely that the service is ready to work.
[biebl@debian.org:
- Fix some typos. ]
[trek00@inbox.ru:
- Fix notification directory and socket permissions. ]
Closes: #910707
|
|
The .changes file describes an upload, and its Binary and Description
fields should contain (as documented) only references to the packages
being uploaded.
In case of a source-only upload, the Binary and Description fields
should be empty.
Closes: #818618
|
|
Filtering this meta-variable means that code parsing the field is unable
to know whether the source specified the build dependencies as relevant
for retriggering. We should also not expand the meta-variable as that
would lose information, so we let it through now.
Closes: #910734
|
|
We should keep these and consider them as pseudo-EOF markers, and stop
processing once seen.
[lamby@debian.org:
- Initial test cases for dpkg-mergechangelogs functional tests. ]
Closes: #916056
|
|
Makes it more explicit what these variables actually mean.
Prompted-by: Axel Beckert <abe@debian.org>
|
|
|
|
It is not always entirely clear how each character class described
maps to the actual characters allowed. For example in some cases
alphanumeric includes only lower-case letters, sometimes both lower-case
and upper-case. Clarify it by appending the actual explicit range within
parenthesis.
Prompted-by: Ian Jackson <ijackson@chiark.greenend.org.uk>
|
|
These commands use both the available database and the package
selections.
Prompted-by: Johannes Schauer <josch@debian.org>
|
|
Add a reference to deb-src-control(5). Remove invalid comment in
example, as this format does not allow it.
Prompted-by: Helmut Grohne <helmut@subdivi.de>
|
|
Make it clear what will be printed when no arguments are specified.
Closes: #917098
|