From: tranzystorek-io <tranzystorek-io@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: helix-22.03
Date: Thu, 31 Mar 2022 17:08:04 +0200 [thread overview]
Message-ID: <20220331150804.1bWlsLcWya8CbqF5cWidBRDABW4n-rbkOPNpzuKvqCQ@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36429@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 431 bytes --]
New comment by tranzystorek-io on void-packages repository
https://github.com/void-linux/void-packages/pull/36429#issuecomment-1084724385
Comment:
> Any idea how to fix i686?
The closest lead I've found is https://bugzilla.redhat.com/show_bug.cgi?id=2020861. On the other hand, Those failing things are doctests built for small usage examples for internal code, I'm guessing we could just disable them and still package i686?
next prev parent reply other threads:[~2022-03-31 15:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-31 4:24 [PR PATCH] " tranzystorek-io
2022-03-31 4:27 ` [PR PATCH] [Updated] " tranzystorek-io
2022-03-31 11:29 ` tranzystorek-io
2022-03-31 11:31 ` shizonic
2022-03-31 14:51 ` leahneukirchen
2022-03-31 15:08 ` tranzystorek-io [this message]
2022-03-31 15:09 ` tranzystorek-io
2022-03-31 18:28 ` [PR PATCH] [Updated] " tranzystorek-io
2022-03-31 18:55 ` tranzystorek-io
2022-03-31 19:01 ` [PR PATCH] [Merged]: " leahneukirchen
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=20220331150804.1bWlsLcWya8CbqF5cWidBRDABW4n-rbkOPNpzuKvqCQ@z \
--to=tranzystorek-io@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).