Could we swap nvm
for nodenv
?
Search Criteria
Package Details: tutanota-desktop 267.250206.0-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/tutanota-desktop.git (read-only, click to copy) |
---|---|
Package Base: | tutanota-desktop |
Description: | The desktop client for Tutanota, the secure e-mail service. |
Upstream URL: | https://tuta.com/secure-email |
Licenses: | GPL-3.0-or-later |
Submitter: | yochananmarqos |
Maintainer: | yochananmarqos (ajgraves) |
Last Packager: | yochananmarqos |
Votes: | 30 |
Popularity: | 0.66 |
First Submitted: | 2020-03-03 17:27 (UTC) |
Last Updated: | 2025-02-10 18:24 (UTC) |
Dependencies (9)
- alsa-lib
- gtk3 (gtk3-no_deadkeys_underlineAUR, gtk3-classicAUR, gtk3-classic-xfceAUR, gtk3-patched-filechooser-icon-viewAUR)
- libsecret
- nss (nss-hgAUR)
- cargo (rustup-gitAUR, rust-nightly-binAUR, rust-gitAUR, rust-beta-binAUR, rustup-stubAUR, rust, rustup) (make)
- emscripten (emscripten-gitAUR) (make)
- git (git-gitAUR, git-glAUR) (make)
- nvmAUR (nvm-gitAUR) (make)
- python (python37AUR, python311AUR, python310AUR) (make)
Required by (0)
Sources (4)
aemonge commented on 2022-03-14 12:49 (UTC)
yochananmarqos commented on 2022-01-25 17:42 (UTC)
@evilrobot: I'd prefer to wait until upstream adds official support.
evilrobot commented on 2022-01-25 15:13 (UTC) (edited on 2022-01-25 15:14 (UTC) by evilrobot)
I was able to get an arm64 build of 3.91.2 based on https://github.com/tutao/tutanota/blob/master/doc/BUILDING.md#building-and-running-your-own-tutanota-desktop-client and a few changes to buildSrc/electron-package-json-template.js (based on https://github.com/tutao/tutanota/pull/3020).
Would you possibly consider updating the package to build from release source, so that we can have aarch64 support please? Havent created a package yet but could give it a go if you think this is better as a separate package.
diff --git a/buildSrc/electron-package-json-template.js b/buildSrc/electron-package-json-template.js
index 8d57ead03..a1f547340 100644
--- a/buildSrc/electron-package-json-template.js
+++ b/buildSrc/electron-package-json-template.js
@@ -81,7 +81,7 @@ export default function generateTemplate({nameSuffix, version, updateUrl, iconPa
"productName": nameSuffix.length > 0
? nameSuffix.slice(1) + " Tutanota Desktop"
: "Tutanota Desktop",
- "artifactName": "${name}-${os}.${ext}",
+ "artifactName": "${name}-${os}-${arch}.${ext}",
"afterSign": notarize ? "buildSrc/notarize.cjs" : undefined,
"protocols": [
{
@@ -125,7 +125,7 @@ export default function generateTemplate({nameSuffix, version, updateUrl, iconPa
"target": [
{
"target": unpacked ? "dir" : "nsis",
- "arch": "x64"
+ "arch": ["x64", "arm64"]
}
]
},
@@ -171,7 +171,7 @@ export default function generateTemplate({nameSuffix, version, updateUrl, iconPa
"target": [
{
"target": unpacked ? "dir" : "AppImage",
- "arch": "x64"
+ "arch": ["x64", "arm64"]
}
]
}
monarc99 commented on 2022-01-22 20:59 (UTC)
increase the memory for node (default is 4096):
export NODE_OPTIONS=--max_old_space_size=8192
set the NODE_OPTIONS env in the shell / or PKGBUILD, before you build the package.
bouche_bag commented on 2022-01-21 22:25 (UTC) (edited on 2022-01-21 22:27 (UTC) by bouche_bag)
FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory 1: 0x560179bd26b1 node::Abort() [node] 2: 0x560179ad8ceb node::FatalError(char const, char const) [node] 3: 0x560179db2782 v8::Utils::ReportOOMFailure(v8::internal::Isolate, char const, bool) [node] 4: 0x560179db29e8 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate, char const, bool) [node] 5: 0x560179f582c6 [node] 6: 0x560179f69bf2 v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [node] 7: 0x560179f6beca v8::internal::Heap::AllocateRawWithLightRetrySlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [node] 8: 0x560179f6bf57 v8::internal::Heap::AllocateRawWithRetryOrFailSlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [node] 9: 0x560179f2fa5d v8::internal::Factory::NewFillerObject(int, bool, v8::internal::AllocationType, v8::internal::AllocationOrigin) [node] 10: 0x56017a280429 v8::internal::Runtime_AllocateInYoungGeneration(int, unsigned long, v8::internal::Isolate) [node] 11: 0x56017a633bf9 [node] [redacted]/.cache/yay/tutanota-desktop/PKGBUILD: line 20: 21936 Aborted (core dumped) node dist -l --custom-desktop-release --unpacked
Getting this build error trying to update 3.91.2-1 from the one below it, anyone know why?
xafr commented on 2021-09-06 17:36 (UTC)
I get this error for a few weeks now. Still stuck with version 3.84.7-1: Build error: ExecError: npm exited with code ERR_ELECTRON_BUILDER_CANNOT_EXECUTE Error output: npm ERR! code ETARGET npm ERR! notarget No matching version found for electron-updater@4.3.5. npm ERR! notarget In most cases you or one of your dependencies are requesting npm ERR! notarget a package version that doesn't exist.
archie63 commented on 2021-07-12 16:50 (UTC)
Build error: ExecError: npm exited with code ERR_ELECTRON_BUILDER_CANNOT_EXECUTE Error output: npm ERR! code ETARGET npm ERR! notarget No matching version found for fs-extra@^9.0.1. npm ERR! notarget In most cases you or one of your dependencies are requesting npm ERR! notarget a package version that doesn't exist.
yochananmarqos commented on 2021-07-06 22:48 (UTC)
@IEPforAUR: I can't reproduce that.
missingSleepDeps commented on 2021-07-06 22:46 (UTC)
"Build error: ExecError: npm exited with code ERR_ELECTRON_BUILDER_CANNOT_EXECUTE"
yochananmarqos commented on 2021-04-14 15:21 (UTC)
@jowlo: It appears you are correct, done.
Pinned Comments
yochananmarqos commented on 2025-02-21 16:35 (UTC)
PSA: This currently fails to build with
emscripten
>=4.0.3. Usetutanota-desktop-bin
for now.