emerge portage fails

[mpdefeo]

So last week I added zenana and naendo repositories. Since then, i emerge --sync and saw there was a new version of portage. So i emerge portage and this is what the terminal spit out.

Code: Select all

>>> Installing sys-apps/portage-2.1.6.7
 * This package will overwrite one or more files that may belong to other
 * packages (see list below). You can use a command such as `portageq
 * owners / <filename>` to identify the installed package that owns a
 * file. If portageq reports that only one package owns a file then do
 * NOT file a bug report. A bug report is only useful if it identifies at
 * least two or more packages that are known to install the same file(s).
 * If a collision occurs and you can not explain where the file came from
 * then you should simply ignore the collision since there is not enough
 * information to determine if a real problem exists. Please do NOT file
 * a bug report at http://bugs.gentoo.org unless you report exactly which
 * two packages install the same file(s). Once again, please do NOT file
 * a bug report unless you have completely understood the above message.
 *
 * package sys-apps/portage-2.1.6.7 NOT merged
 *
 * Detected file collision(s):
 *
 *      /usr/share/doc/portage-2.1.6.7/NEWS.bz2
 *      /usr/share/doc/portage-2.1.6.7/RELEASE-NOTES.bz2
 *      /usr/share/doc/portage-2.1.6.7/ChangeLog.bz2
 *      /usr/lib64/portage/pym/portage/_sets/base.py
 *      /usr/lib64/portage/pym/portage/_sets/files.py
 *      /usr/lib64/portage/pym/portage/_sets/__init__.py
 *      /usr/lib64/portage/pym/portage/_sets/profiles.py
 *
 * Searching all installed packages for file collisions...
 *
 * Press Ctrl-C to Stop
 *
 * None of the installed packages claim the file(s).
 *
 * Package 'sys-apps/portage-2.1.6.7' NOT merged due to file collisions.
 * If necessary, refer to your elog messages for the whole content of the
 * above message.

>>> Failed to install sys-apps/portage-2.1.6.7, Log file:

>>>  '/var/lib/entropy/logs/sys-apps:portage-2.1.6.7:20090308-131058.log'


Does anyone know how to proceed?

[crisandbea]

You remove this file collision and re-run emerge portage.

Code: Select all

      /usr/share/doc/portage-2.1.6.7/NEWS.bz2
      /usr/share/doc/portage-2.1.6.7/RELEASE-NOTES.bz2
      /usr/share/doc/portage-2.1.6.7/ChangeLog.bz2
      /usr/lib64/portage/pym/portage/_sets/base.py
      /usr/lib64/portage/pym/portage/_sets/files.py
      /usr/lib64/portage/pym/portage/_sets/__init__.py
      /usr/lib64/portage/pym/portage/_sets/profiles.py


[WarraWarra]

Have you tried

Code: Select all

emerge unmerge portage && emerge portage

Should work as emerge is loaded into ram while it uninstalls itself and reinstalls itself.

Also are you using " emerge --update " or clean install and replace " emerge portage "

Can even use

Code: Select all

emerge portage --nodeps

and later do

Code: Select all

revdep --help

or

Code: Select all

emerge -uD portage

[mpdefeo]

I removed the conflicting files and portage emerged properly, however it told me i downgraded from portage-2.2 to portage-2.1.6.7...Why is that?

[crisandbea]

I removed the conflicting files and portage emerged properly, however it told me i downgraded from portage-2.2 to portage-2.1.6.7...Why is that?

because portage-2.2 has been masked.... from team Gentoo.

[mpdefeo]

I see...Thanks for the help. BTW i also tried

Code: Select all

emerge --unmerge portage && emerge portage

and i was given the error: no packages to unmerge

[crisandbea]

I see...Thanks for the help. BTW i also tried

Code: Select all

emerge --unmerge portage && emerge portage

and i was given the error: no packages to unmerge

you do not run emerge --unmerge portage, qhen you have the error of collision packages you remove file collision and re-run the command that you have run previously.

[albfneto]

the newer Portage, 2.2 is masked, and the system dowgrades portage, Thiis is made by Gentoo team, because the gentoo team reported unstability in the new portage, bu said that the packages are newer, are the same, and therefore is not necessary turns to the 2.2.23.

But if want to use the newer portage, you may unmask it...

Othet thing, info for you. Zenana Repo and Naendo repo are both for Entropy, not for Portage...
mix t5he two installers are not so easy.
is by this that you experiment the collision problems....
for using the two installers, for tests, but some risks may occurs...

for update entropy, and this will use also your added Naendo and Zenana Repos:
equo update
equo install equo
equo update
if necessary, runs equo conf update

therefore make this:

emerge --sync
emerge -av portage portato

after, run

equo database gentoosync

for syncronize entropy amd portage...
if you plan to mix installers, does not use portage for install entropy:
use "equo install equo entropy spritz" instead of "emerge equo entropy spritz"
Zenana and Naendo Repos are only useful if you want to use entropy( equo command, spritz), not for portage (emerge command, portato)

for a particular package, is best to use only one installer...
example the package nvidia-settings have slighly newer versions in portage, if you run:
emerge nvidia-settings, you will have these new versions, instead, if you using after:
equo install nvidia-settings you will force the dowgrade..
sometimes, you should mask packages in entropy, to control versions...., or equo suggests downgrade as "newer package"

for compare the versions that you need:
emerge -s nameofpackage
equo search nameofpackage
therefore, you see the newer version and use the correspodent installer....

for large packs, as kde, gnome, xfce, gcc is more easy to use the compiled one, from Entropy (equo command)

[mpdefeo]

Thanks for the thorough reply. I moved from gentoo to sabayon, so I am fairly familiar with portage. I try my hardest to use only the entropy i find there are often packages in portage that are not available in entropy, and I am forced to emerge them. I will follow your advice for updating and syncing the two package managers.