Re: github cloning from cmdline

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Jeffery,

Thanks for the reply. In my test, I don't configure a
   $HOME/.gitconfig file, and your <project>/.git/config file.

The weird thing, i'm seeing a number of other people who have had
similar issues with accessing git@xxxxxxxxxx....

and they seem to discuss using the ssh-agent for the key.

But none of the tutorials I've seen indicate you need to use a keyring..

thanks

On Sun, Jan 14, 2024 at 3:54 AM Jeffrey Walton <noloader@xxxxxxxxx> wrote:
>
> On Sun, Jan 14, 2024 at 3:07 AM bruce <badouglas@xxxxxxxxx> wrote:
> >
> > hi  sorry for the typo..
> >
> > the file paths matched in my actual test...
> >
> > the passphrase
> >  issue is throwing me
>
> Post your $HOME/.gitconfig file, and your <project>/.git/config file.
>
> For me, I handle SSH check-ins via $HOME/.gitconfig :
>
> $ cat $HOME/.gitconfig
> [user]
>    email = noloader@xxxxxxxxx
>    name = Jeffrey Walton
>    signingkey = 3F537D88ADBC1677
> [url "ssh://git@xxxxxxxxxx"]
>     pushInsteadOf = https://github.com
> [url "ssh://git@xxxxxxxxxxxxxxxx"]
>     pushInsteadOf = https://salsa.debian.org
>
> [push]
>    default = current
> [gpg]
>    program = gpg2
>
> And then a particular project will use SSH, even though a checkout
> happened with HTTPS:
>
> $ cd cryptopp-fork
> $ cat .git/config
> [core]
>        repositoryformatversion = 0
>        filemode = true
>        bare = false
>        logallrefupdates = true
> [remote "origin"]
>        url = https://github.com/noloader/cryptopp
>        fetch = +refs/heads/*:refs/remotes/origin/*
> [branch "master"]
>        remote = origin
>        merge = refs/heads/master
> [remote "upstream"]
>        url = https://github.com/weidai11/cryptopp
>        fetch = +refs/heads/*:refs/remotes/upstream/*
>
> Jeff
> --
> _______________________________________________
> users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
> To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
> Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
> Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
--
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux