From: Gerald Pfeifer <gerald@pfeifer.com>
To: overseers@gcc.gnu.org
Cc: "Martin Liška" <mliska@suse.cz>
Subject: chown -R gccadmin /www/gcc/htdocs-preformatted
Date: Tue, 18 Oct 2022 16:15:20 +0200 (CEST) [thread overview]
Message-ID: <f8a14896-4b4d-0086-6b69-863d32932180@pfeifer.com> (raw)
Martin reported that his latest change to
https://gcc.gnu.org/codingconventions.html
did not make it to the actual gcc.gnu.org site after pushing to git.
I dug into it and found that /www/gcc/htdocs-preformatted is behind
git head. `git pull` gets stuck (even as user gccadmin).
$ git checkout
Your branch is behind 'origin/master' by 3 commits, and can be fast-forwarded.
(use "git pull" to update your local branch)
$ git pull
Updating 68c7552f..415fcf49
error: unable to unlink old 'htdocs/onlinedocs/8.4.0/index.html': Permission denied
Ask: Can you please run
chown -R gccadmin /www/gcc/htdocs-preformatted
as root?
And then see whether
cd /www/gcc/htdocs-preformatted ; git pull
(as user gccadmin) succeeds?
Thank you,
Gerald
Q: Why is this happening only now, with this specific update?
Why did Martin and others not run into any problems the last years?
A: My commit 91315916d177e42c5888c5d30491ab6d6041b1a4 four days ago
touched every single *.html file in the tree, which is a first in
four years, and a first since wwwdocs moved to git three years ago.
Interestingly newer directories under onlinedocs/ don't run into this
since they are drwxrwsr-x. instead of drwxr-sr-x. like 8.4.0 is.
next reply other threads:[~2022-10-18 14:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-18 14:15 Gerald Pfeifer [this message]
2022-10-18 14:46 ` Frank Ch. Eigler
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=f8a14896-4b4d-0086-6b69-863d32932180@pfeifer.com \
--to=gerald@pfeifer.com \
--cc=mliska@suse.cz \
--cc=overseers@gcc.gnu.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).