Re: www/node16 packing failure

From: Juraj Lutter <otis_at_FreeBSD.org>
Date: Fri, 31 Mar 2023 15:58:38 UTC
Hi,

> On 31 Mar 2023, at 17:20, Dima Panov <fluffy@FreeBSD.org> wrote:
> 
> Moin-moin!
> 
> On 31.03.2023 00: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?
> 
> Both files under COREPACK option which enabled by default
> 
> And both looks like temporary generated files in previous releases
> 

I’ve pushed an update. The problem was that my poudriere did not have COREPACK enabled, for whatever reason.

Sorry about that.

—
Juraj Lutter
otis@FreeBSD.org