[Bug 217556] New port: security/moloch (help with minor npm problem during staging required)
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Sun Mar 5 04:37:55 UTC 2017
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217556
Bug ID: 217556
Summary: New port: security/moloch (help with minor npm problem
during staging required)
Product: Ports & Packages
Version: Latest
Hardware: Any
OS: Any
Status: New
Severity: Affects Only Me
Priority: ---
Component: Ports Framework
Assignee: portmgr at FreeBSD.org
Reporter: h0rst at nurfuerspam.de
CC: freebsd-ports-bugs at FreeBSD.org
Created attachment 180525
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=180525&action=edit
initial port attempt
I wrote up the initial attempt for a security/moloch port (AOLs large scale
packet capturing, indexing and database system).
The port compiles and works fine over here, however I can't finish it up as an
npm-subpackage involves absolute paths when staging thus preventing a clean
package build. It might be enough to somehow exclude the files from the plist,
but I am not sure how to proceed.
Can someone more experienced have a look at that port, which otherwise appears
to work fine?
Thanks!
Build error:
====> Running Q/A tests (stage-qa)
Error: '/usr/ports/custom/moloch/work/.PLIST.mktmp' is referring to
/usr/ports/custom/moloch/work/stage
Error:
'/usr/ports/custom/moloch/work/stage/usr/local/moloch/viewer/node_modules/fs-ext/build/config.gypi'
is referring to /usr/ports/custom/moloch/work/stage
Error:
'/usr/ports/custom/moloch/work/stage/usr/local/moloch/viewer/node_modules/fs-ext/build/Makefile'
is referring to /usr/ports/custom/moloch/work/stage
Error:
'/usr/ports/custom/moloch/work/stage/usr/local/moloch/viewer/node_modules/png/build/config.gypi'
is referring to /usr/ports/custom/moloch/work/stage
Error:
'/usr/ports/custom/moloch/work/stage/usr/local/moloch/viewer/node_modules/png/build/Makefile'
is referring to /usr/ports/custom/moloch/work/stage
*** Error code 1
Stop.
--
You are receiving this mail because:
You are on the CC list for the bug.
More information about the freebsd-ports-bugs
mailing list