debcrafters-packages team mailing list archive

[Nick Rosbrook <2122382@xxxxxxxxxxxxxxxxxx>]

Hello Dirk, or anyone else affected,

Accepted bluez into noble-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/bluez/5.72-0ubuntu5.5
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, what testing has been
performed on the package and change the tag from verification-needed-
noble to verification-done-noble. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-noble. In either case, without details of your testing we will
not be able to proceed.

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Tags removed: verification-done
** Tags added: verification-needed verification-needed-noble

-- 
You received this bug notification because you are a member of
Debcrafters packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/2122382

Title:
  [SRU] Improve audio profiles compatibility

Status in OEM Priority Project:
  New
Status in bluez package in Ubuntu:
  Fix Released
Status in bluez source package in Noble:
  Fix Committed
Status in bluez source package in Plucky:
  Fix Released
Status in bluez source package in Questing:
  Fix Released

Bug description:
  [ Impact ]

   * Older Bluez not able pass the compliance testing from the Bluetooth SIG.
     This SRU aim to back port necessary patches to improve the compatibility.

  [ Test Plan ]

   * Run following test cases from Bluetooth SIG Profile Tuning Suite (PTS)
     won't get fail result.
    - A2DP/SRC/SGSIT/ATTR/BV-04-C
     - check Advanced Audio Distribution profile (A2DP) version
    - AVDTP/SRC/INT/SIG/SMG/BV-15-C
     - Verify that the IUT (Implementation under test) is able to establish a stream connection to a previously configured remote SEP by establishing one L2CAP channel
    - AVDTP/SRC/ACP/TRA/BTR/BI-01-C
     - Verify that the IUT is able to issue a Set Configuration Reject response to the Initiator if the format of the media transport is incorrect

  [ Where problems could occur ]

   * Patches are doing minor bug fix to the profile. Normal user should not be
     affected

  [ Other Info ]

   * Related upstream commits
    - https://github.com/bluez/bluez/commit/f0e9ecb9f4fe3a7bdb011dc155cf6ad657a289ee
      - profiles-avdtp-Fix-reply-for-bad-media-transport-for.patch fix AVDTP/SRC/ACP/TRA/BTR/BI-01-C

    - https://github.com/bluez/bluez/commit/ea3f4047e452b081e34d017cce316aba9d623301
    - https://github.com/bluez/bluez/commit/78aabd896dbe3e23faaebbc97b8ecd711b2502fc
      - cleanup-endpoints-when-devices-been-removed.patch fix AVDTP/SRC/INT/SIG/SMG/BV-15-C, this test case will verify if the IUT follow the correctly command sequences (AVDT_Sig_Event_Registration-> AVDT_Get_Capabilities_Req-> AVDTP_GET_CAPABILITIES_CMD). If there is cached capability data, bluez won't send AVDT_Get_Capabilities_Req, PTS will treat it as fail. This patch make bluez clean cache when removing the device and able to get pass result with PTS.

    - https://github.com/bluez/bluez/commit/f2120e3ded0656c8eda3d8058ee35654aba3fd09
      - audio-upgrade-versions-to-latest-possible-to-qualify.patch fix A2DP/SRC/SGSIT/ATTR/BV-04-C

   * A2DP test suite
    - https://files.bluetooth.com/download/a2dp-ts-p20-pdf
   * AVDTP test suite
    - https://files.bluetooth.com/download/avdtp-ts-p21-pdf

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/2122382/+subscriptions