Opened 2 years ago
Closed 2 years ago
#66212 closed defect (fixed)
filebrowser: --openssl-legacy-provider is not allowed in NODE_OPTIONS
Reported by: | ryandesign (Ryan Carsten Schmidt) | Owned by: | i0ntempest |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.8.0 |
Keywords: | Cc: | ||
Port: | filebrowser |
Description
/opt/local/bin/node: --openssl-legacy-provider is not allowed in NODE_OPTIONS Command failed: NODE_OPTIONS=--openssl-legacy-provider /opt/local/bin/npm --verbose ci && NODE_OPTIONS=--openssl-legacy-provider /opt/local/bin/npm --verbose run build Exit code: 9
Change History (7)
comment:1 Changed 2 years ago by i0ntempest
comment:2 Changed 2 years ago by i0ntempest
Okay to tackle this I need to extract the version of openssl linked by nodejs. If it’s 3.x, I use that option; if it’s 1.x, don’t use that option.
node -e "console.log(process.versions)" | grep openssl | grep -e "\d.\d*.\d*" -o
can do this. Is there a better/more elegant way?
comment:3 Changed 2 years ago by i0ntempest
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
comment:4 Changed 2 years ago by tobypeterson
comment:5 Changed 2 years ago by tobypeterson
Resolution: | fixed |
---|---|
Status: | closed → reopened |
comment:6 Changed 2 years ago by tobypeterson
Reverted change, breaks PortIndex:
Failed to parse file net/filebrowser/Portfile: couldn't execute "${prefix}/bin/node": no such file or directory
comment:7 Changed 2 years ago by i0ntempest
Resolution: | → fixed |
---|---|
Status: | reopened → closed |
Note: See
TracTickets for help on using
tickets.
Oh my god this thing again??? I don't really know what to do here, it doesn't build with or without that arg.