From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21519 invoked by alias); 22 Mar 2016 22:23:15 -0000 Mailing-List: contact cygwin-apps-cvs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: cygwin-apps-cvs-owner@sourceware.org Received: (qmail 21498 invoked by uid 9795); 22 Mar 2016 22:23:15 -0000 Date: Tue, 22 Mar 2016 22:23:00 -0000 Message-ID: <20160322222315.21472.qmail@sourceware.org> From: jturney@sourceware.org To: cygwin-apps-cvs@sourceware.org Subject: [cygwin-apps htdocs - The cygwin-apps website files] branch master, updated. 3886184cea2a6ee3ede6faec419f7acb75c81ac6 X-Git-Refname: refs/heads/master X-Git-Reftype: branch X-Git-Oldrev: 09d0fc1213c7db5e7b135b1a505f586d44bba5c6 X-Git-Newrev: 3886184cea2a6ee3ede6faec419f7acb75c81ac6 X-SW-Source: 2016-q1/txt/msg00071.txt.bz2 https://sourceware.org/git/gitweb.cgi?p=cygwin-apps/apps-htdocs.git;h=3886184cea2a6ee3ede6faec419f7acb75c81ac6 commit 3886184cea2a6ee3ede6faec419f7acb75c81ac6 Author: Jon Turney 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 .tar.xz files and (potentially) setup.hint files.

The !ready file is used to tell -upset (the script which creates setup.ini) that any files older +calm (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 !ready when you have finished uploading everything that you plan on uploading.

@@ -148,7 +148,7 @@ uploading everything that you plan on uploading.

architecture that is uploaded, i.e., in each of the x86 and x86_64 directories or in the package directories themselves.

-

upset will periodically scan the upload directories for +

calm 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 setup.ini will not @@ -161,13 +161,9 @@ since they already exist in the main release.

Although not shown above, you can also create a !mail (or !email) file which contains a list of email address (one per -line) where any upset 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 !email 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.

+line) where any calm reports should be sent. If that isn't +specified then you won't get email when calm finds issues with what was +uploaded. This file must be in the root of your upload directory.

Example lftp upload command line

@@ -203,7 +199,7 @@ To cause files to be removed from the distribution, upload an empty file with th

Q) Why aren't my files being transferred to the release area? I've waited several days and don't see any movement.

-

A) The package updater runs every hour at 10 minutes past the hour so, if you don't see any movement +

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.

The main reason that this could happen is if you uploaded a package that