From: n952162 <n952162@web.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] handling a slot collision (for telegram) [SOLVED]
Date: Sat, 16 May 2020 23:42:47 +0200 [thread overview]
Message-ID: <65ecad0a-4675-49f6-0d1d-19656d9228f9@web.de> (raw)
In-Reply-To: <TC257RUQ.OY3NQNGN.XBOTWX3P@GUGEQYNV.WMCZBSLX.RXF3QQNC>
Thanks to the suggestions I got from the list, I was able to update QT
as follows:
emerge -vu dev-qt/qtgui dev-qt/qtx11extras dev-qt/qtopengl
dev-qt/qtprintsupport dev-qt/qtwidgets dev-qt/qtxml
dev-qt/linguist-tools dev-qt/qtnetwork dev-qt/qtsvg dev-qt/qtcore
and complete the installation of telegram-desktop. Thanks to all.
On 05/16/20 18:18, Jack wrote:
> For these, you probably need to upgrade every qt package to 5.14.
>
> On 2020.05.16 04:46, n952162 wrote:
>> How do I handle a slot collision?
>>
>> I'm trying to install telegram but get a slot conflict for
>> dev-qt/qtwidgets - it wants 5.14.1-r1 and I have 5.13-2 installed.
>>
>> I see that these packages want 5.13.2
>>
>> dev-qt/qtprintsupport-5.13.2
>> dev-qt/qtsvg-5.13.2
>> dev-qt/qtopengl-5.13.2
>>
>> Their ebuilds are like
>>
>> ~dev-qt/qtwidgets-${PV}[gles2-only=]
>>
>> so, qtwidget is dependent on the revision of the package being built.
>>
>> I have no ebuilds (any longer) for qtwidget-5.13, only for 5.14.
>>
>> If I try to emerge dev-qt/qtcore-5.14.1-r1, I get a slot collision.
>> If I try to remove dev-qt/qtcore-5.13.2-r1 (using -p), it tells me
>>
>> >>> No packages selected for removal by depclean
> You have to see what is pulling in qtcore - it's probably some other
> qt package at 5.13, which then also needs to be upgraded to 5.14.
>>
>> I don't know what to try next.
>
prev parent reply other threads:[~2020-05-16 21:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-16 8:46 [gentoo-user] handling a slot collision (for telegram) n952162
2020-05-16 16:18 ` Jack
2020-05-16 21:42 ` n952162 [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=65ecad0a-4675-49f6-0d1d-19656d9228f9@web.de \
--to=n952162@web.de \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox