<feed xmlns='http://www.w3.org/2005/Atom'>
<title>apt, branch main</title>
<subtitle>Debians commandline package manager</subtitle>
<id>https://git.kalnischkies.de/apt/atom?h=main</id>
<link rel='self' href='https://git.kalnischkies.de/apt/atom?h=main'/>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/'/>
<updated>2024-04-26T20:10:30Z</updated>
<entry>
<title>Allow parsing an empty Provides line</title>
<updated>2024-04-26T20:10:30Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2024-04-26T18:50:49Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=c98bcdf00e5366fec101dd17094d36be21872a02'/>
<id>urn:sha1:c98bcdf00e5366fec101dd17094d36be21872a02</id>
<content type='text'>
If dpkg-gencontrol was involved in the creation of a package we will not
usually encounter empty or otherwise useless fields, but apparently not
everyone is using it.

It isn't recommended to have these empty lines, but it isn't too hard to
ignore for Provides as we did for dependencies already and apt-ftparchive
can be convinced to produce empty files (if you feed it such a package)
as well, so lets be nice and provide users with a more accepting parser.

Closes: #1069874
</content>
</entry>
<entry>
<title>Merge branch 'fix/mixed' into 'main'</title>
<updated>2024-04-26T11:01:17Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2024-04-26T11:01:17Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=05a1ee0cf4d5948ec2a084629bb9712af7d9c475'/>
<id>urn:sha1:05a1ee0cf4d5948ec2a084629bb9712af7d9c475</id>
<content type='text'>
Split out of mostly independent fixes: cmake execute errors, removed rev-deps, protected garbage &amp; co

See merge request apt-team/apt!345</content>
</entry>
<entry>
<title>Add test for dealing with unsat Suggests promoted to Recommends</title>
<updated>2024-04-24T13:16:21Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2024-04-04T13:36:24Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=7a1063e81b855ac7ff9ee54f115843c3af6dd1bf'/>
<id>urn:sha1:7a1063e81b855ac7ff9ee54f115843c3af6dd1bf</id>
<content type='text'>
Our code does the right thing currently, so lets add a test to ensure
this keeps being the case in the future.
</content>
</entry>
<entry>
<title>Drop sudo-related envvars in testing framework</title>
<updated>2024-04-24T13:16:21Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2024-04-23T16:13:46Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=9c06578c37ff77b70b9d978d48528df13e13530f'/>
<id>urn:sha1:9c06578c37ff77b70b9d978d48528df13e13530f</id>
<content type='text'>
Our autoremoval-advertisment is modified by SUDO_USER as if the current
apt call was made with sudo it seems a good idea to show the ad with
sudo as well. That is annoying for our tests through as normally the
tests are run locally or by autopkgtest without sudo, but in Gitlab CI
we use it (to run our tests as user… as we are already root) and so
individual tests had to deal with this.

That is annoying and really not needed as we can have our autoremove
test check that this ad gets displayed the right way and ignore it the
rest of the time.
</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>Match version constraints before saving garbage packages</title>
<updated>2024-04-24T13:16:21Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2024-04-03T19:12:01Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=e099ee946000797f4c03b8c5075ce7ebba193337'/>
<id>urn:sha1:e099ee946000797f4c03b8c5075ce7ebba193337</id>
<content type='text'>
We remove new garbage packages from the solution if we can as installing
a new package which is at the same time considered garbage looks silly,
but it could also be a new dependency of another garbage package, so we
have a second round trying to save such packages. In this round we
weren't considering versioned constraints on dependency relations through
so even an unsatisfied old recommends could save which it shouldn't.
</content>
</entry>
<entry>
<title>Avoid figuring which kept pkgs are phased if we don't display it</title>
<updated>2024-04-24T13:16:21Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2024-04-03T12:36:40Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=7d93bcabc3f2c47c093faae7b36b7709f287cce2'/>
<id>urn:sha1:7d93bcabc3f2c47c093faae7b36b7709f287cce2</id>
<content type='text'>
Not all commands show kept back packages, so even if it hardly matters,
lets not crunch numbers needlessly if we don't need the info which also
reduces the lifetime of the involved variables hopefully also reducing
the mental requirements for a reader.
</content>
</entry>
<entry>
<title>Do not ignore if a cmake execute_process fails</title>
<updated>2024-04-24T13:16:21Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2024-04-05T14:02:39Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=3e24f431d9527816820e103df7db9f39062b551d'/>
<id>urn:sha1:3e24f431d9527816820e103df7db9f39062b551d</id>
<content type='text'>
Ignoring errors might lead to failures later on anyhow, but especially
with triehash it could also lead to broken builds or other crazy stuff,
so lets better be save than sorry.
</content>
</entry>
<entry>
<title>The text of notices and audits shall not be bold</title>
<updated>2024-04-23T19:02:30Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2024-04-23T19:01:45Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=edfbc3869361f709d70794a794199ac2076ea9f1'/>
<id>urn:sha1:edfbc3869361f709d70794a794199ac2076ea9f1</id>
<content type='text'>
This turned out to be a bit too bold for most of them, given their
informational nature.
</content>
</entry>
<entry>
<title>Highlight essential removals with action::remove color</title>
<updated>2024-04-23T18:32:30Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2024-04-23T18:32:17Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=d4889a909632f38418c630f257c00ccc595ba572'/>
<id>urn:sha1:d4889a909632f38418c630f257c00ccc595ba572</id>
<content type='text'>
</content>
</entry>
</feed>
