Arch Linux User Repository

@Rhinoceros: Yes, it does--that was the point of the Solstice Python VDF & Steam forks since the upstream PR's have not been merged.

Thanks @lectrode and @yochananmarqos for the heads up. Can you confirm if the fork works for the beta? I'm a little bit wary to add a new random source until we know it's trustworthy. At the moment the fork is not starred by anyone, and it's still a bit rough (at least in the readme). I also can't find any comments about the veracity of the fork from elsewhere on the web. Also, at this stage I'm not entirely convinced it's "maintained" yet, since they have only added in three out of six pull requests from a while ago, and added no code themselves.

@lectrode: Use python-vdf-solstice instead which is a maintained fork by Solstice Game Studios.

It looks like upstream for this package is abandoned. As-is, this will stop working with Steam's next stable release (it has already stopped working for steam beta). It would probably make sense to update this to use a maintained fork so that it continues working with updated vdf formats:

https://github.com/solsticegamestudios/vdf

@Rhinoceros Okay.

@seanfire99 if it's not a problem with this package, then please post at the appropriate place, i.e. you could try the EndeavourOS forums.

after a reinstall i can now finally install python-vdf i just wanted to say thx for trying to help out with this problem of mine. now then since you have been helping me with making a clean chroot i wanted to go ahead and do that since rn i am having a problem with dolphin-emu-git my home dir is no longer btrfs it is now ext4 and since i am not an advanced user I'm just gonna asks you guys who seem to have way more experience in this field then i do cause i have read this a dozen times and honestly still don't understand what it wants me to do any help would be appreciated. link here https://wiki.archlinux.org/title/DeveloperWiki:Building_in_a_clean_chroot

Edit ~/.makepkg.conf to set the packager name and any makeflags. Also adjust the mirrorlist in $CHROOT/root/etc/pacman.d/mirrorlist and enable the testing repositories in $CHROOT/root/etc/pacman.conf, if desired. also this note i am on EndeavourOS

arch-nspawn $CHROOT/root pacman -Syu [sudo] password for seanfire99: error: config file /root/etc/pacman.conf could not be read: No such file or directory error parsing '/root/etc/pacman.conf' error: config file /root/etc/pacman.conf could not be read: No such file or directory error parsing '/root/etc/pacman.conf' ==> ERROR: '/root' does not appear to be an Arch chroot.

okay so i booted up a vm and the install works just fine there i have no idea what is wrong with my system i might just reinstall if i have to.

question im using btrfs and on the wiki on how to make a chroot dir it says the following however when i do do this it deletes chroot so do i just ignore this or something?

One can also define the CHROOT variable in $HOME/.bashrc using the export command if the location is to be repeatedly used.
On btrfs, the chroot is created as a subvolume, so you have to remove it by removing the subvolume by running btrfs subvolume delete $CHROOT/root as root.

@ruahcra thanks for letting me know about that yes it was i had used downgrade to go to an older version because of the backdoor that was installed in xz but had used downgrade again to update to the latest version and thought it was no longer being ignored well ill see if that fix anything. edit removing xz from ignore list fixed chroot i now have chroot working on another not i would like to also note my pythone version is 3.12.4 and i had less error on ver 3.11.8 when builing python-vdf.