@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?
Search Criteria
Package Details: etherpad-lite 1:2.2.7-1
Package Actions
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: | https://etherpad.org |
Licenses: | Apache |
Conflicts: | etherpad-lite-git |
Submitter: | onny |
Maintainer: | None |
Last Packager: | iamawacko |
Votes: | 29 |
Popularity: | 0.000082 |
First Submitted: | 2013-03-15 15:10 (UTC) |
Last Updated: | 2024-12-25 23:12 (UTC) |
Dependencies (12)
- coffeescript (coffeescript-gitAUR)
- libsecret-1.so (libsecret)
- nodejs (nodejs-gitAUR, nodejs6-binAUR, python-nodejs-wheelAUR, nodejs-lts-hydrogen, nodejs-lts-iron, nodejs-lts-jod)
- pnpm (yarn-pnpm-corepackAUR, corepackerAUR, pnpm-binAUR)
- npm (corepackerAUR, nodejs6-binAUR, python-nodejs-wheelAUR) (make)
- pnpm (yarn-pnpm-corepackAUR, corepackerAUR, pnpm-binAUR) (make)
- abiword (abiword-gitAUR) (optional) – advanced import/export of pads
- libreoffice (libreoffice-dev-binAUR, libreoffice-fresh, libreoffice-still) (optional) – advanced import/export of pads
- mariadb (mysql55AUR, mysql56AUR, mysql81AUR, mysql57AUR, mysqlAUR, mysql80AUR, mariadb-lts, percona-server) (optional) – to use mariadb as database
- postgresql (postgresql-12AUR, postgresql17-docsAUR, postgresql17AUR, postgresql13AUR, postgresql-gitAUR, postgresql16-docsAUR, postgresql16AUR, postgresql15-docsAUR, postgresql15AUR) (optional) – to use postgresql as database
- sqlite (sqlite-fossilAUR) (optional) – to use sqlite as databse
- tidy (tidy-html5-gitAUR) (optional) – improve quality of exported pads
Required by (0)
Sources (4)
Latest Comments
« First ‹ Previous 1 .. 4 5 6 7 8 9 10 11 12 13 14 .. 16 Next › Last »
dosenpils commented on 2015-12-01 12:40 (UTC)
dvzrv commented on 2015-12-01 00:07 (UTC)
@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.
dosenpils commented on 2015-11-26 14:08 (UTC) (edited on 2015-11-26 15:12 (UTC) by dosenpils)
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
dosenpils commented on 2015-11-26 12:58 (UTC)
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 (UTC)
@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 (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.
<deleted-account> 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.
https://github.com/nodejs/node/commit/c245a199a7
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.
Pinned Comments