Adding probably relevant links for your consumtion. https://gitlab.freedesktop.org/pipewire/pipewire/-/commits/master/meson.build https://gitlab.freedesktop.org/pipewire/pipewire/-/commits/master/meson_options.txt https://gitlab.freedesktop.org/pipewire/pipewire/-/commits/master/spa/meson.build https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/5c52670421d94e72f011340bbde9300184a9dba8 Please fix.
mattst88 did approve the bump, I pinged the gnome team within the -dev channel (and specifically looked for you as well). Do you have any specific complaints about the bump?
Fixing $summary accordingly. I'm fine with someone else doing the bump, but mattst88 will probably assume you look at Changelogs as well.
I did look at the changelog, the main thing we saw was the bluetooth encoding flags (which default to true). Because of this we decided that no change to the ebuild was needed.
What did we miss? I don't see anything outside of the new bluez5-backend-native and bluez5-backend-native options, which are default on and were always enabled with bluez before. > git log --reverse -p 0.3.7..0.3.10 $(find -name meson.build) meson_options.txt Not seeing anything else that looks like it warrants a change? You referenced commit 5c52670421d94e72f011340bbde9300184a9dba8 but that's after the v0.3.10 tag.
Thanks for clarifying. I had been holding off on the bump having had no time to look into the bluetooth change. We will need user/group for the next bump then.
FYI, I was pointed to this bug after I bumped to 0.3.13. I diffed https://gitlab.freedesktop.org/pipewire/pipewire/-/commits/master/meson.build I did not add anything bluez related because it is disabled by default and I don't know this feature.
