[MacPorts] #34349: dbus 1.4.20_0 +startupitem activation error
MacPorts
noreply at macports.org
Mon May 7 08:33:59 PDT 2012
#34349: dbus 1.4.20_0 +startupitem activation error
---------------------------------+------------------------------------------
Reporter: blair@… | Owner: mcalhoun@…
Type: defect | Status: reopened
Priority: Normal | Milestone:
Component: ports | Version: 2.0.4
Resolution: | Keywords:
Port: dbus |
---------------------------------+------------------------------------------
Changes (by ryandesign@…):
* cc: ryandesign@…, pixilla@…, Angelo.Graziosi@… (added)
* status: closed => reopened
* resolution: duplicate =>
Comment:
This is not a duplicate; this is a new problem.
Angelo Graziosi sent the following transcript by private email:
{{{
$ sudo port selfupdate
$ sudo port outdated
The following installed ports are outdated:
dbus 1.4.18_0 < 1.4.20_0
$ sudo port upgrade dbus
---> Computing dependencies for dbus
---> Fetching archive for dbus
---> Attempting to fetch dbus-1.4.20_0+startupitem.darwin_11.x86_64.tbz2
from http://packages.macports.org/dbus
---> Attempting to fetch
dbus-1.4.20_0+startupitem.darwin_11.x86_64.tbz2.rmd160 from
http://packages.macports.org/dbus
---> Installing dbus @1.4.20_0+startupitem
---> Cleaning dbus
---> Computing dependencies for dbus
---> Deactivating dbus @1.4.18_0
---> Cleaning dbus
---> Activating dbus @1.4.20_0+startupitem
############################################################################
# Startup items have been generated that will aid in
# starting dbus with launchd. They are disabled
# by default. Execute the following command to start them,
# and to cause them to launch at startup:
#
# sudo launchctl load -w /Library/LaunchDaemons/org.freedesktop.dbus-
system.plist
# launchctl load -w /Library/LaunchAgents/org.freedesktop.dbus-
session.plist
############################################################################
Error: Target org.macports.activate returned: could not set owner for file
"/Library/LaunchAgents/org.freedesktop.dbus-session.plist": no such file
or directory
}}}
This suggests that the problem exists only when users get a pre-compiled
binary, not when building from source (which I verified works fine).
--
Ticket URL: <https://trac.macports.org/ticket/34349#comment:2>
MacPorts <http://www.macports.org/>
Ports system for Mac OS
More information about the macports-tickets
mailing list