Arch Linux User Repository

Please note that you can flag the package out-of-date and I'll get a notification just the same as when you comment here. I'll always be sure to check for the latest version and update things accordingly. Use the comments to report issues or fixes regarding the package.

Typically I update the package within a day or so of being notified. If you don't want to wait, you can easily update the PKGBUILD yourself: In the case of a regular release, just update the _pkgver field and replace the first md5sums value with SKIP, before running makepkg -Csi or when your AUR helper asks you if you want to make changes before proceeding with the build / install.

I've updated the package to 1.20.4 but unfortunately the devs didn't get around to updating Harmony yet, so the issue mentioned below is still present. This is for people who would like to mess around to get things to work regardless. Though I personally would not recommend downgrading, as it could cause system instabilities.

edit: Some solutions can be found here: https://github.com/anegostudios/VintageStory-Issues/issues/5252

Indeed, as someone in IRC said: "glibc upgrades broke everything"

ActualLizard on Discord was able to look into it a bit more, and it's indeed caused by changes to glibc relating to the not making the stack executable by default (or something like that). See this issue: https://github.com/MonoMod/MonoMod/issues/198

A fix was pushed out, and Harmony updated its dependency. Harmony being the library that allows Vintage Story mods to patch the game code and each other. Updating just the dependency by hand isn't working, so I think we'll just have to wait for a game update from the Vintage Story team. (Mods that don't use Harmony are fine.)

After the kernel/libc updates on feb 3, when I attempt to join my server the game crashes. The logs seem to be related to mods requiring dotnet mm-exhelper. These mods worked before the feb 3 updates.

/usr/share/vintagestory//tmp/mm-exhelper.so.BZEg41: cannot open shared object file: No such file or directory /usr/share/dotnet/shared/Microsoft.NETCore.App/7.0.20//tmp/mm-exhelper.so.BZEg41: cannot open shared object file: No such file or directory

I got strange problems with mods (combatoverhaul + detailed animals) and the newest glibc version. Very strange. Logs aren't very helpful (smth. smth. cannot laod /tmp/xyz-helper.so.abc). Hope that helps anyone stumbling over the same issue.

@Damgaldor Indeed, that was my problem. The src and/or pkg sticking around end up causing files from older version to end up in the new package I built. The suggested solution is to either use --clean (-c) or --cleanbuild (-C). Alternatively you can always build in a clean directory manually.

• You can run makepkg --clean either on its own, before or after you build the package, which gets rid of those extra files. Using it as makepkg -sic (order doesn't matter), it will clean afterwards. (So if you already got dirty files around it can still mess things up.)
• Or you can use makepkg --cleanbuild -si (or -Csi for short) to clean things up beforehand, to make sure they never affect the package.
• Or just use an AUR helper that takes care of all of this for you. (Lately I've been using paru, myself.) I just do it manually here since I'm maintaining the package.

Funnily enough, in years of maintaining this package, I've never noticed I've made that mistake.

I had this issue when I did makepkg --install in the same direction where I did this for the previous version. So I deleted the directory with PKGBUILD, did git clone again, edited PKGBUILD and install was successful, didn't even need to delete the broken install.

The 1.20.3 update is taking a bit longer because there is an issue (game thinks there are files from a previous installation – there are not) and I need to ask the developer what to do.

Please note that you can flag the package out-of-date and I'll get a notification just the same as when you comment here. I'll always be sure to check for the latest version and update things accordingly. Use the comments to report issues or fixes regarding the package.

Typically I update the package within a day or so of being notified. If you don't want to wait, you can easily update the PKGBUILD yourself: In the case of a regular release, just update the _pkgver field and replace the first md5sums value with SKIP, before running makepkg -Csi or when your AUR helper asks you if you want to make changes before proceeding with the build / install.

Actually 1.20.3

1.20.2 released. Update pretty please?