@rtentser Thanks for bringing this up.
The inconsistent tag versioning of openmw has given me a lot of trouble and I haven't always been able to keep up or grep the version correctly.
This instance was a bug in my latest change to the package.
To avoid this in the future, I have noted the most common cases of failure with the tag and added a validation test in comments of the pkgver function so future fixes don't regress:
First we strip off any openmw-*
There must be no dashes.
We remove any other words such as rc
Finally, if there is no major or patch number, add 0
Test using this script:
declare -a test_tags=("openmw-0.29.0" "0.42.0" "0.42.1" "1.42.1" "0.47.0-RC3" "openmw-48-rc10")
for _tag in "${test_tags[@]}"; do
_fixed_tag=$(echo $_tag | sed 's/^openmw-//' | sed 's/-.*//' | sed -E 's/^([0-9]+)$/0.\1.0/')
echo "$_tag -> $_fixed_tag"
done
Expected output:
openmw-0.29.0 -> 0.29.0
0.42.0 -> 0.42.0
0.42.1 -> 0.42.1
1.42.1 -> 1.42.1
0.47.0-RC3 -> 0.47.0
openmw-48-rc10 -> 0.48.0
Pinned Comments
Lone_Wolf commented on 2022-06-17 10:07 (UTC)
openmw-git has been found to require a sizable amount of temporary space during building.
The available amount depends on system specifics so is different for all systems. In case build fails with "no space left on device" you may be bitten by this.
See https://bbs.archlinux.org/viewtopic.php?id=277304 for details and possible solutions.
bwrsandman commented on 2016-09-24 14:59 (UTC) (edited on 2018-11-22 17:28 (UTC) by bwrsandman)
Please refrain from flagging the git version as out date when a new release comes out. The git aur packages update their version on install time based on the tags of the git repo.
Keep in mind that this is a VCS package and it is meant to be in line with the latest master which might not always work. It is not meant to follow the release pattern in any particularly smart way and assumes that upstream maintains their tags consistently.
For the newest release, the correct page is https://www.archlinux.org/packages/?q=openmw