<feed xmlns='http://www.w3.org/2005/Atom'>
<title>apt/apt-pkg, branch 1.2.3</title>
<subtitle>Debians commandline package manager</subtitle>
<id>https://git.kalnischkies.de/apt/atom?h=1.2.3</id>
<link rel='self' href='https://git.kalnischkies.de/apt/atom?h=1.2.3'/>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/'/>
<updated>2016-02-10T12:03:00Z</updated>
<entry>
<title>get dpkg lock in build-dep if cache was invalid again</title>
<updated>2016-02-10T12:03:00Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2016-02-10T11:26:49Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=b6f1b480164b454661ddd4fdd3968302c6a3ebf6'/>
<id>urn:sha1:b6f1b480164b454661ddd4fdd3968302c6a3ebf6</id>
<content type='text'>
Regression introduced in a249b3e6fd798935a02b769149c9791a6fa6ef16, which
in the case of an invalid cache would build the first part unlocked and
later pick up the (still unlocked) cache for further processing, so the
system got never locked and apt would end up complaining about being
unable to release the lock at shutdown.

The far more common case of having a valid cache worked as expected and
hence covered up the problem – especially as tests who would have
noticed it are simulations only, which do not lock.

Closes: 814139
Reported-By: Balint Reczey &lt;balint@balintreczey.hu&gt;
Reported-By: Helmut Grohne &lt;helmut@subdivi.de&gt; on IRC
</content>
</entry>
<entry>
<title>Set seekpos to 0 after reopening files in Seek()</title>
<updated>2016-02-10T11:48:37Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2016-02-10T11:45:47Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=eda0c1ba43cd3ae0ed85aba2c31573f156cec9c4'/>
<id>urn:sha1:eda0c1ba43cd3ae0ed85aba2c31573f156cec9c4</id>
<content type='text'>
If we just reopened the file, we also need to reset the current
seek position when we reset the buffer, otherwise the code will
not try to seek to the position given to Skip (from 0), but will
try to seek to old offset + the position given to skip.

Closes: #812994, #813000
</content>
</entry>
<entry>
<title>Use some semantically more correct buffer operations</title>
<updated>2016-02-04T17:34:42Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2016-02-04T17:33:30Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=72ed5f14b558984bd9c5731f82345b10cb2df2ca'/>
<id>urn:sha1:72ed5f14b558984bd9c5731f82345b10cb2df2ca</id>
<content type='text'>
When writing into the buffer write to free() bytes starting
at getend(), instead of buffersize_max bytes at get()
-&gt; get() is a read pointer.

This makes no difference in practice though, as we reset
the buffer before the call, so start = end = 0.

Gbp-Dch: ignore
</content>
</entry>
<entry>
<title>Correctly report write errors when flushing buffered writer</title>
<updated>2016-02-04T17:00:42Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2016-02-04T17:00:42Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=1996a6a785a54efaeddb4ecf5e88fa6070330182'/>
<id>urn:sha1:1996a6a785a54efaeddb4ecf5e88fa6070330182</id>
<content type='text'>
We cannot just return false without setting an error,
as InternalWrite does not set one itself.
</content>
</entry>
<entry>
<title>Merge branch 'master' of github.com:adrian17/apt</title>
<updated>2016-02-04T00:08:50Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2016-02-04T00:08:50Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=9ffba52025237c89bcca5de06722729172fe1aea'/>
<id>urn:sha1:9ffba52025237c89bcca5de06722729172fe1aea</id>
<content type='text'>
</content>
</entry>
<entry>
<title>edspsystem.cc: include &lt;stdlib.h&gt; for mkdtemp</title>
<updated>2016-02-03T22:46:19Z</updated>
<author>
<name>Fredrik Fornwall</name>
<email>fredrik@fornwall.net</email>
</author>
<published>2015-12-07T23:48:50Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=ef72d726399763446f31a07b11f30f6a726ea81a'/>
<id>urn:sha1:ef72d726399763446f31a07b11f30f6a726ea81a</id>
<content type='text'>
Include &lt;stdlib.h&gt; to ensure that mkdtemp(3) is defined to improve
general portability and fix a specific build failure on Android.

Closes: #807367
</content>
</entry>
<entry>
<title>Avoid temporary strings in SubstVar.</title>
<updated>2016-02-03T14:54:10Z</updated>
<author>
<name>Adrian Wielgosik</name>
<email>adrian.wielgosik@gmail.com</email>
</author>
<published>2016-02-02T22:15:25Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=732510fef9af5addc5e3ff1a79ce8c9658711fb6'/>
<id>urn:sha1:732510fef9af5addc5e3ff1a79ce8c9658711fb6</id>
<content type='text'>
Microoptimization, but still gives a measurable 2-3% improvement
when using commands with lots of output like `apt list`.
</content>
</entry>
<entry>
<title>Do not buffer writes larger than the buffer if possible</title>
<updated>2016-02-01T15:50:48Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2016-02-01T15:46:53Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=f1828e6b0adb87bf0b99d3cfeeafbb76cbc6aab7'/>
<id>urn:sha1:f1828e6b0adb87bf0b99d3cfeeafbb76cbc6aab7</id>
<content type='text'>
It makes no sense to split a large block into multiple small
blocks, so when we have the chance to write them unbuffered,
do so.
</content>
</entry>
<entry>
<title>BufferedWriteFileFdPrivate: Simplify InternalWrite()</title>
<updated>2016-02-01T15:29:13Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2016-02-01T15:28:43Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=070ed1c9147c092c1f944afd1c17c51f651a5c39'/>
<id>urn:sha1:070ed1c9147c092c1f944afd1c17c51f651a5c39</id>
<content type='text'>
We do not need the loop, FileFd::Private() handles this for us.

Gbp-Dch: ignore
</content>
</entry>
<entry>
<title>simple_buffer::write: Use free() instead of maxsize - size()</title>
<updated>2016-02-01T15:25:03Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2016-02-01T15:25:03Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=47fcfff8a50caebe3cd1f2ee19875a2ca8bbeadc'/>
<id>urn:sha1:47fcfff8a50caebe3cd1f2ee19875a2ca8bbeadc</id>
<content type='text'>
We want to check whether the amount of free space is smaller
than the requested write size. Checking maxsize - size() is
incorrect for bufferstart &gt;= 0, as size() = end - start.

Gbp-Dch: ignore
</content>
</entry>
</feed>
