git/list[1] front-page[2] threads[3] people[4] search[5] about
 

git problems on Kernel.org?

From
FSFrank Sorenson <frank@tuxrocks.com>
Date
Sep 11, 2005, 07:58 UTC
Message-ID
<4323E3C0.1090109@tuxrocks.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Something appears to be something odd going on with the git repos on kernel.org, including both the git and linux trees. I believe that I've tracked down the problem to differences that occur between the repos located at the various IPs that kernel.org translates to (zeus-pub1: 204.152.191.5 and zeus-pub2: 204.152.191.37).

In this case, it appears that the repo located at zeus-pub1 has been updated, but the changes haven't propagated over to zeus-pub2 yet. The result is that one call fetches a list of objects, but the next call goes to the other IP, and it can't find an object it needs, so it ends up dying.

This is probably a temporary error that will periodically (and probably very rarely) occur when pulling from a source with more than a single IP and some lag before the mirror is updated.

Is this an issue that we need to watch for and program around (other than forcing www.kernel.org's IP in /etc/hosts), or is it just one of those things that should be such a rare occurrance that we shouldn't have to worry about it?

Thanks,
Frank
- --
Frank Sorenson - KD7TZK
Systems Manager, Computer Science Department
Brigham Young University
frank@tuxrocks.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFDI+PAaI0dwg4A47wRAgEhAKDPjvyHZwTSw/e+FwE5BXtpH2novACdGBaF +R64XoAYx+WXGjbczO+ZQtY= =vCRj -----END PGP SIGNATURE-----

Next: A Large Angry SCM
Message 1 of 3 in “git problems on Kernel.org?”
  1. Frank SorensonSep 11, 2005
  2. A Large Angry SCMSep 11, 2005
  3. Nathan LaredoSep 11, 2005

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.