Ocaml-4.02 was removed a few months ago in c3634df2 but I forgot to close this
bug report.
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
Le 19 février 2019 23:17:52 GMT+01:00, Andreas Enge a écrit :
>On Thu, Jan 31, 2019 at 06:30:27PM +0100, Julien Lepiller wrote:
>> I still care about ocaml-4.02, but I could probably update it to
>ocaml-4.04 without breaking dependents.
>
>Commits 2e125ece093ef842ca017ffb146cbc5fa33f2f75 and
On Thu, Jan 31, 2019 at 06:30:27PM +0100, Julien Lepiller wrote:
> I still care about ocaml-4.02, but I could probably update it to ocaml-4.04
> without breaking dependents.
Commits 2e125ece093ef842ca017ffb146cbc5fa33f2f75 and
4982c0c98deecea0d4f69f14ea28cab53b5f2123 remove ocaml@4.01, pplacer
Le 31 janvier 2019 18:21:13 GMT+01:00, Andreas Enge a écrit :
>On Thu, Jan 31, 2019 at 05:57:03PM +0100, Andreas Enge wrote:
>> Are people using the software
>
>I suppose not, because one of its dependencies currently does not
>build:
>
>...
>phase `ocaml-findlib-environment' succeeded after 0.0
On 2019-01-31 17:57, Andreas Enge wrote:
Hello,
this bug has been open for quite a while, and the development of pplacer seems
to be stalled, with the latest commit in May 2018, and no reaction whatsoever
to Ben's bug report
https://github.com/matsen/pplacer/issues/354
How should we
On Thu, Jan 31, 2019 at 05:57:03PM +0100, Andreas Enge wrote:
> Are people using the software
I suppose not, because one of its dependencies currently does not build:
...
phase `ocaml-findlib-environment' succeeded after 0.0 seconds
starting phase `configure'
build directory:
Hello,
this bug has been open for quite a while, and the development of pplacer seems
to be stalled, with the latest commit in May 2018, and no reaction whatsoever
to Ben's bug report
https://github.com/matsen/pplacer/issues/354
How should we continue? Are people using the software, or should
On Sat, Jun 24, 2017 at 10:25:52AM +1000, Ben Woodcroft wrote:
> On 24/06/17 02:41, Leo Famulari wrote:
> > Our package ocaml-4.01 is vulnerable to CVE-2015-8869, which we patched
> > in the primary ocaml package in April 2016. Unfortunately, this patch
> > was not included when the ocaml-4.01
Hi Leo,
On 24/06/17 02:41, Leo Famulari wrote:
Our package ocaml-4.01 is vulnerable to CVE-2015-8869, which we patched
in the primary ocaml package in April 2016. Unfortunately, this patch
was not included when the ocaml-4.01 package was created in January
2017.
Our package ocaml-4.01 is vulnerable to CVE-2015-8869, which we patched
in the primary ocaml package in April 2016. Unfortunately, this patch
was not included when the ocaml-4.01 package was created in January
2017.
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-8869
Do we need this
11 matches
Mail list logo
