| Git Clone URL: | https://aur.archlinux.org/collabora-online-server-nodocker.git (read-only) |
|---|---|
| Package Base: | collabora-online-server-nodocker |
| Description: | Collabora CODE (LibreOffice Online) server for Nextcloud or ownCloud, without Docker |
| Upstream URL: | https://www.collaboraoffice.com/code/ |
| Licenses: | |
| Provides: | |
| Submitter: | theYinYeti |
| Maintainer: | theYinYeti |
| Last Packager: | theYinYeti |
| Votes: | 5 |
| Popularity: | 0.928500 |
| First Submitted: | 2017-10-13 20:12 |
| Last Updated: | 2018-12-20 21:20 |
@HLFH, thanks for notifying me, and sorry for not updating sooner: I’ve had a couple of problems to handle… @9-r, I tried to answer your email, but got rejected:
host mx1.worldserver.net[217.13.200.31] said: 550 5.7.1
<…9-r…>: Recipient address rejected: Ask your Mail/DNS-Administrator
to correct HELO and DNS MX settings or to get removed from DNSBLs
(Blacklists)!
I wanted to thank you for your help. Happy Christmas
I flagged this package out of date because 3.4.1 is available. Still, changing only the version line of PKGBUILD is maybe not enough to make it work with Nextcloud 14.
@theYinYeti curl was installed. i am using ubuntu in that container now and installed it by manually following all steps from the docker-file.
sad, but it works now
flower: the only explanation I have would be, that makepkg is unable to find the curl command, which it needs. I will add curl as a make-dependency.
Hello, thank you very much for this package. I have a problem installing it though. Whenever i run i get: "Unknown dependency: loolwsd"
the deb loolwsd_3.3.1-3_amd64.deb is downloaded and extracted though. any hints?
About upstream: 1º Upstream does not maintain past versions of packages, so I have no choice but to follow new releases. 2º Upstream does not advertise minor/patch releases. These are the reasons why the PKGBUILD is made to adapt itself the best it can to the current upstream situation, whatever it is. If an incompatible change occurs, do not hesitate to mark the package as “obsolete”: I will get notified, and fix the the package as soon as my free time allows. Cheers :-)
Oh, I just realize that the bind that is attempted is not so “obviously” wrong. It does look like an IP address after all. But if 2.0.38.25* are indeed addresses of yours, they are probably the wrong choice nonetheless: loolwsd is rather expected to bind to an IP address from a private range (eg. 10.0.0.10), if not 127.0.0.1, and be accessed through Nginx.
Please provide a paste of your config file, so that we can debug your situation :-)
x-f: I must say I have never seen this error. Have you followed the steps in https://wiki.archlinux.org/index.php/Nextcloud#Collabora_Online_Office_integration ? Your loolwsd seems to try and bind a number (a version?) that is obviously not a valid value. Probably something is wrong with the config file. Could you pastebin it somewhere?
I try to get collabora running, but it fails to start via systemd
Starting by hand:
sudo -u lool /usr/bin/loolwsd --version --o:sys_template_path=/opt/lool/systemplate --o:lo_template_path=/opt/collaboraoffice5.3 --o:child_root_path=/opt/lool/child-roots --o:file_server_root_path=/usr/share/loolwsd
/usr/bin/loolwsd: Symbol `_ZTIN4Poco3Net4Impl17SocketAddressImplE' has different size in shared object, consider re-linking
wsd-18214-18214 16:43:48.641633 [ loolwsd ] WRN SSL support: SSL is disabled.| wsd/LOOLWSD.cpp:744
wsd-18214-18214 16:43:48.645078 [ loolwsd ] ERR Failed to bind to: 2.0.38.253:0 (errno: Address family not supported by protocol)| wsd/LOOLWSD.cpp:2460
wsd-18214-18214 16:43:48.645233 [ loolwsd ] ERR Failed to bind to: 2.0.38.254:0 (errno: Address family not supported by protocol)| wsd/LOOLWSD.cpp:2460
wsd-18214-18214 16:43:48.645252 [ loolwsd ] ERR Failed to bind to: 2.0.38.255:0 (errno: Address family not supported by protocol)| wsd/LOOLWSD.cpp:2460
-> I compared the setting with a working Debian instance. SSL is disabled and i want to use a nginx proxy
Tried different settings for server name and port. but it crashes always and the port is closed and unused.
Pinned Comments
theYinYeti commented on 2018-01-04 08:33
About upstream: 1º Upstream does not maintain past versions of packages, so I have no choice but to follow new releases. 2º Upstream does not advertise minor/patch releases. These are the reasons why the PKGBUILD is made to adapt itself the best it can to the current upstream situation, whatever it is. If an incompatible change occurs, do not hesitate to mark the package as “obsolete”: I will get notified, and fix the the package as soon as my free time allows. Cheers :-)