Bug#940686: buster-pu: package uim_1.8.8-4+deb10u2
On Thu, 2019-09-19 at 06:12 +0100, Adam D. Barratt wrote:
> Control: tags -1 + moreinfo
>
> On Thu, 2019-09-19 at 10:24 +0900, NOKUBI Takatsugu wrote:
> > We uim maintainers had a critical report #939588.
> > We made a transition package for libuim-data on buster, but
> > stretch's libuim-data package contains postrm and it causes
> > removing essential configration files.
> > So we made dummpy package and re-generate essential files on
> > postinst.
> >
> > I already uploaded it. And the following is debdiff:
>
> +uim (1:1.8.8-4+deb10u2) buster; urgency=medium
>
> That version is higher than the package in unstable, which is wrong.
>
> Moreover, the package obviously landed in NEW. I have asked ftp-
> master
> to reject it, partly due to the broken version number, but also
> please
> *do not* upload packages to {,old}stable that will involve NEW
> without
> an explicit ACK from the Release Team.
+Section: oldlibs
+Description: transitional package for uim-data
+ This is a transitional package. It will be removed next release.
Transitional packages in the "oldlibs" section should be intended to be
removable within the release containing them, not the one afterwards -
the usual pattern is for the transitional package to depend on its
replacement, so that it can indeed be removed - adding a hard
dependency from another package isn't very transitional.
What's your plan for bullseye? If the package is indeed intended to be
transitional then exactly the same scenario will occur once users
upgrade from buster to bullseye and then purge the package.
Regards,
Adam
Reply to: