Mailing List Archive: world updates blocked by Qt

world updates blocked by Qt

Oct 11, 2023, 6:43 AM

Post #1 of 19 (378 views)

Hi all,

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.

That will be an exceptionally long list and today I feel really lazy and
unwilling :-D
Has anyone seen what the actual blockers are?
I spotted okular, I suspect there are more.

--
Alan McKinnon
alan dot mckinnon at gmail dot com

Re: world updates blocked by Qt [ In reply to ]

neil at digimed

Oct 11, 2023, 6:59 AM

Post #2 of 19 (378 views)

Permalink

On Wed, 11 Oct 2023 15:43:46 +0200, 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.

No such issues here, on ~amd64.

> That will be an exceptionally long list and today I feel really lazy and
> unwilling :-D
> Has anyone seen what the actual blockers are?
> I spotted okular, I suspect there are more.

Have you tried syncing again, just in case you caught it partway through
a stack of Qt packages being updated?

--
Neil Bothwick

If at first you don't succeed, skydiving is not for you.

Re: world updates blocked by Qt [ In reply to ]

alan.mckinnon at gmail

Oct 11, 2023, 7:04 AM

Post #3 of 19 (378 views)

Permalink

On Wed, Oct 11, 2023 at 3:59?PM Neil Bothwick <neil@digimed.co.uk> wrote:

> On Wed, 11 Oct 2023 15:43:46 +0200, 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.
>
> No such issues here, on ~amd64.
>

Hmmm. When did you last sync? Forgot to mention I am ~amd too

>
> > That will be an exceptionally long list and today I feel really lazy and
> > unwilling :-D
> > Has anyone seen what the actual blockers are?
> > I spotted okular, I suspect there are more.
>
> Have you tried syncing again, just in case you caught it partway through
> a stack of Qt packages being updated?
>

Yes, synced twice today, 2 hours apart. No change

--
Alan McKinnon
alan dot mckinnon at gmail dot com

Re: world updates blocked by Qt [ In reply to ]

cara at devcara

Oct 11, 2023, 7:07 AM

Post #4 of 19 (378 views)

Permalink

Re: world updates blocked by Qt [ In reply to ]

purslow at ca

Oct 11, 2023, 7:14 AM

Post #5 of 19 (378 views)

Permalink

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.

--
========================,,============================================
SUPPORT ___________//___, Philip Webb
ELECTRIC /] [] [] [] [] []| Cities Centre, University of Toronto
TRANSIT `-O----------O---' purslowatcadotinterdotnet

Re: world updates blocked by Qt [ In reply to ]

alan.mckinnon at gmail

Oct 11, 2023, 7:14 AM

Post #6 of 19 (378 views)

Permalink

On Wed, Oct 11, 2023 at 4:07?PM Cara Salter <cara@devcara.com> wrote:

> On 10/11/23 09:43, Alan McKinnon wrote:
> > Hi all,
> >
> > 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.
> I had a similar issue -- I resolved it by uninstalling opensoundmeter
> and libreoffice-bin temporarily.
>
> Today's sync/merge is going smoothly so far.
>

Strange, eix says no such package as opensoundmeter and libreoffice-bin is
not installed here

--
Alan McKinnon
alan dot mckinnon at gmail dot com

Re: world updates blocked by Qt [ In reply to ]

alan.mckinnon at gmail

Oct 11, 2023, 7:16 AM

Post #7 of 19 (378 views)

Permalink

On Wed, Oct 11, 2023 at 4:14?PM Philip Webb <purslow@ca.inter.net> wrote:

> 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.
>

My experience is 4 years out of date, I don't recall ever having to do that.

Alan

--
Alan McKinnon
alan dot mckinnon at gmail dot com

Re: world updates blocked by Qt [ In reply to ]

cara at devcara

Oct 11, 2023, 7:17 AM

Post #8 of 19 (378 views)

Permalink

On 10/11/23 10:14, Alan McKinnon wrote:
>
> Strange, eix says no such package as opensoundmeter and libreoffice-bin
> is not installed here

media-sound/opensoundmeter is in ::guru.

Those are just the blockers I had, definitely more to it than that!

--
cara

Re: world updates blocked by Qt [ In reply to ]

mackal.cook at gmail

Oct 11, 2023, 7:48 AM

Post #9 of 19 (378 views)

Permalink

On 10/11/23 09:43, Alan McKinnon wrote:
> Hi all,
>
> 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.
>
> That will be an exceptionally long list and today I feel really lazy
> and unwilling :-D
> Has anyone seen what the actual blockers are?
> I spotted okular, I suspect there are more.
>
>
> --
> Alan McKinnon
> alan dot mckinnon at gmail dot com

I just --backtrack=100 and walked away, seemed to have figured something
out for my system and updated normally.

world updates blocked by Qt [ In reply to ]

purslow at ca

Oct 11, 2023, 9:44 AM

Post #10 of 19 (378 views)

Permalink

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

--
========================,,============================================
SUPPORT ___________//___, Philip Webb
ELECTRIC /] [] [] [] [] []| Cities Centre, University of Toronto
TRANSIT `-O----------O---' purslowatcadotinterdotnet

