Bug 600510 – kde-apps/kmail-4.14.11_pre20160211 fails to compile: No rule to make target '/usr/lib64/libgpgme-pthread.so', needed by 'lib/libmessageviewer.so.4 .14.26

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Mark Nowiasz 2016-11-22 18:54:20 UTC]

After updating and emerge @revdep-rebuilding, kmail failes to compile:  No rule to make target '/usr/lib64/libgpgme-pthread.so', needed by 'lib/libmessageviewer.so.4 .14.26

[Comment 1 Mark Nowiasz 2016-11-22 18:55:12 UTC]

Created attachment 454074 [details]
build.log

[Comment 2 Andreas Sturmlechner 2016-11-23 09:05:16 UTC]

Likely caused by gpgme-1.8.0 upgrade. aheinecke mentioned making libgpgme threadsafe in that version, so linking with libgpgme-pthread.so becomes unnecessary.

[Comment 3 Patrick Holthaus 2016-11-24 07:27:38 UTC]

The same compile error happens with kde-apps/kleopatra-16.08.3.
As a workaround, I tried the following (which helps with compiling, but otherwise might be dangerous idk...)

cd /usr/lib64
ln -s libgpgme-pthread.so.11 libgpgme-pthread.so

[Comment 4 Andreas Sturmlechner 2016-11-24 11:23:02 UTC]

In case of kleopatra, it shouldn't be that hard to patch the buildsystem for the newer gpgme.

[Comment 5 Victor Mataré 2016-12-12 15:57:51 UTC]

Are we sure that it isn't app-crypt/gpgme that should be fixed? Because the .so symlinks it creates in /usr/lib* do seem inconsistent. For example:

# ls /usr/lib64/libgpgme.so*
/usr/lib64/libgpgme.so  /usr/lib64/libgpgme.so.11  /usr/lib64/libgpgme.so.11.17.0

But:

# ls /usr/lib64/libgpgme-pthread.so*
/usr/lib64/libgpgme-pthread.so.11  /usr/lib64/libgpgme-pthread.so.11.16.0

Normally I'd expect a package to always create a lib*.so symlink as well.

[Comment 6 Jack 2016-12-14 20:01:41 UTC]

mail-client/balsa-2.5.3 (my own ebuild, new version bug filed) also fails with gpgme-1.8.0 but succeeded with 1.7.1 - it compiles OK, but fails to run with not finding libgpgme-pthread.so.11.  In 1.8.0, I don't see any library or link with pthread in its name.

[Comment 7 Andreas Sturmlechner 2016-12-17 00:08:24 UTC]

