Summary: | install errors if collision-protect is in FEATURES /different apps/ - 4 prev BUGS (68367,69329,70814/15,70938) | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Rumen Yotov <rumen> |
Component: | [OLD] Unspecified | Assignee: | Vim Maintainers <vim> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Rumen Yotov
2004-11-14 00:34:57 UTC
collision-protect in general works but (I assume) there are still many packages that want to overwrite files. Another problem is that the stage tarballs don't have a proper package database, so you'll get errors until the whole system has been remerged. *** Bug 71126 has been marked as a duplicate of this bug. *** Hi, Seems you right. Later happened again while compiling subversion, same file: /usr/lib/perl5/5.8.5/i686-linux-thread-multi/perllocal.pod As i backed up previous two files a diff shows they are different besides sharing a common name. So short term solution: should i remove 'collision-protect' as this causes to have to emerge twice (maybe i could just run 'ebuild /path_to_ebuild install/qmerge) but still haven't tried? As the compiling phase passes OK, it's just the install/qmerge that breaks. Looks like this mostly happens with packages which have +perl USE-flag, as i've rebuild it with +ithreads. Thanks Rumen Hrm, the only conflicts that I can trigger with vim are with other vi clones. I can't reproduce any perl-related collisions. |