bun-pkg-why-is-node-running-2.3.0
checks.x86_64-linux.ironstar-eventcatalog
· build #46
· raw
patchPhase
1patching script interpreter paths in /nix/store/akcap3a3f5qbjfp0gd08spblp4z4qs0i-bun-pkg-why-is-node-running-2.3.0/share/bun-packages2/nix/store/akcap3a3f5qbjfp0gd08spblp4z4qs0i-bun-pkg-why-is-node-running-2.3.0/share/bun-packages/why-is-node-running@2.3.0/cli.js: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/97gj07wnwmd4r7wi904ma381yz7w5szs-bun-with-fake-node/bin/node"cacheEntryPhase
3info: Creating entry for `why-is-node-running@2.3.0`...45debug: Link out path: `/nix/store/akcap3a3f5qbjfp0gd08spblp4z4qs0i-bun-pkg-why-is-node-running-2.3.0/share/bun-cache/why-is-node-running@2.3.0@@@1`.67debug: Link parent dir: `/nix/store/akcap3a3f5qbjfp0gd08spblp4z4qs0i-bun-pkg-why-is-node-running-2.3.0/share/bun-cache`.89debug: Created parent directory.1011info: Successfully created cache entry symlink for `why-is-node-running@2.3.0`.12