Package Details: etherpad-lite 1:1.8.18-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: 28
Popularity: 0.000025
First Submitted: 2013-03-15 15:10 (UTC)
Last Updated: 2022-05-12 19:28 (UTC)

Pinned Comments

Latest Comments

dvzrv commented on 2022-02-28 12:22 (UTC)

@rstoye: It's always a good idea to wait and/or investigate with upstream a bit if this kind of thing happens. After all it could mean that upstream has been compromised and someone e.g. has added malware.

rstoye commented on 2022-02-28 12:09 (UTC) (edited on 2022-02-28 12:10 (UTC) by rstoye)

@dvzrv, since i could't find sha512 codes i created them (and the b2sum as well, edited the PKGBuild and used makepackage to install it. Isn't that whats be needet to be done to the PKGBUILD in AUR?

sha512sums=('af34dd50777b06eb714b42c47a5232dd902ce9d48b7cbeb9784910071abbe5486d8c0a52b7c57794edef3f33e3381c7c34b9577a814205d9b60049cd7dc2ada6' ... b2sums=('06236b554f8be7428c7249b0b065b5bdc96c8a876046bfaf1af022bcfbe35926daf8af120989a8385c8c5bed6e8bcae5ea4d915e4b695b3b12768c829822499c' ...

edit: just read your issue - you are right

dvzrv commented on 2022-02-28 11:41 (UTC)

@rstoye: Thanks. I have opened for that. They retagged their stuff because someone forgot to merge some docker related changes it seems.

rstoye commented on 2022-02-27 21:30 (UTC)

checksums are not valid ==> Validating source files with sha512sums... etherpad-lite-1.8.17.tar.gz ... FAILED

pwlb commented on 2021-10-27 19:23 (UTC)

is there any reason for not allowing arm architectures?

zangoku commented on 2021-09-14 16:17 (UTC)

I am getting the following npm ERR! semver.simplifyRange is not a function

anonfunc commented on 2021-06-03 21:08 (UTC) (edited on 2021-06-03 21:09 (UTC) by anonfunc)

@mrpg I downgraded to nodejs-lts, that did the trick for me. Seems like its a issue in node or a new interaction with latest nodejs.

mrpg commented on 2021-06-03 19:59 (UTC)

Has anyone gotten this to run recently? I was not able to access the website, so I dug a little deeper.

It seems to break right after starting the service, with journalctl saying something like /usr/bin/node[147752]: ../src/api/ node::InternalCallbackScope::Close(): Assertion(env_->execution_async_id()) == (0)' failed.. I can also bind to port 9001 usingnc -4 -l 9001` with no errors, so it truly doesn't seem to be running anymore.

Any insights?

dvzrv commented on 2021-03-25 19:37 (UTC)

Please not that 1.8.13 seems to be broken, so I will refrain from packaging it until upstream has addressed the issue:

dvzrv commented on 2020-05-18 20:34 (UTC)

Is there a manual procedure I could follow to install a plugin?

@mrvdb: Not that I'm aware of. However, if you're up for the pain, you can of course start packaging extensions for etherpad-lite.

Even if this means redoing it on upgrading the package it's worth it sometimes. Having the secure base install is nice, but without /any/ option to get a plugin to work, most people will need to choose another install method than this package.

And people are free to do so.

I saw someone mentioning manually putting a .ep_initialized file in the plugin folder, but that didn't seem to work for me. Also, given that the upstream issue has been open for more than 2 years now, a workaround would perhaps be fitting.

The problem is, that etherpad-lite doesn't really have a "plugin directory", but pollutes its base install directory when installing plugins.

That being said: You're free to modify this PKGBUILD for your own purposes of course. From a packaging standpoint it makes no sense though as it is unsafe to use and would basically require manual intervention all the time.

If you have some time to spend it is always a good idea to help upstream figure out how to solve the plugin directory issue and fix this problem at the root instead of making your system less secure.

mrvdb commented on 2020-05-16 12:17 (UTC) (edited on 2020-05-16 12:18 (UTC) by mrvdb)

Is there a manual procedure I could follow to install a plugin?

Even if this means redoing it on upgrading the package it's worth it sometimes. Having the secure base install is nice, but without /any/ option to get a plugin to work, most people will need to choose another install method than this package.

I saw someone mentioning manually putting a .ep_initialized file in the plugin folder, but that didn't seem to work for me. Also, given that the upstream issue has been open for more than 2 years now, a workaround would perhaps be fitting.

respiranto commented on 2020-05-01 18:05 (UTC)

The problem appears to be caused by the fact that our Etherpad instance is served by Apache (proxy) under /pad. The fonts seem to be searched for using absolute paths, which probably was not the case before.

So this is not a packaging issue.

dvzrv commented on 2020-05-01 17:38 (UTC) (edited on 2020-05-01 17:41 (UTC) by dvzrv)

@respiranto: is your docroot at /usr/share/etherpad-lite/src/? The files are part of the package and are in /usr/share/etherpad-lite/src/static/font.

Note: Fixed typo in path

respiranto commented on 2020-05-01 17:17 (UTC)

The problem appears with both skins.

respiranto commented on 2020-05-01 17:06 (UTC)

Thanks for the quick reply!

I do indeed get several 404's for the following (font) requests:

GET /static/font/fontawesome-etherpad.woff?2 HTTP/1.1
GET /static/font/Roboto-Bold.ttf HTTP/1.1
GET /static/font/fontawesome-etherpad.ttf?2 HTTP/1.1
GET /static/font/Roboto-Regular.ttf HTTP/1.1

I adapted the configuration using a three-way diff between the old default, the new default and the custom version.

Probably unrelated, but for some reason, one of the preexisting notes, that I used to test the impact of configuration changes is now presented with the default text (and no history), even though it still exists in the database.

dvzrv commented on 2020-05-01 16:16 (UTC)

@respiranto: I can't reproduce this. Which skin are you using? The new "colibris" (that one works fine for me)? Did you use pacdiff (in pacman-contrib) to diff your configuration?

Do you see any error messages in the logs? Check your web server logs for 404s and potentially your etherpad-lite.service journal output.

respiranto commented on 2020-05-01 16:03 (UTC)

All the icons (e.g., to create a list) do no longer show (instead I see those boxes containing 4 hex digits). I do not know whether this is due to removed files or an upstream change requiring something on the client (a font?) that I do not have.

dvzrv commented on 2020-05-01 12:52 (UTC)

I have started removing a lot of arbitrary files in package() to lower the amount of files in this package. If this causes any trouble due to missing files, please let me know!

Apart from that, I have added many additional hardening options to the service file. If any of those cause trouble, please let me know!

etherpad-lite now also supports using unix sockets. I didn't have the time to test this yet, but if you test it, please give feedback and leave suggestions for e.g. systemd sockets unit (if that's possible).

Tio commented on 2020-04-07 11:52 (UTC)

I thought this can be an application that you can run on your desktop and uses a public instance. But I see this is for you to create a public instance.

dvzrv commented on 2020-04-07 11:50 (UTC)

@Tio: what do you mean by "desktop use"? This is a web application, that you can run on a machine and then access via http (your web browser).

If you want to share this with more people by hosting it on a publicly accessible server is up to you! :)

