seems like the URL is passed as-is to the sftp-client, which can't
handle the "sftp://" prefix:
amit0 myapp # ebuild --debug myapp-1.0.ebuild digest
<SNIP>
>>> Downloading 'sftp://my.server.com:/home/public/mydistfile.tar.gz'
Connecting to sftp...
ssh: sftp: Name or service not known
Couldn't read packet: Connection reset by peer
No digest file available and download failed.
Seems then to me I'm not on the right track. Should I be using a
different method? Or is this method supposed to work? If not, would
rsync be my favored approach? How is rsync transfer configured?
Thanks,
Amit
01-29-2009, 07:29 AM
Zac Medico
use of sftp/scp transfer protocol in ebuilds.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Amit Dor-Shifer wrote:
> seems like the URL is passed as-is to the sftp-client, which can't
> handle the "sftp://" prefix:
Then you should use a shell script for FETCHCOMMAND and make the
shell script strip the protocol. Something like this should work: