Package Details: unknown-horizons-git 2019.1.r47.gc196f0704-2

Git Clone URL: (read-only, click to copy)
Package Base: unknown-horizons-git
Description: Open source real-time strategy game with the comfy Anno1602 feeling.
Upstream URL:
Keywords: Anno Game OpenSource Realtime Strategy
Licenses: GPL, CCPL
Conflicts: unknown-horizons
Provides: unknown-horizons
Submitter: nihathrael
Maintainer: Lucki
Last Packager: Lucki
Votes: 52
Popularity: 0.000000
First Submitted: 2010-08-26 10:53 (UTC)
Last Updated: 2019-10-16 13:14 (UTC)

Latest Comments

1 2 3 4 5 Next › Last »

Lucki commented on 2023-06-11 11:40 (UTC) (edited on 2023-06-15 10:05 (UTC) by Lucki)

This is a VCS package which can't be outdated.

The issue is not due to packaging:

Edit: Builds again now

Mr.Smith1974 commented on 2023-06-08 11:57 (UTC) (edited on 2023-06-08 11:57 (UTC) by Mr.Smith1974)

  File "/usr/lib/python3.11/site-packages/setuptools/_distutils/", line 111, in ensure_finalized
  File "/usr/lib/python3.11/site-packages/setuptools/command/", line 219, in finalize_options
    parsed_version = packaging.version.Version(self.egg_version)
  File "/usr/lib/python3.11/site-packages/packaging/", line 198, in __init__
    raise InvalidVersion(f"Invalid version: '{version}'")
packaging.version.InvalidVersion: Invalid version: '2019-dev-154-gc2f4d607b'
==> ERROR: A failure occurred in package().
 -> error making: unknown-horizons-git-exit status 4

Lucki commented on 2019-07-26 07:59 (UTC) (edited on 2019-07-26 15:05 (UTC) by Lucki)

Please create the following directory, try again and also report back if that fixes your problem you've might found a bug in their build script:


I'm actually a bit confused I'm not running into this error in a clean chroot build. The folder doesn't exist there either.

Edit: Are you sure you're on the latest commit? The line in question got fixed 7 months ago and differs from your quoted error message.

tepiloxtl commented on 2019-07-25 20:18 (UTC) (edited on 2019-07-25 20:19 (UTC) by tepiloxtl)

Im unable to build this package right now with error in build:

==> Starting build()...
Traceback (most recent call last):
  File "horizons/engine/", line 70, in <module>
    from horizons.constants import PATHS # isort:skip
  File "/usr/lib/python3.7/site-packages/horizons/", line 596, in <module>
    _config_dir, _data_dir, _cache_dir = get_user_game_directories()
  File "/usr/lib/python3.7/site-packages/horizons/util/", line 104, in get_user_game_directories
FileNotFoundError: [Errno 2] No such file or directory: '/home/tepiloxtl/.cache/yay/unknown-horizons-git/src/python/.config/unknown-horizons'
==> ERROR: A failure occurred in build().

(This has been run manually after yay failed to build this package too)

FredBezies commented on 2019-04-28 21:03 (UTC) (edited on 2019-04-28 21:04 (UTC) by FredBezies)

Here is a modified PKGBUILD:

# Maintainer: Lucki <>
# Contributor: Chris Oelmueller <>
# Contributor: Thomas Kinnen <>
# Contributor: Thomas Kowaliczek-Schmer <>

pkgdesc="Open source real-time strategy game with the comfy Anno1602 feeling."
license=('GPL' 'CCPL')
depends=('fife' 'python-yaml' 'python-pillow' 'python-future')
makedepends=('git' 'intltool')

pkgver() {
    cd "$srcdir/${pkgname%-git}"
    git describe --long --tags | sed -r 's/^v//;s/-dev//;s/([^-]*-g)/r\1/;s/-/./g'

build() {
    cd "$srcdir/${pkgname%-git}"
    HOME=. python build

package() {
    cd "$srcdir/${pkgname%-git}"
    HOME=. python install --root="$pkgdir/" --optimize=1 --skip-build

Lucki commented on 2019-02-13 18:23 (UTC)

The current version (2019.1) doesn't get displayed in the version string because the actual tag is in a separate branch. This is the -git version and builds from the master branch which latest tag is sadly 2017.2 but it's actually several commits in front of the 2019.1 tag. So this package is not outdated, pbnoxious.

If you know how I can get the latest tag over multiple branches with a matching filter let me know.

ChrisOelmueller commented on 2017-08-03 17:29 (UTC)

As opposed to…? All I'm aware of is UH installing a symlink to that exact launcher under a name that's easier to memorize. If something is expected to be placed elsewhere during setup process I'd assume the best course of action is asking about a change in that process upstream – the package simply trusts those definitions are correct and executes them. But I didn't understand the expected behavior from your comment just yet, so you might have to clarify a bit: What would you like to happen but didn't?

<deleted-account> commented on 2017-08-03 15:53 (UTC)

This package does not install the script.

balduin commented on 2014-09-27 13:28 (UTC)

Works without any problems.

ChrisOelmueller commented on 2014-08-22 14:09 (UTC)

And migrated back to fife-git after the segfaults look like they've been fixed.