public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Laurence Perkins <lperkins@openeye.net>
To: "gentoo-user@lists.gentoo.org" <gentoo-user@lists.gentoo.org>
Subject: RE: [gentoo-user] world updates blocked by Qt
Date: Wed, 11 Oct 2023 17:13:09 +0000	[thread overview]
Message-ID: <MW2PR07MB4058C1505B5C7C949C16F4CED2CCA@MW2PR07MB4058.namprd07.prod.outlook.com> (raw)
In-Reply-To: <ZSbQ4vv3zJ9Dlvn6@ca.inter.net>

> -----Original Message-----
> From: Philip Webb <purslow@ca.inter.net> 
> Sent: Wednesday, October 11, 2023 9:44 AM
> To: Gentoo User <gentoo-user@lists.gentoo.org>
> Subject: [gentoo-user] world updates blocked by Qt
> 
> CAUTION: This is an EXTERNAL email. Do not click links or open attachments unless you recognize the sender and know the content is safe.
> 
> 231011 Alan McKinnon wrote:
> > Today a sync and emerge world produces a huge list of blockers.
> > qt 5.15.10 is currently installed and qt 5.15.11 is new in the tree 
> > and being blocked.
> > All the visible blockers are Qt itself so --verbose-conflicts is needed.
> 
> My experience for some time has been that Qt pkgs block one another, st the only way out is to unmerge them all, then remerge them all.
> If anyone knows a better method, please let us know
> 
If you don't want to do that, then adding all the currently installed qt packages to the merge list explicitly works as well.  If you're good with eix's search and output settings it can be done without too much agony.

LMP


  reply	other threads:[~2023-10-11 17:13 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-11 16:44 [gentoo-user] world updates blocked by Qt Philip Webb
2023-10-11 17:13 ` Laurence Perkins [this message]
2023-10-11 17:41 ` Dale
2023-10-12  6:31 ` Wols Lists
  -- strict thread matches above, loose matches on Subject: below --
2023-10-11 13:43 Alan McKinnon
2023-10-11 13:59 ` Neil Bothwick
2023-10-11 14:04   ` Alan McKinnon
2023-10-11 17:46     ` Neil Bothwick
2023-10-11 14:07 ` Cara Salter
2023-10-11 14:14   ` Alan McKinnon
2023-10-11 14:17     ` Cara Salter
2023-10-11 14:14 ` Philip Webb
2023-10-11 14:16   ` Alan McKinnon
2023-10-11 14:48 ` Michael Cook
2023-10-11 17:37   ` Dale
2023-10-11 18:14   ` Alan McKinnon

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=MW2PR07MB4058C1505B5C7C949C16F4CED2CCA@MW2PR07MB4058.namprd07.prod.outlook.com \
    --to=lperkins@openeye.net \
    --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