Re: committing gthumb-3-6 ui+help failed
Op 07-07-18 om 18:07 schreef Abderrahim Kitouni: If this is working, I suggest you push using https. Just use git clone https://gitlab.gnome.org/GNOME/gthumb.git Hello Abderrahim, This method of yours works, I have pushed gthumb-3-6 now. Many thanks to you and Rafael for your help. Hannie ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: committing gthumb-3-6 ui+help failed
Hi Hannie, Le sam. 7 juil. 2018 à 10:01, Hannie Dumoleyn a écrit : > This "other account" could be the account I have on git.gnome > (account.gnome.org). But since this account was imported in gitlab, I do > not understand why it worked on git.gnome.org, but not on > gitlab.gnome.org. I can download gthumb with command git clone > git://git.gnome.org/gthumb, but not with git clone > g...@gitlab.gnome.org:GNOME/gthumb.git (Permission denied). > In the first case you're using the anonymous git:// protocol, so it didn't use your account at all. In the second you're using ssh, and your key isn't recognised. On https://gitlab.gnome.org/users/sign_in I can only sign in using the LDAP tab. When I go to Standard I cannot sign in (not with my git.gnome > or gitlab.gnome account user name and password). > If this is working, I suggest you push using https. Just use git clone https://gitlab.gnome.org/GNOME/gthumb.git And when pushing, you'll be asked for your username and password. It may be annoying that you have to enter your password every time you push, but if you aren't pushing often, it shouldn't be a problem. Both commands 'ssh -v myn...@git.gnome.org' and 'ssh -v myn...@gitlab.gnome.org' give me terminal output Permission > denied. When pushing with ssh, everybody pushes as the git user, you don't need your username. One of the reasons may be that my user name is different on git, > gitlab and in my public key. Changing my user name in my gitlab User > Settings is a risky business, so I will not try as yet. Changing my user > name on my PC (git config --global user.name "newname") might be an > option, but perhaps you can come up with a better solution? > The user.name config should be set to your full name, it doesn't affect authentication at all. HTH, Abderrahim ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: committing gthumb-3-6 ui+help failed
Op 06-07-18 om 13:59 schreef Rafael Fontenelle: Hi Hannie, Em sex, 6 de jul de 2018 às 07:38, Hannie Dumoleyn escreveu: Hi Rafael, Thank you for sending me the jpg of your "User settings". Yes, I found this ssh key icon now and there I see that my SSH key was imported from acount.gnome.org. Unfortunately, it does not work. When I add my public key here, I get the message: Fingerprint has already been taken. Perhaps I have to create a new ssh key. I will try later and let you know if that helps. Best regards, Hannie "Fingerprint has already been taken" means another account has your SSH keys. Could you have already created a Standard account and added SSH keys to it? If yes, logging in as Standard account and removing your keys from Standard account would solve this issue. Best regards, Rafael Fontenelle Hello Rafael, This "other account" could be the account I have on git.gnome (account.gnome.org). But since this account was imported in gitlab, I do not understand why it worked on git.gnome.org, but not on gitlab.gnome.org. I can download gthumb with command git clone git://git.gnome.org/gthumb, but not with git clone g...@gitlab.gnome.org:GNOME/gthumb.git (Permission denied). On https://gitlab.gnome.org/users/sign_in I can only sign in using the LDAP tab. When I go to Standard I cannot sign in (not with my git.gnome or gitlab.gnome account user name and password). So, yes, there is something wrong, but there may be a hundred reasons for this Permission denied. Both commands 'ssh -v myn...@git.gnome.org' and 'ssh -v myn...@gitlab.gnome.org' give me terminal output Permission denied. One of the reasons may be that my user name is different on git, gitlab and in my public key. Changing my user name in my gitlab User Settings is a risky business, so I will not try as yet. Changing my user name on my PC (git config --global user.name "newname") might be an option, but perhaps you can come up with a better solution? Many thanks in advance for your help. You deserve a gold medal for that. btw, thanks for giving further information on msgfmt, I had not noticed they used Notepad++. Hannie ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: committing gthumb-3-6 ui+help failed
Hi Hannie, Em sex, 6 de jul de 2018 às 07:38, Hannie Dumoleyn escreveu: > > Hi Rafael, > > Thank you for sending me the jpg of your "User settings". Yes, I found > this ssh key icon now and there I see that my SSH key was imported from > acount.gnome.org. Unfortunately, it does not work. When I add my public > key here, I get the message: Fingerprint has already been taken. > Perhaps I have to create a new ssh key. I will try later and let you > know if that helps. > > Best regards, > > Hannie > "Fingerprint has already been taken" means another account has your SSH keys. Could you have already created a Standard account and added SSH keys to it? If yes, logging in as Standard account and removing your keys from Standard account would solve this issue. Best regards, Rafael Fontenelle ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: committing gthumb-3-6 ui+help failed
Op 05-07-18 om 18:26 schreef Rafael Fontenelle: See the attached picture for how it is for my account -- you should see the same, I assume. Rafael Fontenelle Hi Rafael, Thank you for sending me the jpg of your "User settings". Yes, I found this ssh key icon now and there I see that my SSH key was imported from acount.gnome.org. Unfortunately, it does not work. When I add my public key here, I get the message: Fingerprint has already been taken. Perhaps I have to create a new ssh key. I will try later and let you know if that helps. Best regards, Hannie ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: committing gthumb-3-6 ui+help failed
Em qui, 5 de jul de 2018 às 13:19, Hannie Dumoleyn escreveu: > > Ha, here we get to the core. I signed in with ldap name/password on > gitlab.gnome.org. I opened my profile, so far so good ;) But on > https://gitlab.gnome.org/myname, or in User Settings, I cannot find an > option where I can add my public ssh key. > https://docs.gitlab.com/ee/ssh/README.html#ssh does not give me the answer. > So, help needed again ;) > Hannie I notice I mentioned "Profile", but the correct is "User Settings". So the correct instruction is to click in your picture to expand a menu, select "Settings" (for User Settings) and finally "SSH keys" in the left sidebar menu. See the attached picture for how it is for my account -- you should see the same, I assume. Rafael Fontenelle ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: committing gthumb-3-6 ui+help failed
Op 05-07-18 om 17:42 schreef Rafael Fontenelle: Hannie, Did you successfully logged into GNOME's Gitlab using your LDAP (not Standard) account at least one time? If yes, did you add your SSH public keys to your profile? (In Gitlab web interface, click in your picture, enter in your Profile -> SSH Keys). Rafael Fontenelle Ha, here we get to the core. I signed in with ldap name/password on gitlab.gnome.org. I opened my profile, so far so good ;) But on https://gitlab.gnome.org/myname, or in User Settings, I cannot find an option where I can add my public ssh key. https://docs.gitlab.com/ee/ssh/README.html#ssh does not give me the answer. So, help needed again ;) Hannie ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: committing gthumb-3-6 ui+help failed
Hannie, Did you successfully logged into GNOME's Gitlab using your LDAP (not Standard) account at least one time? If yes, did you add your SSH public keys to your profile? (In Gitlab web interface, click in your picture, enter in your Profile -> SSH Keys). Rafael Fontenelle Em qui, 5 de jul de 2018 às 12:36, Hannie Dumoleyn escreveu: > > Op 05-07-18 om 15:46 schreef Rafael Fontenelle: > > Hello Hannie, > > > > Em qui, 5 de jul de 2018 às 04:04, Hannie Dumoleyn > > escreveu: > >> Hello Rafael, > >> > >> Thanks for your answer. When I try this command of yours I get the > >> following error message: > >> fatal: No such remote 'origin' > >> > >> When I remove 'origin' I get this: > >> usage: git remote set-url [--push] [] > >> or: git remote set-url --add > >> or: git remote set-url --delete > >> > >> --pushmanipulate push URLs > >> --add add URL > >> --delete delete URLs > >> > > Maybe you have an older Git version? Try adding the "--add" flag like this: > > > > $ git remote set-url --add origin g...@gitlab.gnome.org:GNOME/gthumb.git > > > > Alternatively, you can remove the whole Git checkout directory and run > > git-clone again, now using gitlab.gnome.org as source URL, instead of > > the old git.gnome.org > > > >> I cannot use Damned Lies because I get the following message: An error > >> occurred during applying your action: The commit failed. The error was: > >> “Sorry, adding new translations for documentation is not yet supported.” > > Yep. D-L currently does not support adding new translation file for > > documentation. It is still required to send the first one via Git > > commands and the further updates can be done via D-L web interface. > > > > Best regards, > > Rafael Fontenelle > > > Hi Rafael, > > I still need a helping hand. I was used to working with git.gnome, but > gitlab is another story. > I did this: ~$ git clone g...@gitlab.gnome.org:GNOME/gthumb.git > Terminal answer is this: The authenticity of host 'gitlab.gnome.org > (209.132.180.181)' can't be established. > Are you sure you want to continue connecting (yes/no)? yes > Permanently added 'gitlab.gnome.org,209.132.180.181' (ECDSA) to the list > of known hosts. > sign_and_send_pubkey: signing failed: agent refused operation > g...@gitlab.gnome.org: Permission denied > (publickey,gssapi-keyex,gssapi-with-mic). > fatal: Could not read from remote repository. > > I had expected to be asked to login with my gitlab ldap name and > password, as was the case with git.gnome. Should I get a new ssh key? > The current one works with git.gnome, where I can still download, but > not push, gthumb. > > Thanks for your help, it is much appreciated. > > Hannie > ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: committing gthumb-3-6 ui+help failed
Op 05-07-18 om 15:46 schreef Rafael Fontenelle: Hello Hannie, Em qui, 5 de jul de 2018 às 04:04, Hannie Dumoleyn escreveu: Hello Rafael, Thanks for your answer. When I try this command of yours I get the following error message: fatal: No such remote 'origin' When I remove 'origin' I get this: usage: git remote set-url [--push] [] or: git remote set-url --add or: git remote set-url --delete --pushmanipulate push URLs --add add URL --delete delete URLs Maybe you have an older Git version? Try adding the "--add" flag like this: $ git remote set-url --add origin g...@gitlab.gnome.org:GNOME/gthumb.git Alternatively, you can remove the whole Git checkout directory and run git-clone again, now using gitlab.gnome.org as source URL, instead of the old git.gnome.org I cannot use Damned Lies because I get the following message: An error occurred during applying your action: The commit failed. The error was: “Sorry, adding new translations for documentation is not yet supported.” Yep. D-L currently does not support adding new translation file for documentation. It is still required to send the first one via Git commands and the further updates can be done via D-L web interface. Best regards, Rafael Fontenelle Hi Rafael, I still need a helping hand. I was used to working with git.gnome, but gitlab is another story. I did this: ~$ git clone g...@gitlab.gnome.org:GNOME/gthumb.git Terminal answer is this: The authenticity of host 'gitlab.gnome.org (209.132.180.181)' can't be established. Are you sure you want to continue connecting (yes/no)? yes Permanently added 'gitlab.gnome.org,209.132.180.181' (ECDSA) to the list of known hosts. sign_and_send_pubkey: signing failed: agent refused operation g...@gitlab.gnome.org: Permission denied (publickey,gssapi-keyex,gssapi-with-mic). fatal: Could not read from remote repository. I had expected to be asked to login with my gitlab ldap name and password, as was the case with git.gnome. Should I get a new ssh key? The current one works with git.gnome, where I can still download, but not push, gthumb. Thanks for your help, it is much appreciated. Hannie ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: committing gthumb-3-6 ui+help failed
Hello Hannie, Em qui, 5 de jul de 2018 às 04:04, Hannie Dumoleyn escreveu: > > Hello Rafael, > > Thanks for your answer. When I try this command of yours I get the > following error message: > fatal: No such remote 'origin' > > When I remove 'origin' I get this: > usage: git remote set-url [--push] [] > or: git remote set-url --add > or: git remote set-url --delete > > --pushmanipulate push URLs > --add add URL > --delete delete URLs > Maybe you have an older Git version? Try adding the "--add" flag like this: $ git remote set-url --add origin g...@gitlab.gnome.org:GNOME/gthumb.git Alternatively, you can remove the whole Git checkout directory and run git-clone again, now using gitlab.gnome.org as source URL, instead of the old git.gnome.org > I cannot use Damned Lies because I get the following message: An error > occurred during applying your action: The commit failed. The error was: > “Sorry, adding new translations for documentation is not yet supported.” Yep. D-L currently does not support adding new translation file for documentation. It is still required to send the first one via Git commands and the further updates can be done via D-L web interface. Best regards, Rafael Fontenelle ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: committing gthumb-3-6 ui+help failed
Op 02-07-18 om 19:06 schreef Rafael Fontenelle: Hello Hannie, Em seg, 2 de jul de 2018 às 13:51, Hannie Dumoleyn escreveu: Hello, Following instructions on [1], I did the following: 1. git clone git://git.gnome.org/gthumb git.gnome.org is no more. You should use gitlab.gnome.org as source code repository now. In order to fix your remote origin, run $ git remote set-url origin g...@gitlab.gnome.org:GNOME/gthumb.git and then you should be able to commit. Best regards, Rafael Fontenelle Hello Rafael, Thanks for your answer. When I try this command of yours I get the following error message: fatal: No such remote 'origin' When I remove 'origin' I get this: usage: git remote set-url [--push] [] or: git remote set-url --add or: git remote set-url --delete --push manipulate push URLs --add add URL --delete delete URLs I cannot use Damned Lies because I get the following message: An error occurred during applying your action: The commit failed. The error was: “Sorry, adding new translations for documentation is not yet supported.” I have added /help/nl folder to gthumb on my pc but I cannot send it to gitlab. Hannie ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: committing gthumb-3-6 ui+help failed
Hello Hannie, Em seg, 2 de jul de 2018 às 13:51, Hannie Dumoleyn escreveu: > > Hello, > > Following instructions on [1], I did the following: > 1. git clone git://git.gnome.org/gthumb git.gnome.org is no more. You should use gitlab.gnome.org as source code repository now. In order to fix your remote origin, run $ git remote set-url origin g...@gitlab.gnome.org:GNOME/gthumb.git and then you should be able to commit. Best regards, Rafael Fontenelle ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
