From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <development+bounces-1597-archive=lists.ipfire.org@lists.ipfire.org>
Received: from mail02.haj.ipfire.org (localhost [IPv6:::1])
	by mail02.haj.ipfire.org (Postfix) with ESMTP id 4dysmF31dVz2y1f
	for <archive@lists.ipfire.org>; Sat, 24 Jan 2026 11:20:29 +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)
	(Client CN "mail01.haj.ipfire.org", Issuer "R12" (verified OK))
	by mail02.haj.ipfire.org (Postfix) with ESMTPS id 4dysm96PBTz2xSm
	for <development@lists.ipfire.org>; Sat, 24 Jan 2026 11:20:25 +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 4dysm92hXkz5c2
	for <development@lists.ipfire.org>; Sat, 24 Jan 2026 11:20:25 +0000 (UTC)
DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=ipfire.org;
	s=202003ed25519; t=1769253625;
	h=from:from:reply-to:subject:subject:date:date:message-id:message-id:
	 to:to:cc:mime-version:mime-version:content-type:content-type:
	 content-transfer-encoding:content-transfer-encoding;
	bh=2Cf1/ltxkiP7YF9idSEFiY5as1HmdKSTl7Bv7Cs45Tc=;
	b=zjMDgzt9Wndr65Nv2HUXwBDe4RGjZcIDlwVGKaTIFvFz10cwuStuaPtaUD5adF6NAEJIO6
	B9JOupL0uRLG25Bg==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003rsa;
	t=1769253625;
	h=from:from:reply-to:subject:subject:date:date:message-id:message-id:
	 to:to:cc:mime-version:mime-version:content-type:content-type:
	 content-transfer-encoding:content-transfer-encoding;
	bh=2Cf1/ltxkiP7YF9idSEFiY5as1HmdKSTl7Bv7Cs45Tc=;
	b=gY9KLsRtjByQGunvOAP0HEraCMzMOOkmPGFWgLRioK7cRLcfJSOpmAJ/XaUQJHJss13xcp
	Xnj/6ObqbqBMMI6V0l4tMGeLDprmGvNiGCCI0xrwreiPjAEGFxDiA2mhngeIvhPhrCpbTE
	J2VTki4C3vFl+ltc0TsuoahvAzTOGFvfCpdITLBtmgILWQK2z1wKUM/GfICTWiq2BNEbXG
	AtarrcWdjF38f4UL0vtfL4KLzAIDEc96aeZ5vRxwN44Hw42BMP5FfbkY1yTjAlVAPmFCMe
	wFTdgah3zifT51VatTn17Gf6okHtx+G8t0taChdtKy6uaWnKWTlOoFvjYFBemA==
Message-ID: <48a0fe53-1bbf-4f82-b40a-87ecf2db84cf@ipfire.org>
Date: Sat, 24 Jan 2026 12:20:10 +0100
Precedence: list
List-Id: <development.lists.ipfire.org>
List-Subscribe: <https://lists.ipfire.org/>,
 <mailto:development+subscribe@lists.ipfire.org?subject=subscribe>
List-Unsubscribe: <https://lists.ipfire.org/>,
 <mailto:development+unsubscribe@lists.ipfire.org?subject=unsubscribe>
List-Post: <mailto:development@lists.ipfire.org>
List-Help: <mailto:development+help@lists.ipfire.org?subject=help>
Sender: <development@lists.ipfire.org>
Mail-Followup-To: <development@lists.ipfire.org>
MIME-Version: 1.0
Content-Language: en-GB
To: "IPFire: Development-List" <development@lists.ipfire.org>
From: Adolf Belka <adolf.belka@ipfire.org>
Subject: Cause for aarch64 nightly build failures
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

Hi All,

I was wondering why the aarch64 nightly build was failing for the rust build. I tested out the downloadsrc on the aarch64 build and it failed. I found that the same thing was happening with the riscv64.

After a lot of checking I found that the 1.92.0 version of the tarballs had not been copied into the /build/nightly/.cache/ directory for some reason, although they have been in the source-2.x/ directory since 22nd Jan.

I am sure someone will know how to fix it.

Regards,

Adolf.