unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: emacs-repository-{version|branch} on Windows
Date: Fri, 04 Nov 2022 20:51:33 +0200	[thread overview]
Message-ID: <83v8nu4kp6.fsf@gnu.org> (raw)
In-Reply-To: <CAAeL0SRxiByrjFrwKi+-EzTvAAbd0Ugvp-xmXkyLy1=s-ak1XA@mail.gmail.com> (message from Juanma Barranquero on Fri, 4 Nov 2022 19:24:11 +0100)

> From: Juanma Barranquero <lekktu@gmail.com>
> Date: Fri, 4 Nov 2022 19:24:11 +0100
> 
> I've been struggling with these two variables being nil on my build, and finally I modified
> emacs-repository-version-git to write a log file and see what was happening:
> 
> fatal: detected dubious ownership in repository at 'D:/Devel/emacs/repo/trunk'
> 'D:/Devel/emacs/repo/trunk/.git' is owned by:
>         'S-1-5-32-544'
> but the current user is:
>         'S-1-5-21-...' [my account's SID]
> To add an exception for this directory, call:
> 
>         git config --global --add safe.directory D:/Devel/emacs/repo/trunk

Why is this an Emacs problem?  It's a typical Windows messup, whereby
some directories are "owned" by the Administrators _group_ instead of
by your user.  Just fire up the File Explorer, and make it change the
owner of wherever you keep your Git repository to your user,
recursively.

> One of these cases where there's a directory whose owner is the Administrators group. Changing the
> ownership of .git/ to the current user fixed the problem.

Which is what you should do.  In general, make every directory where
you or your applications create files to be owned by your user, and
make sure they will inherit the ownership to any subdirectories.

> Is this usual? Should it be mentioned on some README? (Or perhaps it is already and I did miss it.)

I see no reason to decide that this has anything to do with Emacs.
That's a slippery slope, especially given that no one is lately
interested in maintaining the Windows port of Emacs.



  parent reply	other threads:[~2022-11-04 18:51 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-04 18:24 emacs-repository-{version|branch} on Windows Juanma Barranquero
2022-11-04 18:36 ` Juanma Barranquero
2022-11-04 18:51 ` Eli Zaretskii [this message]
2022-11-04 18:58   ` Juanma Barranquero
2022-11-04 19:28   ` Stefan Monnier
2022-11-04 20:08     ` Juanma Barranquero
2022-11-04 20:29       ` Eli Zaretskii
2022-11-04 20:42         ` Juanma Barranquero
2022-11-04 20:47           ` Stefan Monnier
2022-11-04 20:56             ` Eli Zaretskii
2022-11-04 21:09               ` Juanma Barranquero
2022-11-04 21:20               ` Stefan Monnier
2022-11-05  6:24                 ` Eli Zaretskii
2022-11-05 11:43                   ` Juanma Barranquero
2022-11-05 12:36                     ` Eli Zaretskii
2022-11-05 13:20                       ` Juanma Barranquero
2022-11-05 15:19                     ` Stefan Monnier

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: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83v8nu4kp6.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=lekktu@gmail.com \
    /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://git.savannah.gnu.org/cgit/emacs.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).