public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Wolfgang Bumiller <w.bumiller@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Cc: "Tianyu Chen" <billchenchina2001@gmail.com>,
	Zenithal <i@zenithal.me>,
	"Proxmox Support Team" <support@proxmox.com>,
	"Fabian Grünbichler" <f.gruenbichler@proxmox.com>
Subject: Re: [pve-devel] Building proxmox on riscv64 Debian Sid
Date: Tue, 21 Feb 2023 12:14:04 +0100	[thread overview]
Message-ID: <20230221111404.w5b7rper6e36cgko@casey.proxmox.com> (raw)
In-Reply-To: <mailman.261.1676973980.376.pve-devel@lists.proxmox.com>

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)




       reply	other threads:[~2023-02-21 11:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.261.1676973980.376.pve-devel@lists.proxmox.com>
2023-02-21 11:14 ` Wolfgang Bumiller [this message]
2023-02-21 11:19 ` Fabian Grünbichler
2023-02-21 14:32 Fabian Grünbichler
2023-02-21 14:37 Fabian Grünbichler
2023-02-27  7:36 Fabian Grünbichler

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20230221111404.w5b7rper6e36cgko@casey.proxmox.com \
    --to=w.bumiller@proxmox.com \
    --cc=billchenchina2001@gmail.com \
    --cc=f.gruenbichler@proxmox.com \
    --cc=i@zenithal.me \
    --cc=pve-devel@lists.proxmox.com \
    --cc=support@proxmox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal