Created attachment 496788 [details] SlotConflictUpdateTestCase debug log While testing a fix for bug 632202, I found that my fix caused SlotConflictUpdateTestCase to fail. Changing the test case as follows also causes it to fail: diff --git a/pym/portage/tests/resolver/test_slot_conflict_update.py b/pym/portage/tests/resolver/test_slot_conflict_update.py index 331e5788b..f251d01f1 100644 --- a/pym/portage/tests/resolver/test_slot_conflict_update.py +++ b/pym/portage/tests/resolver/test_slot_conflict_update.py @@ -80,7 +80,7 @@ class SlotConflictUpdateTestCase(TestCase): # this behavior makes SlotConflictMaskUpdateTestCase # fail. ResolverPlaygroundTestCase( - world, + ['@world'], all_permutations = True, options = {"--update": True, "--deep": True}, success = True,
It clearly misbehaves in the _solve_non_slot_operator_slot_conflicts method where it keeps boost-1.53.0 but removes the boost-build-1.53.0 that it depends on: !!! Slot conflict solution: Conflict: (/tmp/tmpbbbg_epx/, dev-libs/boost:0) keep: (dev-libs/boost-1.53.0:0/1.53::test_repo, ebuild scheduled for merge) keep: (dev-libs/boost-1.52.0:0/1.52::test_repo, installed) Conflict: (/tmp/tmpbbbg_epx/, dev-util/boost-build:0) keep: (dev-util/boost-build-1.52.0:0/0::test_repo, installed) remove: (dev-util/boost-build-1.53.0:0/0::test_repo, ebuild scheduled for merge) Removing package: (dev-util/boost-build-1.53.0:0/0::test_repo, ebuild scheduled for merge)
Patch sent for review: https://archives.gentoo.org/gentoo-portage-dev/message/b758e1bb3f62db340aaf0d8bbe0e2e3a https://github.com/gentoo/portage/pull/211
This is in the master branch: https://gitweb.gentoo.org/proj/portage.git/commit/?id=5a65670ec2b0850c278b85c6417c20d8a4ca7734
Released in 2.3.11.
