Bug 1384127 - unbound-1.5.10-1.fc26 FTBFS: testdata/autotrust_rollalgo.rpl failed
Summary: unbound-1.5.10-1.fc26 FTBFS: testdata/autotrust_rollalgo.rpl failed
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: unbound
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Paul Wouters
QA Contact: Fedora Extras Quality Assurance
URL: http://apps.fedoraproject.org/koschei...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-12 15:29 UTC by Jitka Plesnikova
Modified: 2017-04-26 19:38 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-04-26 19:38:36 UTC
Type: Bug


Attachments (Terms of Use)

Description Jitka Plesnikova 2016-10-12 15:29:07 UTC
Description of problem:
Package unbound fails to build from source in Fedora Rawhide.

testdata/autotrust_revtp_use.rpl OK
testdata/autotrust_rollalgo.rpl failed
make: *** [Makefile:295: test] Error 1
RPM build errors:
error: Bad exit status from /var/tmp/rpm-tmp.FJogpV (%check)
    Bad exit status from /var/tmp/rpm-tmp.FJogpV (%check)
Child return code was: 1
EXCEPTION: [Error()]

Dependency changes in buildroot since last successful build
 	openssl-devel 	1:1.0.2j-1.fc26 	> 	1:1.1.0b-1.fc26
	openssl-libs 	1:1.0.2j-1.fc26 	> 	1:1.1.0b-1.fc26
	filesystem 	3.2-37.fc24 	> 	3.2-38.fc26
	compat-openssl10 		> 	1:1.0.2j-2.fc26
	gnutls 	3.5.4-1.fc26 	> 	3.5.5-1.fc26
	kernel-headers 	4.9.0-0.rc0.git4.1.... 	> 	4.9.0-0.rc0.git5.2....


Additional info:
This package is tracked by Koschei. See:
http://apps.fedoraproject.org/koschei/package/unbound

Comment 1 Rich Mattes 2016-12-21 13:30:51 UTC
There's a thread on the upstream mailing list that points towards openssl-1.1.0 being the cause of this issue[1].

The release notes for unbound-1.6.0[2] include a note about fixing openssl-1.1.0 DSA compatibility:

> - Add DSA support for OpenSSL 1.1.0

It may be that updating to 1.6.0 will solve this issue.

[1] https://unbound.net/pipermail/unbound-users/2016-October/004506.html
[2] https://unbound.net/pipermail/unbound-users/2016-December/004587.html


Note You need to log in before you can comment on or make changes to this bug.