-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
This bug report confuses me. The blocking bug blames the libpisock8 to
libpisock9 transition. Now that is understandable because it is a LARGE
change.
This bug report deals only with one of the pilot-link conduits:
pilot-addresses *not* libpisock8|9 itself.
kpilot should only be calling libpisock itself, not trying to parse the
output of a pilot-link conduit (because it depends on libpisock, not
pilot-addresses) so I think that this is an incorrect block assignment.
Just because pilot-addresses no longer deals with certain addressbook
formats, does *not* mean that libpisock is to blame. The change in the
address handling on the Palm is completely independent of the
transition in libpisock.
I've tested with my own package, pilot-qof, and libpisock9 is perfectly
capable of syncing the addresses when called directly using the
libpisock9 API.
Yes, pilot-addresses is limited in it's current form but the original
bug in kpilot is far more likely to be caused by kpilot not making
sufficient upstream changes to migrate to the libpisock9 API.
libpisock8 was part of pilot-link 0.11 and pilot-link 0.12 took three
years to be released - there are significant changes, hence the API
change from 8 to 9.
I fail to see how 394534 can be blocked by 393792.
- --
Neil Williams
=============
http://www.data-freedom.org/
http://www.nosoftwarepatents.com/
http://www.linux.codehelp.co.uk/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
iD8DBQFFWatIk7DVr6iX/QIRAvLpAJ9UiwbZtEprwjIm2FQ3UWg/iWZLdgCeKRq+
wyYvc9V0yRWVMub6TVHGn5E=
=H5eP
-----END PGP SIGNATURE-----
