[ubuntu/xenial-proposed] update-manager 1:16.04.14 (Accepted)

[Balint Reczey]

update-manager (1:16.04.14) xenial; urgency=medium

  * Print transaction error and let the user try again applying updates
    (LP: #1317164)
  * Don't ask backend to do package operations aready done.
    Aptdaemon cancels the transaction when asked to remove packages already
    removed which results the failure being shown to the user. This
    is unnecessary as update-manager can just filter the package operations to
    be done using a fresh cache and decrease the likelyhood of hitting
    a race condition where packages to be removed are already removed.
    (LP: #1791931)

Date: Wed, 19 Sep 2018 09:18:52 +0200
Changed-By: Balint Reczey <rbalint at ubuntu.com>
Maintainer: Ubuntu Developers <ubuntu-devel-discuss at lists.ubuntu.com>
https://launchpad.net/ubuntu/+source/update-manager/1:16.04.14
-------------- next part --------------
Format: 1.8
Date: Wed, 19 Sep 2018 09:18:52 +0200
Source: update-manager
Binary: update-manager-core python3-update-manager update-manager update-manager-text update-manager-kde
Architecture: source
Version: 1:16.04.14
Distribution: xenial
Urgency: medium
Maintainer: Ubuntu Developers <ubuntu-devel-discuss at lists.ubuntu.com>
Changed-By: Balint Reczey <rbalint at ubuntu.com>
Description:
 python3-update-manager - python 3.x module for update-manager
 update-manager - GNOME application that manages apt updates
 update-manager-core - manage release upgrades
 update-manager-kde - Support modules for Muon Notifier and Apper
 update-manager-text - Text application that manages apt updates
Launchpad-Bugs-Fixed: 1317164 1791931
Changes:
 update-manager (1:16.04.14) xenial; urgency=medium
 .
   * Print transaction error and let the user try again applying updates
     (LP: #1317164)
   * Don't ask backend to do package operations aready done.
     Aptdaemon cancels the transaction when asked to remove packages already
     removed which results the failure being shown to the user. This
     is unnecessary as update-manager can just filter the package operations to
     be done using a fresh cache and decrease the likelyhood of hitting
     a race condition where packages to be removed are already removed.
     (LP: #1791931)
Checksums-Sha1:
 b13d7122b63e4eb9f6fde2512da493f784840178 2158 update-manager_16.04.14.dsc
 fcff81586f7dc36e86b52ff753f39381fc1b1fd6 3010910 update-manager_16.04.14.tar.gz
 fccf3c38a2b607d8344513586af2fdf535e09d07 11824 update-manager_16.04.14_source.buildinfo
Checksums-Sha256:
 611cde22dce1bb250291a21dbc8dde591b54d31c9e9f82fda3cac7e9d6b8468a 2158 update-manager_16.04.14.dsc
 5dc82d603e24e4a13a09c1dd1eccc50e12038e942ce8450cc8ce6923ccfb5296 3010910 update-manager_16.04.14.tar.gz
 ad089cd06c8dd264003446e4e81c8804c5debe4bd57632d3fc84c87bde22993b 11824 update-manager_16.04.14_source.buildinfo
Files:
 e54745d9f3217ab0758eb8679ef055ed 2158 gnome optional update-manager_16.04.14.dsc
 0cae8c6c596ddd25f9dd54aaea3f4bb9 3010910 gnome optional update-manager_16.04.14.tar.gz
 0e4176c4f16306320445627474a6975f 11824 gnome optional update-manager_16.04.14_source.buildinfo