© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
The same problem has been reported several other times in the backuppc-devel list:
http://
http://
http://
http://
The problem has been reported to the list since August, but so far the developers have not said anything about it. If you have another way of contacting them, please do, since this is a problem that should be simple to solve.
There is an alternative patch suggested by a Debian user, but it's setting the variables on the wrong place, inside the function that reads the config file instead of after calling that function where TopDir may potentially be changed.
If you look at the patch, it's extremely straighforward, all it's doing is setting CPool and Pool *after* resetting TopDir instead of before. You can also do the steps on the reported bug and verify that it indeed happens, and cpool will be empty. In fact, you will have a directory structure created under /var/lib/backuppc, no matter what you set TopDir to.
There is also the Debian bug:
http://
But there they took a ridiculous approach of saying that if you want to do that, you should use a symbolic link in /var/lib/backuppc to wherever you want to move it, but that is ridiculous since it breaks the installed RPM (rpm --verify will point that out), and also, if that's the case, the possibility to redefine TopDir should be removed from the config.
I still think you should go ahead and apply the patch.