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. 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.

@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. 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?

Usually I'm on the ball with these things, but my phone can no longer notify me when I get emails, and thus I notice comments here late, so I only realized I needed to do something when Ashantin released her first proper 1.20 let's play episode. :D Thanks for poking me.

I did finally include @lufog's suggestion as well. However, I have no excuse for not including that small change earlier.

Thank you, kind sir.

for those who want to try 1.20.0 before @copygirl updates this package, you can do it in an easy way just modifying PKGBUILD to point to the new version:

$ git clone https://aur.archlinux.org/vintagestory.git
$ cd vintagestory

Modify PKGBUILD file with the new version and md5sum:

_pkgver=1.20.0
...
...
# Replace 6e9c03ebb47eb9c1cf0d4c0e8a6507f1 by 6fd6e877b073656b4ff26df744e4c735
md5sums=("6fd6e877b073656b4ff26df744e4c735"
          "26ff9ca4fb0a583589f26f2c274d4ec6"
          "e77871150115253e0d8c31b77a274182")

and generate the package as usual:

$ makepkg --install

1.20 released. Kindly want to know when it will be packaged?