From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andreas Enge Subject: bug#27462: OCaml CVE-2015-8869 Date: Wed, 20 Feb 2019 12:27:47 +0100 Message-ID: <20190220112747.GA21689@jurong> References: <20190131165613.GA27597@jurong> <20190131172113.GA29071@jurong> <96513178-922C-49D6-AF32-0EF723343C8E@lepiller.eu> <20190219221752.GA4351@jurong> <5510C5B2-07EA-4D26-9629-1403237F6751@lepiller.eu> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([209.51.188.92]:59579) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gwQ2l-000361-8k for bug-guix@gnu.org; Wed, 20 Feb 2019 06:28:03 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gwQ2k-0002R8-Ir for bug-guix@gnu.org; Wed, 20 Feb 2019 06:28:03 -0500 Received: from debbugs.gnu.org ([209.51.188.43]:56454) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1gwQ2k-0002Qn-1Y for bug-guix@gnu.org; Wed, 20 Feb 2019 06:28:02 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1gwQ2j-0002s7-KD for bug-guix@gnu.org; Wed, 20 Feb 2019 06:28:01 -0500 Sender: "Debbugs-submit" Resent-Message-ID: Content-Disposition: inline In-Reply-To: <5510C5B2-07EA-4D26-9629-1403237F6751@lepiller.eu> List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: Julien Lepiller Cc: 27462@debbugs.gnu.org On Wed, Feb 20, 2019 at 09:39:20AM +0100, Julien Lepiller wrote: > At this point, we only need it for bap and dependencies. I've added dependencies for the latest bap commit that work with the latest ocaml, but they haven't released a new version yet. Can we wait a bit longer? > > Another solution would be to jump to ocaml 4.05 and re-package another version of ~50 dependencies. I don't really want to do that… I understand! Waiting a bit more should be okay given how long this bug is already open... Or packaging a current snapshot of bap (with suitable numbering as laid out, I think, in the documentation, so that users will upgrade automatically from the current version over the snapshot to the next released version). Thanks, Andreas