Package Details: rambox-os-git r1028.da3e283-1

Git Clone URL: (read-only)
Package Base: rambox-os-git
Description: Free and Open Source messaging and emailing app that combines common web applications into one.
Upstream URL:
Licenses: GPL3
Conflicts: rambox, rambox-bin, rambox-os
Provides: rambox-os
Submitter: DenBrahe
Maintainer: DenBrahe
Last Packager: DenBrahe
Votes: 2
Popularity: 1.109731
First Submitted: 2018-10-23 14:46
Last Updated: 2019-02-21 10:19

Latest Comments

1 2 Next › Last »

HanFox commented on 2019-02-20 04:45

Ah, well sencha-cmd has an update, so maybe the out-of-date flag will grab the maintainers attention.

DenBrahe commented on 2019-02-19 13:29

That does not work for clean builds, as sencha-cmd-6 first installs another java runtime, to which archlinux-java defaults after that.

sencha-cmd-6 should change its java-runtime dependency to java-runtime<=8, but the maintainer does not respond, so this is for now the best fix I can give afaik.

HanFox commented on 2019-02-19 13:09

Instead of specifying jre8-openjdk you could specify java-runtime=8 as a build dependency.

That should then avoid prompting to install jre8-openjdk if jdk8 or jre8 is already installed, but will still fetch openjdk if no Java is installed.

DenBrahe commented on 2019-01-25 11:44

I've added jre8-openjdk as a build dep, and fixed the build script so now it builds in a clean chroot without further intervention.

DenBrahe commented on 2019-01-24 23:16

Okay, I think I'm out. Sencha CMD require Java 8 or less. However, when installing in a clean chroot, it installs the java-runtime packages, which defaults to jre-openjdk, which is Java 11. So adding Java 8 or less to rambox-os' make-depends does not help, since the default java-runtime is still 11.

The workaround that I see, is to manually install a Java <=8 runtime like jre8-openjdk in the chroot before installing the package, using something like arch-nspawn $CHROOT/root pacman -Syu jre8-openjdk.

Upstream is planning to abandon ExtJS (and I guess Sencha CMD too).

DenBrahe commented on 2019-01-24 22:19

@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.

bjo commented on 2019-01-24 17:06

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

I've created an AUR package for the binary builds:

bjo commented on 2018-12-13 13:53

Thanks for the hint!

DenBrahe commented on 2018-12-13 12:55

@bjo There is quite some controverse about the original rambox, leading to creation of a truly FOSS fork. See and