Package Details: etherpad-lite 1:1.8.0-1

Git Clone URL: https://aur.archlinux.org/etherpad-lite.git (read-only, click to copy)
Package Base: etherpad-lite
Description: Lightweight fork of etherpad based on javascript
Upstream URL: http://etherpad.org
Licenses: Apache
Conflicts: etherpad-lite-git
Submitter: onny
Maintainer: dvzrv
Last Packager: dvzrv
Votes: 28
Popularity: 0.000045
First Submitted: 2013-03-15 15:10
Last Updated: 2019-12-09 12:58

Pinned Comments

dvzrv commented on 2019-02-10 17:17

The upgrade to 1.7.5 brought a lot of security fixes. Please upgrade! The custom directory in /etc/etherpad-lite was replaced by no-skin, introducing a new skin system. The credentials.json file was added and can be used to setup credentials as well.

dvzrv commented on 2017-12-22 16:18

I updated to 1.6.2.

Please note: From now on, etherpad-lite is relying on systemd-tmpfiles and systemd-sysusers and the setting of a dynamic StateDirectory according to its service file. The scripts delivered by upstream are no longer run.

These new features make the package more secure, but the new way of installing it also renders its content static (i.e. the installation of plugins is currently not possible, as the installation folder is now owned by root).

Before the included npm package had the possibility to install all over the install directory, leading to folders and files not taken care of or cleaned up by pacman.

Although the new state is somewhat unfortunate, I hope you can appreciate it nonetheless from a viewpoint of this now being a "clean(er) install".

I referred to upstream about the changes to maybe inspire a change in the way plugins should be installed to a dedicated (settable) directory.

The way etherpad-lite is installed now is still far from being perfect.

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 11 ... Next › Last »

dvzrv commented on 2015-12-01 00:07

@schimicata: You can apply my patch (https://paste.sleepmap.de/view/2fe369aa) and install it, if you like.
I have etherpad running with nodejs>5.1 and npm>3.5 for weeks without any problems.

schimicata commented on 2015-11-26 14:08

EDIT #2: Okay, so etherpad-lite 1:1.5.7-2 doesn't work with icu>55.1-1. Also it doesn't work with nodejs 4.x for me.
But etherpad-lite 1:1.5.7-2, npm 3.5.0-1, nodejs 0.12.7-1 and icu 55.1-1 works fine for me now.

EDIT #1: I found the source of the error. I downgraded the package icu from v56.1-1 down to v55.1-1 and now yaourt seems update etherpad-lite.

=======
when i do # ln -s /lib/libicui18n.so.56 /lib/libicui18n.so.55 I get those errors:
node: symbol lookup error: node: undefined symbol: _ZTVN6icu_5513UnicodeStringE
./bin/installDeps.sh: Zeile 41: [: =: Einstelliger (unärer) Operator erwartet.
node: symbol lookup error: node: undefined symbol: _ZTVN6icu_5513UnicodeStringE
Copy the settings template to settings.json...
Ensure that all dependencies are up to date... If this is the first time you have run Etherpad please be patient.
node: symbol lookup error: node: undefined symbol: _ZTVN6icu_5513UnicodeStringE

schimicata commented on 2015-11-26 12:58

I can't start etherpad anymore. When I try to run ./debugRun.sh I get these messages:
./debugRun.sh
node: error while loading shared libraries: libicui18n.so.55: cannot open shared object file: No such file or directory
bin/installDeps.sh: Zeile 41: [: =: Einstelliger (unärer) Operator erwartet.
node: error while loading shared libraries: libicui18n.so.55: cannot open shared object file: No such file or directory
Ensure that all dependencies are up to date... If this is the first time you have run Etherpad please be patient.
node: error while loading shared libraries: libicui18n.so.55: cannot open shared object file: No such file or directory

I'm running etherpad-lite 1.5.7-1, npm 3.5.0-1 and nodejs 0.12.7-1. I tried to update nodejs to 4.x but I couldn't find nodejs4 anywhere.

dvzrv commented on 2015-11-17 00:17

@RubenKelevra: This must be updated for 5.x.
I made more generic patch, that you can integrate, if you like: https://paste.sleepmap.de/view/38e75fab

RubenKelevra commented on 2015-10-23 19:14

Added a fast fix for nodejs' version bump to 4.x everthing below 5.x should work now without any fixes. Hopefully they don't drop compability without changing the major-version.

mjob commented on 2015-10-14 07:01

Just upgraded to nodejs 4.2.1 and it works :)

dvzrv commented on 2015-10-13 17:55

Let's see if nodejs 4.2.1 fixes this issue as promised.
https://github.com/nodejs/node/commit/c245a199a7

dvzrv commented on 2015-10-13 11:53

@mjob: Yeah, sorry for not checking the version in the meantime! Thought I was on 4.2, too.

Hmm, so this has to be reported upstream with nodejs somehow.

mjob commented on 2015-10-13 11:36

Just for documentation: This only works with nodejs 4.1.2 but not with 4.2.0 - use an old version from http://seblu.net/a/arm/packages/n/nodejs/ in the meantime.

dvzrv commented on 2015-10-13 11:12

@mjob I'm also on the new nodejs. And mysql/mariadb works with the below mentioned settings.

I suspect some other issue with your setup.