|
Bug causes corruption of backups
|
Aaron Kaplan
|
Sep 02, 2005 00:34 PDT
|
There's a bug in pilot-link 0.12.0-pre2 that causes databases backed up
with PilotManager's Backup conduit to be corrupted (more precisely, the
on-disk copy is corrupted; the version on the device remains valid, but
restoring from a backup may not work). As far as I know, this only
affects the Backup conduit; in any case it doesn't affect the conduits I
use regularly, which are SyncPlan, SyncMemo, and SyncBBDB. The same bug
also manifests itself in pilot-xfer, so you can't use that as a workaround.
The problem has been fixed in more recent pre-releases of pilot-link,
but unfortunately in the more recent versions the Perl bindings are
broken, so if you upgrade you won't be able to use PilotManager.
I will be working with the pilot-link maintainers to get the Perl
bindings up to speed with the recent changes, but it will probably be a
couple of weeks before I find the time. In the meantime, if you have
data on your device that need to be backed up, I recommend that you
install either version 0.11.8 (if you don't need libusb support) or the
current CVS version (if you do) of pilot-link, and use pilot-xfer from
one of those versions to backup your device outside of PilotManager. If
you want to continue using PilotManager for its non-Backup conduits, it
is possible to have two versions of pilot-link installed simultaneously,
by installing them in different locations and using the LD_LIBRARY_PATH
environment variable to select the one you need. Let me know if you
need help with this, or if you have other questions.
-Aaron
|
|
 |
|
