Error with GIT Repository
in [PgSql]
|
From: Stephen Frost on 10 Jun 2010 11:44 * Andrew Dunstan (andrew(a)dunslane.net) wrote: > Luxenberg, Scott I. wrote: > >I have been trying to create/run a build farm as part of a project I am > >working on. > > That seems an odd thing to do since we have one ... To clarify, he's setting up a build farm *member*. :) > >However, I have noticed the primary git repostitory, > >git.postgresql.org/git, does not seem to be working. Namely, whenever I > >try to clone the directory, I receive this error: > > > >Error: Unable to find 5e4933c31d3cd2750ee1793efe6eca43055fb273e under > >http://git.postgresql.org/git/postgresql.git > >Cannot obtain needed blob 5e4933c31d3cd2750ee1793efe6eca4305fb273e while > >processing commit c5609c66ce2ee4fdb180be95721252b47f90499 > >Error: fetch failed. > > > >I thought it would be prudent to notify the list so someone could > >possibly check into this. > > > Why are you cloning over http? Here is the best way to clone, which > seems to be working: Unfortunately for us, the port that git uses isn't currently allowed outbound by our corporate firewall. I expect that to be true for other PG users who want git and for some build-farm members, so I think we really need to support git cloning over http. As a side-note, it works just fine from git-hub's http mirror and that's what we've been playing with, but I don't know if we want to recommend that for build-farm members.. Thanks! Stephen
From: Andres Freund on 11 Jun 2010 13:12 On Thursday 10 June 2010 19:30:00 Magnus Hagander wrote: > On Thu, Jun 10, 2010 at 18:20, Stephen Frost <sfrost(a)snowman.net> wrote: > > * Andrew Dunstan (andrew(a)dunslane.net) wrote: > >> I don't see why not. Buildfarm members are going to have to reset their > >> repos when we finally cut over in a few months. Luckily, this is a > >> fairly painless operation - blow away the repo and change the config > >> file and the script will resync as if nothing had happened. > > > > Should we stop bothering to offer http://git.postgresql.org then..? Or > > No, we should not. > > Especially if someone has a clue how to do it. The last time I fixed > it by runnin repack, but that didn't work this time. I have no clue > why it's asking for a file that doesn't exist. Does the repo run 'update-server-info' in some hook? Andres -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
From: Magnus Hagander on 11 Jun 2010 13:19 On Fri, Jun 11, 2010 at 19:12, Andres Freund <andres(a)anarazel.de> wrote: > On Thursday 10 June 2010 19:30:00 Magnus Hagander wrote: >> On Thu, Jun 10, 2010 at 18:20, Stephen Frost <sfrost(a)snowman.net> wrote: >> > * Andrew Dunstan (andrew(a)dunslane.net) wrote: >> >> I don't see why not. Buildfarm members are going to have to reset their >> >> repos when we finally cut over in a few months. Luckily, this is a >> >> fairly painless operation - blow away the repo and change the config >> >> file and the script will resync as if nothing had happened. >> > >> > Should we stop bothering to offer http://git.postgresql.org then..? �Or >> >> No, we should not. >> >> Especially if someone has a clue how to do it. The last time I fixed >> it by runnin repack, but that didn't work this time. I have no clue >> why it's asking for a file that doesn't exist. > Does the repo run �'update-server-info' �in some hook? Yup, it runs after every time it pulls from cvs. -- Magnus Hagander Me: http://www.hagander.net/ Work: http://www.redpill-linpro.com/ -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
From: Daniel Farina on 30 Jun 2010 18:22 On Fri, Jun 11, 2010 at 10:19 AM, Magnus Hagander <magnus(a)hagander.net> wrote: >>> Especially if someone has a clue how to do it. The last time I fixed >>> it by runnin repack, but that didn't work this time. I have no clue >>> why it's asking for a file that doesn't exist. >> Does the repo run �'update-server-info' �in some hook? > > Yup, it runs after every time it pulls from cvs. Is this still a problem? I was just noticing this thread unceremoniously died, and a long time ago now I remembering discussing a problem involving the Postgres git mirror accumulating packfiles eternally. It seemed that whatever repacking scheme was used would get rid of loose objects, turning them into packs but never consolidate packs. Why not just run 'git gc'? This is probably the only quasi-regularly required maintenance command, so much so that git (I think) runs it from time to time when certain thresholds are passed in modern day. (For a clone-source it is probably a good idea to run it a bit more liberally) fdr -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
First
|
Prev
|
Pages: 1 2 Prev: [PERFORM] No hash join across partitioned tables? Next: [HACKERS] Error with GIT Repository |