Hi Jonathan, Since the testing autoremoval is kicking in, do you have a chance to take a look at this bug? Or is it okay for others to NMU and fix it?
Thanks, Boyuan Yang On Tue, 2 Mar 2021 11:00:51 +0100 Sebastian Ramacher <sramac...@debian.org> wrote: > Package: bluefish > Version: 2.2.12-1 > Severity: serious > X-Debbugs-Cc: sramac...@debian.org > > Between the version of bluefish in buster and bullsye, > /usr/share/bluefish/jsbeautifier moved from bluefish-data to bluefish. > However, bluefish does not have the corresponding Breaks and Replaces > reletionships defined to handle this properly and thus upgrades from > buster to bullseye fail: > | Preparing to unpack .../032-bluefish_2.2.12-1+b1_amd64.deb ... > | Unpacking bluefish (2.2.12-1+b1) over (2.2.10-1) ... > | dpkg: error processing archive /tmp/apt-dpkg-install-m8WUj5/032- bluefish_2.2.12-1+b1_amd64.deb (--unpack): > | trying to overwrite '/usr/share/bluefish/jsbeautifier/__init__.py', which is also in package bluefish-data 2.2.10-1 > | Preparing to unpack .../033-bluefish-data_2.2.12-1_all.deb ... > | Unpacking bluefish-data (2.2.12-1) over (2.2.10-1) ... > > Found via the buster to bullseye upgrade tests running on > jenkins.debian.net: > https://jenkins.debian.net/job/chroot-installation_buster_install_education-development_upgrade_to_bullseye/
signature.asc
Description: This is a digitally signed message part
