From mboxrd@z Thu Jan 1 00:00:00 1970 From: Adolf Belka 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 Message-ID: <500bc162-2c1d-40cd-bae9-02f311a2348d@ipfire.org> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============9187500473258210157==" List-Id: --===============9187500473258210157== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi Peter, On 15/09/2024 10:45, Peter M=C3=BCller wrote: > Hello *, > > pursuant to update APR, I am currently trying to get my local build environ= ment working again. > After some back and forth, I failed to bring ./make.sh downloadsrc back int= o a functional state > (which requires properly processing environment variables for HTTP proxy ac= cess), 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 ups= tream does not work: > Trying to do so via SSH (ssh://people.ipfire.org/pub/git/ipfire-2.x.git), G= it complains: > >> fatal: detected dubious ownership in repository at '/pub/git/ipfire-2.x.gi= t' > 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 mess= age 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 sam= e. There was some vulnerability that meant that if the ownerships were differ= ent 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 th= at the path from local git repo to the global .gitconfig is traversable by th= at owner. This might still not be the fix for you as you are having your problem access= ing via ssh and mine was with accessing via git: > Attempts to fetch the same repository via its https://git.ipfire.org/pub/gi= t/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 yes= terday. Hope this turns out to be useful to you. Regards, Adolf | > Thanks, and best regards, > Peter M=C3=BCller --===============9187500473258210157==--