Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 92229 - when updating portage, emerging fails (collision problem?)
Summary: when updating portage, emerging fails (collision problem?)
Status: RESOLVED FIXED
Alias: None
Product: Gentoo/Alt
Classification: Unclassified
Component: Mac OSX (show other bugs)
Hardware: PPC All
: High normal (vote)
Assignee: Gentoo for Mac OS X
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-05-11 03:31 UTC by Kasper Jordaens
Modified: 2006-04-12 10:53 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 Kasper Jordaens 2005-05-11 03:31:05 UTC
I tried adding root to the portagegroup, but the exact same error occurred, sorry but I'm already stuck.



root# groups 
wheel daemon kmem sys tty operator staff guest admin portage
root# emerge -a portage


Calculating dependencies ...done!
[ebuild     U ] sys-apps/portage-2.0.51.19 [2.0.51-r15] 

Do you want me to merge these packages? [Yes/No] y
>>> emerge (1 of 1) sys-apps/portage-2.0.51.19 to /
chflags: invalid flag: nosunlnk
>>> md5 files   ;-) ChangeLog
>>> md5 files   ;-) metadata.xml
>>> md5 files   ;-) portage-2.0.51.19.ebuild
>>> md5 files   ;-) portage-2.0.51.21-r1.ebuild
>>> md5 files   ;-) files/digest-portage-2.0.51.19
>>> md5 files   ;-) files/digest-portage-2.0.51.21-r1
>>> md5 files   ;-) files/portage-2.0.51.21-fixes.patch
>>> md5 files   ;-) files/README.RESCUE
>>> md5 src_uri ;-) portage-2.0.51.19.tar.bz2
>>> Unpacking source...
>>> Unpacking portage-2.0.51.19.tar.bz2 to /var/tmp/portage/portage-2.0.51.19/work
>>> Source unpacked.
 * NOT BUILDING SANDBOX ON ppc
>>> Test phase [not enabled]: sys-apps/portage-2.0.51.19

>>> Install portage-2.0.51.19 into /var/tmp/portage/portage-2.0.51.19/image/ category sys-apps
 * Not installing sandbox on ppc
man:
prepallstrip:
strip: strip --strip-unneeded
strip: strip --strip-unneeded
 * file /var/tmp/portage/portage-2.0.51.19/image// was installed with group portage!
 * file /var/tmp/portage/portage-2.0.51.19/image///etc was installed with group portage!
 * file /var/tmp/portage/portage-2.0.51.19/image///etc/dispatch-conf.conf was installed with group portage!
 * file /var/tmp/portage/portage-2.0.51.19/image///usr/bin/portageq was installed with group portage!
 * file /var/tmp/portage/portage-2.0.51.19/image///usr/bin/quickpkg was installed with group portage!


[...]


 * file /var/tmp/portage/portage-2.0.51.19/image///var/tmp was installed with group portage!
 * file /var/tmp/portage/portage-2.0.51.19/image///var/tmp/.keep was installed with group portage!
>>> Completed installing portage-2.0.51.19 into /var/tmp/portage/portage-2.0.51.19/image/

* checking 122 files for package collisions
existing file /usr/lib/portage/bin/pemerge.py is not owned by this package
* spent 0.157086849213 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-apps/portage-2.0.51.19 NOT merged

No package files given... Grabbing a set.


Reproducible: Always
Steps to Reproduce:
1. emerge portage


Actual Results:  
emerging failed (see details)


!!! Relying on the shell to locate gcc, this may break
!!! DISTCC, installing gcc-config and setting your current gcc
!!! profile will fix this
Portage 2.0.51-r15 (default-darwin/macos/10.3, gcc-3.3, libsystem-7.1-r0, 7.9.0
Power Macintosh)
=================================================================
System uname: 7.9.0 Power Macintosh powerpc
macos-20041118
Python:               [2.3 (#1, Sep 13 2003, 00:49:11)]
distcc 2.0.1-zeroconf powerpc-apple-darwin7.0 (protocol 1) (default port 3632)
[disabled]
dev-lang/python:     [Not Present]
sys-apps/sandbox:    [Not Present]
sys-devel/autoconf:  2.13
sys-devel/automake:  [Not Present]
sys-devel/binutils:  [Not Present]
sys-devel/libtool:   [Not Present]
virtual/os-headers:  7.1
ACCEPT_KEYWORDS="ppc-macos"
AUTOCLEAN="yes"
CFLAGS="-O2 -pipe"
CHOST="powerpc-apple-darwin"
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config
/usr/share/config /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d"
CXXFLAGS="-O2 -pipe"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoaddcvs autoconfig ccache collision-protect distlocks strict userpriv"
GENTOO_MIRRORS="http://distfiles.gentoo.org
http://distro.ibiblio.org/pub/Linux/distributions/gentoo"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="ppc emboss ncurses nls ogg ppc-macos readline userland_BSD kernel_Darwin
elibc_Darwin"
Unset:  ASFLAGS, CBUILD, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS, PORTDIR_OVERLAY
Comment 1 Lina Pezzella (RETIRED) gentoo-dev 2005-05-11 20:09:49 UTC
That is most likely the fault of the installer. I had a similar issue when installing portage for the first time on my Tiger. In this case, it is safe to do:

FEATURES="-collision-protect" emerge portage
Comment 2 Kasper Jordaens 2005-05-12 04:36:24 UTC
That works for me on Pather 10.3.9 too, thanks