From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id AE4331382C5 for ; Sat, 16 May 2020 16:18:37 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 9DE1CE0A46; Sat, 16 May 2020 16:18:33 +0000 (UTC) Received: from mail-qt1-f195.google.com (mail-qt1-f195.google.com [209.85.160.195]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 4D79EE09F9 for ; Sat, 16 May 2020 16:18:33 +0000 (UTC) Received: by mail-qt1-f195.google.com with SMTP id z18so4664978qto.2 for ; Sat, 16 May 2020 09:18:33 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:reply-to:subject:to:cc:mime-version :references:in-reply-to:message-id:content-disposition :content-transfer-encoding; bh=at57ybMJANfRsREsG5fyu61zmuMP5Y/iqw4jrTY6Lqo=; b=QquuUz409S3QycsvmpOdw5RWB1jNhjQVPPAx2nMrBCJwMNprYol7l8ah7cyMWSaFkS eDY3044qiAv9dJc8iN2FCh72E4YMF64phcvnxhO/2c/JHHiuPfotfemPiCZQ/oV/ONOy MwUyFSFrX217EhdDWkE1ecyhcFEP3JV9BIH8QcB5zndWr81qUPn4ZC4Fk+gtLlfUwSFd SIddUaMnoml55Gac/YT19R6JXdFi2vRyzplXe8AqqVupNie5GkQGbkMcpFARWFobe6B6 pYxv9GrmZ7NH3iXfvp0fReQYShh6uINSkWq58WiBsiwP4jF6xUdzsxpUcn6DvaYsKb/o N4dw== X-Gm-Message-State: AOAM530l+OF3bXe9FYB635B284YULeeg8OJKri8ZtdyyVEQ03J2LCTnc O0CrDGiT7tvEby5IYSwqMTHsg7ZgH4xSfQ== X-Google-Smtp-Source: ABdhPJxdxFsEJoeWEmj4ryDSQ9wEF1CvqwAwxyRSwr4NIqkRiXlN+iMwZ3w7obkOKSThM0e3ILZf0Q== X-Received: by 2002:ac8:6b55:: with SMTP id x21mr8666187qts.75.1589645912484; Sat, 16 May 2020 09:18:32 -0700 (PDT) Received: from ffortso9 (c-76-23-130-96.hsd1.ct.comcast.net. [76.23.130.96]) by smtp.gmail.com with ESMTPSA id e28sm4161640qka.125.2020.05.16.09.18.31 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sat, 16 May 2020 09:18:32 -0700 (PDT) Date: Sat, 16 May 2020 12:18:31 -0400 From: Jack Subject: Re: [gentoo-user] handling a slot collision (for telegram) To: gentoo-user@lists.gentoo.org Cc: Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 References: In-Reply-To: X-Mailer: Balsa 2.5.10-65-geb847a2f0 Message-Id: Content-Type: text/plain; charset=ISO-8859-1; DelSp=Yes; Format=Flowed Content-Disposition: inline Content-Transfer-Encoding: quoted-printable X-Archives-Salt: 609f1bdf-8189-4470-bb92-1d14b4fe41f3 X-Archives-Hash: 4f6d251a91dddc0e39a22ad6c4bbc306 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? >=20 > 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. >=20 > I see that these packages want 5.13.2 >=20 > =A0=A0=A0=A0=A0=A0=A0 dev-qt/qtprintsupport-5.13.2 > =A0=A0=A0=A0=A0=A0=A0 dev-qt/qtsvg-5.13.2 > =A0=A0=A0=A0=A0=A0=A0 dev-qt/qtopengl-5.13.2 >=20 > Their ebuilds are like >=20 > ~dev-qt/qtwidgets-${PV}[gles2-only=3D] >=20 > so, qtwidget is dependent on the revision of the package being built. >=20 > I have no ebuilds (any longer) for qtwidget-5.13, only for 5.14. >=20 > 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 >=20 > >>> No packages selected for removal by depclean You have to see what is pulling in qtcore - it's probably some other qt =20 package at 5.13, which then also needs to be upgraded to 5.14. >=20 > I don't know what to try next.