Package Details: lutris-git 0.5.17.r1.ge8bfc73bb-1

Git Clone URL: https://aur.archlinux.org/lutris-git.git (read-only, click to copy)
Package Base: lutris-git
Description: Open Gaming Platform
Upstream URL: https://lutris.net
Licenses: GPL-3.0-or-later
Conflicts: lutris
Provides: lutris
Submitter: ProfessorKaos64
Maintainer: yochananmarqos
Last Packager: yochananmarqos
Votes: 39
Popularity: 0.37
First Submitted: 2017-12-17 21:07 (UTC)
Last Updated: 2024-05-01 14:30 (UTC)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 .. 12 Next › Last »

yochananmarqos commented on 2023-11-10 01:03 (UTC)

The issue is fixed with python-pillow 10.1.0-2 currently in Extra-Testing. I'm sure it will land in Extra soon.

maintuner commented on 2023-11-09 23:35 (UTC)

temporarily solution for using lutris, run the following command:

sudo ln -s /usr/lib/libimagequant.so.0.0.4 /usr/lib/libimagequant.so.0

yochananmarqos commented on 2023-11-09 22:28 (UTC) (edited on 2023-11-09 22:32 (UTC) by yochananmarqos)

@niso: Do not rename libraries. Either rebuild python-pillow yourself or wait until the maintainer fixes it. I've created a bug report: FS#80210

niso commented on 2023-11-09 21:58 (UTC)

Package won't build: "ImportError: libimagequant.so.0: cannot open shared object file: No such file or directory." Newest update of libimagequant renames libimagequant.so.0 to libimagequant.so.0.0.4. After renaming back to libimagequant.so.0 builds and works fine.

italoghost commented on 2023-11-01 01:53 (UTC)

Hi! Is there any reason to add xterm to the checkdepends?

yochananmarqos commented on 2023-10-16 22:57 (UTC) (edited on 2023-10-16 23:00 (UTC) by yochananmarqos)

@tomsk: Please do not paste logs here--especially with no formatting. None can read that.

See Pacman Troubleshooting: "Failed to commit transaction (conflicting files)" error

tomsk commented on 2023-10-16 08:32 (UTC) (edited on 2023-10-24 14:09 (UTC) by tomsk)

Cannot update it anymore: https://pastebin.com/raw/AF8BZNVe

yochananmarqos commented on 2023-10-08 00:14 (UTC)

@solarisfire: It's fixed now with the latest upstream commits.

solarisfire commented on 2023-10-06 21:01 (UTC)

Ah it's upstream, someone borked one of their translation files.