On Thu, 2006-09-28 at 21:23 +0100, David Woodhouse wrote:
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...?
Sorry, there's a feature freeze for a reason. We can't just keep
ignoring it and shoving stuff in at the last minute. Doing the swap
later in an update is _far_ preferable as you can push it to -testing
and let people test it out for a week or two prior to pushing to final
-updates.
Jeremy