On Mon, Dec 26, 2016 at 9:40 AM, Erik Bray <erik.m.b...@gmail.com> wrote: > On Dec 26, 2016 09:28, "Erik Bray" <erik.m.b...@gmail.com> wrote: > > On Dec 25, 2016 19:11, "Dima Pasechnik" <dimp...@gmail.com> wrote: > > > > On Sunday, December 25, 2016 at 12:31:27 PM UTC, Volker Braun wrote: >> >> The ~/.gitolite/logs/ may have some clues about what is going on... > > > no, it doesn't, IMHO. Further, there are two (almost)copies of keystore/, > one in ~/.gitolite/, and the > other in /srv/trac/sage_trac/gitolite-admin/. > The public key in question is in the latter, but not in the former. > I just copied it by hand now, not sure if it has had any effect. > > (I am at loss to describe the design where the same data is stored > in 3 different places... :-)) > > > This I can explain. It has everything to do with how gitolite is designed. > Also this has nothing to do with GCE. I have this documented somewhere but I > don't have the time to look it up right now, but you can also read the > official gitolite documentation. That said, please don't mess around with it > unless you know of what you're doing. > > I don't know why Maxie's key isn't being added and that's unfortunate. It > might be a bug in gitolite. Are other user's ssh keys being added > successfully? > > I might have a moment to look at it later today. > > > Also, if it's true that her key is in /srv/trac/sage_trac/gitolite-admin but > not anywhere else, it could be a problem with the Trac environment. That > path is the local clone of the gitolite-admin repository used by the Trac > plugin to manage the SSH keys. If that got corrupted somehow it could be > failing to push the new key. > > This directory can be safely deleted and recreated by restarting the server.
Nevermind that. Just now I had a look and it was updated fine. It's also in /srv/git/.gitolite/keydir as it should be. So there's a problem with regenerating the authorized_keys list, which could be a problem with gitolite. This has happened before with invalid keys, though IIRC I pushed the change to the plugin a long time ago to make it not accept malformatted keys. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
