fm-orchestrator

#840 Latest mock-scm clones components in the wrong directory during local builds
Closed: Fixed Opened by mprahl.

Closed: Fixed
Reopen Issue

Using mock and mock-scm version 1.4.2, things work as expected. When upgrading to mock and mock-scm version 1.4.8, issues start to occur when running mbs-build local.

When running a local build on testmodule, the mock-scm plugin clones the "ed" package in the directory that mbs-build was run in instead of the temporary directory that mock-scm created. I suspect it stems from this commit in mock but I am not sure:
https://github.com/rpm-software-management/mock/commit/a40567a635ad3a76f480198a499931eab6aabbdd

Further investigation is needed.

Metadata Update from @mprahl:
- Issue assigned to mprahl

I submitted a PR upstream to address this issue:
https://github.com/rpm-software-management/mock/pull/158

The bug fix made it in 1.4.9:
https://bodhi.fedoraproject.org/updates/FEDORA-2018-c17daa06f6
Edited by mprahl

Metadata Update from @mprahl:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

This issue has been migrated to Fedora Forge:
https://forge.fedoraproject.org/koji/mbs/issues/840

Please continue any further discussion there.
Metadata
None
None
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.