From: Albert Lv <albert.lv-us-icloud@outlook.com>
To: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Git Bug Report: 'scalar register' command failed at Mac m1
Date: Sun, 6 Nov 2022 13:56:44 +0000 [thread overview]
Message-ID: <PSBPR01MB3541FDC2CB117051A01A9418FA3D9@PSBPR01MB3541.apcprd01.prod.exchangelabs.com> (raw)
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
next reply other threads:[~2022-11-06 13:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-06 13:56 Albert Lv [this message]
2022-11-07 2:51 ` Git Bug Report: 'scalar register' command failed at Mac m1 Derrick Stolee
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=PSBPR01MB3541FDC2CB117051A01A9418FA3D9@PSBPR01MB3541.apcprd01.prod.exchangelabs.com \
--to=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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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).