Bogus run-time error about wrong endianness for boost-numpy

Bug #1853414 reported by Syncopated
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
boost-defaults (Ubuntu)
New
Undecided
Unassigned

Bug Description

This is about an upstream bug in Boost 1.67:
https://github.com/boostorg/python/issues/209

The bug has been fixed by this merged PR:
https://github.com/boostorg/python/pull/218/commits/0fce0e589353d772ceda4d493b147138406b22fd

The PR made it to upstream version 1.68 but Ubuntu is still using 1.67.

Can there be a minor version upgrade (libboost-numpy1.67.1?) incorporating a patch containing the one-line change in the PR?

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.