#47246 closed update (fixed)
py-pmw update to 2.0.0
Reported by: | howarth.at.macports@… | Owned by: | macports-tickets@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.3.3 |
Keywords: | Cc: | petrrr, kurthindenburg (Kurt Hindenburg) | |
Port: | py-pmw |
Description (last modified by ryandesign (Ryan Carsten Schmidt))
The attached Portfile and pmw2.patch provides a py33-pmw2 and py34-pmw2 package for the Pmw 2.0.0 release with additional fixes from upstream hg repository for 2.0.1 to eliminate demos and tests failures. These can be checked with...
cd /opt/local/Library/Frameworks/Python.framework/Versions/3.4/lib/python3.4/site-packages/Pmw/Pmw_2_0_0/demos python3.3 All.py
and
cd /opt/local/Library/Frameworks/Python.framework/Versions/3.4/lib/python3.4/site-packages/Pmw/Pmw_2_0_0/tests python3.3 All.py
Attachments (3)
Change History (17)
Changed 10 years ago by howarth.at.macports@…
comment:1 Changed 10 years ago by ryandesign (Ryan Carsten Schmidt)
Description: | modified (diff) |
---|
Changed 9 years ago by howarth.at.macports@…
Portfile for py-pmw2 package with python35 variant added
comment:3 Changed 9 years ago by howarth.at.macports@…
I can't edit the title of this ticket but the ticket now is changed to a py-pmw update instead of a new package. The appended Portfile should be ignored and the Portfile.diff and pmw2.diff patch used instead.
comment:4 Changed 9 years ago by howarth.at.macports@…
Note that the 2.0.1 release upstream is an alpha and has test suite regressions compared to 2.0.0 so it should be avoided.
comment:5 Changed 9 years ago by petrrr
Please to not add new py33 subports anymore. We are in the process of deprecating all python ports for < py27 and < py34.
Changed 9 years ago by howarth.at.macports@…
Attachment: | Portfile.diff added |
---|
Portfile.diff to build the python2 and python3 sources from the 2.0.0 source bundle for the python 27, 34 and 35 variants
comment:8 Changed 9 years ago by kurthindenburg (Kurt Hindenburg)
Port: | py-pmw added; py-pmw2 removed |
---|---|
Summary: | py-pmw2 2.0.0 → py-pmw update to 2.0.0 |
Type: | submission → update |
Since the patch is so large, we could just use the hg tree to grab the latest version
comment:9 Changed 9 years ago by howarth.at.macports@…
Last I looked upstream and the 2.0.1 alpha release both introduced other test suite regressions (hence the cherry picked patches from upstream). Also, using hg seems like a lot of extra dependencies for hg compared to a relatively small patch.
comment:10 Changed 9 years ago by howarth.at.macports@…
Note that the patch contains...
https://sourceforge.net/p/pmw/hg/ci/d533281b5eb93351b6cffb79f43cd9eed784dfbb/ https://sourceforge.net/p/pmw/hg/ci/30ff9121b5970790228bfc06a51f21bcd0655cda/ https://sourceforge.net/p/pmw/hg/ci/cb158ee7c2dcb8fe4ec0140cdc3bf3de3a58a36b/ https://sourceforge.net/p/pmw/hg/ci/48399a529da1874f0310201cfc3015b951eacd32/
comment:11 Changed 9 years ago by howarth.at.macports@…
Note that the mercurial repo of pmw is very new and I assume the regressions I see in 2.0.1 alpha compared to 2.0.0 with the above patches applied reflect some issue in the migration of the pmw files into hg. Hence my avoidance of 2.0.1 alpha or hg in favor of just applying the bug fixes to 2.0.0.
comment:12 Changed 9 years ago by howarth.at.macports@…
Also note that https://sourceforge.net/p/pmw/hg/ci/13f476c40ca1c47a8ba2184aff0ca1e18a613604/ occurred on the same day as the 2.0.0 release. So it is unclear if the 2.0.0 release was actually generated out of the hg repository or that after the 2.0.0 release, the hg repository was created using the files from the pre-existing 2.0.0 release.
comment:13 Changed 9 years ago by kurthindenburg (Kurt Hindenburg)
Resolution: | → fixed |
---|---|
Status: | new → closed |
Thanks done r146816 - let us know of any issues
comment:14 Changed 9 years ago by kurthindenburg (Kurt Hindenburg)
and r146819 as I forgot to include all my changes
patch with back port of fixes from hg repository of 2.0.1