Control: retitle -1 dpkg: Print package removal due to Conflicts Control: severity -1 normal
[ Changing title and lowering severity as I take this bug is now about the printing. ] Hi! On Fri, 2021-04-09 at 10:35:56 +0200, Andreas Beckmann wrote: > Control: reopen -1 > > On 08/04/2021 19.22, Guillem Jover wrote: > > > Otherwise, I don't see a bug in dpkg for this here. And I'd be > > > inclined to close this. > > I've managed to solve most of the upgrade paths by propagating some > Conflicts from libreoffice-common to libreoffice-core, s.t. the packages > get removed right away and are not deconfigured first (which causes the > Conflicts encountered later to be ignored). Ok, great! > What I see left for dpkg is the missing verboseness when it is actually > removing the conflicting package: > > Preparing to unpack .../0-ure_7.0.4-4~deb11anbe2_amd64.deb ... > Unpacking ure (1:7.0.4-4~deb11anbe2) over (6.1.5-3+deb10u7) ... > Preparing to unpack > .../1-libreoffice-style-colibre_7.0.4-4~deb11anbe2_all.deb ... > Unpacking libreoffice-style-colibre (1:7.0.4-4~deb11anbe2) over > (1:6.1.5-3+deb10u7) ... > dpkg: considering removing libreoffice-draw in favour of libreoffice-core > ... > dpkg: yes, will remove libreoffice-draw in favour of libreoffice-core > Preparing to unpack .../2-libreoffice-core_7.0.4-4~deb11anbe2_amd64.deb ... > Unpacking libreoffice-core (1:7.0.4-4~deb11anbe2) over (1:6.1.5-3+deb10u7) > ... > Preparing to unpack .../3-libreoffice-common_7.0.4-4~deb11anbe2_all.deb ... > Unpacking libreoffice-common (1:7.0.4-4~deb11anbe2) over > (1:6.1.5-3+deb10u7) ... > Selecting previously unselected package libreoffice-draw. > Preparing to unpack .../4-libreoffice-draw_7.0.4-4~deb11anbe2_amd64.deb ... > Unpacking libreoffice-draw (1:7.0.4-4~deb11anbe2) ... > > which makes it hard to understand the last failing case: Right, I'll add these in 1.21.x. > Removing libreoffice-style-tango (1:6.1.5-3+deb10u7) ... New run starts here. First package being processed. > dpkg: considering removing libreoffice-core in favour of libreoffice-common > ... > dpkg: yes, will remove libreoffice-core in favour of libreoffice-common > dpkg: considering removing libreoffice-draw in favour of libreoffice-common > ... > dpkg: yes, will remove libreoffice-draw in favour of libreoffice-common > dpkg: considering removing libreoffice-impress in favour of > libreoffice-common ... > dpkg: yes, will remove libreoffice-impress in favour of libreoffice-common > (Reading database ... > Preparing to unpack .../0-libreoffice-common_7.0.4-4~deb11anbe2_all.deb ... > De-configuring libreoffice-draw (1:6.1.5-3+deb10u7), to allow removal of > libreoffice-core (1:6.1.5-3+deb10u7) ... > De-configuring libreoffice-impress (1:6.1.5-3+deb10u7), to allow removal of > libreoffice-core (1:6.1.5-3+deb10u7) ... > dpkg-maintscript-helper: error: file > '/usr/lib/libreoffice/share/registry/ogltrans.xcd' not owned by package > 'libreoffice-common:all' > dpkg-maintscript-helper: error: file > '/usr/lib/libreoffice/share/registry/impress.xcd' not owned by package > 'libreoffice-common:all' > dpkg-maintscript-helper: error: file > '/usr/lib/libreoffice/share/registry/graphicfilter.xcd' not owned by package > 'libreoffice-common:all' > dpkg-maintscript-helper: error: file > '/usr/lib/libreoffice/share/registry/draw.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-1xO0pR/0-libreoffice-common_7.0.4-4~deb11anbe2_all.deb > (--unpack): > new libreoffice-common package pre-installation script subprocess returned > error exit status 1 The maintscript failed here so the queued removals didn't happen. > 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 Next package being processed. > Selecting previously unselected package libreoffice-draw. > dpkg: considering deconfiguration of libreoffice-common, which would be > broken by installation of libreoffice-draw ... > dpkg: yes, will deconfigure libreoffice-common (broken by libreoffice-draw) > dpkg: considering deconfiguration of libreoffice-core, which would be > broken by installation of libreoffice-draw ... > dpkg: yes, will deconfigure libreoffice-core (broken by libreoffice-draw) > Preparing to unpack .../1-libreoffice-draw_7.0.4-4~deb11anbe2_amd64.deb ... > De-configuring libreoffice-core (1:6.1.5-3+deb10u7) ... > De-configuring libreoffice-common (1:6.1.5-3+deb10u7) ... > Unpacking libreoffice-draw (1:7.0.4-4~deb11anbe2) over (1:6.1.5-3+deb10u7) > ... > Replacing files in old package libreoffice-core (1:6.1.5-3+deb10u7) ... > Replacing files in old package libreoffice-common (1:6.1.5-3+deb10u7) ... > Selecting previously unselected package libreoffice-core. > Preparing to unpack .../2-libreoffice-core_7.0.4-4~deb11anbe2_amd64.deb ... > Unpacking libreoffice-core (1:7.0.4-4~deb11anbe2) ... > Selecting previously unselected package libreoffice-impress. > Preparing to unpack .../3-libreoffice-impress_7.0.4-4~deb11anbe2_amd64.deb > ... > Unpacking libreoffice-impress (1:7.0.4-4~deb11anbe2) ... > Replacing files in old package libreoffice-common (1:6.1.5-3+deb10u7) ... > > Why is dpkg going to deconfigure some packages that it has scheduled > for removal? Reordering the removals should hopefully be sufficient. Before each package, dpkg clears all pending "is-to-be" queued actions, so because the first package failed, it understands there's no need to act on those, and because the new one requires de-configuration, then it does that here. > I'm not sure what makes libreoffice-impress so special that dpkg > wants to remove libreoffice-core in this case. I've already added > Conflicts against libreoffice-ogltrans (removed after buster), but I'll > try something else ... in a few hours after rebuilding again ... > (I'll send a patch to the other lo bug once I've a working solution) I've not checked the relationships to know why apt and dpkg decide on the current actions. But hope your new attempt is fruitful. :) Thanks, Guillem
