Any reason why gnupload sends symlink: prior to rmsymlink: commands, even when the are specified the other way around on the command line? The net result is that the just-created symlink is nuked, rather than the intended removal of the old link and recreation of the same name pointing to a new location.
$ ./build-aux/gnupload --dry-run --to ftp.gnu.org:m4 \ --rmsymlink m4-latest.tar.bz2 \ --symlink m4-1.4.14.tar.bz2 m4-latest.tar.bz2 Enter GPG passphrase: File eblake-16107.directive: version: 1.1 directory: m4 comment: gnupload v. 2010-02-08.07 symlink: m4-1.4.14.tar.bz2 m4-latest.tar.bz2 rmsymlink: m4-latest.tar.bz2 ---------------------------- Running gpg --batch --no-tty --passphrase-fd 0 --clearsign eblake-16107.directive... Running ncftpput ftp-upload.gnu.org /incoming/ftp eblake-16107.directive.asc... -- Don't work too hard, make some time for fun as well! Eric Blake [email protected]
signature.asc
Description: OpenPGP digital signature
