--- Begin Message ---
On 14/09/16 06:23, Johannes Schauer wrote:
> Hi,
>
> Quoting Emilio Pozuelo Monfort (2016-09-14 00:47:01)
>> On 11/09/16 22:04, Johannes Schauer wrote:
>>> Package: release.debian.org
>>> Severity: normal
>>> User: release.debian.org@packages.debian.org
>>> Usertags: binnmu
>>>
>>> nmu dose3_5.0.1-1 . ANY . unstable . -m "rebuild for camlzip 1.06-1"
>>
>> Can you explain why this is needed? We don't like to blindly binNMU stuff, so
>> a little explanation is always helpful.
>
> When src:dose3 (= 5.0.1-1) was originally built, it was built with src:camlzip
> (= 1.05-3) in the archive. This means that src:dose3 built libdose3-ocaml with
> a dependency on the virtual package libzip-ocaml-8wtm6 on amd64 which was
> provided by libzip-ocaml (= 1.05-3). Building the new src:camlzip release
> 1.06-1, replaced that libzip-ocaml package by a new version which now provides
> libzip-ocaml-4m8e9 on amd64. As a result, no package provides
> libzip-ocaml-8wtm6 anymore and libdose3-ocaml ocaml become uninstallable. You
> can verify this situation here:
>
> https://packages.debian.org/sid/libdose3-ocaml (it says Package not available
> next to libzip-ocaml-8wtm6)
>
> and here:
>
> https://qa.debian.org/dose/debcheck/unstable_main/1473742805/packages/libdose3-ocaml.html
>
> The situation is analogous on all other architectures than amd64.
>
> The situation arises because OCaml packages are statically linked and
> rebuilding a library requires a rebuild of all its reverse dependencies. I was
> told in #debian-ocaml that usually Stéphane Glondu would schedule OCaml binNMUs
> but he hasn't been on IRC for 3 days, so Mehdi Dogguy advised me to ask the
> release team to schedule the required binNMU of src:dose3.
>
> One practical consequence of libdose3-ocaml not being installable right now is,
> that src:botch is currently bd-uninstallable:
>
> https://buildd.debian.org/status/package.php?p=botch
Just a simple "camlzip is an ocaml package, which changes the ABI on every
release, thus needs a rebuild to pick up the updated dependency" would have been
enough ;)
I didn't realise this was ocaml related from the name.
Scheduled now.
And looks like somebody already scheduled it before me without closing this, so
it will be double fixed :P
Cheers,
Emilio
--- End Message ---