#37334: NEW: py-obspy @0.8.3 ------------------------------+-------------------------------- Reporter: Peter.Danecek@… | Owner: macports-tickets@… Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: py-obspy | ------------------------------+-------------------------------- Comment (by ryandesign@…): Instead of deleting py-obspy-core immediately as suggested in comment:ticket:35165:2, we should mark it "`replaced_by py-obspy`" for one year, to help users upgrading. We'll have to manually handle replacing each of its subports with the corresponding subport of py-obspy. "`fetch.type standard`" is not needed because that's the default. "`fetch.ignore_sslcert yes`" is not needed since your master_sites is not an https URL. "`depends_lib-append`" can take multiple ports at once, e.g.: {{{ depends_lib-append port:py${python.version}-numpy \ port:py${python.version}-scipy \ port:py${python.version}-lxml \ port:py${python.version}-suds \ port:py${python.version}-sqlalchemy }}} -- Ticket URL: <https://trac.macports.org/ticket/37334#comment:2> MacPorts <http://www.macports.org/> Ports system for Mac OS

#37334: NEW: py-obspy @0.8.3 ------------------------------+-------------------------- Reporter: Peter.Danecek@… | Owner: ryandesign@… Type: submission | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: py-obspy | ------------------------------+-------------------------- Changes (by ryandesign@…): * owner: macports-tickets@… => ryandesign@… * status: new => assigned Comment: Thanks. Installing py*-obspy fails when the corresponding py*-obspy-core is already installed. So we should employ the "deactivate hack". -- Ticket URL: <https://trac.macports.org/ticket/37334#comment:4> MacPorts <http://www.macports.org/> Ports system for Mac OS

#37334: NEW: py-obspy @0.8.3 ------------------------------+-------------------------- Reporter: Peter.Danecek@… | Owner: ryandesign@… Type: submission | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: py-obspy | ------------------------------+-------------------------- Comment (by Peter.Danecek@…): Here the hook I would add to handle deactivation. However, I have some doubt on how to handle the super-/subport deactivation. In case the port was installed via its superport (py-obspy-core) it should be deactivated as well, so I added the respective line. But this may cause an error if this py-obspy-core is not installed. How to handle this cleanly? Any suggestion? Thanks! {{{ # hook to deactivate old installations of py-obspy-core ("deactivate hack") pre-activate { if {[file exists ${prefix}/bin/obspy-runtests-2.5 && ![catch {set vers [lindex [registry_active py26-obspy-core] 0]}] && [rpm-vercomp [lindex $vers 1] 0.8.0] < 0} { registry_deactivate py-obspy-core "" [list ports_nodepcheck 1] registry_deactivate py25-obspy-core "" [list ports_nodepcheck 1] } if {[file exists ${prefix}/bin/obspy-runtests-2.6 && ![catch {set vers [lindex [registry_active py26-obspy-core] 0]}] && [rpm-vercomp [lindex $vers 1] 0.8.0] < 0} { registry_deactivate py-obspy-core "" [list ports_nodepcheck 1] registry_deactivate py26-obspy-core "" [list ports_nodepcheck 1] } if {[file exists ${prefix}/bin/obspy-runtests-2.7 && ![catch {set vers [lindex [registry_active py26-obspy-core] 0]}] && [rpm-vercomp [lindex $vers 1] 0.8.0] < 0} { registry_deactivate py-obspy-core "" [list ports_nodepcheck 1] registry_deactivate py27-obspy-core "" [list ports_nodepcheck 1] } } }}} -- Ticket URL: <https://trac.macports.org/ticket/37334#comment:6> MacPorts <http://www.macports.org/> Ports system for Mac OS

#37334: NEW: py-obspy @0.8.3 ------------------------------+-------------------------- Reporter: Peter.Danecek@… | Owner: ryandesign@… Type: submission | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: py-obspy | ------------------------------+-------------------------- Comment (by Peter.Danecek@…): Replying to [comment:7 jmr@…]:

You shouldn't need the deactivate hack if the other port is replaced_by this one. source:tags/release_2_1_2/base/src/registry2.0/portimage.tcl#L461

Sorry, I am not sure if I am getting this right. Is this a new feature of the base system (version 2.1.2)? I understood that the hack would be necessary to correctly replace the former port, see also comment:2. But maybe I did the testing against the earlier version? -- Ticket URL: <https://trac.macports.org/ticket/37334#comment:8> MacPorts <http://www.macports.org/> Ports system for Mac OS

#37334: NEW: py-obspy @0.8.3 ------------------------------+-------------------------- Reporter: Peter.Danecek@… | Owner: ryandesign@… Type: submission | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: py-obspy | ------------------------------+-------------------------- Changes (by ryandesign@…): * status: assigned => closed * resolution: => fixed Comment: Committed in r101443 with these changes: * removed deactivate hack * removed "supported_archs noarch" because this port ''does'' install architecture-specific files * "rmd160" was misspelled "rdm160" * disabled universal variant because some of the dependencies are not universal Marked py-obspy-core replaced_by py-obspy in r101445. -- Ticket URL: <https://trac.macports.org/ticket/37334#comment:10> MacPorts <http://www.macports.org/> Ports system for Mac OS