tech-pkg archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: upcoming freeze for 2017Q3, now in careful mode

Am Sun, 10 Sep 2017 00:10:25 +0200
schrieb Thomas Klausner <>: 

> I suspect that some packages find and want to use libgcrypt if it's
> already installed, but build fine without it. If necessary, the

Yeah, my issues revolved around a wrong version from the host system
being picked up. Pkgsrc's insistence on not giving access to the
libgcrypt in pkgsrc while the system one is still found leads to both
versions being pulled in (via deps) and conflict ensues.

> Others look just plain wrong, for example graphics/glu's source has no
> reference to gcrypt.h.

While individual error is possible, I remember had the wrong gcrypt
entering in the builds via dependencies ... so some dependency's
buildlink needs fixing?

> Please check them again more closely.

I'll see what time allows ... definitely, _something_ is missing some
gcrypt in the dependency tree. Of course, if nobody else has those
issues, the patches can rot for a bit.

Alrighty then,


Attachment: smime.p7s
Description: S/MIME cryptographic signature

Home | Main Index | Thread Index | Old Index