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

2020-10-22 Thread Simon McVittie
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 #

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

2020-10-22 Thread Nick Rhodes
Hi #972129 is marked important against the version of Vino in testing/unstable and makes sense to be at that level of severity as I suspect it will be considered for removal in Bullseye. If there any action needed for Vino in Buster, it might be worth keeping this bug report open to work aga

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

2020-10-22 Thread Patrice Duroux
Hi, I think this is reported by #972129 but with a different severity. Another point is that gnome metapackage still depends on it, should this be notified or handle somewhere? On Thu, 22 Oct 2020 17:58:19 +0100 Nick Rhodes wrote: > Package: vino > Severity: normal > > Dear Maintainer, > > L

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

2020-10-22 Thread Nick Rhodes
Package: vino Severity: normal Dear Maintainer, Looking at https://gitlab.gnome.org/Archive/vino/-/issues/7, states that Vino is no longer maintained and has been moved to archive. gnome-remote-desktop has been suggested as an alternative. -- System Information: Debian Release: 10.2 APT prefer