Bug#960193: transition: icu
On Mon, 11 May 2020 at 13:26, Adrian Bunk <bunk@debian.org> wrote:
>
> On Mon, May 11, 2020 at 12:59:07PM +0100, Dimitri John Ledkov wrote:
> > On Mon, 11 May 2020 at 12:34, Adrian Bunk <bunk@debian.org> wrote:
> > >
> > > On Sun, May 10, 2020 at 03:40:43PM +0200, László Böszörményi wrote:
> > > >....
> > > > Level 1.5 is needed for Boost packages to be binNMUed:
> > > > Both boost1.67 and boost1.71 build correctly.
> > > >...
> > >
> > > Changing the icu version changes the libboost_regex ABI.
> > >
> > > The libboost-regex*-icu* provides untangle icu transitions from boost
> > > transitions, but reverse dependencies of libboost-regex1.67.0 in buster
> > > depend on libboost-regex1.67.0 not libboost-regex1.67.0-icu63.
> >
> > If icu in unstable could add Breaks: libbost-regex1.67-0 (<<
> > 1.67.0-141) that should be sufficient to ensure upgrades happen the
> > right way around from buster.
>
> This is only true for upgrades from buster that happen after
> libbost-regex1.67-0 has been removed from unstable and testing.
>
> The safe way is:
>
> > Alternatively, we should work on removing boost1.67 in unstable &
> > testing. It should not ship.
> >...
>
> Is there a good reason why the boost 1.67 -> 1.71 transition has already
> happened in Ubuntu but not yet in Debian?
>
At this point, it seems like sticking to 1.67 is doing more harm than good.
We have many patches to address FTBFS so it should be relatively painless.
--
Regards,
Dimitri.
Reply to: