apt/ftparchive, branch 1.3_pre3Debians commandline package managerhttps://git.kalnischkies.de/apt/atom?h=1.3_pre32016-07-02T10:01:17Zuse +0000 instead of UTC by default as timezone in output2016-07-02T10:01:17ZDavid Kalnischkiesdavid@kalnischkies.de2016-07-02T09:28:42Zurn:sha1:0b45b6e5de1ba4224ced67a9952e009d0f4139a0
All apt versions support numeric as well as 3-character timezones just
fine and its actually hard to write code which doesn't "accidently"
accepts it. So why change? Documenting the Date/Valid-Until fields in
the Release file is easy to do in terms of referencing the
datetime format used e.g. in the Debian changelogs (policy §4.4). This
format specifies only the numeric timezones through, not the nowadays
obsolete 3-character ones, so in the interest of least surprise we should
use the same format even through it carries a small risk of regression
in other clients (which encounter repositories created with
apt-ftparchive).
In case it is really regressing in practice, the hidden option
-o APT::FTPArchive::Release::NumericTimezone=0
can be used to go back to good old UTC as timezone.
The EDSP and EIPP protocols use this 'new' format, the text interface
used to communicate with the acquire methods does not for compatibility
reasons even if none of our methods would be effected and I doubt any
other would (in these instances the timezone is 'GMT' as that is what
HTTP/1.1 requires). Note that this is only true for apt talking to
methods, (libapt-based) methods talking to apt will respond with the
'new' format. It is therefore strongly adviced to support both also in
method input.
Revert "travis: use gcc-5 instead of gcc(-4.8)"2016-06-29T10:23:02ZDavid Kalnischkiesdavid@kalnischkies.de2016-06-29T09:00:04Zurn:sha1:cfc6566d5097ef5518e12f5c1e5f15a8f5b182cf
This reverts commit 2b8221d66a8284042fc53c7bbb14bb9750e9137f.
Avoiding the use of GCC >= 5 stuff lets use go back to 4.8 simplifying
the travis setup again as well as reducing the backport requirements in
general.
This is possible because the std::get_time use requiring GCC >= 5 in
9febc2b238e1e322dce1f94ecbed46d595893b52 was replaced by handrolling it
in 1d742e01470bba27715a8191c50adde4b39c2f19, so the remaining uses are
just small conviniences we can do without.
Gbp-Dch: Ignore
Check for cached hash entries to determine which (if any) hash types2016-06-20T12:47:46ZDominic Bensondominic@dgeb.net2016-06-20T12:47:46Zurn:sha1:51018e947ab1df3ddba5d7a84ed2284d599d8a12
need to be generated for the current file.
In 1.0.9, each hash type was handled by a separate method, each of
which checked the cache. It looks like when these code paths were
unified (in a311fb96b84757ef8628e6a754232614a53b7891) the cache
checks were not incorporated into the new method.
look into the right textdomain for apt-utils again2016-05-28T16:12:02ZDavid Kalnischkiesdavid@kalnischkies.de2016-05-28T11:53:09Zurn:sha1:570ec96dbf4f720d8eff694f8c4429e0b0a033b4
Broken in e7e10e47476606e3b2274cf66b1e8ea74b236757 by looking always
into "apt" while we ship some tools in "apt-utils"…
avoid changing the global LC_TIME for Release writing2016-05-28T10:46:37ZDavid Kalnischkiesdavid@kalnischkies.de2016-05-28T10:41:12Zurn:sha1:e0b01a85bd8395449a88e1806ea4a4e3acdbac33
Using C++ here avoids calling setlocale here which never really was that
ideal, but needed to avoid locale specific weekday/month names.
prevent C++ locale number formatting in text APIs2016-05-27T17:14:38ZDavid Kalnischkiesdavid@kalnischkies.de2016-05-27T16:10:39Zurn:sha1:b58e2c7c56b1416a343e81f9f80cb1f02c128e25
Setting the C++ locale via std::locale::global(std::locale("")); which
would otherwise default to the default C locale (aka: unaffected by
setlocale) effects the formatting of numeric types in IO streams, which
for output for humans is perfectly sensible, but breaks our many text
interfaces used and parsed by us and others without expecting the
numbers to be formatted.
Closes: #825396
ftparchive: Support writing Signed-By fields2016-05-01T09:38:44ZJulian Andres Klodejak@debian.org2016-05-01T09:38:44Zurn:sha1:79fe74283ca8c941806085a3ae1bacfac2287d1cadd dep11 files to default Release patterns2016-04-25T13:35:52ZDavid Kalnischkiesdavid@kalnischkies.de2016-04-05T18:37:57Zurn:sha1:6d9b79dd961242702f0079e3dab2dd1c62bbc61einclude all compressed Packages/Sources files in Release file2016-01-08T14:40:01ZDavid Kalnischkiesdavid@kalnischkies.de2016-01-02T22:15:15Zurn:sha1:83758aed35c3eec66008b2ec01957c8e1cb129b5
Having a hardcoded list of compression types here doesn't really provide
us with anything beside added complexity each time someone adds a new
compression type. That we don't need to be that specific is evident by
Contents and Translation-* matchers which are a lot more generic and
didn't generate problems anyhow.
drop some needlessly public declarations in libapt-private2015-11-29T16:00:11ZDavid Kalnischkiesdavid@kalnischkies.de2015-11-29T15:57:58Zurn:sha1:f6777222f82f6279c104138216b0e5e50d8caa67
Git-Dch: Ignore