From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail02.haj.ipfire.org (localhost [IPv6:::1]) by mail02.haj.ipfire.org (Postfix) with ESMTP id 4ddhCX6j8sz2y2s for ; Sat, 27 Dec 2025 12:11:04 +0000 (UTC) Received: from mail01.ipfire.org (mail01.haj.ipfire.org [IPv6:2001:678:b28::25]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange x25519 server-signature ECDSA (secp384r1 raw public key) server-digest SHA384 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mail01.haj.ipfire.org", Issuer "R12" (verified OK)) by mail02.haj.ipfire.org (Postfix) with ESMTPS id 4ddhCT30T5z2xMw for ; Sat, 27 Dec 2025 12:11:01 +0000 (UTC) Received: from [127.0.0.1] (localhost [127.0.0.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange x25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mail01.ipfire.org (Postfix) with ESMTPSA id 4ddhCR5z7yz1sd; Sat, 27 Dec 2025 12:10:59 +0000 (UTC) DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003ed25519; t=1766837460; 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=/SMQfrBnvYpz5WQq6dIz9Y0j6DOO19E5R5Gvtg0cdq0=; b=3Upu96vUWH30NF5Yw9ldMyEeRytdPn3PYZfdtd/shxe8ftHu5ZN4TlJJmf95RZjnS+3yz1 QVBYI3v81CERmRBA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003rsa; t=1766837460; 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=/SMQfrBnvYpz5WQq6dIz9Y0j6DOO19E5R5Gvtg0cdq0=; b=cytvEj7IAOXzaE9nYP7oxOn1B+8os9ncYYl4Bh/sLGWPRfl6OZpKiy8wUL21a22h7D7bG/ 9Dh2GsQjc5mdVTcQYG1Yf4hOp6y/GKcp0EXX0pTHJfKg7SRX511kuJehV0OThiVlSgcYAx Xiz0NH2XfpS7xMyqDY1XMqMu2GY2K9hlO5b/IyR8ch4lX6liYgvUfnsYVXogD9uHFXm3uX hSlj/V1gXV4mG9um1ozPwdShqdtMxlyFi5MZtoqkF/v6Rao+K+iMOpgXL46mJ4DYBglXz5 kLNy5nTbV4M4RnSDTH/m2FNWrCpWn3LMdvKna65OSaDkAfKM3kJWIrxmwKtJ9A== Message-ID: Date: Sat, 27 Dec 2025 13:10:54 +0100 Precedence: list List-Id: List-Subscribe: , List-Unsubscribe: , List-Post: List-Help: Sender: Mail-Followup-To: MIME-Version: 1.0 Subject: Re: Fwd: GIT has had enough and is no longer interested. Thats it! To: Matthias Fischer References: <9ef4f1dc-57f8-4926-a722-543a170f77e7@ipfire.org> From: Adolf Belka Content-Language: en-GB Cc: "IPFire: Development-List" In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Hi Matthias, Only thing I can think of is that there was a problem, which got fixed or resolved itself but you have the faulty connection now in your browser cache. Maybe try clearing your browser cache and try again. If that doesn't work, I don't have any other thoughts right now. You will then have to wait for a response from Michael or Rico. Regards, Adolf. On 27/12/2025 02:23, Matthias Fischer wrote: > On 27.12.2025 00:31, Adolf Belka wrote: >> Hi Matthias, > Hallo Adolf, ;-) > > see my comments below... > >> On 26/12/2025 20:06, Matthias Fischer wrote: >>> Hi Michael, >>> >>> sorry for this, but since the mail below can't still be seen on the >>> list, I don't know if everything is working as it should - so I'm >>> sending it directly to you. Just FYI only... ;-) >> I can see both of your mails on the development list. > I can see none of mine. > >>> All the best for now and the next year! >>> Matthias >>> >>> -------- Forwarded Message -------- >>> Subject: GIT has had enough and is no longer interested. Thats it! >>> Date: Fri, 26 Dec 2025 14:01:51 +0100 >>> From: Matthias Fischer >>> To: IPFire: Development-List >>> >>> Hi, >>> >>> sorry to interrupt any preparations for new year, but GIT doesn't like >>> me (or us?) anymore: >>> >>> Since two days https://git.ipfire.org/ leads to: >>> >>> "Forbidden >>> >>> You don't have permission to access this resource." >> I am getting access to the git repo via your link without any of those >> warning messages. > Hm. I still have "no permission to access this resource". > >> Either the problem has been fixed or you are experiencing an issue not >> related to the infrastructure itself.  Hopefully it is the former. > Nope. No change. > > I'll wait. New year, new luck. It won't be long now... > > Best > Matthias > >> Guten Rutsch. > Danke - ebenso! ;-) > >> Adolf. >>> Just for the records... ;-) >>> >>> Best regards and all the best for the new year...! >>> >>> Matthias >>> >>> > -- Sent from my laptop