public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Matthias Fischer <matthias.fischer@ipfire.org>
To: "IPFire: Development-List" <development@lists.ipfire.org>
Subject: Re: Sources are gone!?
Date: Mon, 10 Mar 2025 13:12:20 +0100	[thread overview]
Message-ID: <bce38c63-7286-409f-ae2d-c3568051443a@ipfire.org> (raw)
In-Reply-To: <D49A6B13-5DB5-46ED-B567-358B96C60504@ipfire.org>

Hi,

On 10.03.2025 10:48, Michael Tremer wrote:
> Good morning,
> 
> Well, this probably was a problem that was caused by the cold reboot from Friday.
> 
> The server probably came up before the file server was ready and therefore could not mount the NFS shares.

Yep. I thought something like this...

> They are back now.

Confirmed - thanks - looks good... ;-)

Best
Matthias

> Please let me know if you find anything else that does not work.
> 
> Best,
> -Michael
> 
>> On 10 Mar 2025, at 09:26, Matthias Fischer <matthias.fischer@ipfire.org> wrote:
>> 
>> Hi,
>> 
>> while I was trying to update one of my devels (just to be sure), GIT
>> told me that the remote repository doesn't exist:
>> 
>> "root@Devel64-2: /git/ipfire-2.x # git pull origin core191
>> mfischer@people.ipfire.org's password:
>> fatal: '/pub/git/ipfire-2.x.git' does not appear to be a git repository
>> fatal: Could not read from remote repository.
>> 
>> Please make sure you have the correct access rights
>> and the repository exists."
>> 
>> Hm...
>> 
>> Then I tried to upload 'htop 3.4.0' but '/pub/sources' is empty...
>> 
>> HM!
>> 
>> I can't see any directories or repositories on 'people.ipfire.org' under
>> /pub/sources/'. Nothing there...
>> 
>> Can anyone confirm?
>> 
>> Best
>> Matthias
>> 
>> 
> 
> 



      reply	other threads:[~2025-03-10 12:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-10  9:26 Matthias Fischer
2025-03-10  9:48 ` Michael Tremer
2025-03-10 12:12   ` Matthias Fischer [this message]

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=bce38c63-7286-409f-ae2d-c3568051443a@ipfire.org \
    --to=matthias.fischer@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