Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 105777 - cannot emerge py-freebsd due to ownership errors
Summary: cannot emerge py-freebsd due to ownership errors
Status: RESOLVED FIXED
Alias: None
Product: Gentoo/Alt
Classification: Unclassified
Component: Other (show other bugs)
Hardware: x86 FreeBSD
: High normal (vote)
Assignee: Gentoo/BSD Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-09-13 02:51 UTC by Amit Kotlovski
Modified: 2006-04-12 10:50 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Amit Kotlovski 2005-09-13 02:51:38 UTC
On a fresh Gentoo/FreeBSD install, i followed the guide, and it all went
relatively well until the line where i am to emerge python portage py-freebsd.
The first two went okay, but py-freebsd could not compile.

Reproducible: Always
Steps to Reproduce:
1. emerge py-freebsd
2.
3.

Actual Results:  
# emerge py-freebsd
Calculating dependencies  >>> Unpacking source...
>>> Unpacking freebsd-share-5.4.tar.bz2 to
/var/tmp/portage/freebsd-mk-defs-5.4-r1/work
 [32;01m*[0m Applying freebsd-mk-defs-gentoo.patch ...
[A[69C  [34;01m[ [32;01mok[34;01m ][0m
 [32;01m*[0m Applying freebsd-mk-defs-flex.patch ...
[A[69C  [34;01m[ [32;01mok[34;01m ][0m
>>> Source unpacked.
 [32;01m*[0m Nothing to compile
>>> Test phase [not enabled]: sys-freebsd/freebsd-mk-defs-5.4-r1

>>> Install freebsd-mk-defs-5.4-r1 into
/var/tmp/portage/freebsd-mk-defs-5.4-r1/image/ category sys-freebsd
man:
>>> Completed installing freebsd-mk-defs-5.4-r1 into
/var/tmp/portage/freebsd-mk-defs-5.4-r1/image/

  ...done!
>>> emerge (1 of 5) sys-freebsd/freebsd-mk-defs-5.4-r1 to /
>>> md5 src_uri ;-) freebsd-share-5.4.tar.bz2
* checking 25 files for package collisions
existing file /usr/share/mk/bsd.compat.mk is not owned by this package
existing file /usr/share/mk/bsd.cpu.mk is not owned by this package
existing file /usr/share/mk/bsd.dep.mk is not owned by this package
existing file /usr/share/mk/bsd.doc.mk is not owned by this package
existing file /usr/share/mk/bsd.endian.mk is not owned by this package
existing file /usr/share/mk/bsd.files.mk is not owned by this package
existing file /usr/share/mk/bsd.incs.mk is not owned by this package
existing file /usr/share/mk/bsd.info.mk is not owned by this package
existing file /usr/share/mk/bsd.init.mk is not owned by this package
existing file /usr/share/mk/bsd.kmod.mk is not owned by this package
existing file /usr/share/mk/bsd.lib.mk is not owned by this package
existing file /usr/share/mk/bsd.libnames.mk is not owned by this package
existing file /usr/share/mk/bsd.links.mk is not owned by this package
existing file /usr/share/mk/bsd.man.mk is not owned by this package
existing file /usr/share/mk/bsd.nls.mk is not owned by this package
existing file /usr/share/mk/bsd.obj.mk is not owned by this package
existing file /usr/share/mk/bsd.own.mk is not owned by this package
existing file /usr/share/mk/bsd.port.mk is not owned by this package
existing file /usr/share/mk/bsd.port.post.mk is not owned by this package
existing file /usr/share/mk/bsd.port.pre.mk is not owned by this package
existing file /usr/share/mk/bsd.port.subdir.mk is not owned by this package
existing file /usr/share/mk/bsd.prog.mk is not owned by this package
existing file /usr/share/mk/bsd.subdir.mk is not owned by this package
existing file /usr/share/mk/bsd.sys.mk is not owned by this package
existing file /usr/share/mk/sys.mk is not owned by this package
* spent 0.0270168781281 seconds checking for file collisions
* This package is blocked because it wants to overwrite
* files belonging to other packages (see messages above).
* If you have no clue what this is all about report it 
* as a bug for this package on http://bugs.gentoo.org

package sys-freebsd/freebsd-mk-defs-5.4-r1 NOT merged

No package files given... Grabbing a set.
Comment 1 Diego Elio Pettenò (RETIRED) gentoo-dev 2005-09-13 02:55:28 UTC
It's a known side-problem, disable collision-protect, the ebuild was installed 
in the wrong slot in the stage.