Revision: 674
http://svn.savannah.gnu.org/viewvc/?view=rev&root=administration&revision=674
Author: ineiev
Date: 2023-11-27 05:30:49 -0500 (Mon, 27 Nov 2023)
Log Message:
-----------
add examples for rm and rmdir; minor improvements
Modified Paths:
--------------
trunk/sviki/DownloadArea.mdwn
Modified: trunk/sviki/DownloadArea.mdwn
===================================================================
--- trunk/sviki/DownloadArea.mdwn 2023-11-27 10:15:15 UTC (rev 673)
+++ trunk/sviki/DownloadArea.mdwn 2023-11-27 10:30:49 UTC (rev 674)
@@ -1,12 +1,12 @@
Uploading a signed release
--------------------------
-If your project is part of GNU and you want to upload at ftp.gnu.org or
+If your package is part of GNU and you want to upload at ftp.gnu.org or
alpha.gnu.org, you currently need to follow the [maintainers'
-guide](http://www.gnu.org/prep/maintain/html_node/Automated-FTP-Uploads.html).
+guide](//www.gnu.org/prep/maintain/html_node/Automated-FTP-Uploads.html).
On Savannah, you can use scp to upload your GPG signed files. To begin,
-please add your GPG keys to the Public Information of your project.
+please add your GPG keys to the Public Information of your group.
For each upload destined for Savannah, two files need to be uploaded.
@@ -45,7 +45,7 @@
chmod a+r ./*
# Upload the files
- scp release.tar.gz release.tar.gz.sig
[email protected]:/releases/YOUR_PROJECT_NAME_HERE/
+ scp release.tar.gz release.tar.gz.sig
[email protected]:/releases/GROUP_NAME/
Note that unlike ftp.gnu.org, Savannah doesn't enforce using GPG signatures
for releases, and doesn't verify them when they are used.
@@ -72,24 +72,29 @@
For example using scp and a bash command line:
- scp foo-1.11.22.tar.gz{,.sig} [email protected]:/releases/fooproject/
+ scp foo-1.11.22.tar.gz{,.sig} [email protected]:/releases/foogroup/
For example using rsync (do not use -a):
- rsync -tv foo-1.11.22.tar.gz{,.sig}
[email protected]:/releases/fooproject/
+ rsync -tv foo-1.11.22.tar.gz{,.sig}
[email protected]:/releases/foogroup/
+For example removing files and directories:
+
+ ssh [email protected] rm /releases/foogroup/foo-bad-file
+ ssh [email protected] rmdir /releases/foogroup/foo-bad-directory
+
The authentication method to use with scp is SSH public key (one of those
that you registered in your Savannah account).
You can also use the gnupload script to upload multiple files, available
-from the build-aux directory of the Gnulib project,
-<http://savannah.gnu.org/projects/gnulib>.
+from the build-aux directory of the
+[Gnulib package](//savannah.gnu.org/projects/gnulib).
Files will appear at
-<http://download.savannah.nongnu.org/releases/@PROJECT_NAME_HERE@/>.
+http://download.savannah.nongnu.org/releases/GROUP_NAME/.
This is multiplexed between all mirrors, hopefully picking a nearby and
up-to-date one. Please expect a delay of up to 24 hours for an upload on
-savannah to appear on all mirrors.
+Savannah to appear on all mirrors.
Mirrors
-------
@@ -96,12 +101,12 @@
We are always happy to have more mirrors of the nongnu download area.
The webmasters may inform us, or people may come to us
-directly. Information for new mirrors is at
-<http://www.gnu.org/server/mirror.html> (GNU webmasters can edit).
+directly. [Information for new mirrors](http://www.gnu.org/server/mirror.html)
+(GNU webmasters can edit).
When we are told of a new mirror, we should verify, and then 1) on mgt0,
add contact information to `/root/administration/mirrors-contacts.txt`;
-2) on download0.savannah.gnu.org, add the mirror url(s) to 2a)
+2) on download0.savannah.gnu.org, add the mirror URLs to 2a)
`/srv/download/00_MIRRORS.html` (alphabetical, check
-<http://download.savannah.gnu.org/releases-noredirect/00_MIRRORS.html>)
+[list online](//download.savannah.gnu.org/releases-noredirect/00_MIRRORS.html)
and 2b) `/srv/download/00_MIRRORS.txt` (no order).
