Package Details: openmw-git 0.48.0.r3001.g518aa5c6ae-1

Git Clone URL: (read-only, click to copy)
Package Base: openmw-git
Description: An open-source engine reimplementation for the role-playing game Morrowind.
Upstream URL:
Licenses: custom, GPL3, MIT
Conflicts: openmw
Provides: openmw
Submitter: None
Maintainer: bwrsandman (Lone_Wolf)
Last Packager: bwrsandman
Votes: 31
Popularity: 0.38
First Submitted: 2011-01-05 16:17 (UTC)
Last Updated: 2023-08-27 17:03 (UTC)

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

Latest Comments

1 2 3 4 5 6 .. 13 Next › Last »

bwrsandman commented on 2023-08-27 17:07 (UTC)

@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"
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

rtentser commented on 2023-08-27 15:54 (UTC)

For some reason this package sets incorrect version ( for example) and always wants to update (because 0.0.48 is less than 0.48)

Lone_Wolf commented on 2023-07-22 16:14 (UTC)

No, this pacakge builds openmw master , currently 0.49 .

The part of the version before the r is based on tags existing in the upstream repo and there won't be a 0.49 tag until 0.49 is branched off and master becomes 0.50 .

If you want to verify the version used, check the commit hash (leave out the g) at the end of pkgver .

There was a discussion about the version & tags in comments not long ago (check 1 and 2 pages back) but this is bwrsandman' package and they prefer using tags created by upstream.

NZKX commented on 2023-07-22 14:55 (UTC)

Thanks for the quick update, but there's one more problem. This is not the latest build of OpenMW.. The latest .is 0.49.This 0.48. You can grab binary versions of OpenMW .0.49.0 here (the official OpenMW uses it for their build releases)..

NZKX commented on 2023-07-16 08:46 (UTC)

The PKGBUILD won't compile due to an pkgver error It needs to be fixed ==> ERROR: pkgver is not allowed to contain colons, forward slashes, hyphens or whitespace. ==> ERROR: pkgver() generated an invalid version: 48-rc12.1.r2533.gb383efabf5

Lone_Wolf commented on 2023-05-19 08:24 (UTC)

I checked the issue and saw the extra info helped openmw devs to solve the Protective Guards issue.

It's also good to see more people willing to participate in making openmw better. Great job, Le_Limule .

Le_Limule commented on 2023-05-18 12:03 (UTC)

Some lua mods have pbs with recent commits. Especially the Protective Guards mod (

This is the synthesis of all my tests:

The problem appears especially with Protective Guards, so i focused on it. (same pb with Debian and Arch Linux)

Note: Y = Protective Guards works ; N = Protective Guards doesn't work

03 march, commit 0d25656d: Y

18 march, commit d64eea2f: Y

22 march, commit 99dac61e: Y

24 march, commit 5446906b: Y

25 march, commit 2f2b952e: Y

26 march, commit 6756e1ba: N

26 march, commit 76cba95a: N

03 april, commit b04bcb9a: N

11 april, commit 4fd8ed8f: N

11 may, commit 42bf6399: N

14 may, commit 3fe621d5: N

=> it seems that commits have some lua regression since 26 march, until now.

See this issue for more info:

Le_Limule commented on 2023-05-16 15:31 (UTC)

@Lone_Wolf: unfortunately the commit b04bcb9a doesn't resolve the "Protective Guards" problem, but "my old commit" 0d25656d (03 March) is still working. I'm going to test with the commit 3fe621d5 (14 May)...

Lone_Wolf commented on 2023-05-06 15:25 (UTC)

Build fails with gcc 13.1 due to an issue with the repo mygui package.

See for details and a link to an upstream patch for mygui.

Lone_Wolf commented on 2023-04-29 13:45 (UTC)

AARCH64 added, also adjusted pkgver() so the package builds again and some minor changes.