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 ECFD1938E6 for ; Tue, 21 Feb 2023 12:19:41 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id CE709202C for ; Tue, 21 Feb 2023 12:19:41 +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 12:19:40 +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 A969047E22; Tue, 21 Feb 2023 12:19:40 +0100 (CET) Date: Tue, 21 Feb 2023 12:19:39 +0100 (CET) From: =?UTF-8?Q?Fabian_Gr=C3=BCnbichler?= To: Proxmox VE development discussion Cc: Tianyu Chen , Zenithal Message-ID: <1830691257.922.1676978379428@webmail.proxmox.com> In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit 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 11:19:42 -0000 > Tianyu Chen via pve-devel hat am 21.02.2023 07:29 CET geschrieben: > Hi all, > > I'm trying to build proxmox on riscv64 Debian Sid, and I'm having some > questions when building. out of interest - when you say "proxmox", you mean Proxmox VE? on what hardware and for what use case are you trying to port it? > 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? 1. our git repositories are hosted on git.proxmox.com (the Github org is just an unofficial mirror) 2. our repos target bullseye 3. as always, when a new Debian stable release is approaching we will also target that for our new stable release(s), and once we are done, publish the resulting repositories unless you have very little time left to wait before proceeding, you will likely have considerable less work (other than rebuilding packages for riscv64) if you wait for our bookworm-targeting branches/repos to become available. > 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? the corresponding repository is at https://git.proxmox.com/?p=debcargo-conf.git;a=summary (it's a fork of the Debian rust team's debcargo-conf repository with some additional crates and lots of backports for bullseye) > 3. Also proxmox-rs, can I build subprojects by built-dependency order > since I don't have them in my pool? in the proxmox workspace you can build them in the order required by their individual build dependencies > 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? it's used for repository configuration and update querying (e.g., by pve-manager via proxmox-perl-rs).