From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id 942B3939D9 for ; Tue, 21 Feb 2023 15:37:21 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 76CE44322 for ; Tue, 21 Feb 2023 15:37:21 +0100 (CET) Received: from proxmox-new.maurer-it.com (proxmox-new.maurer-it.com [94.136.29.106]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS for ; Tue, 21 Feb 2023 15:37:20 +0100 (CET) Received: from proxmox-new.maurer-it.com (localhost.localdomain [127.0.0.1]) by proxmox-new.maurer-it.com (Proxmox) with ESMTP id 6714F47F59; Tue, 21 Feb 2023 15:37:20 +0100 (CET) Date: Tue, 21 Feb 2023 15:37:19 +0100 (CET) From: =?UTF-8?Q?Fabian_Gr=C3=BCnbichler?= To: Tianyu Chen Cc: Proxmox VE development discussion , Zenithal Message-ID: <1341953105.1062.1676990239395@webmail.proxmox.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Priority: 3 Importance: Normal X-Mailer: Open-Xchange Mailer v7.10.6-Rev32 X-Originating-Client: open-xchange-appsuite X-SPAM-LEVEL: Spam detection results: 0 AWL 0.126 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record URIBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [proxmox.com] Subject: Re: [pve-devel] Building proxmox on riscv64 Debian Sid X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Feb 2023 14:37:21 -0000 > Tianyu Chen hat am 21.02.2023 14:11 CET ges= chrieben: > On Tue, Feb 21, 2023 at 12:19:39PM +0100, Fabian Gr=C3=BCnbichler wrote: > > unless you have very little time left to wait before proceeding, you wi= ll likely have considerable less work (other than rebuilding packages for r= iscv64) if you wait for our bookworm-targeting branches/repos to become ava= ilable. >=20 > As previous e-mail, I'm wondering when will the bookworm tree be > available? the usual answer is "when it's done" ;) we don't want to fork too early, as= that increases the amount of work we have to do. I'll try to remember to p= ing this thread once our bookworm packages are available as preview. but like Wolfgang said - there are two crates that have an incompatible ver= sion in bookworm: - zstd (and zstd-safe and zstd-sys), the patch for that is fairly mechanica= l - syslog (could be backported to the bullseye-based releases) and a few crates that are not in bookworm or too old, as well as the proxmo= x-apt change for also accepting Bookworm or skipping that test. > > the corresponding repository is at https://git.proxmox.com/?p=3Ddebcarg= o-conf.git;a=3Dsummary (it's a fork of the Debian rust team's debcargo-conf= repository with some additional crates and lots of backports for bullseye) >=20 > Gotcha. >=20 > > in the proxmox workspace you can build them in the order required by th= eir individual build dependencies >=20 > Okay, seems porting to a new architecture doesn't have that. well, you have to sort out the actual ordering yourself (I just meant that = the build-dependencies should be correct and you can use them for ordering = the builds) - not sure what tooling you use ;) e.g., debian uses wanna-buil= d for that, we mostly do it by hand since we only (re-)bootstrap every ~2 y= ears when a new Debian stable release is approaching.. hope that helps!