Bug#972696: vino: No longer developed has been moved to archive

Simon McVittie smcv at debian.org
Thu Oct 22 21:41:10 BST 2020


Control: forcemerge 972129 -1

On Thu, 22 Oct 2020 at 20:39:03 +0100, Nick Rhodes wrote:
> If there any action needed for Vino in Buster, it might be worth keeping
> this bug report open to work against (separate to #972129) , but happy for
> it to be marked as a duplicate.

I'm merging this with #972129, which is how the Debian bug tracking
system handles duplicates.

No action will be taken in buster unless there is a concrete problem with
vino that is sufficiently serious to either accept the regression risk
that comes with a fix, or seriously consider removing vino. The purpose
of stable is that we don't change it unless we really have to. If there
was a sufficiently serious problem, that would be a separate bug report.

Once a package is in a stable release, it's usually in that stable release
forever, regardless of whether its upstream developer has discontinued
maintenance. There are rare exceptions, but usually only for packages
that become completely useless, like clients for single-provider network
services that are no longer offered.

The upstream maintenance status only matters when we are deciding
whether to remove a package, and when we are deciding which packages
should be depended on or recommended by the metapackage, both of which
are normally only of interest for testing/unstable. For stable, those
decisions already had to be made before the stable release.

Seeparate bug reports for "the version in stable has problem x" and
"the version in testing/unstable has problem x" are very rarely useful,
because the bug tracking system has version-tracking, so we can mark
the same bug as inapplicable, broken or fixed in stable and testing
independently.

    smcv



More information about the pkg-gnome-maintainers mailing list