Learn more about these different git repos.
Other Git URLs
I'd like to query the Koji eln-build repo, however the src repo is missing. Could it please be generated?
Any time.
When we drop ELN or when all Koji repos would have src repos by default.
No easy way to query the source packages in the eln buildroot.
Thanks
Metadata Update from @mohanboddu: - Issue tagged with: medium-gain, medium-trouble, ops
So, here is my couple of cents on this ticket
But it should be easy change. I will let eln team decide this.
Additionally: Are the queries here something thats going to be ongoing? I really don't want to have this enabled and used once/a few times and then no more...
Are the queries here something thats going to be ongoing?
I cannot promis you that I will keep doing the queries forever, but my intentions are to have this permanently available, yes.
Generating the source repos is not too difficult, but the storage requirements could be significant. @jkaluza is maintaining the ODCS config for ELN; I'd ask him to comment on the feasibility.
The repo on odcs.fedoraproject.org already contains the soruce repo in https://odcs.fedoraproject.org/composes/production/latest-Fedora-ELN/compose/Everything/source/tree/. This request is about the Koji repo, i.e. http://kojipkgs.fedoraproject.org/repos/eln-build/latest/
I don't see a problem with creating this repo, assuming that we have sufficient available storage for it.
In releng meeting today, we decided to enable it and see what happens, if its using more CPU cycles and being slow and also started using more storage, we will rethink about disabling it.
Hello. How can I help to make this happen? After the fedora-eln.repo has become baseos/appstream only, querying build dependencies has become virtually impossible without this. Thanks
Should be fixed in ansible now, should appear in a bit in koji.
Metadata Update from @kevin: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
It did not appear and the rawhide koji-source repo is also no longer available.
Metadata Update from @churchyard: - Issue status updated to: Open (was: Closed)
Sigh. I foolishly assumed they were seperated by , but turns out they are seperated by space. ;(
FIxed I think. Please confirm and you can close.. :)
Thanks, it works.
Metadata Update from @churchyard: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.