Arch Linux User Repository

I had some issues building 1.7.27 but succeeded after adding the following to the prepare section

For anyone adopting this package: I did something very similar in my private fork and can confirm this works, so I'd suggest patching this until it's fixed upstream instead of setting nodejs<16.

I have moved on from manjaro to NixOS, so I'm disowning this package again. Thank you for the recent comments.

I had some issues building 1.7.27 but succeeded after adding the following to the prepare section:

   cd ../element-desktop
   # Switch target to output to directory rather than .deb package
   sed -i 's/"target": "deb"/"target": "dir"/g' package.json
   sed -i 's@"https://packages.riot.im/desktop/update/"@null@g' element.io/release/config.json
+  sed -i '/seshat/s/"2.2.3"/"2.2.4"/' package.json
+  sed -i '/electron-builder/s/"22.10.5"/"22.11.4"/g' package.json
   yarn install

see upstream reports:

• https://github.com/matrix-org/seshat/issues/81
• https://github.com/electron-userland/electron-builder/issues/5668

As some npm dependencies are not yet compatible with NodeJS 16 you might wanna set the nodejs dependency to

nodejs<16

I have adopted this package and it will now follow the upstream 'develop' branch. With recent changes it's now based on electron version 12 with native Wayland compatibility. Start with the following flags to test it:

element-desktop --enable-features=UseOzonePlatform --ozone-platform=wayland

Unfortunately, I have to withdraw from the maintenance of this package for private reasons. Feel free to adopt.

You don't have to update it every time there is a new commit, makepkg will automatically get the latest commit and create a package for that commit, this is actually less work than what you are doing now.

You should read all of the VCS package guidelines and this note about the difference between -git and normal packages

@SeerLite

Maybe you should consider changing it so it does either way.

If this is the case I would have to disown the package because, like many of us, I do the whole thing in my spare time and therefore cannot provide every single commit as an update.

@jaltek Oh, looks like I never came across that guideline, I only read the PKGBUILD wiki page. I had no idea the replaces field could be ignored in VCS packages. Now that I see it I think it makes sense though.

It also doesn't say anything about -git packages having to pull from the last commit, and in fact even explains how to fix the source on a specific commit. But I found this section in the AUR wiki page that gives the impression that -git packages are indeed meant to build from the latest.

Oh and now I also found this! (See the first point). AFAICT this package doesn't really patch or add anything that the official binary package doesn't do already, right? (except for RC versions, which are not the majority of versions) That means it's not complying with the first rule (unless I missed something or the RC versions do indeed work around that). Making it pull from the latest commit would effectively solve that.

And even if it turns out the package is fine, I'm pretty sure most people expect a -git package to have the latest developments of the package. Maybe you should consider changing it so it does either way.

@SeerLite: Thank you for your feedback. According to this guideline the replaces field should be avoided. And yes, this repo does not reflect every commit from the upstream repo. I have used @idanoo's commits as a guide here. So this repo reflects only the RC and stable releases. Maybe the -git is wrong then?