I am attemping to install Blockbench from AUR, using the command seen below, but for some reason it’s conflicting with Electron, which is listed as a dependency. I read through the official Arch documentation detailing the issue, but either did not understand it or it was of no help. Does anyone have an idea for what to do to fix it?
[frost@Frost ~]$ yay -S blockbench AUR Explicit (1): blockbench-4.7.4-1 :: PKGBUILD up to date, skipping download: blockbench 1 blockbench (Build Files Exist) ==> Packages to cleanBuild? ==> [N]one [A]ll [Ab]ort [I]nstalled [No]tInstalled or (1 2 3, 1-3, ^4) ==> n 1 blockbench (Build Files Exist) ==> Diffs to show? ==> [N]one [A]ll [Ab]ort [I]nstalled [No]tInstalled or (1 2 3, 1-3, ^4) ==> n ==> Making package: blockbench 4.7.4-1 (Mon Jun 19 16:28:04 2023) ==> Retrieving sources... -> Updating blockbench git repo... -> Found blockbench.desktop ==> Validating source files with sha256sums... blockbench ... Skipped blockbench.desktop ... Passed :: (1/1) Parsing SRCINFO: blockbench ==> Making package: blockbench 4.7.4-1 (Mon Jun 19 16:28:05 2023) ==> Checking runtime dependencies... ==> Checking buildtime dependencies... ==> Retrieving sources... -> Updating blockbench git repo... -> Found blockbench.desktop ==> Validating source files with sha256sums... blockbench ... Skipped blockbench.desktop ... Passed ==> Removing existing $srcdir/ directory... ==> Extracting sources... -> Creating working copy of blockbench git repo... Klonowanie do „blockbench”... gotowe. Przełączono na nową gałąź „makepkg” ==> Starting prepare()... npm WARN old lockfile npm WARN old lockfile The package-lock.json file was created with an old version of npm, npm WARN old lockfile so supplemental metadata must be fetched from the registry. npm WARN old lockfile npm WARN old lockfile This is a one-time fix-up, please be patient... npm WARN old lockfile npm WARN deprecated email@example.com: This package has been deprecated and is no longer maintained. Please use @rollup/plugin-terser npm WARN deprecated firstname.lastname@example.org: Please use @jridgewell/sourcemap-codec instead npm WARN deprecated email@example.com: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797) npm WARN deprecated firstname.lastname@example.org: Please use @electron/asar moving forward. There is no API change, just a package name change npm WARN deprecated email@example.com: Please use @electron/notarize moving forward. There is no API change, just a package name change npm WARN deprecated firstname.lastname@example.org: Please use @electron/osx-sign moving forward. Be aware the API is slightly different > Blockbench@4.7.4 prepublish > npm run bundle && npm run pwa > Blockbench@4.7.4 bundle > webpack --config webpack.config.js asset bundle.js 1.87 MiB [compared for emit] [minimized] (name: main) orphan modules 1.67 MiB [orphan] 25 modules ./src/index.js + 25 modules 1.67 MiB [built] [code generated] webpack 5.74.0 compiled successfully in 578 ms > Blockbench@4.7.4 pwa > node ./scripts/generate_pwa.js Generated service-worker, which will precache 168 files, totaling 8.97 MB. added 631 packages, and audited 632 packages in 13s 81 packages are looking for funding run `npm fund` for details 9 high severity vulnerabilities To address issues that do not require attention, run: npm audit fix To address all issues (including breaking changes), run: npm audit fix --force Run `npm audit` for details. ==> Sources are ready. -> blockbench-4.7.4-1 already made -- skipping build ==> Making package: blockbench 4.7.4-1 (Mon Jun 19 16:28:20 2023) ==> Checking runtime dependencies... ==> Checking buildtime dependencies... ==> WARNING: Using existing $srcdir/ tree ==> Sources are ready. [sudo] password for frost: loading packages... resolving dependencies... looking for conflicting packages... Package (1) New Version Net Change blockbench 4.7.4-1 16.06 MiB Total Installed Size: 16.06 MiB :: Proceed with installation? [Y/n] y (1/1) checking keys in keyring (1/1) checking package integrity (1/1) loading package files (1/1) checking for file conflicts error: failed to commit transaction (conflicting files) blockbench: /usr/lib/electron exists in filesystem (owned by electron) Errors occurred, no packages were upgraded. -> error installing: [/home/frost/.cache/yay/blockbench/blockbench-4.7.4-1-x86_64.pkg.tar.zst] - exit status 1