No, All packages that use python have removal blocks already filed, and those bugs should be marked as blocking migration of boost.
It will take a while for boost to migrate. There are only a few applications, a few dual py2/py3 packages, and majority already scheduled to be removed from the archive with RC bugs. All the broken packages, are RC buggy themselves already. Anything that is using py2 is RC buggy. And e.g. ledger, I started porting it locally. The buggy app here is ledger. On Sun, 1 Dec 2019, 18:57 Giovanni Mascellani, <g...@debian.org> wrote: > Hi, > > On Fri, 29 Nov 2019 16:42:58 +0100 Kiko Piris > <kiko+deb...@pirispons.net> wrote:> /usr/bin/ledger: error while loading > shared libraries: libboost_python27.so.1.67.0: cannot open shared object > file: No such file or directory > > Dimitri, it seems that removing Python 2 support for Boost 1.67 was a > bit too quick. Apparently some packages are still using it, so this is > causing breakages. Therefore I will upload a new version that re-enables > Python 2. Of course Python 2 should never be enabled from Boost 1.71 on. > > Also, could you please check that you pushed 1.67.0-15 to the git > repository? I cannot see it. > > Of course, reverse dependencies of Boost 1.67 be aware that you will > break when 1.71 will be made the default Boost version, which hopefully > will be relatively soon. > > Giovanni. > -- > Giovanni Mascellani <g.mascell...@gmail.com> > Postdoc researcher - Université Libre de Bruxelles > >
