Arch Linux User Repository

This package is being renamed to collabora-office-bin.

Nothing is compiled here any more. The package unpacks a payload that is built ahead of time and published as a release asset, and Arch names a package like that with a -bin suffix. The contents are unchanged.

To move over, run one of:

yay -S collabora-office-bin
paru -S collabora-office-bin

The new package conflicts with this one, so your helper offers to remove collabora-office in the same step. There is no need to remove it first.

The new package is at 26.04.3.3.

I am filing a merge request into collabora-office-bin, so this page will redirect there once it is processed.

Updated to 26.04.2.4-1 and added back the poco dependency.

Looks like the latest two releases cant be build as the collabora-office-brand files are missing.

But can this be at least updated to 26.04.2.3 and reintroduce the poco dependency again ?

diff --git a/PKGBUILD b/PKGBUILD
index 3b6aff1..69e860f 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -1,8 +1,8 @@
 # Maintainer: Rashesh Padia
 pkgname=collabora-office
-pkgver=26.04.2.1
+pkgver=26.04.2.3
 pkgrel=1
-_source_tag=cp-26.04.2-1
+_source_tag=cp-26.04.2-3
 _source_dir=online.mirror-${_source_tag}
 pkgdesc='Collabora Office - Qt6 desktop document editor powered by Collabora Online'
 arch=('x86_64')
