'git pull' from Linus' tree doesn't work for me any more
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
Quoted 8 lines · Rafael J. Wysocki
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 fromgit://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.gitI 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
Quoted 11 lines · Linus Torvalds
Quoted 8 lines · Rafael J. Wysocki
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 fromgit://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.gitI see this on two different machines.
Quoted 8 lines
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
Pulled this morning PDT,
Without any issues.
justin P. Mattock
Quoted 29 lines · Rafael J. Wysocki
Quoted 11 lines · Linus Torvalds
Quoted 8 lines · Rafael J. Wysocki
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 fromgit://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.gitI see this on two different machines.
Quoted 8 lines
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 [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Quoted 5 lines · Rafael J. Wysocki
Quoted 2 lines
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
Quoted 9 lines · H. Peter Anvin
Quoted 5 lines · Rafael J. Wysocki
Quoted 2 lines
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
Quoted 2 lines · Rafael J. Wysocki
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.
Quoted 1 line
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
Quoted 45 lines · Linus Torvalds
Quoted 2 lines · Rafael J. Wysocki
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
Makefilesettings, 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.
Quoted 3 lines
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
Looks like I need to upgrade
My git. At the moment using
1.5.6.3.
justin P. Mattock
Quoted 63 lines · Linus Torvalds
Quoted 2 lines · Rafael J. Wysocki
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
Makefilesettings, 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 [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/