[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

gnustandards ChangeLog maintain.texi

From: Karl Berry
Subject: gnustandards ChangeLog maintain.texi
Date: Mon, 21 May 2012 00:38:11 +0000

CVSROOT:        /sources/gnustandards
Module name:    gnustandards
Changes by:     Karl Berry <karl>       12/05/21 00:38:11

Modified files:
        .              : ChangeLog maintain.texi 

Log message:
        ftp-upload protocol v1.2 requiring explicit replace of files


Index: ChangeLog
RCS file: /sources/gnustandards/gnustandards/ChangeLog,v
retrieving revision 1.162
retrieving revision 1.163
diff -u -b -r1.162 -r1.163
--- ChangeLog   14 May 2012 22:30:01 -0000      1.162
+++ ChangeLog   21 May 2012 00:38:10 -0000      1.163
@@ -1,3 +1,10 @@
+2012-05-20  Ward Vandewege  <address@hidden>
+       * maintain.texi (FTP Upload Directive File - v1.2): new node.
+       (FTP Upload Directive File - v1.1): access to archived files
+       is simply via email to sysadmin.
+       (FTP Upload Directive File - v1.0): no longer supported.
 2012-05-14  Karl Berry  <address@hidden>
        * maintain.texi (GNU and Linux): url fixes from Ineiev.

Index: maintain.texi
RCS file: /sources/gnustandards/gnustandards/maintain.texi,v
retrieving revision 1.222
retrieving revision 1.223
diff -u -b -r1.222 -r1.223
--- maintain.texi       17 May 2012 23:07:50 -0000      1.222
+++ maintain.texi       21 May 2012 00:38:10 -0000      1.223
@@ -5,7 +5,7 @@
 @c For double-sided printing, uncomment:
 @c @setchapternewpage odd
 @c This date is automagically updated when you save this file:
address@hidden lastupdate May 17, 2012
address@hidden lastupdate May 20, 2012
 @c %**end of header
 @dircategory GNU organization
@@ -1495,6 +1495,7 @@
 * Automated Upload Registration::
 * Automated Upload Procedure::
+* FTP Upload Directive File - v1.2::
 * FTP Upload Directive File - v1.1::
 * FTP Upload Directive File - v1.0::
 @end menu
@@ -1510,7 +1511,6 @@
 for your GNU package:
 Create an account for yourself at @url{}, if
 you don't already have one.  By the way, this is also needed to
@@ -1598,7 +1598,7 @@
 extension. If you do not follow this naming convention, the upload
 @emph{will not be processed}.
-Since v1.1 of the upload script, it is also possible to upload a
+Since v1.1 of the upload directives, it is also possible to upload a
 clearsigned directive file on its own (no accompanying @file{.sig} or
 any other file) to perform certain operations on the server.
 @xref{FTP Upload Directive File - v1.1}, for more information.
@@ -1639,6 +1639,43 @@
address@hidden FTP Upload Directive File - v1.2
address@hidden FTP Upload Directive File - v1.2
+All the directives and documentation for v1.1 of the protocol still
+apply.  @xref{FTP Upload Directive File - v1.1}, for more information.
address@hidden New directive @code{replace}
address@hidden replacing uploaded files
address@hidden uploads, replacing
+As part of an uploaded triplet, a @file{foo.tar.gz.directive.asc} file
+might contain these lines (before being GPG-clearsigned):
+version: 1.2
+directory: bar/v1
+filename: foo.tar.gz
+comment: hello world!
address@hidden example
+If @file{foo.tar.gz} exists prior to upload, this directive file will
+result in an error.  Prior to May 2012, the behavior (of v1.1) was
+different: any existing files were automatically archived and replaced
+with the new upload.  Since May 2012, no files are replaced unless the
+(new) @code{replace} directive is set to @code{true} in the directive
+file.  That directive requires version 1.2 of the protocol.  For
+version: 1.2
+directory: bar/v1
+filename: foo.tar.gz
+replace: true
+comment: hello world!
address@hidden example
 @node FTP Upload Directive File - v1.1
 @subsection FTP Upload Directive File - v1.1
@@ -1646,7 +1683,7 @@
 When part of a triplet, the directive file must always contain the
 directives @code{version}, @code{directory} and @code{filename}, as
-described. In addition, a 'comment' directive is allowed.
+described. In addition, a @code{comment} directive is allowed.
 The @code{version} directive must always have the value @samp{1.1}.
@@ -1676,17 +1713,19 @@
 @file{gnu/bar/v1} of the @code{} site.
 The directive file can be used to create currently non-existent
-directory trees, as long as they are under the package directory for
-your package (in the example above, that is @code{bar}).
+directory trees, as long as they are under the directory for your
+package (in the example above, the package directory is @code{bar}).
 If you upload a file that already exists in the FTP directory, the
 original will simply be archived and replaced with the new upload.
+There is no automated or online access to archived files; if you want
+to retrieve or view them, please email sysadmin.
 @subheading Standalone directives
-When uploaded by itself, the directive file must contain one or more
-of the directives @code{symlink}, @code{rmsymlink} or @code{archive},
-in addition to the obligatory @code{directory} and @code{version}
+When uploaded by itself, a directive file must contain one or more of
+the directives @code{symlink}, @code{rmsymlink} or @code{archive}, in
+addition to the obligatory @code{directory} and @code{version}
 directives.  A @code{filename} directive is not allowed, and a
 @code{comment} directive remains optional.
@@ -1758,11 +1797,8 @@
 @node FTP Upload Directive File - v1.0
 @subsection FTP Upload Directive File - v1.0
address@hidden of June 2006, the upload script is running in compatibility
-mode, allowing uploads with either address@hidden or
address@hidden of the directive file syntax.  Support for v1.0
-uploads will be phased out by the end of 2006, so please upgrade
+Support for v1.0 uploads was phased out in May 2012; please upgrade
 The directive file should contain one line, excluding the clearsigned
 data GPG that inserts, which specifies the final destination directory

reply via email to

[Prev in Thread] Current Thread [Next in Thread]