Description of problem: I am having problems to update an entry in maintdb - I do not manage to submit a correct password - please help! Note: I have no problem to log in to my account on the Mageia identity mangager https://identity.mageia.org/user My username there is juergen_harms. Do I need a separate password to do mgarepo maintdb set (or get) ... ?
it should be as any other mgarepo command no ?
That is what I had assumed - but when I do, for instance, "mgarepo maintdb get pcb" (yes, even "get") I am asked for a password. When I provide the passsword - the one I use everywhere in Mageia - the question for the password is repeated da capo and etc pp. I just tried it again. On the other hand, I can do a mgarepo submit without being asked for the password (could not check now since I have nothing to submit at present, but did so a couple of weeks back) Looks increasingly like a mistery.
What happens when you try to ssh to maintdb.mageia.org ?
CC: (none) => boklm
Same thing - it does not accept the password and asks again. The thing to do would probably be to change my password in the identity manager and see what happens than (and whether I can do that) - but I am reluctant to upset things which presently work, prefer to verify first whether there is some other explanation. My ssh should be correctly set up (a) I have no problems doing mgarepo submit and (b) my present failure is on an mga3 system, but the same thing happens when I log in from a mageia2 partition (where I am pretty sure that I had successfully set my maintainership a couple of months back).
If ssh is correctly set up, then it shouldn't ask a password to connect to maintdb.mageia.org. If your local user name is different from your mageia user name, then you maybe need to edit your ssh configuration file to set your default user name for maintdb.mageia.org.
Hello, Is the problem still present or can we close this bug ?
Sorry for not closing the bug - not a bug, but a user problem: your reply was perfectly right, my names are different and that was easy to fix.
Closing
Status: NEW => RESOLVEDResolution: (none) => INVALID
CC: boklm => (none)