I thought I had fixed that. There is a umask in the gitolote.RC that should cover it. And
a setgid on the log dir.
"Mike McGrath" <mmcgrath(a)redhat.com> wrote:
On Sat, 31 Jul 2010, Mike McGrath wrote:
> On Sat, 31 Jul 2010, Orion Poplawski wrote:
>
> > Trying to check out vtk (or other packages):
> >
> > $ fedpkg co vtk
> > Cloning into vtk...
> > Warning: No xauth data; using fake authentication data for X11 forwarding.
> > open log failed: Permission denied
> > fatal: The remote end hung up unexpectedly
> > Could not clone: Command '['git', 'clone',
> > 'ssh://orion@pkgs.fedoraproject.org/vtk']' returned non-zero exit
status 128
> >
> > I was able to do this earlier today fine with other packages and have
> > the latest fedora-package for F13.
> >
>
> Looking now, I can't even get a shell anymore remotely. Console time.
>
"fixed".. looking for a permanent fix now. Basically the logs got
rotated, dmaphy was the first one in and the default umask was too
restrictive for anyone else to write to the logs.
-Mike
--
devel mailing list
devel(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
--
Sent from my Android phone with K-9 Mail. Please excuse my brevity.