Arch Linux User Repository

Yeah the reason I specified -C is because I wanted to be sure the src directory is clean.

-c only works if you:

• specified it the last time you build the package
• the last build of the package was successful

@SibrenVasse

I did it even better.

I use git clean -ffdxi and then option "4: ask each" in which git let's you exactly walk through everything which does not belong to the repo. :)

The "src" directory is the thing that I removed. I always prefer to keep some existing ".pkg.tar.zst" files around just like I also maintain some regular pacman cache.

Generally I also build using makepkg -csi. Maybe the C is the better way to do it, if it does the exact thing (explanation in man page is for option '-C' versus '-c' is very different however).

However, making a fresh new git clone of this repo into some other directory and trying to build that gives the same error for me.

I have reinstalled ArchLinux. There was definitely no cache nowhere messing anything up.

I can't seem to reproduce your issue. Have you tried buiding the package manually with makepkg -C (capital C)?

Because my build system on github also had no issue. https://github.com/SibrenVasse/deezer/releases/tag/v5.30.580

I am seeing the same error message as @jongeduard

Build fails with an error for me (sorry some texts are in Dutch because I have my system setup as NL language):

==> Bezig met het uitvoeren van prepare()...
build/main.js 299ms
build/preload.js 45ms
build/renderer.js 28ms
build/service-worker.js 1ms
build/titlebar.js 16ms
Applying patch remove-kernel-version-from-user-agent.patch...
patching file build/main.js
patching file build/preload.js
patching file build/renderer.js
patching file build/titlebar.js
Applying patch avoid-change-default-texthtml-mime-type.patch...
patching file build/main.js
Hunk #1 FAILED at 2897.
1 out of 1 hunk FAILED -- saving rejects to file build/main.js.rej
==> FOUT: Er is een fout opgetreden in prepare().
    Afbreken...

I see that the file which the above message about rejects refers to sits in "src/resources/app/build/" and contains the following content:

--- build/main.js
+++ build/main.js
@@ -2897,12 +2897,7 @@
                 this.tray.init(),
                 this.updater.init(),
                 this.network.watch(),
-                this.powerSave.check(),
-                this.deepLink.getSchemes().forEach((scheme) => {
-                  external_electron_namespaceObject.app.setAsDefaultProtocolClient(
-                    scheme
-                  );
-                });
+                this.powerSave.check();
               const dzrFilter = { urls: ["*://*/*"] },
                 DOMAINS_WHITELIST = [
                   "deezer.com",

@CReimer: yeah electron13 is no longer supported unfortunately. The official windows version is shipped with electron12 (also unsupported). I was able to update their app to electron13, but beyond that the changes are very extensive.

So I'd say: at worst it's no more insecure as the official version.

Isn't it a security risk to use Electron 13?

PSA: If you encounter any issues or you see something like the following error when starting Deezer on the cli:

/usr/lib/electron13/electron: error while loading shared libraries: libicui18n.so.71: cannot open shared object file: No such file or directory

Please make sure to install electron13-bin instead of electron13.

msrd0: Unfortunately not. Deezer is distributed with Electron v12. To fix the breaking changes with electron 14 (electron/remote) it would require to include a full electron install in this package (similar installing a binary package, but even more against how arch does things!)