Package: libreoffice-common Version: 4:24.2.1-3 Severity: serious User: debian...@lists.debian.org Usertags: piuparts fileconflict
Hi, during a test with piuparts I noticed your package fails to upgrade from 'testing'. It installed fine in 'testing', then the upgrade to 'sid' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): 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 ... If you add B+R now, you will also need to add them in the opposite direction once -evolutions gets reenabled. cheers, Andreas
libreoffice-evolution=4:24.2.0-1_libreoffice-common=4:24.2.1-3.log.gz
Description: application/gzip
