Summary: | app-crypt/gpgme-1.13.0 should depend on >=dev-libs/libassuan-2.5.3 to satisfy pkgconfig requirement | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Aaron Bauman (RETIRED) <bman> |
Component: | Current packages | Assignee: | Crypto team [DISABLED] <crypto+disabled> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | floppym |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | 695700 | ||
Bug Blocks: | |||
Attachments: | build log |
Description
Aaron Bauman (RETIRED)
![]() build logs: https://transfer.sh/O0CqZ/meson-0.51.1-build.log Please attach any logs to this bug report. A link to an external pastebin site is not sufficient. Created attachment 587878 [details]
build log
build log
Does /usr/lib64/pkgconfig/gpgme.pc exist on this system? If so, please attach it. Also, what do you get when you run this manually? /usr/bin/aarch64-unknown-linux-gnu-pkg-config --modversion gpgme I have the same error on sparc, and I bet the culprit is this: chroot ~ # /usr/bin/sparc-unknown-linux-gnu-pkg-config --modversion gpgme Package libassuan was not found in the pkg-config search path. Perhaps you should add the directory containing `libassuan.pc' to the PKG_CONFIG_PATH environment variable Package 'libassuan', required by 'gpgme', not found So the pkgconfig file installed by gpgme requires libassuan. Older versions of libassuan do not provide a pkgconfig file. This issue has nothing to do with meson, so I am un-blocking the stable request. (In reply to Mike Gilbert from comment #6) > So the pkgconfig file installed by gpgme requires libassuan. > > Older versions of libassuan do not provide a pkgconfig file. > > This issue has nothing to do with meson, so I am un-blocking the stable > request. Meson is testing against this though. How does the remove the blocker? Should the meson tests be fixed... and as a distro the dependencies fixed? Meson has many optional test deps. I'm not going to pull them all in. Users will not be affected by this test failure. The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=5230fb90fe11f235d209450233d34191018f269e commit 5230fb90fe11f235d209450233d34191018f269e Author: Tim Harder <radhermit@gentoo.org> AuthorDate: 2019-09-26 22:18:59 +0000 Commit: Tim Harder <radhermit@gentoo.org> CommitDate: 2019-09-26 22:20:27 +0000 app-crypt/gpgme: version bump to 1.13.1 Bump libassuan dep to 2.5.3 for pkgconfig usage. Closes: https://bugs.gentoo.org/692738 Signed-off-by: Tim Harder <radhermit@gentoo.org> app-crypt/gpgme/Manifest | 1 + app-crypt/gpgme/gpgme-1.13.1.ebuild | 117 ++++++++++++++++++++++++++++++++++++ 2 files changed, 118 insertions(+) The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=2d03f8f2e0b5920130340ee30f388b78847434c1 commit 2d03f8f2e0b5920130340ee30f388b78847434c1 Author: Mike Gilbert <floppym@gentoo.org> AuthorDate: 2019-09-26 18:09:03 +0000 Commit: Mike Gilbert <floppym@gentoo.org> CommitDate: 2019-09-27 00:49:39 +0000 app-crypt/gpgme: depend on >=dev-libs/libassuan-2.5.3 This is necessary to avoid a pkg-config dependency error. Bug: https://bugs.gentoo.org/692738 Package-Manager: Portage-2.3.75_p7, Repoman-2.3.17_p49 Signed-off-by: Mike Gilbert <floppym@gentoo.org> app-crypt/gpgme/gpgme-1.13.0-r1.ebuild | 117 +++++++++++++++++++++++++++++++++ 1 file changed, 117 insertions(+) |