[MacPorts] #49180: dbus-python34, dbus-python35: fails to parse if corresponding python port is not installed
#49180: dbus-python34, dbus-python35: fails to parse if corresponding python port is not installed --------------------------+------------------------- Reporter: ryandesign@… | Owner: mcalhoun@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Keywords: | Port: dbus-python --------------------------+------------------------- The dbus-python34 and dbus-python35 subports fail to parse if corresponding python port is not installed: {{{ sent 64 bytes received 117 bytes 120.67 bytes/sec total size is 512 speedup is 2.83 Creating port index in /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports Warning: failed to open old entry for devel/dbus-python, making a new one Adding port devel/dbus-python Adding subport dbus-python27 Adding subport dbus-python34 Failed to parse file devel/dbus-python/Portfile with subport 'dbus- python35': couldn't execute "/opt/local/bin/python3.5-config": no such file or directory Adding subport dbus-python24 Adding subport dbus-python25 Adding subport dbus-python26 Adding subport dbus-python31 Adding subport dbus-python32 Adding subport dbus-python33 Total number of ports parsed: 10 Ports successfully parsed: 9 Ports failed: 1 Up-to-date ports skipped: 24823 }}} This may be what is killing the portindex (#49179). -- Ticket URL: <https://trac.macports.org/ticket/49180> MacPorts <https://www.macports.org/> Ports system for OS X
#49180: dbus-python34, dbus-python35: fails to parse if corresponding python port is not installed ---------------------------+------------------------ Reporter: ryandesign@… | Owner: mcalhoun@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: dbus-python | ---------------------------+------------------------ Comment (by mcalhoun@…): The change was introduced in r140992.[[BR]] Hopefully, r141026 fixes the problem. -- Ticket URL: <https://trac.macports.org/ticket/49180#comment:1> MacPorts <https://www.macports.org/> Ports system for OS X
#49180: dbus-python34, dbus-python35: fails to parse if corresponding python port is not installed ---------------------------+------------------------ Reporter: ryandesign@… | Owner: mcalhoun@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: dbus-python | ---------------------------+------------------------ Comment (by jmr@…): Why not find out the abiflags and append to configure.args in a pre- configure block? -- Ticket URL: <https://trac.macports.org/ticket/49180#comment:2> MacPorts <https://www.macports.org/> Ports system for OS X
#49180: dbus-python34, dbus-python35: fails to parse if corresponding python port is not installed ---------------------------+------------------------ Reporter: ryandesign@… | Owner: mcalhoun@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: fixed | Keywords: Port: dbus-python | ---------------------------+------------------------ Changes (by jmr@…): * status: new => closed * resolution: => fixed Comment: The parse failure is fixed in any case. -- Ticket URL: <https://trac.macports.org/ticket/49180#comment:3> MacPorts <https://www.macports.org/> Ports system for OS X
#49180: dbus-python34, dbus-python35: fails to parse if corresponding python port is not installed ---------------------------+------------------------ Reporter: ryandesign@… | Owner: mcalhoun@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: fixed | Keywords: Port: dbus-python | ---------------------------+------------------------ Comment (by michaelld@…): Replying to [comment:2 jmr@…]:
Why not find out the abiflags and append to configure.args in a pre- configure block?
That's what I ended up doing, in r141038. Took a little effort because the variables defined outside the "subport" scope are no longer valid inside the "pre-configure" scope. Had to define them in the "subport" scope & then use in the "pre-configure" scope. Gotta love TCL! -- Ticket URL: <https://trac.macports.org/ticket/49180#comment:4> MacPorts <https://www.macports.org/> Ports system for OS X
participants (1)
-
MacPorts