Re: epel8: BuildrootError: could not init mock buildroot

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 2020-02-05 15:41, Kevin Fenzi wrote:
On Mon, Feb 03, 2020 at 11:45:38AM -0500, John Florian wrote:
On 2020-01-30 20:42, Kevin Fenzi wrote:
I fear it's just bad timing + the external rhel8 repo we have only keeps
the newest packages (epel7 repos keep the old packages around too).

koji has no way to know that an external repo updated and needs
regeneration, so it just regenerates it when the buildroots that depend
on it change, ie, for epel8 that means when a stable updates push goes
out. Since updates pushes have been broken, no regen has happened
recently. ;( For epel7, it's fine just using the older package, but in
epel8 it's gone and you see the 404 for it.

Updates pushes should be going again so that should help.

After that I guess we could try and just do a regen every day no matter
what? Or add something to the script that updates the repo to fire one
after anything updates?

kevin
I don't know if it would be useful or not here, but you might want to check
out my gojira tool as part of https://github.com/jflorian/koji-helpers.
Cool. Do you know if upstream koji would be open to just merging this?

It would likely be handy for a lot of places that use external repos.

kevin

I've not approached them but have been wanting to do so.  I needed it for $DAYJOB (and wanted it for $NIGHTHOBBY) and it's proved itself worthwhile.  The hardest part for me was determining that indeed something like this is needed and that no, koji doesn't do that yet.

IIRC, I've seen that they've had discussions for something like this.  I had wanted to clean it up to use native calls rather than shelling to the koji cli, but was waiting until koji was on python 3 since I had never had any interest in taking this backwards to py2.  Then a divorce fell in my lap last year and I'm still sorting out that mess so, unfortunately, I don't have the time to shepherd this thru right now or in the immediate future that I can foresee.  If someone wishes to do that, I'd be more than happy to advise and answer any questions.

My timeline is also crunched while I try to figure out how to configure koji to build against EL8 and seem to be running into many problems that Fedora has faced with EPEL8 and Modularity, which may also affect all of this.  Somehow I got myself onto too many treadmills at once!  :-)
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux