From: Richard Jones <rich@annexia.org>
To: Damien Doligez <Damien.Doligez@inria.fr>
Cc: caml announce <caml-announce@inria.fr>, caml users <caml-list@inria.fr>
Subject: Re: [Caml-list] [ANN] Release Candidate: 3.11.2+rc1
Date: Tue, 5 Jan 2010 15:12:19 +0000 [thread overview]
Message-ID: <20100105151218.GA20201@annexia.org> (raw)
In-Reply-To: <20091229165200.GA22924@annexia.org>
On Tue, Dec 29, 2009 at 04:52:00PM +0000, Richard Jones wrote:
> On Tue, Dec 29, 2009 at 03:59:34PM +0100, Damien Doligez wrote:
> > The release candidate is available as source code at this address:
> > ftp://ftp.inria.fr/INRIA/Projects/cristal/ocaml/ocaml-3.11/ocaml-3.11.2+rc1.tar.bz2
> >
> > See the list of changes at the end of this mail.
> >
> > After testing this release candidate, please send a mail to
> > <damien.doligez@inria.fr> and tell us what you tested and whether
> > it worked.
>
> I've pushed this out to Fedora Rawhide users after some very light
> testing myself. If there are any major problems we should see reports
> from QA systems and users in a day or two.
Following up, two packages had problems building:
camlp5 - When you compile, it complains it doesn't know anything about
3.11.2 and that this will require an upstream change.
cduce - Also FTBFS.
I have not looked any deeper into either of these build problems at
the moment.
Everything else built fine.
Rich.
--
Richard Jones
Red Hat
next prev parent reply other threads:[~2010-01-05 15:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-29 14:59 Damien Doligez
2009-12-29 16:10 ` [Caml-list] " Stéphane Glondu
2009-12-29 16:52 ` Richard Jones
2010-01-05 15:12 ` Richard Jones [this message]
2010-01-05 17:06 ` Stéphane Glondu
2010-01-05 17:20 ` Richard Jones
2010-01-05 18:43 ` Richard Jones
2009-12-30 17:32 ` David Allsopp
2010-01-11 18:33 ` Richard Jones
2010-01-12 10:11 ` Damien Doligez
2010-01-12 10:30 ` Sylvain Le Gall
2010-01-12 10:44 ` [Caml-list] " Damien Doligez
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100105151218.GA20201@annexia.org \
--to=rich@annexia.org \
--cc=Damien.Doligez@inria.fr \
--cc=caml-announce@inria.fr \
--cc=caml-list@inria.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox