Age | Commit message (Collapse) | Author | Files | Lines |
|
We do not distribute the PO files yet for CPAN, so the checks should not
fail when they are missing, even when testing with AUTHOR_TESTING=1.
|
|
Use i18nspector (if available) to check the .po and .pot files.
|
|
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
|
|
Add new test_get_temp_path() function, and replace all hardcoded
settings of the temporary directory and its creation.
|
|
We can easily know the name of the calling unit test, and can thus infer
the pathname for the data directory, instead of having to duplicate the
name, and potentially ending with it being out of sync.
|
|
|
|
|
|
|
|
Using undeterministic filenames based on the buildinfo-id produces ugly
looking filenames, which get left behind when rebuilding the same source
multiple times as they vary by date.
There's really no great point in using unique filenames as they will end
up with different contents depending on the builder.
|
|
Addresses RegularExpressions::RequireExtendedFormatting.
Warned-by: perlcritic
|
|
The .buildinfo files are a new type of control files, similar to
the .changes files, meant to describe the environment of a build
and its artifacts. They are meant to be added to the Debian archive
to allow independent parties to reproduce a build and verify the
result.
Specifications for .buildinfo are available at:
<https://wiki.debian.org/ReproducibleBuilds/BuildinfoSpecification>
This patch adds support for .buildinfo files in Dpkg::Control,
adds new .buildinfo fields to Dpkg::Control::Fields, a new
builtin-system-build-paths Dpkg::Vendor hook, and adds a new script
named dpkg-genbuildinfo, that will now be called by dpkg-buildpackage
before generating the .changes file.
[ntyni@debian.org: small changes. ]
Closes: #138409
Based-on-patch-by: Jérémy Bobbio <lunar@debian.org>
Signed-off-by: Guillem Jover <guillem@debian.org>
|
|
|
|
|
|
This is the variable perl developers expect when running author or
developer tests, honour it to make people's life easier.
|
|
|
|
Place 'use' strict and warnings first, then Exporter 'our' declarations,
then Test module imports, then system module imports, then Dpkg module
imports, then 'use' parent and overload pragmas, separated by a blank
line for each block.
Split each exported symbol declaration into its own line to ease
modifications.
|
|
This will centralize common testsuite functions.
|