Ritesh Raj Sarraf writes:
> For whatever be the reason, gitolite3 expects its $HOME path to be executable.
> Whereas typical non-root file systems on Linux are treated as data partitions
> and their mount options usually are set to not allow execution, suid and other
> stuff.
Typical or no, I've
On Sat, 2015-06-27 at 13:36 +0200, David Bremner wrote:
> The latest upload to experimental (3.6.3-2) won't ask for GITDIR on
> reconfiguration (assuming configuration completed once). Although I
> don't claim this is a fix for the bug you reported, I think it does
> convert it into a feature reque
Ritesh Raj Sarraf writes:
>
> Actually, I think this bug's severity should be raised.
>
> Irrespective of whether it migrated the settings or not, it should
> still, for newer repositories, create the repo in the new locaiton.
>
> Because, by setting up the new path, it gives that impression. Toda
On Wednesday 15 April 2015 04:19 AM, David Bremner wrote:
> I'm not sure. Your "fresh install case" seems like about the only one
> where moving one without the other makes sense. In any case, maybe
> somebody finds the upstream docs at
>
> http://gitolite.com/gitolite/gitolite.html#movi
Ritesh Raj Sarraf writes:
> When installing default, g3 will set gitdir to /var/lib/gitolite3.
> If I use dpkg-reconfigure to configure its gitdir to a different location,
> apart from just creating the dir, nothing else gets migrated.
>
> For repositories, it may be okay. But for configuration
Package: gitolite3
Version: 3.6.1-2
Severity: normal
When installing default, g3 will set gitdir to /var/lib/gitolite3.
If I use dpkg-reconfigure to configure its gitdir to a different location,
apart from just creating the dir, nothing else gets migrated.
For repositories, it may be okay. But f
6 matches
Mail list logo
