pymc: please update pymc 2.2, which has python 3 support

[cdeil (Christoph Deil)]

Could you please update pymc to the current version 2.2

The page ​http://code.google.com/p/pymc/ no longer exists, the project is now here: ​https://github.com/pymc-devs/pymc

Also pymc now supports python 3, so there should be a py32-pymc port. python 25 is no longer supported and should be removed. Indeed it doesn't build for me on Lion (the python 2.6 and 2.7 variants work fine): ​https://gist.github.com/3135538

You should use the unified python portgroup so that only one portfile is needed and not one per python version.

I think the many different variants for gcc versions can be dropped? (But I didn't try which fortran / c compilers do work.)

[cdeil (Christoph Deil)]

Btw., you can test if pymc works by running

python2.6 -c 'import pymc; pymc.test()'
python2.7 -c 'import pymc; pymc.test()'
python3.2 -c 'import pymc; pymc.test()'

With the current pymc 2.0 some tests fail with python 2.6 and 2.7: ​https://gist.github.com/3135561

If there are still failures after upgrading to pymc 2.2 I'd be happy to investigate and file bug reports at ​https://github.com/pymc-devs/pymc/issues if they are new.

[ryandesign (Ryan Carsten Schmidt)]

Presumably the gcc variants should not be dropped since that is the standard way that we deal with ports that require a fortran compiler. Newer gcc variants (gcc46 gcc47) should be added. One could consider removing some of the older gcc variants, but at least gcc45 should be retained since that is the default gcc compiler version that we have chosen across MacPorts at this time.

[g5pw (Aljaž Srebrnič)]

Since this is long past maintainer timeout, I tried updating it to v2.2. I implemented the shiny new ​FortranReceipe. Unfortunately the compilation fails for now, I can't seem to set the FFLAGS without it being overwritten somewhere.

[g5pw (Aljaž Srebrnič)]

Cc Me!

[g5pw (Aljaž Srebrnič)]

Ok, I got it working and it builds fine, but it fails on runtime. I opened an ​issue onGitHub.

[g5pw (Aljaž Srebrnič)]

Waiting for upstream release of pyMC 2.3 which solves some issues.

[g5pw (Aljaž Srebrnič)]

Updated in r112663.

[cdeil (Christoph Deil)]

Thanks for updating!

I get a checksum error now!? ​https://gist.github.com/cdeil/7229144

[g5pw (Aljaž Srebrnič)]

Works for me and for the build bots. See ​FAQ.

[cdeil (Christoph Deil)]

I downloaded and checked again and I still get this checksum which is different from the one in the Portfile:

$ shasum -a 256 /opt/local/var/macports/distfiles/py-pymc/pymc-2.3.tar.gz
23b5a94fc282f6cece096962549cb972cc6c9760a0aa69dc49867bfe580f5688  /opt/local/var/macports/distfiles/py-pymc/pymc-2.3.tar.gz

I think there might have been a stealth upgrade 10 days ago:

• ​https://github.com/pymc-devs/pymc/releases/tag/v2.3
• ​https://github.com/pymc-devs/pymc/commit/46f8f6a784e668612c2448f536a1a4b41f93035a

Can someone please share a link to the latest build on the buildbot?

In case it's more than 10 days ago, can someone please re-trigger the build or check manually that the checksum really has changed?

Thanks!

[g5pw (Aljaž Srebrnič)]

Oh, sorry for the confusion. Yes, 10 days ago the 2.3 was officially released. The portfile I attached to this ticked is thus outdated, but I already commited the correct one in the MacPorts tree. If you tested the attached portfile in the past, you may have the old distfile, try a port clean --all py*-pymc and then port install py33-pymc.

[g5pw (Aljaž Srebrnič)]

Disregard this comment. Apparently, one cannot delete comments once submitted.

[cdeil (Christoph Deil)]

Aargh ... why does this work for you but I can't make it work?

Currently you have

sha256  506455fd0a4f27db4448fcf8343ffa60d1c16a1f2819c947edf52f0fe2f4070d

in the Portfile: ​https://trac.macports.org/browser/trunk/dports/python/py-pymc/Portfile#L30

As you can see above this is not the sha256 I get.

I tried port clean --all py*-pymc and manually deleting the Portfile and tar ball to make sure I don't have an old version.

Not sure what else I can try at this point.

Did you clean and re-download the tar ball and check the sha256?

[g5pw (Aljaž Srebrnič)]

Ok, now it fails for me too. Interesting. I don't know what happened, as I commited the portfile on 29/10/2013. I also tried cleaning all and redownloading after your comment:8.

Anyways, I did a stealth update in r112765, it should work now. Thanks for the patience!

[cdeil (Christoph Deil)]

Thanks!

I've mentioned this possible stealth upgrade problem upstream: ​https://github.com/pymc-devs/pymc/issues/332#issuecomment-27536361

The Python 3 version shows unit test failures which I've also mentioned upstream: ​https://github.com/pymc-devs/pymc/issues/332#issuecomment-27536006

[cdeil (Christoph Deil)]

I think there was another stealth update yesterday:

:info:checksum --->  Checksumming pymc-2.3.tar.gz
:error:checksum Checksum (rmd160) mismatch for pymc-2.3.tar.gz
:info:checksum Portfile checksum: pymc-2.3.tar.gz rmd160 91d3afc6197d683fcc556fcacc114c3b8639ae4e
:info:checksum Distfile checksum: pymc-2.3.tar.gz rmd160 8f810928bd2edf8fbd857eb08530e81d9a661028
:error:checksum Checksum (sha256) mismatch for pymc-2.3.tar.gz
:info:checksum Portfile checksum: pymc-2.3.tar.gz sha256 23b5a94fc282f6cece096962549cb972cc6c9760a0aa69dc49867bfe580f5688
:info:checksum Distfile checksum: pymc-2.3.tar.gz sha256 b4ce92cfffcdebfb4e4083bae5113b019b8ef2c33f3fd020d2818cc3a9a4b53d
:info:checksum The correct checksum line may be:
:info:checksum checksums           rmd160  8f810928bd2edf8fbd857eb08530e81d9a661028 \
                    sha256  b4ce92cfffcdebfb4e4083bae5113b019b8ef2c33f3fd020d2818cc3a9a4b53d

I've mentioned the issue to the developer here: ​https://github.com/pymc-devs/pymc/issues/332#issuecomment-27619401

[mf2k (Frank Schima)]

In the future, you need to re-open the ticket or file a new one in order to get noticed. Closed tickets tend to get ignored.

[g5pw (Aljaž Srebrnič)]

Yes, I confirm the checksum change. Cannot explain it though. The tag is still on the same commit!

[g5pw (Aljaž Srebrnič)]

Checksums changed in r113141.