Opened 12 years ago

Closed 12 years ago

#37227 closed enhancement (fixed)

py-nibabel: new port following the renaming of py-pynifti

Reported by: seanfarley (Sean Farley) Owned by: jameskyle@…
Priority: Normal Milestone:
Component: ports Version:
Keywords: haspatch Cc:
Port: py25-pynifti py26-pynifti py-nibabel

Description

nibabel is the replacement of pynifti, so these patches add a corresponding port following #37226

Attachments (2)

1.patch (2.9 KB) - added by seanfarley (Sean Farley) 12 years ago.
py-nibabel: new port copied from py-pynifti
2.patch (3.3 KB) - added by seanfarley (Sean Farley) 12 years ago.
py-nibabel: update to 1.3.0

Download all attachments as: .zip

Change History (7)

Changed 12 years ago by seanfarley (Sean Farley)

Attachment: 1.patch added

py-nibabel: new port copied from py-pynifti

Changed 12 years ago by seanfarley (Sean Farley)

Attachment: 2.patch added

py-nibabel: update to 1.3.0

comment:1 Changed 12 years ago by mf2k (Frank Schima)

Port: py-pynifti, py-nibabelpy-pynifti py-nibabel
Type: updateenhancement
Version: 2.1.2

comment:2 Changed 12 years ago by mf2k (Frank Schima)

Port: py25-pynifti py26-pynifti added; py-pynifti removed

comment:3 Changed 12 years ago by mf2k (Frank Schima)

Owner: changed from macports-tickets@… to jameskyle@…

Ports should not be simply deleted. They should first switch to use the obsolete portgroup and use replaced_by py-nibabel. In a year, they can actually be deleted.

comment:4 in reply to:  3 Changed 12 years ago by seanfarley (Sean Farley)

Replying to macsforever2000@…:

Ports should not be simply deleted. They should first switch to use the obsolete portgroup and use replaced_by py-nibabel. In a year, they can actually be deleted.

But I didn't delete the py-pynifti port?

comment:5 Changed 12 years ago by seanfarley (Sean Farley)

Resolution: fixed
Status: newclosed

Fixed in r104370 and r104371

Note: See TracTickets for help on using tickets.