Bug 15460

Summary:	gpgme 0.4.0 failed due to "too old libgcrypt"
Product:	Gentoo Linux	Reporter:	Yannick Koehler (RETIRED) <ykoehler>
Component:	New packages	Assignee:	J Robert Ray <jrray>
Status:	RESOLVED INVALID
Severity:	normal	CC:	jap1
Priority:	High
Version:	unspecified
Hardware:	x86
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---

Description Yannick Koehler (RETIRED) gentoo-dev

2003-02-10 18:17:35 UTC

gpgme 0.4.0 depends on libgcrypt >= 1.8.0

/usr/bin/gpgsm --homedir . --import ./cert_g10code_test1.der
gpgsm: Fatal: libgcrypt is too old (need 1.1.8, have 1.1.3)
make[3]: *** [pubring.kbx] Error 2
make[3]: *** Waiting for unfinished jobs....
make[3]: Leaving directory
`/var/tmp/portage/gpgme-0.4.0/work/gpgme-0.4.0/tests/gpgsm'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/var/tmp/portage/gpgme-0.4.0/work/gpgme-0.4.0/tests'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/var/tmp/portage/gpgme-0.4.0/work/gpgme-0.4.0'
make: *** [all] Error 2

!!! ERROR: app-crypt/gpgme-0.4.0 failed.
!!! Function src_compile, Line 40, Exitcode 2
!!! (no error message)


Reproducible: Always
Steps to Reproduce:

Comment 1 J Robert Ray 2003-02-12 12:33:13 UTC

There isn't a good way to express the dependency issues involved here.

What is happening to you is gpgme detected the presense of gpgsm installed on your box, and when testing gpgsm, gpgsm discovers that the version of libgcrypt you have installed is too old.

First things first, gpgsm comes from the newpg package, and the newpg ebuild specifies a dependency of >=dev-libs/libgcrypt-1.1.8.

So, you shouldn't have a situation where you have gpgsm installed but not a new enough version of libgcrypt.  You box must be in a unique position over the course of development of these packages, and this situation shouldn't occur to a normal user.

Anyway, gpgme does not depend on gpgsm (but will use it apparently for something), and gpgme doesn't depend on libgcrypt at all, so I am reluctant to add a dependency entry for it.

Please remerge newpg and see if that resolves this issue for you.

Comment 2 Jacob Perkins 2003-02-28 10:30:55 UTC

Just wanted to add the gpgsm is a supported engine/backend for gpgme, just as gnupg is. So, gpgme should have USE flags to enable the gpgsm/newpg dependency.  I would suggest having 'crypt' pull in newpg.

Comment 3 Yannick Koehler (RETIRED) gentoo-dev

2003-04-09 08:47:08 UTC

What happened is that newpg was installed without the >=libgcrypt1.1.8 probably at my first installation of that non-official ebuild (at that time) and I didn't had it re-installed once you committed it to cvs.

So totally related to my install only, closing.