Opened 2 years ago

Closed 2 years ago

#61514 closed defect (fixed)

ERROR: No value provided for the key: 'commit'. The correct syntax is '--info <key>=<value>'.

Reported by: ryandesign (Ryan Schmidt) Owned by: ryandesign (Ryan Schmidt)
Priority: Normal Milestone:
Component: contrib Version:
Keywords: Cc: admin@…, arjunsalyan (Arjun Salyan)
Port: portindex2json

Description

I deleted the git clone of the ports tree that mprsyncup uses in order to have it check out a new one and create new portindexes from scratch (because #61507).

After it did that, the part of the script that runs portindex2json.tcl happened. It ran the command like this:

/Volumes/RAID/var/tmp/mprsyncup/opt/local/bin/port-tclsh /Volumes/RAID/var/tmp/mprsyncup/release/contrib/portindex2json/portindex2json.tcl PortIndex_darwin_20_arm/PortIndex --info commit=

In other words it did not specify a commit. This caused it to print this error message:

ERROR: No value provided for the key: 'commit'. The correct syntax is '--info <key>=<value>'.

Change History (2)

comment:1 Changed 2 years ago by ryandesign (Ryan Schmidt)

This is happening because the value mprsyncup passes to portindex2json.tcl, $PORTS_NEW_REV, only gets set when updating an existing clone. It does not get set when checking out a new clone.

comment:2 Changed 2 years ago by ryandesign (Ryan Schmidt)

Owner: set to ryandesign
Resolution: fixed
Status: newclosed

In 09b0c78efbac9a6b8d678fe1fefcf0626c2ebe33/macports-infrastructure (master):

mprsyncup: Set PORTS_NEW_REV after cloning

Closes: #61514

Note: See TracTickets for help on using tickets.