public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: "Peter Müller" <peter.mueller@ipfire.org>
To: development@lists.ipfire.org
Subject: Unable to properly fetch IPFire 2.x source code via Git
Date: Sun, 15 Sep 2024 08:45:00 +0000	[thread overview]
Message-ID: <bfa2e755-bddb-4d75-bd32-ed5723d8ab82@ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1051 bytes --]

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

             reply	other threads:[~2024-09-15  8:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-15  8:45 Peter Müller [this message]
2024-09-15  9:27 ` Adolf Belka
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=bfa2e755-bddb-4d75-bd32-ed5723d8ab82@ipfire.org \
    --to=peter.mueller@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