<feed xmlns='http://www.w3.org/2005/Atom'>
<title>apt/debian, branch 2.4.5</title>
<subtitle>Debians commandline package manager</subtitle>
<id>https://git.kalnischkies.de/apt/atom?h=2.4.5</id>
<link rel='self' href='https://git.kalnischkies.de/apt/atom?h=2.4.5'/>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/'/>
<updated>2022-04-08T10:23:25Z</updated>
<entry>
<title>Release 2.4.5</title>
<updated>2022-04-08T10:23:25Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2022-04-08T10:22:37Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=72782263dc1e2f65a1ef02f490d897abdcc9885d'/>
<id>urn:sha1:72782263dc1e2f65a1ef02f490d897abdcc9885d</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Only protect two kernels, not last installed one</title>
<updated>2022-04-07T11:19:52Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2022-04-06T11:51:08Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=824651ded0bcf8603e9b508860b8fe5a68fc53ff'/>
<id>urn:sha1:824651ded0bcf8603e9b508860b8fe5a68fc53ff</id>
<content type='text'>
The kernel autoremoval algorithm was written to accomodate
for Ubuntu's boot partition sizing, which was written to
accomodate 3 kernels - 2 installed ones + a new one being
unpacked.

It seems that when the algorithm was designed, it was overlooked
that it actually kept 3 kernels.

LP: #1968154
</content>
</entry>
<entry>
<title>Release 2.4.4</title>
<updated>2022-04-01T16:52:30Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2022-04-01T16:52:30Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=023c270e27e09cad9f35908caeb933fb23f8bd79'/>
<id>urn:sha1:023c270e27e09cad9f35908caeb933fb23f8bd79</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Release 2.4.3</title>
<updated>2022-03-21T08:22:54Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2022-03-21T08:22:54Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=d29cffc53095c9b5929b6ad45ed98aae330315e0'/>
<id>urn:sha1:d29cffc53095c9b5929b6ad45ed98aae330315e0</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Release 2.4.2</title>
<updated>2022-03-17T08:18:16Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2022-03-17T08:17:39Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=d1d899f56f365178ad9f2d5073f36dc5af8226bc'/>
<id>urn:sha1:d1d899f56f365178ad9f2d5073f36dc5af8226bc</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Revert "bugscript: switch from bash to POSIX shell"</title>
<updated>2022-03-12T11:19:55Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2022-03-12T11:19:55Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=1edd8c323faa5bf8c78d478f6c0b51116d50d422'/>
<id>urn:sha1:1edd8c323faa5bf8c78d478f6c0b51116d50d422</id>
<content type='text'>
This reverts commit 4f89d3629b22255963da3705e4222c71045da58a.

The bugscript uses yesno which is documented to require bash in
/usr/share/doc/reportbug/README.developers.gz.

Closes: #1007121
</content>
</entry>
<entry>
<title>Release 2.4.1</title>
<updated>2022-03-07T13:06:40Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2022-03-07T13:06:40Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=ba08336ba208556de89f945aefc7b83f0f713c93'/>
<id>urn:sha1:ba08336ba208556de89f945aefc7b83f0f713c93</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Document the APT::Periodic interval suffixes and "always" value</title>
<updated>2022-03-02T10:27:17Z</updated>
<author>
<name>Paul Wise</name>
<email>pabs@debian.org</email>
</author>
<published>2022-03-01T00:28:39Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=c6f016200291e7e719f15de4f9a6ad9596c5110b'/>
<id>urn:sha1:c6f016200291e7e719f15de4f9a6ad9596c5110b</id>
<content type='text'>
Without documentation these options will see much less use.

Fixes: commit 1d9e29c9e2a5591b42a99a721b901fc003ed9149
Suggested-by: kibi on #debian-devel
</content>
</entry>
<entry>
<title>Release 2.4.0</title>
<updated>2022-02-22T19:01:41Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2022-02-22T19:01:41Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=409ee5821500f140896715a516ec8ffa008de789'/>
<id>urn:sha1:409ee5821500f140896715a516ec8ffa008de789</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Warn if the legacy trusted.gpg keyring is used for verification</title>
<updated>2022-02-22T17:25:06Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2022-01-07T11:43:32Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=56adf743b02b80a9acc9a2e480bfd15acb94f755'/>
<id>urn:sha1:56adf743b02b80a9acc9a2e480bfd15acb94f755</id>
<content type='text'>
With apt-key going away, people need to manage key files, rather
than keys, so they need to know if any keys are in the legacy keyring.
</content>
</entry>
</feed>
