Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 934771 - app-crypt/pinentry-1.2.1-r7 fails to build: fails to find libassuan with dev-libs/libassuan-3
Summary: app-crypt/pinentry-1.2.1-r7 fails to build: fails to find libassuan with dev-...
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal
Assignee: Gentoo's Team for Core System packages
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-06-23 13:16 UTC by Carlos Konstanski
Modified: 2024-06-25 00:23 UTC (History)
1 user (show)

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

Attachments
build.log (build.log,8.60 KB, text/x-log)
2024-06-23 13:17 UTC, Carlos Konstanski 		Details
emerge --info (emerge.info,11.49 KB, text/plain)
2024-06-23 13:18 UTC, Carlos Konstanski 		Details
config.log (config.log,79.25 KB, text/x-log)
2024-06-23 22:30 UTC, Carlos Konstanski 		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 Carlos Konstanski 2024-06-23 13:16:10 UTC 
Configure fails with an error resulting from a failure to find libassuan:

configure:
***
*** You need libassuan to build this program.
*** This library is for example available at
***   ftp://ftp.gnupg.org/gcrypt/libassuan/
*** (at least version 2.1.0 (API 2) is required).

But libassuan is installed:

# equery list libassuan
 * Searching for libassuan ...
[IP-] [  ] dev-libs/libassuan-3.0.0:0/3.0

Reproducible: Always
Comment 1 Carlos Konstanski 2024-06-23 13:17:44 UTC 
Created attachment 896288 [details]
build.log
Comment 2 Carlos Konstanski 2024-06-23 13:18:41 UTC 
Created attachment 896289 [details]
emerge --info
Comment 3 Greg Kubaryk 2024-06-23 21:24:28 UTC 
/var/tmp/portage/app-crypt/pinentry-1.2.1-r7/work/pinentry-1.2.1/config.log would potentially be useful too
Comment 4 Carlos Konstanski 2024-06-23 22:30:49 UTC 
Created attachment 896312 [details]
config.log
Comment 5 Carlos Konstanski 2024-06-23 22:33:06 UTC 
Uploaded. I see this which looks relevant:

configure:8562: checking LIBASSUAN API version                                                                         
configure:8569: result: does not match.  want=2 got=3.

I'm using the stable version of libassuan which is 3.
Comment 6 Sam James archtester Gentoo Infrastructure gentoo-dev Security 2024-06-24 00:12:13 UTC 
(In reply to Carlos Konstanski from comment #5)

libassuan-3 isn't stable yet, fwiw.
Comment 8 Carlos Konstanski 2024-06-24 02:26:57 UTC 
I misinterpreted the equery output. Indeed I have libassuan keyworded. I must have done that in the past to satisfy some dependency. I just removed the keyword and emerge seems happy with that. pinentry built successfully with libassuan-2.5.7.
Comment 9 Larry the Git Cow gentoo-dev 2024-06-24 03:02:19 UTC 
The bug has been closed via the following commit(s):

https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=7b07caa9d1459f9cba33cb8e7fceddf23a36583d

commit 7b07caa9d1459f9cba33cb8e7fceddf23a36583d
Author:     Sam James <sam@gentoo.org>
AuthorDate: 2024-06-24 03:00:35 +0000
Commit:     Sam James <sam@gentoo.org>
CommitDate: 2024-06-24 03:00:35 +0000

    app-crypt/pinentry: allow <1.3 to build w/ >=libassuan-3
    
    Delete the bundled macro so it uses the system copy which knows libassuan-3
    is compatible with libassuan-2 API-wise.
    
    Closes: https://bugs.gentoo.org/934771
    Signed-off-by: Sam James <sam@gentoo.org>

 .../files/pinentry-1.2.1-libassuan-3.patch         | 46 ++++++++++++++++++++++
 app-crypt/pinentry/pinentry-1.2.1-r7.ebuild        |  3 ++
 app-crypt/pinentry/pinentry-1.2.1-r8.ebuild        |  3 ++
 3 files changed, 52 insertions(+)