Error with GIT Repository
in [PgSql]
|
From: Andrew Dunstan on 10 Jun 2010 11:26 Luxenberg, Scott I. wrote: > Greetings all, > > 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 ... > 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: [andrew(a)sophia ]$ git clone --mirror git://git.postgresql.org/git/postgresql.git Initialized empty Git repository in /home/andrew/postgresql.git/ remote: Counting objects: 376865, done. remote: Compressing objects: 100% (87569/87569), done. remote: Total 376865 (delta 310187), reused 352950 (delta 287485) Receiving objects: 100% (376865/376865), 178.73 MiB | 251 KiB/s, done. Resolving deltas: 100% (310187/310187), done. [andrew(a)sophia ]$ cheers andrew -- 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: Andrew Dunstan on 10 Jun 2010 12:15 Stephen Frost wrote: > * 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*. :) > Aha. Amazing the difference one little word can make ... > > 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.. > > > 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. cheers andrew -- 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: Stephen Frost on 10 Jun 2010 12:20 * 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 do we expect it to get fixed and work correctly once we cut over and rebuild? Also, perhaps we could list the git-hub option on the wiki (http://wiki.postgresql.org/wiki/Other_Git_Repositories)? (and, yea, it's the same me) Thanks, Stephen
From: Magnus Hagander on 10 Jun 2010 13:30 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. -- 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: Alvaro Herrera on 10 Jun 2010 15:23 Excerpts from Andrew Dunstan's message of jue jun 10 11:26:59 -0400 2010: > Why are you cloning over http? Here is the best way to clone, which > seems to be working: > > [andrew(a)sophia ]$ git clone --mirror > git://git.postgresql.org/git/postgresql.git > Initialized empty Git repository in /home/andrew/postgresql.git/ In case you're a git-ignorant like me and are wondering why the above does not produce a usable checkout, the complete recipe is here: http://archives.postgresql.org/message-id/20090602162347.GF23972(a)yugib.highrise.ca (in short, you need a git clone --reference) -- Álvaro Herrera <alvherre(a)commandprompt.com> The PostgreSQL Company - Command Prompt, Inc. PostgreSQL Replication, Consulting, Custom Development, 24x7 support -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
|
Next
|
Last
Pages: 1 2 Prev: [PERFORM] No hash join across partitioned tables? Next: [HACKERS] Error with GIT Repository |