<feed xmlns='http://www.w3.org/2005/Atom'>
<title>apt/apt-pkg/contrib, branch 1.3_exp2</title>
<subtitle>Debians commandline package manager</subtitle>
<id>https://git.kalnischkies.de/apt/atom?h=1.3_exp2</id>
<link rel='self' href='https://git.kalnischkies.de/apt/atom?h=1.3_exp2'/>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/'/>
<updated>2016-06-10T08:49:41Z</updated>
<entry>
<title>don't leak FD in AutoProxyDetect command return parsing</title>
<updated>2016-06-10T08:49:41Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2016-06-09T22:01:46Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=8f858d560e3b7b475c623c4e242d1edce246025a'/>
<id>urn:sha1:8f858d560e3b7b475c623c4e242d1edce246025a</id>
<content type='text'>
Just closing the fd would be enough, but while we are at it we can also
use the Popen interface to have an easier time with this.
</content>
</entry>
<entry>
<title>don't leak an FD in lz4 (de)compression</title>
<updated>2016-06-10T08:49:34Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2016-06-09T19:06:48Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=6f35be91c9e86e463bca7df6eadf05412c7b732c'/>
<id>urn:sha1:6f35be91c9e86e463bca7df6eadf05412c7b732c</id>
<content type='text'>
Seen first in #826783, but as this buglog also shows leaked uncompressed
files as well we don't close it just yet.
</content>
</entry>
<entry>
<title>do not hang on piped input in PipedFileFdPrivate</title>
<updated>2016-06-10T08:48:25Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2016-06-09T18:41:58Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=bdc42211700ef0f6f40e4ef3f362e52d684d70fb'/>
<id>urn:sha1:bdc42211700ef0f6f40e4ef3f362e52d684d70fb</id>
<content type='text'>
This effects only compressors configured on the fly (rather then the
inbuilt ones as they use a library).
</content>
</entry>
<entry>
<title>use de-localed std::put_time instead rolling our own</title>
<updated>2016-05-28T10:55:21Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2016-05-28T10:55:21Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=eceb219c2a64f3f81421c3c6587380b6ae81a530'/>
<id>urn:sha1:eceb219c2a64f3f81421c3c6587380b6ae81a530</id>
<content type='text'>
</content>
</entry>
<entry>
<title>accept only the expected UTC timezones in date parsing</title>
<updated>2016-05-28T09:42:20Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2016-05-28T09:03:35Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=9febc2b238e1e322dce1f94ecbed46d595893b52'/>
<id>urn:sha1:9febc2b238e1e322dce1f94ecbed46d595893b52</id>
<content type='text'>
HTTP/1.1 hardcodes GMT (RFC 7231 §7.1.1.1) and what is good enough for the
internet must be good enough for us™ as we reuse the implementation
internally to parse (most) dates we encounter in various places like the
Release files with their Date and Valid-Until header fields.

Implementing a fully timezone aware parser just feels too hard for no
effective benefit as it would take 5+ years (= until LTS's are out of
fashion) until a repository could use non-UTC dates and expect it to
work. Not counting non-apt implementations which might or might not
only want to encounter UTC here as well.

As a bonus, this eliminates the use of an instance of setlocale in
libapt.

Closes: 819697
</content>
</entry>
<entry>
<title>prevent C++ locale number formatting in text APIs</title>
<updated>2016-05-27T17:14:38Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2016-05-27T16:10:39Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=b58e2c7c56b1416a343e81f9f80cb1f02c128e25'/>
<id>urn:sha1:b58e2c7c56b1416a343e81f9f80cb1f02c128e25</id>
<content type='text'>
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
</content>
</entry>
<entry>
<title>edsp: try harder to not generate unneeded error messages</title>
<updated>2016-05-20T12:18:36Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2016-04-27T11:44:08Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=4e92b11649292714082754920d5b28477414cd5a'/>
<id>urn:sha1:4e92b11649292714082754920d5b28477414cd5a</id>
<content type='text'>
The &amp;= introduced in the EDSP-FileFd conversion isn't working to full
satisfaction for multiple &amp;&amp; clauses as the &amp;&amp; has a higher binding than
&amp;= has, so that the methods were called even through they shouldn't
have because of previous errors. Using variadic functions we can solve
this in a slightly cleaner way bringing down the amount of 'broken pipe'
errors for the error case of the dump resolver substantially.

Git-Dch: Ignore
</content>
</entry>
<entry>
<title>convert EDSP to be based on FileFd instead of FILE*</title>
<updated>2016-05-20T12:18:36Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2016-04-26T10:26:12Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=ef00bd7af5b2bc0625df58482eacb4c2873c3647'/>
<id>urn:sha1:ef00bd7af5b2bc0625df58482eacb4c2873c3647</id>
<content type='text'>
I doubt there is any non-src:apt usage of these interfaces.
</content>
</entry>
<entry>
<title>Merge pull request julian-klode/apt#3 from adrian17/master</title>
<updated>2016-05-10T16:32:06Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2016-05-10T16:32:06Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=a9c2517e9ce961a761022dfa8eb0b62f68f5df9e'/>
<id>urn:sha1:a9c2517e9ce961a761022dfa8eb0b62f68f5df9e</id>
<content type='text'>
Improve GetLocalitySortedVersionSet, speeds up apt search by 30%
</content>
</entry>
<entry>
<title>remove 100-levels config nesting limit</title>
<updated>2016-05-03T11:49:45Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2016-05-02T16:18:37Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=6afe25b56467b228fdd7c045d1062b12c0408e7c'/>
<id>urn:sha1:6afe25b56467b228fdd7c045d1062b12c0408e7c</id>
<content type='text'>
The actual reason for this commit isn't the limit – there isn't much
point in using that much nesting – its in shutting up gcc mostly:

apt/apt-pkg/contrib/configuration.cc: In function ‘bool ReadConfigFile(Configuration&amp;, const string&amp;, const bool&amp;, const unsigned int&amp;)’:
apt/apt-pkg/contrib/configuration.cc:686:20: warning: cannot optimize loop, the loop counter may overflow [-Wunsafe-loop-optimizations]
    string Stack[100];
                    ^
by replacing this with C++s handy std::stack container (adapter).
Also cleans some whitespace noise from the file in the process.
</content>
</entry>
</feed>
