From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5166 invoked by alias); 26 Mar 2016 11:38:05 -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 5146 invoked by uid 9795); 26 Mar 2016 11:38:04 -0000 Date: Sat, 26 Mar 2016 11:38:00 -0000 Message-ID: <20160326113804.5120.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. 64fdc913c2a799a6fdd831c64d3563b8fef8a288 X-Git-Refname: refs/heads/master X-Git-Reftype: branch X-Git-Oldrev: 3886184cea2a6ee3ede6faec419f7acb75c81ac6 X-Git-Newrev: 64fdc913c2a799a6fdd831c64d3563b8fef8a288 X-SW-Source: 2016-q1/txt/msg00074.txt.bz2 https://sourceware.org/git/gitweb.cgi?p=cygwin-apps/apps-htdocs.git;h=64fdc913c2a799a6fdd831c64d3563b8fef8a288 commit 64fdc913c2a799a6fdd831c64d3563b8fef8a288 Author: Jon Turney Date: Sat Mar 26 11:27:04 2016 +0000 More updates for calm Diff: --- package-upload.html | 54 ++++++++++++++++++++++---------------------------- 1 files changed, 24 insertions(+), 30 deletions(-) diff --git a/package-upload.html b/package-upload.html index 7545cdc..aaa964a 100644 --- a/package-upload.html +++ b/package-upload.html @@ -1,5 +1,5 @@ - @@ -134,9 +134,27 @@ directory on cygwin.com will look like this:

lftp cygwin.com:/x86/release> put /dev/null -o !ready +

Example lftp upload command line

+ +
    From: Christopher Faylor
+    To: cygwin-apps
+    Subject: Re: The upload system is live (Re: Major changes coming to
+            procedure for uploading to sourceware)
+    Date: Thu, 17 Oct 2013 00:30:00 -0400
+
+    I just used this command line to upload the time packages:
+
+    cd wherever
+    lftp -c 'connect sftp://cygwin@cygwin.com/; cd x86/release; mirror -eR time; put /dev/null -o !ready'
+
+    FYI.
+
+    cgf
+
+

The package directories should exactly mirror what is currently in the release directory. So, it should be a hierarchy containing -.tar.xz files and (potentially) setup.hint files.

+.tar.xz files and setup.hint files.

The !ready file is used to tell calm (the script which creates setup.ini) that any files older @@ -154,43 +172,20 @@ 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 be updated and the release area will remain pristine. -

Note: The upload area is only for new files -intended for the Cygwin release. There is no reason to put older -files (such as unchanged setup.hints) in the upload directories -since they already exist in the main release.

+

Getting reports

-

Although not shown above, you can also create a !mail (or +

You can also create a !mail (or !email) file which contains a list of email address (one per -line) where any calm reports should be sent. If that isn't +line) where any calm reports on your packages 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

- -
    From: Christopher Faylor
-    To: cygwin-apps
-    Subject: Re: The upload system is live (Re: Major changes coming to
-            procedure for uploading to sourceware)
-    Date: Thu, 17 Oct 2013 00:30:00 -0400
-    
-    I just used this command line to upload the time packages:
-    
-    cd wherever
-    lftp -c 'connect sftp://cygwin@cygwin.com/; cd x86/release; mirror -eR time; put /dev/null -o !ready'
-    
-    FYI.
-    
-    cgf
-
-

Removing files from the Cygwin distribution

To cause files to be removed from the distribution, upload an empty file with the name of the file that you want deleted, prefixed with a "-".

For example, if you want to delete the file foo-1.2-1.tar.xz then upload an empty file named:

 -foo-1.2-1.tar.xz

-

Wildcards: "*" and "?" are supported. So,

 -foo-1.2-1*
will cause both the binary and src package files to be removed.

-

Note that files are not actually deleted; they are moved to a vault where they will be removed after some indeterminate amount of time.

This technique should work with directories but some confusion may arise if you delete a directory, recreate it, and attempt to remove it again. This scenario has not been tested.

@@ -199,7 +194,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 and 40 minutes past the hour so, if you don't see any movement +

A) The package updater runs twice 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 @@ -231,4 +226,3 @@ you aren't listed as an owner there your packages won't be updated. -