<feed xmlns='http://www.w3.org/2005/Atom'>
<title>apt/apt-pkg, branch 2.3.8</title>
<subtitle>Debians commandline package manager</subtitle>
<id>https://git.kalnischkies.de/apt/atom?h=2.3.8</id>
<link rel='self' href='https://git.kalnischkies.de/apt/atom?h=2.3.8'/>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/'/>
<updated>2021-07-28T11:08:35Z</updated>
<entry>
<title>Add support for a maximum delay and testing of delay</title>
<updated>2021-07-28T11:08:35Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2021-07-28T10:43:56Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=4001af8920389e2bb2672b673b181c4e92515872'/>
<id>urn:sha1:4001af8920389e2bb2672b673b181c4e92515872</id>
<content type='text'>
This is very basic support on the testing side, we just test
the debug output but not how long it actually took. Would be
nice to check time really.
</content>
</entry>
<entry>
<title>Properly convert PulseInterval to timeval</title>
<updated>2021-07-28T11:08:35Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2021-07-27T15:14:23Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=51ee79e385d8ccb2f32195cc01f3f9c943197603'/>
<id>urn:sha1:51ee79e385d8ccb2f32195cc01f3f9c943197603</id>
<content type='text'>
Fix the typo, and use the helper function to convert it, so we
do not end up with 5 seconds encoded as 0s and 5*10^6 microseconds.
</content>
</entry>
<entry>
<title>Convert to monotonic clock</title>
<updated>2021-07-28T11:08:35Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2021-07-27T14:40:38Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=48a7ece8d0e065240153a85089f544383e16137f'/>
<id>urn:sha1:48a7ece8d0e065240153a85089f544383e16137f</id>
<content type='text'>
This yields more accurate delays and avoids issues with clock
skew.
</content>
</entry>
<entry>
<title>acquire: Automatically reduce select() timeout as needed</title>
<updated>2021-07-28T11:08:32Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2021-07-13T10:21:23Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=7e88def0548a92112f8295686c2a12379e4028be'/>
<id>urn:sha1:7e88def0548a92112f8295686c2a12379e4028be</id>
<content type='text'>
If there is an item with fetchAfter at the top of a queue,
reduce sleep() timeout so we can detect it and start it,
by calling Cycle() on the queue in the next iteration.

For some reasons we have to call select() with a 0s timeout
if we just marked an item as ready. Oh well.

Previous versions of this patch only called global Bump() after a timeout
from select(); this was unfortunately incorrect - it meant that we
never bumped a queue that did not start yet while other queues were
running, potentially significantly delaying retries.
</content>
</entry>
<entry>
<title>Implement exponential delay between retries</title>
<updated>2021-07-28T11:04:10Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2021-07-08T14:49:20Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=121ccd0e0c2612bab9ba5383d5599b54e29e4643'/>
<id>urn:sha1:121ccd0e0c2612bab9ba5383d5599b54e29e4643</id>
<content type='text'>
Add a new Item field called FetchAfter, which determines the earliest
time the item should be fetched at. Adjust insertion into queue to
take it into account alongside priority, and only fill pipelines
with items that are ready.
</content>
</entry>
<entry>
<title>pkgAcqIndex::CommonFailed: Set StatIdle before calling Init()</title>
<updated>2021-07-13T14:16:55Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2021-07-13T14:03:06Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=363e3a4c91da353d99cf1af3d5089c9455d461de'/>
<id>urn:sha1:363e3a4c91da353d99cf1af3d5089c9455d461de</id>
<content type='text'>
Enqueuing by calling Init(), and then resetting the status to
idle means that the item can get enqueued twice if we call
Cycle() from inside pkgAcquire::Run().

Reset the status to StatIdle before calling Init()
</content>
</entry>
<entry>
<title>Merge branch 'fix/dpkgchroot' into 'main'</title>
<updated>2021-07-05T09:50:05Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2021-07-05T09:50:05Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=544d81a26f8c97a2a45262aecbaef4a5b43fb325'/>
<id>urn:sha1:544d81a26f8c97a2a45262aecbaef4a5b43fb325</id>
<content type='text'>
Restore dpkg::chroot-directory functionality

See merge request apt-team/apt!178</content>
</entry>
<entry>
<title>Restore dpkg::chroot-directory functionality</title>
<updated>2021-06-10T17:25:17Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2021-06-10T16:06:14Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=8083d4019844f764058efa2a950ed16975178bff'/>
<id>urn:sha1:8083d4019844f764058efa2a950ed16975178bff</id>
<content type='text'>
If we call dpkg inside a chroot we have to ensure that the temporary
directory we construct to call dpkg --recursive is inside the chroot and
that we strip the path to the chroot from the directory name we pass to
dpkg.

Note that the added test succeeds before and (hopefully) after as we
can't really chroot here or fiddle with the needed settings as we are
already setting up apt to work with a quasi-chroot. The test perhaps
helps in ensuring we don't break it too much in the future though.

(Broken five years (and one day) ago this seems to have an immense user
 base at the moment, but it might in the future via mmdebstrap)

References: f495992428a396e0f98886c9a761a804aa161c68
Reported-By: Johannes Schauer Marin Rodrigues on IRC
Tested-By: Johannes Schauer Marin Rodrigues
</content>
</entry>
<entry>
<title>Store size from volatile sources for already installed versions</title>
<updated>2021-06-10T10:58:24Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2021-06-10T10:58:24Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=7adecd8b2543fc8ee5288b91525a366cf9525cb8'/>
<id>urn:sha1:7adecd8b2543fc8ee5288b91525a366cf9525cb8</id>
<content type='text'>
Volatile sources are parsed after the status file, so if we have a
version already installed the size information is not stored, so that
a reinstall of said version is refused claiming a broken repository.

References: 1412cf51403286e9c040f9f86fd4d8306e62aff2
</content>
</entry>
<entry>
<title>Use full item description in broken repo error</title>
<updated>2021-06-10T10:51:45Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2021-06-10T10:51:45Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=e45417c4767c2e54def08f52d55350ed0651d95a'/>
<id>urn:sha1:e45417c4767c2e54def08f52d55350ed0651d95a</id>
<content type='text'>
The error says the repository is broken but doesn't mention which one it
is. The item description gives us at least all the information, but is
not as nicely formatted. As this message is not even marked for
translation this is a rather temporary affair and we can survive without
the eye candy for a while.
</content>
</entry>
</feed>
