Scans all your calendar data for buggy incidences.
Also prints some useful statistics like total inline attachment size.

In --fix mode, duplicate incidences ( with same payload ) will be deleted,
incidences with empty summary and description (and no attachments) are deleted
If invalid, DTSTART gets the value of DTEND, or current date if DTEND is invalid too.

A very common use case is to fix recurring to-dos that have a DTDUE but no DTSTART,
RFC doesn't allow this.

Scan with:
$ calendarjanitor

Scan and fix incidences:
$ calendarjanitor --fix

Backup your data first:
$ calendarjanitor --backup

CCMAIL: kde-pim@kde.org
**********************************************************************
Processing collection Sergio Martins calendar (id=567) ...
Checking for incidences with empty summary and description...          [OK]
Checking for incidences with empty UID...                              [OK]
Checking for events with invalid DTSTART...                            [OK]
Checking for recurring to-dos with invalid DTSTART...                  [OK]
Checking for journal with invalid DTSTART...                           [OK]
Checking for duplicate UIDs...                                         [OK]
Gathering statistics...

Events                                            : 516
Todos                                             : 52
Journal                                           : 175
Passed events and to-dos (>365 days)              : 431
Old incidences with alarms                        : 259
Inline attachments                                : 2
Total size of inline attachments (KB)             : 61
**********************************************************************