Package Details: rambox 0.7.5-2

Git Clone URL: https://aur.archlinux.org/rambox.git (read-only, click to copy)
Package Base: rambox
Description: Free and Open Source messaging and emailing app that combines common web applications into one.
Upstream URL: https://rambox.pro/
Licenses: GPL3
Submitter: flying-sheep
Maintainer: masterkorp
Last Packager: TheGoliath
Votes: 15
Popularity: 0.29
First Submitted: 2017-05-23 23:11
Last Updated: 2020-06-15 11:32

Pinned Comments

TheGoliath commented on 2020-05-28 12:33

I've updated the package to version 0.7.5. Feel free to comment down below if anything doesn't work as expected or related :) In the meantime, happy chatting!

Latest Comments

« First ‹ Previous 1 2 3 4 5 Next › Last »

mollitz commented on 2018-10-07 22:01

+1 validity check error

enderst commented on 2018-09-28 03:14

PKGBUILD is broke

Muflone commented on 2018-09-16 11:11

Apart the unmatching validity checks, also the sources have changed the contained folder to community-edition-$pkgver

mrtakdeniz commented on 2018-09-14 13:57

The 0.5.17.tar.gz file doesn't pass the validity check:

==> Validating source files with sha256sums... 0.5.17.tar.gz ... FAILED Rambox-0.5.17-x64.tar.gz ... Passed rambox.desktop ... Passed rambox.js ... Passed ==> ERROR: One or more files did not pass the validity check!

HedgehogCode commented on 2018-09-11 16:41

The 0.5.17.tar.gz file doesn't pass the validity check:

==> Validating source files with sha256sums...
    0.5.17.tar.gz ... FAILED
    Rambox-0.5.17-x64.tar.gz ... Passed
    rambox.desktop ... Passed
    rambox.js ... Passed
==> ERROR: One or more files did not pass the validity check!

bytee commented on 2018-07-13 09:40

I get an error while installing:

