all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: Christopher Allan Webber <cwebber@dustycloud.org>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: [PATCH] gnu: python-flask: Update to 0.11.1.
Date: Wed, 22 Jun 2016 14:50:36 -0400	[thread overview]
Message-ID: <20160622185036.GA13667@jasmine> (raw)
In-Reply-To: <87inx1t6l6.fsf@dustycloud.org>

On Wed, Jun 22, 2016 at 01:35:17PM -0500, Christopher Allan Webber wrote:
> Note that the old URL scheme no longer seemed to work.
> 
> I'm not thrilled by the new URL "scheme".  It seems like more work to
> update with each version bump.  I'm not sure what the solution is?

Please review Ben's 'pypi-origin' patch :)

http://lists.gnu.org/archive/html/guix-devel/2016-06/msg00724.html

>      (source (origin
>                (method url-fetch)
> -              (uri (pypi-uri "Flask" version))
> +              (uri
> +               (string-append
> +                "https://pypi.python.org/packages/55/8a/"
> +                "78e165d30f0c8bb5d57c429a30ee5749825ed461ad6c959688872643ffb3/"
> +                "Flask-0.11.1.tar.gz"))

In the meantime, I think it's best to keep the hash on its own line, to
reduce noise in the commit log if we do more updates in this format.

"55/8a/78e1..."

> -       ("python-werkzeug" ,python-werkzeug)))
> +       ("python-werkzeug" ,python-werkzeug)
> +       ("python-click" ,python-click)))

Remember to mention the new dependency in the commit message!

  reply	other threads:[~2016-06-22 18:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-22 18:35 [PATCH] gnu: python-flask: Update to 0.11.1 Christopher Allan Webber
2016-06-22 18:50 ` Leo Famulari [this message]
2016-06-22 22:20   ` Christopher Allan Webber
2016-06-23 11:39   ` [PATCH]: guix: python-build-system: Change pypi-uri to use https://pypi.io 宋文武
2016-06-23 23:51     ` Ben Woodcroft
2016-06-24 12:14     ` Ludovic Courtès

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=20160622185036.GA13667@jasmine \
    --to=leo@famulari.name \
    --cc=cwebber@dustycloud.org \
    --cc=guix-devel@gnu.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.
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.