RFC - Downgrade BlueZ to v4.101 in Fedora 20
pbrobinson at gmail.com
Sun Jan 26 05:12:33 UTC 2014
On Sat, Jan 25, 2014 at 4:40 PM, Tomasz Torcz <tomek at pipebreaker.pl> wrote:
> On Fri, Jan 24, 2014 at 01:33:07AM +0100, Kevin Kofler wrote:
>> David Sommerseth wrote:
>> > So, I wonder if it can be considered to enable a "downgrade path" for
>> > bluez and depending packages, as described in the "Contingency Plan":
>> > <https://fedoraproject.org/wiki/Changes/Bluez5>
>> Officially downgrading BlueZ from 5 to 4 in a shipped release is totally
>> impractical. It just cannot be done realistically. (Contingency plans are
>> only intended to be enacted BEFORE the release.)
> I think we need to to upgrade PulseAudio to 5.0. That version, with
> bluetooth audio A2DP support, is currently at ”Release Candidate” stage:
> Such upgrade in stable release need to be done carefuly with above-standard
> amount of testing. But I think it's the only viable way.
> Additionaly, F20 is going to be our longer supported release. Thanks to
> fedora.next movement, we won't have F21 in usual time, but much, much later.
> This means we need to treat F20 bugs with more care, as there won't be
> fixed release in 6 months.
The first RC is already in rawhide and in F-20 we've had git snapshots
in F-20 for some time. I'm sure once it's proven stable in rawhide it
will come to F-20 but it would likely do good to test it to ensure it
fixes the problem.
More information about the devel