Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
Because we do not use it and "breaking" causes problems upgraring.
|
|
Update to 274t.
|
|
Update to 1135t.
|
|
We need to pass this option forward to the verify_signature() calls,
otherwise we use the default.
Fixes: commit 139dfc4c78593d995610c0aa180300a9a7dd94ac
Fixes: commit 3821f024d92aabf24a333025c1c1956d8a45e718
|
|
This was causing unit test failures.
|
|
Update to 3016t.
|
|
|
|
Update to 609t.
|
|
|
|
|
|
Make it clear that these classes inherit from some other base class,
which will contain the missing documentation.
Prompted-by: intrigeri <intrigeri@debian.org>
|
|
These were referring to the type and not the instance, which makes
using the incorrect nomenclature confusing.
|
|
This makes sure we execute the handlers on normal errors, and can thus
remove the traps from several functions to run the handlers and to then
rethrow the exception.
|
|
We should cleanup the handlers to the previous state otherwise we
end up changing the behavior globally, when this should be a local
cleanup behavior.
Closes: #932841
|
|
|
|
This hook has been obsoleted for a while and been emitting deprecation
warnings, so it's safe to remove now.
|
|
We do not bump the module version to 2.00, as these functions and option
have croak'ed almost since their introduction.
|
|
|
|
|
|
Bump module version to 2.00.
|
|
Bump module version to 2.00.
|
|
Bump module version to 2.00.
|
|
Bump module version to 2.00.
|
|
Bump module version to 2.00.
|
|
Bump module version to 2.00.
|
|
Bump module version to 2.00.
|
|
Remove warnings for obsolete options forceplugin and libdir. Remove
obsolete functions changelog_parse_debian() and changelog_parse_plugin().
Bump module version to 2.00.
|
|
These are not actual variables, but option passed in a hash, so using
the $ sigil here is very confusing.
|
|
Remove obsolete methods check_header() and check_trailer(). Hide internal
lowercase variables $regex_header and $regex_trailer.
Bump module version to 2.00.
|
|
Bump module version to 2.00.
|
|
Bump module version to 2.00.
|
|
Do not allow non-equal version relations in virtual provides.
Closes: #930317
|
|
Closes: #939969
|
|
Closes: #932967
|
|
Having the template symbols file format described in the dpkg-gensymbols
has been a continuous source of confusion for users, and makes
discovering it more difficult. Move it to its own man page, and link to
it from the various relevant man pages.
|
|
|
|
Ref: #930788
Spotted-by: Sven Joachim <svenjoac@gmx.de>
|
|
This was done in the name of security, but it does not make much sense
as root should make sure to be running in a clean environment. This is
problematic as it makes the interface hard to understand, and produces
unexpected behavior as dpkg can be called from within itself, or as a
wrapper for dpkg-query, which will then not inherit the admindir value.
Closes: #900071
|
|
A package marked to be on hold, denotes that the package should be kept
in its current version and should not be automatically installed, upgraded
or removed. The same applies to frontends. This behavior does not apply
when the user explicitly requested one of these actions, or the
--force-hold option is used.
It should never prevent dpkg from processing these for configuration (if
they were already in unpacked state) or from trigger processing, otherwise
we might get into trigger loops. Some of the code was already doing this,
but this was not consistently done. We update also the help output and
documentation to clarify the fixed behavior.
Closes: #926472
|
|
We should not add up the size of each hardlink into the final sum,
otherwise we will get a size in excess.
Closes: #923475
Co-Authored-by: Guillem Jover <guillem@debian.org>
Signed-off-by: Guillem Jover <guillem@debian.org>
|
|
When we have been requested to load the available file, and that
contains a description for a package that is not installed, we should
use that instead of printing the confusing string stating that the
description is not available.
Closes: #43573
|
|
Several of these are used by the test suite.
|
|
Having this custom rule to create the «configure» file means that it
might end up not being rebuilt if the timestamps of some other files
are off compared to the debian/changelog date. Using dh_autoreconf
guarantees that even if these timestamps got updated incorrectly,
the file will always be rebuilt as expected.
The historic rationale for not doing this before, even though this has
been considered a best packaging practice, was that because dpkg needs
explicit support for new architectures, which is the main reason to
get autotools updated to pull in new config.* files, we would get
reports so that we could add such support and release a new upstream
version. But this has never happened, and it's causing other problems.
Closes: #939516
Signed-off-by: Guillem Jover <guillem@debian.org>
|
|
Closes: #942195
Signed-off-by: Guillem Jover <guillem@debian.org>
|