Error: rev-upgrade failed: Error rebuilding boost-numpy

[BeastOfBodmin]

$ port -v
MacPorts 2.6.2

$ python --version
Python 3.8.3

$ sudo port clean all

$ sudo port install boost-numpy +python38
Password:


--->  Computing dependencies for boost-numpy
--->  Cleaning boost-numpy
--->  Scanning binaries for linking errors
--->  Found 1 broken file, matching files to ports       
--->  Found 1 broken port, determining rebuild order
You can always run 'port rev-upgrade' again to fix errors.
The following ports will be rebuilt: boost-numpy @1.71.0+no_single+no_static+python38
Continue? [Y/n]: Y
--->  Computing dependencies for boost-numpy
--->  Cleaning boost-numpy
--->  Scanning binaries for linking errors
--->  Found 1 broken file, matching files to ports       
--->  Found 1 broken port, determining rebuild order
--->  Rebuilding in order
     boost-numpy @1.71.0 +no_single+no_static+python38
--->  Computing dependencies for boost-numpy
--->  Fetching distfiles for boost-numpy
--->  Verifying checksums for boost-numpy
--->  Extracting boost-numpy
--->  Applying patches to boost-numpy
--->  Configuring boost-numpy
Error: Failed to configure boost-numpy: boost must be installed with +python38.
Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_boost/boost-numpy/main.log for details.
Error: rev-upgrade failed: Error rebuilding boost-numpy
Error: Follow https://guide.macports.org/#project.tickets to report a bug.

$ port installed python*
The following ports are currently installed:
  python2_select @0.0_3 (active)
  python3_select @0.0_1 (active)
  python27 @2.7.16_1
  python27 @2.7.16_2
  python27 @2.7.17_0
  python27 @2.7.18_1 (active)
  python35 @3.5.9_0 (active)
  python36 @3.6.9_1
  python36 @3.6.9_3
  python36 @3.6.10_0 (active)
  python37 @3.7.4_1
  python37 @3.7.5_1
  python37 @3.7.6_0
  python37 @3.7.7_0 (active)
  python38 @3.8.2_0
  python38 @3.8.3_0 (active)
  python_select @0.3_8 (active)

[mf2k (Frank Schima)]

In the future, please use WikiFormatting and add the port maintainer(s) to Cc (port info --maintainers boost-numpy), if any.

[mf2k (Frank Schima)]

What you need to do is printed in the output:

Error: Failed to configure boost-numpy: boost must be installed with +python38

[kencu (Ken)]

these informational messages ask people to open a bug report, and when they do what they are asked, they get bonked.

I'm sure that must be frustrating for people; we should fix our messaging somehow if we don't want them to open tickets...

[BeastOfBodmin]

Replying to kencu:

these informational messages ask people to open a bug report, and when they do what they are asked, they get bonked.

I'm sure that must be frustrating for people; we should fix our messaging somehow if we don't want them to open tickets...

It would help if the instructions to follow were on the same page as the form to raise the bug report.

It's not easy to do do it properly (as I just found out), and I do it seldom.The solutions are

1. Do nothing because it's perfect already
2. Improve the docs (and/ or put them on the same page as the form)
3. Improve the process - maybe supply a simple programme that grabs the information you want so that we can copy/ paste it into the form.

[BeastOfBodmin]

Replying to mf2k:

What you need to do is printed in the output:

Error: Failed to configure boost-numpy: boost must be installed with +python38

But I thought that is what I did:

sudo port install boost-numpy +python38

Maybe improve the contents of the error message?

[kencu (Ken)]

please show us:

port -v installed boost

most likely boost is installed with some other python variant, and the python variants have to match between boost and boost-numpy.

[BeastOfBodmin]

Replying to kencu:

please show us:

port -v installed boost

most likely boost is installed with some other python variant, and the python variants have to match between boost and boost-numpy.

$ port -v installed boost
The following ports are currently installed:
  boost @1.66.0_4+no_single+no_static+python27 platform='darwin 18'
 archs='x86_64' date='2019-07-07T21:38:13+0200'
  boost @1.71.0_0+no_single+no_static+python27 platform='darwin 18'
 archs='x86_64' date='2019-09-05T22:22:21+0200'
  boost @1.71.0_1+no_single+no_static+python27 platform='darwin 19'
 archs='x86_64' date='2020-01-14T20:21:10+0100'
  boost @1.71.0_2+no_single+no_static+python27 (active) platform='d
arwin 19' archs='x86_64' date='2020-05-21T16:43:10+0200'

Why does it complain now? I had python 3.8.2 installed until today.

[kencu (Ken)]

You see how you have boost installed with +python27? That's the issue. It comes from some previous version of boost you installed.

If you do this:

sudo port -f uninstall boost
sudo port -v install boost

you will then pick up the new default variants for boost, which are now +python38.

$ port info boost
boost @1.71.0_2 (devel)
Sub-ports:            boost-numpy
Variants:             clang10, clang33, clang34, clang37, clang50, clang60,
                      clang70, clang80, clang90, cmake_scripts, debug, mpich,
                      mpich_devel, [+]no_single, [+]no_static, openmpi,
                      openmpi_devel, python27, python35, python36, python37,
                      [+]python38, regex_match_extra, universal

If you, for some reason, want to standardize on a different python version, you would have to manually force it by specifying a boost version.

[BeastOfBodmin]

Replying to kencu:

You see how you have boost installed with +python27? That's the issue. It comes from some previous version of boost you installed.

If you do this:

sudo port -f uninstall boost
sudo port -v install boost

you will then pick up the new default variants for boost, which are now +python38.

$ port info boost
boost @1.71.0_2 (devel)
Sub-ports:            boost-numpy
Variants:             clang10, clang33, clang34, clang37, clang50, clang60,
                      clang70, clang80, clang90, cmake_scripts, debug, mpich,
                      mpich_devel, [+]no_single, [+]no_static, openmpi,
                      openmpi_devel, python27, python35, python36, python37,
                      [+]python38, regex_match_extra, universal

If you, for some reason, want to standardize on a different python version, you would have to manually force it by specifying a different python version.

Uninstall/ reinstall worked.

But why did it complain only when I upgraded to python 3.8.3 from 3.8.2?

Maybe I installed 3.8.2 at or before 2.7, and I had to force 2.7 for some other packages. So it only came to light when I upgraded py3.

[kencu (Ken)]

Replying to BeastOfBodmin:

But why did it complain only when I upgraded to python 3.8.3 from 3.8.2?

I think that was probably just a coincidence.