Bug#1053377: ghostscript-x: ghostscript 10.02.0~dfsg-2 does not remove ghostscript-x 10.01.2~dfsg-1 automatically

[Alban Browaeys <prahal@yahoo.com>]

Package: ghostscript-x
Version: 10.01.2~dfsg-1
Severity: normal

Dear Maintainer,
when I attempt an upgrade, the ghostscript upgrade from  10.01.2~dfsg-1
to 10.02.0~dfsg-2 is on hold.
This is because I have ghostscript-x 10.01.2~dfsg-1 installed.

Looking at the dependencies in aptitude I see that 10.02.0~dfsg-2
conflict with any "ghostscript"  package != 10.01.2~dfsg-1
Also ghostscript 10.02.0~dfsg-2 does not conflict with ghostscript-x,
only replaces ghostscript-x (< 10.02.0~dfsg-1).

This is for unstable and testing.


I bet teh aim was to get rid of the ghostscript-x transitional package.

Best regards,
Alban



-- System Information:
Debian Release: trixie/sid
  APT prefers testing-debug
  APT policy: (500, 'testing-debug'), (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable-debug'), (500, 'oldstable-debug'), (500, 'oldoldstable'), (500, 'testing'), (500, 'stable'), (90, 'unstable-debug'), (90, 'unstable'), (1, 'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.4.0-4-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_BAD_PAGE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages ghostscript-x depends on:
ii  ghostscript  10.01.2~dfsg-1

ghostscript-x recommends no packages.

ghostscript-x suggests no packages.

-- no debconf information