On Wed, 20 Feb 2008 02:22:14 +0100 (CET) Johannes Schindelin <Johannes.Schindelin@xxxxxx> wrote: > Hi, > > On Tue, 19 Feb 2008, Stephen Hemminger wrote: > > > On Wed, 20 Feb 2008 02:06:36 +0100 (CET) > > Johannes Schindelin <Johannes.Schindelin@xxxxxx> wrote: > > > > > On Tue, 19 Feb 2008, Stephen Hemminger wrote: > > > > > > > $ git-submodule init > > > > Submodule 'pkgs/linux-image-2.6.23-1-486-vyatta' (http://git.vyatta.com/linux-vyatta.git) registered for path 'pkgs/linux-image-2.6.23-1-486-vyatta' > > > > > > AFAICT this is your problem. Your urls are http:// url, and do not > > > end in a slash. > > > > > > Yes, there was a fix recently, but apparently it was not enough. > > > With the slash, it should even work on older git. > > > > That is a different issue. It worked before my messing around with the > > vyatta-iproute.git repository. > > From your description: > > -- snip -- > In old repository > $ git-submodule update > ... > Getting pack list for > http://git.vyatta.com/home/shemminger/vyatta-iproute/.git/ > error: The requested URL returned error: 403 > error: Unable to find 8d971aff46015fc156d5b74254d21831d275963c under > http://git.vyatta.com/vyatta-iproute.git > Cannot obtain needed object 8d971aff46015fc156d5b74254d21831d275963c > Unable to checkout '79b4dbe51b84fdf37fdc9cb8b17819526508a60c' in submodule > path 'pkgs/vyatta-iproute' > -- snap -- > > So there was some type of invalid HTTP request, and then the hin tat 8d971 > was not found under http://.../vyatta-iproute.git (note the absence of the > trailing slash). Of course, since it is 403 ("forbidden"), and not 30x > (which I thought I read), it could be a different error altogether. > > In any case, this means that your submodule is not at all fine. > > Ciao, > Dscho > The problem was that the rebuilt repository had an alternate file pointing to a different and inaccessible location. Rebuilding again fixed the problem. Thanks for your help. - 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
