Age | Commit message (Collapse) | Author | Files | Lines |
|
Use make_path() instead of mkpath(), and remove_tree() instead of
rmtree().
|
|
Match the ld.so path resolution logic, by preferring multiarch paths
over multilib or cross paths.
[guillem@debian.org:
- Adapt to current code. ]
Closes: #772184
Signed-off-by: Guillem Jover <guillem@debian.org>
|
|
Split them so that we can mark the toolchain cross-compilation libraries
as deprecated, and in the future possibly just hide them by default.
|
|
Assign directly to @librarypaths when adding the cross-compilation
library paths.
|
|
This will allow in the future to hide these by default and avoid
polluting the default paths.
|
|
This was a temporary workaround for very old gcc toolchains.
See: #453267
|
|
This avoids inflicting the cost of the setup on any code loading the
module. It also makes it easier to unit test the module.
|
|
This will allow to initialize the library paths to be an empty array,
instead of just resetting it after the fact, which means the new name
will make more sense.
|
|
|
|
The loading is always the same, the difference is just in the parsing
logic.
|
|
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.
|
|
The old function name was inconsistent with the other gettext family
of short aliases which has already caused some code typos, and functions
starting with underscore are considered by convention private in Perl.
|
|
These allow to tag symbols as being only relevant on architectures with
specific bits or endianness. The current supported values are 32 and 64
for arch-bits, and little and big for arch-endian.
They can also be combined by using multiple tags on the same symbol.
Closes: #630342
|
|
Stop abusing the Dpkg::Deps object just to get the architecture
computation from it.
|
|
Factor out from Dpkg::Deps::Simple::arch_is_concerned().
|
|
|
|
Release 1.17.20
Conflicts:
debian/changelog
scripts/Dpkg/Arch.pm
|
|
Upstream tarballs usually come with detached signatures, which would be
useful to have in the source package, as an additional check that could
be performed to verify its integrity and provenance.
For now just allow the detached signatures to be listed in the file
fields in the source control file (.dsc).
Closes: #759478
Suggested-by: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
|
|
This is to try to make sure, that even if documented, people will not
accidentally rely on private modules, that have not API stability
guarantees.
|
|
These are clearly exported, otherwise they would not be documented.
|
|
This makes it clear what is the current version of the module, and that
it is a public interface.
|
|
|
|
|
|
|
|
Fixes ControlStructures::ProhibitMutatingListFunctions.
Warned-by: perlcritic
|
|
|
|
This makes the DEB_BUILD_PROFILES environment variable parsing more lax.
Signed-off-by: Guillem Jover <guillem@debian.org>
|
|
The loop in the function was expecting $line to be filled by its last
part, and by working on the topic variable it was not getting updated.
Switch all topic variable usages in that funtion so that we can restore
working source unpacking.
Regression introduced in commmit 0d5e17af7391fb0d3a3c695dac40f8df41f8b11c.
Closes: #764206
Addresses BuiltinFunctions::ProhibitUselessTopic.
Warned-by: perlcritic
|
|
pie is blacklisted on mips and mipsel, according to the comments due
to #526961. This bug has been fixed more than 4 years ago, it's time
to reactivate pie support.
Similarly strack-protector support has been added on mips and mipsel
in gcc 4.6 so we can now activate it too.
Closes: #763672
Signed-off-by: Aurelien Jarno <aurelien@aurel32.net>
Signed-off-by: Guillem Jover <guillem@debian.org>
|
|
Addresses Subroutines::RequireArgUnpacking.
Warned-by: perlcritic
|
|
Addresses Subroutines::RequireArgUnpacking.
Warned-by: perlcritic
|
|
- The restriction list parsing now reflects the changes at
<https://wiki.debian.org/BuildProfileSpec> which were agreed upon
in the bootstrap sprint 2014 in Paris.
- Restriction lists are now restriction formulas.
- Restriction formulas are given in disjunctive normal form expression:
pkg <bar baz> <blub>
- Removal of the implicit prefix/namespace mechanic.
- Since there can be more than one <> block, the regex in
parse_string() in Dpkg::Deps is now greedy.
- Construct the profiles entry of the Packages-List field by converting
the "<bar baz> <blub>" syntax into "bar,baz+blub".
- Include a temporary compatibility mapping for the old way to write
the Build-Profiles field in binary packages which can be removed once
all affected source packages have moved to the new syntax.
- Adjust testcases.
Closes: #760158
[guillem@debian.org:
- Add a warning when using the old syntax in dpkg-source.
- Move comments before the regexes, not besides them in dpkg-source.
- Change from an xnor to == in evaluate_restriction_formula().
- Move the Dpkg::Util import close to the other Dpkg imports.
- Add test cases for the new parse_build_profiles() behavior. ]
Signed-off-by: Guillem Jover <guillem@debian.org>
|
|
Properly handle the absence of packages in DEBIAN/control depending
on build profiles, so that we do not emit bogus warnings anymore.
Closes: #758191
Based-on-patch-by: Johannes Schauer <j.schauer@email.de>
Signed-off-by: Guillem Jover <guillem@debian.org>
|
|
Use it everywhere instead of inline code.
|
|
Addresses RegularExpressions::ProhibitFixedStringMatches.
Warned-by: perlcritic
|
|
Addresses RegularExpressions::ProhibitFixedStringMatches.
Warned-by: perlcritic
|
|
Missed in commit 7386defdaebf4746dc074a118bf7430cecf7a57f.
|
|
Make it clear that these are the addon tarballs.
|
|
This will add approproriate options to warn about __TIME__, __DATE__ and
__TIMESTAMP__ macros.
Closes: #762683
Signed-off-by: Guillem Jover <guillem@debian.org>
|
|
Signed-off-by: Guillem Jover <guillem@debian.org>
|
|
|
|
This allows users to specify build flags from specific area features.
These settings will be overridden by any subsequent settings from
DEB_BUILD_MAINT_OPTIONS, in the same way other build flags are affected,
so that the maintainer can disable specific things that might be broken.
|
|
This can be used to test the propagation of build flags by checking the
build logs for any omission.
Closes: #628516
|
|
This feature will enable fatal warnings for code that can pose
actual problems.
Closes: #682659
|
|
This will allow to add various Quality Assurance features that can be
used to avoid common errors.
|
|
|
|
Closes: #759747
Based-on-patch-by: Dima Kogan <dima@secretsauce.net>
|
|
This got missed in commit 5bb02fe80e9f40dcad9703a72f67cf615ff217b5.
|
|
|
|
Fixes BuiltinFunctions::ProhibitUselessTopic
and RegularExpressions::ProhibitUselessTopic.
Warned-by: perlcritic
|