From: Eloitor <Eloitor@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [WIP] Python3 cairosvg
Date: Wed, 20 Jul 2022 07:44:25 +0200 [thread overview]
Message-ID: <20220720054425.YO1CwExr0NTV_9c8Iz7GmywwLAFtpXMEcbyB6vwbE3s@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38129@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 701 bytes --]
New comment by Eloitor on void-packages repository
https://github.com/void-linux/void-packages/pull/38129#issuecomment-1189853171
Comment:
I'm sorry, I don't know how to properly create the patch, what I did was:
```
cd ~/repos
git clone https://github.com/Kozea/CairoSVG
cd CairoSVG
# I removed the lines containing pytest-runner
git diff > pytest-runner.patch
```
When running `./xbps-src patch python3-CairoSVG` I get the error
```
=> python3-CairoSVG-2.5.2_1: patching: pytest-runner.patch.
3 out of 3 hunks FAILED -- saving rejects to file setup.cfg.rej
=> ERROR: python3-CairoSVG-2.5.2_1: do-patch_00-patches: 'patch -s ${_args} < "${_patch}" 2> /dev/null' exited with 1
```
next prev parent reply other threads:[~2022-07-20 5:44 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-18 13:53 [PR PATCH] " Eloitor
2022-07-18 13:58 ` [PR PATCH] [Updated] " Eloitor
2022-07-18 14:02 ` Eloitor
2022-07-18 14:24 ` Eloitor
2022-07-18 14:25 ` Eloitor
2022-07-18 14:25 ` Eloitor
2022-07-18 14:28 ` [PR PATCH] [Updated] " Eloitor
2022-07-18 14:31 ` Eloitor
2022-07-18 19:06 ` [PR REVIEW] " paper42
2022-07-18 19:07 ` paper42
2022-07-18 19:59 ` Eloitor
2022-07-18 20:04 ` [PR PATCH] [Updated] " Eloitor
2022-07-18 20:06 ` [PR REVIEW] " Eloitor
2022-07-18 20:10 ` paper42
2022-07-18 20:15 ` Eloitor
2022-07-18 20:31 ` paper42
2022-07-18 20:40 ` Eloitor
2022-07-18 20:51 ` [PR PATCH] [Updated] " Eloitor
2022-07-18 21:04 ` Eloitor
2022-07-18 21:06 ` [PR REVIEW] " Eloitor
2022-07-19 5:30 ` [PR PATCH] [Updated] " Eloitor
2022-07-19 5:33 ` Eloitor
2022-07-19 5:36 ` Eloitor
2022-07-19 5:40 ` Eloitor
2022-07-19 5:43 ` Eloitor
2022-07-19 5:49 ` Eloitor
2022-07-19 6:39 ` Eloitor
2022-07-19 6:42 ` Eloitor
2022-07-19 9:56 ` paper42
2022-07-19 10:35 ` [PR PATCH] [Updated] " Eloitor
2022-07-19 10:36 ` Eloitor
2022-07-19 10:44 ` [PR PATCH] [Updated] " Eloitor
2022-07-19 10:46 ` Eloitor
2022-07-19 10:49 ` [PR PATCH] [Updated] " Eloitor
2022-07-19 10:50 ` Eloitor
2022-07-19 16:47 ` paper42
2022-07-20 5:18 ` [PR PATCH] [Updated] " Eloitor
2022-07-20 5:35 ` Eloitor
2022-07-20 5:44 ` Eloitor [this message]
2022-07-20 5:44 ` Eloitor
2022-08-01 6:27 ` [PR PATCH] [Updated] " Eloitor
2022-08-01 6:29 ` Eloitor
2022-08-01 7:20 ` Eloitor
2022-08-01 7:22 ` Eloitor
2022-08-01 7:28 ` Eloitor
2022-09-23 21:51 ` [PR PATCH] [Closed]: " Eloitor
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=20220720054425.YO1CwExr0NTV_9c8Iz7GmywwLAFtpXMEcbyB6vwbE3s@z \
--to=eloitor@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).