Bug#874739: stretch-pu: bluedevil/4:5.8.7-1+deb9u1
Control: tag -1 moreinfo
Hi Maxy,
I split this request up into individual per-package bugs. Let's start
with bluedevil.
On Mon, Jun 19, 2017 at 11:49:10 +0200, Maximiliano Curia wrote:
> bluedevil 4:5.8.4-1 currently in stretch to 4:5.8.7-1+deb9u1
> #########
>
> bluedevil (4:5.8.7-1+deb9u1) stretch; urgency=medium
>
> * Upload to stretch.
> * Document how to run bluedevil in in other DEs (Closes: 781012)
>
> -- Maximiliano Curia <maxy@debian.org> Sat, 17 Jun 2017 12:23:14 +0200
>
> bluedevil (4:5.8.7-1) unstable; urgency=medium
>
> * New upstream release (5.8.7).
> + ReceiveFileJob: Don't cancel the request right after accepting it
>
> KNotification::closed is emitted also when one of the notification
> actions was triggered.
>
> KDE#376773
>
> -- Maximiliano Curia <maxy@debian.org> Sun, 28 May 2017 18:35:52 +0200
>
> bluedevil (4:5.8.5-1) experimental; urgency=medium
>
> * New upstream release (5.8.5).
>
> -- Maximiliano Curia <maxy@debian.org> Fri, 30 Dec 2016 18:46:11 +0100
>
> The full debdiff is available in
> https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/bluedevil_5.8.4-1_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/bluedevil_5.8.4_5.8.7.upstream.gitlog
> https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/bluedevil_4:5.8.4-1_4:5.8.7-1+deb9u1.debian.diff
>
A couple of comments:
* Typo in debian/README.Debian, "This is service is provided by the
bluez-obexd package" has an "is" too many.
* The noise from po files getting regenerated is difficult to handle.
I see one fix to the german plasma_applet_org.kde.plasma.bluetooth.po,
addition of a Basque bluedevil.po, a change to the French bluedevil.po
that I'm not sure is accurate, more changes to the French
plasma_applet_org.kde.plasma.bluetooth.po, a change to the Brazilian
bluedevil.po
* The change to src/kded/bluedevil.json is also unreadable :(
One thing I'd like to see is a description of the user impact of the bug
being fixed here. We're talking an awful lot of diff churn for a single
fix here, so it'd be nice to have some actual justification.
Thanks,
Julien
Reply to: