| View previous topic :: View next topic |
| Author |
Message |
bjdacre
n00b
Joined: 25 Nov 2014
Posts: 35
Location: Whangarei, NZ
|
 Posted: Tue Mar 31, 2015 9:00 pm Post subject: Moving eselect* from app-admin to app-eselect [Solved] |
 |
|
Hi,
It look like someone is actually doing this;
http://www.eenyhelp.com/answer/gentoo-dev-rfc-app-eselect-category-help-215626010.html
Except when I update my system it fails because the files are still owned by the package as it is installed from app-admin.
Shouldn't the app-admin versions be uninstalled first, then masked so they don't get re-installed.
| Code: |
>>> Failed to install app-eselect/eselect-lib-bin-symlink-0.1.1
* Detected file collision(s):
*
* /usr/share/doc/eselect-lib-bin-symlink-0.1.1/NEWS.bz2
* /usr/share/eselect/libs/bin-symlink.bash
|
I manually unmerged the app-admin version and the app-eselect version installed, but then the app-admin version failed when the world update wanted to re-install it.
I was able to manually uninstall the app-admin version of a couple of other eselect packages and the app-eselect versions installed successfully, however, this is very tedious and I have more than one computer.
At the moment then, world update is broken for me.
Brendan
Last edited by bjdacre on Tue Mar 31, 2015 11:16 pm; edited 1 time in total |
|
| Back to top |
|
 |
