Arch Linux User Repository

!!!!!! THE PACKAGE CANNOT BE UPGRADED TO 2022.6.14 until libadwaita 1.2.0 is out.

I tried today and the libadwaita-git at the moment it doesn't works... I suggest, as now, if you wanted to build latest bottles, to try change this in /etc/makepkg.conf:

options([...] !check)

why package version says 2022.6.14 but source is hardcoded to 2022.5.28-trento-3 ?

Edited the PKGBuild to exclude wine and everything works. Wine should be an optional dependency.

@FabioLolix why not simply this? https://archlinux.org/packages/community/any/python-pefile/

Need to change from pefile to python-pefile, I've flagged python-pefile-git as OOD but it will be long; python-pefile-git use a 4 commit fork of pefile from 2017 and use git:// in source=() which is deprecated from github since April 2022

Need to remove Pefile from PKGBUILD and then it can be built... Pefile is outdated by 7 years... Unusable...

!!!!!! THE PACKAGE CANNOT BE UPGRADED TO 2022.6.14 until libadwaita 1.2.0 is out.

There's a HUGE build bug I've found. When it is trying to download the python-pefile-git dependency, git finds nothing on the specified URL, hangs, times out and then spits out an error message saying that it can't download the file.

What is the correct URL, so that I could fix the PKGBUILD for myself?

Edit: Here's the full error message:

error: timed out looking for devel update: git://github.com/stangelandcl/pefile

error: failed to lookup: python-pefile-git:

error: failed to download sources for 'python-pefile-git-r93.5958343-1':

@TechXero are you willing submit a request or just post the PKGBUILD on chat? @francescomasala are you watching this?

I was able to build after I manually removed python-pefile. pacman -Rdd python-pefile

I was able to build by removing libadwaita-git and pefile from dependends in PKGBUILD... So far no issues.. PKGBUILD needs to be updated..

Consider change from pefile to python-pefile

Fail again.

Am sticking to older version as this one will not work without libadwaita-git which fails to build for most of us...

Edit : And now another dependency is added that hasn't been updated since 2015 and broken.. WTH you doing maintainer ? Making sure Bottles is unusable ?

@CorvetteCole No, it does not run. With libadwaita bottles will report this error: AttributeError: 'gi.repository.Adw' object has no attribute 'EntryRow'.

Fail to build libadwaita-git, why git???

why does this require libadwaita-git? I don't want to compile and use the -git version of libadwaita. It seems to compile and run fine when using the normal libadwaita package

@FabioLolix Cannot build coz libawaita-git failing... How did you build libadwaita-git ? Am on KDE... FOr now I downgraded to previous version...

I get this https://pastebin.com/kyNtRTNJ

i have a problem with this build, bottles create config files in "local" instead of ".local"

@maher your problem is with libadwaita-git not bottles, I builded that fine today

(/home/maher/.cache/paru/clone/libadwaita-git/src/build/tests/test-leaflet:66161): Gtk-WARNING **: 23:17:32.369: Theme parser error: gtk.css:4685:21-28: Expected a valid color. ――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――

Summary of Failures:

3/37 test-avatar FAIL 1.40s killed by signal 5 SIGTRAP 4/37 test-header-bar FAIL 2.21s killed by signal 5 SIGTRAP 5/37 test-carousel-indicator-lines FAIL 2.49s killed by signal 5 SIGTRAP 6/37 test-password-entry-row FAIL 0.55s killed by signal 5 SIGTRAP 7/37 test-easing FAIL 3.24s killed by signal 5 SIGTRAP 8/37 test-preferences-page FAIL 0.63s killed by signal 5 SIGTRAP 9/37 test-action-row FAIL 3.88s killed by signal 5 SIGTRAP 10/37 test-preferences-row FAIL 0.65s killed by signal 5 SIGTRAP 11/37 test-combo-row FAIL 4.03s killed by signal 5 SIGTRAP 12/37 test-preferences-window FAIL 0.58s killed by signal 5 SIGTRAP 13/37 test-split-button FAIL 0.62s killed by signal 5 SIGTRAP 14/37 test-animation-target FAIL 4.55s killed by signal 5 SIGTRAP 15/37 test-squeezer FAIL 0.70s killed by signal 5 SIGTRAP 16/37 test-style-manager FAIL 0.68s killed by signal 5 SIGTRAP 17/37 test-status-page FAIL 0.76s killed by signal 5 SIGTRAP 18/37 test-animation FAIL 4.98s killed by signal 5 SIGTRAP 19/37 test-tab-bar FAIL 0.71s killed by signal 5 SIGTRAP 20/37 test-tab-view FAIL 0.69s killed by signal 5 SIGTRAP 21/37 test-expander-row FAIL 5.22s killed by signal 5 SIGTRAP 22/37 test-timed-animation FAIL 0.66s killed by signal 5 SIGTRAP 23/37 test-entry-row FAIL 5.34s killed by signal 5 SIGTRAP 24/37 test-toast FAIL 0.74s killed by signal 5 SIGTRAP 25/37 test-toast-overlay FAIL 0.73s killed by signal 5 SIGTRAP 26/37 test-view-switcher FAIL 0.74s killed by signal 5 SIGTRAP 27/37 test-view-switcher-bar FAIL 0.65s killed by signal 5 SIGTRAP 28/37 test-window FAIL 0.68s killed by signal 5 SIGTRAP 29/37 test-carousel FAIL 5.90s killed by signal 5 SIGTRAP 30/37 test-application-window FAIL 5.95s killed by signal 5 SIGTRAP 31/37 test-window-title FAIL 0.66s killed by signal 5 SIGTRAP 32/37 test-bin FAIL 6.19s killed by signal 5 SIGTRAP 33/37 test-flap FAIL 6.46s killed by signal 5 SIGTRAP 34/37 test-preferences-group FAIL 4.31s killed by signal 5 SIGTRAP 35/37 test-button-content FAIL 6.92s killed by signal 5 SIGTRAP 36/37 test-carousel-indicator-dots FAIL 7.43s killed by signal 5 SIGTRAP 37/37 test-leaflet FAIL 6.77s killed by signal 5 SIGTRAP

