| 1 |
On 2018-12-02, allan gottlieb wrote: |
| 2 |
|
| 3 |
> On one of my stable amd64 systems, I just ran |
| 4 |
> |
| 5 |
> emerge --update --changed-use --with-bdeps=n --deep @world |
| 6 |
> |
| 7 |
> and received a list of 65 packages to merge (many gnome). |
| 8 |
> |
| 9 |
> The update completed and I was told |
| 10 |
> |
| 11 |
> !!! existing preserved libs: |
| 12 |
>>>> package: dev-libs/libcdio-2.0.0-r1 |
| 13 |
> * - /usr/lib64/libcdio.so.16 |
| 14 |
> * - /usr/lib64/libcdio.so.16.0.0 |
| 15 |
> * used by /usr/bin/libcdio-paranoia (dev-libs/libcdio-paranoia-0.93_p1) |
| 16 |
> * used by /usr/lib64/libcdio_cdda.so.2.0.0 (dev-libs/libcdio-paranoia-0.93_p1) |
| 17 |
> * used by /usr/lib64/libcdio_paranoia.so.2.0.0 (dev-libs/libcdio-paranoia-0.93_p1) |
| 18 |
> * used by /usr/libexec/gvfsd-cdda (gnome-base/gvfs-1.32.2) |
| 19 |
> Use emerge @preserved-rebuild to rebuild packages using these libraries |
| 20 |
> |
| 21 |
> When I ran emerge --pretend @preserved-rebuild I was told to run |
| 22 |
> merge dev-qt/qtcore-5.11.1 which is ~amd64, which seems wrong. |
| 23 |
> The full output is below. |
| 24 |
> Can someone please explain what is happening. |
| 25 |
> |
| 26 |
> thanks, |
| 27 |
> allan |
| 28 |
> |
| 29 |
> E6430 ~ # emerge --pretend @preserved-rebuild |
| 30 |
> These are the packages that would be merged, in reverse order: |
| 31 |
> |
| 32 |
> Calculating dependencies... done! |
| 33 |
> [ebuild R ] gnome-base/gvfs-1.32.2 |
| 34 |
> [ebuild R ] dev-libs/libcdio-paranoia-0.93_p1 |
| 35 |
> [nomerge ] gnome-base/gvfs-1.32.2 |
| 36 |
> [nomerge ] sys-fs/udisks-2.7.4-r1 |
| 37 |
> [nomerge ] sys-libs/libblockdev-2.14-r1 |
| 38 |
> [nomerge ] dev-libs/volume_key-0.3.11 |
| 39 |
> [nomerge ] app-crypt/gpgme-1.11.1 |
| 40 |
> [nomerge ] dev-qt/qttest-5.9.6 |
| 41 |
> [ebuild UD~] dev-qt/qtcore-5.9.6-r1 [5.11.1-r1] |
| 42 |
> |
| 43 |
> !!! Multiple package instances within a single package slot have been pulled |
| 44 |
> !!! into the dependency graph, resulting in a slot conflict: |
| 45 |
> |
| 46 |
> dev-qt/qtcore:5 |
| 47 |
> |
| 48 |
> (dev-qt/qtcore-5.11.1-r1:5/5.11::gentoo, installed) pulled in by |
| 49 |
> ~dev-qt/qtcore-5.11.1 required by (dev-qt/qtconcurrent-5.11.1:5/5.11::gentoo, installed) |
| 50 |
> ^ ^^^^^^ |
| 51 |
> (and 9 more with the same problem) |
| 52 |
> |
| 53 |
> (dev-qt/qtcore-5.9.6-r1:5/5.9::gentoo, ebuild scheduled for merge) pulled in by |
| 54 |
> ~dev-qt/qtcore-5.9.6 required by (dev-qt/qttest-5.9.6:5/5.9::gentoo, installed) |
| 55 |
> ^ ^^^^^ |
| 56 |
[...] |
| 57 |
|
| 58 |
I would try upgrading qttest first (it is the one pulling |
| 59 |
qtcore-5.9.6{,-r1}, according to the output). Do you have any qttest |
| 60 |
5.11.* version which is keyworded amd64 (and not ~amd64)? |
| 61 |
|
| 62 |
Here and on https://packages.gentoo.org/packages/dev-qt/qttest, |
| 63 |
qttest-5.11.1 is amd64. Maybe the tree was in an inconsistent state when |
| 64 |
you last synced it? |
| 65 |
|
| 66 |
If you have qttest 5.11.1 in ~amd64 and you need a very quick fix, try |
| 67 |
adding it to package.accept_keywords and upgrading it. Otherwise, you |
| 68 |
might prefer to sync the portage tree again first. |
| 69 |
|
| 70 |
-- |
| 71 |
Nuno Silva |
Archives