Привет, ЛОР!
Подскажи, как правильно решать подобного рода проблемы в gentoo?
!!! Multiple package instances within a single package slot have been pulled
!!! into the dependency graph, resulting in a slot conflict:
app-text/libetonyek:0
(app-text/libetonyek-0.1.1:0/0::gentoo, ebuild scheduled for merge) pulled in by
(no parents that aren't satisfied by other packages in this slot)
(app-text/libetonyek-0.0.3:0/0::gentoo, ebuild scheduled for merge) pulled in by
=app-text/libetonyek-0.0* required by (app-office/libreoffice-bin-4.2.8.2:0/0::gentoo, installed)
^ ^^^^
dev-libs/boost:0
(dev-libs/boost-1.56.0-r1:0/1.56.0::gentoo, ebuild scheduled for merge) pulled in by
(no parents that aren't satisfied by other packages in this slot)
(dev-libs/boost-1.55.0-r2:0/1.55.0::gentoo, ebuild scheduled for merge) pulled in by
>=dev-libs/boost-1.46:0/1.55.0= required by (app-office/libreoffice-bin-4.2.8.2:0/0::gentoo, installed)
^^^^^^^^^^
dev-libs/boost:0/1.55.0 required by (app-office/libreoffice-bin-4.2.8.2:0/0::gentoo, installed)
^^^^^^^^^
app-text/libebook:0
(app-text/libebook-0.1.1:0/0::gentoo, ebuild scheduled for merge) pulled in by
(no parents that aren't satisfied by other packages in this slot)
(app-text/libebook-0.0.2:0/0::gentoo, ebuild scheduled for merge) pulled in by
=app-text/libebook-0.0* required by (app-office/libreoffice-bin-4.2.8.2:0/0::gentoo, installed)
^ ^^^^
dev-libs/liborcus:0
(dev-libs/liborcus-0.7.0:0/0::gentoo, ebuild scheduled for merge) pulled in by
(no parents that aren't satisfied by other packages in this slot)
(dev-libs/liborcus-0.5.1:0/0.5::gentoo, ebuild scheduled for merge) pulled in by
=dev-libs/liborcus-0.5* required by (app-office/libreoffice-bin-4.2.8.2:0/0::gentoo, installed)
^ ^^^^
app-text/poppler:0
(app-text/poppler-0.30.0:0/49::gentoo, ebuild scheduled for merge) pulled in by
(no parents that aren't satisfied by other packages in this slot)
(app-text/poppler-0.26.5:0/46::gentoo, ebuild scheduled for merge) pulled in by
app-text/poppler:0/46 required by (app-office/libreoffice-bin-4.2.8.2:0/0::gentoo, installed)
^^^^^
>=app-text/poppler-0.16:0/46=[xpdf-headers(+),cxx] required by (app-office/libreoffice-bin-4.2.8.2:0/0::gentoo, installed)
^^^^^^
dev-libs/libixion:0
(dev-libs/libixion-0.7.0:0/0::gentoo, ebuild scheduled for merge) pulled in by
>=dev-libs/libixion-0.7.0 required by (dev-libs/liborcus-0.7.0:0/0::gentoo, ebuild scheduled for merge)
^^ ^^^^^
(dev-libs/libixion-0.5.0:0/0.5::gentoo, ebuild scheduled for merge) pulled in by
=dev-libs/libixion-0.5* required by (dev-libs/liborcus-0.5.1:0/0.5::gentoo, ebuild scheduled for merge)
^ ^^^^
dev-util/boost-build:0
(dev-util/boost-build-1.56.0:0/0::gentoo, installed) pulled in by
=dev-util/boost-build-1.56* required by (dev-libs/boost-1.56.0-r1:0/1.56.0::gentoo, ebuild scheduled for merge)
^ ^^^^^
(dev-util/boost-build-1.55.0-r1:0/0::gentoo, ebuild scheduled for merge) pulled in by
=dev-util/boost-build-1.55* required by (dev-libs/boost-1.55.0-r2:0/1.55.0::gentoo, ebuild scheduled for merge)
^ ^^^^^
media-video/ffmpeg:0
(media-video/ffmpeg-2.2.11:0/52.55.55::gentoo, ebuild scheduled for merge) pulled in by
>=media-video/ffmpeg-1.2.6:0/52.55.55=[threads] required by (media-video/mplayer2-2.0_p20131009:0/0::gentoo, installed)
^^^^^^^^^^^^
(media-video/ffmpeg-2.5:0/54.56.56::gentoo, installed) pulled in by
>=media-video/ffmpeg-2.3:0 required by (media-video/handbrake-0.10.0:0/0::gentoo, installed)
^^ ^^^^^
It may be possible to solve this problem by using package.mask to
prevent one of those packages from being selected. However, it is also
possible that conflicting dependencies exist such that they are
impossible to satisfy simultaneously. If such a conflict exists in
the dependencies of two different packages, then those packages can
not be installed simultaneously. You may want to try a larger value of
the --backtrack option, such as --backtrack=30, in order to see if
that will solve this conflict automatically.
Часто при обновлениях зависимости libreoffice-bin попадают в такую вот беду. Руками их все маскировать? Как тогда я узнаю, что они стали готовы к обновлению (а они рано или поздно станут)? Или как-то устанавилвать в разные слоты? Тогда стоит ли овчика выделки, и не проще ли некоторое время не обновлять эти пакеты, пока все не разрулится «само-собой» в репозитории?
