!NhAsaYbbgmzHtXTPQJ:funklause.de

Nix NodeJS

209 Members
59 Servers

Load older messages


SenderMessageTime
15 Dec 2023
@joepie91:pixie.town@joepie91:pixie.townI'm not sure01:59:28
@joepie91:pixie.town@joepie91:pixie.townI would try with a verbose loglevel to see exactly what is trying to do a mkdir02:01:05
@lily:lily.flowersLily Foster
In reply to @joepie91:pixie.town
I would try with a verbose loglevel to see exactly what is trying to do a mkdir
/var/empty/.npm seemingly. i'm trying to figure out where /var/empty is coming from
02:01:32
@lily:lily.flowersLily Foster
npm ERR! syscall mkdir
npm ERR! path /var/empty/.npm
npm ERR! errno -1
02:01:41
@joepie91:pixie.town@joepie91:pixie.townno I mean as in, which process is trying to call mkdir02:01:48
@joepie91:pixie.town@joepie91:pixie.townI don't think it's babel, that's an npm-formatted error02:01:54
@joepie91:pixie.town@joepie91:pixie.townthis would normally imply that it's npm trying to mkdir02:02:08
@joepie91:pixie.town@joepie91:pixie.townbut I don't see why npm would be trying to mkdir $HOME02:02:22
@lily:lily.flowersLily Foster
In reply to @joepie91:pixie.town
but I don't see why npm would be trying to mkdir $HOME
is that even $HOME though?
02:03:57
@joepie91:pixie.town@joepie91:pixie.town that's what avocadoom has just done AIUI 02:04:35
@avocadoom:avocadoom.deavocadoom
In reply to @lily:lily.flowers
is that even $HOME though?
I dont think so, since I set HOME equal to my build dir
02:04:40
@joepie91:pixie.town@joepie91:pixie.townset $HOME to that02:04:38
@joepie91:pixie.town@joepie91:pixie.townhm02:04:45
* @joepie91:pixie.town@joepie91:pixie.town probably doesn't have the energy to debug further tonight tbh02:07:51
* @avocadoom:avocadoom.deavocadoom will go to bed now, but is hopeful that someone maybe has an answer or at least an idea where this error comes from02:09:45
@avocadoom:avocadoom.deavocadoomBut I'm really happy with the help so far, thx ♥️02:10:21
* @avocadoom:avocadoom.deavocadoom * will go to bed now, but is hopeful that someone maybe has an answer or an idea where this error comes from02:10:44
@avocadoom:avocadoom.deavocadoomI guess this is some hugo specific problem with how they handle npm stuff 02:11:23
@lily:lily.flowersLily Foster
In reply to @avocadoom:avocadoom.de
I guess this is some hugo specific problem with how they handle npm stuff
Yeah I'm poking at it now. It works fine when using a buildNpmPackage-based environment, so I'm trying to root out what it's doing differently without it that gets all spooked
02:13:25
@lily:lily.flowersLily Foster i'm pretty sure it's something with npx trying to write to places it shouldn't though 02:17:03
@lily:lily.flowersLily Foster since hugo just does an npx --no-install babel ... internally unconditionally afaict 02:17:30
@lily:lily.flowersLily Fosterwait02:19:40
@lily:lily.flowersLily Foster you are setting export HOME=./ 02:19:46
@lily:lily.flowersLily Fosterthat, uh, won't work02:19:49
@lily:lily.flowersLily Foster you need export HOME="$PWD" or something 02:20:11
@lily:lily.flowersLily Foster(fwiw, since i have to run this without sandbox, i get a completely different error on my system)02:21:10
@lily:lily.flowersLily Foster(as well. btw)02:21:17
@lily:lily.flowersLily Foster * (like different than yours with the same derivation, btw)02:21:30
@lily:lily.flowersLily Foster oh, the /var/empty is the home dir in /etc/passwd for the nixbld users (which I'm using auto-allocate-uids so i don't use) 02:24:30
@lily:lily.flowersLily Foster * oh, the /var/empty is the home dir in /etc/passwd for the nixbld users (which I'm using auto-allocate-uids so i don't have) 02:24:34

Show newer messages


Back to Room ListRoom Version: 6