On Fri, Dec 27, 2013 at 05:50:18PM -0800, Adam Williamson wrote:
Sigh. Yes, another of these.
On 2013-12-18, tracker was bumped to 0.7.0:
http://koji.fedoraproject.org/koji/buildinfo?buildID=485698
the sonames of libtracker-extract, libtracker-miner and libtracker-sparql were bumped to 0.18.so.0 (from 0.16.so.0) without announcement, and without all dependent packages being successfully rebuilt. At least the following still depend on the old sparql library:
The thing with Tracker is that they bump the bump the soname and their pkgconfig file version somewhat gratuitously every six months.
I built a new tracker because some applications (eg., gnome-photos) specifically want the features in the 0.17/0.18 series.
I thought I had rebuilt all the affected packages, but obviously I missed some.
bijiben-0:3.11.1-1.fc21.x86_64 brasero-0:3.11.3-1.fc21.x86_64
I thought the round of builds for 3.11.3 would take care of these two, but it looks like bijiben was not built by mclazy and brasero got built before the new tracker hit the trees. :-/
grilo-plugins-0:0.2.9-2.fc21.x86_64 media-explorer-0:0.4.4-5.fc21.x86_64
These two need new upstream releases, but the patches are already in Git.
What does it take for people to handle soname bumps properly?
Barring media-explorer, everything else is part of the GNOME stack so chances of other spins being broken by this was low.
My assumption was that sooner or later this would be sorted by the GNOME builds during the 3.11.x cycle. Given that the Fedora and GNOME schedules are quite a bit out of sync these days, I was hoping for some transient rawhide breakage during the Christmas break to go largely unnoticed. I mean if this is the only thing broken in Rawhide at the moment, then I would be more than happy. :)
Anyway. Thanks for taking care of this, and sorry for the trouble.
Cheers, Debarshi