RM boost1.63, never default 1.65.1 is in

Bug #1729090 reported by Dimitri John Ledkov
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
boost1.63 (Ubuntu)
Fix Released
High
Unassigned

Bug Description

RM boost1.63, was not default 1.65.1 is in.

No reverse dpeneds, just itself on to itself, and one alternative build-dep.

$ reverse-depends src:boost1.63
Reverse-Depends
===============
* libboost-python1.63-dev (for libboost1.63-dev)
* libboost-python1.63-dev (for libboost-python1.63.0)
* libboost-random1.63.0 (for libboost-system1.63.0)
* libboost-wave1.63-dev (for libboost-filesystem1.63-dev)
* libboost-wave1.63-dev (for libboost-serialization1.63-dev)
* libboost-wave1.63-dev (for libboost1.63-dev)
* libboost-wave1.63.0 (for libboost-system1.63.0)
* libboost-wave1.63.0 (for libboost-thread1.63.0)

Packages without architectures listed are reverse-dependencies in: amd64, arm64, armhf, i386, ppc64el, s390x

$ reverse-depends -b src:boost1.63
Reverse-Build-Depends
=====================
* magics++ (for libboost1.63-dev)

$ chdist apt-cache bionic showsrc magics++ | grep boost1.63
Build-Depends: debhelper (>= 10), dh-buildinfo, gfortran, cmake, chrpath, dh-python, swig, python-dev, python-numpy, python3-dev, python3-numpy, libhdf5-serial-dev | libhdf5-dev, libnetcdf-dev, libnetcdf-cxx-legacy-dev, libgl1-mesa-dev, libgd-dev, libemos-dev (>= 2:4.3.9), libgeotiff-dev, libeccodes-dev | libgrib-api-dev (>= 1.14.5-2), libeccodes-tools | libgrib-api-tools, libemos-bin, libopenjp2-7-dev, libaec-dev, libterralib-dev, libcairo2-dev, libpango1.0-dev, ttf-dejavu-core, libxml-parser-perl, ghostscript, zlib1g-dev, libboost-dev | libboost1.63-dev, libproj-dev, qtbase5-dev-tools, qtbase5-dev, qt5-qmake

Note the "libboost-dev | libboost1.63-dev"

description: updated
Changed in boost1.63 (Ubuntu):
status: New → Confirmed
importance: Undecided → High
Revision history for this message
Matthias Klose (doko) wrote :
Download full text (21.9 KiB)

Removing packages from bionic:
 boost1.63 1.63.0+dfsg-1ubuntu4 in bionic
  libboost-atomic1.63-dev 1.63.0+dfsg-1ubuntu4 in bionic amd64
  libboost-atomic1.63-dev 1.63.0+dfsg-1ubuntu4 in bionic arm64
  libboost-atomic1.63-dev 1.63.0+dfsg-1ubuntu4 in bionic armhf
  libboost-atomic1.63-dev 1.63.0+dfsg-1ubuntu4 in bionic i386
  libboost-atomic1.63-dev 1.63.0+dfsg-1ubuntu4 in bionic ppc64el
  libboost-atomic1.63-dev 1.63.0+dfsg-1ubuntu4 in bionic s390x
  libboost-atomic1.63.0 1.63.0+dfsg-1ubuntu4 in bionic amd64
  libboost-atomic1.63.0 1.63.0+dfsg-1ubuntu4 in bionic arm64
  libboost-atomic1.63.0 1.63.0+dfsg-1ubuntu4 in bionic armhf
  libboost-atomic1.63.0 1.63.0+dfsg-1ubuntu4 in bionic i386
  libboost-atomic1.63.0 1.63.0+dfsg-1ubuntu4 in bionic ppc64el
  libboost-atomic1.63.0 1.63.0+dfsg-1ubuntu4 in bionic s390x
  libboost-chrono1.63-dev 1.63.0+dfsg-1ubuntu4 in bionic amd64
  libboost-chrono1.63-dev 1.63.0+dfsg-1ubuntu4 in bionic arm64
  libboost-chrono1.63-dev 1.63.0+dfsg-1ubuntu4 in bionic armhf
  libboost-chrono1.63-dev 1.63.0+dfsg-1ubuntu4 in bionic i386
  libboost-chrono1.63-dev 1.63.0+dfsg-1ubuntu4 in bionic ppc64el
  libboost-chrono1.63-dev 1.63.0+dfsg-1ubuntu4 in bionic s390x
  libboost-chrono1.63.0 1.63.0+dfsg-1ubuntu4 in bionic amd64
  libboost-chrono1.63.0 1.63.0+dfsg-1ubuntu4 in bionic arm64
  libboost-chrono1.63.0 1.63.0+dfsg-1ubuntu4 in bionic armhf
  libboost-chrono1.63.0 1.63.0+dfsg-1ubuntu4 in bionic i386
  libboost-chrono1.63.0 1.63.0+dfsg-1ubuntu4 in bionic ppc64el
  libboost-chrono1.63.0 1.63.0+dfsg-1ubuntu4 in bionic s390x
  libboost-context1.63-dev 1.63.0+dfsg-1ubuntu4 in bionic amd64
  libboost-context1.63-dev 1.63.0+dfsg-1ubuntu4 in bionic arm64
  libboost-context1.63-dev 1.63.0+dfsg-1ubuntu4 in bionic armhf
  libboost-context1.63-dev 1.63.0+dfsg-1ubuntu4 in bionic i386
  libboost-context1.63-dev 1.63.0+dfsg-1ubuntu4 in bionic ppc64el
  libboost-context1.63.0 1.63.0+dfsg-1ubuntu4 in bionic amd64
  libboost-context1.63.0 1.63.0+dfsg-1ubuntu4 in bionic arm64
  libboost-context1.63.0 1.63.0+dfsg-1ubuntu4 in bionic armhf
  libboost-context1.63.0 1.63.0+dfsg-1ubuntu4 in bionic i386
  libboost-context1.63.0 1.63.0+dfsg-1ubuntu4 in bionic ppc64el
  libboost-coroutine1.63-dev 1.63.0+dfsg-1ubuntu4 in bionic amd64
  libboost-coroutine1.63-dev 1.63.0+dfsg-1ubuntu4 in bionic arm64
  libboost-coroutine1.63-dev 1.63.0+dfsg-1ubuntu4 in bionic armhf
  libboost-coroutine1.63-dev 1.63.0+dfsg-1ubuntu4 in bionic i386
  libboost-coroutine1.63-dev 1.63.0+dfsg-1ubuntu4 in bionic ppc64el
  libboost-coroutine1.63.0 1.63.0+dfsg-1ubuntu4 in bionic amd64
  libboost-coroutine1.63.0 1.63.0+dfsg-1ubuntu4 in bionic arm64
  libboost-coroutine1.63.0 1.63.0+dfsg-1ubuntu4 in bionic armhf
  libboost-coroutine1.63.0 1.63.0+dfsg-1ubuntu4 in bionic i386
  libboost-coroutine1.63.0 1.63.0+dfsg-1ubuntu4 in bionic ppc64el
  libboost-date-time1.63-dev 1.63.0+dfsg-1ubuntu4 in bionic amd64
  libboost-date-time1.63-dev 1.63.0+dfsg-1ubuntu4 in bionic arm64
  libboost-date-time1.63-dev 1.63.0+dfsg-1ubuntu4 in bionic armhf
  libboost-date-time1.63-dev 1.63.0+dfsg-1ubuntu4 in bionic i386
  libboost-date-time1.63-dev 1.63.0+df...

Changed in boost1.63 (Ubuntu):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.