#71 Issues with absolute path names and FTP

[Manfred Usselmann]

Using duply version 1.5.10, duplicity version 0.6.21, python 2.7.5+, gpg 1.4.14 (Home: ~/.gnupg), awk 'GNU Awk 4.0.1'.

Backend is ncftp.

The intial backup failed until I used %2F to indicate absolute pathnames:

TARGET='ftp://myuser:mypassword@10.1.2.202/%2Fvbox backup/duply'

Now the second backup fails:

Running 'ncftpget -f /var/tmp/duplicity-y6z2PT-tempdir/mkstemp-HOjCRg-1 -F -t 30 -o useCLNT=0,useHELP_SITE=0 -V -C '10.1.2.202' 'vbox backup/duply/duplicity-full.20131215T082800Z.manifest' '/var/tmp/duplicity-y6z2PT-tempdir/mktemp-JWoeW9-3'' failed with code 3 (attempt #1)

I believe the reason is the missing slash at the beginning:

'vbox backup/duply/duplicity-full.20131215T082800Z.manifest'

This should most likely be

'/vbox backup/duply/duplicity-full.20131215T082800Z.manifest'

with an initial slash.

[ede]

On 15.12.2013 22:37, Manfred Usselmann wrote:

---

[bugs:#71] http://sourceforge.net/p/ftplicity/bugs/71/ Issues with absolute path names and FTP

Status: open
Created: Sun Dec 15, 2013 09:37 PM UTC by Manfred Usselmann
Last Updated: Sun Dec 15, 2013 09:37 PM UTC
Owner: nobody

Using duply version 1.5.10, duplicity version 0.6.21, python 2.7.5+, gpg 1.4.14 (Home: ~/.gnupg), awk 'GNU Awk 4.0.1'.

Backend is ncftp.

The intial backup failed until I used %2F to indicate absolute pathnames:

/TARGET='ftp://myuser:mypassword@10.1.2.202/%2Fvbox backup/duply'/

Now the second backup fails:

/Running 'ncftpget -f /var/tmp/duplicity-y6z2PT-tempdir/mkstemp-HOjCRg-1 -F -t 30 -o useCLNT=0,useHELP_SITE=0 -V -C '10.1.2.202' 'vbox backup/duply/duplicity-full.20131215T082800Z.manifest' '/var/tmp/duplicity-y6z2PT-tempdir/mktemp-JWoeW9-3'' failed with code 3 (attempt #1)/

I believe the reason is the missing slash at the beginning:

/'vbox backup/duply/duplicity-full.20131215T082800Z.manifest'/

This should most likely be

/'/vbox backup/duply/duplicity-full.20131215T082800Z.manifest'/

with an initial slash.

this is a duplicity issue.. if it persists try to search it's bug/answer tracker on launchpad.

i am not sure that absolute paths are actually supported by every ftp server out there. usually ftp servers virtually jail users to folder (configured on a by users basis). but that does not seem to be the problem here.

i'd rather guess that the 'literal slash' functionality was never built in to the ftp backend. you might want to
A. patch duplicity and provide the changes upstream
or
B. try to workaround the issue. symbolic links in the ftp user's folder might help..

..ede

[ede]

On 15.12.2013 22:37, Manfred Usselmann wrote:

---

[bugs:#71] http://sourceforge.net/p/ftplicity/bugs/71/ Issues with absolute path names and FTP

Status: open
Created: Sun Dec 15, 2013 09:37 PM UTC by Manfred Usselmann
Last Updated: Sun Dec 15, 2013 09:37 PM UTC
Owner: nobody

Using duply version 1.5.10, duplicity version 0.6.21, python 2.7.5+, gpg 1.4.14 (Home: ~/.gnupg), awk 'GNU Awk 4.0.1'.

Backend is ncftp.

The intial backup failed until I used %2F to indicate absolute pathnames:

/TARGET='ftp://myuser:mypassword@10.1.2.202/%2Fvbox backup/duply'/

Now the second backup fails:

/Running 'ncftpget -f /var/tmp/duplicity-y6z2PT-tempdir/mkstemp-HOjCRg-1 -F -t 30 -o useCLNT=0,useHELP_SITE=0 -V -C '10.1.2.202' 'vbox backup/duply/duplicity-full.20131215T082800Z.manifest' '/var/tmp/duplicity-y6z2PT-tempdir/mktemp-JWoeW9-3'' failed with code 3 (attempt #1)/

I believe the reason is the missing slash at the beginning:

/'vbox backup/duply/duplicity-full.20131215T082800Z.manifest'/

This should most likely be

/'/vbox backup/duply/duplicity-full.20131215T082800Z.manifest'/

with an initial slash.

and another idea.. try the standard duplicity way to define an absolute backend path (add extra /)
ftp[s]://user[:password]@other.host[:port]/[/absolute_]folder

no guarantees though.. ede