[haiku-development] Re: haiku and buildtools trees inaccessible, destroys .git/FETCH_HEAD: has git URL changed?

  • From: kallisti5 <kallisti5@xxxxxxxxxxx>
  • To: haiku-development@xxxxxxxxxxxxx
  • Date: Sat, 29 Apr 2017 14:46:42 -0500

On 2017-04-28 16:56, Alexander G. M. Smith wrote:

Thomas Mueller wrote on Fri, 28 Apr 2017 02:57:28 +0000
Is this a temporary downtime, or did something change? Do I need to change the location?

Haiku website shows
git clone git://git.haiku-os.org/haiku
and
git clone git://git.haiku-os.org/buildtools

A few months ago (some time last year) the git protocol interface for
anonymous users stopped working.  However, the https one still works,
use https://git.haiku-os.org/haiku for the haiku repository URL.

vmrepo is running an old version of suse with likely an older
version of git.  We see a bunch of git-unpack processes that hang up
which will break the checkout using git:// after some time.

Jessicah pointed this out to me this morning (likely based on this thread)
I killed off all the hung git-unpack processes and restarted the git services.

git:// should be working now.

Most developers are using the ssh protocol to access the git repos
on git.haiku-os.org... so when they get hung up it takes a while
for someone to notice.

If you don't have commit access, the git repo at github is kept
in sync with our tree.  If you have commit access (and are well
versed in git) you can even do something like this:

$ git remote -v
origin  git@xxxxxxxxxx:kallisti5/haiku.git (fetch)
origin  git@xxxxxxxxxx:kallisti5/haiku.git (push)
upstream        ssh://git.haiku-os.org/haiku (fetch)
upstream        ssh://git.haiku-os.org/haiku (push)

We need to schedule the upgrades... they kind of fell through
the cracks.

 -- Alex

Other related posts:

  1. Home
  2. haiku-development
  3. Archive
  4. 04-2017