Age | Commit message (Collapse) | Author | Files | Lines |
|
Missed in commit 1a60e5317318ab0d4097b524a2b5cd39ab905f11.
|
|
The SE Linux context in computer readable form get translated to human
readable form if the mcstransd daemon is running. But if the daemon
fails inbetween then dpkg might try to write wrong data to disk. To
avoid the flakines implied in relying on the state of that daemon,
just never translate the context.
As a side effect this should incur in a slight speed up.
[guillem@debian.org:
- Coding style fixes.
- Added code comment. ]
Closes: #679641
Signed-off-by: Guillem Jover <guillem@debian.org>
|
|
Even if the output format is designed to be human readable, and for
machine parseable output «dpkg-query -W» should be used instead, there's
probably scripts in the wild parsing «dpkg-query -l». Thus, the new
column is inserted before the Description column which is unreliable
to parse anyway as its value will always contain spaces, which are the
column separators, and as such should be pretty safe.
The arch-qualified package names will still be printed, as that
allows to copy-and-paste package names as input to dpkg commands w/o
any possibility of ambiguity.
Closes: #673190
Suggested-by: Jonathan Nieder <jnieder@gmail.com>
|
|
|
|
|
|
This switch frees the -h option to be used in the distant future for
other purposes, it also uses a character that does not have any other
obvious meaning for help output, and which is pretty safe to be used
blindly by the user in the same way as --help.
|
|
Error messages like "couldn't parse control information from foo.deb"
are not full sentences, so don't punctuate them like one. The main
purpose of this patch is stylistic consistency, but perhaps it can
also make copy-and-paste from messages like
dpkg-query: no path found matching pattern /usr/bin/agrep.
a little easier.
Most actual full sentences should remain untouched. A few full sentences
are error messages at heart, so this patch converts those to lower-case
sentence fragment form, too.
[guillem@debian.org:
- Add missed strings.
- Minor tweaks to strings. ]
Closes: #624000
Requested-by: Jari Aalto <jari.aalto@cante.net>
Signed-off-by: Guillem Jover <guillem@debian.org>
|
|
This switches all ad-hoc stderr printing for error notices to the
notice() function.
|
|
As a side effect this mkes the messages more clear as the caller has
more context to describe the error conditions.
Closes: #621763
|
|
This fixes two issues at once: the more detailed inner message is
relied back to the more general outter printer which allows a clearer
error message, and it makes the pkg-format module stop printing things
at all which is bad for a library,
|
|
These replace the now deprecated --control-path command, as these do
not rely on any specific database layout.
|
|
|
|
|
|
|
|
File triggers have been activated up to now explicitly whenever seen,
and only the requested pathname. While unpacking or removing, this is
not an issue as dpkg will traverse the hierarchy and trigger parent
directories during the process.
Because conffiles get a two staged installation, first unpacked into
<conffile>.dpkg-new and then installed in place on configure, a trigger
activated only after unpack will not see the <conffile> at its final
location or see it at all if it correctly ignores those file extensions.
This is an issue for conffiles or explicit dpkg-trigger file triggers,
as an interest on parent paths will not activate the trigger as those
parents are not traversed. With the subsequent cause of missed updates
because code has not been run on the actual installation of conffiles.
Closes: #675613, #676061, #676062, #676107, #676118, #676122
|
|
|
|
|
|
When the package has never been installed before, and the unpack has not
yet finished, the package will be present on the database but the files
list file will not, which would produce a bogus warning. Check if the
package has ever been configured, before printing the warning.
Closes: #673518
|
|
|
|
Verify that the numbers are not out of the range; i.e. that no negative
values are allowed if not appropriate, and that no overflows occur.
Closes: #580038
|
|
There's no guarantee that errno will be set for all error conditions
checked.
Regression introduced in commit 20e7af7b6ee4ab703b5d0e6f091fe3f565550a2b.
|
|
|
|
If we are defining bit flags, it's more natural to just name the bits
by their index instead of using octal values.
Use the opportunity to assign bit indices in increasing order, as some
flags had been inserted in alphabetical/group order but keeping the
other flag's values.
|
|
There's no other users, and no public function expecting such argument,
so just hide this implementation detail where it belongs.
|
|
At the same time reorder the arguments and place the relation operator
in the middle, which is a more natural way to express it.
|
|
|
|
Use more meaningful enum value names, and simplify them by having the
minimum amount of values required.
|
|
|
|
|
|
Autoconf provides an AC_PROG_MKDIR_P macro defining MKDIR_P which is
called by AM_INIT_AUTOMAKE; the obsolete mkdir_p, currently aliased to
MKDIR_P will disappear with automake 1.13.
|
|
This will report about any package missing the list or md5sums files
from the database, so that they can be reinstalled.
|
|
This will allow to pass strings to the checkers.
|
|
This is the first step in allowing to verify installed package files
consistency. Next step will be to track file metadata and then add
options to verify the requested packages.
Closes: #155676, #155799
|
|
|
|
Signed-off-by: Guillem Jover <guillem@debian.org>
|
|
If the file is already owned by the package diverting it, that will
actually mess up the filesystem for no good reason, just ignore the
request and issue a message stating so.
Closes: #588077
|
|
The standard way to select if a specific component of the build is to
be enabled or disabled is through --enable-foo and --disable-foo
options, --with-foo and --without-foo are used for selecting external
modules to be used.
|
|
|
|
Reported-by: Helge Kreutzmann <debian@helgefjell.de>
|
|
Closes: #552517
|
|
These functions have never belonged in the filesdb module, but were put
there temporarily for convenience.
|
|
|
|
This will guarantee there's never a time a call site can get NULL
from the function, and detangles it from the in-core filesdb
initialization.
|
|
|
|
|
|
|
|
This makes sure the filename is absolute and does not contain newlines.
Closes: #21722
|
|
|
|
There's no point in checking it at --add time because even if it was
not specified and it got constructed from filename, it can never be
non-absolute as filename has already been checked for that.
|
|
|