apt/cmdline, branch 1.3.1Debians commandline package managerhttps://git.kalnischkies.de/apt/atom?h=1.3.12016-08-26T22:31:03ZMerge branch 'portability/freebsd'2016-08-26T22:31:03ZJulian Andres Klodejak@debian.org2016-08-26T22:31:03Zurn:sha1:6a68315e938eb2611806658828ecea86805822e7apt-key: Only use readlink -f for existing components2016-08-26T20:17:54ZJulian Andres Klodejak@debian.org2016-08-23T19:01:06Zurn:sha1:dd7758b9245275a31fde70218db9a531c5859c26
On FreeBSD, readlink -f requires the last component
to exist.
Add missing includes and external definitions2016-08-26T13:49:10ZJulian Andres Klodejak@debian.org2016-08-23T11:15:15Zurn:sha1:24a59c62efafbdb8387b2d3c5616b04b9fd21306
Several modules use std::array without including the
array header. Bad modules.
Some modules use STDOUT_FILENO and friends, or close()
without including unistd.h, where they are defined.
One module also uses WIFEXITED() without including
sys/wait.h.
Finally, environ is not specified to be defined in unistd.h. We
are required to define it ourselves according to POSIX, so let's
do that.
show apt-key warnings in apt update2016-08-25T13:22:28ZDavid Kalnischkiesdavid@kalnischkies.de2016-08-25T13:22:28Zurn:sha1:29c590951f812d9e9c4f17706e34f2c3315fb1f6
In 105503b4b470c124bc0c271bd8a50e25ecbe9133 we got a warning implemented
for unreadable files which greatly improves the behavior of apt update
already as everything will work as long as we don't need the keys
included in these files. The behavior if they are needed is still
strange through as update will fail claiming missing keys and a manual
test (which the user will likely perform as root) will be successful.
Passing the new warning generated by apt-key through to apt is a bit
strange from an interface point of view, but basically duplicating the
warning code in multiple places doesn't feel right either. That means we
have no translation for the message through as apt-key has no i18n yet.
It also means that if the user has a bunch of sources each of them will
generate a warning for each unreadable file which could result in quite
a few duplicated warnings, but "too many" is better than none.
Closes: 834973
apt-key: warn instead of fail on unreadable keyrings2016-08-25T10:42:36ZDavid Kalnischkiesdavid@kalnischkies.de2016-08-25T10:42:36Zurn:sha1:105503b4b470c124bc0c271bd8a50e25ecbe9133
apt-key has inconsistent behaviour if it can't read a keyring file:
Commands like 'list' skipped silently over such keyrings while 'verify'
failed hard resulting in apt to report cconfusing gpg errors (#834973).
As a first step we teach apt-key to be more consistent here skipping in
all commands over unreadable keyrings, but issuing a warning in the
process, which is as usual for apt commands displayed at the end of the
run.
allow spaces in fingerprints for 'apt-key del'2016-08-17T12:12:24ZDavid Kalnischkiesdavid@kalnischkies.de2016-08-17T06:10:29Zurn:sha1:e289907f5e7241034cb0d37055dc2cba4e3a19af
Fingerprints tend to be displayed in space-separated octet pairs so be
nice and allow delete to remove a key based on such a string rather than
requiring that the user is deleting all the spaces manually.
add the gpg-classic variant to the gpgv/gnupg or-group2016-08-17T07:52:32ZDavid Kalnischkiesdavid@kalnischkies.de2016-08-16T13:46:19Zurn:sha1:19fdf93d7363261227811a62157063081b9f1a5d
We need to support partial upgrades anyhow, so we have to deal with the
different versions and your tests try to ensure that we do, so we
shouldn't make any explicit higher requirements.
Get rid of the old buildsystem2016-08-10T14:17:19ZJulian Andres Klodejak@debian.org2016-08-09T15:40:01Zurn:sha1:c85c4bed0a4b32ee2dcbd86ea819e39f3d8beb84
Bye, bye, old friend.
CMake: Add basic CMake build system2016-08-06T20:36:02ZJulian Andres Klodejak@debian.org2016-08-06T19:03:43Zurn:sha1:f3de2dbaf657f9040a4da448c57267de0fef7d33
Introduce an initial CMake buildsystem. This build system can build
a fully working apt system without translation or documentation.
The FindBerkelyDB module is from kdelibs, with some small adjustements
to also look in db5 directories.
Initial work on this CMake build system started in 2009, and was
resumed in August 2016.
apt-key: ignore any error produced by gpgconf --kill2016-07-31T08:29:25ZDavid Kalnischkiesdavid@kalnischkies.de2016-07-31T08:29:25Zurn:sha1:215598df84c092f801fe154e510c68fcc263b3ba
gpgconf wasn't always equipped with a --kill option as highlighted by
our testcases failing on Travis and co as these use a much older version
of gpg2. As this is just for cleaning up slightly faster we ignore any
error a call might produce and carry on. Use a recent enough gpg2
version if you need the immediate killing…
Gbp-Dch: Ignore
Reported-By: Travis CI