Bug#874742: stretch-pu: kscreenlocker/5.8.7-1+deb9u1

[Julien Cristau <jcristau@debian.org>]

Control: tag -1 confirmed

On Mon, Jun 19, 2017 at 11:49:10 +0200, Maximiliano Curia wrote:

> kscreenlocker 5.8.6-2 currently in stretch to 5.8.7-1+deb9u1
> #############
> 
> kscreenlocker (5.8.7-1+deb9u1) stretch; urgency=medium
> 
>   * Upload to stretch
> 
>  -- Maximiliano Curia <maxy@debian.org>  Mon, 19 Jun 2017 09:27:23 +0200
> 
> kscreenlocker (5.8.7-1) unstable; urgency=medium
> 
>   * New upstream release (5.8.7)
>      + Implement manual focus on click
>        Currently only the first created screenlock window gets focus.
>        On clicks, no focus events are sent, which makes it impossible to input
>        passwords. This patch now makes it possible to focus to a different
>        screenlock window (on a different monitor, for example) using a mouse
>        button press.
>        This should also fix newly created screenlock windows stealing the focus
>        of already displayed ones as only the first window gains automatic focus.
>        Fixes KDE#348789, KDE#374289
> 
>  -- Maximiliano Curia <maxy@debian.org>  Thu, 08 Jun 2017 17:14:31 +0200
> 
> The full debdiff is available in 
> https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/kscreenlocker_5.8.6-2_5.8.7-1+deb9u1.debdiff
> The full upstream gitlog and the diff for the debian packaging are:
> https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/kscreenlocker_5.8.6_5.8.7.upstream.gitlog
> https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/kscreenlocker_5.8.6-2_5.8.7-1+deb9u1.debian.diff
> 
One new German string and entire Basque translation on top of the focus
fix.  I guess that should be ok, assuming the fix is actually needed and
tested in stretch.

Cheers,
Julien