From mboxrd@z Thu Jan 1 00:00:00 1970
Return-Path:
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.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