Package Details: rambox 0.5.17-3

Git Clone URL: https://aur.archlinux.org/rambox.git (read-only)
Package Base: rambox
Description: Free and Open Source messaging and emailing app that combines common web applications into one.
Upstream URL: http://rambox.pro/
Licenses: GPL3
Submitter: flying-sheep
Maintainer: masterkorp
Last Packager: flying-sheep
Votes: 14
Popularity: 0.001255
First Submitted: 2017-05-23 23:11
Last Updated: 2019-04-05 17:59

Latest Comments

1 2 3 4 5 Next › Last »

flying-sheep commented on 2019-04-28 12:35

Hi! I switched to rambox-os, so I’m orphaning this

flying-sheep commented on 2019-04-05 17:59

thanks!

w4rdriver commented on 2019-04-04 21:23

Hey bro, it appears as your package is breaking because the upstream renamed rambox to community-edition so you can't cd to $pkgname-$pkgver, so I edited it back to rambox.

sed -i 's/cd "$pkgname-$pkgver"/mv "community-edition-$pkgver" "$pkgname-$pkgver"\n\tcd "$pkgname-$pkgver"/' PKGBUILD

michaldybczak commented on 2019-02-18 00:22

I'll hope the issue will be resolved but for the time being, I'm switching to snap version. Native packages are always better but it's good we have alternatives in cases like this.

flying-sheep commented on 2019-02-17 11:04

@Blubberbub thank you for the help! Sadly I can’t figure out how to package the deps … would manually copying the node_modules help?

flying-sheep commented on 2019-02-17 11:01

Hey @Muflone @therojam: You filed orphan and maintenance and requests but as you can see from the comments, nobody is able to compile the package anymore.

I’d love to keep maintaining it, as soon as someone figures out how to do so.

Please post a working PKGBUILD into the comments, then I’ll gladly add you as comaintainer.

mollitz commented on 2019-01-27 19:39

checksum fails

Blubberbub commented on 2019-01-14 13:33

This seems to be a related issue: https://github.com/Teamwork/node-auto-launch/issues/67

Couldn't get it to work, though. The "auto-launch" and the "auto-launch-patched" packages seem to be very closely related?

This commit from a pull-request looks like it might fix the issue: https://github.com/Teamwork/node-auto-launch/pull/82/commits/623ec2dee35141263ed8cd904535a4fe6fd649c3

EDIT: It seems to not be a problem related to that single package. When i replaced the requirement with a mockup i got the same error message for a different package (electron-store):

sed -i "s/require('auto-launch-patched')/(function (a) {this.enable = function(){};this.disable = function(){}})/" '../rambox-build/electron/main.js'

Using sencha app watch and npm start launches the app successfully, so i guess the problem is with the sencha compile command not packaging the dependencies? In the old version there were node_modules in /usr/lib/rambox/node_modules which are now not generated anymore?

nbvcxz commented on 2018-12-13 21:11

@flying-sheep same error here, package compiled (with a lot of warnings, electron 3.0.11, Rambox 0.6.3), anyboby successful compiling and running new Rambox (with native electron)?

flying-sheep commented on 2018-11-08 10:32

Here’s my try, including the error I get: https://gist.github.com/flying-sheep/8fc4f1189a53619a74e12f351f21eb28