Date: Fri, 31 Mar 2023 19:45:16 +0900 From: Hiroki Tagato <tagattie@FreeBSD.org> To: Juraj Lutter <otis@FreeBSD.org>, jonc@chen.org.nz Cc: freebsd-ports@freebsd.org Subject: Re: www/node16 packing failure Message-ID: <b504dacf-79ed-24d6-d664-444e4ed98a94@FreeBSD.org> In-Reply-To: <FA6FD5B1-B85B-496A-B7E7-87E72720244F@FreeBSD.org> References: <9a5bc75f74917e65ae161eb30ce46a98@chen.org.nz> <FA6FD5B1-B85B-496A-B7E7-87E72720244F@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, On 2023/03/31 6:29, Juraj Lutter wrote: > Hi, > >> On 30 Mar 2023, at 23:27, jonc@chen.org.nz wrote: >> >> Hi, >> >> I'm trying to build www/node16 after the latest update to 16.20.0, and I'm getting the following failure during the "package" phase: >> >> ===> Building package for node16-16.20.0 >> pkg-static: Unable to access file /construction/xports/www/node16/work/stage/usr/local/lib/node_modules/corepack/dist/vcc.js:No such file or directory >> pkg-static: Unable to access file /construction/xports/www/node16/work/stage/usr/local/lib/node_modules/corepack/dist/vendors-_yarn_berry_cache_proxy-agent-npm- >> 5_0_0-41772f4b01-9_zip_node_modules_proxy-agent_index_js.js:No such file or directory >> *** Error code 1 >> >> Stop. >> make: stopped in /xports/www/node16 > > Which options do you have set and unset? I have exactly the same error. My build environment is poudriere (r131amd64 jail) with default option setting. Removing those two files from pkg-plist appears to solve the problem. Thanks, Hiroki
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?b504dacf-79ed-24d6-d664-444e4ed98a94>