On Thu, Feb 27, 2020 at 11:47 AM Richard W.M. Jones <rjones@xxxxxxxxxx> wrote: > > On Mon, Feb 24, 2020 at 08:56:04AM +0000, Richard W.M. Jones wrote: > > OCaml 4.10.0 was released over the weekend. > > > > We currently have OCaml 4.10.0 beta 1 in Rawhide. It's not that far > > away from 4.10.0. Unfortunately since building beta 1, Fedora 32 was > > forked from Rawhide so we now have the beta 1 build in Fedora 32 as > > well. > > > > Hopefully the plan is as follows: > > > > (1) Rebuild OCaml 4.10.0 in a side tag then move it to Rawhide. I > > don't expect any difficulties here since all the hard work was already > > done when I built beta 1. > > It was rather more painful than I thought it would be, but it's done > now. > > The major highlights were: > > - coccinelle still FTBFS as before > - opam FTBFS: seems to be an unpackaged dependency > - plplot FTBFS: nothing unusual there > - I didn't try to build the coq part of the stack at all > > > (2) Merge all those changes into the f32 branches of the ocaml* > > packages. > > I will do this next. > > > (3) (This is where it gets more speculative because my mass rebuild > > script has only ever been run against Rawhide ...) Rebuild in a side > > tag of Fedora 32, and if that goes well then merge the side tag in > > F32. (snip) > This is where I might need help. I have a few questions: > > - There was something go on with Bodhi a few days ago which meant > that you didn't want me to start this. Can I start now? > > - Do I need to submit Bodhi updates for each build? (Note I'll be > building into an f32 side tag) > > - If yes to the previous, can I short-circuit the need to wait for > Bodhi updates? I really hope I don't have to wait for each update > to go through. > > Rich. Yeah, because the updates-testing activation happened, which means that just submitting builds is not enough anymore. If you did things "normally", you'd need to create buildroot overrides for each build, wait, submit the next build, and repeat - which is obviously a painful process. But since you're using a side tag, you should not need to create either buildroot overrides or individual updates, but just build everything in the side tag and create an update from the side tag contents. However, I'm not sure if bodhi can do that for non-rawhide branches yet. I also think this is only possible with the bodhi CLI, not from the web interface ... I hope somebody else can fill in the details here, this is all pretty new stuff and I haven't yet had a chance to create side-tag updates in bodhi myself. Fabio > -- > Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones > Read my programming and virtualization blog: http://rwmj.wordpress.com > libguestfs lets you edit virtual machines. Supports shell scripting, > bindings from many languages. http://libguestfs.org > _______________________________________________ > 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 _______________________________________________ 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
