| 1 |
On one of my stable amd64 systems, I just ran |
| 2 |
|
| 3 |
emerge --update --changed-use --with-bdeps=n --deep @world |
| 4 |
|
| 5 |
and received a list of 65 packages to merge (many gnome). |
| 6 |
|
| 7 |
The update completed and I was told |
| 8 |
|
| 9 |
!!! existing preserved libs: |
| 10 |
>>> package: dev-libs/libcdio-2.0.0-r1 |
| 11 |
* - /usr/lib64/libcdio.so.16 |
| 12 |
* - /usr/lib64/libcdio.so.16.0.0 |
| 13 |
* used by /usr/bin/libcdio-paranoia (dev-libs/libcdio-paranoia-0.93_p1) |
| 14 |
* used by /usr/lib64/libcdio_cdda.so.2.0.0 (dev-libs/libcdio-paranoia-0.93_p1) |
| 15 |
* used by /usr/lib64/libcdio_paranoia.so.2.0.0 (dev-libs/libcdio-paranoia-0.93_p1) |
| 16 |
* used by /usr/libexec/gvfsd-cdda (gnome-base/gvfs-1.32.2) |
| 17 |
Use emerge @preserved-rebuild to rebuild packages using these libraries |
| 18 |
|
| 19 |
When I ran emerge --pretend @preserved-rebuild I was told to run |
| 20 |
merge dev-qt/qtcore-5.11.1 which is ~amd64, which seems wrong. |
| 21 |
The full output is below. |
| 22 |
Can someone please explain what is happening. |
| 23 |
|
| 24 |
thanks, |
| 25 |
allan |
| 26 |
|
| 27 |
E6430 ~ # emerge --pretend @preserved-rebuild |
| 28 |
These are the packages that would be merged, in reverse order: |
| 29 |
|
| 30 |
Calculating dependencies... done! |
| 31 |
[ebuild R ] gnome-base/gvfs-1.32.2 |
| 32 |
[ebuild R ] dev-libs/libcdio-paranoia-0.93_p1 |
| 33 |
[nomerge ] gnome-base/gvfs-1.32.2 |
| 34 |
[nomerge ] sys-fs/udisks-2.7.4-r1 |
| 35 |
[nomerge ] sys-libs/libblockdev-2.14-r1 |
| 36 |
[nomerge ] dev-libs/volume_key-0.3.11 |
| 37 |
[nomerge ] app-crypt/gpgme-1.11.1 |
| 38 |
[nomerge ] dev-qt/qttest-5.9.6 |
| 39 |
[ebuild UD~] dev-qt/qtcore-5.9.6-r1 [5.11.1-r1] |
| 40 |
|
| 41 |
!!! Multiple package instances within a single package slot have been pulled |
| 42 |
!!! into the dependency graph, resulting in a slot conflict: |
| 43 |
|
| 44 |
dev-qt/qtcore:5 |
| 45 |
|
| 46 |
(dev-qt/qtcore-5.11.1-r1:5/5.11::gentoo, installed) pulled in by |
| 47 |
~dev-qt/qtcore-5.11.1 required by (dev-qt/qtconcurrent-5.11.1:5/5.11::gentoo, installed) |
| 48 |
^ ^^^^^^ |
| 49 |
(and 9 more with the same problem) |
| 50 |
|
| 51 |
(dev-qt/qtcore-5.9.6-r1:5/5.9::gentoo, ebuild scheduled for merge) pulled in by |
| 52 |
~dev-qt/qtcore-5.9.6 required by (dev-qt/qttest-5.9.6:5/5.9::gentoo, installed) |
| 53 |
^ ^^^^^ |
| 54 |
|
| 55 |
NOTE: Use the '--verbose-conflicts' option to display parents omitted above |
| 56 |
|
| 57 |
It may be possible to solve this problem by using package.mask to |
| 58 |
prevent one of those packages from being selected. However, it is also |
| 59 |
possible that conflicting dependencies exist such that they are |
| 60 |
impossible to satisfy simultaneously. If such a conflict exists in |
| 61 |
the dependencies of two different packages, then those packages can |
| 62 |
not be installed simultaneously. |
| 63 |
|
| 64 |
For more information, see MASKED PACKAGES section in the emerge man |
| 65 |
page or refer to the Gentoo Handbook. |
| 66 |
|
| 67 |
|
| 68 |
The following keyword changes are necessary to proceed: |
| 69 |
(see "package.accept_keywords" in the portage(5) man page for more details) |
| 70 |
# required by dev-qt/qttest-5.9.6::gentoo |
| 71 |
# required by app-crypt/gpgme-1.11.1::gentoo[qt5] |
| 72 |
# required by app-crypt/seahorse-3.20.0::gentoo |
| 73 |
# required by gnome-base/gnome-core-apps-3.24.2::gentoo |
| 74 |
# required by gnome-base/gnome-3.24.2::gentoo |
| 75 |
# required by @selected |
| 76 |
# required by @world (argument) |
| 77 |
=dev-qt/qtcore-5.9.6-r1 ~amd64 |
| 78 |
|
| 79 |
* In order to avoid wasting time, backtracking has terminated early |
| 80 |
* due to the above autounmask change(s). The --autounmask-backtrack=y |
| 81 |
* option can be used to force further backtracking, but there is no |
| 82 |
* guarantee that it will produce a solution. |
| 83 |
|
| 84 |
* IMPORTANT: 1 news items need reading for repository 'gentoo'. |
| 85 |
* Use eselect news read to view new items. |
| 86 |
|
| 87 |
E6430 ~ # |
Archives