I am currently having no problems running grive. I don't believe this
deserves a grave severity. Perhaps important.
Would it be possible to sync into an empty directory?
Another possibility would be to delete the .grive file and
re-authenticate (grive -a). I'm just guessing on the re-authentication.
But I'm wondering if, since it looks like it died on the authentication,
your current authentication token is somehow breaking things, given its
age. I believe that authentication requirements changed in the last year
or so.
It makes sense that it would fail in --dry-run mode as well as normal
mode, as it does the checks with the server to see what needs to be
synchronized, but stops before doing so.
Michael
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
