From: "MOESSBAUER, Felix" <felix.moessbauer@siemens.com>
To: "isar-users@googlegroups.com" <isar-users@googlegroups.com>
Cc: "Bovensiepen, Daniel (bovi)" <daniel.bovensiepen@siemens.com>
Subject: debian-sid build for RISCV64 broken
Date: Fri, 10 Nov 2023 08:13:38 +0000 [thread overview]
Message-ID: <bbe922491ef84aa6c2c0822712d13669b05fd7df.camel@siemens.com> (raw)
Dear devs,
we currently cannot build the riscv64 targets, as the sbuild chroot
packages have conflicting internal dependencies. This happens quite
frequently due to updates to the upstream sid repositories.
I'm wondering if we should pin riscv64 to snapshots.debian.org to avoid
these breaks. However, there we are rate-limited, making our builds
rather slow / unstable.
I'm open for other approaches, but would highly appreciate if we could
have a stable riscv64 build.
Best regards,
Felix
--
Siemens AG, Linux Expert Center
Otto-Hahn-Ring 6, 81739 München, Germany
next reply other threads:[~2023-11-10 8:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-10 8:13 MOESSBAUER, Felix [this message]
2023-11-10 8:22 ` Jan Kiszka
2023-11-10 8:37 ` MOESSBAUER, Felix
2023-11-10 8:44 ` Jan Kiszka
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=bbe922491ef84aa6c2c0822712d13669b05fd7df.camel@siemens.com \
--to=felix.moessbauer@siemens.com \
--cc=daniel.bovensiepen@siemens.com \
--cc=isar-users@googlegroups.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