Tio commented on 2020-04-07 11:45 (UTC)

Hi. Quick question: this is not made for desktop use, but for server use? Correct?

neitsab commented on 2019-11-19 07:38 (UTC)

Thank you @dvzrv for both answers. I tried to look for a "self-contained" Etherpad-lite (via nw.js or electron) to adapt this webapp for a desktop use (with a .desktop file and an icon and all) and to which we could maybe add modules, but to no avail. I'll keep doing it this way or go the manual install route if I really need the plugins.

dvzrv commented on 2019-11-14 14:32 (UTC)

@neitsab: Yes, using this package, etherpad-lite can not install plugins (because the unregulated access to the file system is a high security risk). As long as upstream doesn't find a way to specify a custom location for plugins, this will remain that way.

Furthermore, this PKGBUILD tracks stable releases. If you require a more recent version for yourself, you can either modify the PKGBUILD or create a new one (e.g. for a -git package).

neitsab commented on 2019-11-14 01:48 (UTC) (edited on 2019-11-14 01:53 (UTC) by neitsab)

Edit: sorry, hadn't read the pinned comment from 2017 :D

So for now using this package, it is completely impossible to install plugins? Nobody has found a workaround?

I like the cleanliness of the install but it drastically reduces the interest of the software.

Unrelated question: noticed the official homepage offers the latest 18.8 beta version to download... Should this package follow that or remain on GitHub releases?


dvzrv commented on 2019-02-10 17:17 (UTC)

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.

RubenKelevra commented on 2018-10-11 19:09 (UTC)

@dvzrv thanks a lot for giving my old package new love! :)

dvzrv commented on 2018-06-18 22:50 (UTC)

@immae: Honestly, I would refrain from ever running npm as root.

That being said, I think, that the cleanest way would probably be to define a separate folder for the "user installed" packages, to not pollute the static set of packaged node packages, that come with the application. This directory for the user installed packages would need to be writable by the user running etherpad-lite (this should also never be root), ideally somewhere under /var/lib/etherpad-lite. Sadly, this has not yet been implemented upstream (which is barely keeping up with updating the security hole infested plugins, etherpad-lite is built from).

