From: "David C. Rankin" <drankinatty@gmail.com>
To: Jamie Landeg-Jones <jamie@catflap.org>,
Johannes.Schindelin@gmx.de, gitster@pobox.com
Cc: msuchanek@suse.de, git@vger.kernel.org
Subject: Re: Local git server can't serve https until repos owned by http, can't serve ssh unless repos owned by user after 2.45.1
Date: Fri, 26 Jul 2024 00:58:22 -0500 [thread overview]
Message-ID: <5747ba0d-7268-4538-9705-11650a7d6e35@gmail.com> (raw)
In-Reply-To: <202407260038.46Q0ctEV083266@donotpassgo.dyslexicfish.net>
On 7/25/24 7:38 PM, Jamie Landeg-Jones wrote:
> Junio C Hamano <gitster@pobox.com> wrote:
>
>> Dscho, the f4aa8c8b (fetch/clone: detect dubious ownership of local
>> repositories, 2024-04-10) is your brainchild and people seem to be
>> unhappy about having to adjust their settings. Are there any advice
>> you can offer them?
>
> This thread has gone quiet. Is it going to be fixed? The issue isn't that
> settings need to be adjusted, it's that it no longer works whatever
> your settings are.
>
> I had to go back to.2.45.0
>
> Cheers
>
I too am stuck. It's a damned if you do, damned if you don't Hobson's choice
of git repo ownership on the server. All worked fine serving both https and
ssh prior to the change, now it is either one or the other but not both. So
either your read-only pulls and clones are hosed, or your read/write are.
If more info is needed, let me know and I'm happy to privide it.
--
David C. Rankin, J.D.,P.E.
next prev parent reply other threads:[~2024-07-26 5:58 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-17 0:36 Local git server can't serve https until repos owned by http, can't serve ssh unless repos owned by user after 2.45.1 David C. Rankin
2024-06-17 18:47 ` Junio C Hamano
2024-06-17 21:15 ` Michal Suchánek
2024-06-25 7:24 ` Michal Suchánek
2024-06-25 16:12 ` Junio C Hamano
2024-06-25 18:34 ` Michal Suchánek
2024-06-26 13:03 ` Phillip Wood
2024-06-26 18:14 ` Junio C Hamano
2024-06-26 18:35 ` Phillip Wood
2024-06-26 18:51 ` Junio C Hamano
2024-09-25 11:34 ` Michal Suchánek
2024-08-29 20:34 ` Joey Hess
2024-07-26 0:38 ` Jamie Landeg-Jones
2024-07-26 5:58 ` David C. Rankin [this message]
2024-07-28 3:46 ` Jamie Landeg-Jones
2024-07-28 6:57 ` David C. Rankin
2024-08-01 0:15 ` [SOLVED] " Jamie Landeg-Jones
2024-08-02 19:31 ` Junio C Hamano
2024-06-18 1:08 ` David C. Rankin
2024-06-24 14:53 ` Junio C Hamano
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5747ba0d-7268-4538-9705-11650a7d6e35@gmail.com \
--to=drankinatty@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jamie@catflap.org \
--cc=msuchanek@suse.de \
/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.
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 NNTP newsgroup(s).