<Nathan-web>Hi. does anyone do node development here? If so, how do you manage your node versions? I was somewhat surprised to find that the latest version available in Guix is 14, which is EOL in 2 months, considering there have been 2 major LTS releases since then.
<pmf>Hey, has anyone tried to build junit version 5 on the guix system?
<pmf>Every time I try the build fails because of an "Invalid Java installation" error. Gradle is trying to download a jdk, but something goes wrong and the files are inaccessible
<pmf>I'm pretty out of my depth and was wondering whether there's anyone who has more java experience than I who could offer a pointer of which way to look
<pmf>Invalid Java installation found at '/home/pmf/.gradle/jdks/OpenJDK8U-jdk_x64_linux_hotspot_8u362b09/jdk8u362-b09' (provisioned toolchain). It will be re-checked in the next build. This might have performance impact if it keeps failing. Run the 'javaToolchains' task for more details.
<pmf> > Provisioned toolchain '/home/pmf/.gradle/jdks/OpenJDK8U-jdk_x64_linux_hotspot_8u362b09/jdk8u362-b09' could not be probed: A problem occurred starting process 'command '/home/pmf/.gradle/jdks/OpenJDK8U-jdk_x64_linux_hotspot_8u362b09/jdk8u362-b09/bin/java''
<lechner>sorry folks, i am the pre-dawn shift, and haven't used Java or Node in years
<apteryx>anyone using an HP all-in-one printer (inkjet + scanner) ?
<apteryx>I've tried adding hplip-minimal as an cups-service extension, but it doesn't seem to have helped
<lechner>apteryx / i would probably forget about hplip and instead use modern printer auto-configuration, plus libsane
<iyzsong>a12l: autoreconf is in 'autoconf', but if you have guix, you can run 'guix shell -D guix --pure' to get a build environment for guix (as documented in the guix manual, 22.1 Building from Git).
<a12l>iyzsong: Thanks for the reference! But I still get the same error after entering the guix shell :(
<a12l>Hmm, guix downloads autoconf when I run guix shell autoconf
<a12l>Doesn't seem that autoconf is included in guix's build deps :-/
<abrenon>a12l: the documentation doesn't tell you to open a shell with autoconf, it suggests to open a shell with "everything needed to develop on guix" ("-D guix")
<abrenon>and that should work (at least it worked for me yesterday : ) )
<a12l>abrenon: Okey, but why do I still get the missing autoconf error after entering the shell?
<a12l>I must do something wrong, but I don't see what
<abrenon>(the fact that you have seen it downloaded upon entering the shell doesn't mean it's "not installed" — that doesn't really make sense in guix, a lot of stuff is on the disk, and "installed" or not depends on the environment)
<abrenon>from what I see, your second error is not an autoconf error, it's "autopoint" which wasn't found
<abrenon>now I would too expect it to be part of autoconf, but assuming guix isn't broken, it is certainly not the case, and knowing that you haven't entered a dev environment but only one where autoconf was present, I must assume it is from another packaged mentioned as a dev dependency for guix
<abrenon>indeed, I don't have any autopoint either when I enter a shell for autoconf, but then again that's not what was suggested on the page iyzsong linked to
<iyzsong>a12l: um, you can run "guix shell -D guix -- ./bootstrap" in the guix checkout directory, if still error with autopoint, then you can try "guix pull", open a new terminal (to ensure that "which guix" return just pulled current guix), finally the "guix shell ..." again..
<abrenon>and then, within the spawned shell, you run whatever commands you wish
<abrenon>I have no explanation as to why the last command would fail in the last paste you uploaded
<abrenon>if line 7 is indeed run within the shell spawned by l. 5
<abrenon>question to other guixers: could it be the case that previous attempts in a bad environment have resulted in damaged scripts (for instance is an occurrence of autoreconf normally replaced then by its /gnu/store/… path which could have been left unchanged by running in an environment without autoreconf ?)
<a12l>abrenon: With the help of iyzsong we concluded that `--pure` doesn't work for me. If I simply omit that when creating the shell everything works as intended :)
<abrenon>that's weird ?! could it be a bug in guix package for nix ?
<abrenon>I've retried the exact same steps by copy-pasting each line from your paste and it works here
<abrenon>so I guess it means it uses the autoconf from your user environment but it shouldn't need to, the dev environment must contain it
<abrenon>could you open the shell with --pure again and tell us there's no autoreconf / autopoint / etc. in $GUIX_ENVIRONMENT/bin ?
<abrenon>also, what does $PATH contain when you are within your --pure shell ?
<abrenon>since the --pure option manages to get rid of everything outside what guix prepares, and since your .bashrc doesn't let what's supposed to be added to the environment into the environment, you end up with a trimmed environment, without the dev tools for guix that the "guix shell -D guix … --pure" was supposed to add
<abrenon>so it worked "by accident", so to speak, when you removed the --pure because you were using whatever was in your (personal) environment at that time, not what guix prepared and controlled; you may very well have skipped the guix shell at all in that case
<a12l>nckx: Not sure what you mean with "implicit dotfiles", but these are the ones in my $HOME. `.bashrc` and `.bash_profile` is auto generated by Nix; and `.profile` is managed by Nix, but pretty much only contain what I've configured.
<nckx>I just meant that you were implying the . when you gave the names above.
<abrenon>but I don't see why a bashrc would source a profile; it's not supposed to, and the system-generated one makes sure this isn't happening l.10 of etc-bashrc
<abrenon>I don't see any such problem in your .bashrc either but there must be one somewhere
<a12l>abrenon: bashrc doesn't source a profile? Or have I missed something?
<abrenon>yeah, it's not supposed to and as far as I can see in your files it doesn't; but since you proved that it was getting sourced, it must happen somehow, and that is the source of your problem with guix shell because somewhere in your profile (more precisely, in the gistfile1.txt which gets sourced in your $HOME/.profile) PATH gets erased (instead of just providing a baseline as it is meant to) and that
<a12l>abrenon: But the $HOME/.guix-home/* paths are present in my $PATH (from the second half of my .profile), as is the paths form L8 in gistfile1.txt?
<abrenon>but the path added by guix shell is something which points to within the temporary $GUIX_ENVIRONMENT (which was missing from your PATH when you echoed it), the .guix-home/* .guix-profile/* and such are related to your "permanent" guix install — and so make sense to be defined in your profile by contrast to your bashrc —, not to the transient environment that guix shell opens (which doesn't point
<a12l>sneek later tell abrenon I now think I understand what you mean. When you write `guix shell --pure [...]` you expect only specific Guix's paths to be available in `$PATH`, but because `$PATH` obviously contain Nix paths there's probably somewhere in the global `/etc/bashrc` or `~/.bashrc` there a script get sourced that sets/add the Nix paths to `$PATH`.
<sneek>abrenon, a12l says: I now think I understand what you mean. When you write `guix shell --pure [...]` you expect only specific Guix's paths to be available in `$PATH`, but because `$PATH` obviously contain Nix paths there's probably somewhere in the global `/etc/bashrc` or `~/.bashrc` there a script get sourced that sets/add the Nix paths to `$PATH`.
<abrenon>more than that, you expect only the packages explicitly requested to be present (not even the packages which just "happen to have been installed", by guix or not)
<abrenon>if you open a --pure shell without any argument, you end up in an empty environment where you can't do anything at all, you can't call ls, nor bash nor anything
<frill>Hey Guixers - does anyone know if there's a downloadable version of Luis Felipe's new graphics for 1.4.0? Can't see it anywhere, and I greatly enjoyed Luis's graphic for 1.3.0, and would like to similarly enjoy his new one with the cosmic frogs :)
<apteryx>that was without the user in the "lp" group though, so this may help when I can try again
<f1refly>when I have a machines.scm with one machine (my desktop computer) and that one goes offline, will guix figure out that it can only build packages locally? My desktop is suspended most of the time or otherwise unreachable from my laptop
<lechner>apteryx / i don't need 'lp' locally. i'm in (list "wheel" "users" "netdev" "audio" "video" "cdrom")
<apteryx>interesting. Did you use the printer configuration tool of GNOME?