From: Johnnynator <Johnnynator@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] yarn: unbreak on i686
Date: Fri, 29 May 2020 13:31:36 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-22400@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 378 bytes --]
There is a new pull request by Johnnynator against master on the void-packages repository
https://github.com/Johnnynator/void-packages yarn
https://github.com/void-linux/void-packages/pull/22400
yarn: unbreak on i686
aa113ebd02dcaf1a26ae99c4eeca1030aa978d30 fixed the underlying issue
A patch file from https://github.com/void-linux/void-packages/pull/22400.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-yarn-22400.patch --]
[-- Type: text/x-diff, Size: 763 bytes --]
From 6ea3c2dd02ac8dec3c2a2da113cb67acf9d6248d Mon Sep 17 00:00:00 2001
From: John <me@johnnynator.dev>
Date: Fri, 29 May 2020 13:31:07 +0200
Subject: [PATCH] yarn: unbreak on i686
aa113ebd02dcaf1a26ae99c4eeca1030aa978d30 fixed the underlying issue
---
srcpkgs/yarn/template | 4 ----
1 file changed, 4 deletions(-)
diff --git a/srcpkgs/yarn/template b/srcpkgs/yarn/template
index 69d6dcdccea..140faf0b2e0 100644
--- a/srcpkgs/yarn/template
+++ b/srcpkgs/yarn/template
@@ -13,10 +13,6 @@ checksum=f9e09bf375388f489a62a08d6ab0a455ab47d62b32512b35e4315d12d12db4e5
conflicts="yarn-bin>=0"
-case "$XBPS_TARGET_MACHINE" in
- i686) broken="https://build.voidlinux.org/builders/i686_builder/builds/15057/steps/shell_3/logs/stdio"
-esac
-
pre_build() {
yarn
}
next reply other threads:[~2020-05-29 11:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-29 11:31 Johnnynator [this message]
2020-05-31 9:34 ` [PR PATCH] [Merged]: " Johnnynator
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-22400@inbox.vuxu.org \
--to=johnnynator@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).