Quoting Simon McVittie (2022-10-24 13:24:07)
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: transition
X-Debbugs-Cc: dr@jones.dk
Forwarded: https://release.debian.org/transitions/html/auto-ghostscript.html
Affects: src:ghostscript src:gimp src:dvisvgm src:libspectre src:xfig
ghostscript appears to have started an unscheduled transition from libgs9
and libgs9-common to libgs10 and libgs-common. libgs-common Breaks and
Replaces libgs9-common, so the affected packages will all have to migrate
together.
Looking at ghostscript's changelog, it seems this might have been
accidental? There's no mention of the experimental version having been
intentionally re-uploaded to unstable.
https://release.debian.org/transitions/html/auto-ghostscript.html looks
like it is tracking the affected packages, so I haven't tried to write a
ben file for this.
Please coordinate with the release team to either finish or revert
this transition.
Sorry, I forgot to warn the release team ahead.
Ghostscript upstream has bumped its SONAME. There should be no breakage
(other than the kind of breakage already done in "9" releases, due to
security tightening of the internal Postscript interpreter), but yes it
requires a rebuild for those package directly linking with libgs.
I am frankly clueless about ben files and other transition magic, and
would appreciate if someone more skilled in the art can guide this
process.