public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: Adolf Belka <adolf.belka@ipfire.org>
Cc: "IPFire: Development-List" <development@lists.ipfire.org>
Subject: Re: Wrong directory in the ipfire next git repo
Date: Mon, 7 Jul 2025 10:44:39 +0100	[thread overview]
Message-ID: <A0320EDC-5CF7-4E30-8BBC-5B23C8C4E40C@ipfire.org> (raw)
In-Reply-To: <dee60245-cb9c-4481-8e34-e2505e55cebb@ipfire.org>

Hello Adolf,

It seems that you are referring to the browser at git.ipfire.org <http://git.ipfire.org/>, where indeed, the directory seems to be incorrect:

  https://git.ipfire.org/?p=ipfire-2.x.git;a=tree;f=config/rootfiles/core;h=505d46abd8fba115e43205bdf2e2950f2c40b47c;hb=refs/heads/next

In my actual file system, the directory is correct:

  root@michael:/build/ipfire-2.x# ll config/rootfiles/core/197/
  total 12
  -rw-r--r-- 1 root root  748 Jun 30 08:53 exclude
  drwxr-xr-x 5 root root 4096 Jul  5 09:48 filelists
  -rw-r--r-- 1 root root 2515 Jul  3 14:55 update.sh

This seems to be a caching issue on the Git server and I will look into this how to resolve it.

Sorry for the inconvenience.

Best,
-Michael

> On 5 Jul 2025, at 11:13, Adolf Belka <adolf.belka@ipfire.org> wrote:
> 
> Hi All,
> 
> The IPFire next git repo was moved to CU197 a couple of days ago but I just noticed that the following directory is in next
> 
> config/rootfiles/core/196/
> 
> instead of
> 
> config/rootfiles/core/197/
> 
> 
> Regards,
> 
> Adolf.
> 



  reply	other threads:[~2025-07-07  9:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-05 10:13 Adolf Belka
2025-07-07  9:44 ` Michael Tremer [this message]
2025-07-07 10:32   ` Adolf Belka
2025-07-07 10:42     ` 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=A0320EDC-5CF7-4E30-8BBC-5B23C8C4E40C@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --cc=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