Package: gitolite3 Version: 3.6.1-3 Severity: important
Hi. I was just going through the documentation of gitolite3, and then had a short glance over the maintainer scripts. It seems our setup right now is the following. The package unpacks and places the actual code files to /usr/somewhere. *If* an adminkey was given, it lookes whether $GITDIR/.gitolite.rc exists and then does the admin PK setup. Now comparing this with: http://gitolite.com/gitolite/install.html Okay obviously we don't need gitolite/install since we do this via the package => so initial installation looks fine. But the upgrade procedure is not really covered by the debian package: Quoting http://gitolite.com/gitolite/install.html#upgrading : > 1) Update your clone of the gitolite source. > 2) Repeat the install command you used earlier (make sure you use the > same arguments as before). > 3) Run gitolite setup. (1) and (2) is again not necessary for us, but we no where run "gitolite setup" when package upgrades are done. I guess this might be necessary for any customisations that upstream wants to do on upgrades. Think especially about the: /var/lib/gitolite3/.gitolite/hooks/common/update /var/lib/gitolite3/.gitolite/hooks/gitolite-admin/post-update These are not symlinks, if anything on them would change, existing installations could never get updated. Cheers, Chris. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
