Summary: | `emerge world -Dup` displays obtuse package.provided warning | ||
---|---|---|---|
Product: | Portage Development | Reporter: | SpanKY <vapier> |
Component: | Core - Interface (emerge) | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED FIXED | ||
Severity: | normal | Keywords: | InVCS |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 181949 |
Description
SpanKY
2007-06-29 12:04:42 UTC
The reason for the warning is that package.provided has prevented gentoo-sources from being upgraded. Users often get confused by this behavior when they forget about old entries in package.provided, so the warning was added to let them know what happened. Can you simply remove it from package.provided in order to prevent the warning? Perhaps the warning message should be adjusted to suggest that. as Zack correctly diagnosed on irc, the trouble is i have sys-kernel/gentoo-sources in package.provided, world, and vdb ... so i guess the message needs to be a little bit more informative as to what the problem is ... in my case, the solution was to delete the packages from vdb and world ... i wanted the package.provided entry, not the old vdb stuff ... so the warning told me about package.provided, but not why ... for some the solution would be to cleanse that file because it has things they didnt want, but for others the exact opposite is what they want to do Here's an example of the new warning. The stuff about world will only be shown if the offending atom actually came from world. WARNING: A requested package will not be merged because it is listed in package.provided: sys-kernel/gentoo-sources pulled in by 'world' This problem can be solved in one of the following ways: A) Use emaint to clean offending packages from world (if not installed). B) Uninstall offending packages (cleans them from world). C) Remove offending entries from package.provided. The best course of action depends on the reason that an offending package.provided entry exists. This has been released in 2.1.3_rc7. |