Replying to myself again :( I should prefix this by saying that I don't know Python.
I wrote: > When I run rdiff-backup, it says: > > Traceback (most recent call last): > File "/usr/local/bin/rdiff-backup", line 20, in ? > import rdiff_backup.Main > ImportError: No module named rdiff_backup.Main > > So I guess there's something else wrong but I haven't investigated that yet. I've discovered that there is a file called /usr/local/lib64/python2.3/site-packages/rdiff_backup/Main.py So in my shell, I've typed export PYTHONPATH=/usr/local/lib64/python2.3/site-packages/ and now rdiff-backup runs. But clearly that's a temporary workaround. What's the permanent fix? Is this an oversight in Suse's Python installation (that it doesn't define PYTHONPATH). Is that a standard Python path? Or is it a problem in the rdiff-backup install script? Did it put the modules in the right place? Should it have set PYTHONPATH, or done some other Python magic? Or something else? Thanks, Dave _______________________________________________ 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
