git@vger.kernel.org list mirror (unofficial, one of many)
 help / color / mirror / code / Atom feed
* error
@ 2016-09-22 23:02 Luciano Schillagi
  2016-09-23  4:46 ` error Jeff King
  0 siblings, 1 reply; 5+ messages in thread
From: Luciano Schillagi @ 2016-09-22 23:02 UTC (permalink / raw)
  To: git

Hi,

please, what should I do to fix this error? thanks


Luko ~ $ git init
error: malformed value for push.default: aguas
error: Must be one of nothing, matching, simple, upstream or current.
fatal: bad config variable 'push.default' in file '/Users/imac/.gitconfig' at line 16
-bash: __git_ps1: command not found

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: error
  2016-09-22 23:02 error Luciano Schillagi
@ 2016-09-23  4:46 ` Jeff King
  0 siblings, 0 replies; 5+ messages in thread
From: Jeff King @ 2016-09-23  4:46 UTC (permalink / raw)
  To: Luciano Schillagi; +Cc: git

On Thu, Sep 22, 2016 at 08:02:35PM -0300, Luciano Schillagi wrote:

> please, what should I do to fix this error? thanks
> 
> Luko ~ $ git init
> error: malformed value for push.default: aguas
> error: Must be one of nothing, matching, simple, upstream or current.
> fatal: bad config variable 'push.default' in file '/Users/imac/.gitconfig' at line 16
> -bash: __git_ps1: command not found

Your config file has a bogus value in it.  Try:

  git config --global --unset push.default

Or you may want to simply edit /Users/imac/.gitconfig by hand. It is not
clear where the bogus value came from, but possibly the file is
corrupted in some way (so you are better off examining it first before
asking git to blindly change it).

-Peff

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: error
       [not found] ` <C1F7B566-69F4-4A22-89EA-59B24677DF43@gmail.com>
@ 2016-10-04 17:27   ` Jeff King
  0 siblings, 0 replies; 5+ messages in thread
From: Jeff King @ 2016-10-04 17:27 UTC (permalink / raw)
  To: Luciano Schillagi; +Cc: git

[re-adding git@vger to the cc; please keep conversations on the list so
 everybody can benefit from the answers]

On Tue, Oct 04, 2016 at 01:13:16PM -0300, Luciano Schillagi wrote:

> I ran the command
> 
> Luko ~ $ git config --global --unset push.default
> 
> 
> and it gives me the following
> 
> warning: push.default has multiple values

Ah, OK. "--unset-all" would do the trick, but it may only be one
instance that you want to get rid of...

> I can access my file .gitconfig
> 
> I send attached...
> [...]
>
> [push]
> 	default = upstream
> 	default = aguas

Yep. Deleting the second line there will make your problem go away, and
presumably the first is a config setting you'd want to keep. That still
doesn't answer the question of how the "aguas" line got there, but I can
guess that at some point you might have set "push.default" instead of
"remote.pushdefault".

-Peff

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: Error
  2013-07-10  1:30 Error Chanakya Vattikuti
@ 2013-07-10 15:15 ` Konstantin Khomoutov
  0 siblings, 0 replies; 5+ messages in thread
From: Konstantin Khomoutov @ 2013-07-10 15:15 UTC (permalink / raw)
  To: Chanakya Vattikuti; +Cc: git

On Tue, 9 Jul 2013 20:30:37 -0500
Chanakya Vattikuti <gk2cveragon1@gmail.com> wrote:

> I get this error message when trying to create a shared ssh key in
> Mac osx Lion

This problem has nothing to do with Git as it purely is about
transferring a public part of your SSH key to another host.
So try asking on the OS support channels.

> scp .ssh/id_rsa.pub cvattiku@cook.cs.uno.edu:~/
> ssh_exchange_identification: Connection closed by remote host
> lost connection

Since the public part of your key is not transferred to that remote host
yet, and it is not registered as a trusted key there, you have to use
an SSH authentication method other than "publickey".  Or, if you have
another SSH key which is registered as trusted on the remote host, you
might try to use it explicitly using the "-i <private_key_file_>"
command-line option to `scp`.

If this fails or not applicable, at least try to run `scp` with
multiple "-v" command-line options (like `scp -vvvv ...`) to get
extensive details about authentication protocols it tried with the
server and which of them were agreed upon by both sides and tried.

It might turn out that the server only accepts publickey authentication
mechanism, and so you are not able to upload and register your public
key yourself (chicken and egg problem).  In that case, contact the
server's system administrator for assistance.

If the server has certain "Git hosting" solution like Gitlab, you might
need to try registering your key using some other means like logging to
your Git account via some web interface and pasting the key there --
just like you'd do this on github.

If studying that information won't help you, provide it when you will
be asking this question on the Mac OS support channels.

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Error
@ 2013-07-10  1:30 Chanakya Vattikuti
  2013-07-10 15:15 ` Error Konstantin Khomoutov
  0 siblings, 1 reply; 5+ messages in thread
From: Chanakya Vattikuti @ 2013-07-10  1:30 UTC (permalink / raw)
  To: git

I get this error message when trying to create a shared ssh key in Mac osx Lion

scp .ssh/id_rsa.pub cvattiku@cook.cs.uno.edu:~/
ssh_exchange_identification: Connection closed by remote host
lost connection

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2016-10-04 17:27 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-09-22 23:02 error Luciano Schillagi
2016-09-23  4:46 ` error Jeff King
     [not found] <CAK99BNA_2hwgkLUap_ThOG8drWkP6f74hdW=SNq_DpuNW=j2ew@mail.gmail.com>
     [not found] ` <C1F7B566-69F4-4A22-89EA-59B24677DF43@gmail.com>
2016-10-04 17:27   ` error Jeff King
  -- strict thread matches above, loose matches on Subject: below --
2013-07-10  1:30 Error Chanakya Vattikuti
2013-07-10 15:15 ` Error Konstantin Khomoutov

Code repositories for project(s) associated with this inbox:

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).