GnomePilot 0.1.48
- From: Eskil Heyn Olsen <deity dbc dk>
- To: gnome-announce-list gnome org
- cc: gnome pilot list <gnome-pilot-list gnome org>
- Subject: GnomePilot 0.1.48
- Date: Fri, 14 Jan 2000 01:08:59 +0100 (CET)
GnomePilot 0.1.48
* Availability
+ Development code available from the Gnome CVS server, this
release has tag GNOME_PILOT_0_1_48.
+ Also available from http://www.gnome.org/gnome-pilot/download
in .tar.gz, i386.rpm and .srpm form.
http://www.gnome.org/gnome-pilot/download/gnome-pilot-0.1.48.tar.gz
http://www.gnome.org/gnome-pilot/download/gnome-pilot-0.1.48-2.src.rpm
http://www.gnome.org/gnome-pilot/download/gnome-pilot-0.1.48-2.i386.rpm
http://www.gnome.org/gnome-pilot/download/gnome-pilot-devel-0.1.48-2.i386.rpm
* New since last release
+ SIGINT/timeout bug should be fixed.
* Stability
I still wish to point out, that parts of the synchronization code
is untested, since there still are no completely finished
conduits. However, the logic required by the existing conduits (eg.
the GnomeCalendar conduit) checks out ok.
* Additional notes
* Bug reporting
I am especially interested in bug reports reg. getting the package
up and running on a vanilla installation. This includes both
bugs, and suggestions for making installation easier.
If you encounter problems, please use bugs.gnome.org for bug
reporting, and remember to include the following (if possible);
+ Output from gpilotd. Eg. if you have problems with a
control-center applet, first do a killall -9 gpilotd, then run
gnomecc from a terminal, and capture all the output.
+ Stack traces, after gpilotd coredumps, do a echo where | gdb
`which gpilotd` core, grab the output and include in your bug
report, this makes it so much easier for me to find the error.
+ Even better, use bug-buddy to report bugs after a coredump.
/dev/eskil
---
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]