Opened 10 years ago

Closed 10 years ago

#42318 closed defect (fixed)

py-petsc4py @3.4: fails to parse for subport py33

Reported by: petrrr Owned by: seanfarley (Sean Farley)
Priority: Normal Milestone:
Component: ports Version:
Keywords: Cc: seanfarley (Sean Farley)
Port: py-petsc4py

Description

I observe the following parsing problem after a sudo port -v selfupdateon 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.

Change History (6)

comment:1 Changed 10 years ago by seanfarley (Sean Farley)

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

comment:2 Changed 10 years ago by seanfarley (Sean Farley)

Does anyone have an idea of why this breaks for only the python33 subport?

comment:3 Changed 10 years ago by seanfarley (Sean Farley)

It turns out that petsc4py doesn't support python 3 at all so I removed those subports in r116601. Can you try selfupdate again?

comment:4 Changed 10 years ago by petrrr

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.

comment:5 Changed 10 years ago by petrrr

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

comment:6 Changed 10 years ago by seanfarley (Sean Farley)

Resolution: fixed
Status: assignedclosed

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.

Note: See TracTickets for help on using tickets.