[gentoo-scm] Testing git gx86 repos (and status update)

[gentoo-scm] Testing git gx86 repos (and status update)

[Michał Górny]

[-- Attachment #1: Type: text/plain, Size: 2429 bytes --]

Hello, everyone.

Diego has given me a pretty neat machine to do some git testing, so I
have a few repos for you to play with. But first some status update.

I have four public repos now:

1. history.git -- that contains cvs2git conversion made by rich0 with
some followup cleanup commits. You basically don't want that since it's
huge :). But if you really want to, you should be able to use 'git
replace' to attach it to the dev repo.

2. dev.git -- the main development repository. It starts with squashed
tree of history.git, and that's where developers commit ebuild changes
and stuff. It comes with the update hook that makes sure commits
on master are signed and so on. Currently, signature validation uses
pre-defined key list.

3. user.git -- user syncing repository. It is auto-synced to dev.git
and some other repos (gentoo-news, glsas, herds.xml, dtds), and has
auto-generated metadata cache. Intended to be read-only.

4. rsync.git -- repository used to feed rsync. It is auto-synced to
user.git, with modified layout.conf and thickened and signed Manifests.
No ChangeLogs at the moment. Read-only as well.

The auto-syncing scripts are pulling after each push and every 10
minutes. Best case, your commit shows up in rsync.git in <2 minutes.

The three latter repos are also mirrored to github:

2. https://github.com/gx86-git-test/gx86-test-dev
3. https://github.com/gx86-git-test/gx86-test-user
4. https://github.com/gx86-git-test/gx86-test-rsync

GitHub mirrors are read-only and auto-updated. You can submit pull
requests to dev repo but developers will be supposed to pull them in
locally rather than through github.

Access to main repos goes through SSH currently. If you want it, please
send me your public SSH key in a GPG signed mail. Since this is just
a testing repo, you don't have to be a developer to have it. Note that
this requires IPv6 currently, so get a tunnel if you don't have one
yet :).

Read-only access preferred through github (to offload our server). For
populating rsync mirrors, I'm planning to support two methods:

a. using git repo -- git pull in directory used for rsync :),

b. using rsync -- more space-efficient, slower, non-atomic. Does not
work since I didn't set up rsync daemon on the server yet :).

Current versions of my server scripts:
- https://github.com/mgorny/git-gx86-tools

-- 
Best regards,
Michał Górny

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 949 bytes --]

[gentoo-scm] Re: [gentoo-dev] Testing git gx86 repos (and status update)

[Michał Górny]

[-- Attachment #1: Type: text/plain, Size: 652 bytes --]

Dnia 2014-09-29, o godz. 08:59:44
Michał Górny <mgorny@gentoo.org> napisał(a):

> Access to main repos goes through SSH currently. If you want it, please
> send me your public SSH key in a GPG signed mail. Since this is just
> a testing repo, you don't have to be a developer to have it. Note that
> this requires IPv6 currently, so get a tunnel if you don't have one
> yet :).

Small update: I've grepped all active Gentoo developers from LDAP
and added their SSH and GPG keys.

To access the repo:

  git clone mgorny@c2g.excelsior.flameeyes.eu:dev.git

We can be found on #gentoo-scm @ freenode.

-- 
Best regards,
Michał Górny

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 949 bytes --]

Re: [gentoo-scm] Testing git gx86 repos (and status update)

[Michał Górny]

[-- Attachment #1: Type: text/plain, Size: 1539 bytes --]

Dnia 2014-09-29, o godz. 08:59:44
Michał Górny <mgorny@gentoo.org> napisał(a):

> Access to main repos goes through SSH currently. If you want it, please
> send me your public SSH key in a GPG signed mail. Since this is just
> a testing repo, you don't have to be a developer to have it. Note that
> this requires IPv6 currently, so get a tunnel if you don't have one
> yet :).
> 
> Read-only access preferred through github (to offload our server). For
> populating rsync mirrors, I'm planning to support two methods:
> 
> a. using git repo -- git pull in directory used for rsync :),
> 
> b. using rsync -- more space-efficient, slower, non-atomic. Does not
> work since I didn't set up rsync daemon on the server yet :).

Two more news:

1. I have started git & rsync daemons (the latter on non-standard port
8873).

2. Peter Stuge has provided IPv4 tunnel to the server @ c2gv4.stuge.se.

As for git daemon, it is more formality than real need. You are still
encouraged to use github. But if you really want to play with it:

  git clone git://c2g.excelsior.flameeyes.eu/user.git

As for rsync, it's more for backwards compatibility. It's better to
pull in rsync.git from github :). But if you want to play with it:

  rsync -va rsync://c2g.excelsior.flameeyes.eu:8873/gentoo-portage \
  portage

And the IPv4 host:

  git clone c2gv4.stuge.se:dev.git
  git clone git://c2gv4.stuge.se/user.git
  rsync -va rsync://c2gv4.stuge.se:8873/gentoo-portage portage


-- 
Best regards,
Michał Górny

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 949 bytes --]