@Christopher
as per the Debian comments (1.60 has been dropped, and its associated
bugs too; considering 1.60 as a transitional version), you might check
their now only valid 1.61 release.
If 1.61 is still having the problem you have reported here, then report
against it with a new debbugs
It looks like debian did not actually fixed this, they closed it because
that package is now defunct. Is there anything I'm supposed to do to
follow up on this? Should I file it again against a different version of
debian boost package?
--
You received this bug notification because you are a
** Changed in: boost1.60 (Debian)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1600391
Title:
No b2 executable in libboost-tools-dev
To manage notifications
@Jeremy Bicha: Thank you for looking into this and researching it, your
explanation of the problem and the link you found were much better than
my original report.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: boost1.60 (Debian)
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1600391
Title:
No b2 executable in libboost-tools-dev
To manage notifications about
** Changed in: boost-defaults (Ubuntu)
Importance: Undecided => Wishlist
** Changed in: boost-defaults (Ubuntu)
Status: New => Triaged
** Package changed: boost-defaults (Ubuntu) => boost1.58 (Ubuntu)
** Also affects: boost1.60 (Ubuntu)
Importance: Undecided
Status: New
**
