Bug#755094: transition: harfbuzz
On 17/07/14 18:56, أحمد المحمودي wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian.org@packages.debian.org
> Usertags: transition
>
> Transition is due to upstream API change: replacement of
> 'hb_version_check' with 'hb_version_atleast'.
That function is trivial. I'm wondering if we couldn't reintroduce in a patch
and avoid the package rename. Then 0.9.32 can go to unstable/testing right away.
The next time upstream breaks the ABI (probably during jessie+1) we can remove
the patch and thus the symbol.
The reason why I'm thinking about avoiding the transition is that it won't be
"smooth", i.e. harfbuzz and all the rdeps need to transition *together*. So one
FTBFS problem on any architecture will block the whole transition. And the
affected packages include libreoffice, qtbase-opensource-src, chromium-browser,
webkitgtk... which are huge. And e.g. chromium-browser has a FTBFS bug, which
would block the transition. There may be others.
If the transition was "smooth" (because there weren't conflicts on the old
package) it would be ok. But this late on the cycle, with a few big transition
coming up (one of them being librevenge/libreoffice) I wonder if we shouldn't
revert the ABI break instead.
Thoughts?
Emilio
Reply to: