From: "Ludovic Courtès" <ludovic.courtes@inria.fr>
To: 49083@debbugs.gnu.org
Subject: bug#49083: ‘guix import pypi’ fails in the absence of “sdist” releases
Date: Fri, 18 Jun 2021 09:33:13 +0200 [thread overview]
Message-ID: <87czsjmxty.fsf@inria.fr> (raw)
Hi,
For some packages we get this:
--8<---------------cut here---------------start------------->8---
$ guix import pypi jaxlib
guix import: error: no source release for pypi package jaxlib 0.1.67
--8<---------------cut here---------------end--------------->8---
and indeed, there’s no “sdist” (source distribution), only
“bdist_wheel” (.whl files).
Nevertheless, should the importer do something smarter here? The
metadata at <https://pypi.org/pypi/jaxlib/json> doesn’t contain info
about the source repository (though it contains the home page at
github.com). Would it make sense to build from a .whl file or does this
necessarily include generated code and other byproducts?
Thanks,
Ludo’.
next reply other threads:[~2021-06-18 7:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-18 7:33 Ludovic Courtès [this message]
2021-06-18 8:56 ` bug#49083: ‘guix import pypi’ fails in the absence of “sdist” releases Leo Prikler
2021-06-20 21:03 ` Ludovic Courtès
2021-06-22 18:58 ` Maxim Cournoyer
2022-02-02 17:46 ` Ludovic Courtès
2022-02-02 21:45 ` Maxim Cournoyer
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=87czsjmxty.fsf@inria.fr \
--to=ludovic.courtes@inria.fr \
--cc=49083@debbugs.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).