From: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>
To: cygwin-apps@cygwin.com
Subject: Re: Major changes coming to procedure for uploading to sourceware (long)
Date: Thu, 17 Oct 2013 19:33:00 -0000 [thread overview]
Message-ID: <20131017193321.GA2803@ednor.casa.cgf.cx> (raw)
In-Reply-To: <87mwm73dtk.fsf@Rainer.invalid>
On Thu, Oct 17, 2013 at 09:19:35PM +0200, Achim Gratz wrote:
>Christopher Faylor writes:
>> The package directories should exactly mirror what is currently in the
>> release directory. The !ready file is used to tell upset that any files
>> older than this file in or under the given directory should be
>> processed. The intent is that you create !ready when you have finished
>> uploading everything that you plan on uploading.
>
>Are we supposed to copy the existing contents of the mirrors (curr,
>previous etc. archives) into our release area first before adding
>anything new?
No. This is for adding new/updated packages to the release. Putting
old stuff in the staging area would certainly confuse things.
>My release area is non-empty but incomplete due to previous tests, but
>I don't want to remove or add anything there unless I know how this
>gets handled.
I just wiped out and recreated your home directory. There are no old
packages there now.
The process is:
1) upload new tarballs/setup.hints to package directory
2) package gets syntax checked
3) package gets moved to release area
What is currently missing is a way to delete old tarballs from the
release area. I'll probably have upset do that when it finds old
packages which are not covered by setup.hint.
cgf
next prev parent reply other threads:[~2013-10-17 19:33 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-12 20:22 Christopher Faylor
2013-10-16 16:52 ` The upload system is live (Re: Major changes coming to procedure for uploading to sourceware) Christopher Faylor
2013-10-17 4:30 ` Christopher Faylor
2013-10-22 16:40 ` Chris Sutcliffe
2013-10-22 18:50 ` Christopher Faylor
2013-10-22 19:38 ` Achim Gratz
2013-10-22 19:59 ` Christopher Faylor
2013-10-22 20:18 ` Achim Gratz
2013-10-22 20:26 ` Christopher Faylor
2013-10-22 17:59 ` Andrew Schulman
2013-10-23 2:47 ` Yaakov (Cygwin/X)
2013-10-23 16:51 ` Reini Urban
2013-10-23 17:37 ` Christopher Faylor
2013-10-17 19:19 ` Major changes coming to procedure for uploading to sourceware (long) Achim Gratz
2013-10-17 19:33 ` Christopher Faylor [this message]
2013-10-17 20:24 ` Achim Gratz
2013-10-18 18:43 ` Achim Gratz
2013-10-18 19:00 ` Christopher Faylor
2013-10-18 20:39 ` Achim Gratz
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=20131017193321.GA2803@ednor.casa.cgf.cx \
--to=cgf-use-the-mailinglist-please@cygwin.com \
--cc=cygwin-apps@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).