Peter Krefting:
Receiving objects: 100% (14752/14752), 5.07 MiB | 3629 KiB/s, done.
Resolving deltas: 100% (9278/9278), done.
Server supports multi_ack
Server supports side-band-64k
Server supports ofs-delta
Marking 76b96bfecc0d47013dd1fca1a555f12074eca814 as complete
Unable to fetch in submodule path 'modules/foo'
I added some extra debugging output to the code in builtin-fetch.c and
builtin-fetch-pack.c, and ended up with this:
Receiving objects: 100% (14752/14752), 5.07 MiB | 3383 KiB/s, done.
Resolving deltas: 100% (9278/9278), done.
cmd_fetch(): calling do_fetch()
do_fetch(): calling get_ref_map()
do_fetch(): get_ref_map() done
do_fetch(): check_not_current_branch() done
do_fetch(): read_ref() loop done
fetch_refs(): quickfetch() returned -10001
Server supports multi_ack
Server supports side-band-64k
Server supports ofs-delta
Entering everything_local()
everything_local() after 1st ref loop
Marking 76b96bfecc0d47013dd1fca1a555f12074eca814 as complete
everything_local() after mark_recent_complete_commits()
everything_local() after 2nd ref loop
everything_local() after filter_refs()
everything_local() done with retval = 1
everything_local() returned true
do_fetch_pack() done
fetch_pack(): calling reprepare_packed_git()
fetch_pack(): done
fetch_refs(): transport_fetch_refs() returned -1
do_fetch(): fetch_refs(transport, ref_map) returned non-zero
cmd_fetch(): do_fetch() return with exit_code = 1
Unable to fetch in submodule path 'modules/foo'
This seems to indicate that fetch_refs() seems to think that the fetch
(which is done over ssh) fails, whereas the regular trace output ("Receiving
objects", etc.) indicates that it succeeds.
Is there anything obvious that I should have a look at here?
My next step otherwise is adding trace output to the transport_fetch_refs()
and whatever it is it calls and that calls the code in builtin-fetch-pack.c.
Anywhere in particular I should have a look at?
--
\\// Peter - http://www.softwolves.pp.se/
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html