<feed xmlns='http://www.w3.org/2005/Atom'>
<title>apt/cmdline/apt-cache.cc, branch 1.4.3</title>
<subtitle>Debians commandline package manager</subtitle>
<id>https://git.kalnischkies.de/apt/atom?h=1.4.3</id>
<link rel='self' href='https://git.kalnischkies.de/apt/atom?h=1.4.3'/>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/'/>
<updated>2016-07-02T10:01:17Z</updated>
<entry>
<title>use +0000 instead of UTC by default as timezone in output</title>
<updated>2016-07-02T10:01:17Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2016-07-02T09:28:42Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=0b45b6e5de1ba4224ced67a9952e009d0f4139a0'/>
<id>urn:sha1:0b45b6e5de1ba4224ced67a9952e009d0f4139a0</id>
<content type='text'>
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.
</content>
</entry>
<entry>
<title>look into the right textdomain for apt-utils again</title>
<updated>2016-05-28T16:12:02Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2016-05-28T11:53:09Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=570ec96dbf4f720d8eff694f8c4429e0b0a033b4'/>
<id>urn:sha1:570ec96dbf4f720d8eff694f8c4429e0b0a033b4</id>
<content type='text'>
Broken in e7e10e47476606e3b2274cf66b1e8ea74b236757 by looking always
into "apt" while we ship some tools in "apt-utils"…
</content>
</entry>
<entry>
<title>apt-cache: stats: Show a table utilization as percentage</title>
<updated>2016-01-03T16:42:17Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2016-01-03T16:39:39Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=38a5b1ceeeca6ff530a2816a39bcd10d14c85d33'/>
<id>urn:sha1:38a5b1ceeeca6ff530a2816a39bcd10d14c85d33</id>
<content type='text'>
Gbp-Dch: ignore
</content>
</entry>
<entry>
<title>apt-cache: stats: Average is over used, not all, buckets</title>
<updated>2016-01-03T16:34:50Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2016-01-03T16:34:50Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=6d7fc45ed4e22163bba6478c7523f4509d200c58'/>
<id>urn:sha1:6d7fc45ed4e22163bba6478c7523f4509d200c58</id>
<content type='text'>
It does not make sense to consider empty buckets in the
average, as they do not affect the lookup performance.
</content>
</entry>
<entry>
<title>drop some needlessly public declarations in libapt-private</title>
<updated>2015-11-29T16:00:11Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2015-11-29T15:57:58Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=f6777222f82f6279c104138216b0e5e50d8caa67'/>
<id>urn:sha1:f6777222f82f6279c104138216b0e5e50d8caa67</id>
<content type='text'>
Git-Dch: Ignore
</content>
</entry>
<entry>
<title>move 'unmet' handling into libapt-private</title>
<updated>2015-11-29T14:49:55Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2015-11-29T14:49:55Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=0a778f71f935900ff8a90a958f0e7da700d84f9f'/>
<id>urn:sha1:0a778f71f935900ff8a90a958f0e7da700d84f9f</id>
<content type='text'>
Git-Dch: Ignore
</content>
</entry>
<entry>
<title>use function pointers instead of weak symbols for cmdline parsing</title>
<updated>2015-11-29T12:12:38Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2015-11-29T12:12:38Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=90986d4dbbd38e2e89f986d621e301304210452e'/>
<id>urn:sha1:90986d4dbbd38e2e89f986d621e301304210452e</id>
<content type='text'>
Passing function pointers around while working on this was very icky,
but if weak symbols are too much to ask for…

Reverts "do not use "-Wl,-Bsymbolic-functions" during the build to avoid
breakage" aka a5fc9be36211a290a7abc3ca2a8bf98943bc1f57.
</content>
</entry>
<entry>
<title>review of new/changed translatable program strings</title>
<updated>2015-11-21T17:04:29Z</updated>
<author>
<name>Justin B Rye</name>
<email>justin.byam.rye@gmail.com</email>
</author>
<published>2015-11-21T16:50:06Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=d04e44ac8177fc5b70ae0189bb5e437c2502f910'/>
<id>urn:sha1:d04e44ac8177fc5b70ae0189bb5e437c2502f910</id>
<content type='text'>
Reference mail:
https://lists.debian.org/debian-l10n-english/2015/11/msg00006.html
</content>
</entry>
<entry>
<title>revamp all tools help messages</title>
<updated>2015-11-04T17:04:05Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2015-10-27T08:57:26Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=8561c2fedae26aecd8ba758a5e7ef686ba1243f3'/>
<id>urn:sha1:8561c2fedae26aecd8ba758a5e7ef686ba1243f3</id>
<content type='text'>
The general idea is: A small paragraph on the tool itself as a
description, a list of the most used (!= all) commands available in the
tool, a remark where to find more information on the tool and its
commands (aka: in the manpage) and finally a common block referring to
even more manpages. In exchange options are completely omitted from the
output as well as deprecated or obscure commands. (Better) Information
about them is available in the manpages anyway and the few options which
were listed before were also the least interesting ones (-o -c -q and co
are hardly of interest for someone totally new looking to find info by
asking for help and anyone with a bit of experience doesn't need this
short list. Those would need a list of options applying to the command
they call, but they are too numerous and command specific to list them
sanely in this context.
</content>
</entry>
<entry>
<title>hidden support more apt-get/apt-cache commands in apt</title>
<updated>2015-11-04T17:04:04Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2015-10-26T18:30:44Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=9055d5e68bd09f31df00e45bd14cb599ba3735e5'/>
<id>urn:sha1:9055d5e68bd09f31df00e45bd14cb599ba3735e5</id>
<content type='text'>
apt is supposed to be a user-friendly interface, so while these commands
are usually poweruser material and therefore do not need to be shown in
general introduction manpages/help messages its of no use to not allow
users to use them.

This includes clean, autoclean, build-dep, source, download, changelog,
depends, rdepends and showsrc – it doesn't include more non-interactive
commands like dump or xvcg as those are usually used by scripts if at
all.

Closes: 778234, 780700, 781237
</content>
</entry>
</feed>
