From: Logarithmus <Logarithmus@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] [RFC] Run ./xbps-src check inside qemu for non-x86_64 architectures
Date: Sun, 04 Jul 2021 22:53:56 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-31805@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 352 bytes --]
New issue by Logarithmus on void-packages repository
https://github.com/void-linux/void-packages/issues/31805
Description:
Currently `./xbps-src check` is being skipped for cross-builds. What do you think about using `qemu` for running the tests inside it? Is there interest from Void team in having this? If yes, I can try to make proof of concept.
next reply other threads:[~2021-07-04 20:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-04 20:53 Logarithmus [this message]
2021-07-15 11:35 ` ahesford
2022-05-24 2:13 ` github-actions
2022-06-08 2:11 ` [ISSUE] [CLOSED] " github-actions
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-31805@inbox.vuxu.org \
--to=logarithmus@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/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;
as well as URLs for NNTP newsgroup(s).