From: Oleg Pykhalov <go.wigust@gmail.com>
To: Leo Famulari <leo@famulari.name>
Cc: 30856@debbugs.gnu.org, 30856-done@debbugs.gnu.org
Subject: [bug#30856] [PATCH] gnu: python-ptyprocess: Update source URL.
Date: Tue, 20 Mar 2018 21:47:23 +0300 [thread overview]
Message-ID: <87tvtad1ok.fsf@gmail.com> (raw)
In-Reply-To: <20180319205958.GB20036@jasmine.lan> (Leo Famulari's message of "Mon, 19 Mar 2018 16:59:58 -0400")
[-- Attachment #1: Type: text/plain, Size: 1172 bytes --]
Leo Famulari <leo@famulari.name> writes:
> On Mon, Mar 19, 2018 at 06:29:31PM +0300, Oleg Pykhalov wrote:
>> * gnu/packages/python.scm (python-ptyprocess)[origin](source): Update URL.
>> ---
>> gnu/packages/python.scm | 5 +++--
>> 1 file changed, 3 insertions(+), 2 deletions(-)
>>
>> diff --git a/gnu/packages/python.scm b/gnu/packages/python.scm
>> index 05d339060..5915561ff 100644
>> --- a/gnu/packages/python.scm
>> +++ b/gnu/packages/python.scm
>> @@ -5619,8 +5619,9 @@ markdown_py is also provided to convert Markdown files to HTML.")
>> (origin
>> (method url-fetch)
>> (uri (string-append
>> - "https://pypi.python.org/packages/source/p/ptyprocess/ptyprocess-"
>> - version ".tar.gz"))
>> + "https://pypi.python.org/packages/51/83/"
>> + "5d07dc35534640b06f9d9f1a1d2bc2513fb9cc7595a1b0e28ae5477056ce/"
>> + "ptyprocess-" version ".tar.gz"))
>
> Can it use pypi-uri? That way we wouldn't have to update this hash for
> each new version.
It can. Thank you!
Pushed as 8c4bd04c86cc43252b2f9473f398717970b77234
I'll close the bug report.
Oleg.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
prev parent reply other threads:[~2018-03-20 18:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-19 15:29 [bug#30856] [PATCH] gnu: python-ptyprocess: Update source URL Oleg Pykhalov
2018-03-19 20:59 ` Leo Famulari
2018-03-20 18:47 ` Oleg Pykhalov [this message]
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=87tvtad1ok.fsf@gmail.com \
--to=go.wigust@gmail.com \
--cc=30856-done@debbugs.gnu.org \
--cc=30856@debbugs.gnu.org \
--cc=leo@famulari.name \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.