Package ‘x11-proto/printproto-1.0.5’ NOT merged due to file collisions.

Ха! Прикол сегодня с Gentoo забавный приключился 🙂
Решил обновиться, делаю как всегда:

laptop ~ # eix-sync
laptop ~ # emerge -uavDN world

Все вроде потихоньку собирается …. а потом на тебе! Ошибочка!

'/var/tmp/portage/x11-proto/printproto-1.0.5/image//usr/include/X11/extensions'
make[1]: Leaving directory `/var/tmp/portage/x11-proto/printproto-1.0.5/work/printproto-1.0.5_build'
>>> Completed installing printproto-1.0.5 into /var/tmp/portage/x11-proto/printproto-1.0.5/image/

ecompressdir: bzip2 -9 /usr/share/man

>>> Installing (11 of 76) x11-proto/printproto-1.0.5
* checking 5 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 / ` 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.
*
* Detected file collision(s):
*
*   /usr/share/man/man7/Xprint.7.bz2
*
* Searching all installed packages for file collisions...
*
* Press Ctrl-C to Stop
*
* app-doc/xorg-docs-1.4-r1
*   /usr/share/man/man7/Xprint.7.bz2
*
* Package '
x11-proto/printproto-1.0.5' NOT merged due to file
* collisions. If necessary, refer to your elog messages for the whole
* content of the above message.

>>> Failed to install x11-proto/printproto-1.0.5, Log file:

>>>  '
/var/tmp/portage/x11-proto/printproto-1.0.5/temp/build.log'

* Regenerating GNU info directory index...
* Processed 186 info files.

* IMPORTANT: 3 config files in '
/etc' need updating.
* See the CONFIGURATION FILES section of the emerge
* man page to learn how to update config files.
* After world updates, it is important to remove obsolete packages with
* emerge --depclean. Refer to `man emerge` for more information.
laptop ~ #

Почти что русским языком написано что матерщина изза некоего пакета xorg-docs. Но вот тут и начинается самое интересное!

laptop ~ # eix xorg-docs
No matches found.
laptop ~ # equery depends xorg-docs
[ Searching for packages depending on xorg-docs... ]
laptop ~ #

Во как оказывается … eix про такой пакетик вообще ничего не знает! Вот так чудеса!
Зато поиск emerge выдает все как надо 🙂

laptop ~ # emerge --search xorg-docs
Searching...
[ Results for search key : xorg-docs ]
[ Applications found : 1 ]

*  app-doc/xorg-docs
Latest version installed: 1.4-r1
Homepage:      http://xorg.freedesktop.org/
Description:   X.Org docs
License:       xorg-docs

laptop ~ # emerge --unmerge app-doc/xorg-docs
* This action can remove important packages! In order to be safer, use
* `emerge -pv --depclean ` to check for reverse dependencies before
* removing packages.

app-doc/xorg-docs
selected: 1.4-r1
protected: none
omitted: none

All selected packages: app-doc/xorg-docs-1.4-r1

>>> 'Selected' packages are slated for removal.
>>> 'Protected' and 'omitted' packages will not be removed.

>>> Waiting 5 seconds before starting...
>>> (Control-C to abort)...
>>> Unmerging in:  5 4 3 2 1
>>> Unmerging app-doc/xorg-docs-1.4-r1...

* GNU info directory index is up-to-date.

* IMPORTANT: 3 config files in '/etc' need updating.
* See the CONFIGURATION FILES section of the emerge
* man page to learn how to update config files.
laptop ~ #

Ну вот так вот 🙂 Собственно после удаления пакета xorg-docs обновление пошло нормально.

    • Serge
    • Январь 9th, 2016 12:15дп

    Спасибо.Решил похожую проблему с помощью этого поста.

  1. Трэкбэков пока нет.

Why ask?