[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#899189: nmu: unison_2.48.3-1



Hi,

Stéphane Glondu <glondu@debian.org> (2018-05-20):
> Currently, Unison in Stretch is compiled with OCaml 4.01.0 (at least
> on i386), while OCaml in Stretch is 4.02.3. This triggers a subtle
> interoperability bug more often than it should, and led to too much
> lost time in my opinion (e.g. see [1] and [2]).
> 
> [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=802919
> [2] https://github.com/bcpierce00/unison/issues/94
> 
> I don't know if it is acceptable to do binNMUs in stable (I probably
> can do it myself), so I'm asking here :-)
> 
> nmu unison_2.48.3-1 . ANY . stretch . -m "Recompile with ocaml version in stretch"

For the sake of completeness, here's an extra data point. If someone
ends up with two peers with versions 2.48.3-1 vs. 2.48.3-1+b1 (hosts
with s-p-u enabled, but not dist-upgraded at the same time), one can
get this very issue:
| Uncaught exception Failure("input_value: bad bigarray kind")

with extra unfriendly debug messages (hey, look at those in the github
bug tracker, the ones we wanted to get rid of).

I thought I'd mention the possibly surprising outcome for people not
following debian-release@ closely.


Cheers,
-- 
Cyril Brulebois (kibi@debian.org)            <https://debamax.com/>
D-I release manager -- Release team member -- Freelance Consultant

Attachment: signature.asc
Description: PGP signature


Reply to: