This is the mail archive of the cygwin-apps-cvs mailing list for the cygwin-apps project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[cygwin-apps htdocs - The cygwin-apps website files] branch master, updated. 3886184cea2a6ee3ede6faec419f7acb75c81ac6




https://sourceware.org/git/gitweb.cgi?p=cygwin-apps/apps-htdocs.git;h=3886184cea2a6ee3ede6faec419f7acb75c81ac6

commit 3886184cea2a6ee3ede6faec419f7acb75c81ac6
Author: Jon Turney <jon.turney@dronecode.org.uk>
Date:   Tue Mar 22 22:21:52 2016 +0000

    Update for upset->calm


Diff:
---
 package-upload.html |   16 ++++++----------
 1 files changed, 6 insertions(+), 10 deletions(-)

diff --git a/package-upload.html b/package-upload.html
index bc6a0b6..7545cdc 100644
--- a/package-upload.html
+++ b/package-upload.html
@@ -139,7 +139,7 @@ the release directory.  So, it should be a hierarchy containing
 <tt>.tar.xz</tt> files and (potentially) <tt>setup.hint</tt> files.</p>
 
 <p>The <tt>!ready</tt> file is used to tell
-<tt>upset</tt> (the script which creates setup.ini) that any files older
+<tt>calm</tt> (the script which creates setup.ini) that any files older
 than this file in or under the given directory should be processed.  The
 intent is that you create <tt>!ready</tt> when you have finished
 uploading everything that you plan on uploading.</p>
@@ -148,7 +148,7 @@ uploading everything that you plan on uploading.</p>
 architecture that is uploaded</b>, i.e., in each of the <tt>x86</tt> and
 <tt>x86_64</tt> directories or in the package directories themselves.</p>
 
-<p><tt>upset</tt> will periodically scan the upload directories for
+<p><tt>calm</tt> will periodically scan the upload directories for
 packages that are ready, and, if there are no errors, move the packages
 into the real release area.  New directories in the release area will be
 created as needed.  If there are errors then <tt>setup.ini</tt> will not
@@ -161,13 +161,9 @@ since they already exist in the main release.</p>
 
 <p>Although not shown above, you can also create a <tt>!mail</tt> (or
 <tt>!email</tt>) file which contains a list of email address (one per
-line) where any <tt>upset</tt> errors should be sent.  If that isn't
-specified then you won't get email when upset finds issues with what was
-uploaded.  Currently, this is not a "per-directory" thing since upset
-parsing doesn't work that way so, if you add a <tt>!email</tt> file you
-will get all errors from upset - not just ones associated to your
-uploaded packages.  It doesn't matter where you create this file but
-it makes sense to put it at the root of your upload directory.</p>
+line) where any <tt>calm</tt> reports should be sent.  If that isn't
+specified then you won't get email when <tt>calm</tt> finds issues with what was
+uploaded.  This file must be in the root of your upload directory.</p>
 
 <h4>Example <tt>lftp</tt> upload command line</h4>
 
@@ -203,7 +199,7 @@ To cause files to be removed from the distribution, upload an empty file with th
 <h3><a name="stalled">Q) Why aren't my files being transferred to the release area?  I've waited
 several days and don't see any movement.</h3>
 
-<p>A) The package updater runs every hour at 10 minutes past the hour so, if you don't see any movement
+<p>A) The package updater runs every hour, at 10 and 40 minutes past the hour so, if you don't see any movement
 at, e.g., 20 minutes past the next hour, then your package is not going to be updated.</p>
 
 <p>The main reason that this could happen is if you uploaded a package that


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]