<feed xmlns='http://www.w3.org/2005/Atom'>
<title>apt/apt-pkg, branch 2.7.11</title>
<subtitle>Debians commandline package manager</subtitle>
<id>https://git.kalnischkies.de/apt/atom?h=2.7.11</id>
<link rel='self' href='https://git.kalnischkies.de/apt/atom?h=2.7.11'/>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/'/>
<updated>2024-02-13T13:28:06Z</updated>
<entry>
<title>Add the ?security pattern</title>
<updated>2024-02-13T13:28:06Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2024-02-13T11:33:51Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=82f4cfc971ef6a2e56b34227d9e0b1a594dc2265'/>
<id>urn:sha1:82f4cfc971ef6a2e56b34227d9e0b1a594dc2265</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Add a new ?phasing pattern</title>
<updated>2024-02-13T13:28:06Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2024-02-13T11:29:28Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=422e68f569f374f697b84332f7e68c6fe5f7389f'/>
<id>urn:sha1:422e68f569f374f697b84332f7e68c6fe5f7389f</id>
<content type='text'>
This selects all packages that are being kept back due to phasing
on your system.
</content>
</entry>
<entry>
<title>Add public phased update API</title>
<updated>2024-02-13T13:27:27Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2024-02-12T13:48:48Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=a8352c2859a6f84b36fa5cd0af89231cb656b1ce'/>
<id>urn:sha1:a8352c2859a6f84b36fa5cd0af89231cb656b1ce</id>
<content type='text'>
This moves the functions of the PhasedUpgrader class into
various other classes so they can be publicly exposed.

This introduces three new functions:

pkgDepCache::PhasingApplied() tells you whether phasing should
be applied to the package.

pkgProblemResolver::KeepPhasedUpdates() keeps back updates that
have phasing applied.

pkgCache::VerIterator::IsSecurityUpdate() determines whether this
version contains security fixes.
</content>
</entry>
<entry>
<title>For phasing, check if current version is a security update, not just previous ones</title>
<updated>2024-02-13T13:13:56Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2024-02-13T12:58:40Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=26e0e9b76fb06afe5250eeb8e5b3d069d4793432'/>
<id>urn:sha1:26e0e9b76fb06afe5250eeb8e5b3d069d4793432</id>
<content type='text'>
We only considered an update a security update if a previous update
is a security update but not the update in question itself.

LP: #2051181
</content>
</entry>
<entry>
<title>pkgcachegen: Use placement new to construct header</title>
<updated>2024-01-12T12:49:24Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2024-01-12T12:47:52Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=0ee745995b1f45ed321b0c20b151ec8e76e4344f'/>
<id>urn:sha1:0ee745995b1f45ed321b0c20b151ec8e76e4344f</id>
<content type='text'>
Avoid copying the header from a stack allocated object as this
will copy uninitialized padding bytes into the cache, triggering
valgrind errors which people then use as a strawman for unrelated
errors on armhf.

In an optimal world we should annotate the allocator however such
that valgrind actually does treat those bytes as uninitialized and
then supress warnings in the harmless places, such that when you
then go and try to access it in a place that matters, you do get
an error for uninitialized memory.

Currently any access within the pool will be considered initialized
which is clearly suboptimal. But this is very much a TBD topic and
involves annotating the allocator everywhere.
</content>
</entry>
<entry>
<title>Merge branch 'fix/dontstorediffindex' into 'main'</title>
<updated>2024-01-08T09:15:34Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2024-01-08T09:15:34Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=6e43eef9ca8250eb561f2c9af2f4890d674f3911'/>
<id>urn:sha1:6e43eef9ca8250eb561f2c9af2f4890d674f3911</id>
<content type='text'>
Do not store .diff_Index files in update

See merge request apt-team/apt!316</content>
</entry>
<entry>
<title>Do not store .diff_Index files in update</title>
<updated>2024-01-03T16:59:11Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2024-01-03T16:25:35Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=afcdbcf895284efd76903b2b3ba5cc849059ce50'/>
<id>urn:sha1:afcdbcf895284efd76903b2b3ba5cc849059ce50</id>
<content type='text'>
Nowadays we only download the index file if we have a non-current file
on disk which we want to patch. If that is the case, any index file for
patches we could have stored is by definition outdated, so storing those
files just takes up disk space.

At least, that is the case if we have a Release file – if we don't this
commit introduces a needless redownload for such repositories but such
repositories are an error by default and if they can't be bothered to
provide a Release file its very unlikely they actually ship diffs, so
adding detection code for this seems pointless at best.
</content>
</entry>
<entry>
<title>Improve and test distclean implementation</title>
<updated>2024-01-03T13:53:09Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2024-01-03T13:53:09Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=c82f96210eb62c92d31ded7073f4cf5371cc9485'/>
<id>urn:sha1:c82f96210eb62c92d31ded7073f4cf5371cc9485</id>
<content type='text'>
The implementation as-is as various smaller/esoteric bugs and
inconsistencies like apt-get not supporting them, the option -s
being supported in code but not accepted on the command line,
the regex not escaping the dot before the file extension and
exposing more implementation details to public headers than we
actually need.

Also comes with a small test case to ensure it actually works.

References: bd7c126e3fb1b94e76e0e632c657cea854586844
</content>
</entry>
<entry>
<title>Do not silently ignore directories for reserved file names</title>
<updated>2023-12-13T16:59:34Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2023-12-13T16:55:11Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=7b41275b9da31d6c87bbaa0c9115e224e47b15e1'/>
<id>urn:sha1:7b41275b9da31d6c87bbaa0c9115e224e47b15e1</id>
<content type='text'>
Files with reserved extensions like .list, .sources, .conf,
and .pref should receive notices in their respective directories
even if they are directories.
</content>
</entry>
<entry>
<title>Merge branch 'fix-959093' into 'main'</title>
<updated>2023-12-08T13:14:07Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2023-12-08T13:14:07Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=c555d8f1ae31d1f511bf811640423231b75a8e13'/>
<id>urn:sha1:c555d8f1ae31d1f511bf811640423231b75a8e13</id>
<content type='text'>
Add 'dist-clean' command to remove packages and list files

See merge request apt-team/apt!290</content>
</entry>
</feed>
