On Thu, 2014-01-23 at 20:04 +0100, David Sommerseth wrote:
Nope, several packages depends on the bluez-5.13-1 package.
Indeed. However I could probably live without gnome-bluetooth if
blueman were still available.
pulseaudio-module-bluetooth though. Would it work with Bluez4? Would
it need a compile to do so? I wonder how you make that a functional
downgrade that users can select if they still need Bluez4.
---------------------------
--> Finished Dependency Resolution
Error: Package: pulseaudio-module-bluetooth-4.0-9.gitf81e3.fc20.x86_64
(@updates/20)
Requires: bluez >= 5.0
Removing: bluez-5.13-1.fc20.x86_64 (@updates/20)
bluez = 5.13-1.fc20
Downgraded By: bluez-4.101-9.fc19.x86_64 (updates)
bluez = 4.101-9.fc19
Available: bluez-4.101-6.fc19.x86_64 (fedora)
bluez = 4.101-6.fc19
Error: Package: 1:gnome-bluetooth-3.10.0-1.fc20.x86_64 (@anaconda/20)
Requires: bluez >= 5.0
Removing: bluez-5.13-1.fc20.x86_64 (@updates/20)
bluez = 5.13-1.fc20
Downgraded By: bluez-4.101-9.fc19.x86_64 (updates)
bluez = 4.101-9.fc19
Available: bluez-4.101-6.fc19.x86_64 (fedora)
bluez = 4.101-6.fc19
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
----------------------------
Might even be a worse conflict for other users, depending on installed
packages. I believe there's no way around re-compiling NetworkManager,
pulseaudio and other GNOME and KDE packages depending on bluez.
Indeed. I suspect the same. Perhaps gnome-bluetooth could be
uninstalled and replace with blueman without too much heartburn. It's
the other packages that get troublesome. A
pulseaudio-module-bluetooth-bluez4 as an alternative BT module for PA?
Something similar for NM? It's starting to get ugly and perhaps the
effort spent doing that would be better put towards:
https://bugs.freedesktop.org/show_bug.cgi?id=73325#c5
But either way, it does seem a pretty serious regression. Although
maybe you and me, David, are the only F20 users using HSP bluetooth
headsets. :-/
b.