Package Details: standardnotes-desktop 3.194.0-1

Git Clone URL: https://aur.archlinux.org/standardnotes-desktop.git (read-only, click to copy)
Package Base: standardnotes-desktop
Description: An end-to-end encrypted notes app for digitalists and professionals.
Upstream URL: https://standardnotes.com
Keywords: notes
Licenses: GPL-3.0-or-later
Submitter: FillFeile
Maintainer: yochananmarqos
Last Packager: yochananmarqos
Votes: 47
Popularity: 0.000000
First Submitted: 2017-06-04 13:58 (UTC)
Last Updated: 2024-04-24 22:28 (UTC)

Pinned Comments

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 .. 10 Next › Last »

lsf commented on 2021-05-31 19:04 (UTC)

I'm currently unable to get this to build on aarch64 anymore.

I'll keep trying, though – and if anyone has any ideas how to get this resolved, I'm all ears!

lsf commented on 2021-02-28 15:24 (UTC)

Oh dear, what have I gotten myself into ;)

But I totally understand you @FillFeile – building and packaging NodeJS/Electron based packages is (imho) really a terrible experience, and it's even more complicated with this package than with many others (I'm currently unable to build the -git version of it anymore, for example… hope this will improve before the next release is made).

Anyway, I'll try to keep maintaining it a bit – but I can't make any promises and might not spot any issues, as I'm not using it at the moment myself.

FillFeile commented on 2021-02-28 15:10 (UTC) (edited on 2021-02-28 15:11 (UTC) by FillFeile)

Hi all, Hi @randomguy343,

I just decided to disown this package as I'm currently not able to properly maintain it anymore. At the moment I do not find the time to cope with the frequent build system changes on upstream which have been challenging for me to keep up with as I'm not very experienced with the NodeJS and Electron build/package frameworks.

Thank you all for the feedback over the last years which have been a great opportunity for me to learn how to maintain a package. I hope someone (maybe @lsf) will pick this one up and keep it alive.

Cheers, FillFeile

<deleted-account> commented on 2021-02-28 11:58 (UTC)

Thanks, works fine so far but needs yarn as an dependency. I rarely use Standard Notes myself, but I'll report any issues nonetheless.

lsf commented on 2021-02-27 13:16 (UTC)

@randomguy343

I have a seemingly working PKGBUILD over at https://gitlab.com/ohfp/pinebookpro-things/-/tree/master/standardnotes-desktop

You could give it a try, if you wish – it's only barely tested, though; I'm not using standardnotes myself at the moment.

<deleted-account> commented on 2021-02-27 11:59 (UTC)

Is this package still actively maintained and will be updated soon or what's the current status?

PrzemekS commented on 2020-12-01 08:31 (UTC) (edited on 2020-12-01 08:32 (UTC) by PrzemekS)

Hello, recently I noticed top bar is not working. Cannot minimize, close etc. In terminal I see:

extServer: Server started at http://127.0.0.1:45653/
09:25:29.933 › Checking for update
09:25:29.961 › Error: Error: ENOENT: no such file or directory, open '/opt/standardnotes-desktop/app/dev-app-update.yml'
updateManager: [Error: ENOENT: no such file or directory, open '/opt/standardnotes-desktop/app/dev-app-update.yml'] {
  errno: -2,
  code: 'ENOENT',
  syscall: 'open',
  path: '/opt/standardnotes-desktop/app/dev-app-update.yml'
} Cannot check for updates: Error: ENOENT: no such file or directory, open '/opt/standardnotes-desktop/app/dev-app-update.yml'
updateManager: Exception caught while checking for autoupdates: [Error: ENOENT: no such file or directory, open '/opt/standardnotes-desktop/app/dev-app-update.yml'] {
  errno: -2,
  code: 'ENOENT',
  syscall: 'open',
  path: '/opt/standardnotes-desktop/app/dev-app-update.yml'
}
09:25:30.530 › Checking for update
09:25:30.531 › Error: Error: ENOENT: no such file or directory, open '/opt/standardnotes-desktop/app/dev-app-update.yml'
updateManager: [Error: ENOENT: no such file or directory, open '/opt/standardnotes-desktop/app/dev-app-update.yml'] {
  errno: -2,
  code: 'ENOENT',
  syscall: 'open',
  path: '/opt/standardnotes-desktop/app/dev-app-update.yml'
} Cannot check for updates: Error: ENOENT: no such file or directory, open '/opt/standardnotes-desktop/app/dev-app-update.yml'
updateManager: Exception caught while checking for autoupdates: [Error: ENOENT: no such file or directory, open '/opt/standardnotes-desktop/app/dev-app-update.yml'] {
  errno: -2,
  code: 'ENOENT',
  syscall: 'open',
  path: '/opt/standardnotes-desktop/app/dev-app-update.yml'
}

Regards, Przemek

jackyzy823 commented on 2020-11-21 15:30 (UTC)

Here's my working version which tested under electron 10. just for your reference.

diff --git a/PKGBUILD b/PKGBUILD
index a20e6fc..82b1f49 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -1,15 +1,15 @@
 # Maintainer: Daniel Haß <aur@hass.onl>
 pkgname=standardnotes-desktop
 _pkgname=desktop
-pkgver=3.4.10
-pkgrel=2
+pkgver=3.5.6
+pkgrel=1
 pkgdesc="A standard notes app with an un-standard focus on longevity, portability, and privacy."
 arch=('x86_64')
 url="https://standardnotes.org/"
 license=('GPL3')
 conflicts=('sn-bin')
 depends=('electron')
-makedepends=('npm' 'node-gyp' 'git' 'jq')
+makedepends=('npm' 'node-gyp' 'git' 'jq' 'python2')
 source=("git://github.com/standardnotes/desktop.git"
         "git://github.com/sn-extensions/extensions-manager.git"
         "git://github.com/sn-extensions/batch-manager.git"
@@ -30,8 +30,11 @@ prepare() {

 build() {
   cd $srcdir/$_pkgname/
+  # see https://github.com/standardnotes/desktop/blob/develop/.env.js.sample
+  cp .env.js.sample .env.js
   # use temporary npm cache - https://wiki.archlinux.org/index.php/Node.js_package_guidelines
   npm install --cache "${srcdir}/npm-cache"
+  npm install --prefix ./web --cache "${srcdir}/npm-cache"
   npm run bundle
   ./node_modules/.bin/electron-builder --linux --x64 --dir $dist
 }

Note: 1. python2 is required to an old-version node-gyp to build node-sass which can't found a ABI-matched prebuilt binary from it's github releases because of nodejs ABI bumping to 88 .

  1. .env.js is required to pass the webpack build.

FillFeile commented on 2020-10-30 14:09 (UTC)

I recognized the comments and will dry to address the issues and feedback as soon as possible.

lsf commented on 2020-10-30 09:37 (UTC)

If the patching/workaround is simple enough (as in this case with a one-line-fix), I'd find that more attractive – but that's probably because for my specific case (a separate repo), maintaining different electron versions as well is just way more of a hassle.

So yeah, both solutions should be fine, I guess ^^