immae commented on 2018-06-18 06:57 (UTC)

I’ll answer my own question, maybe it can help other people with the same problem. So actually, etherpad tries to initialize each module, creating a .ep_initialized in each of them. This call hangs forever, thus making the whole thing hang too (for reference: src/static/js/pluginfw/plugins.js method callInit).

It turns out that most modules don’t have an initialization hook (I have 20 and none of them has it), so just touch-ing the .ep_initialized file of each module will unlock the process.

This permits at least to load a bunch of modules installed manually. It doesn’t solve every case, but it may help.

immae commented on 2018-06-18 05:40 (UTC)

Hello @dvzrv, Thanks for your packaging. The idea of making the /usr/share folder static is nice. However I tried to install plugins manually, doing npm install as root from the /usr/share/etherpad-lite, but the start of etherpad then stales waiting for something forever (and never listening).

Did you manage to do this kind of manual installation? You seem to suggest so in the github issue, but maybe I missed something. Modules installation seem to say it should work to just run this npm install (e.g. )

dvzrv commented on 2018-04-12 17:24 (UTC)

@schimicata: my bad, forgot to run updpkgsums. It's now fixed.

schimicata commented on 2018-04-12 11:10 (UTC) (edited on 2018-04-12 11:12 (UTC) by schimicata)

upgrave from v1.6.3 to v1.6.5 fails with:

==> Validating source files with sha512sums...

etherpad-lite-1.6.5.tar.gz ... Passed
jquery-1.9.1.js ... Passed
etherpad-lite-sysusers.conf ... Passed
etherpad-lite-tmpfiles.conf ... Passed
etherpad-lite.service ... FAILED

==> ERROR: One or more files did not pass the validity check!

:: failed to verify etherpad-lite integrity

dvzrv commented on 2018-03-13 11:20 (UTC)

@GFdevelop why do you flag this out-of-date? There is no new release!

If there are problems with etherpad-lite, report them upstream. This is not a development platform!

dvzrv commented on 2018-02-03 16:26 (UTC) (edited on 2018-02-03 16:27 (UTC) by dvzrv)

Upgraded to 1.6.3.

The move of {APIKEY,SESSIONKEY}.txt to /etc/etherpad-lite was not very straight forward though. Currently it is not possible to put these files in the backup array, as they would have to be created for that first. Using an empty file for them doesn't work though [1].

Adding them to the backup array without being created leads to them being renamed to a .pacsave file every time.

So, there's no real benefit of them being in /etc/etherpad-lite for the time being (apart from a more strict folder permission).

Additionally, I've unset the specific $HOME directory for the etherpad-lite user (via sysusers.d).


dvzrv commented on 2018-02-03 14:20 (UTC)

Hmm, according to the devtools output, gnuplot is an uninstalled dependency. I just can't find the reference to it anywhere, so it might be a red herring. It's removed for the time being.

I'll push an update for 1.6.3 in a few minutes and include the move of the {SESSIONKEY,APIKEY}.txt to /etc/etherpad-lite.

Please keep that change in mind!

patrick.luehne commented on 2018-01-29 23:55 (UTC)

@dvzrv: According to the Wiki, the APIKEY.txt file is generated upon the first execution of Etherpad Lite [1]. Concerning the SESSIONKEY.txt, the Arch Wiki recommends setting the sessionKey configuration option in settings.json [2]. However, with the release of Etherpad Lite 1.5.5, this option seems to have moved to SESSIONKEY.txt according to the release notes [3].

From this point of view, it could make sense to treat both secrets as configurable by users and put them in /etc/etherpad-lite (that’s just my opinion).

That being said, I’d suggest leaving the permissions of /etc/etherpad-lite at 750, because the settings.json may contain secrets (database access, basic authentication, etc.).




dvzrv commented on 2018-01-29 19:09 (UTC)

@patrick.luehne: I don't think it will. It seems, that they are automatically created by the application. I tried to figure out more about them and their handling upstream, but they either didn't understand my feature request regarding the state directory, or just haven't gotten around doing anything about it. Are the *KEY.txt files meant to be changed by the user?

Regarding the state directory: It will automatically be created upon first start of the application by the systemd service file. The user doesn't need to take care of it. The "standard" dirty.db will be moved there as well, because of the modification in the prepare() function.

Another thing, I'm currently elaborating is, whether chmodding /etc/etherpad-lite to 750 is maybe too restrictive...

patrick.luehne commented on 2018-01-29 18:50 (UTC)

@dvzrv: On another note, would it make sense to symlink the APIKEY.txt and SESSIONKEY.txt to /etc/etherpad-lite instead of /var/lib/etherpad-lite?

