On Wed, 2017-09-20 at 11:34 +0200, Sébastien Villemot wrote:
> It consists in bumping the "r-api-3" value to "r-api-3.4", or "r-api-
> 3a" (or basically whatever you want, as long as it is different from
> previous values).
>
> This takes less than 5 minutes of your time, is clean and robust, and
> solves the whole issue.
I agree that this seems to be the best solution. That was also
suggested by the release team, but for some (unexplained) reason was
not done.
> I know you don’t consider this issue as an ABI break, but this is a
> rather theoretical debate. In practice this proposed change does the
> job.
>
> Then the Release Team will schedule binNMUs for all R reverse
> dependencies, and everything will migrate to testing. Of course this
> means more rebuilds than strictly necessary, but who cares?…
> computing resources are cheap.
That is also the case for most other ABI changes: most often only a few
functions are affected, but everything has to be rebuilt when the
soname of a library changes (or the r-api-${x} here), even when not
using the interface that actually changed.
Ansgar
