Bug#1079267: discover: turn into transitional empty packages?
* Pascal Hambourg <pascal@plouf.fr.eu.org> [240822 11:36]:
> On 22/08/2024 at 09:09, Petter Reinholdtsen wrote:
> > [Chris Hofstaedtler]
> > > I don't know of any way of removing packages on upgrades from users
> > > systems, but at least the packages could become empty themselves.
> >
> > Perhaps we can turn them into empty packages, add a description
> > specifying that they are transitional packages, and in the next release
> > add a conflict from a often installed package on these transitional
> > packages to get them removed? Or will it work to let the transitional
> > discover package depend on some other package first, and then let the
> > other package conflict with discover in the next release?
>
> The release notes have paragraphs about obsolete packages after upgrade:
> <https://www.debian.org/releases/stable/amd64/release-notes/ch-upgrading.en.html#obsolete>
> <https://www.debian.org/releases/stable/amd64/release-notes/ch-information.en.html#noteworthy-obsolete-packages>
>
> Why not just remove the package from the archive (and mention it in release
> notes) ?
> How will it be different from any other obsolete package ?
It is different from almost all other packages by virtue of
a) being installed on all systems installed using d-i
b) there is no direct replacement for it that would take care of
replacing the binary packages on a default install.
Chris
Reply to: