| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Historically, this hook put the certs in a ref named refs/push-certs.
However, git does *NOT* replicate single-level refs, and this meant that
gitolite mirroring did not replicate the push-certs!
Trying to push them explicitly causes this error:
```
remote: error: refusing to create funny ref 'refs/push-certs' remotely
```
Upstream Git has good reasons as to why not to replicate single-level
refs: https://lore.kernel.org/git/robbat2-20211115T063838-612792475Z@orbis-terrarum.net/
As a good-enough solution, use the namespace of meta/ for the refs.
This is already used in other systems:
- kernel.org refs/meta/cgit
- gerrit refs/meta/config
- GitBlit reflog: refs/meta/gitblit https://www.gitblit.com/administration.html#H12
- cc-utils refs/meta/ci
- JGit refs/meta/push-certs https://www.ibm.com/docs/en/radfws/9.6.1?topic=SSRTLW_9.6.1/org.eclipse.egit.doc/help/JGit/New_and_Noteworthy/4.1/4.1.htm
To migrate from old to new, for each repo, you must explicitly run:
git update-ref refs/meta/push-certs refs/push-certs
Then the hook will populate both refs.
You can remove the old ref after that:
git update-ref -d refs/push-certs
Signed-off-by: Robin H. Johnson <robbat2@gentoo.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
with perl 5.32.0 trying to use ukm gives:
```
$ ssh gitolite@localhost ukm
Enter passphrase for key '/home/kousu/.ssh/id_rsa':
FATAL: Can't use global $_ in "my" at /usr/lib/gitolite/commands/ukm line 296, near "($_"
Execution of /usr/lib/gitolite/commands/ukm aborted due to compilation errors.
```
This fixes it
```
$ ssh gitolite@localhost ukm list
Enter passphrase for key '/home/kousu/.ssh/id_rsa':
Hello alice, you manage the following keys:
fingerprint userid keyid
SHA256:VxHhqhOq5GxpPPUrYMeFMly4Mdc3YlP40qkLX4gr5fI alice alice
```
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This affects the mirroring code and documentation:
"slave"/"slaves" are now "copy"/"copies".
Backward compatibility should be maintained; you do not need to
change either your gitolite.conf, or any scripts you have
written on top, until you are ready to do so. (This in turn
means the word "slave" will still be present in the code, though
only just as much as needed.)
Should you wish to make this change, you need to migrate to the
latest version (which is also tagged as 3.6.12, so if you want
to wait till the distros pick it up wait for that), and then:
- In the gitolite.conf file, change `option mirror.slaves` to
`option mirror.copies`.
- If you have any scripts that use the `gitolite mirror list
slaves` command, change to `gitolite mirror list copies`.
sitaram
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
with the new "template-data" section, it becomes important to be able to
visually know if you're entering something in the wrong section
(template stuff outside the begin/end markers, or normal stuff inside).
(unfortunately I only know vim; maybe others can help with other
editors' setups?)
|
| |
|
|
|
|
|
|
| |
Signed-off-by: Till Maas <opensource@till.name>
(with minor whitespace changes by sitaramc@gmail.com)
|
| |
|
| |
|
|
|
|
|
|
| |
UKM was never updated for new-style fingerprints at all.
Signed-off-by: Robin H. Johnson <robbat2@gentoo.org>
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
(both thanks to Junio's review)
- detect/discard replayed certs in handling 'git push --signed'
- make the commit message also contain the blob. It's kinda redundant to
have it in both the commit message *and* the individual files, but is
easier to process in terms of checking the entire cert chain.
links to threads:
https://groups.google.com/forum/#!topic/gitolite/7cSrU6JorEY
http://article.gmane.org/gmane.comp.version-control.git/261928
|
| |
|
|
|
|
| |
please see documentation in the code
|
|
|
|
|
| |
(This was started off by someone on irc wanting to backup his repos to s3
using jgit.)
|
| |
|
| |
|
|
|
|
|
|
|
| |
Add sample script for getting group membership from LDAP.
based on ldapsearch.
(committer added author name as comment in case of questions)
|
| |
|
|
committer's notes:
code here, and docs in gitolite-doc repo, fetched from
git://github.com/hemmecke/gitolite
git://github.com/hemmecke/gitolite-doc
respectively.
|