Thats a pretty old guide... are you sure updating bugs it in would do any good at this point?

The group you need to be in is 'docs-writers'. You can ask on the docs mailing lists, or #fedora-docs on freenode for sponsorship.

Hi Kevin,

I already am a member of docs-writers. I agree that updating an older guide is a bit unusual but it has been requested on the fedora-docs mailing list that attributions for the Russian translation are added to that guide. Also, it remains to be the most-recent published version of that guide.

Cheers,
Martin

ok.

Odd. docs-writers should already be able to commit to that repo.

What error(s) do you get?

Feel free to drop by #fedora-admin on freenode.net for realtime debugging, or add info here.

I get these errors when I try to push:
{{{
master!f13-SELinux_Guide> git svn dcommit
Committing to http://svn.fedorahosted.org/svn/selinuxguide/community/branches/f13 ...
Permission denied: Can't create directory '/svn/selinuxguide/db/transactions/497-1.txn': Permission denied at /usr/libexec/git-core/git-svn line 922
}}}

That repo definitely has docs-writers as being able to write.

Does it do this if you use svn directly instead of svn-git?

I see http://svn.fedorahosted.org/... there... is your gitsvn repo set to use that as it's master?
Shouldn't that be 'ssh://svn.fedorahosted.org...' ?

Hmm, with SVN it fails with:

{{{
WARNING: gnome-keyring:: couldn't connect to: /run/user/mprpic/keyring-24st08/pkcs11: No such file or directory
svn: E000013: Commit failed (details follow):
svn: E000013: Can't create directory '/svn/selinuxguide/db/transactions/497-1.txn': Permission denied
}}}

I am using Xfce btw. Any ideas? Does this operation have anything to do with what's stored in the keyring?

Well, the keyring is likely trying to look for your ssh key...

does 'ssh-add -L' show your fedora key in your agent?

Of course I see the ssh working in logs, so it seems like the key isn't quite the issue. ;(

The permissions are all looking right.

drwxrwsr-x. 2 root docs-writers 4096 Nov 21 2010 /svn/selinuxguide/db/transactions/

I'm at a loss for what could be going wrong here. svnadmin verify completes fine.

Are you able to commit to any other svn repos?

I get:

{{{

ssh-add -L
The agent has no identities.
}}}

And no, I can't commit to any repo. I tried the OpenSSH Guide repo (at http://svn.fedorahosted.org/svn/openssh-guide/community/trunk/):

{{{
master!openssh_guide> git svn dcommit
Committing to http://svn.fedorahosted.org/svn/openssh-guide/community/trunk ...
WARNING: gnome-keyring:: couldn't connect to: /run/user/mprpic/keyring-24st08/pkcs11: No such file or directory
Permission denied: Can't create directory '/svn/openssh-guide/db/transactions/54-1.txn': Permission denied at /usr/libexec/git-core/git-svn line 922
}}}

Odd...

If you:

ssh-add

your fedora ssh key and re-try does it work?

Nope :( I'm at loss here. It must be something with the SSH key. Though, I got rid of the gnome-keyring warning by starting the daemon which initialized the missing pkcs11 component. So at least we know it's not that. Committing to Git repos works just fine btw.

{{{
master!f13-SELinux_Guide> ssh-add ~/.ssh/id_rsa
Enter passphrase for /home/mprpic/.ssh/id_rsa:
Identity added: /home/mprpic/.ssh/id_rsa (/home/mprpic/.ssh/id_rsa)
master!f13-SELinux_Guide> git svn dcommit
Committing to http://svn.fedorahosted.org/svn/selinuxguide/community/branches/f13 ...
Permission denied: Can't create directory '/svn/selinuxguide/db/transactions/497-1.txn': Permission denied at /usr/libexec/git-core/git-svn line 922
}}}

Is the SVN repo SELinux Guide the same as the SELinux Users' Guide in git?

Replying to [comment:12 sparks]:

Is the SVN repo SELinux Guide the same as the SELinux Users' Guide in git?

Yes, but the SVN repo holds the f13 version whereas the new Git repo holds the f17 and onwards versions. Should I port the f13 version into the Git repo?

Yes, we shouldn't have multiple repos for the same document.

Did this get solved? Or is there some action still to take here?

Closing this ticket. I moved the content to the SELinux Guide Git repo.

Thanks for the help!

Martin