Summary: | dev-python/python-fchksum, sys-devel/flex, sys-apps/diffutils cannot be emerged during emerge system - Collision with stage1 files? | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Alexander Skwar <askwar> |
Component: | Current packages | Assignee: | SpanKY <vapier> |
Status: | RESOLVED FIXED | ||
Severity: | blocker | CC: | catalyst, joe, lars, mvergall, solar |
Priority: | High | Keywords: | InVCS |
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 78241 |
Description
Alexander Skwar
2004-11-07 23:44:01 UTC
Next package:
>>> emerge (2 of 55) sys-devel/flex-2.5.4a-r5 to /
>>> md5 src_uri ;-) flex-2.5.4a.tar.gz
* checking 6 files for package collisions
existing file /usr/bin/flex is not owned by this package
rescue build_system # epm -qf /usr/bin/flex
file /usr/bin/flex is not owned by any package
Hm. Are those the files, that were in the stage1 tar?
>>> emerge (3 of 54) sys-apps/diffutils-2.8.7 to /
>>> md5 src_uri ;-) diffutils-2.8.7.tar.gz
* checking 12 files for package collisions
existing file /usr/bin/cmp is not owned by this package
existing file /usr/bin/diff is not owned by this package
existing file /usr/bin/diff3 is not owned by this package
existing file /usr/bin/sdiff is not owned by this package
rescue build_system # epm -qf /usr/bin/cmp /usr/bin/diff /usr/bin/diff3 /usr/bin/sdiff
file /usr/bin/cmp is not owned by any package
file /usr/bin/diff is not owned by any package
file /usr/bin/diff3 is not owned by any package
file /usr/bin/sdiff is not owned by any package
why do we clean out /var/db/pkg in our stage1/stage2 ? cant a better solution be found ? Since catalyst is the one doing the cleaning, I'm reassigning. Personally, I think we should stop cleaning out /var/db/pkg in stage1 and stage2. This will probably mean a change to the bootstrap.sh script to have it run a "emerge -e $list_of_packages" rather than just emerge, so that all of the packages get rebuilt with the user's USE/CFLAGS. As far as catalyst is concerned, this has been modified in CVS now. What we need from here is a modified bootstap.sh script that works with the new stage files, as both stage1 and stage2 now have much more in their /var/db/pkg directory. Catalyst 1.1.2 is now out! Sorry... forgot that the bootstrap.sh script needs updating... Reassigning to vapier... I have been getting this to work myself, by adding a -e onto the baselayout/glibc emerge in bootstrap.sh, but I'm sure you can come up with a more elegant solution. We will also have to figure out something for "emerge system", as catalyst uses "emerge -e system" now to ensure all packages get updated. This is resolved in newer stages created by catalyst and will be resolved when 2005.0 is released. vapier: can you test the bootstrap-new.sh script in cvs and make sure it looks good (or fix it)... my tests have shown it to work as expected, so everything seems to be resolved. If the bootstrap-new.sh script works, we will be replacing the old bootstrap.sh script with this new one. *** Bug 81676 has been marked as a duplicate of this bug. *** *** Bug 75870 has been marked as a duplicate of this bug. *** *** Bug 80868 has been marked as a duplicate of this bug. *** You can RESOLVE this one now that 2005.0 is released. Fixed with the 2005.0 stages and new bootstrap.sh script. |