Bug#912140: libreoffice-base,libreoffice-common: trying to overwrite '/usr/lib/libreoffice/share/basic/dialog.xlc', which is also in package libreoffice-{base,common} 1:5.2.7-1+deb9u3

[Axel Beckert <abe@debian.org>]

Hi again,

Axel Beckert wrote:
> When trying to fix this manually using "dpkg --purge --force-depends"
> to later use "apt install -f", libreoffice-base failed to purge due to
> some (seemingly broken) diversion. Here's my next try after
> libreoffice-common was already successfully purged:
> 
> root@localhost:~# dpkg --purge --force-depends libreoffice-base                   
> dpkg: libreoffice-base: dependency problems, but removing anyway as you requested:
>  libreoffice-report-builder-bin depends on libreoffice-base.
>  libreoffice depends on libreoffice-base.
> 
> (Reading database ... 63690 files and directories currently installed.)
> Removing libreoffice-base (1:5.2.7-1+deb9u4) ...
> dpkg-divert: error: mismatch on package
>   when removing 'diversion of /usr/lib/libreoffice/share/basic/dialog.xlc to /usr/lib/libreoffice/share/basic/dialog.xlc.noaccess by libreoffice-base'
>   found 'diversion of /usr/lib/libreoffice/share/basic/dialog.xlc to /usr/lib/libreoffice/share/basic/dialog.xlc.noaccess by --add'

Please note the "--add" in here.

In /var/lib/dpkg/diversions, the according entry had "--add" listed as
package name. I fixed the issue by replacing "--add" with
"libreoffice-base" and then the package could be purged.

So if there never was a dpkg-divert call in the libreoffice maintainer
scripts that was so broken that "--add" had been parsed as package
name, feel free to close this as locally misconfigured system. (I
though can imagine that by e.g. missing quotes around a shell
variable, this could happen if the variable with the package name was
empty for some reason.

P.S.: I have no idea about the history of that installation. It is
likely installed by a non-official image tailored for that hardware.
But since that hardware is only available since May 2018, I doubt that
any bug present in Testing/Unstable in 2014 could have been the cause
for this. IIRC, back then, the arm64 architecture even didn't exist at
all, at least the first arm64 build of firefox as well as chromium was
in 2016. So I doubt that issue from 2014 can be the cause for this.

		Regards, Axel
-- 
 ,''`.  |  Axel Beckert <abe@debian.org>, https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-    |  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE