From: n952162 <n952162@web.de>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] handling a slot collision (for telegram)
Date: Sat, 16 May 2020 10:46:32 +0200 [thread overview]
Message-ID: <fba0c297-fc3d-127b-4458-736627999b4b@web.de> (raw)
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
I don't know what to try next.
next reply other threads:[~2020-05-16 8:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-16 8:46 n952162 [this message]
2020-05-16 16:18 ` [gentoo-user] handling a slot collision (for telegram) Jack
2020-05-16 21:42 ` [gentoo-user] handling a slot collision (for telegram) [SOLVED] n952162
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=fba0c297-fc3d-127b-4458-736627999b4b@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