ell 0.38 bluez 5.56

[ericonr]

General

• This is a new package and it conforms to the quality requirements

Have the results of the proposed changes been tested?

• I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
• I generally don't use the affected packages but briefly tested this PR

[ericonr]

Welp, they broke ABI

[ericonr]

Should wait on IWD 1.12. I'm considering moving it to use built-in ELL to avoid ABI/API mismatches (IWD 1.11 won't even build with this one).

@sgn what do you think about doing the same for bluez?

[sgn]

I'm expecting new release of bluez soon. In my experience, ell don't break that often.

[ericonr]

From what I understand, most of the time the releases come out near each other, ell, bluez and IWD. But since they are so tied to a specific ll version, I'm not sure we gain much by using the dynamic library... It's tiny and using the bundled one helps avoid weird compatibility issues.

Since I'd consider wireless generally more essential than bt, we could link only IWD with the bundled version.

[sgn]

Seems like Debian (which wants to dynamic link the most) also uses bundled version for iwd. I think it should be fine.
They uses external ell for bluez, though.

[sgn]

BlueZ: hold for a bit https://marc.info/?l=linux-bluetooth&m=161437459815658&w=2

[ahesford]

iwd seems to work fine as a WPA supplicant and link manager. IPv6 still fails to work as expected. In my network, which offers Router Advertisements for IPv6 configuration, iwd crashes when it is configured to enable IPv6. Earlier versions supported only DHCPv6 for IPv6, but I don't rememember if that caused iwd to crash or just fail to give me a v6 address before. I can't comment on DHCPv6 functionality.

For now, iwd still fails to deliver key IPv6 support, which leaves me turning off network configuration and using dhcpcd. This is nothing new and, unless previously working DHCPv6 support is broken, probably shouldn't block this update.

I continue to wait for the day when iwd handles IPv6 properly and I can drop my dhcpcd dependnecy.

[sgn]

I would say switch BlueZ to vendor ell for now (if bluez failed to build from source with new ell) and push ell and iwd out first.

---

BlueZ 5.55 built fine with new ell?

[ericonr]

BlueZ 5.55 built fine with new ell?

I didn't check. But now that IWD is using bundled ell, I can hold the ell update without issue.

[ericonr]

This PR is now exclusively about ell and bluez.

[paper42]

bluez 5.57 and 5.58 are out. They fix an issue in 5.56 where bluetooth headphones could connect with HSP instead of SBC/AptX etc. which meant really bad sound quality.

[paper42]

• 5.58 requires ell 0.39
• using -n flag in the service means that bluetoothd logs to stdout, could you add logging to the service? What's the policy about logging in services in Void? When should they be included in the package?
• could you add --enable-experimental flag to bluez as a build option? (disabled by default) This option should enable monitoring battery level with a dbus interface.

[ericonr]

@paper42 I have pushed an updated version of the PR, could you please test it out?

[paper42]

Thanks, I will try using this for a few days and report back soon.

[paper42]

I was able to test this only for a few hours before my hardware broke, but it worked fine.