Opened 9 years ago

Closed 9 years ago

Last modified 9 years ago

#49336 closed enhancement (fixed)

py-gmpy2 @2.0.7: Add py35 subport

Reported by: mndavidoff (Monte Davidoff) Owned by: petrrr
Priority: Normal Milestone:
Component: ports Version: 2.3.4
Keywords: haspatch maintainer Cc:
Port: py-gmpy2

Description

The attached patch adds the py35-gmpy2 subport.

Attachments (2)

Portfile.diff (661 bytes) - added by mndavidoff (Monte Davidoff) 9 years ago.
Portfile.py-graveyard.diff (559 bytes) - added by mndavidoff (Monte Davidoff) 9 years ago.

Download all attachments as: .zip

Change History (9)

comment:1 Changed 9 years ago by petrrr

It would be great, if you could also fix the livecheck and retire the obsolete py26 and py33 subports. There seem to be no dependents for these anymore.

petr% port livecheck py-gmpy2
py-gmpy2 seems to have been updated (port version: 2.0.7, new version: 2.0.3)

comment:2 Changed 9 years ago by petrrr

Owner: changed from macports-tickets@… to petr@…
Status: newassigned

Changed 9 years ago by mndavidoff (Monte Davidoff)

Attachment: Portfile.diff added

Changed 9 years ago by mndavidoff (Monte Davidoff)

Attachment: Portfile.py-graveyard.diff added

comment:3 Changed 9 years ago by mndavidoff (Monte Davidoff)

Thanks for catching that. I've attached updated diffs to fix livecheck and retire the py26 and py33 subports. The py-graveyard diff also includes changes to retire py26-gmpy and py33-gmpy (#49335).

comment:4 in reply to:  1 Changed 9 years ago by mndavidoff (Monte Davidoff)

Replying to petr@…:

It would be great, if you could also fix the livecheck and retire the obsolete py26 and py33 subports.

The requested changes are attached. Do you want anything else from me before committing these changes and #49335?

comment:5 Changed 9 years ago by petrrr

Looks okay, just had not the occasion to look at it and commit them. Sorry!

comment:6 Changed 9 years ago by petrrr

Resolution: fixed
Status: assignedclosed

Committed in r142375.

See comment in #49335. Please provide one single diff per ticket. Thanks!

comment:7 Changed 9 years ago by mndavidoff (Monte Davidoff)

Thank you for committing the changes. In the future, I will do as you advise: keep changes for each ticket separate and combine changes for one ticket into a single diff. I did not know I could put changes for multiple files into a single diff.

Note: See TracTickets for help on using tickets.