Unable to install into system: creating LaunchAgent directory: mkdir ~/Library/LaunchAgents: not a directory
mur-wtag opened this issue · comments
Trying to install puma-dev
but it's not installing and throwing this error:
% puma-dev -install
2020/07/13 10:38:34 Existing valid puma-dev CA keypair found. Assuming previously trusted.
* Use '/usr/local/bin/puma-dev' as the location of puma-dev
2020/07/13 10:38:34 Unable to install into system: creating LaunchAgent directory: mkdir /Users/rony/Library/LaunchAgents: not a directory
To install I've followed these steps:
% brew install puma/puma/puma-dev
Updating Homebrew...
==> Installing puma-dev from puma/puma
==> Downloading https://github.com/puma/puma-dev/releases/download/v0.14/puma-dev-0.14-darwin-amd64.zip
Already downloaded: /Users/rony/Library/Caches/Homebrew/downloads/862fa79e193e4e9d086cc3a64fd6b6521751e6dbd81c1a15350f063c9b8a7f20--puma-dev-0.14-darwin-amd64.zip
==> Caveats
Setup dev domains:
sudo puma-dev -setup
Install puma-dev as a launchd agent (required for port 80 usage):
puma-dev -install
==> Summary
🍺 /usr/local/Cellar/puma-dev/0.14: 3 files, 10.8MB, built in 3 seconds
% sudo puma-dev -setup
Password:
* Configuring /etc/resolver to be owned by rony
* Changing '/etc/resolver/localhost' to be owned by rony
* Changing '/etc/resolver/test' to be owned by rony
% puma-dev -install
2020/07/13 10:34:22 Existing valid puma-dev CA keypair found. Assuming previously trusted.
* Use '/usr/local/bin/puma-dev' as the location of puma-dev
2020/07/13 10:34:22 Unable to install into system: creating LaunchAgent directory: mkdir /Users/rony/Library/LaunchAgents: not a directory
Am I missing something?
# test that it's a directory
[ -d /Users/rony/Library/LaunchAgents ] || echo "/Users/rony/Library/LaunchAgents is not a directory!"
Please ensure that /Users/rony/Library/LaunchAgents
is a directory. It's possible that your filesystem is in a state that puma-dev doesn't account for.
If the directory doesn't exist, try manually creating the /Users/rony/Library/LaunchAgents
directory, ensuring that it has correct ownership and permissions (i.e. rony:staff
with 755
)
yeah it worked by creating this directory manually. thanks a lot!