2016-09-08 v3.6.6 simple but important fix for a future perl deprecation
(perl will be removing "." from @INC in 5.24)
'perms' now requires a '-c' to activate batch mode
(should not affect interactive use but check your scripts
perhaps?)
gitolite setup now accepts a '-m' option to supply a
custom message (useful when it is used by a script)
From Harry Waddell in PR 52293.
Changelog:
2016-02-20 v3.6.5 allow creator check to be bypassed during mirroring
handle new style ssh fingerprinting correctly (thanks to
Robin Johnson)
allow pre-auto-gc as a repo-specific hook
optimise mirror pushes for heavily used repos
create-with-reference trigger: on repo creation, setup
objects/info/alternates for a server side alternate object
store.
'mirror status all all' prints a list of repos that have
*some* error, which is arguably more useful for further
action/processing
allow incrementally adding more repo-specific hooks
Changelog:
2015-11-01 v3.6.4 a ref-create bug in wild repos was fixed
some contrib code related to AD integration, and to
redmine user aliases
teach Alias.pm a few new tricks
remove a race condition in 'create' command that affected
the 'default roles' setting
make 'who-pushed' more efficient (local push logs, and
'tip search')
'gitolite query-rc' learns '-d' ('--dump') option
Issues found with existing distfiles:
distfiles/eclipse-sourceBuild-srcIncluded-3.0.1.zip
distfiles/fortran-utils-1.1.tar.gz
distfiles/ivykis-0.39.tar.gz
distfiles/enum-1.11.tar.gz
distfiles/pvs-3.2-libraries.tgz
distfiles/pvs-3.2-linux.tgz
distfiles/pvs-3.2-solaris.tgz
distfiles/pvs-3.2-system.tgz
No changes made to these distinfo files.
Otherwise, existing SHA1 digests verified and found to be the same on
the machine holding the existing distfiles (morden). All existing
SHA1 digests retained for now as an audit trail.
* Use GITHUB framework.
Changelog:
2015-04-26 v3.6.3 allow limited use of 'git config' using the new 'config'
command
accept openssh 6.8's new fingerprint output format
(finally!) allow limited symlinks within ~/repositories;
see commit 8e36230 for details
perms command now lists available roles
minor backward compat breakage: 'perms -l repo' no longer
works; see 'perms -h' for new usage
allow gitolite-shell to be used as $SHELL (experts only;
no support, no docs; see commit 9cd1e37 for details)
help with 'git push --signed' using a post-receive hook to
adopt push certs into 'refs/push-certs'; for details see
contrib/hooks/repo-specific/save-push-signatures
new 'transparent proxy' feature for git repos; see
src/lib/Gitolite/Triggers/TProxy.pm for details
Changelog:
2014-11-10 v3.6.2 disable ../ everywhere (see mailing list thread for
details)
VREF/NAME_NC -- like VREF/NAME but for new commits only.
Details within src/VREF/NAME_NC.
allow gitolite.conf to be tested locally; details within
contrib/utils/gitolite-local
* Improve MESSAGE
Changelog:
2014-06-22 v3.6.1 experimental rc format convertor for "<= 3.3" users who
have already upgraded the *code* to ">= v3.4". Program is
in contrib/utils.
giving shell access to a few users got a lot easier (see
comments in the rc file).
allow logging to syslog as well (see comments in the rc
file)
new 'motd' command
redis caching redone and now in core; see
http://gitolite.com/gitolite/cache.html
2014-05-09 v3.6 (cool stuff) the access command can now help you debug
your rules / understand how a specific access decision was
arrived at.
mirroring: since mirroring is asynchronous (by default
anyway), when a 'git push --mirror' fails, you may not
know it unless you look in the log file on the server.
Now gitolite captures the info and -- if the word 'fatal'
appears anywhere within it, it saves the entire output and
prints it to STDERR for anyone who reads or writes the
repo on the *master* server, until the error condition
clears up.
mirroring: allow 'nosync' slaves -- no attempt to
automatically push to these slaves will be made. Instead,
you have to manually (or via cron, etc) trigger pushes.
(backward compat breakage) the old v2 syntax for
specifying gitweb owner and description is no longer
supported.
macros now allow strings as arguments (thanks to Jason
Donenfeld for the idea/problem).
the 'info' command can print in JSON format if asked to.
repo-specific hooks: now you can specify more than one,
and gitolite runs all of them in sequence.
new trigger 'expand-deny-messages' to show more details
when access is denied.
git-annex support is finally in master, yaaay!
new 'readme' command, modelled after 'desc'. Apparently
gitweb can use a README.html file in the *bare* repo
directory -- who knew!
2013-10-14 v3.5.3 catch undefined groupnames (when possible)
mirroring: async push to slaves
(some portability fixes)
(a couple of contrib scripts - querying IPA based LDAP
servers for group membership, and user key management)
allow groups in subconf files (this *may* slow down
compilation in extreme cases)
make adding repo-specific hooks easier (see cust.mkd or
cust.html online for docs)
smart http now supports git 1.8.2 and above (which changed
the protocol requirements a wee bit)
Do it for all packages that
* mention perl, or
* have a directory name starting with p5-*, or
* depend on a package starting with p5-
like last time, for 5.18, where this didn't lead to complaints.
Let me know if you have any this time.
pax -rw, the destination directory must exist. pax in NetBSD creates it if
not, pax in MirBSD complains. I read through all pkgsrc Makefiles that use
pax and added an entry to INSTALLATION_DIRS, or an INSTALL_DATA_DIR
invocation.
I did not test all the changes but they should be fairly safe. If you notice
any breakage because of this change, please contact me.
Changelog:
2013-07-10 v3.5.2 allow ENV vars to be set from repo options, for use in
triggers and hooks
bug-fix: the new set-default-roles feature was being
invoked on every run of "perms" and overriding it!
Changelog:
2013-03-24 v3.5 (2 minor backward compat breakages)
1. 'DEFAULT_ROLE_PERMS' replaced by per repo
'default.roles' option
2. 'gitolite list-memberships' now requires a '-r' or a
'-u' flag
new 'gitolite owns' command (thanks to Kevin Pulo)
a) refer 'perl' in their Makefile, or
b) have a directory name of p5-*, or
c) have any dependency on any p5-* package
Like last time, where this caused no complaints.
Changelog:
2012-12-29 v3.3 bug fix: gl-perms propagation to slaves broke sometime
after v3.2 (so if you're only picking up tagged releases
you're OK)
the "D" command now allows rm/unlock to be totally
disabled
new trigger: update-gitweb-daemon-from-options; another
way to update gitweb and daemon access lists
new 'create' command for explicit wild repo creation, and
new AutoCreate trigger to control auto-creation
allow simple macros in conf file
2012-11-14 v3.2 major efficiency boost for large setups
optional support for multi-line pubkeys; see
src/triggers/post-compile/ssh-authkeys-split
bug fix for not creating gl-conf when repo para has only
config lines and no access rules
new 'bg' trigger command to put long jobs started from a
trigger into background
%GL_REPO and %GL_CREATOR now work for 'option's also
test suite now much more BSD friendly
2012-10-05 v3.1 (security) fix path traversal on wild repos
new %GL_CREATOR variable for git-config lines
rsync command to create and send bundles automagically
migrated 'who-pushed'
logical expressions on refexes!!!
Gitolite is an SSH-based gatekeeper providing access control for
a server that hosts many git repositories. Without gitolite, each
developer needing to push to one of the repositories hosted would
need a user account on that server; gitolite lets you do that just
using SSH public keys tied to a single, common, user that hosts
all the repositories.
Gitolite can restrict who can read (clone/fetch) from or write
(push) to a repository, and who can push to what branch or tag -
an important issue in corporate environments. Other features include:
* access control by branch-name or by modified file/directory;
* per-developer "personal namespace" prefixes;
* simple but powerful configuration file syntax (with validation);
* config files (and authority for maintaining them) can be split;
* easy integration with gitweb;
* comprehensive logging;
* easy migration from gitosis.