To my mind, these two are more like configuration files than something that belongs to /var/lib. Additionally, /etc/etherpad-lite is already created with restrictive permissions in contrast to some /var/lib/etherpad-lite that users would create manually, perhaps forgetting to restrict the directory permissions to something different than 755.

patrick.luehne commented on 2018-01-29 18:46 (UTC)

@dvzrv: Many thanks for your quick response. This will clean up things for sure :).

dvzrv commented on 2018-01-29 18:44 (UTC)

@patrick.luehne: You are right. It's still a left over from the previous packager(s). I meant to check it out, but forgot. Will remove it in a new pkgrel!

patrick.luehne commented on 2018-01-29 18:13 (UTC)

Dear maintainers,

I wonder why gnuplot is listed as a dependency for etherpad-lite. I couldn’t find any reference to gnuplot in the source code hosted at GitHub. Additionally, gnuplot pulls a lot of dependencies such as gd, wxgtk2, gtk2, gstreamer, sdl, and qt5-svg, which usually aren’t installed on servers.

Would it make sense to remove gnuplot from the dependencies? If that’s not possible, it could also be turned into an optdep, for example.

On my personal server, I manually removed gnuplot as a dependency, and everything appears to run smoothly.

Best wishes, Patrick

twiggers commented on 2017-12-27 13:14 (UTC)

Aside from what dvzrv noted, the user that is running etherpad-lite changed to 'etherpad-lite' (originally 'etherpad') and the configuration files moved. This lead to some non-trivial breakages on my end (I need to move a postgresql database).

dvzrv commented on 2017-12-22 16:18 (UTC) (edited on 2017-12-22 18:06 (UTC) by dvzrv)

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.

matschi commented on 2017-12-12 19:34 (UTC)

At this point I'd like to say thanks to you two for maintaining. :-)

dvzrv commented on 2017-12-12 19:29 (UTC)

@RubenKelevra: No worries. I'll get to it in the next few days. Remember: 'Real life' will ruin your life! ;-)

RubenKelevra commented on 2017-12-12 18:47 (UTC)

Feel free to adopt this package, the last update should be minor, but I haven't got the time to do it. Sorry for the delay

dvzrv commented on 2017-11-04 19:55 (UTC)

@RubenKelevra: I have been maintaining my private PKGBUILD for this package, as I don't like the way it is packaged in /usr/share/webapps and how it is forcefully deleting files during .install and still leaves random files behind in its install directory after removal. I found a way to facilitate systemd's DynamicUser (with StateDirectory since systemd>235) to create a static version of this package, that doesn't call (and by proxy constantly [1], which means, it doesn't create files unaccounted for (with the downside, that you can also not install plugins so easily). For security and practicality reasons I'd like you to consider the attached PKGBUILD, which could be a good starting point to fix some issue with yours. [1]

RubenKelevra commented on 2017-02-08 22:43 (UTC)

@sofchanger you can ignore this warning.

sofchanger commented on 2017-01-20 20:01 (UTC) (edited on 2017-01-20 20:02 (UTC) by sofchanger)

Hi, after installation, shows me this: :: Processing package changes... (1/1) installing etherpad-lite [############] 100% useradd: warning: the home directory already exists. Not copying any file from skel directory into it. Whats happends? I not launch etherpad-lite. Please, help me! Thanks!

RubenKelevra commented on 2016-12-24 19:01 (UTC)

Update 1.6.1 is out, package was just updated. Merry x-mas :)

RubenKelevra commented on 2016-12-21 17:30 (UTC)

Good news, etherpad-lite is close to a new fixing release 1.6.1 which makes the issues obsolete :)

RubenKelevra commented on 2016-12-19 04:42 (UTC)

I'm sorry this package is currently not possible to build or run with all updates installed. You would need to downgrade nodejs and the dependency icu, which then breaks Pacman. I've added a ticket to the project, until this bug is not fixed, I cannot provide a solution. If somebody has another solution I would be grateful!

schimicata commented on 2016-12-02 13:00 (UTC)

For sudo -u etherpad /usr/share/webapps/etherpad-lite/bin/ I'll get following errors and etherpad doesn't start up.

RubenKelevra commented on 2016-12-01 20:27 (UTC)

Just to be clear, on this update, the warnings might still appear, because the checks are done previously before upgrading.

smithinger44 commented on 2016-11-26 23:05 (UTC)

npm returns so many warnings during installation:

PetaByteBoy commented on 2016-11-11 08:57 (UTC)

@RubenKelevra compatibility issues with nodejs >= 7.0

RubenKelevra commented on 2016-06-15 04:56 (UTC)

