[OT] 'git pull' from Linus' tree doesn't work for me any more

[OT] 'git pull' from Linus' tree doesn't work for me any more

[Rafael J. Wysocki]

Hi,

Does anybody else see something like this after the latest push from Linus:

~/devel/linux-2.6> git pull
fatal: The remote end hung up unexpectedly
Cannot get the repository state from git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git

?

I see this on two different machines.

Thanks,
Rafael

Re: [OT] 'git pull' from Linus' tree doesn't work for me any more

[Linus Torvalds]

On Thu, 21 Aug 2008, Rafael J. Wysocki wrote:
> 
> Does anybody else see something like this after the latest push from Linus:
> 
> ~/devel/linux-2.6> git pull
> fatal: The remote end hung up unexpectedly
> Cannot get the repository state from git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
> 
> I see this on two different machines.

It might easily be just a temporary glitch in the matrix.

It happens sometimes because the kernel.org machines use rsync to 
synchronize with each other, and since it's not really a git-aware 
protocol, rsync might copy the branch files _before_ it copies the object 
files.

It starts working after a few minutes when the rsync has completed.

		Linus

Re: [OT] 'git pull' from Linus' tree doesn't work for me any more

[Rafael J. Wysocki]

On Thursday, 21 of August 2008, Linus Torvalds wrote:
> 
> On Thu, 21 Aug 2008, Rafael J. Wysocki wrote:
> > 
> > Does anybody else see something like this after the latest push from Linus:
> > 
> > ~/devel/linux-2.6> git pull
> > fatal: The remote end hung up unexpectedly
> > Cannot get the repository state from git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
> > 
> > I see this on two different machines.
> 
> It might easily be just a temporary glitch in the matrix.
> 
> It happens sometimes because the kernel.org machines use rsync to 
> synchronize with each other, and since it's not really a git-aware 
> protocol, rsync might copy the branch files _before_ it copies the object 
> files.
> 
> It starts working after a few minutes when the rsync has completed.

Well, it hasn't been working for a couple of hours now ...

Rafael

Re: [OT] 'git pull' from Linus' tree doesn't work for me any more

[Justin P. Mattock]

Pulled this morning  PDT,
Without any issues.

justin P. Mattock



On Aug 20, 2008, at 3:58 PM, "Rafael J. Wysocki" <rjw@sisk.pl> wrote:

> On Thursday, 21 of August 2008, Linus Torvalds wrote:
>>
>> On Thu, 21 Aug 2008, Rafael J. Wysocki wrote:
>>>
>>> Does anybody else see something like this after the latest push  
>>> from Linus:
>>>
>>> ~/devel/linux-2.6> git pull
>>> fatal: The remote end hung up unexpectedly
>>> Cannot get the repository state from git://git.kernel.org/pub/scm/ 
>>> linux/kernel/git/torvalds/linux-2.6.git
>>>
>>> I see this on two different machines.
>>
>> It might easily be just a temporary glitch in the matrix.
>>
>> It happens sometimes because the kernel.org machines use rsync to
>> synchronize with each other, and since it's not really a git-aware
>> protocol, rsync might copy the branch files _before_ it copies the  
>> object
>> files.
>>
>> It starts working after a few minutes when the rsync has completed.
>
> Well, it hasn't been working for a couple of hours now ...
>
> Rafael
> --
> To unsubscribe from this list: send the line "unsubscribe linux- 
> kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

Re: [OT] 'git pull' from Linus' tree doesn't work for me any more

[H. Peter Anvin]

Rafael J. Wysocki wrote:
>>
>> It starts working after a few minutes when the rsync has completed.
> 
> Well, it hasn't been working for a couple of hours now ...
> 

My fault; I forgot to kick xinetd after updating the configuration file 
for the git-daemon -> git daemon rename.

	-hpa

Re: [OT] 'git pull' from Linus' tree doesn't work for me any more

[Linus Torvalds]

On Thu, 21 Aug 2008, Rafael J. Wysocki wrote:
> 
> Well, it hasn't been working for a couple of hours now ...

Hmm. I just tested it myself, and it worked fine for me to just update 
another machine by pulling from git.kernel.org.

What version of git do you have? One thing that changed recently is that 
at least some kernel.org git binaries got updated to 1.6.0, and if you 
have a really ancient version of git (Debian 'stable' aka 'rubbish' ships 
with something two years old), you'd better upgrade.

>From the 1.6.0 announcement:

  GIT v1.6.0 Release Notes
  ========================
  
  User visible changes
  --------------------
  
  With the default Makefile settings, most of the programs are now
  installed outside your $PATH, except for "git", "gitk" and
  some server side programs that need to be accessible for technical
  reasons.  Invoking a git subcommand as "git-xyzzy" from the command
  line has been deprecated since early 2006 (and officially announced in
  1.5.4 release notes); use of them from your scripts after adding
  output from "git --exec-path" to the $PATH is still supported in this
  release, but users are again strongly encouraged to adjust their
  scripts to use "git xyzzy" form, as we will stop installing
  "git-xyzzy" hardlinks for built-in commands in later releases.
  
  An earlier change to page "git status" output was overwhelmingly unpopular
  and has been reverted.
  
  Source changes needed for porting to MinGW environment are now all in the
  main git.git codebase.
  
  By default, packfiles created with this version uses delta-base-offset
  encoding introduced in v1.4.4.  Pack idx files are using version 2 that
  allows larger packs and added robustness thanks to its CRC checking,
  introduced in v1.5.2 and v1.4.4.5.  If you want to keep your repositories
  backwards compatible past these versions, set repack.useDeltaBaseOffset
  to false or pack.indexVersion to 1, respectively.
  
