Hi again, Am 18.03.21 um 06:53 schrieb Rene Engelhard: > It would be helpful if you actually did your homework. There already was > 985297 so you now caused a bogus addditional RC bug. > > That bug even was marked as blocked by the dpkg bug so being careful > when reassigning RC bugs would actually be of help. > > Now I have two of them. (Yes, I know about merge but still it is wrong > to reassign llike this at all.)
Sorry for my tone this morning, but waking up with a RC bug more for this wasn't actually making me happy in any way. >>> Preparing to unpack .../3-libreoffice-common_1%3a7.0.4-3_all.deb ... >>> dpkg-maintscript-helper: error: file >>> '/usr/lib/libreoffice/share/registry/writer.xcd' not owned by package >>> 'libreoffice-common:all' >>> dpkg-maintscript-helper: error: directory >>> '/usr/lib/libreoffice/share/registry' contains files not owned by package >>> libreoffice-common:all, cannot switch to symlink >>> dpkg: error processing archive >>> /tmp/apt-dpkg-install-sERX6l/3-libreoffice-common_1%3a7.0.4-3_all.deb >>> (--unpack): >>> new libreoffice-common package pre-installation script subprocess >>> returned error exit status 1 >>> rmdir: failed to remove '/var/lib/libreoffice/program/': No such file or >>> directory >>> rmdir: failed to remove '/var/lib/libreoffice': No such file or directory >> The libreoffice-common preinst maintainer script fails, so I'd expect >> the installation for the package gets aborted and the conflictor does >> not get removed after this, and before processing the next archive. > > It fails because of > > dpkg-maintscript-helper: error: file > '/usr/lib/libreoffice/share/registry/writer.xcd' not owned by package > 'libreoffice-common:all' > dpkg-maintscript-helper: error: directory > '/usr/lib/libreoffice/share/registry' contains files not owned by package > libreoffice-common:all, cannot switch to symlink > > which is dpkg-maintscript-helpers domain. Actually I pondered filing a bug back then (wishlist) when I first saw this because I think dpkg should trust maintainers to do the right thing if they used dir_to_symlink and the ownership of the file changes. (That would also have saved the Conflicts) Is there a way to do that? Or some way to force it? Then I didn't actually do it and "just" added the Conflicts: (The symlink is only needed because of LO not honouring their own configuration so otherwise the config is not found - see #972043 and #969653) Regards, Rene
