See #209131 for why update-catalog is run on upgrade. The infelicity is in the design of update-catalog. If catalogs are not removed and re-added on upgrade, then if a package's catalogs change on upgrade, the old ones will not be removed from the catalog file, and new ones won't be added.
I could change dh_installcatalogs, but would be inviting packages that use it to break in the future by doing so. It would be better to change update-catalog to use an interface for catalog registration similar to the ones used by update-menus, update-mime, scrollkeeper-update, update-desktop-database, etc. -- see shy jo
signature.asc
Description: Digital signature
