Ian Wadham <iandw...@gmail.com> writes: > On Thursday 14 April 2011 11:53:17 pm Raphael Kubo da Costa wrote: >> 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 .. >> > Tried git clone kde:strigi, but some kind of no-access error.
Do you have the 'kde:' prefix configured, as per http://community.kde.org/Sysadmin/GitKdeOrgManual#Let_Git_rewrite_URL_prefixes? > So tried: > git clone http://anongit.kde.org/strigi > got similar errors to those I got before and attached to my first email. [snip] > Have not tried git clone http://anongit.kde.org/libstreams. Would I need > to do cd strigi first? The intention, in the strigi/CMakeLists.txt, seems to > be to have libstreams, etc. in subdirs. Well, most people who have had to deal with the strigi repositories consider them... bit awkward, to put it mildly. You can clone each of the submodules (libstreams, strigiutils etc) separately. The strigi supermodule is just supposed to have them at a specific revision, from what I see. > -- 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' > got 04028c5a62e1c9817d3b0ad027f5022d19a12e0b > walk 04028c5a62e1c9817d3b0ad027f5022d19a12e0b > 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 42ac728743497edda3fa048bcc1f1827672faa38 under > http://anongit.kde.org/libstreams > Cannot obtain needed object 42ac728743497edda3fa048bcc1f1827672faa38 > while processing commit 04028c5a62e1c9817d3b0ad027f5022d19a12e0b. > fatal: Fetch failed. > Initialized empty Git repository in /extra/kdesrc/strigi/libstreams/.git/ Perhaps this is related to your network access? Are you somehow behind a firewall? Are you able to clone any other git repository just fine? A few remaining suggestions: * Try cloning using the "git://" protocol instead of "http://"; * Try cloning each submodule separately (either with "git://" or "http://";) * Try setting the `GIT_CURL_VERBOSE' environment variable when cloning. >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
