Bug 190790 - [patch] net-mgmt/nrpe fix build with ssl (.rnd file placement)
Summary: [patch] net-mgmt/nrpe fix build with ssl (.rnd file placement)
Status: Closed Overcome By Events
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Many People
Assignee: Niclas Zeising
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-06-08 13:12 UTC by Olli Hauer
Modified: 2016-02-14 20:34 UTC (History)
0 users

See Also:

Attachments
nrpe ssl rnd location patch (948 bytes, patch)
2014-06-08 13:14 UTC, Olli Hauer 		no flags Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Olli Hauer freebsd_committer freebsd_triage 2014-06-08 13:12:24 UTC 
The following error can be found if build with PD.

===========================================================================
====>> Checking for filesystem violations... done
====>> Error: Filesystem touched during build:
root/.rnd extra
===>  Cleaning for nrpe-2.15_3
build of /usr/ports/net-mgmt/nrpe ended at Sun Jun  8 13:21:13 CEST 2014
build time: 00:00:11
!!! build failure encountered !!!

Using env HOME=... in the configure file will change the place and let the port build again.
Comment 1 Olli Hauer freebsd_committer freebsd_triage 2014-06-08 13:14:06 UTC 
Created attachment 143526 [details]
nrpe ssl rnd location patch
Comment 2 Niclas Zeising freebsd_committer freebsd_triage 2016-02-04 20:37:34 UTC 
I can't duplicate this any longer, with any supportet version of FreeBSD and the latest poudriere.  Is this still an issue?

Apologies for taking so long to get to this.
Comment 3 Olli Hauer freebsd_committer freebsd_triage 2016-02-14 20:34:10 UTC 
After removing my local patch it seems the issue was solved by the ports framework or by PD.
Don't know if it is a possible issue for users using tinderbox or any other build system, anyway I will close the PR knowing there was a workaround in case the issue comes up again at a later time.