py27-pymc @2.3_2 +gcc48 Checksum error

[jeisch@…]

--->  Fetching distfiles for py27-pymc
--->  Attempting to fetch pymc-2.3.tar.gz from https://github.com/pymc-devs/pymc/tarball/2.3
--->  Verifying checksums for py27-pymc
Error: Checksum (rmd160) mismatch for pymc-2.3.tar.gz
Error: Checksum (sha256) mismatch for pymc-2.3.tar.gz
Error: org.macports.checksum for port py27-pymc returned: Unable to verify file checksums

From the port file:

checksums           rmd160  8f810928bd2edf8fbd857eb08530e81d9a661028 \
                    sha256  b4ce92cfffcdebfb4e4083bae5113b019b8ef2c33f3fd020
d2818cc3a9a4b53d

The log file suggests that the checksums should be:

checksums           rmd160  c832b5eb35a4e67b14743e4a9274cd5ae9fef21f \
                    sha256  775d164826c55f369906dc2cd82309326deb1ac4e61dd6c144f471293a0a3931

[Russell-Jones-OxPhys (Russell Jones)]

Cc Me!

[Russell-Jones-OxPhys (Russell Jones)]

At ​https://pypi.python.org/pypi/pymc/ the md5 sum given for pymc-2.3.tar.gz (source) is 03678068b552eecb16fc7aded39d125a

However,

wget --no-check-certificate https://github.com/pymc-devs/pymc/tarball/2.3/pymc-2.3.tar.gz
-> pymc-2.3.tar.gz
wget --no-check-certificate https://github.com/pymc-devs/pymc/tarball/2.3/
-> index.html
(in browser, https://github.com/pymc-devs/pymc/tarball/2.3 -> pymc-devs-pymc-v2.3-10-g0f87c8e.tar.gz)

$ md5 index.html pymc-2.3.tar.gz  pymc-devs-pymc-v2.3-10-g0f87c8e.tar.gz
MD5 (index.html) = f93ad949ab92061c535b089e9c486586
MD5 (pymc-2.3.tar.gz) = f93ad949ab92061c535b089e9c486586
MD5 (pymc-devs-pymc-v2.3-10-g0f87c8e.tar.gz) = f93ad949ab92061c535b089e9c486586

[dbevans (David B. Evans)]

Seems to be an ongoing problem. From svn log:

------------------------------------------------------------------------
r113141 | g5pw@macports.org | 2013-11-10 12:04:17 -0800 (Sun, 10 Nov 2013) | 4 lines

python/py-pymc:
  checksums changed again, for no apparent reason.
  Treating as silent upgrade.

------------------------------------------------------------------------
r112765 | g5pw@macports.org | 2013-10-31 02:45:51 -0700 (Thu, 31 Oct 2013) | 4 lines

python/py-pymc:
  Strange checksum mismatch, doing a stealth update just to be sure (#35241)
  maintainer override, port broken

[dbevans (David B. Evans)]

As shown at ​https://github.com/pymc-devs/pymc/releases, the correct tag for this release is 'v2.3' not '2.3'.

Attached is a proposed patch that adds the 'v' tag_prefix to the github.setup command line. I've also added a md5 checksum line for comparison with that from the pypi site.

Unfortunately they don't match.

e49de8920609727c13de42f3101454fe from ​https://github.com/pymc-devs/pymc/tarball/v2.3/pymc-2.3.tar.gz
03678068b552eecb16fc7aded39d125a from ​https://pypi.python.org/packages/source/p/pymc/pymc-2.3.tar.gz

[dbevans (David B. Evans)]

Proposed patch for Portfile

[dbevans (David B. Evans)]

After manually downloading the two separate versions from their respective web sites, verifying their individual checksums and performing a diff -ur on the unpacked files it appears they are identical with the exception of the name of the top level archive directory.

github uses pymc-devs-pymc-46f8f6a
pypi   uses py-2.3

Satisfied that nothing funny is going on and build is successful for me, fix committed as per patch in r115527.

[g5pw (Aljaž Srebrnič)]

As per the ​MacPorts Guide:

Using the ${revision} variable in the dist_subdir definition isn't usually a good idea, because the revision is supposed to allow the portfile author to offer the user an upgrade that is unrelated to the upstream software version.

Otherwise, the commit looks OK to me, thanks!