All of lore.kernel.org
 help / color / mirror / Atom feed
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 22:00:23 +0000	[thread overview]
Message-ID: <bug-9706-163-8oFTRdRjiE@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-9706-163@https.bugs.busybox.net/>

https://bugs.busybox.net/show_bug.cgi?id=9706

Arnout Vandecappelle <arnout@mind.be> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |INVALID

--- Comment #1 from Arnout Vandecappelle <arnout@mind.be> ---
When bumping the package, SUPERVISOR_SITE should change from the current 

http://pypi.python.org/packages/source/s/supervisor

to

https://pypi.python.org/packages/44/80/d28047d120bfcc8158b4e41127706731ee6a3419c661e0a858fb0e7c4b2d

but it's not unusual for the _SITE to change when the version is bumped.

I don't see how this is a bug, so I'm closing as invalid. If you disagree, feel
free to reopen.

PS if you do bump the package, don't forget to send the patch to the Buildroot
mailing list for upstream inclusion.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  reply	other threads:[~2017-03-03 22:00 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 ` bugzilla at busybox.net [this message]
2017-03-03 22:20   ` [Buildroot] [Bug 9706] " Yegor Yefremov
2017-03-03 22:26 ` bugzilla at busybox.net
2017-03-03 23:12 ` bugzilla at busybox.net
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-8oFTRdRjiE@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.