[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1065461: libreoffice-common: disabling libreoffice-evolution has moved evolocal.odb to libreoffice-common



Hi,

Am 05.03.24 um 00:47 schrieb Andreas Beckmann:
   Preparing to unpack .../libreoffice-common_4%3a24.2.1-3_all.deb ...
   Unpacking libreoffice-common (4:24.2.1-3) over (4:24.2.0-1) ...
   dpkg: error processing archive /var/cache/apt/archives/libreoffice-common_4%3a24.2.1-3_all.deb (--unpack):
    trying to overwrite '/usr/lib/libreoffice/presets/database/evolocal.odb', which is also in package libreoffice-evolution 4:24.2.0-1
   dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
   rmdir: failed to remove '/var/lib/libreoffice/share/prereg/': No such file or directory
   rmdir: failed to remove '/var/lib/libreoffice/share/': No such file or directory
   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
   rmdir: failed to remove '/var/lib/libreoffice': No such file or directory
   Errors were encountered while processing:
    /var/cache/apt/archives/libreoffice-common_4%3a24.2.1-3_all.deb

I'm not sure whether Breaks+Replaces are the correct solution here, or
whether -common should rather not ship the file regardless of (not)
building -evolution ...

The latter, imho.

ifeq "$(ENABLE_EVO2)" "y"
        mkdir -p $(PKGDIR)-evolution/$(OODIR)/presets/database
        mkdir -p $(PKGDIR)-evolution/$(OODIR)/share/registry
        mv $(PKGDIR)-common/$(OODIR)/presets/database/evolocal.odb \
                $(PKGDIR)-evolution/$(OODIR)/presets/database
else
        rm -f $(PKGDIR)-common/$(OODIR)/presets/database/evolocal.odb
endif

Added the else part just now.

If you add B+R now, you will also need to add them in the opposite
direction once -evolutions gets reenabled.

libphonenumber is fixed now, so I can re-enable it now and not have it blocking builds.


But I need to do the Replaces: libreoffice-common in -evolution anyways now?


Regards,


Rene


Reply to: