Opened 11 years ago
Closed 10 years ago
#38797 closed defect (duplicate)
avahi: Incompatible with Mountain Lion?
| Reported by: | Crosmatron | Owned by: | pixilla (Bradley Giesbrecht) |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 2.1.3 |
| Keywords: | Cc: | cooljeanius (Eric Gallager), nonstop.server@… | |
| Port: | avahi |
Description
I get the following error when trying to install avahi on Mountain Lion.
:error:activate org.macports.activate for port avahi returned: launchctl: Couldn't stat("/System/Library/LaunchDaemons/com.apple.DirectoryServicesLocal.plist"): No such file or directory
Attachments (2)
Change History (10)
Changed 11 years ago by Crosmatron
comment:1 Changed 11 years ago by ryandesign (Ryan Carsten Schmidt)
| Owner: | changed from macports-tickets@… to pixilla@… |
|---|---|
| Port: | avahi added |
comment:2 follow-up: 5 Changed 11 years ago by jmroot (Joshua Root)
That's the addgroup/adduser calls failing. While the port should switch to setting add_users instead, that still just runs dscl behind the scenes. Does dscl work when you run it manually? Does that launchctl message mean that dscl has failed, or should we be ignoring it? Why is it even trying to load com.apple.DirectoryServicesLocal.plist, which doesn't exist because it has been replaced by opendirectoryd?
comment:3 Changed 11 years ago by jmroot (Joshua Root)
Are you running in single user mode or something? If so, does it work when you run port using sudo from an admin account instead?
comment:4 Changed 11 years ago by Crosmatron
Pauls-MacBook:~ crosma$ sudo dscl
launchctl: Couldn't stat("/System/Library/LaunchDaemons/com.apple.DirectoryServicesLocal.plist"): No such file or directory
nothing found to load
Entering interactive mode... (type "help" for commands)
>
I'm not running in single user mode. Running without sudo produces the same message. I am using an admin account.
comment:5 Changed 11 years ago by cooljeanius (Eric Gallager)
Replying to jmr@…:
Does that launchctl message mean that dscl has failed, or should we be ignoring it?
We can ignore the message, just a sec, let me find the citation...
Edit: here we go: https://discussions.apple.com/thread/4819128 (the original Apple support page is dead so we'll just have to go with my discussion thread posted in response to it instead...)
comment:8 Changed 10 years ago by neverpanic (Clemens Lang)
| Resolution: | → duplicate |
|---|---|
| Status: | new → closed |
Duplicate of #42347, will be fixed in 2.3.
main.log