Ok: 2
Expected Fail: 0
Fail: 35
Unexpected Pass: 0
Skipped: 0
Timeout: 0

@FabioLolix: Ah, good point.

@brombinmirko: You can remove the pinned message, it hasn't been relevant for several months now.

@yochananmarqos when they bump the 'date' part of the pkgver (2022.5.14) which is higher then the 'codename' there is absolutely no need of epoch

@FabioLolix: The problem with that is if they choose a codename lower in the alphabet, then an epoch would have to be used. It would be better to just bump the pkgrel.

pkgname=bottles
pkgver=2022.5.14
pkgrel=5
_codename=trento
_pkgrel=3

source=("${pkgname}-${pkgver}-${_codename}-${_pkgrel}.tar.gz::https://github.com/bottlesdevs/Bottles/archive/${pkgver}-${_codename}-${_pkgrel}.tar.gz")

Since 'trento' is part of the pkgver you can use

_pkgver=2022.5.14-trento-2
pkgver=${_pkgver//-/.}

source=("${pkgname}-${pkgver}.tar.gz::https://github.com/bottlesdevs/Bottles/archive/${_pkgver}.tar.gz")

Test are not performed, you can add

checkdepends=(appstream-glib)

check () {
  ninja test -C "Bottles/build"
}

and are failing since this commit https://github.com/bottlesdevs/Bottles/commit/95b451d152c5a8609c2a46fd173514f2cbd6fb54

@gap30 patool is on the AUR and need to be build first, pacman don't deal with stuff and never will

Do I have to manually install wine before this install?

error: target not found: lib32-gnutls error: target not found: patool error: target not found: wine ==> ERROR: 'pacman' failed to install missing dependencies. ==> Missing dependencies: -> lib32-gnutls -> gtksourceview4 -> libhandy -> patool -> p7zip -> python-gobject -> wine -> cabextract -> webkit2gtk

If using Manjaro, please install libhandy-git as the one in their repository is not updated and Bottles need 1.6.

In the official repo there is already libhandy v1.6.1, so you have either an outdated system or you're on Manjaro

Can't update because of libhandy dependency > 1.4.

wine should not be a dependency because bottles already provides and manages its own wine runners.

missing lib32-glibc, lib32-freetype2, lib32-libxxf86vm, lib32-vkd3d, lib32-alsa, lib32-libsm dependencies.

I think there is a typo in the PKGBUILD which prevents a successful build. lib32-gnutxls in the first line of depends() should be lib32-gnutls

@nikic60245 That did the trick. Thanks a lot!

@trustin To fix the Gtk version error add the following lines to the begining of /usr/share/bottles/bottles/dialogs/generic.py:

import gi

gi.require_version('GtkSource', '4')

Reference: https://github.com/bottlesdevs/Bottles/commit/ced821b66952757b7adbed459c0bf3479b9b4d0c

I'm getting the following error after some updates (I'm now sure what packages were updated exactly.):

Traceback (most recent call last):
  File "/usr/lib/python3.10/site-packages/gi/importer.py", line 137, in load_module
    introspection_module = get_introspection_module(namespace)
  File "/usr/lib/python3.10/site-packages/gi/module.py", line 257, in get_introspection_module
    module = IntrospectionModule(namespace, version)
  File "/usr/lib/python3.10/site-packages/gi/module.py", line 109, in __init__
    repository.require(namespace, version)
gi.RepositoryError: Requiring namespace 'Gtk' version '4.0', but '3.0' is already loaded

Any clues? I rebuilt patool and bottles but it didn't help.

@gyurman: You probably need to rebuild patool due to recent Python 3.10 update. It's working for me.

