On 2025-06-17 15:11:18 +0200, Stéphane Glondu wrote: > Hi, > > Le 13/06/2025 à 10:47, Stéphane Glondu a écrit : > > > Please go ahead with the upload and remove the moreinfo tag from > > > this unblock > > > request once the new upload has been in unstable for a few days, and > > > you think > > > it's ready to migrate. > > > > An unforeseen and unfortunate consequence is the change of the ABI hash > > of libstdlib-ocaml-dev on (at least) amd64. > > > > I've yet to understand the cause of this change. > > > > This is not due to changes introduced in 5.3.0-3, since 5.3.0-2 builds > > with the same ABI hash right now. The change must be due to some change > > elsewhere in the toolchain, between the last build of ocaml in testing > > (2025-01-27 14:44:59) and now. > > I got it. This hash is computed over compressed (zstd) data, and zstd > changed from 1.5.6+dfsg-2 to 1.5.7+dfsg-1. > > I tried compiling ocaml with --disable-zstd in today's unstable and in > stable updated to unstable snapshot of 20250127T000000Z, and I get the same > ABI hashes. Without --disable-zstd, I get the two different ABI hashes (the > current testing one and the current unstable one). > > The ABI hash being dependent of the version of zstd used at build time seems > to be a defect for me... What do you think? Should I fix it right now in > unstable? That means another round of binNMUs...
I aggree that it should be fixed, but unless there is a good reason for it (e.g., we have another zstd update for trixie), let's postpone adding --disable-zstd to forky. Best Sebastian -- Sebastian Ramacher
