From: "Sebastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: Can't make org-install.el
Date: Sat, 19 May 2012 15:40:36 +0200 [thread overview]
Message-ID: <808vgoqoff.fsf@somewhere.org> (raw)
In-Reply-To: 87obpkxtwv.fsf@Rainer.invalid
Hi Achim,
Achim Gratz wrote:
> Sebastien Vauban writes:
>> drwxr-xr-x+ 1 Seb Aucun 0 May 19 12:30 lisp
> : ^
> :__________/
>
> This tells you that in addition to the Cygwin permissions Windows ACL
> are in effect. These may partially or completely subvert the POSIX
> permissions. Since you've re-created the directory, these ACL are most
> likely inherited ACL (applied from directories further up in the
> hierarchy).
These allow me to do everything I want (I'm even admin of my machine).
>> Would it be possible to have a more detailed reporting of the problem? For
>> example, I don't understand why org-install.el should be read-only, while
>> there was none before making autoloads... So, such a buffer has been
>> created... but can't be saved?
>
> Me neither and I've been using that same setup at work for months without
> any such problems. Only org-install.el seems to be read-only however, while
> org-version.el (which is created by the same method) is not, which makes
> this even more puzzling...
Absolutely. You pinpoint a real un-understandable thing (at least, for now)...
> But here's one other oddity in your log which may be able to explain it:
>
>> Loading vc-svn...
>
> It looks like lisp (or all of org probably) is both under SVN and Git
> version control... That is a Bad Idea™ and might explain why the buffer
> becomes read-only if org-install.el is already registered in SVN (which
> doesn't allow non-check-out files to be edited).
The location ~/src/org-mode/lisp/ is not in both Git and SVN.
In Git, well.
For SVN, it's ~/ that's for most parts of it (all my rc files) under SVN. Some
directories are as well in SVN, most aren't (just ignored).
I don't know if putting ~/ (= C:/home/sva/) under SVN is good or bad, but, for
sure, ~/src/org-mode/ is not under both.
> So can you please remove the Git work tree completely from SVN or just
> install in a pristine location?
But, you're right, this could be confusing. So, I've just clone Org into
C:/home/, a directory which is absolutely not under any VC system; and ditto
for its parent C:/.
--8<---------------cut here---------------start------------->8---
Seb@MEDIACENTER:c/home 0$ git clone git://orgmode.org/org-mode.git
Cloning into 'org-mode'...
Seb@MEDIACENTER:c/home 0$ cd org-mode
Seb@MEDIACENTER:home/org-mode 0$ make autoloads
======================================================
= Invoke "make help" for a synopsis of make targets. =
= Created a default local.mk template. =
= Setting "oldorg" as the default target. =
= Please adapt local.mk to your local setup! =
======================================================
make -C lisp autoloads
make[1]: Entering directory `/cygdrive/c/home/org-mode/lisp'
rm -f org-version.el org-install.el org-version.elc org-install.elc
org-version: 7.8.10 (release_7.8.10-572-g40a789)
Loading c:/home/org-mode/lisp/org-compat.el (source)...
Loading c:/home/org-mode/UTILITIES/org-fixup.el (source)...
Loading vc-git...
Saving file c:/home/org-mode/lisp/org-version.el...
Wrote c:/home/org-mode/lisp/org-version.el
org-install: 7.8.10 (release_7.8.10-572-g40a789)
Loading c:/home/org-mode/lisp/org-compat.el (source)...
Loading c:/home/org-mode/UTILITIES/org-fixup.el (source)...
Buffer is read-only: #<buffer org-install.el>
Makefile:30: recipe for target `org-install.el' failed
make[1]: *** [org-install.el] Error 127
make[1]: Leaving directory `/cygdrive/c/home/org-mode/lisp'
targets.mk:87: recipe for target `autoloads' failed
make: *** [autoloads] Error 2
Seb@MEDIACENTER:home/org-mode 0$ ls -l
total 44
-rw-r--r-- 1 Seb Aucun 3179 May 19 15:15 Makefile
-rw-r--r-- 1 Seb Aucun 1138 May 19 15:15 README
-rw-r--r-- 1 Seb Aucun 1054 May 19 15:15 README_DIST
-rw-r--r-- 1 Seb Aucun 3522 May 19 15:15 README_GIT
-rw-r--r-- 1 Seb Aucun 11757 May 19 15:15 README_maintainer
drwxr-xr-x+ 1 Seb Aucun 0 May 19 15:15 UTILITIES
drwxr-xr-x+ 1 Seb Aucun 0 May 19 15:15 contrib
-rw-r--r-- 1 Seb Aucun 3865 May 19 15:15 default.mk
drwxr-xr-x+ 1 Seb Aucun 0 May 19 15:15 doc
drwxr-xr-x+ 1 Seb Aucun 0 May 19 15:15 etc
drwxr-xr-x+ 1 Seb Aucun 0 May 19 15:17 lisp
-rw-r--r-- 1 Seb Aucun 1460 May 19 15:17 local.mk
-rw-r--r-- 1 Seb Aucun 1007 May 19 15:15 request-assign-future.txt
-rw-r--r-- 1 Seb Aucun 3194 May 19 15:15 targets.mk
drwxr-xr-x+ 1 Seb Aucun 0 May 19 15:15 testing
Seb@MEDIACENTER:home/org-mode 0$
--8<---------------cut here---------------end--------------->8---
The same happens, this time without any vc messages (neither Git nor SVN).
Searches on the net tell this message can happen when the owner is root or
with bad permissions. I did chmod -R 0777 on every file and directory, but I
still have the same problem.
>> Other question: why do we have to make org-install.el? Shouldn't it be
>> distributed with the other files, without requiring all users to make it?
>
> Because you use the sources and have to generate all the things that
> need to be generated. The generated files might be included in
> distribution archives, Bastien and I are currently thinking about that.
OK. That makes sense.
But, if it causes troubles for people with no make capability, couldn't that
be autogenerated as a post-commit process on the server or so? I don't know
it this is a good idea.
Anyway, it shouldn't be a big deal.
Best regards,
Seb
[1] DEFINITION NOT FOUND: 1
--
Sebastien Vauban
next prev parent reply other threads:[~2012-05-19 13:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-18 20:49 Can't make org-install.el Sebastien Vauban
2012-05-19 8:54 ` Achim Gratz
2012-05-19 10:42 ` Sebastien Vauban
2012-05-19 12:00 ` Achim Gratz
2012-05-19 13:40 ` Sebastien Vauban [this message]
2012-05-19 15:11 ` Achim Gratz
2012-05-19 17:56 ` [PATCH] " Achim Gratz
2012-05-19 18:05 ` Bastien
2012-05-19 19:00 ` Sebastien Vauban
2012-05-19 19:17 ` Achim Gratz
2012-05-19 19:41 ` Achim Gratz
2012-05-19 20:27 ` Achim Gratz
2012-05-21 8:37 ` Sebastien Vauban
2012-05-21 8:59 ` Sebastien Vauban
2012-05-23 22:01 ` Achim Gratz
2012-05-21 13:34 ` Bastien
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=808vgoqoff.fsf@somewhere.org \
--to=wxhgmqzgwmuf-genee64ty+gs+fvcfc7uqw@public.gmane.org \
--cc=emacs-orgmode-mXXj517/zsQ@public.gmane.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://git.savannah.gnu.org/cgit/emacs/org-mode.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).