It would seem that getting dput to provide some sort of tracking id would enable much better status tracking. Perhaps the dput output should indicate the full upload location in its output as a URL like ftp://ppa.launchpad.net/~nealmcb/ubuntu/authtool_0.2.2~ppa1.dsc (or whatever)
and that could be cut-and-pasted as input in some launchpad web query to get status?
Or Is ftp just the wrong sort of protocol for this queue injection function?
Here are some other relevant details.
authtool_ 0.2.2~ppa1_ source. upload:
Successfully uploaded ../authtool_ 0.2.2~ppa1. dsc to ppa.launchpad.net. 0.2.2~ppa1. tar.gz to ppa.launchpad.net. 0.2.2~ppa1_ source. changes to ppa.launchpad.net.
Successfully uploaded ../authtool_
Successfully uploaded ../authtool_
(3 times)
.dput.cf:
[my-ppa]
fqdn = ppa.launchpad.net
incoming = ~nealmcb/ubuntu/
login = anonymous
It would seem that getting dput to provide some sort of tracking id would enable much better status tracking. Perhaps the dput output should indicate the full upload location in its output as a URL like launchpad. net/~nealmcb/ ubuntu/ authtool_ 0.2.2~ppa1. dsc (or whatever)
ftp://ppa.
and that could be cut-and-pasted as input in some launchpad web query to get status?
Or Is ftp just the wrong sort of protocol for this queue injection function?