as.gentoo
Guru
Joined: 07 Aug 2004
Posts: 319
|
| Posted: Tue Mar 31, 2015 9:26 pm Post subject: Re: Moving eselect* from app-admin to app-eselect |
|
|
I have something similar:
| Code: | >>> Verifying ebuild manifests
>>> Emerging (1 of 18) x11-libs/libdrm-2.4.60::gentoo
>>> Installing (1 of 18) x11-libs/libdrm-2.4.60::gentoo
>>> Emerging (2 of 18) x11-base/xorg-drivers-1.17::gentoo
>>> Installing (2 of 18) x11-base/xorg-drivers-1.17::gentoo
>>> Emerging (3 of 18) app-eselect/eselect-fontconfig-1.1::gentoo
>>> Installing (3 of 18) app-eselect/eselect-fontconfig-1.1::gentoo
>>> Failed to install app-eselect/eselect-fontconfig-1.1, Log file:
>>> '/var/log/portage/app-eselect:eselect-fontconfig-1.1:20150331-210226.log.gz'
>>> Jobs: 2 of 18 complete, 1 failed Load avg: 1.00, 1.11, 2.36
*** Resuming merge...
These are the packages that would be merged, in order:
Calculati ... done!
* Package: app-eselect/eselect-fontconfig-1.1
* Repository: gentoo
* Maintainer: fonts@gentoo.org
* USE: abi_x86_64 amd64 elibc_glibc kernel_linux policykit userland_GNU
* FEATURES: preserve-libs sandbox splitdebug userpriv usersandbox
>>> Unpacking source...
>>> Unpacking fontconfig.eselect-1.1.bz2 to /mnt/ramdisk/portage/app-eselect/eselect-fontconfig-1.1/work
>>> Source unpacked in /mnt/ramdisk/portage/app-eselect/eselect-fontconfig-1.1/work
>>> Compiling source in /mnt/ramdisk/portage/app-eselect/eselect-fontconfig-1.1/work ...
>>> Source compiled.
>>> Test phase [not enabled]: app-eselect/eselect-fontconfig-1.1
>>> Install eselect-fontconfig-1.1 into /mnt/ramdisk/portage/app-eselect/eselect-fontconfig-1.1/image/ category app-eselect
>>> Completed installing eselect-fontconfig-1.1 into /mnt/ramdisk/portage/app-eselect/eselect-fontconfig-1.1/image/
./
./usr/
./usr/share/
./usr/share/eselect/
./usr/share/eselect/modules/
./usr/share/eselect/modules/fontconfig.eselect
>>> Done.
* checking 1 files for package collisions
* 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). See
* http://wiki.gentoo.org/wiki/Knowledge_Base:Blockers for tips on how to
* solve the problem. And once again, please do NOT file a bug report
* unless you have completely understood the above message.
*
* Detected file collision(s):
*
* /usr/share/eselect/modules/fontconfig.eselect
*
* Searching all installed packages for file collisions...
*
* Press Ctrl-C to Stop
*
* app-admin/eselect-fontconfig-1.1:0::gentoo
* /usr/share/eselect/modules/fontconfig.eselect
*
* Package 'app-eselect/eselect-fontconfig-1.1' NOT merged due to file
* collisions. If necessary, refer to your elog messages for the whole
* content of the above message. |
Now,
"[...] 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."
AFAIK eselect is gentoo specific, so it should be known where such files come from...
How can I be sure that '--skipfirst' doesn't break my system? |
|
| Back to top |
|
|
Fred Krogh
Veteran
Joined: 07 Feb 2005
Posts: 1036
Location: Tujunga, CA
|
| Posted: Tue Mar 31, 2015 9:32 pm Post subject: |
|
|
| I had similar problem. Unmerged most of the app-admin packages that were causing conflicts with no great problems. BUT,the app-admin and app-eselect versions of eselect-lib-bin-symlink seems to want both versions, and they are not compatible. I think bjdacre had it right on how things should have been done. And it seems there is still one problem if one tries to work through it manually. |
|
| Back to top |
|
|
Markus09
Tux's lil' helper
Joined: 22 Mar 2013
Posts: 78
|
| Posted: Tue Mar 31, 2015 9:33 pm Post subject: |
|
|
I can confirm that world update is broken with this app-admin vs. app-eselect change.
So I did a
| Code: | | emerge -a -C 'app-admin/eselect-*' |
to remove all eselect-* packages from the app-admin path.
Then I checked the output of the world emerge for app-admin/eselect-* packages.
As I need an older nvidia driver which needs
app-admin/eselect-opengl and app-admin/eselect-opencl
I listed these the packages in
/etc/portage/profile/package.provided
to be able to use the old package. (Note: package.provided needs the package name with package version!)
This might not be necessary for you, if you just use current packages.
The other packages only pull the app-eselect/eselect* packages on my system.
Then I did
| Code: | | emerge -uaDNv @world |
to install the app-eselect/eselect-* packages.
BR,
Markus |
|
| Back to top |
|
|
derk
Guru
Joined: 10 Mar 2003
Posts: 347
Location: St Thomas Ontario
|
| Posted: Tue Mar 31, 2015 9:44 pm Post subject: |
|
|
| this is a migration bug ..545182 .. there should have been portage database migration adjustments made and the whole thing would have been invisible .. but stuff has happened out of sequence .. thus pain and confusion |
|
| Back to top |
|
|
derk
Guru
Joined: 10 Mar 2003
Posts: 347
Location: St Thomas Ontario
|
| Posted: Tue Mar 31, 2015 9:57 pm Post subject: |
|
|
| a now you should be able to --sync and get the fixes automagicly .. worked for me at least .. notice the database migration stuff at the end .. my guess is a the master portage tree was not locked out briefly for all the updates to get added prior to releasing .. if you still have problems either wait or add to bug report.. |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54239
Location: 56N 3W
|
| Posted: Tue Mar 31, 2015 10:01 pm Post subject: |
|
|
derk,
Correct.
The mirror update process is not atomic.
The CVS commit process is not atomic either.
This means that some users can get broken --syncs.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
bjdacre
n00b
Joined: 25 Nov 2014
Posts: 35
Location: Whangarei, NZ
|
| Posted: Tue Mar 31, 2015 11:15 pm Post subject: |
|
|
Thanks everyone.
I re-ran the sync and update and it now appears to work. 
Brendan |
|
| Back to top |
|
|
|
Portage & Programming
