Opened 6 years ago

Closed 6 years ago

#58046 closed defect (invalid)

dbus @1.12.2_0+universal any operation ends in error "invalid command name "startupitems""

Reported by: chtonic Owned by: MarcusCalhoun-Lopez (Marcus Calhoun-Lopez)
Priority: Normal Milestone:
Component: ports Version: 2.4.0
Keywords: Cc:
Port: dbus

Description

The simplest operation I could this to (after failed builds for ffmpeg) is:

port -d info dbus
DEBUG: Changing to port directory: /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/devel/dbus
DEBUG: OS darwin/16.7.0 (Mac OS X 10.12) arch i386
DEBUG: Reading variant descriptions from /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/_resources/port1.0/variant_descriptions.conf
DEBUG: Sourcing PortGroup muniversal 1.0 from /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/_resources/port1.0/group/muniversal-1.0.tcl
DEBUG: invalid command name "startupitems"
    while executing
"startupitems        name        dbus-system \
                    location    LaunchDaemons \
                    uniquename  ${daemon_uniquename} \
 ..."
    (file "Portfile" line 57)
    invoked from within
"source Portfile"
    invoked from within
"$workername eval {source Portfile}"
    (procedure "mportopen" line 41)
    invoked from within
"mportopen $porturl [array get options] [array get merged_variations]"
Error: Unable to open port: invalid command name "startupitems"

But because of this I also can't get the maintainer. The version and variants I got through running 'port installed'.

Change History (3)

comment:1 Changed 6 years ago by MarcusCalhoun-Lopez (Marcus Calhoun-Lopez)

Owner: set to MarcusCalhoun-Lopez
Status: newaccepted

startupitems is a relatively recent addition to MacPorts.
I suspect you are running an old version of MacPorts.

port version should read 2.5.4.
If not, please run sudo port selfupdate and try again.

If this works, please report back so we can close this ticket.

comment:2 Changed 6 years ago by chtonic

Indeed, I found this out a little bit later. But I was puzzled why my software wasn't up to date. MacPorts works so well that one tends to forget that MacPorts is a package that needs to be installed or updated separately by way of the normal MacOS X mechanism.

Or does it, seeing as you recommend 'sudo port selfupdate'. But this only updated the ports definitions, not the port install.

Can be closed.

Last edited 6 years ago by chtonic (previous) (diff)

comment:3 Changed 6 years ago by MarcusCalhoun-Lopez (Marcus Calhoun-Lopez)

Resolution: invalid
Status: acceptedclosed

I am glad things are working now.

Note: See TracTickets for help on using tickets.