Re: [gentoo-user] Re: Qt-4.8.7 bug

[Frank Steinmetzger]

On Tue, May 23, 2017 at 09:59:20PM -0700, Ian Zimmerman wrote:
> On 2017-05-23 23:16, Frank Steinmetzger wrote:
>
> > KDE doesn’t find my beloved terminus font anymore, both on my PC and
> > my laptop.  It does not show up in any font selection dialog. The same
> > goes for GTK applications such as gimp (GTK2) and firefox (GTK3). No
> > Terminus anywhere.
> >
> > Does that ring a bell with anyone?
>
> Yes:
>
> https://bugs.gentoo.org/show_bug.cgi?id=618918
>
> I seem to scent a faint Poettering type hormone in the air around
> freetype :-(

Ah, thank you very very much. I’ll be offline for the next few days and it’s
nice to know a solution. Coulda thunk myself to look at bgo.

-- 
Gruß | Greetings | Qapla’
Please do not share anything from, with or about me on any social network.

The boss is a human just like everyone else, he just doesn’t know.


signature.asc
Description: Digital signature

[gentoo-user] Re: Qt-4.8.7 bug

[Ian Zimmerman]

On 2017-05-23 23:16, Frank Steinmetzger wrote:

> KDE doesn’t find my beloved terminus font anymore, both on my PC and
> my laptop.  It does not show up in any font selection dialog. The same
> goes for GTK applications such as gimp (GTK2) and firefox (GTK3). No
> Terminus anywhere.
> 
> Does that ring a bell with anyone?

Yes:

https://bugs.gentoo.org/show_bug.cgi?id=618918

I seem to scent a faint Poettering type hormone in the air around
freetype :-(

-- 
Please *no* private Cc: on mailing lists and newsgroups
Personal signed mail: please _encrypt_ and sign
Don't clear-text sign:
http://primate.net/~itz/blog/the-problem-with-gpg-signatures.html

[gentoo-user] Re: Qt-4.8.7 bug

[Jörg Schaible]

Hello Kai,

Kai Krakow wrote:

> Am Mon, 22 May 2017 19:33:55 +0200
> schrieb Jörg Schaible :
> 
>> Peter Humphrey wrote:

[snip]

>> > 
>> > I can only suggest you read bug report 618922 if you haven't
>> > already, including following its reference to bug 595618. It makes
>> > sense to me.
>> 
>> It does not for me. My packages were already compiled with gcc-5.4.0.
>> Those Buzilla issues only talk about (plasma/qt) packages compiled
>> with previous gcc-4.x which are supposed to be incompatible. All of
>> the plasma/qt related packages that have been recompiled, because
>> they were built upon libQtCore.so.4 were already recompiled with
>> gcc5. I've checked my logs.
> 
> Is the problem maybe order of building packages?
> 
> From your description I see one edge case: Plasma could have been
> compiled with gcc-5 but linked to qt still built with gcc-4. Then, qt
> was rebuilt after this and is compiled by gcc-5 now.
> 
> Without reading the bug report I would guess that is what the bug is
> about: Linking plasma against gcc-4 built qt binaries... Even when you
> rebuild qt with gcc-5 after this, you'd need to relink plasma.
> 
> From your logs, you should see the order in which those packages were
> rebuilt and linked.
> 
> revdep-rebuild is not always able to perfectly order packages right for
> emerge, and emerge in turn has no problem with wrong ordering because
> it is rebuilding packages and the dependency constraints are already
> fulfilled (read: runtime and build deps are already there). Portage
> does not consider rebuilds as a hard dependency/precondition for
> rebuilding other packages...
> 
> As far as I understood, "--changed-deps" should fix this and also
> rebuild packages depending on the rebuilt packages _after_ they've been
> rebuilt.
> 
> The "--empty" option would have a similar effect, tho rebuild many more
> packages.
> 
> You could've tried if "revdep-rebuild ... -- --changed-deps" would've
> done anything better. I would be interested...

Too late now for this, but your assumption can be true. The rebuild for the 
gcc5 switch did not work smoothly because emerge failed to build all 515 
packages reported by revdep-rebuild in correct order. Especially the Kontact 
suite was affected, because emerge tried to build kdepim-common-libs before 
some of the dependent packages (happened to me on two different machines). A 
second run rebuilding only the failed stuff succeeded in the end, but that 
might have lead to the linker situation you've described above. I wonder, 
what else might still be affected :-/

Cheers,
Jörg

[gentoo-user] Re: Qt-4.8.7 bug

[Kai Krakow]

Am Mon, 22 May 2017 19:33:55 +0200
schrieb Jörg Schaible :

> Peter Humphrey wrote:
> 
> > On Monday 22 May 2017 09:49:01 Jörg Schaible wrote:  
> >> Hi Peter,
> >> 
> >> Peter Humphrey wrote:
> >> 
> >> [snip]
> >>   
>  [...]  
> >> 
> >> well, this does not seem to be the complete truth. When I switched
> >> to gcc 5.x I did a revdep-rebuild for anything that was compiled
> >> against libstdc++.so.6 just like the according news entry was
> >> recommending. And I am quite sure that those Qt plugins were part
> >> of my 515 recompiled packages.
> >> 
> >> Nevertheless, my KDE 4 apps were broken after the update to Qt
> >> 4.8.7. Rebuilding anything that was using libQtCore.so.4 solved
> >> it, but I fail to see how this is related to the gcc update two
> >> weeks ago.  
> > 
> > I can only suggest you read bug report 618922 if you haven't
> > already, including following its reference to bug 595618. It makes
> > sense to me.  
> 
> It does not for me. My packages were already compiled with gcc-5.4.0.
> Those Buzilla issues only talk about (plasma/qt) packages compiled
> with previous gcc-4.x which are supposed to be incompatible. All of
> the plasma/qt related packages that have been recompiled, because
> they were built upon libQtCore.so.4 were already recompiled with
> gcc5. I've checked my logs.

Is the problem maybe order of building packages?

From your description I see one edge case: Plasma could have been
compiled with gcc-5 but linked to qt still built with gcc-4. Then, qt
was rebuilt after this and is compiled by gcc-5 now.

Without reading the bug report I would guess that is what the bug is
about: Linking plasma against gcc-4 built qt binaries... Even when you
rebuild qt with gcc-5 after this, you'd need to relink plasma.

From your logs, you should see the order in which those packages were
rebuilt and linked.

revdep-rebuild is not always able to perfectly order packages right for
emerge, and emerge in turn has no problem with wrong ordering because
it is rebuilding packages and the dependency constraints are already
fulfilled (read: runtime and build deps are already there). Portage
does not consider rebuilds as a hard dependency/precondition for
rebuilding other packages...

As far as I understood, "--changed-deps" should fix this and also
rebuild packages depending on the rebuilt packages _after_ they've been
rebuilt.

The "--empty" option would have a similar effect, tho rebuild many more
packages.

You could've tried if "revdep-rebuild ... -- --changed-deps" would've
done anything better. I would be interested...


-- 
Regards,
Kai

Replies to list-only preferred.

[gentoo-user] Re: Qt-4.8.7 bug

[Ian Zimmerman]

On 2017-05-20 16:36, Mick wrote:

> It seems revdep-rebuild'ing against library='libQtCore.so.4' also
> rebuilds the newly installed Qt packages.  This is why there so many
> packages to rebuild.

For me it was just 20 packages, I have no KDE.  That was much fewer that
Kai's suggestion would have done - for some reason that wanted to
recompile almost everything, if not literally everything (I didn't check).

-- 
Please *no* private Cc: on mailing lists and newsgroups
Personal signed mail: please _encrypt_ and sign
Don't clear-text sign:
http://primate.net/~itz/blog/the-problem-with-gpg-signatures.html

[gentoo-user] Re: Qt-4.8.7 bug

[Kai Krakow]

Am Sun, 21 May 2017 09:38:31 +0100
schrieb Peter Humphrey :

> On Saturday 20 May 2017 18:39:07 Kai Krakow wrote:
> > Am Sat, 20 May 2017 16:36:08 +0100
> > 
> > schrieb Mick :  
> > > On Saturday 20 May 2017 10:48:52 Mick wrote:  
>  [...]  
>  [...]  
> > >  [...]
> > >  [...]
> > >  [...]
> > >  [...]
> > >  [...]
> > >  [...]
> > >
>  [...]  
> > >  
> > >  [...]
> > >
>  [...]  
>  [...]  
> > > 
> > > It seems revdep-rebuild'ing against library='libQtCore.so.4' also
> > > rebuilds the newly installed Qt packages.  This is why there so
> > > many packages to rebuild.  
> > 
> > That's why I suggested using "--changed-deps": It doesn't rebuild
> > packages that provide the library itself and have already been built
> > after the library provider...
> > 
> > OTOH, it doesn't check binary dependence, just what is written into
> > the ebuilds itself. But it should work most of the time.
> > 
> > A combination of two emerge invocations may work, too:
> > 
> > # emerge -DNua world --changed-deps
> > # emerge -1a @preserved-rebuild --changed-deps
> > 
> > This also worked well for me when I did the gcc upgrade.
> > 
> > But I think the need to use changed-deps to rebuild dependers
> > should be considered a bug and be reported. Portage has support for
> > sub-slot dependencies to describe such binary breakage during
> > upgrades and automatically rebuild the dependers.  
> 
> Have you seen https://bugs.gentoo.org/show_bug.cgi?id=595618 ? It
> says that "Qt plugins compiled with gcc-4 are incompatible with
>  can be expected to anticipate that. On the other hand, some kind of
> notice could be issued, and bug 618922 is pursuing that. (That's the
> one I started this thread with.)

I was thinking about how portage could support the user here:

Portage could record which compiler in which version was used building
the package. It already records tons of information in /var/db/pkg.
There's CFLAGS but that doesn't really help here.

What I did after "emerge -DNua world --changed-deps" while upgrading
GCC at the same time, was finding all packages in /var/db/pkg that had
mtime older than the CFLAGS file of the GCC build. While changed-deps
seemed to capture most of what needed to be rebuilt, I just wanted to be
sure the rest of the system was rebuilt, too.

Of course there are ebuilds that just create data files or scripts
which could've been excluded from rebuilding, and packages that are
built with different compilers than gcc... That's why I thought it
would be nice if portage recorded the exact compiler version used.


-- 
Regards,
Kai

Replies to list-only preferred.

Re: [gentoo-user] Re: Qt-4.8.7 bug

[Peter Humphrey]

On Saturday 20 May 2017 18:39:07 Kai Krakow wrote:
> Am Sat, 20 May 2017 16:36:08 +0100
> 
> schrieb Mick :
> > On Saturday 20 May 2017 10:48:52 Mick wrote:
> > > On Saturday 20 May 2017 03:19:20 Peter Humphrey wrote:
> > > > On Saturday 20 May 2017 00:26:58 Kai Krakow wrote:
> >  [...]
> >  [...]
> >  [...]
> >  [...]
> >  [...]
> >  [...]
> >  
> > > > After all that, KMail now works as it did before.
> >  
> >  [...]
> >  
> > > > Mick might like to try that, perhaps. I assume the effect will be
> > > > the same.
> > > 
> > > Thanks Peter.  First PC is going through it.  91 packages!
> > 
> > It seems revdep-rebuild'ing against library='libQtCore.so.4' also
> > rebuilds the newly installed Qt packages.  This is why there so many
> > packages to rebuild.
> 
> That's why I suggested using "--changed-deps": It doesn't rebuild
> packages that provide the library itself and have already been built
> after the library provider...
> 
> OTOH, it doesn't check binary dependence, just what is written into the
> ebuilds itself. But it should work most of the time.
> 
> A combination of two emerge invocations may work, too:
> 
> # emerge -DNua world --changed-deps
> # emerge -1a @preserved-rebuild --changed-deps
> 
> This also worked well for me when I did the gcc upgrade.
> 
> But I think the need to use changed-deps to rebuild dependers should be
> considered a bug and be reported. Portage has support for sub-slot
> dependencies to describe such binary breakage during upgrades and
> automatically rebuild the dependers.

Have you seen https://bugs.gentoo.org/show_bug.cgi?id=595618 ? It says that 
"Qt plugins compiled with gcc-4 are incompatible with 

[gentoo-user] Re: Qt-4.8.7 bug

[Kai Krakow]

Am Sat, 20 May 2017 16:36:08 +0100
schrieb Mick :

> On Saturday 20 May 2017 10:48:52 Mick wrote:
> > On Saturday 20 May 2017 03:19:20 Peter Humphrey wrote:  
> > > On Saturday 20 May 2017 00:26:58 Kai Krakow wrote:  
>  [...]  
>  [...]  
>  [...]  
>  [...]  
>  [...]  
>  [...]  
> > > 
> > > After all that, KMail now works as it did before.
> > >   
>  [...]  
> > > 
> > > Mick might like to try that, perhaps. I assume the effect will be
> > > the same.  
> > 
> > Thanks Peter.  First PC is going through it.  91 packages!  
> 
> It seems revdep-rebuild'ing against library='libQtCore.so.4' also
> rebuilds the newly installed Qt packages.  This is why there so many
> packages to rebuild.

That's why I suggested using "--changed-deps": It doesn't rebuild
packages that provide the library itself and have already been built
after the library provider...

OTOH, it doesn't check binary dependence, just what is written into the
ebuilds itself. But it should work most of the time.

A combination of two emerge invocations may work, too:

# emerge -DNua world --changed-deps
# emerge -1a @preserved-rebuild --changed-deps

This also worked well for me when I did the gcc upgrade.

But I think the need to use changed-deps to rebuild dependers should be
considered a bug and be reported. Portage has support for sub-slot
dependencies to describe such binary breakage during upgrades and
automatically rebuild the dependers.


-- 
Regards,
Kai

Replies to list-only preferred.


pgpIVPoQ1wk25.pgp
Description: Digitale Signatur von OpenPGP

Re: [gentoo-user] Re: Qt-4.8.7 bug

[Peter Humphrey]

On Saturday 20 May 2017 16:36:08 Mick wrote:

> It seems revdep-rebuild'ing against library='libQtCore.so.4' also rebuilds
> the newly installed Qt packages.  This is why there so many packages to
> rebuild.

I hadn't notice that, but now you mention it I had 14 dev-qt packages, 41 
kde-apps and 3 kde-plasma among my 71.

All's well that ends well.

-- 
Regards
Peter

Re: [gentoo-user] Re: Qt-4.8.7 bug

[Mick]

On Saturday 20 May 2017 10:48:52 Mick wrote:
> On Saturday 20 May 2017 03:19:20 Peter Humphrey wrote:
> > On Saturday 20 May 2017 00:26:58 Kai Krakow wrote:
> > > Am Fri, 19 May 2017 22:50:06 +0100
> > > 
> > > schrieb Peter Humphrey :
> > > > On Friday 19 May 2017 15:15:24 Mick wrote:
> > > > > On Friday 19 May 2017 13:43:24 Peter Humphrey wrote:
> > > > > > Hello list,
> > > > > > 
> > > > > > Today's update broke KMail. 15 dev-qt packages were upgraded from
> > > > > > 4.8.6 to 4.8.7, and when I logged out, restarted xdm and logged
> > > > > > in again, KMail's folder list showed all the folders in red, and
> > > > > > the other two panes were blank. Akonadiconsole showed the LAN
> > > > > > Mail agent offline, broken.
> > > > > > 
> > > > > > In case anyone else falls over this one, I've raised this bug;
> > > > > > it's been confirmed by one other user so far:
> > > > > > 
> > > > > > https://bugs.gentoo.org/show_bug.cgi?id=618922
> > > > > > 
> > > > > > Has anyone found a fix for this?
> > > > > 
> > > > > I haven't run an update yet, but thank you for bringing this to our
> > > > > attention. I'll stay put on 4.8.6-r2, until the bug is resolved.
> > > > 
> > > > Apparently, a revdep-rebuild fixes it: revdep-rebuild --
> > > > library='libQtCore.so.4'
> > > > 
> > > > 71 packages! See you in the morning - I don't intend to sit and wait
> > > > while the likes of qtwebkit and libreoffice compiling.
> > 
> > After all that, KMail now works as it did before.
> > 
> > > You could try "emerge -DNua world --changed-deps" to fix such problems.
> > > It should work even when already upgraded.
> > 
> > Mick might like to try that, perhaps. I assume the effect will be the
> > same.
> 
> Thanks Peter.  First PC is going through it.  91 packages!

It seems revdep-rebuild'ing against library='libQtCore.so.4' also rebuilds the 
newly installed Qt packages.  This is why there so many packages to rebuild.

-- 
Regards,
Mick

signature.asc
Description: This is a digitally signed message part.

Re: [gentoo-user] Re: Qt-4.8.7 bug

[Mick]

On Saturday 20 May 2017 03:19:20 Peter Humphrey wrote:
> On Saturday 20 May 2017 00:26:58 Kai Krakow wrote:
> > Am Fri, 19 May 2017 22:50:06 +0100
> > 
> > schrieb Peter Humphrey :
> > > On Friday 19 May 2017 15:15:24 Mick wrote:
> > > > On Friday 19 May 2017 13:43:24 Peter Humphrey wrote:
> > > > > Hello list,
> > > > > 
> > > > > Today's update broke KMail. 15 dev-qt packages were upgraded from
> > > > > 4.8.6 to 4.8.7, and when I logged out, restarted xdm and logged
> > > > > in again, KMail's folder list showed all the folders in red, and
> > > > > the other two panes were blank. Akonadiconsole showed the LAN
> > > > > Mail agent offline, broken.
> > > > > 
> > > > > In case anyone else falls over this one, I've raised this bug;
> > > > > it's been confirmed by one other user so far:
> > > > > 
> > > > > https://bugs.gentoo.org/show_bug.cgi?id=618922
> > > > > 
> > > > > Has anyone found a fix for this?
> > > > 
> > > > I haven't run an update yet, but thank you for bringing this to our
> > > > attention. I'll stay put on 4.8.6-r2, until the bug is resolved.
> > > 
> > > Apparently, a revdep-rebuild fixes it: revdep-rebuild --
> > > library='libQtCore.so.4'
> > > 
> > > 71 packages! See you in the morning - I don't intend to sit and wait
> > > while the likes of qtwebkit and libreoffice compiling.
> 
> After all that, KMail now works as it did before.
> 
> > You could try "emerge -DNua world --changed-deps" to fix such problems.
> > It should work even when already upgraded.
> 
> Mick might like to try that, perhaps. I assume the effect will be the same.

Thanks Peter.  First PC is going through it.  91 packages!

-- 
Regards,
Mick

signature.asc
Description: This is a digitally signed message part.

Re: [gentoo-user] Re: Qt-4.8.7 bug

[Peter Humphrey]

On Saturday 20 May 2017 00:26:58 Kai Krakow wrote:
> Am Fri, 19 May 2017 22:50:06 +0100
> 
> schrieb Peter Humphrey :
> > On Friday 19 May 2017 15:15:24 Mick wrote:
> > > On Friday 19 May 2017 13:43:24 Peter Humphrey wrote:
> > > > Hello list,
> > > > 
> > > > Today's update broke KMail. 15 dev-qt packages were upgraded from
> > > > 4.8.6 to 4.8.7, and when I logged out, restarted xdm and logged
> > > > in again, KMail's folder list showed all the folders in red, and
> > > > the other two panes were blank. Akonadiconsole showed the LAN
> > > > Mail agent offline, broken.
> > > > 
> > > > In case anyone else falls over this one, I've raised this bug;
> > > > it's been confirmed by one other user so far:
> > > > 
> > > > https://bugs.gentoo.org/show_bug.cgi?id=618922
> > > > 
> > > > Has anyone found a fix for this?
> > > 
> > > I haven't run an update yet, but thank you for bringing this to our
> > > attention. I'll stay put on 4.8.6-r2, until the bug is resolved.
> > 
> > Apparently, a revdep-rebuild fixes it: revdep-rebuild --
> > library='libQtCore.so.4'
> > 
> > 71 packages! See you in the morning - I don't intend to sit and wait
> > while the likes of qtwebkit and libreoffice compiling.

After all that, KMail now works as it did before.

> You could try "emerge -DNua world --changed-deps" to fix such problems.
> It should work even when already upgraded.

Mick might like to try that, perhaps. I assume the effect will be the same.

-- 
Regards
Peter

[gentoo-user] Re: Qt-4.8.7 bug

[Kai Krakow]

Am Fri, 19 May 2017 22:50:06 +0100
schrieb Peter Humphrey :

> On Friday 19 May 2017 15:15:24 Mick wrote:
> > On Friday 19 May 2017 13:43:24 Peter Humphrey wrote:  
> > > Hello list,
> > > 
> > > Today's update broke KMail. 15 dev-qt packages were upgraded from
> > > 4.8.6 to 4.8.7, and when I logged out, restarted xdm and logged
> > > in again, KMail's folder list showed all the folders in red, and
> > > the other two panes were blank. Akonadiconsole showed the LAN
> > > Mail agent offline, broken.
> > > 
> > > In case anyone else falls over this one, I've raised this bug;
> > > it's been confirmed by one other user so far:
> > > 
> > > https://bugs.gentoo.org/show_bug.cgi?id=618922
> > > 
> > > Has anyone found a fix for this?  
> > 
> > I haven't run an update yet, but thank you for bringing this to our
> > attention. I'll stay put on 4.8.6-r2, until the bug is resolved.  
> 
> Apparently, a revdep-rebuild fixes it: revdep-rebuild --
> library='libQtCore.so.4'
> 
> 71 packages! See you in the morning - I don't intend to sit and wait
> while the likes of qtwebkit and libreoffice compiling.

You could try "emerge -DNua world --changed-deps" to fix such problems.
It should work even when already upgraded.

-- 
Regards,
Kai

Replies to list-only preferred.