DebuggingEvolution

Differences between revisions 1 and 2
⇤ ← Revision 1 as of 2007-09-04 17:09:20 →
Size: 4140
Editor: pool-71-170-39-244
Comment:
← Revision 2 as of 2007-09-04 18:52:26 → ⇥
Size: 5291
Editor: pool-71-170-39-244
Comment:
Deletions are marked like this. Additions are marked like this.
Line 7: Line 7:
 1. Evolution Data Server  '''1. Evolution Data Server'''
Line 9: Line 9:
    Source package:
        evolution-data-server
    Generated binary packages:
        evolution-data-server - evolution database backend server
        evolution-data-server-common - architecture independent files for Evolution Data Server
        evolution-data-server-dbg - evolution database backend server with debugging symbols
        evolution-data-server-dev - Development files for evolution-data-server (meta package)
        libcamel1.2-10 - The Evolution MIME message handling library
        libcamel1.2-dev - Development files for libcamel
        libebook1.2-9 - Client library for evolution address books
        libebook1.2-dev - Client library for evolution address books (development files)
        libecal1.2-7 - Client library for evolution calendars
        libecal1.2-dev - Client library for evolution calendars (development files)
        libedata-book1.2-2 - Backend library for evolution address books
        libedata-book1.2-dev - Backend library for evolution address books (development files)
        libedata-cal1.2-6 - Backend library for evolution calendars
        libedata-cal1.2-dev - Backend library for evolution calendars (development files)
        libedataserver1.2-9 - Utility library for evolution data servers
        libedataserver1.2-dev - Utility library for evolution data servers (development files)
        libedataserverui1.2-8 - GUI utility library for evolution data servers
        libedataserverui1.2-dev - GUI utility library for evolution data servers (development files
        libegroupwise1.2-13 - Client library for accessing groupwise POA through SOAP interface
        libegroupwise1.2-dev - Development files for libegroupwise
        libexchange-storage1.2-3 - Backend library for evolution calendars
        libexchange-storage1.2-dev - Backend library for evolution calendars (development files)   2. Evolution		     
         || evolution-data-server||evolution database backend server||
       ||evolution-data-server-common||architecture independent files for Evolution Data Server||
       ||evolution-data-server-dbg||evolution database backend server with debugging symbols||
       ||evolution-data-server-dev||Development files for evolution-data-server (meta package)||
       ||libcamel<version>||The Evolution MIME message handling library||
       ||libcamel<version>-dev||Development files for libcamel||
       ||libebook<version>||Client library for evolution address books||
       ||libebook<version>-dev||Client library for evolution address books (development files)||
       ||libecal<version>||Client library for evolution calendars||
       ||libecal<version>-dev||Client library for evolution calendars (development files)||
       ||libedata-book<version>||Backend library for evolution address books||
       ||libedata-book<version>-dev||Backend library for evolution address books (development files)||
       ||libedata-cal<version>||Backend library for evolution calendars||
       ||libedata-cal<version>-dev||Backend library for evolution calendars (development files)||
       ||libedataserver<version>||Utility library for evolution data servers||
       ||libedataserver<version>-dev||Utility library for evolution data servers (development files)||
       ||libedataserverui<version>||GUI utility library for evolution data servers||
       ||libedataserverui<version>-dev||GUI utility library for evolution data servers (development files)||
       ||libegroupwise<version>||Client library for accessing groupwise POA through SOAP interface||
       ||libegroupwise<version>-dev||Development files for libegroupwise||
       ||libexchange-storage<version>||Backend library for evolution calendars||
       ||libexchange-storage<version>-dev||Backend library for evolution calendars (development files)||
 ''' 2. Evolution'''
       ||evolution||groupware suite with mail client and organizer||
       ||evolution-common||architecture independent files for Evolution||
       ||evolution-dbg||debugging symbols for Evolution||
       ||evolution-dev||development library files for Evolution||
       ||evolution-plugins||standard plugins for Evolution||
       ||evolution-plugins-experimental||experimental plugins for Evolution||
 ''' 3. Evolution Exchange'''
       || evolution-exchange||Exchange plugin for the Evolution groupware suite||
Line 36: Line 43:
 1. User interface bugs - require a detailed description of the issue, steps to reproduce and screen captures where appropriate.
 1. Crasher bugs - Log files from the crash incident are required to track down these.
 1. Hardware specific bugs - The developers may not have access to the hardware that triggers this bug. Certain log files and command outputs can help
 1. Package selection - Help to find the right package (may be specific to category -- a bug filed as ubiquity may in fact be a casper d-i bug, an xorg bug may be an xorg-driver bug, etc.)		 Additionally, Evolution uses libgtkhtml3.14 to format HTML email (either for viewing or printing). There are many other packages that Evolution depends on, of course.
Line 43: Line 48:
Useful for bug-filers and as a boiler-plate advice for triagers. Bugs should be filled under the correct package -- so, for example, if you find a bug on libcamel, the correct package is Evolution-Data-Server, not Evolution. Nevertheless, if you are unsure -- but it is an Evolution* bug --, file it under any of the Evolution packages; we will, eventually, find the correct package and reassign the bug as needed.
Line 47: Line 53:
Specific to this type of package. First of all: try to identify what is wrong. We usually have bugs on:
 1. User interface - require a detailed description of the issue, steps to reproduce and screen captures where appropriate.
 1. Program crash - Log files from the crash incident are required to track down these.
 1. Incorrect results - for example, connection errors, deleted emails are not deleted, etc.
 1. Wishlists - a product feature that is either absent, or should be modified to suit the reporter's view of usability.
 1. Package selection - Help to find the right package (may be specific to category -- a bug filed as ubiquity may in fact be a casper d-i bug, an xorg bug may be an xorg-driver bug, etc.)

Introduction

What we generically call Evolution is in fact a collection of binary and source packages:

  • 1. Evolution Data Server

    • evolution-data-server

      evolution database backend server

      evolution-data-server-common

      architecture independent files for Evolution Data Server

      evolution-data-server-dbg

      evolution database backend server with debugging symbols

      evolution-data-server-dev

      Development files for evolution-data-server (meta package)

      libcamel<version>

      The Evolution MIME message handling library

      libcamel<version>-dev

      Development files for libcamel

      libebook<version>

      Client library for evolution address books

      libebook<version>-dev

      Client library for evolution address books (development files)

      libecal<version>

      Client library for evolution calendars

      libecal<version>-dev

      Client library for evolution calendars (development files)

      libedata-book<version>

      Backend library for evolution address books

      libedata-book<version>-dev

      Backend library for evolution address books (development files)

      libedata-cal<version>

      Backend library for evolution calendars

      libedata-cal<version>-dev

      Backend library for evolution calendars (development files)

      libedataserver<version>

      Utility library for evolution data servers

      libedataserver<version>-dev

      Utility library for evolution data servers (development files)

      libedataserverui<version>

      GUI utility library for evolution data servers

      libedataserverui<version>-dev

      GUI utility library for evolution data servers (development files)

      libegroupwise<version>

      Client library for accessing groupwise POA through SOAP interface

      libegroupwise<version>-dev

      Development files for libegroupwise

      libexchange-storage<version>

      Backend library for evolution calendars

      libexchange-storage<version>-dev

      Backend library for evolution calendars (development files)

    2. Evolution

    • evolution

      groupware suite with mail client and organizer

      evolution-common

      architecture independent files for Evolution

      evolution-dbg

      debugging symbols for Evolution

      evolution-dev

      development library files for Evolution

      evolution-plugins

      standard plugins for Evolution

      evolution-plugins-experimental

      experimental plugins for Evolution

    3. Evolution Exchange

    • evolution-exchange

      Exchange plugin for the Evolution groupware suite

Additionally, Evolution uses libgtkhtml3.14 to format HTML email (either for viewing or printing). There are many other packages that Evolution depends on, of course.

How to file

Bugs should be filled under the correct package -- so, for example, if you find a bug on libcamel, the correct package is Evolution-Data-Server, not Evolution. Nevertheless, if you are unsure -- but it is an Evolution* bug --, file it under any of the Evolution packages; we will, eventually, find the correct package and reassign the bug as needed.

Debugging procedure

First of all: try to identify what is wrong. We usually have bugs on:

  1. User interface - require a detailed description of the issue, steps to reproduce and screen captures where appropriate.
  2. Program crash - Log files from the crash incident are required to track down these.
  3. Incorrect results - for example, connection errors, deleted emails are not deleted, etc.
  4. Wishlists - a product feature that is either absent, or should be modified to suit the reporter's view of usability.
  5. Package selection - Help to find the right package (may be specific to category -- a bug filed as ubiquity may in fact be a casper d-i bug, an xorg bug may be an xorg-driver bug, etc.)

Known bugs

Description of known issues, how to recognise them and stock responses/actions.

Open

Bug#

Description

Action

[https://bugs.beta.launchpad.net/ubuntu/+source/synaptic/+bug/8896 #8896]

This bug can be identified by ...

Mark as duplicate of 8896 with the comment "Thank you for reporting. This issue has already been reported as bug #8896. Marking as Duplicate."

Closed

Bug#

Description

Action

[https://bugs.beta.launchpad.net/ubuntu/+source/synaptic/+bug/8896 #8896]

This bug can be identified by ...

Mark as duplicate of 8896 with the comment "Thank you for reporting. This issue has already been reported as bug #8896. Marking as Duplicate."

Non-bugs

How to recognise common issues arising from hardware failures, common feature requests and other invalid bugs for this category. Advice how triage them and stock responses.

Also see

CategoryBugSquad

DebuggingEvolution (last edited 2010-01-08 10:59:38 by eth0)