Package Details: etherpad-lite 1:1.8.0-1

Git Clone URL: (read-only, click to copy)
Package Base: etherpad-lite
Description: Lightweight fork of etherpad based on javascript
Upstream URL:
Licenses: Apache
Conflicts: etherpad-lite-git
Submitter: onny
Maintainer: dvzrv
Last Packager: dvzrv
Votes: 29
Popularity: 0.000100
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 ... Next › Last »

twiggers commented on 2016-04-10 09:27

I've reinstalled now and it seems to be working again...

RubenKelevra commented on 2016-02-29 13:10

@twiggers can you paste me the output of $(pacman -Qen) please? I cannot reproduce your issue.

RubenKelevra commented on 2016-02-28 21:42

Sad to hear that twiggers, gonne try this on an freshly installed system and report back to you.

twiggers commented on 2016-02-27 17:00

Etherpad won't start for me with this error: error: could not load library "/usr/lib/postgresql/": /usr/lib/postgresql/ undefined symbol: DatumIsReadWriteExpandedObject

RubenKelevra commented on 2016-02-17 14:58

Update released, please note that you can't install the new package without updating nodejs first. So update nodejs without dependecy-check and upgrade etherpad-lite after this, or remove and reinstall etherpad-lite.

matschi commented on 2016-01-09 20:45

would be great not to have to --ignore nodejs anymore :-P

dvzrv commented on 2015-12-12 13:41

@RubenKelevra: Any particular reason, why you're ignoring my patch for nodejs > 5?

dvzrv commented on 2015-12-01 20:30

@schimicata: Don't start it as your own user or even as root, if you like your system intact. The service starts etherpad-lite as the user etherpad for a reason.
Please follow the output of your journal with "journalctl -f -u etherpad-lite" while starting/stopping/restarting the service.
Your posted output is not complete and doesn't show the initial error.

schimicata commented on 2015-12-01 14:11

Okay, I noticed that something changed the permission for my folders in /usr/share/webapps/etherpad-lite/. I think it should work again as soon as I fixed the permissions.


Okay, it works partly so far. At first: the problem with the icu-packages is fixed. As I updatet nodejs etherpad I had also to update icu to v56.1-1 or etherpad-lite wouldn't start.

But now I have the problem, that I cannot start etherpad-lite as a service. systemctl status -l says:

When I go to /usr/share/webapps/etherpad-lite/bin and run ./ as user it says:
(In the last line it says: no permission). If I start it as root (sudo), it starts. But I don't want to run it as root.

schimicata commented on 2015-12-01 12:40

@dvzrv: Thank you! I thought if I install/update the package from aur, it will apply the patch on it's own. But as far as I could see, the patch won't fix the problem with the icu-package - am I right?