Introduction

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

1. Evolution Data Server
   • 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
3. User interface bugs - require a detailed description of the issue, steps to reproduce and screen captures where appropriate.
4. Crasher bugs - Log files from the crash incident are required to track down these.
5. Hardware specific bugs - The developers may not have access to the hardware that triggers this bug. Certain log files and command outputs can help
6. 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.)

How to file

Useful for bug-filers and as a boiler-plate advice for triagers.

Debugging procedure

Specific to this type of package.

Known bugs

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

Open

Closed

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

• DebuggingProcedures

CategoryBugSquad