[MacPorts] #42623: py-numba fails checksum if mirrors fail through to github

[MacPorts]

#42623: py-numba fails checksum if mirrors fail through to github
------------------------------+--------------------------------
  Reporter:  russell.jones@…  |      Owner:  macports-tickets@…
      Type:  enhancement      |     Status:  closed
  Priority:  Low              |  Milestone:
 Component:  ports            |    Version:  2.2.1
Resolution:  invalid          |   Keywords:
      Port:  py-numba         |
------------------------------+--------------------------------
Changes (by ryandesign@…):

 * status:  new => closed
 * cc: russell.jones@… (removed)
 * cc: ryandesign@… (added)
 * resolution:   => invalid


Comment:

 Replying to [ticket:42623 russell.jones@…]:
 > Sometimes py*-numba fails to build because the file is obtained from
 https://github.com/numba/numba/tarball/0.12.0 (for example) rather than
 from any of the mirrors with the macports distfiles.

 In other words, a [wiki:PortfileRecipes#stealth-updates stealth update]
 may have occurred. Normally in these cases, we would want to compare the
 old (from distfiles.macports.org) and new (from github.com) tarballs to
 see what changed. However, I am not able to find the old tarball on any
 MacPorts distfiles mirror. One possible reason for this is if the checksum
 did not match, even when that version was originally committed to
 MacPorts. This could happen if the developers released 0.12.0, the
 maintainer downloaded it and began working on the update, and before the
 maintainer finished the update and committed it to MacPorts, the
 developers stealth-updated 0.12.0.


 Replying to [comment:2 russell.jones@…]:
 > I think the checksum is wrong for the github tar ball because it's
 dynamically generated, BTW. But I could be missing something.

 Even though the tarballs are dynamically generated, they are generated
 identically, so this is not a problem unless something else has changed.


 In any case, the port was already updated to 0.12.1 a week ago so it's a
 moot point. selfupdate and use that version.

 You mentioned "those who want to run old versions deliberately". We don't
 support that. Certainly, if you're following the
 [wiki:howto/InstallingOlderPort instructions for installing an older
 port], then you're manually downloading an old historical portfile from
 our repository; no amount of commits to the current version of the
 portfile will change the historical portfiles. So users who deliberately
 use historical portfiles have to be aware that these kinds of problems can
 occur, and have to be prepared to do some legwork to work around such
 problems.


 Note that, as the reporter, you don't need to add your address to the Cc
 field; you'll get Cc'd automatically.

-- 
Ticket URL: <https://trac.macports.org/ticket/42623#comment:3>
MacPorts <http://www.macports.org/>
Ports system for OS X