While running flatpak-module build-module I get:
flatpak-module build-module
$ flatpak-module build-module Traceback (most recent call last): File "/usr/bin/flatpak-module", line 11, in <module> load_entry_point('flatpak-module-tools==0.9.3', 'console_scripts', 'flatpak-module')() File "/usr/lib/python3.7/site-packages/pkg_resources/__init__.py", line 489, in load_entry_point return get_distribution(dist).load_entry_point(group, name) File "/usr/lib/python3.7/site-packages/pkg_resources/__init__.py", line 2843, in load_entry_point return ep.load() File "/usr/lib/python3.7/site-packages/pkg_resources/__init__.py", line 2434, in load return self.resolve() File "/usr/lib/python3.7/site-packages/pkg_resources/__init__.py", line 2440, in resolve module = __import__(self.module_name, fromlist=['__name__'], level=0) File "/usr/lib/python3.7/site-packages/flatpak_module_tools/cli.py", line 6, in <module> from .container_builder import ContainerBuilder File "/usr/lib/python3.7/site-packages/flatpak_module_tools/container_builder.py", line 10, in <module> from .module_locator import ModuleLocator File "/usr/lib/python3.7/site-packages/flatpak_module_tools/module_locator.py", line 12, in <module> from module_build_service.builder.utils import create_local_repo_from_koji_tag File "/usr/lib/python3.7/site-packages/module_build_service/__init__.py", line 49, in <module> gi.require_version("Modulemd", "2.0") # noqa File "/usr/lib64/python3.7/site-packages/gi/__init__.py", line 121, in require_version (namespace, loaded_version)) ValueError: Namespace Modulemd is already loaded with version 1.0
flatpak-module-tools-0.9.3-1.fc31 python3-flatpak-module-tools-0.9.3-1.fc31 module-build-service-2.24.0-1.fc31
I get the same results in f30 and f29. I tried downgrading the packages above and libmodulemd too. The error persists. Changing module_locator.py to import the 2.0 version of Modulemd causes the build to start but it fails to finish with errors related to failing to download metadata for repo 'localrepo'.
It seems to work with module-build-service-2.20.0-1.fc30.noarch and libmodulemd-2.5.0-2.fc30.x86_64
Version 0.10.1 (https://bodhi.fedoraproject.org/updates/FEDORA-2019-a3735ca709) updates to the libmodulemd v2 API and should fix this issue.
Metadata Update from @otaylor: - Issue status updated to: Closed (was: Open)