Arch Linux User Repository

@theo01 good catch!

it may be a good idea to report this upstream as well; the .deb release uses the same incorrectly-sized icons

Here is a version which fixes the incorrect icon size https://github.com/TheoBrigitte/ente-auth-bin

The current 128x128 and 256x256 icons have a size of 1024x1024 I fixed those by using : magick ente_auth.png -resize 128x128 icons/hicolor/128x128/apps/ente_auth.png magick ente_auth.png -resize 256x256 icons/hicolor/256x256/apps/ente_auth.png

Upgrading from versions v2.0.50-v3.0.17 (inclusive) to v3.1.1 (or newer) will require manual intervention. Please EITHER

• run [ "$(readlink /usr/lib/libsodium.so.23)" = "/usr/lib/libsodium.so" ] && sudo rm /usr/lib/libsodium.so.23 in a terminal before upgrading.
• uninstall ente-auth-bin and only then install the new version

This is needed because the symlink created in the previous version of this package will conflict with the file provided by the package libsodium-1.0.18 which is now a dependency. If such symlink is not removed, pacman will throw the following error:

error: failed to commit transaction (conflicting files)
libsodium-1.0.18: /usr/lib/libsodium.so.23 exists in filesystem

There is no way for me to make this seamless as every AUR helper will first install the package dependencies and then execute the commands in the PKGBUILD. This means that there is no way for me to reliably remove that symlink before libsodium-1.0.18 gets installed.

Good news is, now this should use the right version of the libsodium library, @yochananmarqos i hope this works for you now.

@nktnet thank you, added xdg-user-dirs as a dependency

@windy done, now the upsteam URL should point to the right release

For the error

ERROR:flutter/runtime/dart_vm_initializer.cc(41)] Unhandled Exception: PlatformException(Libsecret error, Failed to unlock the keyring, null, null

See this issue: - https://github.com/ente-io/ente/issues/2046

In short, install xdg-user-dirs, e.g.

yay -S xdg-user-dirs

@alessandroberna: Symlinking libraries like that is absolutely wrong. They're versioned for a reason. Upstream making the same mistake is no justification.

Good news is, upstream is listening to community feedback. Eventually they'll figure it out.

Hi, thank you very much for maintaining this packages.

One suggestion: Could you use the version number variable in the download URL? This would make the diff easier to read. Thank you!

The package is still incorrectly symlinking libsodium.so.23 to libsodium.so.26, with only the version having been bumped.

Due to ongoing university exams, I won't have much time to look into this for about a month. The fix isn't trivial, as I can't make pacman remove the symlink /usr/lib/libsodium.so.23 before the new dependency (libsodium-1.0.18) gets installed. This causes pacman to error out, since the shared object is already present during installation. In order for that to work, manual intervention would be required: either uninstalling the package before reinstalling, or manually removing /usr/lib/libsodium.so.23.

This would not be a seamless upgrade, and I'd prefer to fix it differently. It might make more sense to report the issue upstream, as the developers now seem interested in building for Arch-based distros too. They're currently using the same symlink hack for their Arch builds (see https://github.com/ente-io/ente/blob/80d5d7e44e7ea7956490989c44c11d7e358037fa/auth/linux/packaging/pacman/make_config.yaml).

If they update their Arch build to depend on the newer libsodium, it would be enough to just remove the symlink post-upgrade to fix everything, without needing to install the older libsodium and somehow remove the existing symlinked libsodium.so.23

@yochananmarqos I said that I WILL edit the PKGBUILD and make the package depend on libsodium-1.0.18 (and remove that symlink, in case it was not clear)

I was just discussing the fix, I never said that the package is ok in its current state.

I will update this as soon as I can, thank you for your report and I apologize for the poor quality PKGBUILD

@alessandroberna: Okay...so why doesn't this package depend on libsodium-1.0.18, then? Apparently it doesn't work if you're creating incompatible symlinks to "fix" things.