RE: world updates blocked by Qt [ In reply to ]

lperkins at openeye

Oct 11, 2023, 10:13 AM

Post #11 of 19 (378 views)

Permalink

> -----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

Re: world updates blocked by Qt [ In reply to ]

rdalek1967 at gmail

Oct 11, 2023, 10:37 AM

Post #12 of 19 (378 views)

Permalink

Michael Cook wrote:
> On 10/11/23 09:43, Alan McKinnon wrote:
>> Hi all,
>>
>> 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.
>>
>> That will be an exceptionally long list and today I feel really lazy
>> and unwilling :-D
>> Has anyone seen what the actual blockers are?
>> I spotted okular, I suspect there are more.
>>
>>
>> --
>> Alan McKinnon
>> alan dot mckinnon at gmail dot com
>
> I just --backtrack=100 and walked away, seemed to have figured
> something out for my system and updated normally.
>

I have backtrack set to that by default. I did that a long time ago
because sometimes it doesn't work out a solution otherwise. It takes
longer to build the upgrade list sometimes but it figures out the
solution which tends to save time in the long run. You may want to add
that to emerge defaults in make.conf. Oh, don't forget to add -1 to so
that the world file stays clean. ;-)

Dale

:-) :-)

Re: world updates blocked by Qt [ In reply to ]

rdalek1967 at gmail

Oct 11, 2023, 10:41 AM

Post #13 of 19 (378 views)

Permalink

Philip Webb wrote:
> 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
>

I haven't ran into anything like that in ages and I have all KDE and qt
packages as unstable. I wonder why yours does that and mine doesn't?
I'm the one who usually runs into weird problems around here. What did
I miss? LOL

Dale

:-) :-)

P. S. I'm having that problem again with missing replies. I'm still
missing one of Neil's from several hours ago. If someone replies and I
don't, I may not have it yet. :-/

Re: world updates blocked by Qt [ In reply to ]

neil at digimed

Oct 11, 2023, 10:46 AM

Post #14 of 19 (378 views)

Permalink

On Wed, 11 Oct 2023 16:04:08 +0200, Alan McKinnon wrote:

> > On Wed, 11 Oct 2023 15:43:46 +0200, 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.
> >
> > No such issues here, on ~amd64.
> >
>
> Hmmm. When did you last sync? Forgot to mention I am ~amd too

A few hours earliers, but I synced again before replying.

As posted elsewhere, try cranking up --backtrack. I have it set to 20,
which avoids almost all issues without hammering dependency calculation
times.

--
Neil Bothwick

I am Zaphod of Borg. Now, where's the coolest place to be assimilated...

Re: world updates blocked by Qt [ In reply to ]

alan.mckinnon at gmail

Oct 11, 2023, 11:14 AM

Post #15 of 19 (378 views)

Permalink

On Wed, Oct 11, 2023 at 4:49?PM Michael Cook <mackal.cook@gmail.com> wrote:

> On 10/11/23 09:43, Alan McKinnon wrote:
>
> Hi all,
>
> 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.
>
> That will be an exceptionally long list and today I feel really lazy and
> unwilling :-D
> Has anyone seen what the actual blockers are?
> I spotted okular, I suspect there are more.
>
>
> --
> Alan McKinnon
> alan dot mckinnon at gmail dot com
>
> I just --backtrack=100 and walked away, seemed to have figured something
> out for my system and updated normally.
>

This is the one that solved it. Been away too long, forgot all about
backtrack

