Update to 3.18 (remove controls needed for Unity and other desktops)

See https://bugzilla.gnome.org/show_bug.cgi?id=700070 for rationale on preferences removal

That's indeed a problem for us, they are dropping it because they have the controls in the new gnome-control-center privacy panel, we don't have that version though

3.10 is in debian, how difficult would it be to merge?

It would be trivial to merge and get an useless vino in return (since we don't have gnome-control-center 3.10 we wouldn't have any configuration interface)

I've proposed moving the Vino preferences into unity-control-center: lp:~robert-ancell/unity-control-center/screen-sharing

Now it's 3.18.

The update doesn't bring much out of dropping the standalone settings dialogs that are used out of GNOME

Is this done for xenial?

>Is this done for xenial?

No (at least not yet). See the versions available in different Ubuntu releases on the overview page https://launchpad.net/ubuntu/+source/vino

It is better to fork or stay at 3.8. I , for example use preference over ssh (with x11 forwarding) to setup vnc remotely. If preference is moved under unity-control-center, there will be no easy way to achieve this.

Note that Vino 3.8.1 bundles a very old libvncserver, with significant image quality problems. One example is attached to https://github.com/novnc/noVNC/issues/737

I do not object to forking 3.8.1, as long as the fork is updated to use the latest libvncserver.

the libvncserver copy doesn't seem to have been updated upstream either in newer versions, https://git.gnome.org/browse/vino/log/server/libvncserver

I looked into this today. The .desktop for the preferences dialog in Ubuntu's vino 3.8 has OnlyShowIn=GNOME;Unity; set so the removed preferences dialog really only affects Unity.

If the removed preferences dialog is not a blocker, we are good with merging vino 3.22 with Debian. The only remaining Ubuntu diff is enabling the system miniupnpc patch.

That patch was disabled in Debian in 2012 with this message:
"Disable 05_use-system-miniupnpc.patch for now, until we have a patch that is ready to be sent upstream and the Debian maintainer of miniupnpc has learned how to maintain a library package."

(The patch forces using the system miniupnpc library instead of making it optional which presumably makes it less interesting to upstream.)

I started a community topic for this update request at
https://community.ubuntu.com/t/update-vino-to-current-version-affects-unity/2537

This bug was fixed in the package vino - 3.22.0-2ubuntu1

---------------
vino (3.22.0-2ubuntu1) bionic; urgency=medium

  * Sync with Debian (LP: #1271358). Remaining change:
    - debian/control.in, debian/patches/05_use-system-miniupnpc.patch:
      + Build with system miniupnpc library

vino (3.22.0-2) unstable; urgency=medium

  * Drop unneeeded Suggests (gnome-user-guide, vinagre)
  * Bump Standards-Version to 4.1.2
  * Update Vcs fields for conversion to git
  * Add debian/gbp.conf
  * Bump debhelper compat to 11

vino (3.22.0-1) unstable; urgency=medium

  * New upstream release.

vino (3.21.92-2) unstable; urgency=medium

  * Add Build-Depends on gnome-common, required for autoreconf.
    (Closes: #837791)
  * Use a non-multiarch path for libexecdir as we did before the dh
    conversion.

vino (3.21.92-1) unstable; urgency=medium

  * New upstream development release.
  * Add Build-Depends on libice-dev and libsm-dev as per configure.ac.
  * Add Build-Depends on systemd on Linux to get the correct path for the
    systemd user unit directory.
  * Convert from cdbs to dh.
  * Enable all hardening build flags.
  * Bump debhelper compat level to 10.

vino (3.20.2-1) unstable; urgency=medium

  * New upstream release.
  * Bump debhelper compatibility level to 9.
  * Bump Standards-Version to 3.9.8.

vino (3.20.1-1) unstable; urgency=medium

  * New upstream release.
  * Drop obsolete Breaks and fix the version for the gnome-control-center
    Breaks.

vino (3.20.0-1) unstable; urgency=medium

  * New upstream release.
  * Bump Standards-Version to 3.9.7

vino (3.18.1-1) unstable; urgency=medium

  * New upstream release.

vino (3.18.0-1) unstable; urgency=medium

  * New upstream release.

vino (3.16.0-1) unstable; urgency=medium

  * New upstream release.
  * Drop Build-Depends on network-manager-dev and bump Build-Depends on
    libglib2.0-dev to (>= 2.32.0). Drop the obsolete configure switch
    accordingly. Vino now uses GNetworkMonitor rather than NetworkManager
    D-Bus interfaces.
  * Bump Standards-Version to 3.9.6. No further changes.
  * Update Homepage URL.

vino (3.14.0-2) unstable; urgency=low

  * Add gnome-control-center (<< 3.13.2) to Breaks.
    - previous versiones of g-c-c used the now removed "enabled" schema
      key in the sharing panel.

vino (3.14.0-1) unstable; urgency=medium

  * New upstream release.
  * Upload to unstable.

vino (3.13.90-1) experimental; urgency=medium

  * New upstream development release.
    - Note: no longer started by gnome-session, now by g-s-d sharing instead.
  * Have quilt refresh patches.
  * debian/rules: drop vino-server.desktop autostart file move since
    we're now started by gnome-settings-daemon sharing plugin instead
    so the file is no longer installed under /etc/xdg/autostart.

vino (3.12.0-2) unstable; urgency=medium

  * Build-depend against libgnutls28-dev and libgcrypt20-dev (Closes: #753164)
    - Instead of libgnutls-dev (gnutls26) and libgcrypt11-dev
  * Bump Standards-Version to 3.9.5

vino (3.12.0-1) unstable; urgency=medium

  * New upstream release.
  * Update build-dependencies according to configure.ac changes:
    - drop libsoup2.4
  * Make vino suggest ...

This bug was fixed in the package unity-control-center - 15.04.0+17.10.20171225-0ubuntu1

---------------
unity-control-center (15.04.0+17.10.20171225-0ubuntu1) bionic; urgency=medium

  [ Andrea Azzarone ]
  * sound: Discard selection-changed events that are not triggered
    by the user (lp: #1716359)

  [ Dale Beaudoin ]
  * version change 17.10 to 18.04 LTS

  [ Khurshid Alam ]
  * Merge Robert Ancell's Desktop Sharing panel since Vino
    no longer provides its own settings app (LP: #1271358)

 -- Jeremy Bicha <email address hidden> Mon, 25 Dec 2017 14:10:10 -0500

The change seems to be buggy, see bug #1741027, the panel is using the "enabled" gsettings key which has been removed from the vino schemas