Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
There should be no difference between Copyright and Portions Copyright,
remove the distinction, and merge all these notices.
|
|
Doing a normal import via use, means that we need the module to be
present for the unit tests, when we only need it as part of the
distribution process.
|
|
We should mention when these functions are present and what they do,
so that users know when they can rely on these.
Warned-by: Test::Pod::Coverage
|
|
Even though we will not use the domain value set by this function, we
should honor its original interface and return a domain string, and
update it when requested.
|
|
Update to 600t.
|
|
|
|
This makes it easier to read which long option matches the short option.
|
|
This makes the --help output clearer, and matches the man page.
|
|
|
|
This makes it possible to select the current default behavior.
|
|
Makes the purpose of the variable clear.
|
|
Makes the purpose of the variable clear.
|
|
This should really be a vendor specific default. It's also documented
that way in the man page.
|
|
This function was being called on each foreach iteration to parse the
options within the DEB_BUILD_MAINT_OPTIONS and DEB_BUILD_OPTIONS
environment variables, and needed to parse these at construction time
every time. Inlining it should make it more performant and in addition
reduce line count.
|
|
The usage in this file is correct, but we are still doing boolean
evaluation.
|
|
We should always assign a proper Dpkg::Version object to the deprecated
variable. Otherwise it can get confused with the scalar value 0 used on
boolean context to denote it is *not* deprecated, instead of it being
a version number 0.
|
|
Give context to the warning message, otherwise it's not clear what is
going on. If the users to not conditionalize the warning usage they will
get a perl warning about the unknown warning category itself, bump the
module version to be able to discern this change, and update documentation
to reflect this.
|
|
Use i18nspector (if available) to check the .po and .pot files.
|
|
When we specify the debian/rules targets to call with --rules-target, we
should check only the build dependencies required bu those targets, and
nothing more.
Reported-by: Johannes Schauer <josch@debian.org>
|
|
|
|
|
|
If we are not going to build any binary package, there is no point in
checking whether we need to run any of the build targets.
|
|
Parse --rules-file instead of --rules-target, which made it a no-op.
Fixes: commit 293bd243a19149165fc4fd8830b16a51d471a5e9
Stable-Candidate: 1.18.x
|
|
We can just assign an anonymous sub to the typeglob.
|
|
If DEB_SIGN_KEYID is not set in the environment or the signing key is
not passed via --sign-key, dpkg-buildpackage emits a perl warning.
Warned-by: perl
Fixes: commit 6f903af181057a046a1344aadca552b113a2c2ee
Based-on-patch-by: Sven Joachim <svenjoac@gmx.de>
|
|
Update to 600t.
|
|
Instead of relying on the tail command, simply read the end of the
file ourselves, assuming a packed set of 80 character lines, reading
4096 bytes before the end, implies around 51 lines, which is close
to the 40 lines currently used.
This should be both faster and should improve portability, because even
if we are using the POSIX -n option, some systems do not have a POSIX
compliant tail(1) on the default path, such as Solaris.
Analysis-by: James Clarke <jrtc27@debian.org>
|
|
Update to 601t.
|
|
We should not accept short key IDs, and warn about long key IDs.
Recommend to use fingerprints.
|
|
The current bool overload has broken semantics, because it considers the
version "0" to be false.
The bool overload used to have sane semantics (equivalent to is_valid())
before commit 5b9f353b2940de751df47036608afbe71992d622, but there it got
changed to return the stringified version if it was valid, or undef
otherwise, to fix a problem within dpkg-shlibdeps, instead of properly
fixing the local-only problem in the tool. This makes the overload hard
to use, and broke existing callers from external projects.
We will emit a warning until dpkg 1.20.x to notify of the semantic change
in case there is code relying on the broken semantics. For fixed code the
warning can then be quiesced with:
no warnings qw(Dpkg::Version::semantic_change::overload::bool);
Closes: #895004
|
|
|
|
An ELF executable is defined by whether the object has the EXEC_P flag
defined or an interpreter in the program header. The former applies to
statically linked programs, the latter to dynamically linked programs
and possibly some shared libraries that can be executed, such as the
ones provided by glibc.
This is now more relevant as PIE makes normal executables show up as
shared objects, so they do not contain the EXEC_P flag, and were not
being detected as executables.
|
|
|
|
At least the format "3.0 (native)" supports no format specific options,
which makes the describe_cmdline_options() return an empty list.
|
|
|
|
Add a new dist-cpan target that takes care of preparing a perl
distribution to be uploaded to CPAN. Only the modules are shipped,
some of which do require dpkg tools being installed though.
Closes: #821177
|
|
Even though we always override it from the build system the default
pathname got out-of-sync with the repository when the architecture
tables got moved into the data directory.
Fixes: commit 97309bef8b664c2d58cb689a3e82848021ae9bad
|
|
This reverts commit 83272497c5be8c4e703ab179906cf904465fe775.
This commit introduced a regression in the author test suite. And there's
a patch by Johannes 'josch' Schauer <josch@mister-muffin.de> which should
be fixing this and other problems. If this is needed after all, we will
need to refactor the functions first to take a hash instead of a long list
of arguments.
|
|
|
|
This makes changing them easier to see when diffing.
|
|
|
|
This is more extensible and more clear.
|
|
Update to 599t.
|
|
The dpkg-architecture(1) man page states that these variables are
exported, and that's what dpkg-buildpackage does itself when setting
up the build environment. Doing this is always safe.
Closes: #888964
Signed-off-by: Guillem Jover <guillem@debian.org>
|
|
When we are picking up upstream tarball signatures, we should also print
them as being used to create the source package.
Closes: #888787
|
|
Lumping all found tarballs into a single line makes the output more
confusing.
|
|
This new option makes it possible to force falling back to the legacy
behavior of assuming that debian/rules files require root.
|
|
This variable is set by the builder to notify debian/rules that it
supports this specification.
Wordsmithing-by: Niels Thykier <niels@thykier.net>
|
|
The specification is clear on this, and we should not be setting this
variable when the values are different to "no" and "binary-targets".
|