apt, branch 1.5_rc1Debians commandline package managerhttps://git.kalnischkies.de/apt/atom?h=1.5_rc12017-08-24T21:21:40ZRelease 1.5~rc12017-08-24T21:21:40ZJulian Andres Klodejak@debian.org2017-08-24T21:21:40Zurn:sha1:d885930f62756e4ca8ad9a80be2ffebe68ac3e97Make test-bug-818628-unreadable-source work on !amd642017-08-24T15:44:31ZJulian Andres Klodejak@debian.org2017-08-24T15:44:31Zurn:sha1:427828d9638c9e5f3550820bd9d71da5d5a0909c
It was broken because apt.conf.d was not readable, but that's
where the architecture is defined...
Replace APT_CONST with APT_PURE everywhere2017-08-24T14:56:52ZJulian Andres Klodejak@debian.org2017-08-24T14:55:15Zurn:sha1:0e4ac8334d02ea256f750ad61689f28ff1ebdf6c
As a follow up to the last commit, let's replace APT_CONST
with APT_PURE everywhere to clean stuff up.
Redefine APT_CONST to mean APT_PURE2017-08-24T14:56:48ZJulian Andres Klodejak@debian.org2017-08-24T14:50:12Zurn:sha1:03590fb98226bfdf3147eb78effc3fa7987709bb
Functions marked with the const attribute may not inspect
any global memory. This includes targets of pointers or
references passed as arguments. A pure function however
is free to inspect memory, but may not have any side
effects.
The function StringSplit() was marked as const, but took
two references to strings. When the second one was passed
as a literal as in StringSplit(name, "::") the compiler
cleverly figured out that we only inspect the address of
"::" (since StringSplit is const) and thus optimized away
the "::" content.
While patching out individual broken uses of APT_CONST
would be possible, this is already the second case, and
there might be more, so let's redefine APT_CONST to use
the pure attribute, so we don't end up with the same
situation again in some time.
Release 1.5~beta22017-08-17T17:28:24ZJulian Andres Klodejak@debian.org2017-08-17T17:28:24Zurn:sha1:d64ef1c36b2885f1f178f5438c1a4f67f8bdee88doc: Fix validity error in apt_auth.conf.5.xml2017-08-17T17:26:35ZJulian Andres Klodejak@debian.org2017-08-17T17:26:35Zurn:sha1:ea7581c9aaaaebf844d00935a1cdf8c8fee7f7f3
It contained raw text inside a refsect1
Gbp-Dch: ignore
debian: Update symbols for libapt-pkg5.02017-08-17T15:36:19ZJulian Andres Klodejak@debian.org2017-08-17T15:36:19Zurn:sha1:550907ac0e1c1337686cb30c0a05bce9690d3d59
The version is probably wrong for most, but oh well,
let's just pretend we are introducing them now.
Handle GCC 7 std::string operator ABI break2017-08-17T14:16:43ZJulian Andres Klodejak@debian.org2017-08-17T13:37:49Zurn:sha1:f63b3e01e436a8c0b4711b69a1a8794161e4c5a7
We now require gcc 7 on the packaging side, and add an appropriate
symbol to our symbols file.
Also adjust prepare-release to ignore g++ version requirements
when setting up build dependencies on CI.
Closes: #871275
Work around float rounding change in gcc 7 on i3862017-08-12T14:03:26ZJulian Andres Klodejak@debian.org2017-08-12T14:02:45Zurn:sha1:79c0a12d5c2d4fd8e6bfcf3a632a452239c07fe0
This caused a build failure in the test suite.
don't hang if multiple sources use unavailable method2017-08-04T12:33:34ZDavid Kalnischkiesdavid@kalnischkies.de2017-08-04T10:51:34Zurn:sha1:e250a8d8d8ef2f8f8c5e2041f7645c49fba7aa36
APT clients always noticed if a method isn't supported and nowadays
generate a message of the form:
E: The method driver …/foobar could not be found.
N: Is the package apt-transport-foobar installed?
This only worked if a single source was using such an unavailable method
through as we were registering the failed config the first round and
the second would try to send requests to the not started method, which
wouldn't work and hang instead (+ hiding the error messages as they would
be shown only at the end of the execution).
Closes: 870675