Re: epel8: BuildrootError: could not init mock buildroot
tor 2020-01-30 klockan 17:42 -0800 skrev Kevin Fenzi: > On Thu, Jan 30, 2020 at 07:57:22AM -0500, Stephen John Smoogen wrote: > > On Thu, 30 Jan 2020 at 06:06, Jiri Kucera wrote: > > > Hello, > > > > > > when doing `fedpkg scratch-build --target epel8-candidate --srpm > > > sox-14.4.2.0-29.el8.src.rpm`, I get: > > > > > > > So there seems to be something off in koji and the repo is not getting > > properly regenerated after the repo gets updated. These errors seem to > > have occurred after we updated koji to the latest release so this may > > be a change in what koji does. > > 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 There is a work-around for this. Since the buildroot is regenerated when a buildroot override is added, you can repair the buildroot by adding an override for some random package you don't really need an override for, see e.g.: https://bodhi.fedoraproject.org/overrides/castxml-0.2.0-1.el8 It would of course be better if changes to the external repo would be automatically detected, but until that happens you can work around it. Mattias smime.p7s Description: S/MIME cryptographic signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org
Re: epel8: BuildrootError: could not init mock buildroot
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@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org
Re: epel8: BuildrootError: could not init mock buildroot
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 signature.asc Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org
Re: epel8: BuildrootError: could not init mock buildroot
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. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org
Re: epel8: BuildrootError: could not init mock buildroot
On Thu, 30 Jan 2020 at 20:49, Kevin Fenzi wrote: > On Thu, Jan 30, 2020 at 07:57:22AM -0500, Stephen John Smoogen wrote: > > On Thu, 30 Jan 2020 at 06:06, Jiri Kucera wrote: > > > > > > Hello, > > > > > > when doing `fedpkg scratch-build --target epel8-candidate --srpm > sox-14.4.2.0-29.el8.src.rpm`, I get: > > > > > > > So there seems to be something off in koji and the repo is not getting > > properly regenerated after the repo gets updated. These errors seem to > > have occurred after we updated koji to the latest release so this may > > be a change in what koji does. > > 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? > > I was trying to see how to make it fire off at the end of the script but it seemed it needed to get a kerberos ticket which I never got to figuring out. -- Stephen J Smoogen. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org
Re: epel8: BuildrootError: could not init mock buildroot
On Thu, Jan 30, 2020 at 07:57:22AM -0500, Stephen John Smoogen wrote: > On Thu, 30 Jan 2020 at 06:06, Jiri Kucera wrote: > > > > Hello, > > > > when doing `fedpkg scratch-build --target epel8-candidate --srpm > > sox-14.4.2.0-29.el8.src.rpm`, I get: > > > > So there seems to be something off in koji and the repo is not getting > properly regenerated after the repo gets updated. These errors seem to > have occurred after we updated koji to the latest release so this may > be a change in what koji does. 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 signature.asc Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org
Re: epel8: BuildrootError: could not init mock buildroot
On Thu, 30 Jan 2020 at 06:06, Jiri Kucera wrote: > > Hello, > > when doing `fedpkg scratch-build --target epel8-candidate --srpm > sox-14.4.2.0-29.el8.src.rpm`, I get: > So there seems to be something off in koji and the repo is not getting properly regenerated after the repo gets updated. These errors seem to have occurred after we updated koji to the latest release so this may be a change in what koji does. -- Stephen J Smoogen. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org
epel8: BuildrootError: could not init mock buildroot
Hello, when doing `fedpkg scratch-build --target epel8-candidate --srpm sox-14.4.2.0-29.el8.src.rpm`, I get: [] 100% 00:00:01 1.02 MiB 773.06 KiB/sec Building sox-14.4.2.0-29.el8.src.rpm for epel8-candidate Created task: 41245726 Task info: https://koji.fedoraproject.org/koji/taskinfo?taskID=41245726 Watching tasks (this may be safely interrupted)... 41245726 build (epel8-candidate, sox-14.4.2.0-29.el8.src.rpm): free 41245726 build (epel8-candidate, sox-14.4.2.0-29.el8.src.rpm): free -> FAILED: BuildrootError: could not init mock buildroot, mock exited with status 30; see root.log for more information 0 free 0 open 0 done 1 failed 41245727 rebuildSRPM (noarch): FAILED: BuildrootError: could not init mock buildroot, mock exited with status 30; see root.log for more information 41245726 build (epel8-candidate, sox-14.4.2.0-29.el8.src.rpm) failed When I investigating the logs (both `root.log` and `mock_output.log`), I found that `dnf` has problem with package downloading: Downloading Packages: Error: Error downloading packages: Status code: 404 for https://infrastructure.fedoraproject.org/repo/rhel/rhel8/koji/latest/x86_64/RHEL-8-001/non_modular/libarchive-3.3.2-7.el8.x86_64.rpm (IP: 10.5.126.23) I get the same result also with `--target epel8`. Any ideas how to resolve this issue? Regards Jiri ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org
