#67167 closed defect (fixed)

py310-pyarrow: Error: No such port: py310-tensorflow

Reported by: ryandesign (Ryan Carsten Schmidt) Owned by:
Priority: Normal Milestone:
Component: ports Version: 2.8.1
Keywords: Cc: emcrisostomo (Enrico Maria Crisostomo), essandess (Steve Smith)
Port: py-pyarrow py-tensorflow

Description

https://build.macports.org/builders/jobs-mirror/builds/553066/steps/mirror/logs/stdio

Error: No such port: py310-tensorflow

essandess added py310-pyarrow
emcrisostomo maintains py-tensorflow

Change History (4)

comment:1 Changed 13 months ago by essandess (Steve Smith)

comment:2 in reply to:  1 Changed 13 months ago by ryandesign (Ryan Carsten Schmidt)

Replying to essandess:

Would you please merge

I'm not planning to work on that, but for anyone who is:

https://github.com/macports/macports-ports/pull/15397 and

That's a draft. If it's ready to be merged, mark it as not a draft.

https://github.com/macports/macports-ports/pull/16149 to fix this issue?

That has conflicts that need to be resolved.

comment:3 Changed 13 months ago by essandess (Steve Smith)

I resolved all conflicts and pushed an update to the latest version.

This is an artificial problem for MacPorts because the port specifies the dependency py310-tensorflow only for older macOS versions. Newer versions use Apple's py310-tensorflow-macos, and running TF on an old OS is, at best, and edge case scenario. Furthermore, TF fails to build from source on macOS for several reasons—the PR lists the two I've encountered.

Because the existing, ancient version of TF in MacPorts will neither build nor work if installed anyway, I recommend merging PR 16149 to at least create the port py310-tensorflow. It won't build in the edge cases where it's called, but those edge cases aren't useful for TF.

comment:4 Changed 11 months ago by mascguy (Christopher Nielsen)

Resolution: fixed
Status: newclosed
Note: See TracTickets for help on using tickets.