Hello;
https://docs.fedoraproject.org/en-US/flatpak/troubleshooting/
I was troubleshooting packages for debug and I enabled "RPMS_ALLOW_REPOSITORY = True" and set DISTGITS config(from docs) then start it gives errors; "no defined commands for ..."
Traceback (most recent call last): File "/usr/lib/python3.9/site-packages/module_build_service/scheduler/batches.py", line 63, in start_build_component c.task_id, c.state, c.state_reason, c.nvr = builder.build( File "/usr/lib/python3.9/site-packages/module_build_service/builder/MockModuleBuilder.py", line 736, in build builder = SCMBuilder(mock_config, resultsdir, source, artifact_name) File "/usr/lib/python3.9/site-packages/module_build_service/builder/MockModuleBuilder.py", line 804, in __init__ distgit_cmds = self._get_distgit_commands(source) File "/usr/lib/python3.9/site-packages/module_build_service/builder/MockModuleBuilder.py", line 848, in _get_distgit_commands raise KeyError("No defined commands for {}".format(source))
app.yaml
kde-settings: repository: file:///home/thunderbirdtr/Projects/src_fedora/kde-settings rationale: Runtime dependency ref: f33
What am I missing ? Thank you.
The instructions in the docs are likely out-of-date with respect to the current module-build-service packages in Fedora.
I would recommend using the packages from https://copr.fedorainfracloud.org/coprs/otaylor/flatpak-module-tools-experimental/ instead - they work much better for local builds. I don't feel comfortable updating the docs to point to them though, I have not yet had any luck getting upstream to review or incorporate the patches from this copr.
With my modified version, and I think with the newer unpatched module-build-service, no changes to the config should be need to support file:/// URIs for local build.
@otaylor I used your copr version in weekend and worked nicely. It fixed my build problem and all work better(also better terminal outputs(colors and cleaner log path as well) I wanna update document accordingly gonna need to wait until update/commit in upstream as well.
Thank you.
Login to comment on this ticket.