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 11:42:47 +0100 [thread overview]
Message-ID: <35967ADF-D993-423A-BC59-3CEFD3990E01@ipfire.org> (raw)
In-Reply-To: <e9fbb616-088e-400f-bd3b-a80b28139243@ipfire.org>
Hello,
Okay I fine-tuned the caching rules slightly.
Now, it will strictly match a hash in the URL and only then cache for forever. Otherwise, we will cache for five minutes.
So this now works fine for me:
https://git.ipfire.org/?p=ipfire-2.x.git;a=tree;f=config/rootfiles/core;h=a6e66fec1442c33f5ce1f4228aefd41788aeed7a;hb=refs/heads/next
> On 7 Jul 2025, at 11:32, Adolf Belka <adolf.belka@ipfire.org> wrote:
>
> Hi Michael,
>
> On 07/07/2025 11:44, Michael Tremer wrote:
>> 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
>
> Yes it was the browser view that I meant.
>
>> 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
>
> Yes, also on my local repo it is correct.
>
>> This seems to be a caching issue on the Git server and I will look into this how to resolve it.
>
> You mentioning a caching issue I cleared my Firefox browser cache and it now shows 197.
>
> It looks like the change from 196 to 197 was not seen by my browser as an actual change in the data so it kept serving me the cached content.
We incorrectly cached too much for too long. It is a risk that you take :)
>> Sorry for the inconvenience.
>
> No problems. I just thought I should highlight it.
No, this was really helpful. I hope it is fixed now.
Looking at stale data is never fun.
-Michael
> Regards,
>
> Adolf.
>
>> 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.
>>>
>
>
prev parent reply other threads:[~2025-07-07 10:42 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
2025-07-07 10:32 ` Adolf Belka
2025-07-07 10:42 ` Michael Tremer [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=35967ADF-D993-423A-BC59-3CEFD3990E01@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