From: David Hillman <davidahillman@gmail.com>
To: git@vger.kernel.org
Subject: bug: Commit throws fatal ownership error without explanation
Date: Tue, 11 Jun 2024 15:52:49 -0500 [thread overview]
Message-ID: <28659397-293f-4706-a0ac-75298673ee30@gmail.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)
Attempted to commit a change.
What did you expect to happen? (Expected behavior)
Commit should have been applied.
What happened instead? (Actual behavior)
Git threw a fatal error with the following malformed message,
which fails to identify the file(s) with problematic ownership.
"[master 3e58b1d] Updated sans comment
1 file changed, 3 insertions(+)
fatal: detected dubious ownership in repository at '/srv/git/projects.git'
To add an exception for this directory, call:
git config --global --add safe.directory /srv/git/projects.git
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists. "
What's different between what you expected and what actually happened?
If git throws a fatal error due to improper file ownership, it
must report the offending file(s) so the user can correct the issue. It
is never acceptable to die and leave behind a mystery as to the cause.
At an absolute minimum, the error message must report the
expected ownership that was not found, not the vague and useless
characterization of "dubious ownership". "Dubious ownership" might be
fine for a warning, but is unacceptable for a fatal error. In other
words, this error message should be as follows:
"fatal: The following files have incorrect ownership.
file /srv/git/projects.git/example/path/to/file/one.pl is owned by
user123541, should be user434892
... [ repeat as necessary ]
"
Anything else you want to add:
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.43.0
cpu: x86_64
no commit associated with this build
sizeof-long: 8
sizeof-size_t: 8
shell-path: /bin/sh
uname: Linux 6.8.0-31-generic #31-Ubuntu SMP PREEMPT_DYNAMIC Sat Apr 20
00:40:06 UTC 2024 x86_64
compiler info: gnuc: 13.2
libc info: glibc: 2.39
$SHELL (typically, interactive shell): /bin/bash
[Enabled Hooks]
not run from a git repository - no hooks to show
--
David Hillman
next reply other threads:[~2024-06-11 20:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-11 20:52 David Hillman [this message]
2024-06-11 21:13 ` Commit throws fatal ownership error without explanation rsbecker
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=28659397-293f-4706-a0ac-75298673ee30@gmail.com \
--to=davidahillman@gmail.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 NNTP newsgroup(s).