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 67418938DC for ; Tue, 21 Feb 2023 12:14:07 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 46CE61EA4 for ; Tue, 21 Feb 2023 12:14:07 +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) server-digest SHA256) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS for ; Tue, 21 Feb 2023 12:14:06 +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 0D2AC47E11; Tue, 21 Feb 2023 12:14:06 +0100 (CET) Date: Tue, 21 Feb 2023 12:14:04 +0100 From: Wolfgang Bumiller To: Proxmox VE development discussion Cc: Tianyu Chen , Zenithal , Proxmox Support Team , Fabian =?utf-8?Q?Gr=C3=BCnbichler?= Message-ID: <20230221111404.w5b7rper6e36cgko@casey.proxmox.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-SPAM-LEVEL: Spam detection results: 0 AWL 0.185 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 11:14:07 -0000 On Tue, Feb 21, 2023 at 02:29:22PM +0800, Tianyu Chen via pve-devel wrote: > Hi all, > > I'm trying to build proxmox on riscv64 Debian Sid, and I'm having some > questions when building. Very nice. As a side note: the next pve-container release will recognize riscv32/64 architectures (and therefore also work via qemu-static to run riscv contaienrs on amd64 hosts via binfmt_misc). (Personally, I do intend to give a fully bootstrapped PVE a spin on a vision five 2 at some point, but can't commit to any timeline there atm., but it'll have to be bookworm, not bullseye, and as you already figured out, getting there is a bit more involved now with the rust crate version dependencies ;-)) > > 1. When I'm building proxmox-rs, the dependencies are incorrect. I > fetched proxmox-rs source code from > https://github.com/proxmox/proxmox-rs.git and it shows that most > dependencies are targeting bullseye, not Sid. I've tried editing > Cargo.toml and some of them worked. Is there a actively developing > branch targeting Sid? Or is there a schedule against testing(bookworm) > so I can schedule the porting? The rust crate situation is a *little* bit annoying due the version differences. Some, like zstd, require tiny modifications (unfortunately in a way that supporting both versions in the same code base would require an annoying build script :-S). Some just work because we don't use the affected APIs. I don't think there are any *major* changes required, but I'm not sure. @Fabian did some initial/test-bootstrapping for bookworm and might remember more? But for now there's unfortunately nothing targeting anything past bullseye in the repos as it would just require merging/rebasing without there being an actual release for it yet. > > 2. Missing dependencies. I've found that proxmox have packed some > librust-*-dev packages out of tree. (I mean, Debian tree). Since > librust-*-dev packages are with `Architecture: amd64` (from > http://download.proxmox.com/debian/devel/dists/bullseye/main/binary-amd64/), > I cannot install the proxmox version. Since there's no dsc file in the > pool, Can I assume proxmox only did debcargo things, without any patch? You can find a `debcargo-conf.git` with a `proxmox/bullseye` branch on git.proxmox.com which is the source of all the librust- packages we packaged separately. You can build from that, or, since they're actually source-only packages, you could fixup the architecture on the deb files from our bullseye repo directly (dpkg-deb --extract, sed, dpkg-deb --build) and use it that way ;-) > > 3. Also proxmox-rs, can I build subprojects by built-dependency order > since I don't have them in my pool? There's no automatic ordering in the build system right now. > > 4. proxmox-apt. The package proxmox-apt shows that DebianCodename only > support stable versions, not Sid. test_get_current_release_codename > failed since codename != DebianCodename::Bullseye. I'm wondering where > are these piece of code used? Is there any unexpected behavior with Sid? Hmm, I don't actually know :-) @Fabian? (Why would we even have it test the host version :S)