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

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

6 years ago

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

6 years ago

Login to comment on this ticket.

Metadata