Thanks for your hint.

schimicata commented on 2016-06-10 10:20 (UTC)

@RubenKelevra: Yaourt doesn't see the newer version of etherpad-lite, so it doesn't upgrade it automatically. Is it because in v1:1.5.7-3 there was "epoch=1" in PKGBUILD and now it's "#epoch=1" --> thus epoch=0 ?

RubenKelevra commented on 2016-06-07 13:02 (UTC)

@dvzrv sorry for the delayed releases, but I test every release some days in my environment, since sometimes they are far from stable. I dislike unstable software and don't want to push them to you. :)

dvzrv commented on 2016-05-24 22:35 (UTC)

etherpad-lite 1.6.0 is working with nodejs>=6.2. Version patch now not needed anymore. Anyone willing to try can makepkg this:

commented on 2016-05-10 18:07 (UTC)

I needed to downgrade to icu 56 (57 is the current version). After this the etherpad service started just fine.

matschi commented on 2016-05-05 16:04 (UTC)

Has Issues with nodejs 6

twiggers commented on 2016-04-10 09:27 (UTC)

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

RubenKelevra commented on 2016-02-29 13:10 (UTC)

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

RubenKelevra commented on 2016-02-28 21:42 (UTC)

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 (UTC)

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 (UTC)

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 (UTC)

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

dvzrv commented on 2015-12-12 13:41 (UTC)

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

dvzrv commented on 2015-12-01 20:30 (UTC)

@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 (UTC) (edited on 2015-12-01 14:24 (UTC) by schimicata)

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 (UTC)

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

dvzrv commented on 2015-12-01 00:07 (UTC)

@schimicata: You can apply my patch ( 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 (UTC) (edited on 2015-11-26 15:12 (UTC) by schimicata)

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/ /lib/ I get those errors: node: symbol lookup error: node: undefined symbol: _ZTVN6icu_5513UnicodeStringE ./bin/ 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 (UTC)

I can't start etherpad anymore. When I try to run ./ I get these messages: ./ node: error while loading shared libraries: cannot open shared object file: No such file or directory bin/ Zeile 41: [: =: Einstelliger (unärer) Operator erwartet. node: error while loading shared libraries: 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: 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 (UTC)

@RubenKelevra: This must be updated for 5.x. I made more generic patch, that you can integrate, if you like:

RubenKelevra commented on 2015-10-23 19:14 (UTC)

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.

commented on 2015-10-14 07:01 (UTC)

Just upgraded to nodejs 4.2.1 and it works :)

dvzrv commented on 2015-10-13 17:55 (UTC)

Let's see if nodejs 4.2.1 fixes this issue as promised.

dvzrv commented on 2015-10-13 11:53 (UTC)

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

commented on 2015-10-13 11:36 (UTC)

Just for documentation: This only works with nodejs 4.1.2 but not with 4.2.0 - use an old version from in the meantime.

dvzrv commented on 2015-10-13 11:12 (UTC)

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

commented on 2015-10-13 09:40 (UTC)

@dvzrv Mine looks like this: It doesn't work. With the old nodejs it connects just fine. With the new one not.

dvzrv commented on 2015-10-13 09:32 (UTC)

@mjob: not quite sure what you are doing there. It works just fine with my installation. My database configuration block looks like this: Don't forget the "host"! "socketPath" is not etherpad-lite specific afaik.

commented on 2015-10-13 08:29 (UTC)

I just tested it. Doesn't work either. I also couldn't find socketPath in the code:

commented on 2015-10-13 08:19 (UTC)

"socketPath": "/var/run/mysqld/mysqld.sock" Ah ... I used the "port" setting that worked with older nodejs just fine, but maybe it simply used the localhost. See

dvzrv commented on 2015-10-13 08:13 (UTC)

@mjob: with mine it does. You most likely have a configuration problem. Add "socketPath": "/var/run/mysqld/mysqld.sock" to your dbSettings (at the end)! I completely forgot to add a bug report for it! This also took me 10 minutes of googling :P

commented on 2015-10-13 07:35 (UTC)

@dvzrv No luck so far My used PKGBUILD (don't use it - it currently doesn't work)

dvzrv commented on 2015-10-07 00:36 (UTC)

I just realized that a lot of backslashes were missing in that PKGBUILD for some reason. Added those and the makedepends for rsync: Works fine for me so far. Anyone else tested it? Seems the pull request for the node.js version test is taking some time to get processed for master...

dvzrv commented on 2015-10-04 17:34 (UTC)

