Learn more about these different git repos.
Other Git URLs
Yesterday I've built a new version of the pagure-dist-git package in the epel8-infra-stg tag.
This triggered a newRepo for this repo: https://koji.fedoraproject.org/koji/taskinfo?taskID=54783388
However, looking at: https://kojipkgs.fedoraproject.org/repos-dist/epel8-infra-stg/latest/x86_64/ the version seems to be from August 4th. (checking it now, the latest repo seems to be gone... and the most recent one seems empty: https://kojipkgs.fedoraproject.org/repos-dist/epel8-infra-stg/2354668/x86_64/ )
So something somewhere isn't performing as expected, could you check?
There was a builder with a missing nfs mount, so it was failing createrepos. ;(
Should be fixed now.
Metadata Update from @kevin: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
I'm not seeing the latest folder at: https://kojipkgs.fedoraproject.org/repos-dist/epel8-infra-stg/
Metadata Update from @pingou: - Issue status updated to: Open (was: Closed)
Ah, so it seems some of the packages tagged in there were archived. We cannot have any archived packages used in active repos.
So, we need to untag those, or move them back from the archive volume.
Metadata Update from @kevin: - Issue tagged with: medium-gain, medium-trouble, ops
@kevin untagging is not an option the package is coming from epel8 tag. How do we move it from the archive? And how did it get there? The build itself is the latest build of python-django-rest-framework in epel8 repository.
So, in our case archive means that the build has been moved to an archive volume. My intent with this was that nothing that was in archive volumes should ever be needed still by active builds/repos.
It's unclear to me why this build would have been moved to archive. ;(
In any case the fix is either to untag it (which as you note isn't right in this case) or move it back from archive:
koji set-build-volume DEFAULT python-django-rest-framework-3.11.0-2.el8
(DEFAULT is the main / normal koji volume).
Looks like @mohanboddu fixed this?
Yes @mohanboddu fixed this and I was able to install the new pagure-dist-git on stg.
Thanks everyone for helping with this!
Metadata Update from @pingou: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Issue status updated to: Open (was: Closed)
Issue status updated to: Closed (was: Open) Issue close_status updated to: Fixed
Log in to comment on this ticket.