#120 Forking resulted in an incomplete repository
Closed: Fixed 4 years ago by praiskup. Opened 6 years ago by benzea.

Some time ago I forked a repository, but apparently some packages in certain versions were missing.

What I do know is that in https://copr.fedorainfracloud.org/coprs/benzea/hwtesting-unstable/ the forked FWTS build https://copr.fedorainfracloud.org/coprs/benzea/hwtesting-unstable/build/589310/ was missing for EPEL-7. When I noticed this, I resubmitted the same SRPM as before and it build just fine https://copr.fedorainfracloud.org/coprs/benzea/hwtesting-unstable/build/590982/.


Metadata Update from @clime:
- Issue assigned to frostyx

6 years ago

Yes, that might happen if prunerepo (automatic repository prunning script running on backend) removed the package from the chroot because it was built somewhere else (in some other build for that same chroot) and by repodata, that other built package was preferred.

Metadata Update from @msuchy:
- Issue tagged with: RFE

5 years ago

I tried to create this fork:
https://copr.fedorainfracloud.org/coprs/praiskup/sclo-postgresql10-test-that-fork-doesnt-work/monitor/

And it is incomplete, is it related to this issue? If yes, this should be labeled as "Bug", not "RFE".

Metadata Update from @praiskup:
- Issue untagged with: RFE
- Issue tagged with: bug

5 years ago

Login to comment on this ticket.

Metadata
Related Pull Requests
  • #943 Merged 4 years ago