Your message dated Wed, 23 Jan 2019 12:05:37 +0000
with message-id <[email protected]>
and subject line Bug#911625: fixed in boost1.67 1.67.0-12
has caused the Debian Bug report #911625,
regarding libboost-python1.62.0: insufficient python dependencies allow early 
upgrade, breaking stretch->buster upgrades
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
911625: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911625
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: libboost-python1.62.0
Version: 1.62.0+dfsg-10
Severity: serious
User: [email protected]
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

Attachment: libcasa-measures2_2.4.1-3+b1.log.gz
Description: application/gzip


--- End Message ---
--- Begin Message ---
Source: boost1.67
Source-Version: 1.67.0-12

We believe that the bug you reported is fixed in the latest version of
boost1.67, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Giovanni Mascellani <[email protected]> (supplier of updated boost1.67 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Wed, 23 Jan 2019 12:14:16 +0100
Source: boost1.67
Architecture: source
Version: 1.67.0-12
Distribution: unstable
Urgency: medium
Maintainer: Debian Boost Team <[email protected]>
Changed-By: Giovanni Mascellani <[email protected]>
Closes: 903665 911625
Changes:
 boost1.67 (1.67.0-12) unstable; urgency=medium
 .
   * Add patch to fix FTBFS of package bali-phy on ppc64* (closes: #903665).
   * Ignore file .gitlab-ci.yml when creating the source package.
   * Expose supported Python version as virtual packages, so that reverse
     dependencies can depend on the right package (closes: #911625).
   * Work around broken architecture detection under x32.
Checksums-Sha1:
 010490cc2f68af5da6179f70d2c619724384a89f 7762 boost1.67_1.67.0-12.dsc
 51cecbfd577c053f3c777ae1d70c2eeaba47b462 350376 
boost1.67_1.67.0-12.debian.tar.xz
 a2a97b6540f9222e92e99b26cce2fe8a22b926c6 13509 
boost1.67_1.67.0-12_source.buildinfo
Checksums-Sha256:
 9531e37531570c127583550bd62424435ba81ce6ee6b3d42a48e1f8ec84e2c46 7762 
boost1.67_1.67.0-12.dsc
 9ebdf1b04e056d11feb80ba3a22122293a8ee6b0a62f7ad21bdc2296dce37d67 350376 
boost1.67_1.67.0-12.debian.tar.xz
 b375cdfedb591193f2cfe0cd9d8a2b83c4e73a0a9c1552fcab4acb4cd2fc4a76 13509 
boost1.67_1.67.0-12_source.buildinfo
Files:
 63b8e2d7ee079443d90b27db41883323 7762 libs optional boost1.67_1.67.0-12.dsc
 cea8714ec5e81d1dd1a14f22991e65d2 350376 libs optional 
boost1.67_1.67.0-12.debian.tar.xz
 487de9e728dde30fd48738c7af24ec02 13509 libs optional 
boost1.67_1.67.0-12_source.buildinfo

-----BEGIN PGP SIGNATURE-----

iHUEARYKAB0WIQSiBF6hBvCQNcghJEaNr8EMz954SQUCXEhM5wAKCRCNr8EMz954
SSEHAP0bWyhlR/VmyKxzfB/KplNO12HLpuOyu/QBeY++9q1s1wEApiH8c+nMkYqn
ZRrel+KY+ozbXKjDMstQp5HRlVffTwY=
=7Iya
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to