Migration should not attempt to use universal variant on 10.14 or later

[umeshksingla (Umesh Singla)]

The migration script (from 10.13 to 10.15) tried to install zlib as zstd's dependency and got the following error:

Error: zlib cannot be installed for the configured universal_archs 'x86_64 i386' because the arch(s) 'i386' are not supported.
Error: Follow https://guide.macports.org/#project.tickets to report a bug.
Error: Processing of port zlib failed

It works without +universal though.

[kencu (Ken)]

so you're suggesting the migration script needs to strip out +universal on 10.14 and up?

[umeshksingla (Umesh Singla)]

I wouldn't be able to answer that. I do not know if +universal has a special significance. From ports.macports.org, it seems as if 10.15 builder is yet to run for this port since the port health status is greyed out.

I found a similar situation with ports xar and openssl.

If someone is able to reproduce the issue, that'd help more.

[kencu (Ken)]

everyone can reproduce it, as +universal is not supported on 10.14 and up...

[ryandesign (Ryan Carsten Schmidt)]

Replying to umeshksingla:

From ports.macports.org, it seems as if 10.15 builder is yet to run for this port since the port health status is greyed out.

zlib is a dependency of a zillion other ports. The 10.15 builder has of course built it. But the status information on the ports web site will only be accurate if the build was attempted on its own. In the case of zlib, and a zillion other ports, the build was not attempted on its own but rather as a dependency of another port, and the ports web site is not able to show you status information for those kinds of builds.

But you cannot use the universal variant with the 10.14 SDK or later. Remove any references to "+universal" from myports.txt before attempting to restore on 10.14 or later. If wiki:Migration doesn't already say to do that, it should be edited to say so.

[umeshksingla (Umesh Singla)]

Thank you for this. Seems like I would need to accommodate it in the GSoC17 migration code.

and the ports web site is not able to show you status information for those kinds of builds.

Ideally it should do this, right?