From: SpidFightFR <SpidFightFR@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: mesa: update to 23.1.1. (+ required consul update)
Date: Sat, 27 May 2023 10:52:28 +0200 [thread overview]
Message-ID: <20230527085228.TVCIuma7PP2MX9MyudYz6Klue21ZKbS_OAO8SDtQZtQ@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-44108@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 748 bytes --]
New comment by SpidFightFR on void-packages repository
https://github.com/void-linux/void-packages/pull/44108#issuecomment-1565287083
Comment:
@classabbyamp i get an error wit the updated commit of consul:
```
=> ERROR: mesa-23.1.1_1: do-patch_00-patches: 'patch -s ${_args} < "${_patch}" 2> /dev/null' exited with 1
=> ERROR: in _process_patch() at common/hooks/do-patch/00-patches.sh:34
=> ERROR: in hook() at common/hooks/do-patch/00-patches.sh:51
=> ERROR: in run_func() at common/xbps-src/shutils/common.sh:21
=> ERROR: in run_pkg_hooks() at common/xbps-src/shutils/common.sh:262
=> 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
```
next prev parent reply other threads:[~2023-05-27 8:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-26 21:56 [PR PATCH] " SpidFightFR
2023-05-26 21:58 ` [PR PATCH] [Updated] " SpidFightFR
2023-05-27 8:52 ` SpidFightFR [this message]
2023-05-27 8:56 ` SpidFightFR
2023-05-27 8:58 ` classabbyamp
2023-05-27 9:07 ` SpidFightFR
2023-05-27 9:42 ` [PR PATCH] [Updated] " SpidFightFR
2023-05-27 9:46 ` SpidFightFR
2023-05-27 13:54 ` mesa: update to 23.1.1 abenson
2023-05-27 14:15 ` abenson
2023-05-27 15:19 ` [PR PATCH] [Updated] " SpidFightFR
2023-05-27 15:20 ` SpidFightFR
2023-05-29 16:24 ` classabbyamp
2023-05-29 17:51 ` [PR PATCH] [Closed]: " SpidFightFR
2023-05-29 17:51 ` [PR PATCH] [Updated] " SpidFightFR
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=20230527085228.TVCIuma7PP2MX9MyudYz6Klue21ZKbS_OAO8SDtQZtQ@z \
--to=spidfightfr@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).