On Sat, 06 Jun 2020 09:47:57 -0400 John Scott <jsc...@posteo.net> wrote:
> Control: forwarded -1
https://lists.gforge.inria.fr/pipermail/frama-c-discuss/2020-June/005823.html
> Control: tags -1 fixed-upstream
>
> I'm having trouble finding their VCS and what commit fixed this, but
updating
> Frama-C to the beta should be sufficient. Unstable and testing
already have
> Why3 >= 1.3.
For information, the Frama-C public VCS (git) is available at:
https://git.frama-c.com/pub/frama-c/-/tree/master
There is no specific commit which updated compatibility from Why3 1.2 to
Why3 1.3 (there is an entire branch with several commits related to it),
but https://git.frama-c.com/pub/frama-c/-/commit/1c7acc37c44f914f60a27
would be close.
In any case, thanks for looking into this, and please tell us if there's
anything we can do to help fix the frama-c package on Debian testing.
--
André Maroneze, for the Frama-C team