Default boost v1.54 has broken asio while available 1.55 is fixed

Status changed to 'Confirmed' because the bug affects multiple users.

Is there any way to provide help, patches or testing in order to get this bug fixed in the current LTS Trusty? Should I file a new SRU bug or this is enough?

Utopic, which will become 14.10, has boost version 1.55 so I am marking this as Fix Released, but will open a 14.04 (Trusty) task for it.

Comment #15 in the upstream bug report links to a couple of commits which should fix the issue with asio. For Stable Release Updates we prefer to make minimal changes to packages (https://wiki.ubuntu.com/StableReleaseUpdates), so it would be best if those changes were added to 1.54.

For the SRU, the test case to try is attached, please compile using:

 - g++ chat_client.cpp -std=gnu++11 -lboost_system -lpthread -o chat_client

You will need the header chat I will attach in the following comment in order to make it to compile.

Bug in current boost Trusty libraries, while trying to conect to non existing server.

* Bug:
./chat_client localhost 2423424
Success

* Expected:
./chat_client localhost 2423424
Connection refused

Here is the patch against current libboost1.54-dev in Trusty that fix the regression that makes impossible to use the ASIO library.

Thanks for the patch, I'll take care of sponsoring this to the trusty-proposed queue. I've modified the debian/changelog slightly though.

The syntax to reference a bug report in Launchpad in a debian/changelog file so that the Launchpad Bug Janitor and scripts can modify the Launchpad bug is to use the format LP: #1319338. I also copied the description from the patch to the changelog as that seemed more informative. The changelog entry now looks like this:

boost1.54 (1.54.0-4ubuntu4) trusty; urgency=medium

  * Fix a regression where, on some platforms, errors from async_connect are
    not correctly propagated through to the completion handler. (LP: #1319338)

Hello Tobias, or anyone else affected,

Accepted boost1.54 into trusty-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/boost1.54/1.54.0-4ubuntu3.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Hello Tobias, or anyone else affected,

Accepted boost-mpi-source1.54 into trusty-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/boost-mpi-source1.54/1.54.0-4ubuntu3.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Thanks Brian, Steve, Scott and Dimitri.

I've tested the new boost1.54-dev package in my trusty amd64 system and is fixing the problem. Silvio Traversaro was kind enough to give it a try also and reported good results in OSRF Gazebo issue tracker:
https://bitbucket.org/osrf/gazebo/issue/1204/trusty-remote_endpoint-transport-endpoint#comment-10857403

More testers are always welcome.

Yes, I can confirm that the proposed package fixed the problem that we had.

The verification of the Stable Release Update for boost1.54 has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regresssions.

This bug was fixed in the package boost-mpi-source1.54 - 1.54.0-4ubuntu3.1

---------------
boost-mpi-source1.54 (1.54.0-4ubuntu3.1) trusty; urgency=medium

  * Universe build of MPI boost components, to match LP: #1319338 upload
    of boost1.54.

boost1.54 (1.54.0-4ubuntu3.1) trusty; urgency=medium

  * Fix a regression where, on some platforms, errors from async_connect are
    not correctly propagated through to the completion handler. (LP: #1319338)
 -- Dimitri John Ledkov <email address hidden> Sat, 21 Jun 2014 05:17:47 +0100