From: Eric Blake <ebb9@byu.net>
To: The Cygwin-Talk Malingering List <cygwin-talk@cygwin.com>
Subject: Re: Mirroring and stage and tmp dirs
Date: Mon, 17 Apr 2006 13:21:00 -0000 [thread overview]
Message-ID: <44439644.1090900@byu.net> (raw)
In-Reply-To: <Pine.GSO.4.63.0604161101551.5936@access1.cims.nyu.edu>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
According to Igor Peshansky on 4/16/2006 9:04 AM:
> The /stage folder is used to build up parts of the changed directory
> structure and transfer them over in one swell foop (to avoid a race with
> the upset cron job, where it could catch the uploader in mid-update and
> result in a broken setup.ini).
And somebody just changed the permissions on that directory so that it is
no longer writable by members of the cygwin group. In other words, when I
tried to use it this morning to upload bash-3.1-5, I got permissions
errors, whereas previously I had no problems.
$ ls -ld stage # mtime is near when I used it to upload coreutils-5.94-5
drwxrwsr-x 2 root root 4096 Apr 15 16:30 stage
$ ls -ld --time=ctime stage # ctime reflects permissions change
drwxrwsr-x 2 root root 4096 Apr 17 09:00 stage
cgf - care to fix it please?
- --
Life is short - so eat dessert first!
Eric Blake ebb9@byu.net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.1 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFEQ5ZE84KuGfSFAYARAjSqAKDQiadqVS1OcXWdXhaiBYfzExLzZwCdGtSc
4/D9ReqHPOgF41JPUqeTiec=
=zFlC
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2006-04-17 13:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-16 14:55 Robert Pendell
2006-04-16 15:04 ` Igor Peshansky
2006-04-16 16:31 ` Robert Pendell
2006-04-16 17:24 ` Igor Peshansky
2006-04-16 17:52 ` Robert Pendell
2006-04-16 18:03 ` Brian Dessent
2006-04-17 13:21 ` Eric Blake [this message]
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=44439644.1090900@byu.net \
--to=ebb9@byu.net \
--cc=cygwin-talk@cygwin.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.
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).