Age | Commit message (Collapse) | Author | Files | Lines |
|
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.
|
|
|
|
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.
|
|
|
|
|
|
|
|
Warned-by: codespell
|
|
|
|
|
|
|
|
The find() function does not cope well with trying to traverse an
unexistent directory and generates various alarming warnings.
|
|
On source format 1.0, the default is for the debian/source/format file
not being present, which means we'll start with an empty Format field
name.
Fixes: commit d1d35a56e401181b6d15baf474a7db21d3372a65
|
|
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
|
|
Update to 603t.
|
|
|
|
|
|
Closes: #921031
Fixes: commit d1d35a56e401181b6d15baf474a7db21d3372a65
Diagnosed-by: Ian Jackson <ijackson@chiark.greenend.org.uk>
|
|
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>
|
|
We do not want to move the entries beneath the first depth of the
pathname, as when we try to move those, we will have already moved
their parent.
Closes: #922799
Signed-off-by: Guillem Jover <guillem@debian.org>
|
|
Print where these are to be used.
Closes: #922039
|
|
Update to 603t.
|
|
|
|
Version the macros so that both can be used, and default the unversioned
one to the version 0 macro.
|
|
Add a missing comma, and $(shell) make function invocation.
Closes: #913816
Signed-off-by: Guillem Jover <guillem@debian.org>
|
|
When not using --multiversion, track any repeated instance that would
possibly benefit from running with --multiversion, and output it at the
end with a suggestion to use that option.
Prompted-by: Johannes Schauer <josch@debian.org>
|
|
When not in multi-version mode, we can only ever have one package in the
%packages hash, remove the confusing loop and replace with an explicit
assignment using the first array reference element.
|
|
When we specify a --hash argument we should not compute all checksums to
then discard them.
Closes: #916456
Based-on-patch-by: Chris Lamb <lamby@debian.org>
|
|
|
|
|
|
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
|
|
This makes the creation of the object more compact and easier to read.
|
|
This move it at the beginning were it belongs, as the later code can
change behavior based on the format selected. This also will make it
possible to delegate the source format object selection to the
Dpkg::Source::Package class.
|
|
This move all ad-hoc code to use the new Dpkg::Source::Format module.
|
|
This new public module centralizes the handling of debian/source/format
so that other projects can reuse it instead of having to reimplement it.
Prompted-by: Mattia Rizzolo <mattia@debian.org>
Ref: https://salsa.debian.org/debian/devscripts/merge_requests/63
|
|
Make the regex more strict and decompose it right away instead of doing
a second pass over it. Only initialize minor when we need to update the
format. And fix the error for an invalid format to stop referencing the
Format field, which might not be involved during the parsing.
|
|
This makes it easier to construct a source package object with the
desired object, and initialize it as required.
Prompted-by: James McCoy <jamesan@debian.org>
Ref: https://salsa.debian.org/debian/devscripts/merge_requests/61
|
|
|
|
If the option has not been set, then the source format does not support
it and we should thus not recommend the --include-removal option in the
warning.
Closes: #913012
|
|
We initialized it already in the new constructor, no point in doing the
same twice.
|
|
Running code in the module scope means that anything importing the
module will execute that code, which is undesirable. Move the
initialization into a _select_objdump() sub, which gets assigned into
a state variable on demand.
|
|
The spawn() call was removed but not the matching import.
Fixes: commit 8ae966ae7d3635b8359829085db4262923ceae96
|
|
The default buildflags got moved from the Dpkg::BuildFlags module to
the Dpkg::Vendor::Debian, but this module was not adapted to match.
Instead of running the Debian hooks after the Ubuntu buildflags are set
up, run them first, and then modify/prepend the bits we need to change.
This fixes compiler optimization on ppc64el, and makes setting it more
future proof.
Fixes: commit d5374bc618310917557daa9c9ac2f4930515a0b2
Closes: #915881
Co-Author: Iain Lane <laney@ubuntu.com>
Co-Author: Adam Conrad <adconrad@ubuntu.com>
|
|
This makes several call sites more clear, as we move the logic inside
the function.
|
|
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
|
|
|