apt, branch 1.5_beta2Debians commandline package managerhttps://git.kalnischkies.de/apt/atom?h=1.5_beta22017-08-17T17:28:24ZRelease 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
don't keep configuration files open needlessly2017-08-04T11:06:10ZDavid Kalnischkiesdavid@kalnischkies.de2017-07-31T20:47:58Zurn:sha1:898d53aca8fb26f3861d0efa4d5bef8adb620a7c
Regression-Of: 3317ad864c997f4897756c0a2989c4199e9cda62
ftparchive: sort discovered filenames before writing indexes2017-08-04T11:06:10ZDavid Kalnischkiesdavid@kalnischkies.de2017-07-28T16:20:14Zurn:sha1:d108e019d3ca74c31a1ab646ddef5c60744a5e7d
If 'apt-ftparchive packages /path/to/files/' (or sources) is used the
files to include in the generated index (on stdout) were included in the
order in which they were discovered, which isn't a very stable order
which could lead to indexes changing without actually changing content
causing needless changes in the repository changing hashsums, pdiffs,
rsyncs, downloads, ….
This does not effect apt-ftparchive calls which already have an order
defined via a filelist (like generate) which will still print in the
order given by the filelist.
Note that a similar effect can be achieved by post-processing index
files with apt-sortpkgs.
Closes: 869557
Thanks: Chris Lamb for initial patch & Stefan Lippers-Hollmann for testing
Always warn if --force-yes is validly specified, not just if used2017-07-27T13:47:59ZJulian Andres Klodejak@debian.org2017-07-27T13:47:59Zurn:sha1:eb0ccb003ceedac0fd78fee05d7b8119dd04c48b
The code only used to warn when it came into a situation where
something actually had to be forced. Warn directly after parsing
the command-line instead, that's more accurate.
doc: Add '--allow-unauthenticated' to '--force-yes'2017-07-27T10:54:25ZDominikDominik-K@users.noreply.github.com2017-07-27T10:38:32Zurn:sha1:e1d66c94e6ed6d79ba0f089fc00789bf7fd161d8