upgrade bcmwl-kernel-source to 6.30.223.248

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

I've made an updated package that works for me - I'll just get Alberto Milone to check it for me as he normally does the uploads.

Uploaded. Thanks for your work, Robert!

This bug was fixed in the package bcmwl - 6.30.223.248+bdcom-0ubuntu1

---------------
bcmwl (6.30.223.248+bdcom-0ubuntu1) utopic; urgency=medium

  * New upstream release: (LP: #1342645)
    - This is an official public release from Broadcom.
  * debian/dkms.conf.in:
    - Drop patches for kernels 3.10 (now upstream)
 -- Robert Ancell <email address hidden> Fri, 01 Aug 2014 11:09:43 +1200

Hello James, or anyone else affected,

Accepted bcmwl into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/bcmwl/6.30.223.271+bdcom-0ubuntu1~0.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 on 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!

The fix for this bug has been awaiting testing feedback in the -proposed repository for trusty for more than 90 days. Please test this fix and update the bug appropriately with the results. In the event that the fix for this bug is still not verified 15 days from now, the package will be removed from the -proposed repository.

I no longer own a machine using this driver, hence cannot test.

As this report was an upgrade request, not related to a specific bug, I'd support the upgrade over retaining the current version.

As part of a recent change in the Stable Release Update verification policy we would like to inform that for a bug to be considered verified for a given release a verification-done-$RELEASE tag needs to be added to the bug where $RELEASE is the name of the series the package that was tested (e.g. verification-done-xenial). Please note that the global 'verification-done' tag can no longer be used for this purpose.

Thank you!

Trusty release has gone end of support for this package, so marking this as such.

Newer releases will have this fix though.