Re: Cannot build strigi
On Thursday 14 April 2011 4:34:08 pm Andreas Pakulat wrote: > On 14.04.11 16:00:11, Ian Wadham wrote: > > Now kdesrc-build-1.13 reports the first failure on strigi. After that, > > no major modules will build build. Re strigi, I get the messages: > > Looks like either someone broke the strigi repository, or your cmake > cannot handle Git submodules that well. I recall a related bugfix in > cmake 2.8.3 or 2.8.4. > Thanks, Andreas. What version of Cmake is required now in KDE? I have 2.8.2, built on 30 June last year and I am not aware of any later version being required (nothing found in Techbase post-2.8.2), but I have been out of touch with KDE for most of the last 9 months. Cmake 2.8.2 built KDE OK for me early in January and Cmake's latest version on www.cmake.org is 2.8.4, released 16 Feb 2011. > If updating cmake does not help, you can try to > update the submodules manually, go to the strigi repository then do > > git submodule init > git submodule update > I don't think a git novice (ignoramus) like me should be dinking with KDE's git repository, if that's what you mean. > if that also fails you're out of luck until someone fixes the > repository > That could be the case for me. So could someone fix it? Cheers, Ian W. >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: Cannot build strigi
On 14.04.11 21:59:24, Ian Wadham wrote: > On Thursday 14 April 2011 4:34:08 pm Andreas Pakulat wrote: > > On 14.04.11 16:00:11, Ian Wadham wrote: > > > Now kdesrc-build-1.13 reports the first failure on strigi. After that, > > > no major modules will build build. Re strigi, I get the messages: > > > > Looks like either someone broke the strigi repository, or your cmake > > cannot handle Git submodules that well. I recall a related bugfix in > > cmake 2.8.3 or 2.8.4. > > > Thanks, Andreas. > > What version of Cmake is required now in KDE? I have 2.8.2, built on > 30 June last year and I am not aware of any later version being required > (nothing found in Techbase post-2.8.2), but I have been out of touch > with KDE for most of the last 9 months. Cmake 2.8.2 built KDE OK for me > early in January and Cmake's latest version on www.cmake.org is 2.8.4, > released 16 Feb 2011. 2.8.2 is fine for building KDE, but this is not KDE code, you'll have to talk to the strigi-authors about their requirement. > > If updating cmake does not help, you can try to > > update the submodules manually, go to the strigi repository then do > > > > git submodule init > > git submodule update > > > I don't think a git novice (ignoramus) like me should be dinking with > KDE's git repository, if that's what you mean. No, you run this in your local clone of the strigi repository. Not sure wether you're aware of this, but the single strigi module was split into multiple git repositories. Apparently there's now also a 'meta repository' called "strigi" which uses the git submodule feature to merge back all the different strigi-related git repositories into 1 local checkout. Doing this requires to use the git submodule command after having cloned the meta-repository and it looks like your cmake version is not able to do that for some reason. Andreas >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: Cannot build strigi
Ian Wadham writes: > The git-clone.log seems to be OK. It is getting strigi from > git://anongit.kde.org/strigi. Attached is a copy of the cmake > error log file, but I do not understand any of the error messages > and have no idea what to do next. Any ideas? [snip] > # kdesrc-build running: 'cmake' '/extra/kdesrc/strigi' > '-DCMAKE_BUILD_TYPE=RelWithDebInfo' '-DSTRIGI_SYNC_SUBMODULES=TRUE' > '-DCMAKE_CXX_FLAGS:STRING=-pipe' '-DCMAKE_INSTALL_PREFIX=/extra/kdesrc/kde' [snip] > -- Checking: /extra/kdesrc/strigi/libstreams/CMakeLists.txt > -- No CMakeLists.txt found in libstreams > -- Trying to download the libstreams submodule > Submodule 'libstreams' (http://anongit.kde.org/libstreams) registered for > path 'libstreams' > Getting alternates list for http://anongit.kde.org/libstreams > Getting pack list for http://anongit.kde.org/libstreams > error: Unable to verify pack 7036d6bf6add07e947eafae2a9d649590417c64c is > available > error: Unable to find 650b33eaa30b43312fce9ef703e66e47da7151b5 under > http://anongit.kde.org/libstreams > Cannot obtain needed object 650b33eaa30b43312fce9ef703e66e47da7151b5 > fatal: Fetch failed. > Initialized empty Git repository in /extra/kdesrc/strigi/libstreams/.git/ > Clone of 'http://anongit.kde.org/libstreams' into submodule path 'libstreams' > failed I've recently made some commits to the strigi submodules and then updated the strigi supermodule to make it use the newer hashes for its submodules. I've just tried building a fresh new strigi clone here and everything worked fine: $ git clone kde:strigi $ cd strigi && mkdir build && cd build $ cmake -DSTRIGI_SYNC_SUBMODULES=TRUE .. After that, each submodule is correctly cloned. Simply doing `git clone http://anongit.kde.org/libstreams' also worked fine. The only differences I can see are that my CMake and git versions are newer than yours (respectively 2.8.4 and 1.7.4.4). Can you try cloning again (either via kdesrc-build or by just cloning a submodule like libstreams like I mentioned in the previous paragraph)? >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
kdesupport for 4.6
There doesn't seem to be a kdesupport package in git or svn for use with KDE 4.6, equivalent to the svn tag kdesupport-for-4.5 for KDE 4.5. Are there plans to create this? -- David Jarvie. KDE developer. KAlarm author -- http://www.astrojar.org.uk/kalarm signature.asc Description: This is a digitally signed message part. >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: Cannot build strigi
On Thursday 14 April 2011 08:34:08 Andreas Pakulat wrote: > On 14.04.11 16:00:11, Ian Wadham wrote: > > Now kdesrc-build-1.13 reports the first failure on strigi. After that, > > > no major modules will build build. Re strigi, I get the messages: > Looks like either someone broke the strigi repository, or your cmake > cannot handle Git submodules that well. I recall a related bugfix in > cmake 2.8.3 or 2.8.4. If updating cmake does not help, you can try to > update the submodules manually, go to the strigi repository then do > > git submodule init > git submodule update > > if that also fails you're out of luck until someone fixes the > repository or you use the indvidual separated strigi repositories. Don't do that: http://sourceforge.net/tracker/index.php?func=detail&aid=3168442&group_id=171000&atid=856302 And it looks like there is no intention to solve it. They made a curious mess with the strigi git migration. On one hand they tried to break it up (even installing different cmake config files) on the other hand they require you to build to the strigi repository which downloads all others. Mike >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: Cannot build strigi
On Thursday 14 April 2011 11:53:17 pm Raphael Kubo da Costa wrote: > Can you try cloning again (either via kdesrc-build or by just cloning a > submodule like libstreams like I mentioned in the previous paragraph)? > Thanks very much for all the information and advice, Raphael. I am busy today (Friday) but will try again over the weekend. All the best, Ian W. >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: kdesupport for 4.6
On Thursday, April 14, 2011 23:13:29 David Jarvie wrote: > There doesn't seem to be a kdesupport package in git or svn for use with KDE > 4.6, equivalent to the svn tag kdesupport-for-4.5 for KDE 4.5. Are there > plans to create this? Last I heard was an explicit no, mostly because many (though not all) of the libraries that were in kdesupport for 4.5 had migrated to git by the time 4.6 was tagged/released, and therefore the svn tag wouldn't really fully describe all the kdesupport libraries that were required. Don't take this as opposition from myself however. ;) Regards, - Michael Pyne signature.asc Description: This is a digitally signed message part. >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