@mjob: If you're keen on testing, you can apply this pull request: @RubenKelevra: Is it really necessary to do all those chmods during package()? Why do other users/groups than "etherpad" need the execute bit? If at all, those should actually be removed not added. I updated the PKGBUILD, incorporating above mentioned pull request, removed some (hopefully) unneeded stuff, moved other relevant things to /usr/share/doc/etherpad-lite, used rsync as copy command (sorry, still not in makedepends) and otherwise solely relied upon the use of install. Check it out: (sorry, still self-signed).

RubenKelevra commented on 2015-09-21 23:28 (UTC)

I'm already testing, stay tuned.

commented on 2015-09-21 15:17 (UTC)

There is now nodejs 4.1.0 in the repos. Can this package be updated or is it incompatible with the new nodejs?

RubenKelevra commented on 2015-09-01 11:30 (UTC)

The missing button-issue has been reported and confirmed here: I'm NOT going to create a patch for this. If somebody is willing to provide one, this is very welcome.

RubenKelevra commented on 2015-08-30 07:50 (UTC)

@KlipperKyle I'm testing two szenarios: -Fresh-install with default-config. -MySQL-setup with some thousands of pads. If you can provide any hint how to get etherpad to work, please write it down to the wiki, since this depends on customized configs. I think the MySQL-setup is the most used variant. :)

KlipperKyle commented on 2015-08-30 04:25 (UTC)

@RubenKelevra, I'm sorry it took so long to get back to you. I am in fact using sqlite3. I have the sqlite pacman package installed and the npm sqlite3 package installed in the webapps directory as I mentioned earlier. I had to make a couple of changes (after install) to etherpad's settings.json to tell it to use sqlite. By default it uses it's own "dirtyDB", which it looks like you are using. <> I remember when I switched the config setting to use sqlite, etherpad kept giving errors about how sqlite libraries were missing (because I had yet to `npm install sqlite3`). After `npm install sqlite3`, everything seemed to work fine.

RubenKelevra commented on 2015-08-17 18:45 (UTC)

Well I'm maintaining a pad-instance with a several hundred megabytes db and 20-80 users concurrently using the pad as daily peak. I use a nginx reverse proxy in front of the pad server which add https and caching of static js/css. Maybe my issue depends on the size or setup but it was gone since the downgrade, so it is definitely an issue which is introduced with the new version.

schimicata commented on 2015-08-17 17:13 (UTC)

I didn't notice any issues so far. My Pad is still running on 1.5.7 without any problems.

RubenKelevra commented on 2015-08-15 19:20 (UTC)

I discovered several issues: not saving changes in pad, some missing buttons etc. since the upgrade from 1.5.2 to 1.5.7. I will test the subversions between, and create some bugreports. Until then I downgrade the package to the last known working version 1.5.2. I'm sorry for any inconvenience

RubenKelevra commented on 2015-08-14 15:24 (UTC)

Thank you! Gonna release a new Version today

schimicata commented on 2015-08-14 15:17 (UTC)

@RubenKelevra I disowned it now, so you can maintain it again. Sorry for that delay.

RubenKelevra commented on 2015-08-14 13:35 (UTC)

@KlipperKyle I've tested it on my Test-Machine, but here is your bug not happening. Aug 14 15:33:47 i3 systemd[1]: Started Etherpad-Lite server. Aug 14 15:33:48 i3[16477]: Ensure that all dependencies are up to date... If this is the first time you have run Etherpad please be patient. Aug 14 15:33:48 i3[16477]: npm WARN package.json ep_etherpad-lite@1.5.7 No license field. Aug 14 15:33:50 i3[16477]: Ensure jQuery is downloaded and up to date... Aug 14 15:33:50 i3[16477]: Clearing minified cache... Aug 14 15:33:50 i3[16477]: Ensure custom css/js files are created... Aug 14 15:33:50 i3[16477]: Started Etherpad... Aug 14 15:33:51 i3[16477]: [2015-08-14 15:33:51.321] [WARN] console - DirtyDB is used. This is fine for testing but not recommended for production. I think sqlite3 is the wrong Database for etherpad-lite, so are you using sqlite3? Best regards

RubenKelevra commented on 2015-08-02 16:17 (UTC)

Well, I think in the future I'll have more time to spend it in this package.

schimicata commented on 2015-08-02 10:46 (UTC)

I adopted this package just to import it into aur4. I have not much time to update this package. So if you have more time for that, write to me and I'll disown it.

RubenKelevra commented on 2015-05-22 18:20 (UTC)

Thanks for the hint, I gonna look into the new version at the weekend. :)

KlipperKyle commented on 2015-05-22 01:32 (UTC)

