Package Details: portmod 2.7.3-1

Git Clone URL: (read-only, click to copy)
Package Base: portmod
Description: A cli tool to manage mods for OpenMW
Upstream URL:
Licenses: GPL3
Replaces: openmmm
Submitter: bmwinger
Maintainer: bmwinger
Last Packager: bmwinger
Votes: 8
Popularity: 0.001858
First Submitted: 2019-08-11 01:45 (UTC)
Last Updated: 2023-12-29 03:01 (UTC)

Latest Comments

1 2 Next › Last »

RamenFiend commented on 2023-05-19 01:46 (UTC)

@bmwinger Thanks! I actually didn't know that. I was able to skip the checks just fine and upgraded. For anybody else with the same issues, do a reinstall of portmod and all dependencies, commenting out the check sections in the PKGBUILDs of the python packages that fail.

bmwinger commented on 2023-05-18 12:58 (UTC)

@RamenField: See This is a standard issue with how the AUR interacts with arch's binary packages which everyone using the AUR needs to be aware of.

The only thing that failed for me was redbaron, and that was just a test for the optional pygments functionality, so I just skipped the tests for redbaron when installing it.

RamenFiend commented on 2023-05-17 01:15 (UTC) (edited on 2023-05-17 01:16 (UTC) by RamenFiend)

Dependency python-rply (orphaned) will fail to build since last portmod update. Installing python-rply-git builds, but causes a build failure in portmod:

Configuration error:
There is a programmable error in your configuration file:

Traceback (most recent call last):
  File "/usr/lib/python3.11/site-packages/sphinx/", line 354, in eval_config_file
    exec(code, namespace)  # NoQA: S102
  File "/tmp/makepkg/portmod/src/portmod-v2.6.2/doc/", line 19, in <module>
    from portmod.globals import get_authors, get_version  # noqa
  File "/tmp/makepkg/portmod/src/portmod-v2.6.2/portmod/", line 4, in <module>
    import portmod.globals  # noqa # pylint: disable=unused-import
  File "/tmp/makepkg/portmod/src/portmod-v2.6.2/portmod/", line 150, in <module>
    from portmod.repos import get_local_repos  # noqa: E402
  File "/tmp/makepkg/portmod/src/portmod-v2.6.2/portmod/", line 14, in <module>
    from .config import get_config
  File "/tmp/makepkg/portmod/src/portmod-v2.6.2/portmod/config/", line 25, in <module>
    from .pyconf import (
  File "/tmp/makepkg/portmod/src/portmod-v2.6.2/portmod/config/", line 14, in <module>
    from portmodlib._loader import MINIMAL_GLOBALS, Policy
  File "/tmp/makepkg/portmod/src/portmod-v2.6.2/portmodlib/", line 19, in <module>
    from RestrictedPython import (
ModuleNotFoundError: No module named 'RestrictedPython'

make: *** [Makefile:20: man] Error 2
make: Leaving directory '/tmp/makepkg/portmod/src/portmod-v2.6.2/doc'
==> ERROR: A failure occurred in build().
 -> error making: portmod-exit status 4

becko commented on 2023-05-08 13:37 (UTC)

Required dependencies got abandoned and they don't build :(

error: can't build portmod-2.6.2-1, deps not satisfied: python-redbaron
error: packages failed to build: python-rply-0.7.8-4  python-baron-0.10.1-2  python-redbaron-0.9.2-8  portmod-2.6.2-1

orphaned deps: python-redbaron, python-baron, python-rply

gyscos commented on 2023-03-13 14:42 (UTC) (edited on 2023-03-13 14:45 (UTC) by gyscos)

Arf the issue was submodule.recurse = true in my user git config. The tests includes running the git CLI to fetch a repo, and it loads my config.

As a result, running git pull -v --rebase -- origin somehow fails. Indeed, for some reasons --recurse-submodules and -v appear incompatible with my git version (2.39.2).

Looks like this:

bmwinger commented on 2023-01-19 01:40 (UTC)

@gyscos, is it related to those tests requiring network access?

gyscos commented on 2023-01-03 14:52 (UTC)

Two tests are failing for me: test/ and test/ Both seem to be failing when calling git pull -v --rebase origin.

bmwinger commented on 2022-05-24 22:59 (UTC)

@silverhikari haven't been able to reproduce that. The current package still seems to work fine right after updating the rest of my system.

silverhikari commented on 2022-05-20 01:15 (UTC) (edited on 2022-05-20 01:16 (UTC) by silverhikari)

hey, just wanted to inform you the location of the file "" is now back to being located at "/portmod-v2.3.4/build/lib/portmodlib/"

bmwinger commented on 2022-05-18 00:00 (UTC)

Something must have changed. It would be useful if the python-setuptools-rust package would get updated so that we can go back to using the more reliable python --build_rust --inplace --release.

I've updated it to use the new path.