On Fri, 25 Jul 2008, Andrew Ferguson wrote:
[snip lots of debug output]
This doesn't make any sense. Everything seems correct. :-(
You could try deleting all of the *.pyc files in
/var/lib/python-support/python2.4/rdiff_backup/ ... those files are just
temporary compiled Python and could potentially cause problem if they are out
of sync. Python will regenerate them automatically from the source.
Doesn't help :-(
Also, what version of Python is running on the server? (pc00136)
[EMAIL PROTECTED]:~ #
python -V
Python 2.4.4
[EMAIL PROTECTED]:~ #
dpkg -l python
ii python 2.4.4-2
An interactive high-level object-oriented language (default version)
And did you do the --restrict-read-only options that Dean suggests in his HOWTO?
Yes, .ssh/authorized_keys contains
command="rdiff-backup --server --restrict-read-only
/",from="gatefmtc-new",no-port-forwarding,no-X11-forwarding,no-pty ssh-rsa ....
I guess I will have to setup Debian to check this. I just tried pushing a
restore with 1.1.15 with Centos client and Ubuntu server with no trouble.
I had a quick look at
<http://backports.org/debian/pool/main/r/rdiff-backup/rdiff-backup_1.1.15-2~bpo40+1.diff.gz>,
and it doesn't seem to alter any code, which makes it more plausible to me it is
either a nasty config error on my side (or some issue in the dependencies?)
sh-3.1$ apt-cache show rdiff-backup | grep Depends
Depends: libc6 (>= 2.3.5-1), librsync1 (>= 0.9.6), python (<< 2.5), python-support
(>= 0.3.4), python (>= 2.4)
Thx for looking into this!
Klaas
_______________________________________________
rdiff-backup-users mailing list at [email protected]
http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki
