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

Is there really a need for packed-refs to exist for rsync://?

From
RBRalf Baechle <ralf@linux-mips.org>
Date
Apr 16, 2008, 09:42 UTC
Message-ID
<20080416094222.GA23987@linux-mips.org>

Trying to clone a repository using its rsync:// URL I'm getting this error message:

[...] sent 150 bytes received 363603747 bytes 80800866.00 bytes/sec total size is 363559095 speedup is 1.00 rsync: link_stat "/scm/upstream-linus.git/packed-refs" (in pub) failed: No such file or directory (2) rsync error: some files could not be transferred (code 23) at main.c(1385) [receiver=2.6.9] fatal: Could not run rsync to get refs $

The same repository can be cloned with no problem using its git:// and http:// URLs so I guess the rsync:// method is broken here. This is using git 1.5.4.1.

Cheers,
  Ralf
Message 1 of 1 in “Is there really a need for packed-refs to exist for rsync://?”
  1. Ralf BaechleApr 16, 2008

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.