From: jbenden <jbenden@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR REVIEW] New package: python3-pre-commit-2.15.0_1.
Date: Sun, 07 Nov 2021 00:29:11 +0100 [thread overview]
Message-ID: <20211106232911.fqy7-Umq96C0CVvWFmGlu4u8pflNOvHuqxUV6kpApjY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-33770@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 388 bytes --]
New review comment by jbenden on void-packages repository
https://github.com/void-linux/void-packages/pull/33770#discussion_r744179729
Comment:
I am not sure why i686 GNU is failing... It fully works in a local i686 VBox VM. It was a tad old on packages, so I upgraded and re-tested - still locally works.
What is different about that i686 CI instance, compared to a VBox 32-bit VM?
next prev parent reply other threads:[~2021-11-06 23:29 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-26 19:49 [PR PATCH] " jbenden
2021-10-26 20:30 ` [PR PATCH] [Updated] " jbenden
2021-10-26 20:44 ` jbenden
2021-10-27 16:33 ` Chocimier
2021-10-27 21:35 ` [PR PATCH] [Updated] " jbenden
2021-10-27 21:37 ` jbenden
2021-10-29 19:37 ` Chocimier
2021-10-29 20:19 ` jbenden
2021-11-03 21:08 ` [PR REVIEW] " Chocimier
2021-11-03 22:31 ` jbenden
2021-11-03 22:45 ` paper42
2021-11-06 4:05 ` [PR PATCH] [Updated] " jbenden
2021-11-06 4:07 ` jbenden
2021-11-06 18:56 ` [PR REVIEW] " jbenden
2021-11-06 20:05 ` Chocimier
2021-11-06 22:20 ` [PR PATCH] [Updated] " jbenden
2021-11-06 22:33 ` [PR REVIEW] " jbenden
2021-11-06 23:29 ` jbenden [this message]
2021-11-06 23:32 ` jbenden
2021-11-09 0:10 ` Chocimier
2021-12-06 20:16 ` [PR PATCH] [Updated] " jbenden
2021-12-06 20:20 ` jbenden
2021-12-08 17:29 ` [PR REVIEW] " Chocimier
2021-12-08 17:30 ` Chocimier
2021-12-08 18:52 ` [PR PATCH] [Updated] " jbenden
2021-12-28 23:46 ` jbenden
2021-12-29 23:13 ` [PR PATCH] [Merged]: " Chocimier
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=20211106232911.fqy7-Umq96C0CVvWFmGlu4u8pflNOvHuqxUV6kpApjY@z \
--to=jbenden@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).