and no, I am not at all interested in helping Debian continue to ship
git versions almost two years old, and much inferior to modern versions. 
So I'm not going to set the flag that makes it work with old gits.
  
  		Linus

Re: [OT] 'git pull' from Linus' tree doesn't work for me any more

[Rafael J. Wysocki]

On Thursday, 21 of August 2008, Linus Torvalds wrote:
> 
> On Thu, 21 Aug 2008, Rafael J. Wysocki wrote:
> > 
> > Well, it hasn't been working for a couple of hours now ...
> 
> Hmm. I just tested it myself, and it worked fine for me to just update 
> another machine by pulling from git.kernel.org.
> 
> What version of git do you have? One thing that changed recently is that 
> at least some kernel.org git binaries got updated to 1.6.0, and if you 
> have a really ancient version of git (Debian 'stable' aka 'rubbish' ships 
> with something two years old), you'd better upgrade.
> 
> From the 1.6.0 announcement:
> 
>   GIT v1.6.0 Release Notes
>   ========================
>   
>   User visible changes
>   --------------------
>   
>   With the default Makefile settings, most of the programs are now
>   installed outside your $PATH, except for "git", "gitk" and
>   some server side programs that need to be accessible for technical
>   reasons.  Invoking a git subcommand as "git-xyzzy" from the command
>   line has been deprecated since early 2006 (and officially announced in
>   1.5.4 release notes); use of them from your scripts after adding
>   output from "git --exec-path" to the $PATH is still supported in this
>   release, but users are again strongly encouraged to adjust their
>   scripts to use "git xyzzy" form, as we will stop installing
>   "git-xyzzy" hardlinks for built-in commands in later releases.
>   
>   An earlier change to page "git status" output was overwhelmingly unpopular
>   and has been reverted.
>   
>   Source changes needed for porting to MinGW environment are now all in the
>   main git.git codebase.
>   
>   By default, packfiles created with this version uses delta-base-offset
>   encoding introduced in v1.4.4.  Pack idx files are using version 2 that
>   allows larger packs and added robustness thanks to its CRC checking,
>   introduced in v1.5.2 and v1.4.4.5.  If you want to keep your repositories
>   backwards compatible past these versions, set repack.useDeltaBaseOffset
>   to false or pack.indexVersion to 1, respectively.
>   
> and no, I am not at all interested in helping Debian continue to ship
> git versions almost two years old, and much inferior to modern versions. 
> So I'm not going to set the flag that makes it work with old gits.

I have 1.5.2.4 and it works now.

Thanks,
Rafael

Re: [OT] 'git pull' from Linus' tree doesn't work for me any more

[Rafael J. Wysocki]

On Thursday, 21 of August 2008, H. Peter Anvin wrote:
> Rafael J. Wysocki wrote:
> >>
> >> It starts working after a few minutes when the rsync has completed.
> > 
> > Well, it hasn't been working for a couple of hours now ...
> > 
> 
> My fault; I forgot to kick xinetd after updating the configuration file 
> for the git-daemon -> git daemon rename.

It works now, thanks for fixing.

Rafael

Re: [OT] 'git pull' from Linus' tree doesn't work for me any more

[Justin P. Mattock]

Looks like I need to upgrade
My git. At the moment using
1.5.6.3.

justin P. Mattock



On Aug 20, 2008, at 4:07 PM, Linus Torvalds <torvalds@linux-foundation.org 
 > wrote:

>
>
> On Thu, 21 Aug 2008, Rafael J. Wysocki wrote:
>>
>> Well, it hasn't been working for a couple of hours now ...
>
> Hmm. I just tested it myself, and it worked fine for me to just update
> another machine by pulling from git.kernel.org.
>
> What version of git do you have? One thing that changed recently is  
> that
> at least some kernel.org git binaries got updated to 1.6.0, and if you
> have a really ancient version of git (Debian 'stable' aka 'rubbish'  
> ships
> with something two years old), you'd better upgrade.
>
> From the 1.6.0 announcement:
>
>  GIT v1.6.0 Release Notes
>  ========================
>
>  User visible changes
>  --------------------
>
>  With the default Makefile settings, most of the programs are now
>  installed outside your $PATH, except for "git", "gitk" and
>  some server side programs that need to be accessible for technical
>  reasons.  Invoking a git subcommand as "git-xyzzy" from the command
>  line has been deprecated since early 2006 (and officially announced  
> in
>  1.5.4 release notes); use of them from your scripts after adding
>  output from "git --exec-path" to the $PATH is still supported in this
>  release, but users are again strongly encouraged to adjust their
>  scripts to use "git xyzzy" form, as we will stop installing
>  "git-xyzzy" hardlinks for built-in commands in later releases.
>
>  An earlier change to page "git status" output was overwhelmingly  
> unpopular
>  and has been reverted.
>
>  Source changes needed for porting to MinGW environment are now all  
> in the
>  main git.git codebase.
>
>  By default, packfiles created with this version uses delta-base- 
> offset
>  encoding introduced in v1.4.4.  Pack idx files are using version 2  
> that
>  allows larger packs and added robustness thanks to its CRC checking,
>  introduced in v1.5.2 and v1.4.4.5.  If you want to keep your  
> repositories
>  backwards compatible past these versions, set  
> repack.useDeltaBaseOffset
>  to false or pack.indexVersion to 1, respectively.
>
> and no, I am not at all interested in helping Debian continue to ship
> git versions almost two years old, and much inferior to modern  
> versions.
> So I'm not going to set the flag that makes it work with old gits.
>
>          Linus
> --
> To unsubscribe from this list: send the line "unsubscribe linux- 
> kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/