Re: FYI: OCaml 4.10.0 beta1 will go into Fedora 32 soonish

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

 



On Sat, Jan 18, 2020 at 10:30 PM Richard W.M. Jones <rjones@xxxxxxxxxx> wrote:
>
> On Sat, Jan 18, 2020 at 04:38:27PM +0100, Fabio Valentini wrote:
> > On Sat, Jan 18, 2020 at 1:09 PM Richard W.M. Jones <rjones@xxxxxxxxxx> wrote:
> > >
> > > OCaml 4.10.0 beta1 was released upstream about a week ago
> > > (https://bugzilla.redhat.com/show_bug.cgi?id=1673688).  I'm intending
> > > to build OCaml packages into a side tag starting today, and then
> > > if it seems to work well integrate it into F32.
> > >
> > > The release notes for this are here:
> > >
> > >   https://github.com/ocaml/ocaml/blob/4.10/Changes
> > >
> > > Please note there are some incompatible changes.  The ones which I
> > > think may affect Fedora are below (but there are more, please read the
> > > release notes in full):
> >
> > How will this change the number of OCaml packages that are already
> > broken in rawhide? Will it get better or worse with this rebuild?
> > There seem to be a number of OCaml packages that haven't even been
> > built with either 4.08 or 4.09 yet.
> >
> > OCaml packages cause most of the "broken dependencies" in rawhide
> > right now, and drown out almost everything else:
> > See: https://pagure.io/fedora-health-check/blob/master/f/reports/report-rawhide.md
>
> This is the first I've heard of this.  I can't fix stuff I don't
> know about!

Sure, no pressure - just wanted to make sure you know about it.

> I've just looked at the link you posted, and it seems a bit "biased"
> to OCaml packages because of the way that Fedora packages encode OCaml
> dependencies into RPM dependencies, resulting in many ocaml(Stdlib_*)
> dependencies which are essentially saying the same thing.

Yeah, that's what I figured after looking at the list.
RPM seems to generate large number of AutoProv / AutoReq entries for a
small number of packages, which skews the statistics.

> There are many packages in the list which are orphaned, especially all
> the camlp4 deprecations[1].  Those should be ignored IMO.

Erm ... none of the packages with broken dependencies is orphaned right now.
Looking at Miro's "orphaned packages report", not a single OCaml
package is orphaned right now.
Unless you meant to say that the *missing* things are caused by
packages that were orphaned and then retired (which is a different
issue ...)

> As for the rest, not sure I can action anything unless I can get a
> list of actually broken packages which are not orphaned.  But don't do
> anything until the current rebuild is out of the way.

Looking at the current report, these are the currently broken OCaml
packages (be it FTBFS or FTI), keyed by primary POC:

andyli: ocaml-benchmark, ocaml-rope
avsej: utop
defolos: ocaml-bin-prot, ocaml-deriving
orion: ocaml-plplot
rjones: ocaml-curl, ocaml-json-wheel, ocaml-ocamlnet, ocaml-pxp,
ocaml-ulex, ocaml-xmlrpc-light
tc01: ocaml-dose3, ocaml-lambda-term, ocaml-lwt-log
(orphan: ---)

And don't worry, the report is purely informational. I won't do anything :)
The data does not inform any actions, beside me filing BugZilla
reports for new and obvious breakages when I see them.
I try to generate the report daily, so obvious issues and oversights
can get reported and fixed in a timely fashion.

> About the current rebuild: I finally fixed a bunch of problems with my
> rebuild script (which I'm writing at the same time, see [2]) - but now
> Koji seems to be actually broken ...

Sounds interesting!
Koji might suffer from the database dump cron job ... though I'm not
sure at which time of day it's supposed to run.

Fabio

> Rich.
>
> [1] https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx/message/G2JBIWB423ECYGBXZ3QCPR7NQ66XGXTU/
>
> [2] https://rwmj.wordpress.com/2020/01/14/goals-an-experimental-new-tool-which-generalizes-make/
>
>
> --
> Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
> Read my programming and virtualization blog: http://rwmj.wordpress.com
> virt-top is 'top' for virtual machines.  Tiny program with many
> powerful monitoring features, net stats, disk stats, logging, etc.
> http://people.redhat.com/~rjones/virt-top
> _______________________________________________
> 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




[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