--
Alan McKinnon
alan dot mckinnon at gmail dot com

Re: world updates blocked by Qt [ In reply to ]

antlists at youngman

Oct 11, 2023, 11:31 PM

Post #16 of 19 (362 views)

Permalink

On 11/10/2023 17:44, Philip Webb wrote:
> 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
>
I haven't had that in a long time. If I get blocks like that (rare)
--backtrack=100 (or whatever it is) unusually unblocks it.

The other thing is, I don't have any explicit perl code on my system,
but on at least one occasion running perl-cleaner --all unbunged a
problem ...

There's a whole bunch of incantations that are rarely needed but need to
be remembered for when they are ...

Cheers,
Wol

Re: world updates blocked by Qt [ In reply to ]

realnc at gmail

Oct 12, 2023, 3:19 AM

Post #17 of 19 (362 views)

Permalink

On 11/10/2023 21:14, Alan McKinnon wrote:
> On Wed, Oct 11, 2023 at 4:49?PM Michael Cook <mackal.cook@gmail.com
> <mailto:mackal.cook@gmail.com>> wrote:
> I just --backtrack=100 and walked away, seemed to have figured
> something out for my system and updated normally.
>
> This is the one that solved it. Been away too long, forgot all about
> backtrack

I've had this in my make.conf for many years now:

EMERGE_DEFAULT_OPTS="--backtrack=200"

Never hit the issue you described (KDE desktop, thus Qt is always a dep.)

Re: Re: world updates blocked by Qt [ In reply to ]

alan.mckinnon at gmail

Oct 12, 2023, 3:56 AM

Post #18 of 19 (362 views)

Permalink

On Thu, Oct 12, 2023 at 12:19?PM Nikos Chantziaras <realnc@gmail.com> wrote:

> On 11/10/2023 21:14, Alan McKinnon wrote:
> > On Wed, Oct 11, 2023 at 4:49?PM Michael Cook <mackal.cook@gmail.com
> > <mailto:mackal.cook@gmail.com>> wrote:
> > I just --backtrack=100 and walked away, seemed to have figured
> > something out for my system and updated normally.
> >
> > This is the one that solved it. Been away too long, forgot all about
> > backtrack
>
> I've had this in my make.conf for many years now:
>
> EMERGE_DEFAULT_OPTS="--backtrack=200"
>
> Never hit the issue you described (KDE desktop, thus Qt is always a dep.)
>
>
> Added similar here now. I see the default is 10, obviously that is not
enough when a big Qt drop hits.

I have something like 30 Qt-5 packages! When did it get so big? I recall
building Qt4 and it was about 6 or so.
Perhaps the devs split it up into many smaller packages.

Alan

--
Alan McKinnon
alan dot mckinnon at gmail dot com

Re: Re: world updates blocked by Qt [ In reply to ]

mackal.cook at gmail

Oct 12, 2023, 7:19 AM

Post #19 of 19 (361 views)

Permalink

On 10/12/23 06:56, Alan McKinnon wrote:
> On Thu, Oct 12, 2023 at 12:19?PM Nikos Chantziaras <realnc@gmail.com>
> wrote:
>
> On 11/10/2023 21:14, Alan McKinnon wrote:
> > On Wed, Oct 11, 2023 at 4:49?PM Michael Cook <mackal.cook@gmail.com
> > <mailto:mackal.cook@gmail.com>> wrote:
> > I just --backtrack=100 and walked away, seemed to have figured
> > something out for my system and updated normally.
> >
> > This is the one that solved it. Been away too long, forgot all
> about
> > backtrack
>
> I've had this in my make.conf for many years now:
>
> EMERGE_DEFAULT_OPTS="--backtrack=200"
>
> Never hit the issue you described (KDE desktop, thus Qt is always
> a dep.)
>
>
> Added similar here now. I see the default is 10, obviously that is not
> enough when a big Qt drop hits.
>
> I have something like 30 Qt-5 packages! When did it get so big? I
> recall building Qt4 and it was about 6 or so.
> Perhaps the devs split it up into many smaller packages.
>
> Alan
>
> --
> Alan McKinnon
> alan dot mckinnon at gmail dot com

I built this computer in 2018, been using KDE for my desktop and it's
always been on ~amd64. I've had to increase backtrack like twice to
resolve some Qt upgrades, not worth upping the default, would not save time.