ok fixed it by removing wifite2-git and python-argparse
Search Criteria
Package Details: bottles 2:51.21-2
Package Actions
Git Clone URL: | https://aur.archlinux.org/bottles.git (read-only, click to copy) |
---|---|
Package Base: | bottles |
Description: | Easily manage wine and proton prefix |
Upstream URL: | https://github.com/bottlesdevs/Bottles |
Keywords: | Bottles gaming Wine Wineprefixes |
Licenses: | GPL-3.0-only |
Submitter: | ragouel |
Maintainer: | lotation (brombinmirko, francescomasala) |
Last Packager: | lotation |
Votes: | 156 |
Popularity: | 2.53 |
First Submitted: | 2020-11-28 22:52 (UTC) |
Last Updated: | 2025-03-31 08:34 (UTC) |
Dependencies (37)
- cabextract
- dconf
- gtk4 (gtk4-paper-planeAUR, gtk4-gitAUR)
- gtksourceview5 (gtksourceview-gitAUR)
- hicolor-icon-theme (hicolor-icon-theme-gitAUR)
- icoextractAUR
- imagemagick (imagemagick-gitAUR, imagemagick-full-gitAUR, imagemagick-fullAUR)
- libadwaita (libadwaita-gitAUR, libadwaita-without-adwaita-gitAUR)
- libportal-gtk4
- p7zip (p7zip-natspecAUR, p7zip-full-binAUR, 7zip)
- patoolAUR (patool-gitAUR)
- python (python37AUR, python311AUR, python310AUR)
- python-chardet
- python-fvsAUR
- python-gobject
- python-markdown
- python-orjson (python-orjson-gitAUR)
- python-pathvalidateAUR
- python-pycurl
- python-requests
- Show 17 more dependencies...
Required by (2)
- arch-gaming-meta (optional)
- cartridges-git (optional)
Sources (2)
Latest Comments
« First ‹ Previous 1 .. 10 11 12 13 14 15 16 17 18 19 20 .. 27 Next › Last »
frankenstein20 commented on 2023-03-03 22:31 (UTC)
RAMChYLD commented on 2023-02-28 19:54 (UTC) (edited on 2023-02-28 19:55 (UTC) by RAMChYLD)
@aag @bms yep, removing python-argparse (and python-pyclip which is for some reason dependent on python-argparse) worked. The error went away. Very strange...
bms commented on 2023-02-28 16:34 (UTC)
Try removing the python-argparse package if you hit the same issue as I did, as it breaks the import from standard library.
Hmm. That's the winner. Thanks.
aag commented on 2023-02-28 16:12 (UTC)
Try removing the python-argparse package if you hit the same issue as I did, as it breaks the import from standard library.
bms commented on 2023-02-28 13:47 (UTC)
@RAMChYLD Yup, see https://aur.archlinux.org/packages/bottles?all_deps=1&O=10#comment-895476 and follow-ups.
The issue actually occurs a bit before that error in the blueprint-compiler step it seems. That step should generate the missing file(s). I tried meson-git and blueprint-compiler-git to no effect.
Looking at the source, I see nothing wrong in how the blueprint compiler is being called, but you should be seeing an output a bit above that that hints that the compiler was called with the wrong command line parameters. Not sure though. Also no clue why it doesn't fail until later and don't really know meson...
Either way, the issue apparently started when Bottles converted to using blueprints sometime last year, but the issue may be local to our installed python packages somehow. I installed an earlier version for the time being (tag from August last year works for me).
RAMChYLD commented on 2023-02-28 13:08 (UTC)
Latest version of Bottles is giving me the following error during makepkg:
[53/55] Generating bottles/frontend/ui/bottles_gresource with a custom command
FAILED: bottles/frontend/ui/bottles.gresource
/usr/bin/glib-compile-resources ../bottles/frontend/ui/bottles.gresource.xml --sourcedir bottles/frontend/ui --sourcedir ../bottles/frontend/ui --internal --generate --target bottles/frontend/ui/bottles.gresource --dependency-file bottles/frontend/ui/bottles.gresource.d
../bottles/frontend/ui/bottles.gresource.xml: Failed to locate “window.ui” in any source directory.
I see that this was an issue in bottles-git three months ago but no solution was specified.
bms commented on 2023-02-28 10:42 (UTC)
@frankenstein20, @aag I'm also stuck on this one. The issue upstream also has no further details. Do you guys have any tips?
frankenstein20 commented on 2023-02-25 21:23 (UTC)
@aag a try with
pikaur -Qtdq | pikaur -Rns -
did not fix it for me
RAMChYLD commented on 2023-02-23 16:52 (UTC) (edited on 2023-02-23 16:56 (UTC) by RAMChYLD)
Started experiencing an issue where bottles will fail to install certain dependencies if cabextract is 1.10. This is related to the winetricks bug https://github.com/Winetricks/winetricks/issues/2023 . A fix has been proposed in https://github.com/Winetricks/winetricks/pull/2025 . However, when I communicated with the devs of Bottles, they have told me that they will not implement a fix as they prioritize the flatpak which ships with cabextract 1.9.1 and have no plans to move on to a newer version of cabextract anytime soon (https://github.com/bottlesdevs/Bottles/issues/2720)
I have managed to create a workaround by editing the cabextract.py file to include the new command, but this will break compatibility for those who're still using the older version of cabextract for whatever reason.
My diff containing my fix is as follows:
--- cabextract.py.orig 2023-02-23 23:30:45.135410676 +0800
+++ cabextract.py 2023-02-24 00:41:38.806568026 +0800
@@ -80,6 +80,7 @@
command = [
self.cabextract_bin,
+ f"--keep-symlinks",
f"-F '*{file}*'",
f"-d {self.destination}",
f"-q {self.path}"
@@ -98,6 +99,7 @@
else:
command = [
self.cabextract_bin,
+ f"--keep-symlinks",
f"-d {self.destination}",
f"-q {self.path}"
]
As I'm not very well versed in Python as I wish I could be, I hope that someone can create a proper patch that allows the cabextract library to detect the version of cabextract installed and add the new switch if necessary.
aag commented on 2023-02-22 16:31 (UTC)
@frankenstein20 Fyi: I managed to solve this by cleaning up some unused python modules and stray files from site-packages. Build is okay for me now.
Pinned Comments
brombinmirko commented on 2022-09-15 20:54 (UTC) (edited on 2022-09-15 20:54 (UTC) by brombinmirko)
=====================
READ HERE FIRST
=====================
This package is not officially supported by the Bottles Developers. Even though some of those developers are package maintainers, support is offered by the package authors who will make sure it is handled in the best possible way. They will diagnose the issues and report the issues to the development team if they are not related to the package.