|
|
image.png (91,408 bytes)
image-2.png (33,467 bytes) |
|
|
Our issue currently is that the build system relies on yarn and yarnpkg is currently broken: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972952 And it can't be fixed because it's no longer buildable in Debian either: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960120 As Kali packagers, we really don't like this node ecosystem which is really brittle and next to impossible to package in a clean way and requires lots of efforts to keep it working... i'm wondering if we should not replace the Kali package with a kaboxer container instead. |
|
|
@rhertzog - @TJ_Null was filling me in about this issue - would it be possible to touch base on this issue? I don't have a solution yet, but trying to replicate it on my end, and wanted to compare notes. If so, what medium would be best to do this? Forum DM? Thanks. |
|
|
@initinfosec Email? buxy@kali.org Though the main issue is outside of my control so I don't really know what you expect from me. We're trying to package joplin out of the appimage binary release instead of building from source. Not clean but I don't really have a better solution. |
|
|
version 1.6.7-0kali3 is now in kali-rolling |
- Anonymous