Re: Entries not synced or with the wrong time
You should be able to build the more recent versions of gnome-pilot, such as gnome-pilot 2.32.0: http://ftp.gnome.org/pub/GNOME/sources/gnome-pilot/2.32/ However, these likely won't have fixed the conduit issues you mention. Those issues could, potentially, be due to recent changes in Evolution that have not been tracked by the conduits. What version of Evoution are you using? While you are debugging, it would be safest to set the sync mode to 'desktop overwrite PDA', so that at least you can trust the desktop :( Matt Matt Davey You will become one with the Universe next week, incurring mcda...@mrao.cam.ac.uk the wrath of all the Universe's old boyfriends. On Thu, 2011-01-20 at 08:52 +0100, Andreas Heinlein wrote: Hello, I have another problem with gnome-pilot sync'ing, and I hope you can help me again. Today I discovered on one of our palm devices that some appointments from evolution were missing on the handheld despite sync'ing multiple times. Even worse, on of the appointments existed on both sides, but with different times (6-8pm vs. 6:30-9pm). Even if these were both entered manually, they should have been treated as different appointments, I think. I then created another test appointment and sync'ed again, this entry was synced. I deleted it on the desktop and sync'ed once more, it was deleted from the palm, *and two, but not all of the other missing entries, were copied over*. I gave it another try and deleted the two xml files from ~/.evolution/calendar/local/system/*pilot*. This gave again duplicate entries on both sides, but all events were transferred this time. Only said entry with different times was overwritten, it now appeared twice with 6-8pm on both sides. I finally managed to clean up with deleting all duplicates on the desktop and doing a one-way sync to the palm. But the problem is: if there is the possibility that some appointments, possibly several weeks or even months in the future, are not sync'ed, the whole thing is next to useless. It was only by accident that I actually noticed this, it might as well have been a problem for the last weeks. Any idea how to deal with this? Is there any usable development version, or are these all only useful with GNOME 3? We are using 2.0.17 from Ubuntu 10.04 THanks, Andreas ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list
Re: Building gnome-pilot
Hi Colin, It would be great if you had some time to contribute. As you can tell, gnome-pilot is a bit time-starved at the moment. Any time I've had to spend over the last while (year+) has been spent trying to keep it up to date with the gnome3/gtk3 changes (which have been considerable). I'm glad you figured things out despite the poor instructions. It might have been easier for you to start with the most recent .tar.gz release, as this includes a 'configure' script, rather than requiring the 'autogen.sh' step which is required when building from the checked out repository. Hope this helps. What features are you interested in working on? Matt DaveyMany hands make light work - but mcda...@mrao.cam.ac.uk Too many cooks spoil the broth. On Sat, 2011-01-22 at 20:10 -0500, Colin Williams wrote: Hey, I thought I'd try to do a bit of development work on gnome-pilot, as I have a palm Z22 and the current release has some features missing that I really needed. Anyway, I'm trying to get the development version and build it, and I've run into several problems. Some of these may be my inexperience with the tools, but I was hoping somebody could give me a hand. First, I tried to clone the git repository, using the command on the site, and I got the following: $ git clone git://git.gnome.org/gnome-pilot/ Initialized empty Git repository in /home/lackita/Documents/gnome-pilot/.git/ git.gnome.org[0: 209.132.180.173]: errno=Connection timed out fatal: unable to connect a socket (Connection timed out) Not a big deal, I just switched the protocol to http and it worked fine. My first question: Was there some configuration problem I needed to fix with git, is the command on the site incorrect, or is there a configuration error with the git repository? Second, I tried to build the code. To my surprise, I could not find a configure file. I also could not find an INSTALL file, which was my fallback. The README appears to be woefully out of date (it still had me fetching from the cvs repository at cvs.gnu-designs.com) but ended up suggesting autogen.sh which is what I needed to get moving. I think this was my own inexperience for the most part, but the README could be organized a little better. Colin ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list