(In reply to Victor Mataré from comment #5)
> Are we sure that it isn't app-crypt/gpgme that should be fixed?

Yes we're sure, app-crypt/gpgme-1.8.0 does not install any *pthread*.so at all anymore. What you see comes from another package.

libgpgme.so itself is now threadsafe, so linking to it is enough instead of libgpgme-pthread.so.

For reference, look at how this was ported: https://gitweb.gentoo.org/repo/gentoo.git/tree/mail-client/trojita/files/trojita-0.7-gpgme.patch?id=fcf39a79df5b3b14e887edb2a25c232ac7587708

[Comment 8 Agostino Sarubbo 2017-03-04 15:02:09 UTC]

This seems to affect the stable tree now.


(In reply to Andreas Sturmlechner from comment #7)
> Yes we're sure, app-crypt/gpgme-1.8.0 does not install any *pthread*.so at
> all anymore. What you see comes from another package.

I didn't understand at all but the previously gpgme version installs it:

ago@arcadia ~ $ qfile -v /usr/lib64/libgpgme-pthread.so
app-crypt/gpgme-1.5.5 (/usr/lib64/libgpgme-pthread.so

[Comment 9 Andreas Sturmlechner 2017-03-05 23:33:58 UTC]

As a temporary solution, I have added "app-crypt/gpgme cxx qt5" to plasma profile package.use.stable.mask and fixed kdepimlibs' Find{Q,}Gpgme.cmake files to no longer require gpgme++-pthread.

That should help us over the time until we can implement and stabilise fully side-by-side installable versions of kdepimlibs and fixed reverse-dependencies.

Arches, please stabilise.

[Comment 10 Andreas Sturmlechner 2017-03-05 23:46:41 UTC]

Stefan, CCing you in case you still use kmail-4.4.2016.01 and you might want to test - hope that's OK.

[Comment 11 Stabilization helper bot 2017-03-06 00:02:16 UTC]

An automated check of this bug failed - repoman reported dependency errors (68 lines truncated): 

> dependency.bad kde-apps/kleopatra/kleopatra-4.4.2016.01-r1.ebuild: DEPEND: x86(default/linux/x86/13.0) ['>=kde-apps/libkdepim-4.4.2015:4[aqua=]', '>=kde-apps/libkleo-4.4.2015:4[aqua=]']
> dependency.bad kde-apps/kleopatra/kleopatra-4.4.2016.01-r1.ebuild: RDEPEND: x86(default/linux/x86/13.0) ['>=kde-apps/libkdepim-4.4.2015:4[aqua=]', '>=kde-apps/libkleo-4.4.2015:4[aqua=]']
> dependency.bad kde-apps/kleopatra/kleopatra-4.4.2016.01-r1.ebuild: DEPEND: x86(default/linux/x86/13.0/desktop) ['>=kde-apps/libkdepim-4.4.2015:4[aqua=]', '>=kde-apps/libkleo-4.4.2015:4[aqua=]']
> dependency.bad kde-apps/kleopatra/kleopatra-4.4.2016.01-r1.ebuild: DEPEND: x86(default/linux/x86/13.0) ['>=kde-apps/libkdepim-4.4.2015:4[aqua=]', '>=kde-apps/libkleo-4.4.2015:4[aqua=]']
> dependency.bad kde-apps/kleopatra/kleopatra-4.4.2016.01-r1.ebuild: RDEPEND: x86(default/linux/x86/13.0) ['>=kde-apps/libkdepim-4.4.2015:4[aqua=]', '>=kde-apps/libkleo-4.4.2015:4[aqua=]']
> dependency.bad kde-apps/kleopatra/kleopatra-4.4.2016.01-r1.ebuild: DEPEND: x86(default/linux/x86/13.0/desktop) ['>=kde-apps/libkdepim-4.4.2015:4[aqua=]', '>=kde-apps/libkleo-4.4.2015:4[aqua=]']
> dependency.bad kde-apps/kmail/kmail-4.4.2016.01-r1.ebuild: DEPEND: x86(default/linux/x86/13.0) ['>=kde-apps/libkdepim-4.4.11.1-r1:4[aqua=]', '>=kde-apps/libkleo-4.4.2015:4[aqua=]', '>=kde-apps/libkpgp-4.4.2015:4[aqua=]']
> dependency.bad kde-apps/kmail/kmail-4.4.2016.01-r1.ebuild: RDEPEND: x86(default/linux/x86/13.0) ['>=kde-apps/libkdepim-4.4.11.1-r1:4[aqua=]', '>=kde-apps/libkleo-4.4.2015:4[aqua=]', '>=kde-apps/libkpgp-4.4.2015:4[aqua=]']
> dependency.bad kde-apps/kmail/kmail-4.4.2016.01-r1.ebuild: DEPEND: x86(default/linux/x86/13.0/desktop) ['>=kde-apps/libkdepim-4.4.11.1-r1:4[aqua=]', '>=kde-apps/libkleo-4.4.2015:4[aqua=]', '>=kde-apps/libkpgp-4.4.2015:4[aqua=]']
> dependency.bad kde-apps/kmail/kmail-4.4.2016.01-r1.ebuild: DEPEND: x86(default/linux/x86/13.0) ['>=kde-apps/libkdepim-4.4.11.1-r1:4[aqua=]', '>=kde-apps/libkleo-4.4.2015:4[aqua=]', '>=kde-apps/libkpgp-4.4.2015:4[aqua=]']
> dependency.bad kde-apps/kmail/kmail-4.4.2016.01-r1.ebuild: RDEPEND: x86(default/linux/x86/13.0) ['>=kde-apps/libkdepim-4.4.11.1-r1:4[aqua=]', '>=kde-apps/libkleo-4.4.2015:4[aqua=]', '>=kde-apps/libkpgp-4.4.2015:4[aqua=]']
> dependency.bad kde-apps/kmail/kmail-4.4.2016.01-r1.ebuild: DEPEND: x86(default/linux/x86/13.0/desktop) ['>=kde-apps/libkdepim-4.4.11.1-r1:4[aqua=]', '>=kde-apps/libkleo-4.4.2015:4[aqua=]', '>=kde-apps/libkpgp-4.4.2015:4[aqua=]']

[Comment 12 Stabilization helper bot 2017-03-06 01:01:25 UTC]

An automated check of this bug succeeded - the previous repoman errors are now resolved.

[Comment 13 Guido Winkelmann 2017-03-06 11:44:04 UTC]

I've hit this bug today as well, still with kde-apps/kmail-4.14.11_pre20160211.

On my system at least, gpgme-1.8 does appear to still install libgpgme-pthread* files:

# equery belongs /usr/lib64/libgpgme-pthread.so.11
 * Searching for /usr/lib64/libgpgme-pthread.so.11 ... 
app-crypt/gpgme-1.8.0-r2 (/usr/lib64/libgpgme-pthread.so.11 -> libgpgme-pthread.so.11.13.4)
app-crypt/gpgme-1.8.0-r2 (/usr/lib64/libgpgme-pthread.so.11.13.4)

[Comment 14 Andreas Sturmlechner 2017-03-06 19:09:23 UTC]

(In reply to Guido Winkelmann from comment #13)
> On my system at least, gpgme-1.8 does appear to still install
> libgpgme-pthread* files:
> # equery belongs /usr/lib64/libgpgme-pthread.so.11

These must be preserved libs that are falsely reported by equery to be owned by gpgme-1.8 when they were preserved from the previous version of gpgme.

[Comment 15 Stefan Kiesler 2017-03-08 07:00:44 UTC]

(In reply to Andreas Sturmlechner from comment #10)
> Stefan, CCing you in case you still use kmail-4.4.2016.01 and you might want
> to test - hope that's OK.

What exactly should I test?
I have app-crypt/gpgme-1.8.0-r2 installed with all USE flags disabled.
Then unmasked the 4.14.11 PIM components because I forgot why I masked them. :-D
Kmail2 compiled fine and greeted me with its dreaded import dialog, so I masked it again and recompiled the 4.4.2016.01 components.

So I can confirm that both (stable) branches compile and work fine, if that's of any use for you.
Also learned that it's better to put comments in my package.mask file. :-)

[Comment 16 Andreas Sturmlechner 2017-03-08 09:47:00 UTC]

Thanks, in this case mostly if it builds and links we're fine.

[Comment 17 Guido Winkelmann 2017-03-09 12:07:38 UTC]

(In reply to Andreas Sturmlechner from comment #14)
> (In reply to Guido Winkelmann from comment #13)
> > On my system at least, gpgme-1.8 does appear to still install
> > libgpgme-pthread* files:
> > # equery belongs /usr/lib64/libgpgme-pthread.so.11
> 
> These must be preserved libs that are falsely reported by equery to be owned
> by gpgme-1.8 when they were preserved from the previous version of gpgme.

These files are also listed in /var/db/pkg/app-crypt/gpgme-1.8.0-r2/CONTENTS:

sym /usr/lib64/libgpgme-pthread.so.11 -> libgpgme-pthread.so.11.13.4 1471977087
obj /usr/lib64/libgpgme-pthread.so.11.13.4 994dc06069474ccffc7ceaf7c3c13007 1471977088

Even if they were just left over preserved libs, that doesn't help me much, because emerge @preserved-rebuild does not work for me (because kmail won't build).

I have tried moving those files away and then rebuilding kmail, but that didn't work either.

[Comment 18 Andreas Sturmlechner 2017-03-09 12:09:30 UTC]

Please use the package list of this bug and put it into your package.accept_keywords directory.

[Comment 19 Andreas Sturmlechner 2017-03-09 12:25:20 UTC]

amd64 stable.

[Comment 20 Agostino Sarubbo 2017-03-10 11:00:37 UTC]

x86 stable. Closing.

[Comment 21 Guido Winkelmann 2017-03-10 13:41:38 UTC]

Bug is fixed for me in kde-apps/kmail-4.14.11_pre20160211-r1. Thanks for the fix.