From: Corinna Vinschen <vinschen@redhat.com>
To: overseers@sourceware.org
Subject: Re: Cygwin infrastructure assistance, part 3
Date: Wed, 13 Aug 2014 13:18:00 -0000 [thread overview]
Message-ID: <20140813131802.GI21106@calimero.vinschen.de> (raw)
In-Reply-To: <20140812184045.GA1811@ednor.casa.cgf.cx>
[-- Attachment #1: Type: text/plain, Size: 978 bytes --]
On Aug 12 14:40, Christopher Faylor wrote:
> On Tue, Aug 12, 2014 at 02:29:40PM -0400, Frank Ch. Eigler wrote:
> >Yaakov wrote:
> >> There may also be jobs in the root crontab that are Cygwin related.
> >> Could someone please check this as well; we want all Cygwin-specific
> >> jobs in the cygwin-admin@ crontab so that we can manage them ourselves.
> >
> >OK, commented out a few items from the root crontab, related to
> >cygwin/cleancache, chowning stuff under the ftp pub/cygwin directory,
> >and running cygwin-staging/mkpkgdir .
>
> The cleancache and mkpkgdir could likely be run by cygwin-owned crontab
> but the chown part needs to still be there. It changes ownership and
> protection for files uploaded to the cygwin release directory by people
> with login privileges to sourceware who update the release area by hand.
Could the chown be handled by some sudo magic?
Thanks,
Corinna
--
Corinna Vinschen
Cygwin Maintainer
Red Hat
[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-08-13 13:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-12 5:28 Yaakov Selkowitz
2014-08-12 15:53 ` Yaakov Selkowitz
2014-08-12 18:29 ` Frank Ch. Eigler
2014-08-12 18:40 ` Christopher Faylor
2014-08-13 13:18 ` Corinna Vinschen [this message]
2014-08-13 14:09 ` Christopher Faylor
2014-08-13 14:24 ` Corinna Vinschen
2014-08-12 19:18 ` Yaakov Selkowitz
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=20140813131802.GI21106@calimero.vinschen.de \
--to=vinschen@redhat.com \
--cc=overseers@sourceware.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).