Bug 5269

(In reply to comment #0)
> It would be nice if those who can generate the help files for installer in
> Calenco, could also commit them to SVN.
> 
> We'd like to have commit rights for JohnR (John Rye) and marja (Marja van Waes)

And "We" is of course documentation team

CC: (none) => doc-bugs

Pleas add simonnzg (Simon Parsons), too, he also has publication rights in Calenco, so he can generate the help files, too :)

Summary: SVN commit rights for JohnR and marja => SVN commit rights for JohnR, simonnzg and marja

Hello,

Do you know where the documentation needs to be commited on svn ? Do we need to create a new svn repository for doc, or should it be commited somewhere on an existing repository ?

CC: (none) => boklm

(In reply to comment #3)
> Hello,
> 
> Do you know where the documentation needs to be commited on svn ? Do we need to
> create a new svn repository for doc, or should it be commited somewhere on an
> existing repository ?

Sorry for not understanding your question, I'll cc obgr_seneca and trust he'll give the correct answer.

The installer help texts are already in svn and only need to be improved (we haven't finished all of them, they still need to be corrected and other languages need to be added)

http://svnweb.mageia.org/packages/cauldron/drakx-installer-help/

When they are finished, we'll probably first start working on help for the drakxtools and when that is finished on a Mageia manual

CC: (none) => oliver.bgr

Hi Nicolas,

Thx to Manuel and Kamil I do understand your question now.

For help files for existing packages, it doesn't feel good to have them in http://svnweb.mageia.org/doc/ 
I think it is better to keep them close to the packages they are referring to.

They should go in the packager's repository.

And when we're used to committing there, we might as well commit the texts for the Mageia Manual there, too.

The mga-doc group has been created in ldap with marja and simonnzg as members. Can you tell me what is JohnR user name in ldap to add him to the group ?

Users from this group should now be allowed to upload their ssh key on https://identity.mageia.org/ (on sshPublicKey attribute). And commit to the svn.

>>Can you tell me what is JohnR user name in ldap to add him to the group ?

johnrnz

(In reply to comment #7)
> >>Can you tell me what is JohnR user name in ldap to add him to the group ?
> 
> johnrnz

Ok, you have been added to the mga-doc group.

Status: NEW => RESOLVED
Resolution: (none) => FIXED

Please add papoteur and lebarhon to the mageia-doc ldap group.

I'm the only docteam member who sometimes (not often enough) gets around to committing translated or updated installer help files, it would be great if they could help.

Status: RESOLVED => REOPENED
CC: (none) => lebarhon, yves.brungard_mageia
Resolution: FIXED => (none)
Summary: SVN commit rights for JohnR, simonnzg and marja => SVN commit rights for docteam

Hello,

papoteur and lebarhon have been added to the mga-doc ldap group.

See this page for ssh configuration to access the svn :
https://wiki.mageia.org/en/Packagers_ssh

Status: REOPENED => RESOLVED
Resolution: (none) => FIXED

(In reply to Nicolas Vigier from comment #10)
> Hello,
> 
> papoteur and lebarhon have been added to the mga-doc ldap group.
> 
> See this page for ssh configuration to access the svn :
> https://wiki.mageia.org/en/Packagers_ssh

Perfect!

Thanks Nicolas, and thx for the link, too :-)

(In reply to Marja van Waes from comment #11)
> (In reply to Nicolas Vigier from comment #10)
> > Hello,
> > 
> > papoteur and lebarhon have been added to the mga-doc ldap group.
> > 
> > See this page for ssh configuration to access the svn :
> > https://wiki.mageia.org/en/Packagers_ssh
> 
> Perfect!
> 
> Thanks Nicolas, and thx for the link, too :-)

In tonight's docteam meeting, lebarhon told that it still doesn't work for neither him, nor papoteur.

@ Yves & André

can you please paste any error message you get

Status: RESOLVED => REOPENED
CC: gm4nzg, john, oliver.bgr => (none)
Resolution: FIXED => (none)

lebarhon et moi avons essayé de nous connecter, mais sans succès.
Nous avons suivi le wiki, en créant une clé.
J'ai chargé l'élément que je considère comme étant la clé dans le fichier id_rsa.pub (la suite de lettre et chiffres) sur identity, puis tenté la connexion.
J'ai une demande de mot de passe qui revient toujours.
Qu'a-t-on loupé ?
Papoteur

(In reply to papoteur from comment #13)
> lebarhon et moi avons essayé de nous connecter, mais sans succès.
> Nous avons suivi le wiki, en créant une clé.
> J'ai chargé l'élément que je considère comme étant la clé dans le fichier
> id_rsa.pub (la suite de lettre et chiffres) sur identity, puis tenté la
> connexion.
> J'ai une demande de mot de passe qui revient toujours.
> Qu'a-t-on loupé ?
> Papoteur

When you generated the key, did you choose to have a password?
Is it that password that you enter over and over again?

it is probably easier for one of the sysadmins to investigate what goes wrong if you both attach your 
~/.ssh/id_rsa.pub

sorry for not having asked before

hello,
In this wiki page : https://wiki.mageia.org/en/Packagers_ssh
there is a test that ask to enter a command. If the password (the pass-phrase in fact) is asked again and again, that means something is wrong. It is my case.
[samageia@localhost ~]$ svn ls svn+ssh://svn.mageia.org/svn/packages
Password: 
Password: 
....
Ctrl C
svn: E210002: Unable to connect to a repository at URL 'svn+ssh://svn.mageia.org/svn/packages'

$ cat ~/.ssh/id_rsa.pub
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDRkfPZDGok+4RmNi7ktfp+QS3i0dmrtUkVmftygzjAA/hEs26Q/m1YyNEUq3D0q5CqFoo1RdaH2f5Vg+YfnCbr9gn3rE/H/xs3e5v/l4jj5TJvt8vsrRpwEoaTMkZiajcMfNBbAY+GMY8KqlJxx94Tfi05Y89gqpqEbwcoRQdXNKskA5uBdmhoHZ0FDyt8P79tbfFgY4vF7n6KYuwgULOo1ElNC3ZBYWXMFmUalxcy07Kr4HRxuc2XO/2al357GUvFTI5WDCa3KYSAArIPY7txg8Oqix1LcemukRIcQR05eoOY+v5jdO91N/oMkWdg1U615pOgl4ZLA25uux7Qf1S5 samageia@localhost.localdomain

(In reply to André DESMOTTES from comment #16)
> If the password (the
> pass-phrase in fact) is asked again and again, that means something is
> wrong. It is my case.
> [samageia@localhost ~]$ svn ls svn+ssh://svn.mageia.org/svn/packages
> Password: 
> Password: 
> ....
> Ctrl C
> svn: E210002: Unable to connect to a repository at URL
> 'svn+ssh://svn.mageia.org/svn/packages'
> 

Sorry, you're not a packager or padawan and don't have access to svn/packages

Can you please try whether you get the same error with svn/soft ?

For instance:

svn co svn+ssh://svn.mageia.org/svn/soft/drakx-installer-help

Same error with your example. :(

(In reply to André DESMOTTES from comment #18)
> Same error with your example. :(

I've run out of ideas... I hope one of the sysadmins has a suggestion

It may be to do with your username being different on your personal computer than it is on svn.

You can work around that by adding a config file in your .ssh directory

$ cat /home/thisun/.ssh/config 
Host svn.mageia.org
IdentityFile /home/thisun/.ssh/magid
Hostname svn.mageia.org
User claire
Compression yes
CompressionLevel 9
ServerAliveInterval 120
ForwardX11 no
ForwardAgent yes

Host *
ForwardX11 yes
ForwardAgent yes

CC: (none) => eeeemail

Here is my /.ssh/config

[samageia@localhost ~]$ cat ~/.ssh/config
Host svn.mageia.org
      ForwardAgent yes
      User lebarhon
Host binrepo.mageia.org svn.mageia.org
      User lebarhon
      IdentityFile ~/.ssh/id_rsa

You can see here that you have been aded on svn: 
http://people.mageia.org/g/mga-doc.html

The problem must lie with the config. My guess is that you need IdentityFile in the svn section and to remove svn from the binrepo section. Or just reduce it to one section for mageia.org.

(In reply to claire robinson from comment #20)
> It may be to do with your username being different on your personal computer
> than it is on svn.
> 

I'm trying to understand this.

When I do 
marja [ ~ ]$ ssh xi@rpabc
Enter passphrase for key '/home/marja/.ssh/id_rsa':
Linux rpabc 3.6.11+ #371 PREEMPT Thu Feb 7 16:31:35 GMT 2013 armv6l
<snip>
Last login: Wed Jul 24 10:05:10 2013 from lenovoz.fritz.box
xi@rpabc ~ $

so just having my public key added to 
/home/xi/.ssh/authorized_keys
of "rpabc" was enough to make it work

I do *not* have a ./ssh/config

marja [ ~ ]$ ls -al ./.ssh/
total 44
drwx------  2 marja marja  4096 Mar 12 11:58 ./
drwx------ 98 marja marja 12288 Jul 24 10:32 ../
-rwx------  1 marja marja    50 Dec  2  2012 .directory*
-rwx------  1 marja marja  1766 May 25  2012 id_rsa*
-rwx------  1 marja marja   387 May 26  2012 id_rsa.pub*
-rwx------  1 marja marja   397 May 26  2012 id_rsa.pub~*
-rwx------  1 marja marja  6142 May 20 11:58 known_hosts*
-rwx------  1 marja marja  3551 Mar 12 11:58 known_hosts~*
marja [ ~ ]$

@boklm:

theese accuonts (papoteur and lebarhon) are "broken" on valstar...

either something went wrong during account promotion to posix, 
or maybe something broke with the changes for gitolite ...

theese 2 has not got any /home/* (or the old /var/lib/pubkeys/*)

that would store their public ssh keys...

hm..., not to mention I dont see their public ssh keys in identity either...

@papoteur and lebarhon:

Have you added your public ssh keys on identity ?

(choose: "Add attribute sshPublicKey with value:", paste in your key and push "Add")

CC: (none) => tmb

(In reply to André DESMOTTES from comment #21)
> Here is my /.ssh/config
> 
> [samageia@localhost ~]$ cat ~/.ssh/config
> Host svn.mageia.org
>       ForwardAgent yes
>       User lebarhon
> Host binrepo.mageia.org svn.mageia.org
>       User lebarhon
>       IdentityFile ~/.ssh/id_rsa

Hello, here when you will connect to mageia, you will use ~/.ssh/id_rsa 
ida_rsa is your *private* key, so you do not paste it here :p or change it to be secure.
In your case, my advice will be to reconfigurate your .ssh/config file, like :

Host svn.mageia.org
       IdentityFile ~/.ssh/id_rsa
       ForwardAgent yes
       User lebarhon
Host binrepo.mageia.org
       User lebarhon
       IdentityFile ~/.ssh/id_rsa

Don't forget to publish on the megeia ssh configuration on the mageia server the public key.

CC: (none) => benoit.tuduri

(In reply to Marja van Waes from comment #23)
> (In reply to claire robinson from comment #20)
> > It may be to do with your username being different on your personal computer
> > than it is on svn.
> > 
> 
> I'm trying to understand this.
> 
> When I do 
> marja [ ~ ]$ ssh xi@rpabc
> Enter passphrase for key '/home/marja/.ssh/id_rsa':
> Linux rpabc 3.6.11+ #371 PREEMPT Thu Feb 7 16:31:35 GMT 2013 armv6l
> <snip>
> Last login: Wed Jul 24 10:05:10 2013 from lenovoz.fritz.box
> xi@rpabc ~ $
> 
> so just having my public key added to 
> /home/xi/.ssh/authorized_keys
> of "rpabc" was enough to make it work
> 
> I do *not* have a ./ssh/config
> 
> marja [ ~ ]$ ls -al ./.ssh/
> total 44
> drwx------  2 marja marja  4096 Mar 12 11:58 ./
> drwx------ 98 marja marja 12288 Jul 24 10:32 ../
> -rwx------  1 marja marja    50 Dec  2  2012 .directory*
> -rwx------  1 marja marja  1766 May 25  2012 id_rsa*
> -rwx------  1 marja marja   387 May 26  2012 id_rsa.pub*
> -rwx------  1 marja marja   397 May 26  2012 id_rsa.pub~*
> -rwx------  1 marja marja  6142 May 20 11:58 known_hosts*
> -rwx------  1 marja marja  3551 Mar 12 11:58 known_hosts~*
> marja [ ~ ]$

Hello Marja,

The config file which located in ~/.ssh are not created by default.
It's useful if only if you wanna have a multiple keys ssh for a or many servers authentication.
In the claire's config example, she customizes her connection parameters on the mageia server to improve the latency time with some compression level etc etc.
Another case will be to would like have n ssh key for n mageia server authentication : a key for your doc team connection, another for the mageia packages upload, another for anything.

I do not if i answer your question.

(In reply to Thomas Backlund from comment #24)
> @boklm:
> 
> theese accuonts (papoteur and lebarhon) are "broken" on valstar...
> 
> either something went wrong during account promotion to posix, 
> or maybe something broke with the changes for gitolite ...
> 
> theese 2 has not got any /home/* (or the old /var/lib/pubkeys/*)
> 
> that would store their public ssh keys...
> 
> hm..., not to mention I dont see their public ssh keys in identity either...

It's not broken. If there is no ssh key in ldap, then it's normal that no home dir is created.

So the problem seems to be that there is no ssh key in ldap.

Hello,
I'm sure to have already loaded the public key in mageia identity two monthes ago.
I just loaded it again, but I'm always asked for a password.
Papoteur.

After checking on ldap, the key is still not added.

How did you add the key ? Did you have an error when adding the key and can you see it on identity ?

(In reply to benoît tuduri from comment #26)

> I do not if i answer your question.

Thx for trying to help :)

Well, *if* having a different username on your workstation than on our svn can cause problems getting ssh access to it, too, then I still don't understand why that is.

However, it seems the missing public ssh keys from paporeur and lebarhon in ldap are the (first) problem here.

(In reply to Marja van Waes from comment #30)
> 
> Well, *if* having a different username on your workstation than on our svn
> can cause problems getting ssh access to it, too, then I still don't
> understand why that is.

Because svn uses ssh, which uses the local username to connect, unless a different one is specified in the ssh configuration, or in the URL.

(In reply to Nicolas Vigier from comment #31)

> Because svn uses ssh, which uses the local username to connect, unless a
> different one is specified in the ssh configuration, or in the URL.

Thanks for explaining, Nicolas.
(I had the totally wrong idea that with svn+ssh we all log in as the same temporary user, after which subversion decides, depending on which public key matches your private one, who you really are and which access rights you have.)

(In reply to benoît tuduri from comment #25)
> (In reply to André DESMOTTES from comment #21)
> > Here is my /.ssh/config
> > 
> > [samageia@localhost ~]$ cat ~/.ssh/config
> > Host svn.mageia.org
> >       ForwardAgent yes
> >       User lebarhon
> > Host binrepo.mageia.org svn.mageia.org
> >       User lebarhon
> >       IdentityFile ~/.ssh/id_rsa
> 
> Hello, here when you will connect to mageia, you will use ~/.ssh/id_rsa 
> ida_rsa is your *private* key, so you do not paste it here :p or change it
> to be secure.
> In your case, my advice will be to reconfigurate your .ssh/config file, like
> :
> 
> Host svn.mageia.org
>        IdentityFile ~/.ssh/id_rsa
>        ForwardAgent yes
>        User lebarhon
> Host binrepo.mageia.org
>        User lebarhon
>        IdentityFile ~/.ssh/id_rsa
> 
> Don't forget to publish on the megeia ssh configuration on the mageia server
> the public key.

Done, and something changed :)

[samageia@localhost ~]$ ssh lebarhon@svn.mageia.org
X11 forwarding request failed on channel 0
Last login: Wed Jul 24 19:24:02 2013 from lns-bzn-26-82-254-81-205.adsl.proxad.net
You tried to run a interactive shell.
Sorry, you are not allowed to execute that command.
You are member of the following groups :
mga-users mga-shell_access mga-i18n mga-doc
Connection to svn.mageia.org closed.
[samageia@localhost ~]$

[samageia@localhost ~]$ svn co svn+ssh://svn.mageia.org/svn/soft/drakx-installer-help
Révision 8654 extraite.
[samageia@localhost ~]$

For my own side, I tried to create the same ~/ssh/config file as Lebarhon, with my nickname, but without success:
svn co svn+ssh://svn.mageia.org/svn/soft/drakx-installer-help
or 
ssh papoteur@svn.mageia.org
ask for password
:(
I have also tried to restart sshd service.

(In reply to papoteur from comment #34)

> ssh papoteur@svn.mageia.org
> ask for password


Do you get some output like this (but with s/test/papoteur/ and a different ip address):

marja [ ~ ]$ ssh test@svn.mageia.org
Password:
Password:
Password:
test@svn.mageia.org's password:
Permission denied, please try again.
test@svn.mageia.org's password:
Received disconnect from 2a02:2178:2:7::3: 2: Too many authentication failures for test
marja [ ~ ]$

Or do you see a different message? Please paste.

@ papoteur

Does it work for you, too, now, so that this bug report can be closed?

Yes it works for me

(In reply to papoteur from comment #37)
> Yes it works for me

Closing as fixed, then. I understood from comment 33 that it already worked for lebarhon :-)

Status: REOPENED => RESOLVED
Resolution: (none) => FIXED

Unfortunately it doesn't work! I have no more the ask for the passphrase, but something else:

[samageia@localhost ~]$ ssh lebarhon@svn.mageia.org
ssh_exchange_identification: Connection closed by remote host

[samageia@localhost ~]$ svn co svn+ssh://svn.mageia.org/svn/soft/drakx-installer-help
svn: E210002: Unable to connect to a repository at URL 'svn+ssh://svn.mageia.org/svn/soft/drakx-installer-help'
svn: E210002: Pour mieux déboguer les problèmes de connexion SSH, retirer l'option -q de 'ssh' dans la section [tunnels] de votre fichier de configuration de Subversion.
svn: E210002: La connexion réseau a été fermée de façon inattendue
[samageia@localhost ~]$ 

Note: I changed my passphrae about half an hour before doing the tests.

(In reply to André DESMOTTES from comment #39)
> Unfortunately it doesn't work! I have no more the ask for the passphrase,
> but something else:
> 
> [samageia@localhost ~]$ ssh lebarhon@svn.mageia.org
> ssh_exchange_identification: Connection closed by remote host



> 
> Note: I changed my passphrae about half an hour before doing the tests.

Do you mean your public key in identity? IIRC, it can take more than half an hour after that, but shouldn't take until tomorrow.

Next time you could try "ssh -v lebarhon@svn.mageia.org" (or even more verbose with -vv. -vvv is most verbose)

Status: RESOLVED => REOPENED
Resolution: FIXED => (none)

Closing again, because it has worked for lebarhon, and it no longer working is a different issue and should thus go into a different bug report.

bug 16119 has now been filed for the new issue

Status: REOPENED => RESOLVED
Resolution: (none) => FIXED