Summary: | Improve output when visibility prevents subslot-triggered rebuilds | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Andreas K. Hüttel <dilfridge> |
Component: | Core | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | esigra, josef64, redwolfe |
Priority: | Normal | Keywords: | InVCS |
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
See Also: | https://bugs.gentoo.org/show_bug.cgi?id=452732 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 155723, 611328 |
Description
Andreas K. Hüttel
![]() ![]() It shouldn't be too difficult to identify and highlight these packages in the slot conflict output. That will be a vast improvement over the current situation. I've posted this patch for review: https://archives.gentoo.org/gentoo-portage-dev/message/553e19a6126d6989453d9ac359650809 https://github.com/gentoo/portage/pull/77 This is in the master branch: https://gitweb.gentoo.org/proj/portage.git/commit/?id=ddbe020d9385f8b70e4ec6f085d3afa7271949d7 We could extend this to include information about other issues found in the depgraph _slot_operator_trigger_reinstalls and _slot_operator_update_probe methods. For example: * _slot_operator_trigger_reinstalls will not call _slot_operator_update_probe if the package depth is greater than the current --deep setting * _slot_operator_update_probe will not trigger a rebuild if it can't find an available package that satisfies the check_reverse_dependencies function *** Bug 607244 has been marked as a duplicate of this bug. *** Fixed in portage-2.3.5. |