Learn more about these different git repos.
Other Git URLs
[2019-12-04 11:10:37,032][ DEBUG][backend.build_dispatcher][build_dispatcher.py:run:187] Skipping job BuildJob<id: 849021, owner: @copr, project: TEST1575431880370966030CoprDirTest, project_dir: TEST1575431880370966030CoprDirTest:examplegit branch: None, git hash: 1ae0c12b1536a4c6f31925b8e12f486247d6402d, status: None > because copr_base repo is not available yet
That's because we don't regenerate copr_dir when we create coprdir.
Commit 0242c13 relates to this ticket
worked-around for release purposes, proper fix TBD
Metadata Update from @praiskup: - Issue untagged with: release-blocker
Metadata Update from @praiskup: - Issue marked as depending on: #1145
This task is free to take again.
Metadata Update from @praiskup: - Assignee reset
See the 0242c13 commit and comment:
This isn't really proper fix; we should bound the createrepo action with *any* CoprDir creation, and create CoprDir automatically with new CoprChroot instance. But it will require proper testing and I don't have enough time before release.
Metadata Update from @praiskup: - Issue assigned to praiskup
Metadata Update from @praiskup: - Issue unmarked as depending on: #1145
Metadata Update from @praiskup: - Issue close_status updated to: Invalid - Issue status updated to: Closed (was: Open)
Not that easy ... I was probably wrong. At the time CoprDir is created there aren't usually the related CoprChroots, yet.
Log in to comment on this ticket.