Your message dated Sun, 18 Nov 2012 12:48:00 +1000
with message-id <[email protected]>
and subject line Re: Bug#693546: likely to be a timeout problem
has caused the Debian Bug report #693546,
regarding duplicity: permission failure on davfs2 mountpoints
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
693546: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=693546
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: duplicity
Version: 0.6.08b-1+b1
Severity: normal
When duplicity attempts to write to a davfs2-mounted folder, it falls
over with a permission error:
Writing /mountpoint/box.net/duplicity-full.20121111T101011Z.vol1.difftar.gpg
Traceback (most recent call last):
File "/usr/bin/duplicity", line 1251, in <module>
with_tempdir(main)
File "/usr/bin/duplicity", line 1244, in with_tempdir
fn()
File "/usr/bin/duplicity", line 1217, in main
full_backup(col_stats)
File "/usr/bin/duplicity", line 416, in full_backup
globals.backend)
File "/usr/bin/duplicity", line 315, in write_multivol
(tdp, dest_filename)))
File "/usr/lib/python2.6/dist-packages/duplicity/asyncscheduler.py", line
145, in schedule_task
return self.__run_synchronously(fn, params)
File "/usr/lib/python2.6/dist-packages/duplicity/asyncscheduler.py", line
171, in __run_synchronously
ret = fn(*params)
File "/usr/bin/duplicity", line 314, in <lambda>
async_waiters.append(io_scheduler.schedule_task(lambda tdp,
dest_filename: put(tdp, dest_filename),
File "/usr/bin/duplicity", line 240, in put
backend.put(tdp, dest_filename)
File "/usr/lib/python2.6/dist-packages/duplicity/backends/localbackend.py",
line 57, in put
target_path.writefileobj(source_path.open("rb"))
File "/usr/lib/python2.6/dist-packages/duplicity/path.py", line 589, in
writefileobj
fout = self.open("wb")
File "/usr/lib/python2.6/dist-packages/duplicity/path.py", line 531, in open
result = open(self.name, mode)
IOError: [Errno 13] Permission denied:
'/mountpoint/box.net/duplicity-full.20121111T101011Z.vol1.difftar.gpg'
-- System Information:
Debian Release: 6.0.6
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages duplicity depends on:
ii gnupg 1.4.10-4 GNU privacy guard - a free PGP rep
ii libc6 2.11.3-4 Embedded GNU C Library: Shared lib
ii librsync1 0.9.7-7 rsync remote-delta algorithm libra
ii python 2.6.6-3+squeeze7 interactive high-level object-orie
ii python-central 0.6.16+nmu1 register and build utility for Pyt
ii python-pexpect 2.3-1 Python module for automating inter
duplicity recommends no packages.
Versions of packages duplicity suggests:
pn ncftp <none> (no description available)
pn python-boto <none> (no description available)
-- no debconf information
--- End Message ---
--- Begin Message ---
On Sat, 17 Nov 2012 17:28:56 -0500, Anonymous writes:
>I should also point out that this is likely to be a timeout problem.
sorry but that is not a bug in duplicity - if anything, it's a bug
in davfs2.
duplicity does precisely what it's supposed to do with local files:
do an open() with write perms, and write to the resulting file handle.
the fact that you've mounted a remote resource and that
these 'local' files aren't local is not discernible to duplicity,
nor should it need to know.
regards
az
--
Alexander Zangerl + GPG Key 0x42BD645D or 0x5B586291 + http://snafu.priv.at/
Every program in development at MIT expands until it can read mail.
signature.asc
Description: Digital Signature
--- End Message ---
