Bug 210947

Summary: security/gnutls install error
Product: Ports & Packages Reporter: Marco Beishuizen <mbeis>
Component: Individual Port(s)Assignee: Tijl Coosemans <tijl>
Status: Closed FIXED    
Severity: Affects Only Me Keywords: needs-patch, needs-qa
Priority: --- Flags: bugzilla: maintainer-feedback? (tijl)
koobs: merge-quarterly?
Version: Latest   
Hardware: amd64   
OS: Any   
Attachments:
Description Flags
security/gnutls install config.log none

Description Marco Beishuizen 2016-07-09 18:41:23 UTC 
Upgrading the security/gnutls port to 3.4.14 results in the following error:

===>   Registering installation for gnutls-3.4.14
pkg-static: Unable to access file /usr/ports/security/gnutls/work/stage/usr/local/bin/tpmtool: No such file or directory
*** Error code 74

Stop.
make[2]: stopped in /usr/ports/security/gnutls
*** Error code 1

Stop.
make[1]: stopped in /usr/ports/security/gnutls
*** Error code 1

Stop.
make: stopped in /usr/ports/security/gnutls
** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade20160709-478-13myn9n env UPGRADE_TOOL=portupgrade UPGRADE_PORT=gnutls-3.4.13 UPGRADE_PORT_VER=3.4.13 make reinstall
--->  Restoring the old version
Installing gnutls-3.4.13...
Extracting gnutls-3.4.13: 100%
** Fix the installation problem and try again.

Uname -a:
FreeBSD yokozuna.lan 10.3-STABLE FreeBSD 10.3-STABLE #1 r297561: Mon Apr  4 23:08:56 CEST 2016     root@yokozuna.lan:/usr/obj/usr/src/sys/MAX  amd64
Comment 1 Tijl Coosemans freebsd_committer freebsd_triage 2016-07-10 08:41:06 UTC 
Can you add /usr/ports/security/gnutls/work/gnutls-3.4.14/config.log as attachment to this bug?
Comment 2 Marco Beishuizen 2016-07-10 11:20:24 UTC 
Created attachment 172312 [details]
security/gnutls install config.log

Sure, hereby config.log attached.
Comment 3 Tijl Coosemans freebsd_committer freebsd_triage 2016-07-10 12:16:15 UTC 
The log contains this:
warning: libcrypto.so.8, needed by /usr/local/lib/libtspi.so, not found

So something must have changed in your OpenSSL (libcrypto) installation.  Maybe you recently removed it or updated it?  Try rebuilding security/trousers (libtspi).  That should either restore libcrypto or make libtspi use your current version of libcrypto.
Comment 4 Marco Beishuizen 2016-07-10 12:40:32 UTC 
Yes, problem solved. I recently removed the OpenSSL port to only use the one in base. Didn't see this one because normally the error of the missing libcrypto appears in the xterm output.

Is there a way of seeing which ports are still linked to the removed OpenSSL port?

Thanks for all the help.

Regards,
Marco
Comment 5 Tijl Coosemans freebsd_committer freebsd_triage 2016-07-10 13:36:45 UTC 
pkg shlib libcrypto.so.8