<feed xmlns='http://www.w3.org/2005/Atom'>
<title>apt/apt-pkg/depcache.cc, branch 3.1.8</title>
<subtitle>Debians commandline package manager</subtitle>
<id>https://git.kalnischkies.de/apt/atom?h=3.1.8</id>
<link rel='self' href='https://git.kalnischkies.de/apt/atom?h=3.1.8'/>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/'/>
<updated>2025-03-08T23:12:27Z</updated>
<entry>
<title>depcache: Add a new UpgradeCount() member</title>
<updated>2025-03-08T23:12:27Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2025-02-18T12:37:38Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=1ab3740704f8cf478d01ef95f4ef8152b79d7b87'/>
<id>urn:sha1:1ab3740704f8cf478d01ef95f4ef8152b79d7b87</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Introduce pkgDepCache::Transaction for transactional depcache updates</title>
<updated>2025-03-08T23:12:27Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2025-02-04T17:22:35Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=71d3d399d7de75a96b2911677b74ce8b59579ee9'/>
<id>urn:sha1:71d3d399d7de75a96b2911677b74ce8b59579ee9</id>
<content type='text'>
</content>
</entry>
<entry>
<title>refactor: Deduplicate and Move SectionInSubTree to Configuration</title>
<updated>2025-02-18T09:56:45Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2025-02-17T20:33:30Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=e8b240eb3aab7e2584e245f03700ede30a3fc23a'/>
<id>urn:sha1:e8b240eb3aab7e2584e245f03700ede30a3fc23a</id>
<content type='text'>
Deduplicate the copies in a central one, mark it unavailable to
external users.
</content>
</entry>
<entry>
<title>solver3: Defer 3.0 'deep' autoremoval to 3.1, fix autoremove</title>
<updated>2025-02-14T18:08:45Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2025-02-11T11:11:20Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=4c48b5618ba15d4e33625cec81843891910e81a2'/>
<id>urn:sha1:4c48b5618ba15d4e33625cec81843891910e81a2</id>
<content type='text'>
Restore the depcache's MarkRequired logic for 3.0 solver; and
change the MarkInstall() call to pass a more correct value for
FromUser, to not override an existing automatic status.
</content>
</entry>
<entry>
<title>Measure BootSize as integer</title>
<updated>2025-02-03T12:40:37Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2025-02-03T12:19:12Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=452586e84ad54ca23dee399bf9809c49e7171f36'/>
<id>urn:sha1:452586e84ad54ca23dee399bf9809c49e7171f36</id>
<content type='text'>
I don't know why I used a double here this is awkward.
</content>
</entry>
<entry>
<title>Correctly calculate kernel size in /boot</title>
<updated>2025-02-03T12:40:37Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2025-02-03T12:07:37Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=c303750ecb89b7210fe998515432e358b3cc0cff'/>
<id>urn:sha1:c303750ecb89b7210fe998515432e358b3cc0cff</id>
<content type='text'>
Change the code to get the size from the existing vmlinuz,
rather than using the package size, which only worked in
Ubuntu, and possibly not on all kernel packages either.

Refactor the code a bit to avoid the nested if as well,
and use off_t to measure and sum the sizes before switching
to floating point.

Closes: #1085184
</content>
</entry>
<entry>
<title>Drop usage of macro APT_OVERRIDE for simple override</title>
<updated>2025-01-05T22:16:08Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2024-12-26T19:41:53Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=f73593a4034d9eec0ec4466b8e173d4a4daece1f'/>
<id>urn:sha1:f73593a4034d9eec0ec4466b8e173d4a4daece1f</id>
<content type='text'>
We were rather inconsistent in using it and as our public headers
contain deduction guides (a c++17 feature) it seems silly to try to hide
a c++11 feature in a macro, so lets stop this charade and drop the
macro and while we are changing all these lines lets apply [[nodiscard]]
(another c++17 feature) and other suggestions from clang-tidy and
formatting for a little more consistency.
</content>
</entry>
<entry>
<title>Do not mark new if we have already installed providers</title>
<updated>2024-05-16T20:12:51Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2024-05-16T13:41:48Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=b1c3039dae19553bff19615fbb4d116aeaa644a7'/>
<id>urn:sha1:b1c3039dae19553bff19615fbb4d116aeaa644a7</id>
<content type='text'>
The test is actually documenting another bug hidden a bit by this one as
we do not need to install a NEW package in this situation as the upgrade
needing it was kept back, but it was protected from considering it to
be autoremoveable as all providers tend to be considered protected, but
by limiting us to installed providers if we have some we can drag those
new packages out of hiding.

Now, we "just" have to get right of the NEW package in a next step.
</content>
</entry>
<entry>
<title>Do not upgrade rev-deps ear-marked for removal</title>
<updated>2024-04-24T13:16:21Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2024-03-14T20:59:10Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=d030a1041b243c45dcd41e34d3c2b21cf1a533ba'/>
<id>urn:sha1:d030a1041b243c45dcd41e34d3c2b21cf1a533ba</id>
<content type='text'>
We schedule reverse dependencies for an upgrade, but we shouldn't do it
if we have ear-marked this package for removal later on. Usually the
solver will end up doing the right thing like it already did in the
included testcase in the end, but given that before it reaches the right
end it explored a bad path which can lead to more installs and removals
influencing later decisions or are just too hard for the resolver to
undo later on, we can just not explore this path to begin with.

References: e077370ffcb3669a50a600e80356c2002e6b176d
</content>
</entry>
<entry>
<title>Show space estimate for /boot, if separate; or estimate initrd for /usr</title>
<updated>2024-04-13T18:27:48Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2024-04-13T18:27:48Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=f7e5ed3c8dffcdfc2c55c63f2e3cbcb390bbf013'/>
<id>urn:sha1:f7e5ed3c8dffcdfc2c55c63f2e3cbcb390bbf013</id>
<content type='text'>
Calculate an estimate of 110% of the biggest initrd + system.map
as the additional space a kernel needs in /boot.

If /boot is a different file system than /usr, print the size of
the kernels + the additional space they will need separately;
otherwise include it in our /usr figure.
</content>
</entry>
</feed>
