<feed xmlns='http://www.w3.org/2005/Atom'>
<title>apt/test/integration/test-external-dependency-solver-protocol, 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>2025-03-10T21:33:05Z</updated>
<entry>
<title>edsp: Set Forbid-New-Install/Forbid-Remove: no if other is set</title>
<updated>2025-03-10T21:33:05Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2025-03-10T17:37:55Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=1fc8e9eee4d6a81f907b399034f6f82da2e98140'/>
<id>urn:sha1:1fc8e9eee4d6a81f907b399034f6f82da2e98140</id>
<content type='text'>
The upgrade code may also set Upgrade: yes, and this sets both to
yes, so `apt upgrade` dumps behave like `apt-get upgrade` ones,
which of course is not intentional.

moo
</content>
</entry>
<entry>
<title>edsp: Write 'Size' to the EDSP files</title>
<updated>2025-03-03T10:21:55Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2025-03-03T10:20:52Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=45b04762e1990a761a7c308f9e73a286a92f908a'/>
<id>urn:sha1:45b04762e1990a761a7c308f9e73a286a92f908a</id>
<content type='text'>
This allows solvers to optimize by download size; and gives us
a better means of interpreting "downloadable" debs (they must have
a size &gt; 0 after all).
</content>
</entry>
<entry>
<title>test: Fix 7 test cases for 3.0 solver, annotate others</title>
<updated>2025-02-14T18:08:45Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2025-02-11T16:02:00Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=e86f3d875a48987a026f79aa4e19eeda4ad01b3b'/>
<id>urn:sha1:e86f3d875a48987a026f79aa4e19eeda4ad01b3b</id>
<content type='text'>
Fix the test cases we can fix directly; add annotations where we
know what work is needed, next we'll look at the other bugs.
</content>
</entry>
<entry>
<title>Write Pre-Depends with a dash again in EDSP</title>
<updated>2025-01-17T00:27:48Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2025-01-17T00:01:13Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=4454fd246b3b7f605dcd272b2107313ba53688c5'/>
<id>urn:sha1:4454fd246b3b7f605dcd272b2107313ba53688c5</id>
<content type='text'>
For some reason ~ that I don't know and can't come up with on the spot ~
we output the Pre-Depends field as PreDepends in the translated
user-visible output and I accidentally copied that over to the
untranslated variant that replaced the embedded copy (with a dash)
in the EDSP generator.

Code-copies and implementation details littered all over the place are
apparently sometimes a good bug-free thing, too…

Regression-of: 6828ae2c2f9268c8187f0fa91b3c464ed84a8476
Closes: #1093254
</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>Avoid dealing with a fake dpkg stanza in the tests</title>
<updated>2022-09-02T14:55:45Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2022-08-31T19:49:33Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=3498fbedafbf30e5c91deeaefa6a60d1e387593a'/>
<id>urn:sha1:3498fbedafbf30e5c91deeaefa6a60d1e387593a</id>
<content type='text'>
We needed a fake dpkg in our status file for dpkg --assert-multi-arch to
work in the past, but recent dpkg versions do not require this anymore,
so we can remove this somewhat surprising hackery in favour of better
hidden hackery we only use if we work with an older dpkg (e.g. on
current Debian stable).
</content>
</entry>
<entry>
<title>Deduplicate EDSP Provides line of M-A:foreign packages</title>
<updated>2020-06-14T08:19:39Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2020-06-14T07:48:29Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=a1464cb4025cd737ac57ea7392402d5efd2af027'/>
<id>urn:sha1:a1464cb4025cd737ac57ea7392402d5efd2af027</id>
<content type='text'>
M-A:foreign causes Provides to apply to all architectures and as we
wanted to avoid resolver changes for M-A those are done by explicitly
creating these provides instead of forcing the resolvers to learn about
this. The EDSP is a different beast though &amp; we don't need this trick
here especially as it leads to needless (but harmless) duplication.

No sort+unique is done to avoid changing order (not that it should
matter, but just to be sure), but the sets should be small enough to not
make a huge difference either way.
</content>
</entry>
<entry>
<title>Tell EDSP solvers about all installed pkgs ignoring arch</title>
<updated>2020-06-14T08:19:39Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2020-06-13T09:45:38Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=419190f6c17aaf750887ec7471599681377fb01b'/>
<id>urn:sha1:419190f6c17aaf750887ec7471599681377fb01b</id>
<content type='text'>
We usually tell EDSP solvers only about architectures we are configured
to treat as native/foreign, but the system could have packages from
other architectures installed (even if very unlikely) which could
influence the solution (e.g. requiring a removal) so we make sure to
tell them.
</content>
</entry>
<entry>
<title>Do not sent our filename-provides trick to EDSP solvers</title>
<updated>2020-06-14T08:19:39Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2020-06-13T09:36:41Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=71d753b5e450a99f7f6677fe4899515aaec7e585'/>
<id>urn:sha1:71d753b5e450a99f7f6677fe4899515aaec7e585</id>
<content type='text'>
If package is installed via an explicitly given deb file we store the
filename as a provides, so that the frontend can request the filename
and get the usual "Selected foo instead of foo.deb" message.

We do not need to trouble the EDSP solvers with that though as these
provides are not valid in various ways and we have already solved the
link between commandline and package (and version) for them.

Closes: #962741
</content>
</entry>
<entry>
<title>ensure generation of valid EDSP error stanzas</title>
<updated>2016-12-31T01:29:20Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2016-12-29T10:20:18Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=0161280405fe5aa256dc9df6a56106dd3a1a6f38'/>
<id>urn:sha1:0161280405fe5aa256dc9df6a56106dd3a1a6f38</id>
<content type='text'>
The crude way of preparing a message to be a multiline value failed at
generation valid deb822 in case the error message ended with a new line
like the resolving errors from apt do. apt itself can parse these, but
other tools like grep-dctrl choke on it, so be nice and print valid.

Reported-By: Johannes 'josch' Schauer on IRC
</content>
</entry>
</feed>
