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

[Rene Engelhard <rene@debian.org>]

Hi again,

On Sun, Nov 18, 2018 at 01:54:20PM +0100, Rene Engelhard wrote:
> 
>        dpkg-divert --package $DPKG_MAINTSCRIPT_PACKAGE --add --rename \
> 
> is the call. So indeed, if $DPKG_MAINTSCRIPT_PACKAGE was empty... Now
> Good point.
> the question is why that happens Now the question is why that happens...

While looking for DPKG_MAINTSCRIPT_PACKAGE in dpkgs changelog I saw

dpkg (1.16.0) unstable; urgency=low

  [ Guillem Jover ]
  * Use DPKG_MAINTSCRIPT_PACKAGE environment variable as package name on
    dpkg-divert when no --package or --local options have been specified.
[...]

That doesn't explain why it wasn't set... TTBOMK dpkg sets it?

  Internal environment
[...]
       DPKG_MAINTSCRIPT_PACKAGE
              Defined by dpkg on the maintainer script environment to the (non-arch-qualified) package name being handled (since dpkg 1.14.17).
[...]

(man dpkg)

But so we can remove --package $DPKG_MAINTSCRIPT_PACKAGE without a risk anyway:
dpkg       | 1.16.18       | oldoldstable       | source, amd64, armel, armhf, i386, ia64, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390, s390x, sparc
(or at least it wouldn't be worse than before.)
or even write the package name out, as we know it...

Now that means we just need to fix eventually broken configurations "-add", though
I am not sure we should even attempt to do it in maintainer scripts and not let the
local admin do it.

Regards,
 
Rene