From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mail3-relais-sop.national.inria.fr (mail3-relais-sop.national.inria.fr [192.134.164.104])
	by walapai.inria.fr (8.13.6/8.13.6) with ESMTP id p477Oe1W006441
	for <caml-list@sympa-roc.inria.fr>; Sat, 7 May 2011 09:24:40 +0200
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AroBAHrzxE2BaB4imWdsb2JhbACYMo1tFAEBAQEBCAsLBxQliHG8UA6FfQSePg
X-IronPort-AV: E=Sophos;i="4.64,330,1301868000"; 
   d="scan'208";a="82538090"
Received: from mx1.polytechnique.org ([129.104.30.34])
  by mail3-smtp-sop.national.inria.fr with ESMTP/TLS/ADH-AES256-SHA; 07 May 2011 09:24:35 +0200
Received: from gavalla (bne75-13-78-249-168-217.fbx.proxad.net [78.249.168.217])
	(using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits))
	(No client certificate requested)
	by ssl.polytechnique.org (Postfix) with ESMTPSA id A238E1400829A
	for <caml-list@inria.fr>; Sat,  7 May 2011 09:24:34 +0200 (CEST)
Date: Sat, 7 May 2011 09:24:30 +0200
From: Virgile Prevosto <virgile.prevosto@m4x.org>
To: caml-list@inria.fr
Message-ID: <20110507092430.3de33a0c@gavalla>
In-Reply-To: <op.vu2xcbi2soui26@mail.gmx.net>
References: <BANLkTinkBbiVB+dEBTGm=yMiD_n0Vzvatg@mail.gmail.com>
	<op.vu2xcbi2soui26@mail.gmx.net>
X-Mailer: Claws Mail 3.7.9 (GTK+ 2.24.3; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
X-AV-Checked: ClamAV using ClamSMTP at svoboda.polytechnique.org (Sat May  7 09:24:34 2011 +0200 (CEST))
X-Spam-Flag: No, tests=bogofilter, spamicity=0.156456, queueID=D7925140082A5
X-Org-Mail: virgile.prevosto.1996@polytechnique.org
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by walapai.inria.fr id p477Oe1W006441
Subject: Re: [Caml-list] Warning: Ubuntu 11.04 Vs OCaml 3.12.0

Le ven. 06 mai 2011 23:44:25 CEST,
"Till Crueger" <Till.Crueger@gmx.net> a écrit :

> Too late... I already upgraded all my computers and lots of things
> seem to be broken with Natty Narwhale. Just as another warning for
> those considering it right now.
> 
> Is there any indication as to when this will be fixed in GODI?

In principle, this is already the case (packages godi-ocaml-src and
godi-ocaml 3.12.0#2 and 3.11.2#1 for sections 3.12 and 3.11
respectively).

-- 
E tutto per oggi, a la prossima volta.
Virgile