^^>>> bottles                                                                                                                                                       16:51:48 
Traceback (most recent call last):
  File "/usr/bin/bottles", line 56, in <module>
    from bottles import main
  File "/usr/share/bottles/bottles/main.py", line 33, in <module>
    from .window import MainWindow
  File "/usr/share/bottles/bottles/window.py", line 27, in <module>
    from .backend.manager import Manager
  File "/usr/share/bottles/bottles/backend/manager.py", line 42, in <module>
    from .dependency import DependencyManager
  File "/usr/share/bottles/bottles/backend/dependency.py", line 22, in <module>
    import patoolib
ModuleNotFoundError: No module named 'patoolib'

FREQUENTLY ASKED QUESTIONS (read before flagging or commenting!)

There is a new version out, why is the package not updated?

Don't worry, I'll update the package as soon as I have my computer at hand (we're talking about a day or so after the last release)

I have a problem with wine, should I blame bottles?

Absolutely not, try changing the version of wine in the settings or switch to another fork of wine.

Something is broken with the app, where do I report it?

You can either open an issue on github or use our internal bug reporting tool in bottles.

I suggest not to edit the .SRCINFO manually. You can a avoid this mistake by generating it from the PKGBUILD like that: makepkg --printsrcinfo > .SRCINFO

pkgrel needs to be updated in PKGBUILD

Samba is not a dependency of this software and should be removed from the PKGBUILD.

https://github.com/bottlesdevs/Bottles/search?q=samba returns 0 results.

Also, the package provides a desktop file: https://github.com/bottlesdevs/Bottles/blob/master/data/com.usebottles.bottles.desktop.in

But as @saber716rus said, it is possibly not properly installed/linked to the /usr/share/applications/ folder.

не создаётся ярлык в системе.

Since the version string is "2021.7.1-treviso" i get the following message using yay to update:

-> bottles: local (2021.7.1-1) is newer than AUR (2021.7.1-treviso)

Is the version string you chose based on the source repo compatible with the pacman package versioning system? Disclaimer: i know nothing about versioning in pacman or creating packages (sadly). i just wanted to report you this message.

@rrods @nulldev

Sorry, the checksum of the penultimate commit has not been updated, with the last commit it has been fixed

cf56a681f2b23455ef5cdf371a26f65068b35ad7e6e138bb9f3ed66e55927a04 bottles-3.1.14.tar.gz

i installed using >

yay -S bottles --editmenu

replace +sha256sums=('ecebf7cb78b0843b903dcff8c712ddcef1409230ebd1a7c08d0e56362c3538c3')

with

+sha256sums=('cf56a681f2b23455ef5cdf371a26f65068b35ad7e6e138bb9f3ed66e55927a04')

It looks like the checksum for the latest source archive is incorrect or has changed somehow. Can you update the checksum?

The best solution would be a package called "wine-core" which does exactly this without installing the whole wine. https://fedoraproject.org/wiki/Wine

However Arch currently doesn't have split wine packages. wine-core is also a dependency on Fedora for lutris.

@shuriken wine is required due to a lack of dependencies, we are looking for these to bundle them with the package

wine should be an (optional) dependency similar to the Lutris package.As it doesn't require system wine, proton or other runners. Still putting them as optional does make sense as its user preference. Thanks for this great software brombinmirko. things like gamemode mangohud and other system runners can all be in optdepends as well.

@brito at the current stage, Bottles does not recognize system components (wine, dxvk) but could do so with the new version v4.

Would be nice if this used the dxvk-bin package, instead of downloading it in the user's home at first run.

This depends on gtk3 and python-gobject, see main.py.

I noticed a few things that could be improved with the PKGBUILD:

• arch should be any as there are no binaries in this package
• sha256sums is empty, while the only source is an archive. Please generate a sha256 checksum for the archive (in my case c854fbc333703449e82ae36db1ae4bd285b64441aec97e372ac6459dfdfe3585). Tip: If you need to update the sha256sum for a later release you can use the tool updpkgsums from the pacman-contrib package
• The file is missing a # Maintainer tag at the top

Most of these things can be checked automatically by using the tool namcap from the pacman-contrib package. Just run it against your PKGBUILD and a built package archive.

Cheers!

Hi.
Two notes. Could you please add ${pkgname}- in front of the source line? Makes it easier for those, which use $SRCDEST. Additionally skipping the generation of checksums is in general only allowed for VCS builds. As this downloads an archive, checksums should be generated. So please revert that change.
Maintainer lines aren't removed from a PKGBUILD. If there is a change, it will be changed from Maintainer to Contributor

Ehy man, new update here :D https://github.com/bottlesdevs/Bottles/releases/tag/2.1.0

Ehy! https://github.com/bottlesdevs/Bottles/releases/tag/2.0.8 new update :D can you please update!

@PsykeDady, I looked at the AppImage, dependencies are ok. I fixed the URL issue. Cheers.

Upstream URL is wrong, take url from the new repository of Bottles https://github.com/bottlesdevs/Bottles.git

and please, contact bottles team (mirko and co.) to fix the dependences that are wrong