git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Jeff King <peff@peff.net>
To: Tobias Boesch <tobias.boesch@googlemail.com>
Cc: git@vger.kernel.org
Subject: Re: Git Gui Clone: Error Failed to create repository (with hints)
Date: Tue, 2 Apr 2024 21:30:39 -0400	[thread overview]
Message-ID: <20240403013039.GD892394@coredump.intra.peff.net> (raw)
In-Reply-To: <6aadf39561e13681c069d4da7b1a4581f143dc92.camel@googlemail.com>

On Fri, Mar 29, 2024 at 10:12:17PM +0100, Tobias Boesch wrote:

> when I clone a git repo (from github or COdeberg) through Git Gui I get
> the following GUI error (nothing in the terminal and nothing in
> journalctl):
> 
> "Failed to create repository <repo-path>: Hint Using 'master' as the
> name for the initial branch. This default branch..." and so on.
> 
> Screenshot
> https://i.postimg.cc/66df98MZ/Screenshot-from-2024-03-29-22-06-49.png
> 
> I have no idea what is going on here. Has someone an idea what the
> reason could be?

I don't work on or use git-gui, but it is written in Tcl/Tk. And IIRC
Tcl is very anxious to consider programs that print anything to stderr
as "failed". And in this case we are just printing warning/hint
diagnostics to stderr.

I suspect there are solutions within git-gui's code base to check the
actual exit code, and it's just a bug that we're not using them in this
instance. But the obvious workaround in the meantime is to set the
config that the hint mentions, which should silence it.

> Cloning the same source into the same path from command line works.
> The cloned git repo opens fine in git gui.

Right, the clone is happening fine. It's just that git-gui is
incorrectly thinking that it failed.

-Peff


      reply	other threads:[~2024-04-03  1:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-29 21:12 Git Gui Clone: Error Failed to create repository (with hints) Tobias Boesch
2024-04-03  1:30 ` Jeff King [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20240403013039.GD892394@coredump.intra.peff.net \
    --to=peff@peff.net \
    --cc=git@vger.kernel.org \
    --cc=tobias.boesch@googlemail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public 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).