omapzoom tree broken?

omapzoom tree broken?

[Russell King - ARM Linux]

When trying to fetch the omapzoom tree, I get:

got a4ae90758b3c38012c875a62d0dd8a20a30e413b
walk a4ae90758b3c38012c875a62d0dd8a20a30e413b
Getting alternates list for http://git.omapzoom.org/repo/omapkernel
Getting pack list for http://git.omapzoom.org/repo/omapkernel
Getting index for pack 567cbb972dbfa42338e1269ca4a4a03ec2b1d35f
Resuming fetch of index for pack 567cbb972dbfa42338e1269ca4a4a03ec2b1d35f at byte 5890048
error: wrong index v1 file size in .git/objects/pack/pack-567cbb972dbfa42338e1269ca4a4a03ec2b1d35f.idx
Segmentation fault

Could we have it accessible via git the protocol please, rather than
http?

Re: omapzoom tree broken?

[Ashwin Bihari]

On Tue, Sep 9, 2008 at 1:59 PM, Russell King - ARM Linux
<linux@arm.linux.org.uk> wrote:
> When trying to fetch the omapzoom tree, I get:
>
> got a4ae90758b3c38012c875a62d0dd8a20a30e413b
> walk a4ae90758b3c38012c875a62d0dd8a20a30e413b
> Getting alternates list for http://git.omapzoom.org/repo/omapkernel
> Getting pack list for http://git.omapzoom.org/repo/omapkernel
> Getting index for pack 567cbb972dbfa42338e1269ca4a4a03ec2b1d35f
> Resuming fetch of index for pack 567cbb972dbfa42338e1269ca4a4a03ec2b1d35f at byte 5890048
> error: wrong index v1 file size in .git/objects/pack/pack-567cbb972dbfa42338e1269ca4a4a03ec2b1d35f.idx
> Segmentation fault
>
> Could we have it accessible via git the protocol please, rather than
> http?

Russell,

I just pulled the omapzoom tree for the first time and it had no
problems in the "git clone". Perhaps something to do with fetching
into an existing repo?

~ Ashwin

Re: omapzoom tree broken?

[Russell King - ARM Linux]

On Tue, Sep 09, 2008 at 02:37:42PM -0400, Ashwin Bihari wrote:
> On Tue, Sep 9, 2008 at 1:59 PM, Russell King - ARM Linux
> <linux@arm.linux.org.uk> wrote:
> > When trying to fetch the omapzoom tree, I get:
> >
> > got a4ae90758b3c38012c875a62d0dd8a20a30e413b
> > walk a4ae90758b3c38012c875a62d0dd8a20a30e413b
> > Getting alternates list for http://git.omapzoom.org/repo/omapkernel
> > Getting pack list for http://git.omapzoom.org/repo/omapkernel
> > Getting index for pack 567cbb972dbfa42338e1269ca4a4a03ec2b1d35f
> > Resuming fetch of index for pack 567cbb972dbfa42338e1269ca4a4a03ec2b1d35f at byte 5890048
> > error: wrong index v1 file size in .git/objects/pack/pack-567cbb972dbfa42338e1269ca4a4a03ec2b1d35f.idx
> > Segmentation fault
> >
> > Could we have it accessible via git the protocol please, rather than
> > http?
> 
> Russell,
> 
> I just pulled the omapzoom tree for the first time and it had no
> problems in the "git clone". Perhaps something to do with fetching
> into an existing repo?

Looks like the pack index was corrupted; removing the one it just fetched
and repulling has made it happier.

However, it's made me unhappier.  Again, can we please have it accessible
via the git protocol.  Or at least can whoever looks after that tree avoid
repacking it except maybe once a month?

Why?  I don't want to have to keep on fetching 300 odd MB of pack files
every time I pull from this tree.  10 minutes into my current pull and
I only have 80MB... another 220MB to go.  IOW, 45 minutes for a pull.

This really isn't practical.

Re: omapzoom tree broken?

[Felipe Balbi]

On Tue, Sep 09, 2008 at 07:54:15PM +0100, Russell King - ARM Linux wrote:
> Looks like the pack index was corrupted; removing the one it just fetched
> and repulling has made it happier.
> 
> However, it's made me unhappier.  Again, can we please have it accessible
> via the git protocol.  Or at least can whoever looks after that tree avoid
> repacking it except maybe once a month?
> 
> Why?  I don't want to have to keep on fetching 300 odd MB of pack files
> every time I pull from this tree.  10 minutes into my current pull and
> I only have 80MB... another 220MB to go.  IOW, 45 minutes for a pull.
> 
> This really isn't practical.

Sure, repacking should be avoided on servers for that. Do what you want
with your local copy and repack sure helps making git a bit faster,
still it's not good for the server side since we'd have to pull the
packs again and again.

-- 
balbi

RE: omapzoom tree broken?

[Pandita, Vikram]

Russell

> -----Original Message-----
> From: linux-omap-owner@vger.kernel.org [mailto:linux-omap-owner@vger.kernel.org] On Behalf Of Russell
> King - ARM Linux
> Sent: Wednesday, September 10, 2008 12:24 AM
> To: Ashwin Bihari
> Cc: linux-omap@vger.kernel.org
> Subject: Re: omapzoom tree broken?
> 
> > >
> > > Could we have it accessible via git the protocol please, rather than
> > > http?
> >
> > Russell,
> >
> > I just pulled the omapzoom tree for the first time and it had no
> > problems in the "git clone". Perhaps something to do with fetching
> > into an existing repo?
> 
> Looks like the pack index was corrupted; removing the one it just fetched
> and repulling has made it happier.
> 
> However, it's made me unhappier.  Again, can we please have it accessible
> via the git protocol.  

Yes TI is looking into the option of enabling GIT protocol for the zoom tree.

>Or at least can whoever looks after that tree avoid
> repacking it except maybe once a month?

Yes I will take care not to repack often, till git protocol is available.

> 
> Why?  I don't want to have to keep on fetching 300 odd MB of pack files
> every time I pull from this tree.  10 minutes into my current pull and
> I only have 80MB... another 220MB to go.  IOW, 45 minutes for a pull.
> 
> This really isn't practical.

Agreed.

> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html