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

Bug#1034691: marked as done (nmu: why3_1.5.1-1+b1 frama-c_20220511-manganese-3-10)

Your message dated Wed, 3 May 2023 22:35:45 +0200
with message-id <ZFLFobAzwJtYT6zw@ramacher.at>
and subject line Re: Bug#1034691: nmu: why3_1.5.1-1+b1 frama-c_20220511-manganese-3-10
has caused the Debian Bug report #1034691,
regarding nmu: why3_1.5.1-1+b1 frama-c_20220511-manganese-3-10
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
1034691: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034691
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: binnmu
X-Debbugs-Cc: why3@packages.debian.org
Control: affects -1 + src:why3 src:frama-c

Hi release team,

can you please binNMU why3 to pick up the new ABI:

nmu why3_1.5.1-1+b1 . ANY . unstable . -m "Rebuild with new OCaml ABI"

And afterwards frama-c needs a rebuild against the new why3:

nmu frama-c_20220511-manganese-3-10 . ANY . unstable . -m "Rebuild with new OCaml ABI (Closes: #1033701)"

Thanks!

Jochen

--- End Message ---
--- Begin Message --- 
On 2023-05-02 12:08:08 +0200, Stéphane Glondu wrote:
> Dear Sebastian,
> 
> Le 23/04/2023 à 11:36, Sebastian Ramacher a écrit :
> > ocaml 4.13.1-4 causes the ABI to change for at least why3. Do you expect
> > that the ABI of ther ocaml packages also changes? If so, we should
> > rebuild the ocaml world before the release to not get any surprises if a
> > ocaml package gets a stable update.
> 
> See also:
> 
>   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030785
> 
> The ABI of ocaml-compiler-libs changed (only on native architectures), with
> no visible changes in virtual packages, so anything using that is
> potentially broken. I (thought I) binNMUed all affected packages (there were
> a lot of them), but missed why3 for some reason.
> 
> IMHO, the cleanest way to fix the issue for sure is to change the OCaml ABI
> advertised in the virtual package name. But that means an amount of work
> similar to an OCaml transition. Do we really work this kind of move at this
> stage of the freeze? I don't think so.

Probably not, but please fix that in trixie. For now, I've scheduled the
rebuilds of why3 and frama-c.

Cheers

> 
> A pretty good approximation to checking that everything is fine is to
> mass-rebuild everything (as Lucas Nussbaum does regularly), identify the
> (few, I expect) packages that FTBFS, and binNMU them (+ maybe some of their
> dependencies). I suspect why3 is special because it embeds modules provided
> by ocaml in a plugin (dh_ocaml's --nodefined-map is suspicious in this
> context) but this situation should be rare.
> 
> 
> Cheers,
> 
> -- 
> Stéphane
> 

-- 
Sebastian Ramacher

--- End Message ---
Reply to: