From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Unable to properly fetch IPFire 2.x source code via Git
Date: Sun, 15 Sep 2024 11:27:40 +0200 [thread overview]
Message-ID: <500bc162-2c1d-40cd-bae9-02f311a2348d@ipfire.org> (raw)
In-Reply-To: <bfa2e755-bddb-4d75-bd32-ed5723d8ab82@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 2235 bytes --]
Hi Peter,
On 15/09/2024 10:45, Peter Müller wrote:
> Hello *,
>
> pursuant to update APR, I am currently trying to get my local build environment working again.
> After some back and forth, I failed to bring ./make.sh downloadsrc back into a functional state
> (which requires properly processing environment variables for HTTP proxy access), and started
> with a fresh clone of my IPFire 2.x Git repository again.
>
> However, even adding /pub/git/ipfire-2.x.git as a remote origin for the upstream does not work:
> Trying to do so via SSH (ssh://people.ipfire.org/pub/git/ipfire-2.x.git), Git complains:
>
>> fatal: detected dubious ownership in repository at '/pub/git/ipfire-2.x.git'
> It then suggests to run "git config --global --add safe.directory /pub/git/ipfire-2.x.git", which
> however does not change anything - at the next attempt, the same error message is shown.
I have had this recommendation in the past from git. It also didn't help me. I found that this was due to an upgrade in git and if I remember correctly it is to do with the ownership of the .gitconfig local and global being the same. There was some vulnerability that meant that if the ownerships were different someone could do something bad.
From what I remember, and it is at least from 2023 or maybe even 2022 when I had this problem, you need to make sure that the ownership of the local and global .gitconfig files are the same, or belong to the same group and also that the path from local git repo to the global .gitconfig is traversable by that owner.
This might still not be the fix for you as you are having your problem accessing via ssh and mine was with accessing via git:
> Attempts to fetch the same repository via its https://git.ipfire.org/pub/git/ipfire-2.x.git URL
> fail with an error 500.
>
> Has the way for accessing /pub/git/ipfire-2.x.git changed?
When I am cloning one of the repo's from fresh then the url I am using is
|git://git.ipfire.org/ipfire-2.x.git I have never used the http: version. The git one is still working currently as I have done a test fresh git clone yesterday. Hope this turns out to be useful to you. Regards, Adolf |
> Thanks, and best regards,
> Peter Müller
next prev parent reply other threads:[~2024-09-15 9:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-15 8:45 Peter Müller
2024-09-15 9:27 ` Adolf Belka [this message]
2024-09-15 10:38 ` Michael Tremer
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=500bc162-2c1d-40cd-bae9-02f311a2348d@ipfire.org \
--to=adolf.belka@ipfire.org \
--cc=development@lists.ipfire.org \
/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