User refresh should only happen when upgrading from broken versions

[Andreas Hasenack]

The final fix for https://bugs.launchpad.net/landscape-client/+bug/1508110 introduces a forced user refresh on landscape-client package upgrades. This refresh should only be triggered for upgrades that are happening from broken client releases, not *all*.

It should be a simple matter of guarding the fix with a dpkg --compare-versions call, similar to what already exists in the same file for another bug:
        # Check if we're upgrading from a D-Bus version like the client in the
        # lucid archives.
        if ! [ -z $2 ]; then
            if dpkg --compare-versions $2 lt 1.5.1; then
                # Launch a proxy service that will forward requests over DBus
                # from the old package-changer to the new AMP-based broker. This
                # is a one-off only needed for the DBus->AMP upgrade
                start-stop-daemon -x /usr/bin/landscape-dbus-proxy -b -c landscape -u landscape -S
            fi
         fi

[David Britton (dpb)]

What is in place is fine