Arch Linux User Repository

Thanks @qbvt

@TaXules

Currently I don't have much time to maintain nor access to a day-to-day arch computer. I'm happy to handover to you.

I will add you as co-maintainer + disown the package so that you become primary maintainer.

If in your turn you need support in the future please ping me, maybe by then I'll have more time to spend on AUR packages.

@qbvt I have a working PKGBUILD for latest version (at least for scala3). I’d happily maintain this package if you give me the rights.

Hi @qvbt,

I honestly don't remember how I came up with the PKGBUILD, as it was quite a while ago, and the last commit that I did in February of 2020 was a minor fix/version change.

I think it was based on almond's website at the time, but I'm not certain about it.

I might look into it, but since I haven't used almond + jupyter in quite some time (and I don't really remember my scala lessons), I won't really be able to test it.

Hi,

This package fails to install and has several issues:

1. Coursier seems to ignore the COURSIER_CACHE variable (at least on my system). So when running in fakeroot, it tries to use /root/.cache/coursier and fails with exception java.nio.file.AccessDeniedException: /root/.cache/coursier, because it lack root privileges. A solution is to not call coursier in fakeroot, ie. don't call it during package()
2. Coursier now is on the AUR, so it should be made a makedepend instead of fetching the binary in the PKGBUILD,
3. New versions of Almond and Coursier have been released, so version numbers should be updated,
4. For readability in scripts, full versions of the cli arguments should be used instead of the short versions (eg. prefer --isolated to -i),

Regarding issue 1. I have opened a github issue at Coursier's.

Since I needed this package, I tried to fix these issues. I don't think that these happen only on my system, so you might also want to update your PKGBUILD.

EDIT: The kernel doesn't load properly in jupyter-lab though, so there must still be some errors in my PKGBUILD

EDIT2: How did you come up with the coursier bootstrap command ? Was it the recommended way to install things when you did the PKGBUILD ? For reference, if I follow the current instruction guide, I can get a functional install as a user (ie. in ~/.local/share/jupyter/kernels), but not as an admin (ie. in /usr/share/jupyter/kernels). Fixing this would allow us to write a correct PKGBUILD, so if anyone has an idea, I'd gratefully take it. In the meantime I also contacted the almond guys on github.

@clouds56 should be fixed I knew it was a problem but didn't take the time to fix it until now

The kernel failed to start with error

Error: Unable to access jarfile /var/tmp/pamac-build/almond/pkg/almond/usr/share/jupyter/kernels/scala/launcher.jar

the /usr/share/jupyter/kernels/scala/kernel.json shows

{
  "language" : "scala",
  "display_name" : "Scala",
  "argv" : [
    "java",
    "-jar",
    "/var/tmp/pamac-build/almond/pkg/almond/usr/share/jupyter/kernels/scala/launcher.jar",
    "--jupyter-path",
    "/var/tmp/pamac-build/almond/pkg/almond/usr/share/jupyter/kernels/",
    "--connection-file",
    "{connection_file}"
  ]
}

I think it set kernel to wrong path.