From: jason1987d <jason1987d@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: python3-dnsrecon: update to 1.1.5.
Date: Sun, 26 Nov 2023 21:49:28 +0100 [thread overview]
Message-ID: <20231126204928.i91bNpLS7_l2KWxkno-Zik6HqYlX6VLhMJS7tRsDgvw@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-47317@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 782 bytes --]
New comment by jason1987d on void-packages repository
https://github.com/void-linux/void-packages/pull/47317#issuecomment-1826892872
Comment:
> When I say to pull the upstream patch, I literally mean
>
> ```
> curl -L -o requirements.patch https://github.com/darkoperator/dnsrecon/commit/d0507ef2499d9cc3c3354e1c0632cfc5898a9bf3.patch
> ```
>
> Using the upstream patch verbatim provides a "chain of custody" with headers that show the upstream commit hash and original author.
I did that, and it leads to...
```
=> python3-dnsrecon-1.1.5_1: patching: requirements.patch.
1 out of 1 hunk FAILED -- saving rejects to file requirements.txt.rej
=> ERROR: python3-dnsrecon-1.1.5_1: do-patch_00-patches: 'patch -s ${_args} < "${_patch}" 2> /dev/null' exited with 1
```
next prev parent reply other threads:[~2023-11-26 20:49 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-19 20:00 [PR PATCH] Python3 dnsrecon jason1987d
2023-11-19 20:10 ` [PR REVIEW] [WIP] python3-dnsrecon: update to 1.1.5 ahesford
2023-11-19 20:23 ` jason1987d
2023-11-19 20:25 ` jason1987d
2023-11-19 20:48 ` ahesford
2023-11-19 21:34 ` jason1987d
2023-11-19 21:59 ` ahesford
2023-11-19 22:02 ` [PR PATCH] [Updated] " jason1987d
2023-11-19 22:04 ` jason1987d
2023-11-19 22:04 ` jason1987d
2023-11-19 23:10 ` ahesford
2023-11-24 2:49 ` jason1987d
2023-11-26 4:31 ` [PR PATCH] [Updated] " jason1987d
2023-11-26 5:42 ` jason1987d
2023-11-26 15:35 ` jason1987d
2023-11-26 19:30 ` ahesford
2023-11-26 20:49 ` jason1987d [this message]
2023-11-27 1:08 ` ahesford
2023-11-27 1:14 ` [PR PATCH] [Closed]: " ahesford
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=20231126204928.i91bNpLS7_l2KWxkno-Zik6HqYlX6VLhMJS7tRsDgvw@z \
--to=jason1987d@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).