From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 9706] Can't download newer revisions of package from PyPI
Date: Fri, 03 Mar 2017 23:12:02 +0000 [thread overview]
Message-ID: <bug-9706-163-Xd8rm5tJIK@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-9706-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=9706
--- Comment #3 from J. Eric Mason <jem@kamama.com> ---
Semantically buildroot could (I won't go as far to say should yet) be using the
simple repository protocol to find download URLs and hashes for a package
generically https://www.python.org/dev/peps/pep-0503/ as the URLs could change
over time. If I have the bandwidth I'll see if I can propose a changelist to do
this resolution so this wouldn't be a problem in the future.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2017-03-03 23:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-03 19:44 [Buildroot] [Bug 9706] New: Can't download newer revisions of package from PyPI bugzilla at busybox.net
2017-03-03 22:00 ` [Buildroot] [Bug 9706] " bugzilla at busybox.net
2017-03-03 22:20 ` Yegor Yefremov
2017-03-03 22:26 ` bugzilla at busybox.net
2017-03-03 23:12 ` bugzilla at busybox.net [this message]
2017-03-04 10:44 ` bugzilla at busybox.net
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=bug-9706-163-Xd8rm5tJIK@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@busybox.net \
/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 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.