@@ -19,6 +19,7 @@ depends=(
     'libpng'
     'openssl'
     'pam'
+    'poco'
     'zlib'
     'zstd'
     'hicolor-icon-theme'
@@ -49,12 +50,12 @@ optdepends=(
 options=('!strip' '!debug')
 source=(
     "online-${_source_tag}.tar.gz::https://github.com/CollaboraOnline/online.mirror/archive/refs/tags/${_source_tag}.tar.gz"
-    "https://github.com/Rash419/collabora-core-assets/releases/download/cp-26.04.2-1/core-co-26.04-assets.tar.gz"
-    "https://www.collaboraoffice.com/downloads/collabora-office-brand/collabora-office-brand-26.04.2.1.tar.gz"
+    "https://github.com/Rash419/collabora-core-assets/releases/download/${_source_tag}/core-co-26.04-assets.tar.gz"
+    "https://www.collaboraoffice.com/downloads/collabora-office-brand/collabora-office-brand-${pkgver}.tar.gz"
 )
-sha256sums=('7701031ffd4736e55658dd371b2e42d9f0dc262628398536f0d3d960926cfdd5'
-            'fb91e40eaa52cbfc824f2a1d62b3f87093567284d1f22a5979415e0623afb6c8'
-            '321112b8f29d338ca9530dc604448c9eb465c4f9308468722f16a95fc6f830a8')
+sha256sums=('f51717b61714f27ad4d7c05695d7740b2ecce76581626934c447bb7189ff2091'
+            '72b5c75e5249344858efa5eca8881cbf01c046c64214c802dcb45ba38b83c0a5'
+            '2d0c9b407019d4744a57a2771ec42bf97685f082601e075237a04ee6c6b7e8e3')

 build() {
     cd "$_source_dir"

It looks like poco was accidentally removed from the depends array in the recent commit updating to 26.04.2.1. Since Collabora Online relies on POCO C++ libraries, clean chroot builds and installs on minimal systems fail without it. Could you please re-add 'poco' back to depends=(...)? Thanks.

@rash419 still needs poco as dependency

Hi @guiodic,

Feel free to report the bugs on https://github.com/CollaboraOnline/online/issues

Regards, Rashesh :)

edit: It seems AUR download the unpatched PKGBUILD. Now I try to change it on my local system

edit 2: It works after the fix.

Unfortunately, I have to say that the software is still a bit rough around the edges, but I hope it will improve in future releases.

@rash419

Now I receive the same error of Foer

checking for Poco/Net/WebSocket.h... no configure: error: header Poco/Net/WebSocket.h not found; build the engine first (POCO is built there) or install a system POCO

Hi guiodic,

Thanks for the report. Looks like npm 12 dropped the support for npm-shrink package json. I added a temporary fix to aur package. Let me know if it resolves the issue for you. I will also report it to upstream.

Regards, Rashesh

/run/media/guido/nvme1/linux/collabora-office/src/include/COKit/COKit.h:197:8: warning: type 'struct COKitDocumentClassStruct' violates the C++ One Definition Rule [-Wodr]
  197 | struct COKitDocumentClassStruct
      |        ^
/run/media/guido/nvme1/linux/collabora-office/src/include/COKit/COKit.h:197:8: note: a different type is defined in another translation unit
  197 | struct COKitDocumentClassStruct
      |        ^
/run/media/guido/nvme1/linux/collabora-office/src/include/COKit/COKit.h:213:11: note: the first difference of corresponding definitions is field 'getParts'
  213 |     int (getParts) (COKitDocument pThis);
      |           ^
/run/media/guido/nvme1/linux/collabora-office/src/include/COKit/COKit.h:197:8: note: a type with different number of fields is defined in another translation unit
  197 | struct COKitDocumentClassStruct
      |        ^
make[3]: uscita dalla directory «/run/media/guido/nvme1/linux/collabora-office/src/online.mirror-cp-26.04.2-1/qt»
make[2]: uscita dalla directory «/run/media/guido/nvme1/linux/collabora-office/src/online.mirror-cp-26.04.2-1/qt»
Making all in browser
make[2]: ingresso nella directory «/run/media/guido/nvme1/linux/collabora-office/src/online.mirror-cp-26.04.2-1/browser»
npm error code EUSAGE
npm error
npm error The npm ci command can only install with an existing
npm error package-lock.json with lockfileVersion >= 1. Run an install with npm@5
npm error or later to generate a package-lock.json file, then try again.
npm error
npm error Clean install a project
npm error
npm error Usage:
npm error npm ci
npm error
npm error Options:
npm error [--install-strategy <hoisted|nested|shallow|linked>] [--legacy-bundling]
npm error [--global-style] [--omit <dev|optional|peer> [--omit <dev|optional|peer> ...]]
npm error [--include <prod|dev|optional|peer> [--include <prod|dev|optional|peer> ...]]
npm error [--strict-peer-deps] [--foreground-scripts] [--ignore-scripts]
npm error [--allow-directory <all|none|root>] [--allow-file <all|none|root>]
npm error [--allow-git <all|none|root>] [--allow-remote <all|none|root>]
npm error [--allow-scripts <package-list> [--allow-scripts <package-list> ...]]
npm error [--strict-allow-scripts] [--dangerously-allow-all-scripts] [--no-audit]
npm error [--no-bin-links] [--no-fund] [--dry-run]
npm error [-w|--workspace <workspace-name> [-w|--workspace <workspace-name> ...]]
npm error [--workspaces] [--include-workspace-root] [--install-links]
npm error
npm error   --install-strategy
npm error     Sets the strategy for installing packages in node_modules.
npm error
npm error   --legacy-bundling
npm error     Instead of hoisting package installs in node_modules, install packages
npm error
npm error   --global-style
npm error     Only install direct dependencies in the top level node_modules,
npm error
npm error   --omit
npm error     Dependency types to omit from the installation tree on disk.
npm error
npm error   --include
npm error     Option that allows for defining which types of dependencies to install.
npm error
npm error   --strict-peer-deps
npm error     If set to true, and --legacy-peer-deps is not set, then any
npm error
npm error   --foreground-scripts
npm error     Run all build scripts (ie, preinstall, install, and
npm error
npm error   --ignore-scripts
npm error     If true, npm does not run scripts specified in package.json files.
npm error
npm error   --allow-directory
npm error     Limits the ability for npm to install dependencies from directories.
npm error
npm error   --allow-file
npm error     Limits the ability for npm to install dependencies from tarball files.
npm error
npm error   --allow-git
npm error     Limits the ability for npm to fetch dependencies from git references.
npm error
npm error   --allow-remote
npm error     Limits the ability for npm to fetch dependencies from urls.
npm error
npm error   --allow-scripts
npm error     Comma-separated list of packages whose install-time lifecycle scripts
npm error
npm error   --strict-allow-scripts
npm error     If true, turn the install-script policy from a warning into a hard
npm error
npm error   --dangerously-allow-all-scripts
npm error     If true, bypass the allowScripts policy entirely and run every
npm error
npm error   --audit
npm error     When "true" submit audit reports alongside the current npm command to the
npm error
npm error   --bin-links
npm error     Tells npm to create symlinks (or .cmd shims on Windows) for package
npm error
npm error   --fund
npm error     When "true" displays the message at the end of each npm install
npm error
npm error   --dry-run
npm error     Indicates that you don't want npm to make any changes and that it should