Age | Commit message (Collapse) | Author | Files | Lines |
|
Document inherited methods. Document the return values. Note which
arguments are optional. Reorder methods by their position in the stack.
|
|
The test suite expects to run under the C locale.
Fixes: https://rt.cpan.org/Ticket/Display.html?id=127314
|
|
All these environment variables are only relevant while running the
test suite. Do not pollute the rest of the environment.
|
|
Reported-by: Johannes Schauer <josch@debian.org>
Warned-by: shellcheck
|
|
Warned-by: shellcheck
|
|
Update to 603t.
|
|
|
|
This makes it possible to reuse the code by other modules.
|
|
|
|
The check is very simple, and can be done w/o requiring calling diff(1)
for each input file.
This makes the code shorter, more portable, and should be faster in the
non-binary cases.
|
|
|
|
|
|
This will contain different data depending on the program used. We do
not really care about that, later versions of GnuPG have stopped
emitting it, and it makes the test suite fail when using GnuPG 1.x.
Fixes: https://rt.cpan.org/Public/Bug/Display.html?id=127217
|
|
For the CPAN distribution or a non-dpkg-based distribution we cannot
assume that dpkg will be installed, or even available at build time.
Skip these tests if the tools is missing.
|
|
Split the test recommends from the requires and add develop recommends
into a prereqs metadata hierarchy.
|
|
|
|
This will enable the -TRIAL versioning that CPAN uses to avoid indexing
such releases.
|
|
Set the more generic name from within DPKG_DIST_IS_RELEASE, and use that
directly in the Build.PL.in file.
|
|
|
|
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.
|
|
When building the CPAN package, we need to also distribute the data
files, otherwise the modules will not work correctly once installed.
|
|
We had an empty do_perl_subst variable in the dist-cpan autotools
target that resulted in copying an empty file, but that was shadowed by
a subsequent copy of the original. So we were ending up with a pristine
non-substituted file.
We actually need to substitute the install paths during the CPAN module
building to preserve system and user settings at that point. Otherwise
the dpkg autotools configure settings might be completely out of touch
with the settings from the system where the CPAN module gets built.
|
|
Update to 602t.
|
|
The former calls /bin/pwd, while the latter uses the getcwd() syscall
directly.
Signed-off-by: Guillem Jover <guillem@debian.org>
|
|
This option will make the output be in reverse order.
|
|
This should make it possible to ignore the warning w/o hardcoding any
distribution specific package name pattern on the code.
|
|
This will make it possible to track key/value attributes for each file,
so that we can track interesting information and pass it to the various
programs parsing the debian/files file.
|
|
This is a superset of the fixdebugpath feature supported by gcc-8, but
covering in addition mappings for macros such as __FILE__ and similar.
|
|
Architecture:all packages are treated as native ones as part of the
current multi-arch design, the only current exception is in
build dependencies with the :native arch-qualifier.
It looks like this was an oversight when implementing the :native
support, as there's been no rationale found for the current behavior.
Closes: #854438
Analysis-by: Johannes Schauer <josch@debian.org>
|
|
When we need the environment variablem check that it is defined, and
error out otherwise.
Closes: #907772
|
|
We were trying to use realpath() on nonexistent directories, which means
we'd get undef. Instead just completely ignore nonexistent directories
from any processing.
Fixes: commit 174a5bd2a080847d0ed901d269a2ba74476eba8b
|
|
|
|
Update to 602t.
|
|
Having the string read as “\nTo” confuses codespell, as a typo for not.
Just break the string at the newline to make it more clear for humans
and spell checkers alike.
Warned-by: codespell
|
|
|
|
Forcing the signing while not actually preparing a tarball for a
release disitribution, that is due to a signed tag, means that any
random «make distcheck» will trigger an annoying gpg prompt.
|
|
Warned-by: perlcritic
Fixes: Subroutines::ProhibitAmpersandSigils
|
|
This way we can distinguish the failure from the success case.
|
|
We might use a vendor specific series file, so we should print the one
being used to notify if this fact.
|
|
This makes the deprecation explicit, so that we can start noticing
what is inappropriately setting this variable for a purpose it was
not designed for.
|
|
This option will make it possible to stop using LD_LIBRARY_PATH when
calling this script.
|
|
Clarify the unknown and unused substitution variable warnings, to try to
make them more clear as to what each implies.
Closes: #904258
|
|
Thanks-to: Niels Thykier <niels@thykier.net> (for typo in dpkg(1))
|
|
C++11 makes it possible to use these attributes so that errors can be
avoided, by helping the compiler know when we mean methods to override
the ones from the parent class.
Warned-by: cppcheck
|
|
To be able to build a source tree, a user needs write permisions on it,
but not necessarily ownership of those files. We check the existing file
permissions and avoid changing them if not necessary, which helps in the
case where the user does not have ownership of those files, and they
were already present.
Closes: #898010
Naming-by: Julian Andres Klode <jak@debian.org>
|
|
This makes the structure easier to comprehend, and easier to read,
otherwise it's difficutl to search for specific methods or functions
and know immediately to what module they belong. It also makes for
more structured POD.
|
|
This method is currently used by Dpkg::Deps::Simple, and is marked as
private by way of its underscore prefix. This will be a problem once
we split the modules into different files, as then we are not supposed
to be using private methods from external modules.
Rename the method, and document it explicitly as being private, while
only giving a partial prototype to deter its use.
|
|
Document each implemented method. This will make it easier to split the
modules into their own files.
|
|
Add new TODO tests for behavior that is not yet implemented, but should.
|
|
Dependency simplification can only really be done for metadata for which
we have all its context and information during the simplification
process. Anything that relies on the state of the dependencies cannot be
simplified. This means that any dependency that might change the
satisfiability due to the value of Multi-Arch field of the depended on
package cannot be simplified.
Clarify this in the function commends, and add new test cases to cover
this.
Prompted-by: Stuart Prescott <stuart@debian.org>
|