Bug 1223869 - non-existing 'cert.h' file on ppc64
Summary: non-existing 'cert.h' file on ppc64
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: nss
Version: 23
Hardware: ppc64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Elio Maldonado Batiz
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Keywords:
Depends On:
Blocks: PPCTracker
TreeView+ depends on / blocked
 
Reported: 2015-05-21 15:06 UTC by Vratislav Podzimek
Modified: 2015-08-13 14:52 UTC (History)
5 users (show)

(edit)
Clone Of:
(edit)
Last Closed: 2015-08-13 14:52:38 UTC


Attachments (Terms of Use)
SRPM that failed to build (508.30 KB, application/x-rpm)
2015-05-21 15:06 UTC, Vratislav Podzimek
no flags Details

Description Vratislav Podzimek 2015-05-21 15:06:17 UTC
Created attachment 1028255 [details]
SRPM that failed to build

Description of problem:
An attempt to build libblockdev which uses libvolume_key which uses nss on PPC64 failed with the following error:

In file included from crypto.c:24:0:
/usr/include/volume_key/libvolume_key.h:21:18: fatal error: cert.h: No such file or directory

URL of the scratch build:
http://ppc.koji.fedoraproject.org/koji/taskinfo?taskID=2503033

Comment 1 Dan Horák 2015-05-21 16:17:36 UTC
It might be a transient issue with rawhide on ppc koji. It is not fully up-to-date yet with primary koji and a scratch build in f22 succeeds - http://ppc.koji.fedoraproject.org/koji/taskinfo?taskID=2503726

Comment 2 Jan Kurik 2015-07-15 14:07:32 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 23 development cycle.
Changing version to '23'.

(As we did not run this process for some time, it could affect also pre-Fedora 23 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 23 End Of Life. Thank you.)

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora23

Comment 3 Rafael Fonseca 2015-08-13 12:44:53 UTC
nss seems to build successfully. Can we close this bug?


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