apt/test/integration/test-bug-591882-conkeror, branch mainDebians commandline package managerhttps://git.kalnischkies.de/apt/atom?h=main2025-05-26T10:45:12Zsolver3: Assume manual packages2025-05-26T10:45:12ZJulian Andres Klodejak@debian.org2025-05-26T09:19:11Zurn:sha1:717ca7922be8a025b8034dc840b2ad9befc3b171
If we have allowed the removal of manual packages, assume them
all before starting the solver. This should ensure that as long
as there is a solution that does not remove a manually installed
package, it is found.
This requires a sweeping set of changes in the test suite, but
ensures that we get "safe" behavior from the solver. We have
in particular seen that without asserting the installed packages,
several people ended up with ubuntu-minimal and perl removed in
a situation where that was not warranted, that is, they install
winehq, and then pull in some new perl packages in a newer version
than the installed one, and the solver chose to create a mismatched
version set, which then caused the main perl package to not be
installable.
Oops: 1b55173a-3526-11f0-b7ac-fa163e171f02
Oops: dbd5149e-36b9-11f0-bb74-fa163ec44ecd
solver3: Handle previously satisfied Suggests last2025-03-20T21:22:17ZJulian Andres Klodejulian.klode@canonical.com2025-03-20T19:47:28Zurn:sha1:83bad834c63604035c251f24ee9ea99dac1a1369
In #2103556 we can see that avahi-daemon Suggests avahi-autoipd,
which is previously satisfied by dhcpcd-base due to a Provides;
that Provides has now been dropped; and solver3 keeps the update
back.
As in LP: #2102720 this is a Suggests and it seems wrong for the
Suggests to actually influence dependency choices and be able to
hold back updates.
Instead, satisfy previously satisfied Suggests at the end. For the
particular case in this bug report, this results in avahi-autoipd,
the real package, to be installed to keep the Suggests working
which needs further consideration whether that is the right choice
(we can argue either way), but in any case this is a better solution.
This in turn breaks the conkeror test which is a somewhat awkward
unrealistic test these days as it has no automatically installed
packages; because previously something must have had a Suggests
on say libdatrie1 or something that was processed first.
This would be fine before 5daf6dbfd272be2f8e3c59d4bab4be8c119b7aa1
but as of that commit we no longer rewrite
conkeror Depends xulrunner-1.9 | xulrunner-1.9.1
into
conkeror Depends xulrunner-1.9.1 | xulrunner-1.9
Because xulrunner-1.9 is manually installed. Mark xulrunner-1.9
as automatically installed to fix the test case.
The resulting behavior seems correct: If you manually want
xulrunner-1.9 specifically we should not replace it with
xulrunner-1.9.1; but if it's automatically installed we should.
LP: #2103556
solver3: Promote satisfied Suggests to Recommends2024-05-24T15:01:55ZJulian Andres Klodejulian.klode@canonical.com2024-05-19T19:24:08Zurn:sha1:0fa3b176652ff10276569a478c910ca866a4da5d
As per the test-suggests-promoted-to-recommends test. This is still
a bit messy as we ignore alternative choices and only check the last
one, but um seems useful?
tests: support spaces in path and TMPDIR2015-12-19T22:04:34ZDavid Kalnischkiesdavid@kalnischkies.de2015-12-15T16:20:26Zurn:sha1:3abb6a6a1e485b3bc899b64b0a1b7dc2db25a9c2
This doesn't allow all tests to run cleanly, but it at least allows to
write tests which could run successfully in such environments.
Git-Dch: Ignore
test exitcode as well as string equality2015-03-16T17:01:54ZDavid Kalnischkiesdavid@kalnischkies.de2015-03-09T23:59:44Zurn:sha1:25b86db159fbc3c043628e285c0c1ef24dec2c6e
We use test{success,failure} now all over the place in the framework, so
its only consequencial to do this in the situations in which we test for
a specific output as well.
Git-Dch: Ignore
fix progress output for (dist-)upgrade calculation2014-09-26T22:10:05ZDavid Kalnischkiesdavid@kalnischkies.de2014-08-17T10:30:21Zurn:sha1:2a884c612b10b27f4be2cc6dd689bfe448d9361a
Previously, we had a start and a done of the calculation printed by
higher-level code, but this got intermixed by progress reporting from an
external solver or the output of autoremove code…
The higherlevel code is now only responsible for instantiating a
progress object of its choosing (if it wants progress after all) and the
rest will be handled by the upgrade code. Either it is used to show the
progress of the external solver or the internal solver will give some
hints about its overall progress. The later isn't really a proper
progress as it will jump forward after each substep, but that is at
least a bit better than before without any progress indication.
Fixes also the 'strange' non-display of this progress line in -q=1, while
all others are shown, which is reflected by all testcase changes.
tests/integration/test-*: remove a bunch of "local" that are used outside funtions (bash complains)2010-10-13T13:22:48ZMichael Vogtmvo@debian.org2010-10-13T13:22:48Zurn:sha1:9962ae934b367294a57b27d58f7cdb4e2d54ce04fix the testcases which were broken by the new space between number and unit2010-09-29T16:34:48ZDavid Kalnischkieskalnischkies@gmail.com2010-09-29T16:34:48Zurn:sha1:1054d76b2519efc858a9d23301495a763c1f8230implement the first round of automated dummy package building and2010-08-18T10:56:57ZDavid Kalnischkieskalnischkies@gmail.com2010-08-18T10:56:57Zurn:sha1:ce9864a8bfdfc7f5380b3335a6a14f305d372d45
archive building
add finally my very small testcase for the conkeror problem resulting2010-08-15T17:12:35ZDavid Kalnischkieskalnischkies@gmail.com2010-08-15T17:12:35Zurn:sha1:f107544e43fc3d262d9df5bde6eb430b7008825f
in the FixByInstall code we currently "experiment" with