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