Arch Linux User Repository

Hi, here is an update on the libstrangle and libstrangle-git packages:

Context:
- Updates to GCC 13 and GLIBC 2.38 broke libstrangle,
- There are pending merge requests to the original upstream repo[1] to bring the package back to functional state,
- However, the upstream repo appears not to be maintained anymore and the MRs have been pending for a year,

Our AUR packages:
- libstrangle will remain based on the original upstream repo, but I updated the PKGBUILD to include all necessary changes as .patch files,
- libstrangle-git will switch to @Infernio's fork[2] of the original upstream repo,
- This brings back both packages to functional state, and give users flexibility depending on whether the origin upstream repo comes back to life, or whether @Infernio's fork is more reliable,

Finally, sorry for the long resolution delay. Since @Infernio volunteered, I added him as co-maintainer of both packages.

@Infernio, I now have more time for this maintainance work, so I should be able to contribute more reliably. But if you prefer to completely take over, let me know and I will set you as primary maintainer.

[1] https://gitlab.com/torkel104/libstrangle
[2] https://gitlab.com/Infernio/libstrangle

Hi, here is an update on the libstrangle and libstrangle-git packages:

Context:
- Updates to GCC 13 and GLIBC 2.38 broke libstrangle,
- There are pending merge requests to the original upstream repo[1] to bring the package back to functional state,
- However, the upstream repo appears not to be maintained anymore and the MRs have been pending for a year,

Our AUR packages:
- libstrangle will remain based on the original upstream repo, but I updated the PKGBUILD to include all necessary changes as .patch files,
- libstrangle-git will switch to @Infernio's fork[2] of the original upstream repo,
- This brings back both packages to functional state, and give users flexibility depending on whether the origin upstream repo comes back to life, or whether @Infernio's fork is more reliable,

Finally, sorry for the long resolution delay. Since @Infernio volunteered, I added him as co-maintainer of both packages.

@Infernio, I now have more time for this maintainance work, so I should be able to contribute more reliably. But if you prefer to completely take over, let me know and I will set you as primary maintainer.

[1] https://gitlab.com/torkel104/libstrangle
[2] https://gitlab.com/Infernio/libstrangle

Well, you can compile it, but it still won't work, as the OS complains that libstrangle.so is missing __libc_dlsym. Some reads in the forum suggests one should use libstrangle-git to resolve that issue.

Hm, this does appear to be the problem.

I resolved it by editing the build file and adding the following line to the prepare statement:

sed -i -e '/limiter.h/a #include <cstdio>' src/vulkan/overlay.cpp

Oddly, this failed to compile for me, complaining that it couldn't find stderr or fprintf, and that perhaps someone failed to #include <cstdio>.

Has anyone else had that problem?

Hello,

As you can see upstream v0.1.1 is indeed the latest release[1]. Therefore, I will "unflag" out of date.

Debian packagers already opened an issue requesting for a new release[2], so I will not open another one. I will simply comment that a new release would help us too.

Finally, I will take a look at updating libstrangle-git[3]. I see that there are a few comments for which I received no notifications. Maybe you can use this until we get a new release ?

[1] https://gitlab.com/torkel104/libstrangle/-/releases
[2] https://gitlab.com/torkel104/libstrangle/-/issues/55
[3] https://aur.archlinux.org/packages/libstrangle-git

The thing is the 'release' for strangle is quite old, as you can see here https://gitlab.com/torkel104/libstrangle/-/releases so the GIT version is the only solution to workaround any recent issue as it will pull all the latest commits instead of the very old latest release. No big deal this AUR package will be updated to latest version when strangle dev will make a new point release.

Same for me. Not working with proton. Didn't investigate further because libstrangle-git is working fine. The package maintainer is not to blame as the one year old version 0.1.1 is the latest release version which it is quite a lot of commits behind the recent git.

Currently doesn't work anymore on any of my Steam/Proton games (maybe related to me using Steam BETA, didn't try to get back to normal Steam as it is currently broken I can't access library/store/community it doesn't render the content). The GIT version is working though so I'm using it in the meantime.

doesnt have to have libstrangle in conflicts and provides