[Debian-astro-maintainers] Bug#956580: closed by Ole Streicher <olebole at debian.org> (Re: aoflagger: boost update makes aoflagger uninstallable)

[Sebastian Ramacher]

On 2020-06-03 15:41:41 +0200, Ole Streicher wrote:
> Hi Sebastian,
> 
> 
> On 15.04.20 09:45, Sebastian Ramacher wrote:
> > Looking at aoflagger's build system, it could be affected by the same
> > issues during the next Python 3 transition. The build system currently
> > doesn't ensure that the libpython and libboost-python versions are
> > compatabile. So let's keep this bug open to get this properly fixed for
> > the next Python 3 transition.
> 
> The problem now re-appears, since boost it now 1.71 by default and this
> seems to not work. Pinning it to 1.67 helps. However, I think this is
> fragile and will break in future again.
> 
> What is the right way to ensure libpython3 and libboost-python are
> compatible? What is the reason that they are not in the moment?

I'm not sure what you mean. libboost-python1.71.0 is built against
Python 3.8 only and libpython3 currently points python3.8's libpython3.

Cheers
-- 
Sebastian Ramacher
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/debian-astro-maintainers/attachments/20200603/680173db/attachment.sig>