+1 On Sat, 30 Mar 2019 at 13:53, Kevin Fenzi <kevin@xxxxxxxxx> wrote: > > On 3/29/19 1:33 PM, Jonathan Dieter wrote: > > On Mon, 2019-03-11 at 20:23 +0000, Jonathan Dieter wrote: > >> On Mon, 2019-03-11 at 11:24 -0700, Kevin Fenzi wrote: > >>> On 3/11/19 12:26 AM, Jonathan Dieter wrote: > >>>> This adds zchunk support for the updates and updates-testing > >>>> repositories for both rpms and modularity. We already have zchunk > >>>> metadata being generated for the fedora repository. I'd like to > >>>> get this in before Beta comes out so Beta users will have zchunk- > >>>> enabled updates-testing repositories when Beta is released. > >>> > >>> yeah, hopefilly not too much pain since it's been in rawhide a while now. > >>> > >>>> I am making the assumption that a zchunk-enabled createrepo_c (0.12.0-2 > >>>> or later) is available on the builders (I think I'm safe making that > >>>> assumption, since zchunk metadata is already being generated for some > >>>> repos). > >>> > >>> Well, bodhi-backend01 (where the updates process/pungi runs for these) > >>> has a newer one, so yes. It's all run on bodhi-backend01, not builders. > >>> > >>>> I have *not* tested this patch, because I'm not sure how I'd go about > >>>> doing so. If we don't have any test builders, my suggestion would be > >>>> to wait until no compose is running, and then run this play on a > >>>> builder, verifying that the generated pungi configuration is valid for > >>>> both f29 and f30, with no createrepo_extra_args in f29. > >>> > >>> yeah, we can commit this, run the playbook then examine the results. > >> > >> Great. I'm on UTC time right now, so hopefully I'll be off of work and > >> available if there are any issues whenever we get another +1 and you > >> run it. I do expect that it will go fine. > > > > Since we never got the extra +1 to get this in before Beta, are we at a > > point where we can turn this on now? > > Nope, we are still frozen until the day after beta release. ;( > > But I will try and scare up another +1 > > kevin > > > _______________________________________________ > infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx -- Stephen J Smoogen. _______________________________________________ infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
