From: Derrick Stolee <derrickstolee@github.com>
To: Albert Lv <albert.lv-us-icloud@outlook.com>,
"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Git Bug Report: 'scalar register' command failed at Mac m1
Date: Sun, 6 Nov 2022 21:51:55 -0500 [thread overview]
Message-ID: <42804b53-7035-1ba0-3076-2207e63681b7@github.com> (raw)
In-Reply-To: <PSBPR01MB3541FDC2CB117051A01A9418FA3D9@PSBPR01MB3541.apcprd01.prod.exchangelabs.com>
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
next prev parent reply other threads:[~2022-11-07 2:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-06 13:56 Git Bug Report: 'scalar register' command failed at Mac m1 Albert Lv
2022-11-07 2:51 ` Derrick Stolee [this message]
2022-11-07 14:53 ` 回复: " Albert Lv
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=42804b53-7035-1ba0-3076-2207e63681b7@github.com \
--to=derrickstolee@github.com \
--cc=albert.lv-us-icloud@outlook.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).