Opened 7 years ago
Closed 7 years ago
#54253 closed update (fixed)
py-astropy @1.3.2: update to 1.3.3
Reported by: | Schamschula (Marius Schamschula) | Owned by: | robitaille@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | |
Keywords: | haspatch | Cc: | Deil.Christoph@… |
Port: | py-astropy |
Description
py-astropy has been updated to version 1.3.3.
Attachments (2)
Change History (7)
Changed 7 years ago by Schamschula (Marius Schamschula)
Attachment: | Portfile-py27-astropy.diff added |
---|
comment:1 follow-up: 3 Changed 7 years ago by cdeil (Christoph Deil)
Changed 7 years ago by Schamschula (Marius Schamschula)
Attachment: | Portfile-py-astropy.diff added |
---|
Correct patch file with checksums
comment:2 Changed 7 years ago by Schamschula (Marius Schamschula)
Oops. Somehow my update build script did not re-run diff after the checksums were manually updated.
comment:3 Changed 7 years ago by Schamschula (Marius Schamschula)
Replying to cdeil:
OK to update. Needs an update of checksums, no?
What should I do here as maintainer without the commit bit? Does it help if I send a pull request on Github, or can you just as easily commit the update directly?
I can commit it for you.
comment:4 Changed 7 years ago by cdeil (Christoph Deil)
I have tested the Portfile-py-astropy.diff
patch locally with Python 2.7:
sudo port install subport=py27-astropy PYTHONPATH=/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages /opt/local/bin/python2.7 -c 'import astropy; astropy.test()'
and with Python 3.5:
sudo port install subport=py35-astropy PYTHONPATH=/opt/local/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/site-packages /opt/local/bin/python3.5 -c 'import astropy; astropy.test()'
All tests pass, i.e. everything looks good.
Marius - Please go ahead and commit the update. Thank you!
comment:5 Changed 7 years ago by Schamschula (Marius Schamschula)
Resolution: | → fixed |
---|---|
Status: | new → closed |
Note: See
TracTickets for help on using
tickets.
OK to update. Needs an update of checksums, no?
What should I do here as maintainer without the commit bit? Does it help if I send a pull request on Github, or can you just as easily commit the update directly?