Age | Commit message (Collapse) | Author | Files | Lines |
|
This will make it possible to access the filesystem entries per package
from anything that queries the database, such as «dpkg-query --show».
|
|
The code was there but commented out. Let's add proper support for
debugging output, controllable at run-time.
|
|
These implement the systemd readiness protocol for services. So that
a service can tell s-s-d when it's ready and then we can return and
callers can assume safely that the service is ready to work.
[biebl@debian.org:
- Fix some typos. ]
[trek00@inbox.ru:
- Fix notification directory and socket permissions. ]
Closes: #910707
|
|
The .changes file describes an upload, and its Binary and Description
fields should contain (as documented) only references to the packages
being uploaded.
In case of a source-only upload, the Binary and Description fields
should be empty.
Closes: #818618
|
|
Filtering this meta-variable means that code parsing the field is unable
to know whether the source specified the build dependencies as relevant
for retriggering. We should also not expand the meta-variable as that
would lose information, so we let it through now.
Closes: #910734
|
|
We should keep these and consider them as pseudo-EOF markers, and stop
processing once seen.
[lamby@debian.org:
- Initial test cases for dpkg-mergechangelogs functional tests. ]
Closes: #916056
|
|
Makes it more explicit what these variables actually mean.
Prompted-by: Axel Beckert <abe@debian.org>
|
|
|
|
It is not always entirely clear how each character class described
maps to the actual characters allowed. For example in some cases
alphanumeric includes only lower-case letters, sometimes both lower-case
and upper-case. Clarify it by appending the actual explicit range within
parenthesis.
Prompted-by: Ian Jackson <ijackson@chiark.greenend.org.uk>
|
|
These commands use both the available database and the package
selections.
Prompted-by: Johannes Schauer <josch@debian.org>
|
|
Add a reference to deb-src-control(5). Remove invalid comment in
example, as this format does not allow it.
Prompted-by: Helmut Grohne <helmut@subdivi.de>
|
|
Make it clear what will be printed when no arguments are specified.
Closes: #917098
|
|
Describe when --remove is equivalent to --purge, and what data it will
cleanup and when.
Closes: #914478
|
|
Update to 2952t1f.
|
|
|
|
This makes it possible to disable any pager usage from these programs.
For dpkg this also becomes a configuration option.
Closes: #909754
|
|
|
|
This makes it possible to use a dpkg specific pager.
Suggested-by: Craig Sanders <cas@taz.net.au>
Ref: #909754
|
|
The PAGER environment variable is specified in POSIX as taking a pager
command and any number of arguments to be passed to «sh -c», so we have
to preserve that behavior or this breaks badly on systems where PAGER is
set that way.
This actually gets in the way of improving the pager command presence
detection, but we'll fix that later on, by making the scanning of the
environment variable smarter or by trying to execute the fallbacks.
Closes: #910009
|
|
This makes it possible to use alternative installation directories.
And will make these commands honor those directories when specified
for dpkg, and passed down to the maintainer script via the DPKG_ROOT
environment variable.
|
|
When we started making «dpkg-query --list» use a pager, we missed
documenting this environment variable.
Fixes: commit 05458bb8d50cb3b0f29e53d2a079f2ef874b8f23
|
|
This includes the --force-breaks, --force-conflicts, --force-depends,
--force-depends-versio and --ignore-depends.
Prompted-by: James Clarke <jrtc27@debian.org> (on IRC)
|
|
Prompted-by: Stuart Prescott <stuart@debian.org>
|
|
Turn the reference to the vendor-specific series file vendor-neutral,
and specify the order and default name. Explain one of the reasons for
the feature, and where it is particularly helpful.
|
|
Prompted-by: Manuel A. Fernandez Montecelo <mafm@debian.org>
|
|
Prompted-by: Mattia Rizzolo <mattia@debian.org> (on IRC)
|
|
|
|
Update to 2932t1f.
|
|
|
|
Prompted-by: Michael Orlitzky <michael@orlitzky.com>
Ref: https://redmine.kannel.org/issues/771
|
|
Update to 2930t1f.
|
|
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.
|
|
Update to 2924t1f.
|
|
Update to 2905t10f10u.
This update only deals with strings which can be trivially unfuzzied.
|
|
This option will make it possible to stop using LD_LIBRARY_PATH when
calling this script.
|
|
When not passing any argument these commands will dump the entire
database. This way external programs will have a proper public
interface to get all package records, even when there are unmerged
journal entries.
Closes: #616342
|
|
The current code, checks whether we are running on a terminal, and then
truncates the output fields so that it can fit within. This causes data
loss and can confuse the user depending where the cut point has happened.
Instead we remove that logic, and always redirect the outout through a
pager in case we are running on a terminal, which gives full information
and does not necessarily emit ugly output.
Closes: #898603
|
|
Closes: #900033, #900035, #900040
Signed-off-by: Guillem Jover <guillem@debian.org>
|
|
Closes: #904060
|
|
Thanks-to: Niels Thykier <niels@thykier.net> (for typo in dpkg(1))
|
|
Signed-off-by: Guillem Jover <guillem@debian.org>
|
|
Update to 2909t7f8u.
This update only deals with strings which can be trivially unfuzzied.
|
|
Update to 2923t1f.
|
|
Closes: #902616
Reported-by: Uwe Kleine-König <ukleinek@debian.org>
|
|
We are distributing the man.stamp, so we need the timestamps of the
files to match the original ones, so that make can work its magic,
at least for man.stamp, the rest we do to be future-proof.
|
|
The pre-requisite might be available on the source or build directories
depending on whether we are building from git or a distribution tarball.
We should use an automatic variable to always grab the file from VPATH
wherever it might be located.
|
|
Update to 2923t1f.
|