RFC - Downgrade BlueZ to v4.101 in Fedora 20

Reindl Harald h.reindl at thelounge.net
Sat Jan 25 16:43:51 UTC 2014

Am 25.01.2014 17:40, schrieb Tomasz Torcz:
> 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:
> http://lists.freedesktop.org/archives/pulseaudio-discuss/2014-January/019858.html
> 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

my expierience with pulseaudio-upgrades is good

Rex Dieter had PA 4.0 in a un-official repo months before it arrived
in Fedora and there was no regression using that repo on current Fedora

what about a scratch-build announced on @devel and @users to get active testers?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 246 bytes
Desc: OpenPGP digital signature
URL: <http://lists.fedoraproject.org/pipermail/devel/attachments/20140125/357f1242/attachment.sig>

More information about the devel mailing list