From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail02.haj.ipfire.org (localhost [127.0.0.1]) by mail02.haj.ipfire.org (Postfix) with ESMTP id 4bbLRc3Jcyz333d for ; Mon, 7 Jul 2025 10:42:52 +0000 (UTC) Received: from mail01.ipfire.org (mail01.haj.ipfire.org [172.28.1.202]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (secp384r1) server-digest SHA384 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mail01.haj.ipfire.org", Issuer "R11" (verified OK)) by mail02.haj.ipfire.org (Postfix) with ESMTPS id 4bbLRX6PsNz2xph for ; Mon, 7 Jul 2025 10:42:48 +0000 (UTC) Received: from [127.0.0.1] (localhost [127.0.0.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail01.ipfire.org (Postfix) with ESMTPSA id 4bbLRX1JhHzK2; Mon, 7 Jul 2025 10:42:48 +0000 (UTC) DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003ed25519; t=1751884968; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=4cJ2Lje7IJgq1ZphQ62YYkB0PRiZZIxKh/0DFRjOB7c=; b=anyLaCZDUzyrmRb1Ltj6RY6e7aEuTX1rkUJqnVJ7KvTKlQU1L0rwdBiIHf+FipVR0280EF STgIYlNzW40R7cDw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003rsa; t=1751884968; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=4cJ2Lje7IJgq1ZphQ62YYkB0PRiZZIxKh/0DFRjOB7c=; b=DQJLzC0M1fN4/meJhbBfQQJXuE91Da1bKGH8eRJzeKQN62t5BOrV1dgOwc7lo3fCwJOGL5 d8nxorLOTEEys23kDfDtg2/dT4r6uRSqDtgkzbEjAnCxfelOKNoitld6btvhKo3y3Ga8HL 0epvbSzooghow5e0IbbqygVmPOs0Ey+ViOXTIdsqo7KegLKh8ahg00Ks7mvTqGPFPmyuCV k5rz9hIQtLHW1i8Ikj/VFVMGiUSXZuPP2HBNjYMBZG2YQi+SHxgL98l8JE13eJjvqFD1gz KAJWuAJVehJJuJP5CUcBjNwiIr6E8AvYGi7K/i2sWpAVompu5Jpbk5ockl0lpA== Content-Type: text/plain; charset=us-ascii Precedence: list List-Id: List-Subscribe: , List-Unsubscribe: , List-Post: List-Help: Sender: Mail-Followup-To: Mime-Version: 1.0 Subject: Re: Wrong directory in the ipfire next git repo From: Michael Tremer In-Reply-To: Date: Mon, 7 Jul 2025 11:42:47 +0100 Cc: "IPFire: Development-List" Content-Transfer-Encoding: quoted-printable Message-Id: <35967ADF-D993-423A-BC59-3CEFD3990E01@ipfire.org> References: To: Adolf Belka 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=3Dipfire-2.x.git;a=3Dtree;f=3Dconfig/rootfiles/c= ore;h=3Da6e66fec1442c33f5ce1f4228aefd41788aeed7a;hb=3Drefs/heads/next > On 7 Jul 2025, at 11:32, Adolf Belka wrote: >=20 > Hi Michael, >=20 > On 07/07/2025 11:44, Michael Tremer wrote: >> Hello Adolf, >> It seems that you are referring to the browser at git.ipfire.org = , where indeed, the directory seems to be = incorrect: >> = https://git.ipfire.org/?p=3Dipfire-2.x.git;a=3Dtree;f=3Dconfig/rootfiles/c= ore;h=3D505d46abd8fba115e43205bdf2e2950f2c40b47c;hb=3Drefs/heads/next >=20 > Yes it was the browser view that I meant. >=20 >> 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 >=20 > Yes, also on my local repo it is correct. >=20 >> This seems to be a caching issue on the Git server and I will look = into this how to resolve it. >=20 > You mentioning a caching issue I cleared my Firefox browser cache and = it now shows 197. >=20 > 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. >=20 > 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, >=20 > Adolf. >=20 >> Best, >> -Michael >>> On 5 Jul 2025, at 11:13, Adolf Belka wrote: >>>=20 >>> Hi All, >>>=20 >>> 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 >>>=20 >>> config/rootfiles/core/196/ >>>=20 >>> instead of >>>=20 >>> config/rootfiles/core/197/ >>>=20 >>>=20 >>> Regards, >>>=20 >>> Adolf. >>>=20 >=20 >=20