Sencha Cmd v6.5.3.6 [INF] Using GPL version of Ext JS version 5.1.1.451 from rambox/src/rambox-0.5.17/ext. [INF] The implications of using GPL version can be found here (http://www.sencha.com/products/extjs/licensing). [INF] Processing Build Descriptor : default (production environment) [ERR] javax/xml/bind/DatatypeConverter [ERR] [ERR] The application was last modified by an older version of Sencha Cmd (6.1.2.15). [ERR] Running "sencha app upgrade" may resolve the error described above. [ERR] npm ERR! code ELIFECYCLE npm ERR! errno 65 npm ERR! @ sencha:compile: sencha app build && cp app/package.json build/production/Rambox/ && npm --prefix ./build/production/Rambox/ install ./build/production/Rambox/ npm ERR! Exit status 65 npm ERR! npm ERR! Failed at the @ sencha:compile script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in: npm ERR! .npm/_logs/2018-07-13T09_37_34_539Z-debug.log ==> ERROR: A failure occurred in build(). Aborting...

iskenderoguz commented on 2018-05-03 09:13

i have an error while updating

==> Validating source files with sha256sums... 0.5.17.tar.gz ... Passed Rambox-0.5.17-x64.tar.gz ... Passed rambox.desktop ... Passed rambox.js ... Passed ==> Extracting sources... -> Extracting 0.5.17.tar.gz with bsdtar ==> Starting build()... npm ERR! code ERR_STREAM_WRITE_AFTER_END npm ERR! write after end

npm ERR! A complete log of this run can be found in: npm ERR! /home/user/.npm/_logs/2018-05-03T09_08_39_648Z-debug.log ==> ERROR: A failure occurred in build(). Aborting...

log file :

9034 verbose stack Error [ERR_STREAM_WRITE_AFTER_END]: write after end 9034 verbose stack at writeAfterEnd (_stream_writable.js:241:12) 9034 verbose stack at PassThrough.Writable.write (_stream_writable.js:291:5) 9034 verbose stack at PassThrough.Writable.end (_stream_writable.js:576:10) 9034 verbose stack at ReadEntry.entry.on (/usr/lib/node_modules/npm/node_modules/pacote/lib/extract-stream.js:19:41) 9034 verbose stack at ReadEntry.emit (events.js:185:15) 9034 verbose stack at ReadEntry.emit (/usr/lib/node_modules/npm/node_modules/tar/node_modules/minipass/index.js:287:25) 9034 verbose stack at ReadEntry.[maybeEmitEnd] (/usr/lib/node_modules/npm/node_modules/tar/node_modules/minipass/index.js:240:12) 9034 verbose stack at ReadEntry.end (/usr/lib/node_modules/npm/node_modules/tar/node_modules/minipass/index.js:153:27) 9034 verbose stack at Unpack.[consumeBody] (/usr/lib/node_modules/npm/node_modules/tar/lib/parse.js:210:13) 9034 verbose stack at Unpack.[consumeChunkSub] (/usr/lib/node_modules/npm/node_modules/tar/lib/parse.js:391:40) 9034 verbose stack at Unpack.[consumeChunk] (/usr/lib/node_modules/npm/node_modules/tar/lib/parse.js:360:30) 9034 verbose stack at Unzip.(anonymous function).on.chunk (/usr/lib/node_modules/npm/node_modules/tar/lib/parse.js:291:59) 9034 verbose stack at Unzip.emit (events.js:180:13) 9034 verbose stack at Unzip.emit (/usr/lib/node_modules/npm/node_modules/tar/node_modules/minipass/index.js:287:25) 9034 verbose stack at Unzip.write (/usr/lib/node_modules/npm/node_modules/tar/node_modules/minipass/index.js:90:17) 9034 verbose stack at Unzip.write (/usr/lib/node_modules/npm/node_modules/tar/node_modules/minizlib/index.js:284:29)

burningserenity commented on 2018-03-09 02:22

The problem was that I had java-9-sdk as my active Java runtime. I switched it back to java-8-sdk/jre and Rambox compiled just fine.

burningserenity commented on 2018-03-08 23:56

Fails to build with Sencha:

 Sencha Cmd v6.1.3.42
 [INF] Using GPL version of Ext JS version 5.1.1.451 from /tmp/pamac-build-helios/rambox/src/rambox-0.5.16/ext.
 [INF] The implications of using GPL version can be found here (<http://www.sencha.com/products/extjs/licensing>).
 [INF] Processing Build Descriptor : default
 [ERR] javax/xml/bind/DatatypeConverter
 [ERR] 
 The application was last modified by an older version of Sencha Cmd (6.1.2.15)
 the current is 6.1.3.42.
 Please run "sencha app upgrade" to update to 6.1.3.42.

 npm ERR! code ELIFECYCLE
 npm ERR! errno 65
 npm ERR! @ sencha:compile: `sencha app build && cp app/package.json build/production/Rambox/ && npm --prefix ./build/production/Rambox/ install ./build/production/Rambox/`
 npm ERR! Exit status 65
 npm ERR! 
 npm ERR! Failed at the @ sencha:compile script.
 npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

 npm ERR! A complete log of this run can be found in:
 npm ERR!     /home/helios/.npm/_logs/2018-03-08T23_48_07_614Z-debug.log
 ==> ERROR: A failure occurred in build().
     Aborting...

running

 sencha app upgrade

returns null

Also, this is the log produced:

 Sencha Cmd 6.5.3.6 - Crash report
 ================================================
 An error occurred while executing the following command: app upgrade

 Diagnostic information:
 =======================
                           cmd.config.dir : /opt/Sencha/Cmd                                   
                                  cmd.dir : /opt/Sencha/Cmd                                   
               cmd.merge.tool.args.araxis : -wait -merge -3 -a1 {base} {user} {generated} {out}
               cmd.merge.tool.args.kdiff3 : {base} {user} {generated} -o {out}                
              cmd.merge.tool.args.p4merge : {base} {user} {generated} {out}                   
            cmd.merge.tool.args.smartsync : {user} {generated} {base}                         
           cmd.merge.tool.args.sourcegear : --merge --result={out} {user} {base} {generated}  
             cmd.merge.tool.args.tortoise : -base:{base} -theirs:{generated} -mine:{user} -merged:{out}
                               cmd.minver : 3.0.0.0                                           
                             cmd.platform : linux-x64                                         
                      cmd.unicode.escapes : /opt/Sencha/Cmd/unicode-escapes.json              
                              cmd.version : 6.5.3.6                                           
                             cmd.web.port : 1841                                              
                        inspector.address : <http://localhost:1839/>                            
                           repo.local.dir : /opt/Sencha/repo                                  
                        shared.sencha.dir : false                                             
         system.java.net.useSystemProxies : true

 Exception information:
 =======================
 java.lang.NullPointerException
      at com.sencha.command.app.AppCommands$UpgradeCommand.execute(AppCommands.java:1072)
      at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
      at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
      at java.base/java.lang.reflect.Method.invoke(Method.java:564)
      at com.sencha.util.MethodInvoker$Arguments.invoke(MethodInvoker.java:175)
      at com.sencha.cli.Command.dispatch(Command.java:43)
      at com.sencha.command.BasePluginCommands$BasePluginCommand.dispatch(BasePluginCommands.java:289)
      at com.sencha.cli.Commands.dispatch(Commands.java:64)
      at com.sencha.cli.Commands.dispatch(Commands.java:64)
      at com.sencha.command.Sencha.dispatch(Sencha.java:80)
      at com.sencha.command.Sencha.main(Sencha.java:147)
      at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
      at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
      at java.base/java.lang.reflect.Method.invoke(Method.java:564)
      at com.exe4j.runtime.LauncherEngine.launch(LauncherEngine.java:65)
      at com.install4j.runtime.launcher.UnixLauncher.main(UnixLauncher.java:57)

flying-sheep commented on 2018-03-01 08:44

Yeah, the v URL and the checksum mismatch looks like the author changed stuff.

I don’t want to re-host the author’s API keys somewhere. They’re hidden in a asar file inside a .tar.gz file, and I shouldn’t re-host them as plain text where they can be found by e.g. web crawlers.

Yeah, I’d like to replace the convoluted build system, but that needs to be done upstream, not here in this package.