From: waynevanson <waynevanson@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: spago-0.16.0
Date: Tue, 08 Sep 2020 13:02:21 +0200 [thread overview]
Message-ID: <20200908110221.lOPy4buRRSDqh3Ny1QoWRi4RVrd5IxcNDaAQiIayn3k@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-24723@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1371 bytes --]
New comment by waynevanson on void-packages repository
https://github.com/void-linux/void-packages/pull/24723#issuecomment-688793927
Comment:
This is now set up to build from source.
I've been having some trouble with the patches. I've never patched before. Any insight on why this might be happening? Check out TravisCI for some insight:
```sh
=> spago-0.16.0_1: verifying checksum for distfile '0.16.0.tar.gz'... OK.
=> spago-0.16.0_1: running do-extract hook: 00-distfiles ...
=> spago-0.16.0_1: extracting distfile(s), please wait...
=> spago-0.16.0_1: running do-patch hook: 00-patches ...
=> spago-0.16.0_1: patching: 7dcd30d810d29c2bf2ae61c7947d183255b1844e.patch.
=> ERROR: spago-0.16.0_1: do-patch_00-patches: 'patch -sl ${_args} -i ${_patch} 2> /dev/null' exited with 2
=> ERROR: in _process_patch() at common/hooks/do-patch/00-patches.sh:34
=> ERROR: in hook() at common/hooks/do-patch/00-patches.sh:43
=> ERROR: in run_func() at common/xbps-src/shutils/common.sh:21
=> ERROR: in run_pkg_hooks() at common/xbps-src/shutils/common.sh:242
=> ERROR: in run_step() at common/xbps-src/shutils/common.sh:71
=> ERROR: in main() at common/xbps-src/libexec/xbps-src-dopatch.sh:33
The command "if [ -z "$XLINT" ]; then docker exec -t void hostrepo/common/travis/build.sh $BOOTSTRAP $ARCH; fi" exited with 1.
```
next prev parent reply other threads:[~2020-09-08 11:02 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-07 1:06 [PR PATCH] " waynevanson
2020-09-07 1:10 ` sgn
2020-09-07 4:00 ` waynevanson
2020-09-07 8:04 ` fosslinux
2020-09-07 8:05 ` [PR REVIEW] " fosslinux
2020-09-07 8:05 ` fosslinux
2020-09-07 23:24 ` waynevanson
2020-09-08 10:49 ` [PR PATCH] [Updated] " waynevanson
2020-09-08 10:57 ` waynevanson
2020-09-08 11:02 ` waynevanson [this message]
2020-09-08 11:09 ` ericonr
2020-09-08 11:17 ` [PR PATCH] [Updated] " waynevanson
2020-09-08 11:19 ` waynevanson
2020-09-08 11:41 ` ericonr
2020-09-08 11:42 ` ericonr
2020-09-08 12:08 ` [PR REVIEW] " ahesford
2020-09-08 12:08 ` ahesford
2020-09-08 12:08 ` ahesford
2020-09-08 12:08 ` ahesford
2020-09-08 13:27 ` waynevanson
2020-09-08 13:56 ` ericonr
2020-09-08 16:47 ` Chocimier
2020-09-08 17:19 ` ahesford
2020-09-09 1:29 ` [PR REVIEW] " waynevanson
2020-09-09 1:49 ` waynevanson
2020-09-12 2:26 ` waynevanson
2020-09-12 2:31 ` [PR PATCH] [Updated] " waynevanson
2020-09-12 5:03 ` waynevanson
2020-09-12 11:05 ` fosslinux
2020-09-12 13:47 ` [PR REVIEW] " ahesford
2020-09-12 13:47 ` ahesford
2020-09-12 13:47 ` ahesford
2020-09-12 15:20 ` ericonr
2020-09-13 7:04 ` waynevanson
2020-09-13 7:17 ` waynevanson
2020-09-13 7:58 ` fosslinux
2020-10-22 12:17 ` [PR PATCH] [Updated] " waynevanson
2020-10-22 12:32 ` waynevanson
2020-10-22 20:19 ` New package: spago-0.16.0 (WIP) fosslinux
2020-10-24 1:26 ` waynevanson
2021-01-18 3:46 ` waynevanson
2021-01-18 3:46 ` waynevanson
2021-03-25 3:55 ` [PR PATCH] [Closed]: [WIP] New package: spago-0.16.0 waynevanson
2021-03-25 3:57 ` waynevanson
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=20200908110221.lOPy4buRRSDqh3Ny1QoWRi4RVrd5IxcNDaAQiIayn3k@z \
--to=waynevanson@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).