1.5.6 is out. I was able to build a package by just changing the version number. However, pacman dumped a lot of permissions warnings when I upgraded an existing installation from 1.5.2 to 1.5.6. Also, I opted for sqlite as the database, but I had to install it manually in /usr/share/webapps/etherpad-lite with $ cd /usr/share/webapps/etherpad-lite $ sudo -u etherpad npm install sqlite3 Otherwise, etherpad-lite complains and repeatedly restarts. Keep up the good work.

RubenKelevra commented on 2015-05-12 03:23 (UTC)

added npm as dependency.

RubenKelevra commented on 2015-04-15 04:55 (UTC)

@mjob Update was released some hours after my comment. I gonna look in your bugreport soon.

commented on 2015-04-14 15:51 (UTC)

/etc/webapps/etherpad-lite/settings.json should be owned by etherpad:etherpad and the world read permission should be removed

commented on 2015-04-14 15:31 (UTC)

@RubenKelevra Any news regarding the update?

RubenKelevra commented on 2015-04-08 16:21 (UTC)

This Package was flagged as outofdate today,update is running on a testsystem since some hours, I've releasing it soon.

RubenKelevra commented on 2015-02-22 02:32 (UTC)

added in v 1.5.1-3 a dependency which blocks a possible nodejs v0.13.x from being installed when it's available.

RubenKelevra commented on 2015-02-22 02:19 (UTC)

fixed it, thanks for your report dvzrv

dvzrv commented on 2015-02-16 09:41 (UTC)

Hmm, sadly this doesn't build with nodejs 0.12: "You're running a wrong version of node, or io.js is not installed. You're using v0.12.0, we need v0.8.x, v0.10.x or v0.11.x" (thrown by ./bin/ Have you tried though? Would it work?

RubenKelevra commented on 2015-02-07 16:07 (UTC)

Updating to 1.5.1, running in my productive installation for some hours stable.

RubenKelevra commented on 2015-01-16 19:39 (UTC)

Hey fordprefect, thanks again for you hint. Sorry for not releasing a new version, since I owe this package not that long many things are not solved as I would do. I need some Time to access this issues and ensure that I don't break older installations. Since a new version is released I have to update it anyway, so I gonna invest this time now. Best regards Ruben

fordprefect commented on 2014-10-31 16:51 (UTC)

i found the reason for the /etherpad file: in the install file line 8 you touch the apikey and etherpad. this looks like you wanted to change its owner or something…

RubenKelevra commented on 2014-10-30 17:24 (UTC)

Hey ford, Thanks for your hints, gonna look into this soon. Best regards Ruben

fordprefect commented on 2014-10-29 17:39 (UTC)

hi RubenKelevra thanks for caring for this package. at the moment you keep the config in /usr/webapps directory. i feel uneasy about this, as /usr should not contain config and other mutable data (like dbs, which are here stored in /var/lib afais). how about adding a config dir in /etc/webapps as several other webapps do and link to that from /usr/share/webapps? i would like that much more. please share your opinion about that and keep up the good work! ford (during the build or installation there was a file /etherpad showing up in / directory, which was not owned by the package. i didnt look into it, but is this some unwanted side-effect?)

RubenKelevra commented on 2014-10-26 11:26 (UTC)

1.4.1-2 released: -fix npm 2.x bug with patch from official repo, thanks to Mic92 -fix python2/3 bug, thanks to linkmauve -add Restart=always to [service] section, thanks to therp If you discover any other issue, just let me know.

RubenKelevra commented on 2014-10-24 17:43 (UTC)

Hey! This package just got adopted from me, gonna release a new version which fixes the problems soon. Best regards.

commented on 2014-10-03 04:08 (UTC)

Its been 2 weeks since flagged out-of-date. Will this package ever be updated?

linkmauve commented on 2014-09-28 16:26 (UTC)

Also, you should add an “export PYTHON=python2” before running, so it won’t fail at building some modules.

linkmauve commented on 2014-09-28 15:51 (UTC)

Additionally, even after having fixed the build with Mic92’s patch, when I run /usr/share/webapps/etherpad-lite/bin/ it tries to compile stuff in /usr/share/webapps/etherpad-lite, which is obviously going to fail.

Mic92 commented on 2014-09-27 17:24 (UTC)

The upstream fix for npm version is just a modification of the install script:

commented on 2014-09-19 21:17 (UTC)

Same here. The build still fails with "You're running a wrong version of npm, you're using 2.0.0, we need 1.x". Can this be fixed with this package or is it an upstream issue? On AUR, can we create an appropriate nodejs version for this package?

commented on 2014-09-16 12:39 (UTC)

build fails "You're running a wrong version of npm, you're using 2.0.0, we need 1.x" ..I thought nodejs v0.10 is supported ..maybe nodejs 0.10.31-5 is to new?

