Arch Linux User Repository

@sonic2kk: No, the same information does not actually apply here. Notice the source is the AppImage, so there's nothing to do. ;)

(Copied from protonup-qt package, as the same information applies here)

Hello! Just wanted to let you know that the next release of ProtonUp-Qt is going to use a fork of the vdf and steam dependencies, as the upstream versions of these have not been updated to parse the new Steam appinfo.vdf format, which breaks functionality on the current Steam Client Beta for the last ~1 month and will thus also break once this is out of the Steam Client Beta and into the Steam Client Stable. For the record, it is semi-common for the appinfo.vdf format to change, the version gets bumped every so often and libraries have to be updated to accommodate this. So this isn't a bug on the Steam Client that we're working around, but a deliberate format update on the Steam Client's appinfo.vdf that we have to account for.

Being able to parse this file has required changes on both the steam and vdf libraries, and upstream did not merge the PRs in time and there has been little activity upstream for a while, so SolsticeGameStudios are maintaining forks with the necessary PRs merged.

SolsticeGameStudios intend to keep the forks around, as they are using it themselves: https://github.com/DavidoTek/ProtonUp-Qt/issues/415#issuecomment-2254092417 - As a caveat, they don't intend to support older Python versions, but that shouldn't be an issue for an AUR package :-)

I hope it is not too problematic to update to support these new dependencies. Quite a few users that open issues on ProtonUp-Qt are using an AUR package of ProtonUp-Qt (the issue template asks for the installation method, and AUR is not uncommon). I have seen protonup-qt-bin be mentioned specifically in the command when users provide it with yay -S protonup-qt-bin. If there is anything that can be done on the ProtonUp-Qt side to make this easier, feel free to open an issue / pull request!

SteamDatabase work to figure out the format change:

• https://github.com/SteamDatabase/SteamAppInfo/commit/56b1fec7f5ce6be961c3e44cf9baf117e363ad91

Relevant ProtonUp-Qt discussion:

• Initial issue: https://github.com/DavidoTek/ProtonUp-Qt/issues/415

• PR to use forks instead of upstream dependencies: https://github.com/DavidoTek/ProtonUp-Qt/pull/426

Upstream PRs that were not merged:

• https://github.com/ValvePython/vdf/pull/61

• https://github.com/ValvePython/steam/pull/464

SolsticeGameStudios forks:

• https://github.com/solsticegamestudios/vdf

• https://github.com/solsticegamestudios/steam

Gentle reminder to please update your package.

changes needed : 1. BUMP the package number in PKGBUILD to 2.9.2 and update the sha256sum to the latest 2. .SRCINFO also needs a change in version to 2.9.2 and change the old sha256sum to the latest. It looks like the source mentioned in the .SRCINFO source refers to 2.8.2 please update it to latest as well.

Please update the package to latest version. AppImage version 2.9.1 is already available

I have already tested with the new version changes on a local git branch and it seems to be working as intended. Please bump up the version in aur as well.

it misses the requirement of fuse2. Appimages don't work with fuse3

thanks for providing the appimage version.

Thank you for the feedback @yochananmarqos. I updated the PKGBUILD to use the icons from the AppImage.

The icons are in the AppImage. Extract it and install them from there:

prepare() {
  chmod +x "$_pkgname-$pkgver-$CARCH.AppImage"
  ./"$_pkgname-$pkgver-$CARCH.AppImage" --appimage-extract
}

In the package() function:

  install -d "$pkgdir/usr/share/icons/"
  cp -r squashfs-root/usr/share/icons/hicolor/ "$pkgdir/usr/share/icons/"

The noextract() array is unnecessary as AppImages are not automatically extracted.