Ted Zlatanov writes: > On Sun, 18 Apr 2010 11:51:34 +0200 Andreas Seltenreich wrote: > > AS> Tim Landscheidt writes: > >>> Is the repo "stable" now? > > AS> Not quite. Since Ted's push, the packed refs disappeared from the > AS> info/refs file again and a clone via http[1] lacked all tags and > AS> branches except for the master branch. Maybe somehow > AS> git-update-server-info is not doing its job? > > The repo is stable AFAIK. I can pull an update I've committed; all the > branches and tags show up on a new HTTP clone and on existing HTTP > clones. Andreas, I'm not sure why it's not working for you. I'm on > git version 1.7.0.4. Did you happen to do the test clone after 10:12 UTC? I've set up a cronjob on friday to monitor some directories on git.gnus.org to get more clues while debugging (output attached). The info/refs file oscillated between 1k and 32k (i.e., including the packed-refs or not). It appears to shrink on each push and is reset to 32k at 10:12 UTC each day. (Maybe a cronjob on your side?) This correlates with whether I see the packed-refs in a fresh clone[1] or not. I checked locally to confirm that git-update-server-info groks packed refs and updates the info/refs file properly. A hook running git-update-server-info is also activated on git.gnus.org, but I guess those hooks aren't run at all on WebDAV accesses? Here's some more evidence from the log mentioned yesterday[2] that pushing placed a bogus (see file size) info/refs file: ,---- | > PUT /gnus.git/info/refs HTTP/1.1 | User-Agent: git/1.5.6.5 | Host: git.gnus.org | Accept: */* | If: () | Content-Length: 59 | Expect: 100-continue `---- I haven't tested to push yet with the newer git, but as the release notes say that packed-refs are supported since 1.4.x, I'm not convinced that a newer git behaves differently. I see some ways to go from here: - Use smart protocols (git/ssh) instead of dumb ones (http/webdav). This way the info/* files aren't needed. As a bonus, the communication is much more efficient. - Make sure the hooks are run so git-update-server-info can generate a valid info/refs no matter what git PUT there through WebDAV. - Fix git to PUT a proper info/refs file. - Get rid of packed-refs, as suggested by Andreas, may also work. regards, andreas Footnotes: [1] also "git ls-remote", a faster way to check [2] http://gate450.dyndns.org/~andreas/push-debug.txt.gz