Git Bug Report: 'scalar register' command failed at Mac m1

Git Bug Report: 'scalar register' command failed at Mac m1

[Albert Lv]

Thank you for filling out a Git bug report!
Please answer the following questions to help us understand your issue.

What did you do before the bug happened? (Steps to reproduce your issue)
1. First I run 'scalar register' to register current git repo'.
2. Because previous command report 'Permission denied', so I run 'sudo scalar register'.

What did you expect to happen? (Expected behavior)
Scalar successfully registered

What happened instead? (Actual behavior)
Command report:
fatal: failed to bootstrap service /Users/albert/Library/LaunchAgents/org.git-scm.git.hourly.plist
error: could not turn on maintenance

What's different between what you expected and what actually happened?
Command failed

Anything else you want to add:
I am using mac m1 and macOS 13.0

Please review the rest of the bug report below.
You can delete any lines you don't wish to share.


[System Info]
git version:
git version 2.38.1.dirty
cpu: arm64
built from commit: d5b41391a472dcf9486055fd5b8517f893e88daf
sizeof-long: 8
sizeof-size_t: 8
shell-path: /bin/sh
feature: fsmonitor--daemon
uname: Darwin 22.1.0 Darwin Kernel Version 22.1.0: Sun Oct  9 20:14:30 PDT 2022; root:xnu-8792.41.9~2/RELEASE_ARM64_T8103 arm64
compiler info: clang: 12.0.5 (clang-1205.0.22.9)
libc info: no libc information available
$SHELL (typically, interactive shell): /bin/zsh

Re: Git Bug Report: 'scalar register' command failed at Mac m1

[Derrick Stolee]

On 11/6/22 8:56 AM, Albert Lv wrote:
> Thank you for filling out a Git bug report!
> Please answer the following questions to help us understand your issue.
> 
> What did you do before the bug happened? (Steps to reproduce your issue)
> 1. First I run 'scalar register' to register current git repo'.
> 2. Because previous command report 'Permission denied', so I run 'sudo scalar register'.
> 
> What did you expect to happen? (Expected behavior)
> Scalar successfully registered
> 
> What happened instead? (Actual behavior)
> Command report:
> fatal: failed to bootstrap service /Users/albert/Library/LaunchAgents/org.git-scm.git.hourly.plist
> error: could not turn on maintenance

Thanks for the report, Albert!

I suspect that you get the same problem with
"git maintenance start" which is the underlying
command that "scalar register" is running at this
point of failure.

The "~/Library/LaunchAgents/" should be owned by
your user, allowing this to work without needing
to "sudo". However, if your permissions on that
directory have changed, then the "sudo" will be
necessary. Could you double-check your permissions
by running "ls -al ~/Library"?

Thanks,
-Stolee

回复: Git Bug Report: 'scalar register' command failed at Mac m1

[Albert Lv]

Thanks a lot, Derrick!

"ls -al ~/Library" showed that "~/Library/LaunchAgents/" was owned by root user. Then I changed the owner of the "~/Library/LaunchAgents/" to my user. After that, "scalar register" successfully worked.

Thanks,
-Albert

________________________________________
发件人: Derrick Stolee <derrickstolee@github.com>
发送时间: 2022年11月7日 10:51
收件人: Albert Lv; git@vger.kernel.org
主题: Re: Git Bug Report: 'scalar register' command failed at Mac m1

On 11/6/22 8:56 AM, Albert Lv wrote:
> Thank you for filling out a Git bug report!
> Please answer the following questions to help us understand your issue.
>
> What did you do before the bug happened? (Steps to reproduce your issue)
> 1. First I run 'scalar register' to register current git repo'.
> 2. Because previous command report 'Permission denied', so I run 'sudo scalar register'.
>
> What did you expect to happen? (Expected behavior)
> Scalar successfully registered
>
> What happened instead? (Actual behavior)
> Command report:
> fatal: failed to bootstrap service /Users/albert/Library/LaunchAgents/org.git-scm.git.hourly.plist
> error: could not turn on maintenance

Thanks for the report, Albert!

I suspect that you get the same problem with
"git maintenance start" which is the underlying
command that "scalar register" is running at this
point of failure.

The "~/Library/LaunchAgents/" should be owned by
your user, allowing this to work without needing
to "sudo". However, if your permissions on that
directory have changed, then the "sudo" will be
necessary. Could you double-check your permissions
by running "ls -al ~/Library"?

Thanks,
-Stolee