From: Cyril Roelandt <tipecaml@gmail.com>
To: guix-devel@gnu.org
Subject: Re: pypi URL change
Date: Mon, 25 Apr 2016 00:26:25 +0200 [thread overview]
Message-ID: <571D4811.4050300@gmail.com> (raw)
In-Reply-To: <571C754A.1050506@gmail.com>
On 04/24/2016 09:27 AM, Ben Woodcroft wrote:
> Hi,
>
> Today I tried using pypi-url to autogenerate a package that was only
> released today. Unfortunately, it seems that the URL scheme has changed
> and I was unable to download, though I believe this only affects newly
> released package versions. I found this on the nix mailing list:
> http://comments.gmane.org/gmane.linux.distributions.nixos/20158
>
>> So, previously PyPI used URLs like :
>> //packages//{python version}/{name[0]}/{name}/{filename}
>>
>> Now it uses:
>> //packages//{hash[:2]}/{hash[2:4]}/{hash[4:]}/{filename}
>> Where hash is blake2b(file_content, digest_size=32).hexdigest().lower()
>
> Is there a blake2b implemented in Guile? In the meantime, the URL will have to be specified manually: 'guix import pypi ...' provides the correct and updated URL.
>
The URL should always be correct, because the pypi importer can detect
whether the URL build by pypi-uri is wrong (see make-pypi-sexp).
Now, in order to handle this new pattern, maybe pypi-uri should:
1) try to compute the "new URI"
2) issue a "curl --head $uri" using some Guile magic
3) return the URI or compute the "old URI" depending on 2)
WDYT?
Cyril.
next prev parent reply other threads:[~2016-04-24 22:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-24 7:27 pypi URL change Ben Woodcroft
2016-04-24 22:26 ` Cyril Roelandt [this message]
2016-04-24 23:21 ` Ben Woodcroft
2016-04-25 0:13 ` Cyril Roelandt
2016-04-25 1:44 ` Ben Woodcroft
2016-04-25 7:54 ` Ludovic Courtès
2016-04-26 11:46 ` Ben Woodcroft
2016-04-27 12:25 ` Ludovic Courtès
2016-06-17 22:33 ` Ben Woodcroft
2016-06-17 22:33 ` [PATCH 1/3] build-system/python: Add pypi-origin Ben Woodcroft
2016-06-17 22:33 ` [PATCH 2/3] gnu: Add python-screed Ben Woodcroft
2016-06-25 17:44 ` Leo Famulari
2016-06-17 22:33 ` [PATCH 3/3] not a real patch Ben Woodcroft
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=571D4811.4050300@gmail.com \
--to=tipecaml@gmail.com \
--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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).