Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 935028 - app-crypt/gnupg: /usr/lib64/libassuan.so.9: version `LIBASSUAN_2.0' not found after updating dev-libs/libassuan to 3.x series
Summary: app-crypt/gnupg: /usr/lib64/libassuan.so.9: version `LIBASSUAN_2.0' not found...
Status: UNCONFIRMED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Gentoo's Team for Core System packages
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-06-27 18:26 UTC by risto.paavola
Modified: 2024-07-01 03:00 UTC (History)
3 users (show)

See Also:
Package list:
Runtime testing required: ---

Attachments
Emerge --info log (emerge_info.txt,6.56 KB, text/plain)
2024-06-27 18:29 UTC, risto.paavola 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description risto.paavola 2024-06-27 18:26:45 UTC 
When for example "emerge-webrsync" or "emaint -a sync" are executed, they give following:

OpenPGP key import failed: gpg: /usr/lib64/libassuan.so.9: version `LIBASSUAN_2.0' not found (required by gpg)  

Reproducible: Always

Steps to Reproduce:
1.emerge-webrsync
2.Error
Actual Results:  
Error

Expected Results:  
Synced packages
Comment 1 risto.paavola 2024-06-27 18:29:17 UTC 
Created attachment 896533 [details]
Emerge --info log
Comment 2 risto.paavola 2024-06-27 18:30:42 UTC 
Emaint stdout:
# emaint -a sync
>>> Syncing repository 'gentoo' into '/var/db/repos/gentoo'...
 * Using keys from /usr/share/openpgp-keys/gentoo-release.asc
!!! Manifest verification impossible due to keyring problem:
OpenPGP key import failed:
gpg: /usr/lib64/libassuan.so.9: version `LIBASSUAN_2.0' not found (required by gpg)

gpgconf --kill failed:
gpgconf: error running '/usr/bin/gpg-connect-agent': exit status 1
gpgconf: error running '/usr/bin/gpg-connect-agent KILLDIRMNGR': General error
gpgconf: error running '/usr/bin/gpg-connect-agent': exit status 1
gpgconf: error running '/usr/bin/gpg-connect-agent scd killscd': General error
gpgconf: error running '/usr/bin/gpg-connect-agent': exit status 1
gpgconf: error running '/usr/bin/gpg-connect-agent KILLAGENT': General error
gpgconf: error running '/usr/bin/gpg-connect-agent': exit status 1
gpgconf: error running '/usr/bin/gpg-connect-agent KILLKEYBOXD': General error


Action: sync for repo: gentoo, returned code = 1
Comment 3 Eli Schwartz 2024-06-28 04:47:23 UTC 
Probably you have libassuan 3.0.1

$ emerge -p =libassuan-3.0.1

!!! All ebuilds that could satisfy "=libassuan-3.0.1" have been masked.
!!! One of the following masked packages is required to complete your request:
- dev-libs/libassuan-3.0.1::gentoo (masked by: package.mask, ~amd64 keyword)
/var/db/repos/gentoo/profiles/package.mask:
# Sam James <sam@gentoo.org> (2024-06-25)
# The symbol versioning "fix" breaks anything built with 3.0.0.


Rebuild gnupg and you should be fine. Unclear that there's anything which can be done to detect this beyond masking libassuan itself.
Comment 4 risto.paavola 2024-06-28 05:41:58 UTC 
Thank you, rebuilding of gnupg did the job.

I'm using ~amd64 and libassuan-3.0.1 got pulled automatically in some day for some reason.