@kali-team, please could this be packaged up.
@author, If you want to help the packaging process, you can check the documentation here ~ https://www.kali.org/docs/development/public-packaging

Upstream provides build instructions: https://github.com/laurent22/joplin/blob/master/BUILD.md

Arch Linux seems to have an unofficial package: https://aur.archlinux.org/cgit/aur.git/tree/?h=joplin
https://aur.archlinux.org/packages/joplin/
(that example might help to build some initial packaging for Debian, even though we would prefer to rely on node-* packages available in Debian rather than stuff downloaded via npm)

Just wanted to provide an update to this situation:

Recently a bug was discovered in Joplin that would not allow Debian Users to run the program.

tjnull@conops:~/Downloads$ ./Joplin-1.0.179.AppImage
[3061:0227/105900.905299:FATAL:setuid_sandbox_host.cc(157)] The SUID sandbox helper binary was found, but is not configured correctly. Rather than run without sandboxing I'm aborting now. You need to make sure that /tmp/.mount_JoplinThf4iS/chrome-sandbox is owned by root and has mode 4755.
Trace/breakpoint trap

This was due to the appimage sandbox permission that had to be modified in the app image. While working on the issue I had a person in the community by the name of whiskers confirm the issues and the changes to make it work. The changes were able to resolve the bug and got it to run in Kali Linux.

Whiskers was actually able to find a way to repackage the application from source and the permissions be preserved in the program as a deb file. He will be working with the developers later this week to see if they can be able to support the continued package to create the deb File. In case they say no we have the source and can be able to package this for further releases if we need to do so.

I can confirm and verify that the application he compiled and repackage does work properly if we want to use it since the program is FOSS.

Here is a link to download the application: https://github.com/initinfosec/joplin-debfix

Shout out to whiskers for taking the time and effort to look into this!

It seems the creators of Joplin will not be building a deb package at this time. Therefore, whiskers (InitInfosec) has been given approval by the creators to create and update the main Joplin Deb package at this time.

You can find the official support here: https://github.com/initinfosec/joplin-debian

I will continue to work with him if he has any questions or concerns.

Whiskers (initinfosec) has just placed a bug in for this package: https://bugs.kali.org/view.php?id=6194

apologies for the duplicate,, I had started a new issue to request addition of the tool. Please note that the github repo mention above has changed from joplin-debian to joplin-kali.

- [Name] - Joplin

• [Version] - 1.0.193-0kali1
• [Homepage] - https://github.com/initinfosec/joplin-kali
• [Package] - https://github.com/initinfosec/joplin-kali/releases/tag/1.0.193
• [Author] - initinfosec
• [License] - MIT License
• [Description] - Joplin for Desktop, originally developed by Laurent Cozic. This package is an unofficially supported port of the original application from source, maintained by initinfosec, and OK'd by the original author.
• [Dependencies] - Requires: libgtk-3-0, libnotify4, libnss3, libxss1, libxtst6, xdg-utils, libatspi2.0-0, libuuid1, kde-cli-tools | kde-runtime | trash-cli | libglib2.0-bin | gvfs-bin
• [Similar tools] - CherryTree
• [Activity] - Initial commit/stable debian port from official latest stable sources (1.0.193)
• [How to use] - joplin (or launch from App Menu)

Let me know if you need anything further on my end.

Thanks,
~initinfosec / "whiskers"

joplin version 1.0.201-0kali2 is in kali-experimental: only for amd64 for the moment.
It can't be built for armel (nodejs is not available).

joplin version 1.0.201-0kali6 in kali-experimental: on amd64, arm64 and armhf.
The build on i386 fails with segmentation fault.

Thanks for the hard work @sbrun - would be curious to hear what you did/where I went wrong sometime,

Curious if you have logs for the i386 failure? I believe I got it to work successfully once when testing, but I only did it once, and it was for one of the older 1.0.18X releases IIRC

I'm not sure that the i386 failure is related to joplin. I think it's a npm's failure, maybe specific to the Debian package npm (?)
the segmentation fault occurs if I run "npm install" directly in source directory, or if I run "npm install" in the directories ReactiveNativeClient or ElectronClient.
I will try to investigate soon.

Now we have joplin for amd64, arm64, armhf
joplin-cli is available for amd64, arm64, armhf AND i386.

FTR: the "npm install" command seems to fail on i386 when there are many packages to install. I tried to make several "npm install" instead of one command to avoid the failure.