| Git Clone URL: | https://aur.archlinux.org/standardnotes-bin.git (read-only, click to copy) |
|---|---|
| Package Base: | standardnotes-bin |
| Description: | Free, open-source encrypted notes app. |
| Upstream URL: | https://github.com/standardnotes/app |
| Keywords: | electron encrypted-notes encryption journal note-taking notes standard-notes |
| Licenses: | AGPL3 |
| Conflicts: | standardnotes-desktop |
| Provides: | standardnotes-desktop |
| Submitter: | plague-doctor |
| Maintainer: | dataprolet |
| Last Packager: | dataprolet |
| Votes: | 28 |
| Popularity: | 0.53 |
| First Submitted: | 2020-12-07 23:34 (UTC) |
| Last Updated: | 2026-03-30 15:56 (UTC) |
I'm having an issue with the latest version here: 3.183.22-1.
It won't build and I'm getting this error:
Error: ENOENT: no such file or directory, open '/home/mmmotion/.cache/yay/standardnotes-bin/src/squashfs-root/resources/app.asar.unpacked/node_modules/cbor-extract/build/node_gyp_bins/python3'
Anyone else?
@proledatarian: If you're able to get it setup, sure.
@yochananmarqos Got it, thanks. The Github API is just REST, that fairly easy. I'll see what I can make of it. I can keep you updated if you like?
EDIT: Also there is a forum that's just a separate repo which has issues enabled: https://github.com/standardnotes/forum/issues/.
@proledatarian: No, the AppImage is updated along with the Pre-Releases. I only update when there is a Release on GitHub which is currently 3.169.32.
They also mentioned one can use the GitHub API to fetch it in a script as documented here. All that is a little over my head.
@yochananmarqos Thanks for investigating. So the release on the website is indeed the latest and Github is lacking behind.
EDIT: I don't like it, that behavior totally defeats the purpose of enabling notifications for releases of the Github repo. I was wondering why I only get mails about pre-releases, but never for releases. I guess I will also write the devs a mail, because there must be a better way for package maintainers that to blindly package pre-releases without really knowing whether those are actual releases or not.
@proledatarian: Follow up email reply:
If you need to know which one is marked as the latest release, you can also use the desktop app itself for reference. Whenever the desktop app notifies you of a new update, the version marked as the latest there is also the one marked as the latest on our repository.
@@proledatarian: Not much of an answer, but this is the response I received:
Apologies for the confusion! We do not immediately mark each new release as the latest on Github, because if we did, the updates would be much too frequent on the user's end. Similarly, this would mean that you'd have to constantly pull in a new version as we push new changes. However, if you do download the app from our website, it will immediately direct to the latest build that is live with the latest changes on the web app.
@proledatarian: That's a very good question. Upstream issues are disabled, so I sent them an email.
@yochananmarqos Thanks, but why are they releasing other versions on their website?
Here the latest version is .23 and it was .21 yesterday: https://standardnotes.com/download.
@proledatarian: Again, I only update my standardnotes-desktop to Release tags, not Pre-Release tags. I also only flag this package out of date when there is a Release to help you follow them as well. Today, 3.169.20 and 3.169.22 were Releases while 3.169.21 was a Pre-Release.
Pinned Comments