Comment 2 for bug 82143

The current conflict generation seems quite okay for Ubuntu (it is more problematic with ".dfsg" string in the version number). If a rebuild is done, the field will be openoffice.org-core (>= 2.1.1), which should be a proper conflict for Feisty, ie. if anyone is trying to update OOo later on to 2.2 in Feisty (which is of course a bit unlikely), it will be noticed that a new OOo-voikko has to be built at the same time.

I think it should be fine for now, unless a failproof method to unregister/register every OOo extension when updating OOo is written, in which case a rebuild/reinstallation is not needed and the whole Conflicts-generation can be removed.