py-appscript looks broken on a number of macOS versions

[barracuda156]

See: ​https://ports.macports.org/port/py-appscript/details

[jmroot (Joshua Root)]

Looks like successful builds on all platforms to me. Why do you think it's broken?

[ryandesign (Ryan Carsten Schmidt)]

Like all py-* ports, py-appscript is a stub port which doesn't install anything, so the python portgroup sets it to supported_archs noarch and platforms any so it only needs to be built successfully on one buildbot builder; the others won't attempt it if there was a successful build on any of them. The failures you see shown on that details page are for older versions of the port, from a time when it failed to build. Josh fixed it three days ago. The ports web page should really clear out details for older versions of a port when a new version appears, and it should be made aware of supported_archs noarch and platforms any, but at present it does not know about those things so the health indicators can be misleading.

[barracuda156]

Replying to ryandesign:

Like all py-* ports, py-appscript is a stub port which doesn't install anything, so the python portgroup sets it to supported_archs noarch and platforms any so it only needs to be built successfully on one buildbot builder; the others won't attempt it if there was a successful build on any of them. The failures you see shown on that details page are for older versions of the port, from a time when it failed to build. Josh fixed it three days ago. The ports web page should really clear out details for older versions of a port when a new version appears, and it should be made aware of supported_archs noarch and platforms any, but at present it does not know about those things so the health indicators can be misleading.

Got it, thank you for a clarification. Issue can be closed then.

[jmroot (Joshua Root)]

Webapp issue is ​https://github.com/macports/macports-webapp/issues/135