No coreutils on macOS 14.2?

[jbaraban]

$ sudo port install coreutils
Error: Port coreutils not found

Why is coreutils not available on Sonoma arm64? How can I fix this? Thanks.

[ryandesign (Ryan Carsten Schmidt)]

Run sudo port -d selfupdate

[jbaraban]

Thanks - I still get the same error message after running that. Looking at its output though, I notice this:

Failed to parse file sysutils/coreutils/Portfile: invalid command name "<<<<<<<"

When I comment out 3 lines in the Portfile that have invalid characters like that (they look like git comments), then everything works.

[jmroot (Joshua Root)]

Are you using a git checkout for your ports tree?

[jbaraban]

How would I check, and should I be? I see some indications for rsync and some for git when I poke around in /opt/local.

I think I am - here is the end of sources.conf:

#rsync://rsync.macports.org/release/tarballs/ports.tar [default]                                                                                                                                            
file:///opt/local/var/macports/sources/github.com/macports/macports-ports/ [default]

If I recall correctly, that change was part of getting wine working on arm64. I'll try to go back to the default rsync.

Replying to jmroot:

Are you using a git checkout for your ports tree?

[ryandesign (Ryan Carsten Schmidt)]

Replying to jbaraban:

Thanks - I still get the same error message after running that. Looking at its output though, I notice this:

Failed to parse file sysutils/coreutils/Portfile: invalid command name "<<<<<<<"

If you were using rsync, the entire ports tree would get replaced every time you sudo port sync (or selfupdate), and our copy of that Portfile​ doesn't contain those characters, so since you have a different copy of that file you must be using git, and you must have edited that file manually to make some change, and when you later ran sudo port sync (or selfupdate) again the incoming changes conflicted with what you had changed before, resulting in git inserting those conflict markers for you to help you see what changes you made vs what changes we made. The solution, if you want to continue using git, is to edit that file and either resolve the conflict or just revert the changes you made to that file.

[jbaraban]

Thanks - either way seems to work for coreutils, so this ticket seems resolved. At the moment I can't check that everything works properly because I'm stuck on the gobject-introspection issue (#68909) - any chance they're related?

Replying to ryandesign:

Replying to jbaraban:

Thanks - I still get the same error message after running that. Looking at its output though, I notice this:

Failed to parse file sysutils/coreutils/Portfile: invalid command name "<<<<<<<"

If you were using rsync, the entire ports tree would get replaced every time you sudo port sync (or selfupdate), and our copy of that Portfile​ doesn't contain those characters, so since you have a different copy of that file you must be using git, and you must have edited that file manually to make some change, and when you later ran sudo port sync (or selfupdate) again the incoming changes conflicted with what you had changed before, resulting in git inserting those conflict markers for you to help you see what changes you made vs what changes we made. The solution, if you want to continue using git, is to edit that file and either resolve the conflict or just revert the changes you made to that file.

[ryandesign (Ryan Carsten Schmidt)]

Replying to jbaraban:

I'm stuck on the gobject-introspection issue (#68909) - any chance they're related?

Sure: if you modified your glib2 Portfile to be an older version, that would explain why MacPorts wouldn't install a newer version.