therp commented on 2014-06-21 19:31 (UTC)

As Siosm pointed out, chown -R etherpad:etherpad /usr/share/webapps/etherpad-lite is required in post_install. Also please add Restart=always to the [Service] section of the .service file. etherpad is inherently unstable and it just a bit of a PITA to always manually restart it. Thanks for the great package! :)

Siosm commented on 2014-01-13 22:19 (UTC)

Updated PKGBUILD ( with the following fixes: * Use a tmpfile.d config instead of manually creating and fixing /var/run/... I'm not sure this is even required anymore, the directory remains empty in my installation ; * Use /var/lib/etherpad as home dir & runtime dir ; * Fix install script, links /usr/share/webapps/etherpad-lite/var/ to /var/lib/etherpad ; * Added sqlite support by default ; * I have not found yet how to fully run this with /usr/share/webapps/etherpad-lite read only : the first time, I have to chown -R etherpad the folder and from then on, it works when I chown root:root the folder back and restart.

RubenKelevra commented on 2013-12-26 16:20 (UTC)

change line ExecStartPre=-/usr/bin/mkdir /var/run/etherpad-lite to ExecStartPre=-/usr/bin/mkdir -p /var/run/etherpad-lite in etherpad-lite.service

RubenKelevra commented on 2013-12-17 14:19 (UTC)

Please ask such questions in the newbe corner of the forum. Its a service, so start it as it is.

71GA commented on 2013-12-17 12:13 (UTC)

How do I start etherpad after install? etherpad nor etherpad-lite is working.

RubenKelevra commented on 2013-11-21 15:03 (UTC)

Still missing the patch for npm: Please patch file[1] line var python = gyp.opts.python || process.env.PYTHON || 'python' to var python = gyp.opts.python || process.env.PYTHON || 'python2' Causing trouble with gyp, see [2]. [1] /usr/share/webapps/etherpad-lite/src/node_modules/npm/node_modules/node-gyp/lib/configure.js [2]

onny commented on 2013-11-06 15:22 (UTC)

@RubenKelevra: Sorry for that. In the future I'll be more careful. @vkvn: Folder will be now created via systemd, so try again!

vimalkvn commented on 2013-11-05 01:29 (UTC)

Plugin manager (http://localhost:9001/admin/plugins) fails with this error message Error: ENOENT, open '/var/run/etherpad-lite/.npm/-/all/.cache.json' I had to do the following: mkdir /var/run/etherpad-lite chown -R etherpad.etherpad /var/run/etherpad-lite

RubenKelevra commented on 2013-10-13 09:16 (UTC)

My Settings.json is also deleted, THANK YOU!

RubenKelevra commented on 2013-10-13 09:11 (UTC)

WHY THE HECK IS THE PAD NOW IN /usr/share/webapps/ NOT IN /usr/share/webapps/etherpad-lite???

RubenKelevra commented on 2013-09-19 01:33 (UTC)

/usr/share/webapps/etherpad-lite/var need to be writeable

RubenKelevra commented on 2013-09-18 23:36 (UTC)

Dependency is python2 not python.

RubenKelevra commented on 2013-09-18 23:36 (UTC)

Please patch file[1] line var python = gyp.opts.python || process.env.PYTHON || 'python' to var python = gyp.opts.python || process.env.PYTHON || 'python2' Causing trouble with gyp, see [2]. [1] /usr/share/webapps/etherpad-lite/src/node_modules/npm/node_modules/node-gyp/lib/configure.js [2]

RubenKelevra commented on 2013-09-18 23:27 (UTC)

The folder /usr/share/webapps/etherpad-lite/node_modules should be writeable for installing plugins. http as user is a bad idea, because etherpad adds .npm and tmp to the homefolder and download files there. Etherpad should be run with its own useraccount, like 'etherpad'.

senorsmile commented on 2013-07-17 21:34 (UTC)

Download link is not functioning (getting 503 Service Unavailable)

ogasser commented on 2013-07-02 22:42 (UTC)

New pkgrel=4 with fullver=4ceb2c2 is out. sha512sums need updates. Additionally I had to replace ${_fullver:1} with ${_fullver} to make it work for me. Please check or explain your rationale.

onny commented on 2013-03-15 21:15 (UTC)

Sorry, but I can not reproduce your problem. When extracting the etherpad-lite source package with unzip, the .sh installation file has the following permissions: -rwxr-xr-x 1 onny onny 2961 Mar 6 15:17 This is also the case when using makepkg.

thomas.oster commented on 2013-03-15 18:50 (UTC)

Please change the file, so that it runs "chmod +x" on the .sh files. Right now they can not be executed and the installation fails. I can help if you need.