Azure pipeline failing due to parse error
ryandesign at macports.org
Tue Jul 6 11:26:29 UTC 2021
On Jul 5, 2021, at 00:45, Manoj Karthick wrote:
> Hi! I was updating the antibody port, PR: https://github.com/macports/macports-ports/pull/11516 and the Azure Pipeline check seems to be failing during portindex due to an error parsing an unrelated port.
> See: https://dev.azure.com/macports/macports-ports/_build/results?buildId=15295&view=logs&j=ca395085-040a-526b-2ce8-bdc85f692774&t=bc2d1ad2-204c-5a7b-d5d8-da0852fe1639
> Creating port index in /Users/runner/work/1/s/ports
> Adding port devel/cmake
> Adding subport cmake-devel
> Adding port devel/fcat
> Adding port devel/onefetch
> Adding port lang/gcc10
> Adding subport libgcc10
> Failed to parse file mail/MailHog/Portfile: invalid command name "startupitem.user"
> Adding port sysutils/antibody
> Adding port sysutils/just
> Adding port textproc/mdcat
> Adding port textproc/tcat
startupitem.user and startupitem.group were added in MacPorts 2.7.0.
More information about the macports-dev