A while ago, I updated bluez-libs to the new 3.x version, since it had a new soname and I wanted to make sure anything using it got rebuilt against the new version. The plan was to update bluez-utils and replace the horrid bluez-pin package with the shiny new bluez-gnome, but other things (mostly OLPC hardware bringup) have been taking priority. I've now found the time to do the bluez stuff, and have set it up for testing -- I appreciate that it's fairly late to be doing this, but I'd like to do the minor update of bluez-libs to 3.6, along with the update of bluez-utils from its ancient 2.25 version to 3.6. That will require building bluez-gnome in place of bluez-pin, too. Yes, it's far later than I'd like to be doing this, but the alternative is that we end up swapping them out _later_ in an erratum, which is _far_ more likely to be problematic. I've can make some time now to do a proper test of bluez stuff in advance of the fc6 release, and in fact I have a strong suspicion that after what I've done today, the new packages have probably had _more_ testing than the old ones in rawhide. Hands up those who've actually done any testing of bluetooth stuff in rawhide...? I've got packages just about ready to go; I'm still working on testing the stuff which is _known_ to be broken in rawhide but which shouldn't be broken with the new packages. I'd like to put them into FC6. Comments, objections? -- dwmw2 -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
