public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: "Fabian Grünbichler" <f.gruenbichler@proxmox.com>
To: Tianyu Chen <billchenchina2001@gmail.com>
Cc: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
	Zenithal <i@zenithal.me>
Subject: Re: [pve-devel] Building proxmox on riscv64 Debian Sid
Date: Tue, 21 Feb 2023 15:37:19 +0100 (CET)	[thread overview]
Message-ID: <1341953105.1062.1676990239395@webmail.proxmox.com> (raw)

> Tianyu Chen <billchenchina2001@gmail.com> hat am 21.02.2023 14:11 CET geschrieben:
> On Tue, Feb 21, 2023 at 12:19:39PM +0100, Fabian Grünbichler wrote:
> > 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.
> 
> 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 ping this thread once our bookworm packages are available as preview.

but like Wolfgang said - there are two crates that have an incompatible version in bookworm:
- zstd (and zstd-safe and zstd-sys), the patch for that is fairly mechanical
- 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 proxmox-apt change for also accepting Bookworm or skipping that test.

> > 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)
> 
> Gotcha.
> 
> > in the proxmox workspace you can build them in the order required by their individual build dependencies
> 
> 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-build for that, we mostly do it by hand since we only (re-)bootstrap every ~2 years when a new Debian stable release is approaching..

hope that helps!




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

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-21 14:37 Fabian Grünbichler [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-02-27  7:36 Fabian Grünbichler
2023-02-21 14:32 Fabian Grünbichler
     [not found] <mailman.261.1676973980.376.pve-devel@lists.proxmox.com>
2023-02-21 11:14 ` Wolfgang Bumiller
2023-02-21 11:19 ` 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=1341953105.1062.1676990239395@webmail.proxmox.com \
    --to=f.gruenbichler@proxmox.com \
    --cc=billchenchina2001@gmail.com \
    --cc=i@zenithal.me \
    --cc=pve-devel@lists.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