apt/test/integration/test-resolve-by-keep-obsolete-removals, branch mainDebians commandline package managerhttps://git.kalnischkies.de/apt/atom?h=main2024-11-11T11:30:01ZReturn an error if ResolveByKeep() is unsuccessful2024-11-11T11:30:01ZJulian Andres Klodejulian.klode@canonical.com2024-09-05T12:58:50Zurn:sha1:2f5aab4afaa61ec9b9c690dea4a0b7d650bb2374
In case of held packages or packages that otherwise can't be kept
back, we should return an error and not require the client to check
the broken_count after calling us.
LP: #2078720
Fix keeping back removals of obsolete packages2024-11-11T11:30:01ZJulian Andres Klodejulian.klode@canonical.com2024-09-05T12:56:01Zurn:sha1:49d3d6b2c3dbc0d30e46131dd288f4e106ea2fe6
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