Description of problem:
KDE 4.0 Beta 1 (3.92.0) now needs Strigi >= 0.5.3. A formal 0.5.4 release is
probably going to be out shortly. In the meantime, I repackaged 0.5.3 from:
in a standard tarball (the ZIP had everything in a second-level directory
Here's an updated SRPM:
Version-Release number of selected component (if applicable):
I use to periodically check both http://www.vandenoever.info/software/strigi/
and http://strigi.sf.net/ for latest news about strigi, but none of those
mention any new release later than 0.5.1. And I just checked the download page
on sourceforge right now, it still has strigi-0.5.1; do you know if the
development has moved elsewhere?
Development happens in KDE SVN, but AFAIK releases are still supposed to happen
at vandenoever.info (and I believe 0.5.4 is supposed to be up there soon, there
was a SVN commit saying "Preparing 0.5.4 release" in any case). There appears
to be some miscommunication there with KDE prereleasing the beta to packagers
before the version of Strigi required by it is up.
If that's case (and if it is going to impact your KDE 4.0 packaging), I think we
should get the source from KDE SVN instead. While I trust you and accept you
know much about this package than I do, I don't know anything about the source
of the 0.5.3 tarball you provided.
PS: Let me know if you're interested in co-maintaining strigi.
The URL I've given comes from the kde-windows folks, I don't think they're out
to trojan their users' machines. (That would ruin KDE's reputation really
badly. ;-) )
But we can also use something straight out of KDE SVN if you're more
comfortable with that.
I've made a build from a snapshot KDE SVN checked out this afternoon. The rpm
spec and src.rpm are at ftp://czar.eas.yorku.ca/pub/strigi/strigi.spec and
ftp://czar.eas.yorku.ca/pub/strigi/strigi-0.5.4-0.1.svn20070729.src.rpm. Let me
know if you're O.K. with it, and I'll then build it for rawhide.
I'm fine with it.
Built (strigi-0.5.4-0.1.svn20070729) successfully in koji.
The official 0.5.4 is now out on the KDE mirrors:
It's actually 3 days older than the snapshot you've been using, but I think the
best way to proceed is to push this one to all branches.