From 49d3d6b2c3dbc0d30e46131dd288f4e106ea2fe6 Mon Sep 17 00:00:00 2001 From: Julian Andres Klode Date: Thu, 5 Sep 2024 14:56:01 +0200 Subject: Fix keeping back removals of obsolete packages ResolveByKeepInternal() inadvertently considered packages that were marked for removals as not being possible to keep back, but that's not true, all they need is to have a currently installed version. The test case is a bit awkward to construct because our upgrade code doesn't get into a place where this happens that we know off. Or maybe it does with phased upgrades, but here we simplify this by using a helper binary that dumps state, marks for removal, and then calls ResolveByKeep and checks the removal is undone. LP: #2078720 --- test/integration/solver3.broken | 1 + 1 file changed, 1 insertion(+) (limited to 'test/integration/solver3.broken') diff --git a/test/integration/solver3.broken b/test/integration/solver3.broken index 75ddbe5df..dd06ed0eb 100644 --- a/test/integration/solver3.broken +++ b/test/integration/solver3.broken @@ -26,6 +26,7 @@ test-phased-updates-upgrade test-prevent-markinstall-multiarch-same-versionscrew test-release-candidate-switching test-resolve-by-keep-new-recommends +test-resolve-by-keep-obsolete-removals test-ubuntu-bug-1304403-obsolete-priority-standard test-ubuntu-bug-1990586 test-ubuntu-bug-2025462-phased-dist-upgrade -- cgit v1.2.3-70-g09d2