Summary: | slot conflict message gives incorrect advice regarding --newuse | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Graham Murray <graham> |
Component: | [OLD] Core system | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED FIXED | ||
Severity: | trivial | Keywords: | InVCS |
Priority: | Normal | ||
Version: | 2008.0 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 210077, 261959 |
Description
Graham Murray
2009-03-10 18:37:30 UTC
So is your concern really portage being quite unhelpful or do you rather want to have bug #261889 fixed? (which already happened) (In reply to comment #1) > So is your concern really portage being quite unhelpful or do you rather want > to have bug #261889 fixed? (which already happened) > That portage was unhelpful. Previous versions just announced that different versions cannot be installed in the same slot. Neither of the two possible actions suggested by portage 'fixed' the problem. From past experience with this type of blockage, I did not expect either of portage's suggestions to work. I always use --newuse, and I think that every time I have seen 'multiple version' blockages that the eventual solution (as in this case) has been a change to one (or more) of the ebuilds which wants to pull in the 'downgrade'. This is fixed in svn r13059. This is fixed in 2.2_rc25 which is in package.mask. I'll close this bug when it's also released in 2.1.6.8. This is released in 2.1.6.8. |