tags 546772 pending thanks I have removed the offending patch and will include this fix in the next uploaded version of this package.
As for the concerns about re-opening #508504, I have looked into this and do not believe it is a problem. When the file is not found, it sends zero as the timestamp to the server. The server sends back a valid timestamp which is correctly written to the file. Unfortunately, this does cause a single sync to fail when the timestamp file is not found because the server does not send any results when it receives a timestamp of zero. I believe this is a problem with the server and I am working with the upstream maintainer to release the source code for the server so that we can fix this issue and others. Thanks - Kyle Willmon -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
