@bjo I think it's the same error as below, namely Sencha CMD does only work correctly with Java 8 or earlier. If you have Java 8 as default runtime it should build. I don't know what would be the appropriate way to fix this, help is sure welcome.
Search Criteria
Package Details: hamsket-git r1133.433cadb-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/hamsket-git.git (read-only, click to copy) |
---|---|
Package Base: | hamsket-git |
Description: | Free and Open Source messaging and emailing app that combines common web applications into one. |
Upstream URL: | https://github.com/TheGoddessInari/hamsket |
Licenses: | GPL3 |
Conflicts: | hamsket, hamsket-bin, rambox, rambox-bin, rambox-os, rambox-os-git, ramboxpro-bin |
Provides: | hamsket |
Replaces: | rambox-os-git |
Submitter: | bserckx |
Maintainer: | None |
Last Packager: | bserckx |
Votes: | 4 |
Popularity: | 0.000000 |
First Submitted: | 2019-08-02 10:24 (UTC) |
Last Updated: | 2019-11-04 16:23 (UTC) |
Dependencies (7)
- electron (electron-binAUR)
- desktop-file-utils (desktop-file-utils-gitAUR) (make)
- git (git-gitAUR, git-glAUR) (make)
- java-runtime (jre10AUR, jre12AUR, jdk10AUR, jdk10-openj9-binAUR, jdk7AUR, jre7AUR, amazon-corretto-16AUR, jdk8-graalvm-binAUR, jdk16-graalvm-binAUR, jdk16-adoptopenjdkAUR, jdk8-armAUR, liberica-jre-11-binAUR, jdk11-j9-binAUR, jre11-jbr-xdgAUR, jre16-openjdkAUR, jre14-openjdkAUR, jre15AUR, jre14AUR, jre13AUR, jre16AUR, jre18-openjdkAUR, amazon-corretto-19-binAUR, jdk19-graalvm-binAUR, liberica-jre-11-full-binAUR, jdk19-graalvm-ee-binAUR, jdk13-openjdk-binAUR, liberica-jre-8-full-binAUR, jdk11-graalvm-binAUR, jre-openj9AUR, jdk11-graalvm-ee-binAUR, jre12-openjdkAUR, jdk11-dragonwell-standard-binAUR, jdk11-jetbrains-binAUR, jdk20-graalvm-binAUR, jdk17-graalvm-binAUR, jdk8-graalvm-ee-binAUR, zulu-15-binAUR, jdk20-openj9-binAUR, zulu-13-binAUR, jdk8-dragonwell-extended-binAUR, jdk8-dragonwell-standard-binAUR, jdk11-dragonwell-extended-binAUR, jdk17-dragonwell-standard-binAUR, jre11AUR, jdk8-j9-binAUR, jdk7-j9-binAUR, jdk7r1-j9-binAUR, jdk8-dragonwell-extendedAUR, jre13-openjdkAUR, jre15-openjdkAUR, jdk21-graalvm-binAUR, jre17-jetbrainsAUR, jdk8-openj9-binAUR, jre-ltsAUR, microsoft-openjdk-11-binAUR, microsoft-openjdk-17-binAUR, microsoft-openjdk-21-binAUR, liberica-nik-24-full-binAUR, jre21-jetbrains-gitAUR, jdk21-jetbrains-gitAUR, zulu-17-binAUR, zulu-11-binAUR, zulu-8-binAUR, mandrel-binAUR, mandrel24-binAUR, liberica-jdk-17-full-binAUR, liberica-jdk-11-lite-binAUR, liberica-jdk-11-full-binAUR, liberica-jdk-11-binAUR, jdk17-graalvm-ee-binAUR, jdk21-graalvm-ee-binAUR, jdk22-graalvm-ee-binAUR, jdk20-graalvm-ee-binAUR, jdk22-graalvm-binAUR, jre19-openjdkAUR, jdk17-jetbrains-binAUR, zulu-jdk-fx-binAUR, jre21-jetbrainsAUR, jdk17-zulu-prime-binAUR, zing-21-binAUR, zing-8-binAUR, jdk23-graalvm-ee-binAUR, jre17AUR, java-openjdk-binAUR, jre21-zulu-binAUR, amazon-corretto-17AUR, amazon-corretto-21-binAUR, jre17-zulu-binAUR, jdk21-temurinAUR, amazon-corretto-8AUR, amazon-corretto-11AUR, jdk11-temurinAUR, liberica-jdk-full-binAUR, liberica-jdk-21-full-binAUR, liberica-jdk-8-full-binAUR, jdk17-temurinAUR, jdk8-temurinAUR, zulu-21-binAUR, jdk-temurinAUR, jre8AUR, jdk8AUR, zulu-17-fx-binAUR, jdk8-perfAUR, zulu-jre-fx-binAUR, zulu-fx-binAUR, zulu8-fx-binAUR, zulu11-fx-binAUR, zulu17-fx-binAUR, zulu21-fx-binAUR, jdk-openj9-binAUR, jdk11-openj9-binAUR, jdk17-openj9-binAUR, jre-jetbrainsAUR, jre-openjdk-wakefieldAUR, jdk-openjdk-wakefieldAUR, jdk21-openj9-binAUR, zulu-23-binAUR, jreAUR, jdkAUR, jdk21-jetbrains-binAUR, jre-zulu-binAUR, jre-zulu-fx-binAUR, jdk21-dragonwell-standard-binAUR, jdk21-dragonwell-extended-binAUR, jdk-android-studioAUR, java-openjdk-ea-binAUR, jdk-openjdk, jdk11-openjdk, jdk17-openjdk, jdk21-openjdk, jre-openjdk, jre11-openjdk, jre17-openjdk, jre21-openjdk, jre8-openjdk) (make)
- npm (corepackerAUR, python-nodejs-wheelAUR) (make)
- ruby (make)
- sencha-cmd-6AUR (make)
Required by (0)
Sources (2)
bserckx commented on 2019-01-24 22:19 (UTC)
bjo commented on 2019-01-24 17:06 (UTC)
Building fails here:
9 verbose lifecycle @~compile: CWD: /home/build/rambox-os-git/src/rambox-os
10 silly lifecycle @~compile: Args: [ '-c',
10 silly lifecycle 'sencha app build && cpy app/package.json app/package-lock.json build/production/Rambox/ && npm run buildversion' ]
11 silly lifecycle @~compile: Returned: code: 65 signal: null
12 info lifecycle @~compile: Failed to exec compile script
13 verbose stack Error: @ compile: `sencha app build && cpy app/package.json app/package-lock.json build/production/Rambox/ && npm run buildversion`
13 verbose stack Exit status 65
13 verbose stack at EventEmitter.<anonymous> (/usr/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:301:16)
13 verbose stack at EventEmitter.emit (events.js:188:13)
13 verbose stack at ChildProcess.<anonymous> (/usr/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
13 verbose stack at ChildProcess.emit (events.js:188:13)
13 verbose stack at maybeClose (internal/child_process.js:978:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:265:5)
14 verbose pkgid @
15 verbose cwd /home/build/rambox-os-git/src/rambox-os
16 verbose Linux 4.20.3-arch1-1-ARCH
17 verbose argv "/usr/bin/node" "/usr/bin/npm" "run" "compile"
18 verbose node v11.7.0
19 verbose npm v6.7.0
20 error code ELIFECYCLE
21 error errno 65
22 error @ compile: `sencha app build && cpy app/package.json app/package-lock.json build/production/Rambox/ && npm run buildversion`
22 error Exit status 65
23 error Failed at the @ compile script.
bjo commented on 2018-12-13 22:50 (UTC)
I've created an AUR package for the binary builds: https://aur.archlinux.org/packages/rambox-os-bin/
bjo commented on 2018-12-13 13:53 (UTC)
Thanks for the hint!
bserckx commented on 2018-12-13 12:55 (UTC)
@bjo There is quite some controverse about the original rambox, leading to creation of a truly FOSS fork. See https://github.com/ramboxapp/community-edition/issues/1811 and https://github.com/ramboxapp/community-edition/issues/1810
bjo commented on 2018-12-05 18:45 (UTC)
Why do you use the fork instead of the usual repo?
bserckx commented on 2018-11-18 11:02 (UTC)
@bbaserdem : see previous comment
bserckx commented on 2018-11-10 17:09 (UTC)
I have found what is wrong: Sencha CMD 6 does not work with Java 9 or newer, it needs Java 8 or earlier. This should be specified in Sencha CMD's dependencies (which isn't). Building rambox-os in a clean chroot with the Sencha package, automatically grabs a (newer) JRE and sets it as default, so specifying it in rambox-os's makedepends does not work. (Well, I guess this is the reason it does not work) You need to modify Sencha CMD's PKGBUILD, and include that package in your chroot build.
I'll message sencha-cmd's maintainer to fix the PKGBUILD.
bserckx commented on 2018-11-10 12:00 (UTC)
I didn't have an error indeed. I am also not very familiar with NodeJS or Electron myself, but I'll have a look
silverbluep commented on 2018-11-08 19:09 (UTC)
Trying to build this in clean chroot fails, I'm getting build error with log here; https://pastebin.com/MSV23j7p
I don't know much about nodejs, or electron. Any idea how I can fix this? (I assume people have built this package 2 days before successfully judging from the comments)
Pinned Comments
bserckx commented on 2019-08-06 09:50 (UTC)
Hamsket is the new name for Rambox-OS. Please use this package instead of rambox-os-git.
bserckx commented on 2019-08-06 09:49 (UTC) (edited on 2019-08-06 09:50 (UTC) by bserckx)
As rjt said, Rambox-OS is renamed to Hamsket. I made a new package for the git version, located at hamsket-git (https://aur.archlinux.org/packages/hamsket-git/). Please switch to the new package.