Package: php-composer-pcre Version: 3.1.0-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts fileconflict Control: affects -1 + src:composer
Hi, during a test with piuparts I noticed your package fails to upgrade from 'bullseye'. It installed fine in 'bullseye', then the upgrade to 'bookworm' 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 This was observed during an upgrade test of the composer package. From the attached log (scroll to the bottom...): Selecting previously unselected package php-composer-pcre. Preparing to unpack .../06-php-composer-pcre_3.1.0-1_all.deb ... Unpacking php-composer-pcre (3.1.0-1) ... dpkg: error processing archive /tmp/apt-dpkg-install-BF4xWr/06-php-composer-pcre_3.1.0-1_all.deb (--unpack): trying to overwrite '/usr/share/php/Composer/Pcre/MatchAllResult.php', which is also in package composer 2.0.9-2+deb11u2 This is a recent regression, most probably caused by this change in bullseye-pu: composer (2.0.9-2+deb11u2) bullseye; urgency=medium . [ David Prévot ] * Force system dependencies loading * Import Pcre I'd suggest to use "(<< 2.2)" as the version constraint as that seems to be the first composer version adding a (build-)dependency on php-composer-pcre (and thus no longer needing an embedded copy). (bookworm has composer 2.5.5.) cheers, Andreas
composer_2.5.5-1+deb12u1.log.gz
Description: application/gzip
