Package: libboost-python1.62.0 Version: 1.62.0+dfsg-10 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Control: affects -1 + libcasa-measures2
Hi,
during a test with piuparts I noticed your package causes other packages
to fail to upgrade from 'stretch'.
It installed fine in 'stretch', then the upgrade to 'buster' fails.
>From the attached log (scroll to the bottom...):
Setting up casacore-data-tai-utc (1.2) ...
Traceback (most recent call last):
File "/usr/bin/casacore-update-tai_utc", line 11, in <module>
from casacore import tables
File "/usr/lib/python3/dist-packages/casacore/tables/__init__.py", line 60,
in <module>
from .table import table
File "/usr/lib/python3/dist-packages/casacore/tables/table.py", line 44, in
<module>
from ._tables import Table
ImportError: libboost_python-py35.so.1.62.0: cannot open shared object file:
No such file or directory
dpkg: error processing package casacore-data-tai-utc (--configure):
subprocess installed post-installation script returned error exit status 1
This is a upgrade test of stretch/amd64 with --install-recommends enabled.
It failed during 'apt-get upgrade'. At the point of failure the following
relevant packages are installed:
# dpkg -l | grep python | cut -c-60
ii dh-python 3.20180927 all
ii libboost-python1.62.0 1.62.0+dfsg-10 amd64
ii libcasa-python3-2:amd64 2.2.0-2 amd64
ii libpython3-stdlib:amd64 3.5.3-1 amd64
ii libpython3.5:amd64 3.5.3-1 amd64
ii libpython3.5-minimal:amd64 3.5.3-1 amd64
ii libpython3.5-stdlib:amd64 3.5.3-1 amd64
ii python3 3.5.3-1 amd64
ii python3-casacore 2.1.2-3+b1 amd64
ii python3-minimal 3.5.3-1 amd64
ii python3-numpy 1:1.12.1-3 amd64
ii python3-pkg-resources 40.2.0-1 all
ii python3-six 1.11.0-2 all
ii python3.5 3.5.3-1 amd64
ii python3.5-minimal 3.5.3-1 amd64
i.e. libboost-python1.62.0 is already upgraded to buster
while python3 is still python3.5 from stretch.
The dependency chain starting from casacore-data-tai-utc looks as follows:
Package: casacore-data-tai-utc
Status: install ok half-configured
Architecture: all
Version: 1.2
Config-Version: 1.1
Depends: python3, python3-casacore, tzdata
Package: python3-casacore
Status: install ok installed
Architecture: amd64
Source: python-casacore (2.1.2-3)
Version: 2.1.2-3+b1
Provides: python3.5-casacore
Depends: python3-numpy, python3-six, python3 (<< 3.6), python3 (>= 3.5~),
python3-pkg-resources, python3:any (>= 3.4~), libboost-python1.62.0, libc6 (>=
2.14), libcasa-casa2, libcasa-coordinates2, libcasa-fits2, libcasa-images2,
libcasa-lattices2, libcasa-measures2, libcasa-mirlib2, libcasa-python3-2,
libcasa-scimath-f2, libcasa-scimath2, libcasa-tables2, libgcc1 (>= 1:4.0),
libstdc++6 (>= 5.2)
Package: libboost-python1.62.0
Status: install ok installed
Architecture: amd64
Source: boost1.62
Version: 1.62.0+dfsg-10
Depends: libc6 (>= 2.14), libgcc1 (>= 1:3.0), libstdc++6 (>= 5.2)
Suggests: python, python3
Just an idea, do not know if this can be implemented efficiently:
If libboost-python1.62.0 provides pythonX.Y-libboost-python1.62.0
and the consumers depend on pythonX.Y-libboost-python1.62.0 instead of
(or in addition to) libboost-python1.62.0, everything should be fine.
As a workaround you could add
Breaks: python3-casacore (<< 2.2.0)
(and probably some more in case I hit them)
to libboost-python1.62.0 (2.2.0-1 was the first version built without
python3.5 support).
No need to carry this Breaks over to newer boost versions.
cheers,
Andreas
libcasa-measures2_2.4.1-3+b1.log.gz
Description: application/gzip
