Bug#868558: nmu: multiple r-* packages
On 09/09/17 13:48, Dirk Eddelbuettel wrote:
>
> On 9 September 2017 at 06:44, Niels Thykier wrote:
> | Thanks to Sébastien and Andreas for explaining the issue.
>
> Well, was it "explained" ? They both raised and stressed a hypothetical
> issue: That "there might be siutations where a partial upgrade breaks"
>
> We don't actually know whether this holds. This R 3.4.* change was not a
> full-fledged ABI change.
>
> | That is fine. Then (to my knowledge) your only option is an "ABI bump".
>
> I still disagree, for this case.
>
> We will likely need one for anticipated internal R changes by R 3.5.0.
>
> | Until one of these solutions is applied, this bug is "wontfix" and
> | r-base is blocked from migrating to testing.
>
> I think this is a dissservice to our users.
The only disservice here is that you refuse to prevent users from getting broken
systems due to this ABI break. This is particularly surprising given the simple
fix (adding breaks) and that Sébastien is offering you a patch.
This is no different from someone breaking a shared library ABI, say libfoo0,
and then asking for rebuilds of the rdeps, and refusing to bump the SONAME,
rename the package or add breaks against the non-rebuilt rdeps. That would be
unacceptable, and so is your case.
As it was pointed out, look at the recent Python extension ABI break that was
quickly fixed by adding Breaks and scheduling a bunch of binNMUs.
Cheers,
Emilio
Reply to: