[MacPorts] #42318: py-petsc4py @3.4: fails to parse for subport py33
#42318: py-petsc4py @3.4: fails to parse for subport py33 -----------------------------+-------------------------------- Reporter: Peter.Danecek@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: py-petsc4py -----------------------------+-------------------------------- I observe the following parsing problem after a `sudo port -v selfupdate`on my system (OS X 10.8.5). {{{ Creating port index in /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports Warning: failed to open old entry for python/py-petsc4py, making a new one Adding port python/py-petsc4py Adding subport py26-petsc4py Adding subport py27-petsc4py Adding subport py32-petsc4py Error: Install py33-mpi4py +mpich Failed to parse file python/py-petsc4py/Portfile with subport 'py33-petsc4py': py33-mpi4py +mpich not installed Total number of ports parsed: 5 Ports successfully parsed: 4 Ports failed: 1 Up-to-date ports skipped: 18097 }}} The port `py33-petsc4py` seems not to be available then: {{{ petr% port search petsc4py py-petsc4py @3.4 (python, math) PETSc for Python - Python bindings for PETSc py26-petsc4py @3.4 (python, math) PETSc for Python - Python bindings for PETSc py27-petsc4py @3.4 (python, math) PETSc for Python - Python bindings for PETSc py32-petsc4py @3.4 (python, math) PETSc for Python - Python bindings for PETSc Found 4 ports. }}} -- Ticket URL: <https://trac.macports.org/ticket/42318> MacPorts <http://www.macports.org/> Ports system for OS X
#42318: py-petsc4py @3.4: fails to parse for subport py33 ------------------------------+---------------------- Reporter: Peter.Danecek@… | Owner: sean@… Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: py-petsc4py | ------------------------------+---------------------- Changes (by sean@…): * status: new => assigned * owner: macports-tickets@… => sean@… -- Ticket URL: <https://trac.macports.org/ticket/42318#comment:1> MacPorts <http://www.macports.org/> Ports system for OS X
#42318: py-petsc4py @3.4: fails to parse for subport py33 ------------------------------+---------------------- Reporter: Peter.Danecek@… | Owner: sean@… Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: py-petsc4py | ------------------------------+---------------------- Comment (by sean@…): Does anyone have an idea of why this breaks for only the python33 subport? -- Ticket URL: <https://trac.macports.org/ticket/42318#comment:2> MacPorts <http://www.macports.org/> Ports system for OS X
#42318: py-petsc4py @3.4: fails to parse for subport py33 ------------------------------+---------------------- Reporter: Peter.Danecek@… | Owner: sean@… Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: py-petsc4py | ------------------------------+---------------------- Comment (by sean@…): It turns out that petsc4py doesn't support python 3 at all so I removed those subports in r116601. Can you try selfupdate again? -- Ticket URL: <https://trac.macports.org/ticket/42318#comment:3> MacPorts <http://www.macports.org/> Ports system for OS X
#42318: py-petsc4py @3.4: fails to parse for subport py33 ------------------------------+---------------------- Reporter: Peter.Danecek@… | Owner: sean@… Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: py-petsc4py | ------------------------------+---------------------- Comment (by Peter.Danecek@…): At the moment I still cannot confirm that the problem disappeared -- the change has not yet propagated to the tarball -- but I would assume it is highly probable. In any case, the fact that Python 3 is not supported, does not explain why the parsing of the TCL Portfile for one single subport fails here. At most missing Python 3 support would break installation or runtime. Will report back later, when the update becomes available. -- Ticket URL: <https://trac.macports.org/ticket/42318#comment:4> MacPorts <http://www.macports.org/> Ports system for OS X
#42318: py-petsc4py @3.4: fails to parse for subport py33 ------------------------------+---------------------- Reporter: Peter.Danecek@… | Owner: sean@… Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: py-petsc4py | ------------------------------+---------------------- Comment (by Peter.Danecek@…): Okay the update is now available and parsing works now as expected: {{{ Creating port index in /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports Adding port python/py-petsc4py Adding subport py26-petsc4py Adding subport py27-petsc4py Total number of ports parsed: 3 Ports successfully parsed: 3 Ports failed: 0 Up-to-date ports skipped: 18093 ---> MacPorts base is already the latest version }}} -- Ticket URL: <https://trac.macports.org/ticket/42318#comment:5> MacPorts <http://www.macports.org/> Ports system for OS X
#42318: py-petsc4py @3.4: fails to parse for subport py33 ------------------------------+-------------------- Reporter: Peter.Danecek@… | Owner: sean@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: py-petsc4py | ------------------------------+-------------------- Changes (by sean@…): * status: assigned => closed * resolution: => fixed Comment: I also don't know why this failed for python 3. If someone does figure it out, please respond to this ticket. For now, I'm going to close it. -- Ticket URL: <https://trac.macports.org/ticket/42318#comment:6> MacPorts <http://www.macports.org/> Ports system for OS X
participants (1)
-
MacPorts