I've had this problem before with paludis on occasion, and now I'm
getting it with cave. I must not be doing something the "paludis way"
and dealing with these kinds of dependency issues can be frustrating.
What is the RightWay(TM) to handle a situation like this:
Eons ago I had lzma-utils installed. At some point I removed it and
installed xz-utils.
The problem is that lots of stuff is installed which depended on either
of those packages, and paludis captured at the time of installation that
lzma-utils was used to satisfy the dependency, and it keeps coming up.
Re-installing anything that had a direct dependency on lzma-utils will
tend to fix the problem (they now depend on xz-utils), but is a real pain.
How can I fix these kinds of issues without rebuilding everything. This
isn't a library linking issue - those packages will work just fine as
long as they can access the binary (assuming they even need it runtime).
Example:
# cave resolve -C i --resume-file /sstorage3/tmp/.cave-resume-XXXXXX -J
3 -c world
....lots of output about the stuff it wants to install...
I encountered the following errors:
! app-arch/lzma-utils:0::(install_to_slash)
Reasons: !app-arch/lzma-utils from app-arch/xz-utils,
dev-texlive/texlive-bibtexextra, dev-texlive/texlive-documentation-base,
19 more
Unsuitable candidates:
* app-arch/lzma-utils-4.32.7:0::gentoo
Did not meet !app-arch/lzma-utils, use existing if possible,
installing to / from !app-arch/lzma-utils from app-arch/xz-utils
Any suggestions? I know that I can use --lazy instead to avoid the
problem, but I'd like to upgrade dependencies and use-flag changes/etc.
There must be another way...
Rich
_______________________________________________
paludis-user mailing list
[email protected]
http://lists.pioto.org/mailman/listinfo/paludis-user
