[MacPorts] #68905: No coreutils on macOS 14.2?
MacPorts
noreply at macports.org
Sun Dec 17 13:55:21 UTC 2023
#68905: No coreutils on macOS 14.2?
------------------------+--------------------
Reporter: jbaraban | Owner: (none)
Type: defect | Status: new
Priority: Normal | Milestone:
Component: ports | Version:
Resolution: | Keywords:
Port: coreutils |
------------------------+--------------------
Comment (by 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
(https://trac.macports.org/ticket/68909) - any chance they're related?
Replying to [comment:5 ryandesign]:
> Replying to [comment:2 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 [source:macports-
ports/sysutils/coreutils/Portfile 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.
--
Ticket URL: <https://trac.macports.org/ticket/68905#comment:6>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list