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.
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?
Thanks, and best regards, Peter Müller
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
Hello,
On 15 Sep 2024, at 09:45, Peter Müller peter.mueller@ipfire.org 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.
The build environment should support proxy configuration through environment variables even inside the chroot.
I have been running a build behind a proxy with no other internet access last week and that worked well for me. Please let me know if something does not work as expected.
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.
Attempts to fetch the same repository via its https://git.ipfire.org/pub/git/ipfire-2.x.git URL fail with an error 500.
No, we have not changed anything here. However, I am getting the same problem across many repositories. However when I access them on people01 or fs01, everything is fine.
I disabled the check now because I cannot find anything. The internet has sources that it does not work well for shared repositories.
Has the way for accessing /pub/git/ipfire-2.x.git changed?
No.
-Michael
Thanks, and best regards, Peter Müller
-
Adolf Belka -
Michael Tremer -
Peter Müller