Bug #1260041 “Unattended-Upgrades crashes with a dpkg error” : Bugs : unattended-upgrades package : Ubuntu

Revision history for this message

avius (avi142) wrote on 2013-12-11:

#1

Dependencies.txt Edit (1.7 KiB, text/plain; charset="utf-8")
ProcEnviron.txt Edit (125 bytes, text/plain; charset="utf-8")

Balint Reczey (rbalint) on 2018-07-19

description:

updated

Balint Reczey (rbalint) on 2018-07-19

Changed in unattended-upgrades (Ubuntu):
status:	New → Fix Released

Revision history for this message

Balint Reczey (rbalint) wrote on 2018-07-19:

#2

In Cosmic 1.4ubuntu1 fixed the issue:

* Unlock for dpkg operations with apt_pkg.pkgsystem_unlock_inner() when it
is available, also stop running when reacquiring the lock fails.
Thanks to to Julian Andres Klode for original partial patch

Revision history for this message

Łukasz Zemczak (sil2100) wrote on 2018-07-19: Please test proposed package

#3

Hello avius, or anyone else affected,

Accepted unattended-upgrades into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/unattended-upgrades/1.1ubuntu1.18.04.5 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Changed in unattended-upgrades (Ubuntu Bionic):
status:	New → Fix Committed
tags:	added: verification-needed verification-needed-bionic

Revision history for this message

Balint Reczey (rbalint) wrote on 2018-07-19:

#4

Download full text (3.6 KiB)

Verified the fix with 1.1ubuntu1.18.04.5:

root@uu-lock-bail:~# ./unattended-upgrade --dry-run --verbose
Initial blacklisted packages:
Initial whitelisted packages:
Starting unattended upgrades script
Allowed origins are: o=Ubuntu,a=bionic, o=Ubuntu,a=bionic-security, o=UbuntuESM,a=bionic
Option --dry-run given, *not* performing real actions
Packages that will be upgraded: apport bind9-host curl dirmngr distro-info-data dnsutils file git git-man gnupg gnupg-l10n gnupg-utils gpg gpg-agent gpg-wks-client gpg-wks-server gpgconf gpgsm gpgv libbind9-160 libcurl3-gnutls libcurl4 libdns-export1100 libdns1100 libgcrypt20 libirs160 libisc-export169 libisc169 libisccc160 libisccfg160 liblwres160 libmagic-mgc libmagic1 libperl5.26 libpng16-16 libpolkit-agent-1-0 libpolkit-backend-1-0 libpolkit-gobject-1-0 libprocps6 libssl1.0.0 libssl1.1 openssl perl perl-base perl-modules-5.26 policykit-1 procps python3-apport python3-problem-report wget
Writing dpkg log to /var/log/unattended-upgrades/unattended-upgrades-dpkg.log
/usr/bin/dpkg --status-fd 9 --no-triggers --unpack --auto-deconfigure /var/cache/apt/archives/distro-info-data_0.37ubuntu0.1_all.deb
/usr/bin/dpkg --status-fd 9 --configure --pending
Exception happened during upgrade.
Traceback (most recent call last):
  File "./unattended-upgrade", line 539, in cache_commit
    res = cache.commit(install_progress=iprogress)
  File "./unattended-upgrade", line 360, in __exit__
    apt_pkg.pkgsystem_lock()
apt_pkg.Error: E:Could not get lock /var/lib/dpkg/lock - open (11: Resource temporarily unavailable), E:Unable to lock the administration directory (/var/lib/dpkg/), is another process using it?
Exception happened during upgrade.
NoneType: None
Installing the upgrades failed!
error message: E:Could not get lock /var/lib/dpkg/lock - open (11: Resource temporarily unavailable), E:Unable to lock the administration directory (/var/lib/dpkg/), is another process using it?
dpkg returned a error! See /var/log/unattended-upgrades/unattended-upgrades-dpkg.log for details
root@uu-lock-bail:~# dpkg -l unattended-upgrades | cat
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-===================-==================-============-===========================================

# while sleep 0.1; do python3 -c 'import apt, apt_pkg, time; print(apt_pkg.pkgsystem_lock()); time.sleep(2)' ; done
Traceback (most recent call last):
  File "<string>", line 1, in <module>
apt_pkg.Error: E:Could not get lock /var/lib/dpkg/lock - open (11: Resource temporarily unavailable), E:Unable to lock the administration directory (/var/lib/dpkg/), is another process using it?
...
Traceback (most recent call last):
  File "<string>", line 1, in <module>
apt_pkg.Error: E:Could not get lock /var/lib/dpkg/lock - open (11: Resource temporarily unavailable), E:Unable to lock the administration directory (/var/lib/dpkg/), is another process using it?
Traceback (most recent call last):
  File "<string>", line 1, in <module>
apt_pkg.Error: E:Could not ...

Tested with 0.90ubuntu0.10 (not fixed) and 1.1ubuntu1.18.04.7~16.04.1 (fixed):

With the not fixed version the lock is lost by u-u, while u-u kept running:
...
SystemError: E:Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource temporarily unavailable), E:Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it?
Traceback (most recent call last):
  File "<string>", line 1, in <module>
SystemError: E:Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource temporarily unavailable), E:Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it?
Traceback (most recent call last):
  File "<string>", line 1, in <module>
SystemError: E:Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource temporarily unavailable), E:Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it?
True
True
True
True
True
True
True
True
True
True
...

With the fixed version but keeping unfixed python-apt the lock is still lost by u-u, but u-u crashes. This is expected and is safer than the unfixed behaviour:
...
conffile line: /etc/rsyslog.d/21-cloudinit.conf d4cf2e5d3cb9914cf7e6cdc08d298339
current md5: d4cf2e5d3cb9914cf7e6cdc08d298339
blacklist: []
whitelist: []
Option --dry-run given, *not* performing real actions
Packages that will be upgraded: cloud-init curl kmod libc-bin libc6 libcurl3-gnutls libkmod2 locales multiarch-support python-apt-common python3-apt snapd ubuntu-core-launcher
Writing dpkg log to /var/log/unattended-upgrades/unattended-upgrades-dpkg.log
applying set ['python-apt-common']
/usr/bin/dpkg --status-fd 9 --unpack --auto-deconfigure /var/cache/apt/archives/python-apt-common_1.1.0~beta1ubuntu0.16.04.3_all.deb 
/usr/bin/dpkg --status-fd 11 --configure python-apt-common:all 
/usr/bin/dpkg --status-fd 13 --configure --pending 
Exception happened during upgrade.
Traceback (most recent call last):
  File "/usr/bin/unattended-upgrade", line 374, in __exit__
    apt_pkg.pkgsystem_lock_inner()
AttributeError: module 'apt_pkg' has no attribute 'pkgsystem_lock_inner'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/bin/unattended-upgrade", line 558, in cache_commit
    res = cache.commit(install_progress=iprogress)
  File "/usr/bin/unattended-upgrade", line 376, in __exit__
    apt_pkg.pkgsystem_lock()
SystemError: E:Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource temporarily unavailable), E:Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it?
Exception happened during upgrade.
NoneType
Installing the upgrades failed!
error message: E:Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource temporarily unavailable), E:Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it?
dpkg returned a error! See /var/log/unattended-upgrades/unattended-upgrades-dpkg.log for details
InstCount=0 DelCount=0 BrokenCount=0
root@x-uu:~#

With both u-u and python-apt fixed u-u keeps the lock for the whole run:
...
SystemError: E:Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource temporarily unavailable), E:Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it?
Traceback (most recent call last):
  File "<string>", line 1, in <module>
SystemError: E:Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource temporarily unavailable), E:Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it?
Traceback (most recent call last):
  File "<string>", line 1, in <module>
SystemError: E:Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource temporarily unavailable), E:Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it?

Traceback (most recent call last):
  File "<string>", line 1, in <module>
SystemError: E:Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource temporarily unavailable), E:Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it?
True
True
...

...
Writing dpkg log to /var/log/unattended-upgrades/unattended-upgrades-dpkg.log
applying set ['python-apt-common']
/usr/bin/dpkg --status-fd 9 --unpack --auto-deconfigure /var/cache/apt/archives/python-apt-common_1.1.0~beta1ubuntu0.16.04.3_all.deb 
/usr/bin/dpkg --status-fd 11 --configure python-apt-common:all 
/usr/bin/dpkg --status-fd 13 --configure --pending 
left to upgrade {'libc-bin', 'libcurl3-gnutls', 'libkmod2', 'curl', 'libc6', 'ubuntu-core-launcher', 'multiarch-support', 'snapd', 'locales', 'kmod', 'cloud-init'}
applying set ['libc-bin']
/usr/bin/dpkg --status-fd 9 --unpack --auto-deconfigure /var/cache/apt/archives/libc-bin_2.23-0ubuntu11_amd64.deb 
/usr/bin/dpkg --status-fd 11 --configure libc-bin:amd64 
/usr/bin/dpkg --status-fd 13 --configure --pending 
left to upgrade {'libcurl3-gnutls', 'libkmod2', 'curl', 'libc6', 'ubuntu-core-launcher', 'multiarch-support', 'kmod', 'locales', 'snapd', 'cloud-init'}
applying set ['libc6']
Preconfiguring packages ...
/usr/bin/dpkg --status-fd 9 --unpack --auto-deconfigure /var/cache/apt/archives/libc6_2.23-0ubuntu11_amd64.deb 
/usr/bin/dpkg --status-fd 11 --configure libc6:amd64 
/usr/bin/dpkg --status-fd 13 --configure --pending 
left to upgrade {'libcurl3-gnutls', 'libkmod2', 'curl', 'ubuntu-core-launcher', 'multiarch-support', 'snapd', 'locales', 'kmod', 'cloud-init'}
applying set ['multiarch-support']
/usr/bin/dpkg --status-fd 9 --unpack --auto-deconfigure /var/cache/apt/archives/multiarch-support_2.23-0ubuntu11_amd64.deb 
/usr/bin/dpkg --status-fd 11 --configure multiarch-support:amd64 
/usr/bin/dpkg --status-fd 13 --configure --pending 
left to upgrade {'libcurl3-gnutls', 'libkmod2', 'curl', 'ubuntu-core-launcher', 'kmod', 'locales', 'snapd', 'cloud-init'}
applying set ['locales']
Preconfiguring packages ...
/usr/bin/dpkg --status-fd 9 --unpack --auto-deconfigure /var/cache/apt/archives/locales_2.23-0ubuntu11_all.deb 
/usr/bin/dpkg --status-fd 11 --configure locales:all 
/usr/bin/dpkg --status-fd 13 --configure --pending 
left to upgrade {'libcurl3-gnutls', 'libkmod2', 'curl', 'ubuntu-core-launcher', 'snapd', 'kmod', 'cloud-init'}
applying set ['cloud-init']
Preconfiguring packages ...
/usr/bin/dpkg --status-fd 9 --unpack --auto-deconfigure /var/cache/apt/archives/cloud-init_18.5-21-g8ee294d5-0ubuntu1~16.04.1_all.deb 
/usr/bin/dpkg --status-fd 11 --configure cloud-init:all 
/usr/bin/dpkg --status-fd 13 --configure --pending 
left to upgrade {'libcurl3-gnutls', 'libkmod2', 'curl', 'ubuntu-core-launcher', 'snapd', 'kmod'}
applying set ['snapd', 'ubuntu-core-launcher']
/usr/bin/dpkg --status-fd 9 --unpack --auto-deconfigure /var/cache/apt/archives/ubuntu-core-launcher_2.37.1_amd64.deb /var/cache/apt/archives/snapd_2.37.1_amd64.deb 
/usr/bin/dpkg --status-fd 11 --configure snapd:amd64 ubuntu-core-launcher:amd64 
/usr/bin/dpkg --status-fd 13 --configure --pending 
left to upgrade {'libkmod2', 'curl', 'kmod', 'libcurl3-gnutls'}
applying set ['libkmod2', 'kmod']
/usr/bin/dpkg --status-fd 9 --unpack --auto-deconfigure /var/cache/apt/archives/kmod_22-1ubuntu5.2_amd64.deb /var/cache/apt/archives/libkmod2_22-1ubuntu5.2_amd64.deb 
/usr/bin/dpkg --status-fd 11 --configure libkmod2:amd64 kmod:amd64 
/usr/bin/dpkg --status-fd 13 --configure --pending 
left to upgrade {'curl', 'libcurl3-gnutls'}
applying set ['curl', 'libcurl3-gnutls']
/usr/bin/dpkg --status-fd 9 --unpack --auto-deconfigure /var/cache/apt/archives/curl_7.47.0-1ubuntu2.12_amd64.deb /var/cache/apt/archives/libcurl3-gnutls_7.47.0-1ubuntu2.12_amd64.deb 
/usr/bin/dpkg --status-fd 11 --configure libcurl3-gnutls:amd64 curl:amd64 
/usr/bin/dpkg --status-fd 13 --configure --pending 
left to upgrade set()
All upgrades installed
InstCount=0 DelCount=0 BrokenCount=0
root@x-uu:~#

tags:

added: verification-done verification-done-xenial
removed: verification-needed verification-needed-xenial

Revision history for this message

Łukasz Zemczak (sil2100) wrote on 2019-02-28:

#10

Hello avius, or anyone else affected,

Accepted unattended-upgrades into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/unattended-upgrades/1.1ubuntu1.18.04.7~16.04.2 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

tags:

added: verification-needed verification-needed-xenial
removed: verification-done verification-done-xenial

Revision history for this message

Balint Reczey (rbalint) wrote on 2019-03-13:

#11

Download full text (20.8 KiB)

Tested with 1.1ubuntu1.18.04.7~16.04.2 on Xenial:

root@x-uu-lp-1260041:~# unattended-upgrade --dry-run --verbose --debug
Initial blacklisted packages:
Initial whitelisted packages:
Starting unattended upgrades script
Allowed origins are: o=Ubuntu,a=xenial, o=Ubuntu,a=xenial-security, o=UbuntuESM,a=xenial, o=Ubuntu,a=xenial-updates
Using (^linux-image-[0-9]+\.[0-9\.]+-.*|^linux-headers-[0-9]+\.[0-9\.]+-.*|^linux-image-extra-[0-9]+\.[0-9\.]+-.*|^linux-modules-[0-9]+\.[0-9\.]+-.*|^linux-modules-extra-[0-9]+\.[0-9\.]+-.*|^linux-signed-image-[0-9]+\.[0-9\.]+-.*|^kfreebsd-image-[0-9]+\.[0-9\.]+-.*|^kfreebsd-headers-[0-9]+\.[0-9\.]+-.*|^gnumach-image-[0-9]+\.[0-9\.]+-.*|^.*-modules-[0-9]+\.[0-9\.]+-.*|^.*-kernel-[0-9]+\.[0-9\.]+-.*|^linux-backports-modules-.*-[0-9]+\.[0-9\.]+-.*|^linux-modules-.*-[0-9]+\.[0-9\.]+-.*|^linux-tools-[0-9]+\.[0-9\.]+-.*|^linux-cloud-tools-[0-9]+\.[0-9\.]+-.*) regexp to find kernel packages
Using (^linux-image-4\.18\.0\-16\-generic$|^linux-headers-4\.18\.0\-16\-generic$|^linux-image-extra-4\.18\.0\-16\-generic$|^linux-modules-4\.18\.0\-16\-generic$|^linux-modules-extra-4\.18\.0\-16\-generic$|^linux-signed-image-4\.18\.0\-16\-generic$|^kfreebsd-image-4\.18\.0\-16\-generic$|^kfreebsd-headers-4\.18\.0\-16\-generic$|^gnumach-image-4\.18\.0\-16\-generic$|^.*-modules-4\.18\.0\-16\-generic$|^.*-kernel-4\.18\.0\-16\-generic$|^linux-backports-modules-.*-4\.18\.0\-16\-generic$|^linux-modules-.*-4\.18\.0\-16\-generic$|^linux-tools-4\.18\.0\-16\-generic$|^linux-cloud-tools-4\.18\.0\-16\-generic$) regexp to find running kernel packages
Checking: cloud-init ([<Origin component:'main' archive:'xenial-proposed' origin:'Ubuntu' label:'Ubuntu' site:'archive.ubuntu.com' isTrusted:True>])
adjusting candidate version: cloud-init=18.5-21-g8ee294d5-0ubuntu1~16.04.1
Checking: distro-info-data ([<Origin component:'main' archive:'xenial-proposed' origin:'Ubuntu' label:'Ubuntu' site:'archive.ubuntu.com' isTrusted:True>])
pkg distro-info-data not in allowed origin
sanity check failed
Checking: libpam-systemd ([<Origin component:'main' archive:'xenial-updates' origin:'Ubuntu' label:'Ubuntu' site:'archive.ubuntu.com' isTrusted:True>])
Checking: libsystemd0 ([<Origin component:'main' archive:'xenial-updates' origin:'Ubuntu' label:'Ubuntu' site:'archive.ubuntu.com' isTrusted:True>])
Checking: libudev1 ([<Origin component:'main' archive:'xenial-updates' origin:'Ubuntu' label:'Ubuntu' site:'archive.ubuntu.com' isTrusted:True>])
Checking: snapd ([<Origin component:'main' archive:'xenial-proposed' origin:'Ubuntu' label:'Ubuntu' site:'archive.ubuntu.com' isTrusted:True>])
adjusting candidate version: snapd=2.34.2ubuntu0.1
Checking: systemd ([<Origin component:'main' archive:'xenial-updates' origin:'Ubuntu' label:'Ubuntu' site:'archive.ubuntu.com' isTrusted:True>])
Checking: systemd-sysv ([<Origin component:'main' archive:'xenial-updates' origin:'Ubuntu' label:'Ubuntu' site:'archive.ubuntu.com' isTrusted:True>])
Checking: ubuntu-core-launcher ([<Origin component:'main' archive:'xenial-proposed' origin:'Ubuntu' label:'Ubuntu' site:'archive.ubuntu.com' isTrusted:True>])
adjusting candidate version: ubuntu-core-launcher=2.34.2ubuntu0.1
Checking: udev ([<Origi...

Tested with 1.1ubuntu1.18.04.7~16.04.2 on Xenial:

root@x-uu-lp-1260041:~# unattended-upgrade --dry-run --verbose --debug
Initial blacklisted packages: 
Initial whitelisted packages: 
Starting unattended upgrades script
Allowed origins are: o=Ubuntu,a=xenial, o=Ubuntu,a=xenial-security, o=UbuntuESM,a=xenial, o=Ubuntu,a=xenial-updates
Using (^linux-image-[0-9]+\.[0-9\.]+-.*|^linux-headers-[0-9]+\.[0-9\.]+-.*|^linux-image-extra-[0-9]+\.[0-9\.]+-.*|^linux-modules-[0-9]+\.[0-9\.]+-.*|^linux-modules-extra-[0-9]+\.[0-9\.]+-.*|^linux-signed-image-[0-9]+\.[0-9\.]+-.*|^kfreebsd-image-[0-9]+\.[0-9\.]+-.*|^kfreebsd-headers-[0-9]+\.[0-9\.]+-.*|^gnumach-image-[0-9]+\.[0-9\.]+-.*|^.*-modules-[0-9]+\.[0-9\.]+-.*|^.*-kernel-[0-9]+\.[0-9\.]+-.*|^linux-backports-modules-.*-[0-9]+\.[0-9\.]+-.*|^linux-modules-.*-[0-9]+\.[0-9\.]+-.*|^linux-tools-[0-9]+\.[0-9\.]+-.*|^linux-cloud-tools-[0-9]+\.[0-9\.]+-.*) regexp to find kernel packages
Using (^linux-image-4\.18\.0\-16\-generic$|^linux-headers-4\.18\.0\-16\-generic$|^linux-image-extra-4\.18\.0\-16\-generic$|^linux-modules-4\.18\.0\-16\-generic$|^linux-modules-extra-4\.18\.0\-16\-generic$|^linux-signed-image-4\.18\.0\-16\-generic$|^kfreebsd-image-4\.18\.0\-16\-generic$|^kfreebsd-headers-4\.18\.0\-16\-generic$|^gnumach-image-4\.18\.0\-16\-generic$|^.*-modules-4\.18\.0\-16\-generic$|^.*-kernel-4\.18\.0\-16\-generic$|^linux-backports-modules-.*-4\.18\.0\-16\-generic$|^linux-modules-.*-4\.18\.0\-16\-generic$|^linux-tools-4\.18\.0\-16\-generic$|^linux-cloud-tools-4\.18\.0\-16\-generic$) regexp to find running kernel packages
Checking: cloud-init ([<Origin component:'main' archive:'xenial-proposed' origin:'Ubuntu' label:'Ubuntu' site:'archive.ubuntu.com' isTrusted:True>])
adjusting candidate version: cloud-init=18.5-21-g8ee294d5-0ubuntu1~16.04.1
Checking: distro-info-data ([<Origin component:'main' archive:'xenial-proposed' origin:'Ubuntu' label:'Ubuntu' site:'archive.ubuntu.com' isTrusted:True>])
pkg distro-info-data not in allowed origin
sanity check failed
Checking: libpam-systemd ([<Origin component:'main' archive:'xenial-updates' origin:'Ubuntu' label:'Ubuntu' site:'archive.ubuntu.com' isTrusted:True>])
Checking: libsystemd0 ([<Origin component:'main' archive:'xenial-updates' origin:'Ubuntu' label:'Ubuntu' site:'archive.ubuntu.com' isTrusted:True>])
Checking: libudev1 ([<Origin component:'main' archive:'xenial-updates' origin:'Ubuntu' label:'Ubuntu' site:'archive.ubuntu.com' isTrusted:True>])
Checking: snapd ([<Origin component:'main' archive:'xenial-proposed' origin:'Ubuntu' label:'Ubuntu' site:'archive.ubuntu.com' isTrusted:True>])
adjusting candidate version: snapd=2.34.2ubuntu0.1
Checking: systemd ([<Origin component:'main' archive:'xenial-updates' origin:'Ubuntu' label:'Ubuntu' site:'archive.ubuntu.com' isTrusted:True>])
Checking: systemd-sysv ([<Origin component:'main' archive:'xenial-updates' origin:'Ubuntu' label:'Ubuntu' site:'archive.ubuntu.com' isTrusted:True>])
Checking: ubuntu-core-launcher ([<Origin component:'main' archive:'xenial-proposed' origin:'Ubuntu' label:'Ubuntu' site:'archive.ubuntu.com' isTrusted:True>])
adjusting candidate version: ubuntu-core-launcher=2.34.2ubuntu0.1
Checking: udev ([<Origin component:'main' archive:'xenial-updates' origin:'Ubuntu' label:'Ubuntu' site:'archive.ubuntu.com' isTrusted:True>])
pkgs that look like they should be upgraded: libpam-systemd
libsystemd0
libudev1
systemd
systemd-sysv
udev
Fetched 0 B in 0s (0 B/s)                                                                                                                                                    
fetch.run() result: 0
<apt_pkg.AcquireItem object:Status: 2 Complete: 1 Local: 1 IsTrusted: 1 FileSize: 11468 DestFile:'/var/cache/apt/archives/systemd-sysv_229-4ubuntu21.17_amd64.deb' DescURI: 'http://archive.ubuntu.com/ubuntu/pool/main/s/systemd/systemd-sysv_229-4ubuntu21.17_amd64.deb' ID:0 ErrorText: ''>
check_conffile_prompt(/var/cache/apt/archives/systemd-sysv_229-4ubuntu21.17_amd64.deb)
found pkg: systemd-sysv
No conffiles in deb /var/cache/apt/archives/systemd-sysv_229-4ubuntu21.17_amd64.deb (There is no member named 'conffiles')
<apt_pkg.AcquireItem object:Status: 2 Complete: 1 Local: 1 IsTrusted: 1 FileSize: 115114 DestFile:'/var/cache/apt/archives/libpam-systemd_229-4ubuntu21.17_amd64.deb' DescURI: 'http://archive.ubuntu.com/ubuntu/pool/main/s/systemd/libpam-systemd_229-4ubuntu21.17_amd64.deb' ID:0 ErrorText: ''>
check_conffile_prompt(/var/cache/apt/archives/libpam-systemd_229-4ubuntu21.17_amd64.deb)
found pkg: libpam-systemd
No conffiles in deb /var/cache/apt/archives/libpam-systemd_229-4ubuntu21.17_amd64.deb (There is no member named 'conffiles')
<apt_pkg.AcquireItem object:Status: 2 Complete: 1 Local: 1 IsTrusted: 1 FileSize: 204002 DestFile:'/var/cache/apt/archives/libsystemd0_229-4ubuntu21.17_amd64.deb' DescURI: 'http://archive.ubuntu.com/ubuntu/pool/main/s/systemd/libsystemd0_229-4ubuntu21.17_amd64.deb' ID:0 ErrorText: ''>
check_conffile_prompt(/var/cache/apt/archives/libsystemd0_229-4ubuntu21.17_amd64.deb)
found pkg: libsystemd0
No conffiles in deb /var/cache/apt/archives/libsystemd0_229-4ubuntu21.17_amd64.deb (There is no member named 'conffiles')
<apt_pkg.AcquireItem object:Status: 2 Complete: 1 Local: 1 IsTrusted: 1 FileSize: 3813730 DestFile:'/var/cache/apt/archives/systemd_229-4ubuntu21.17_amd64.deb' DescURI: 'http://archive.ubuntu.com/ubuntu/pool/main/s/systemd/systemd_229-4ubuntu21.17_amd64.deb' ID:0 ErrorText: ''>
check_conffile_prompt(/var/cache/apt/archives/systemd_229-4ubuntu21.17_amd64.deb)
found pkg: systemd
conffile line: /etc/dbus-1/system.d/org.freedesktop.hostname1.conf f55c94d000b5d62b5f06d38852977dd1
current md5: f55c94d000b5d62b5f06d38852977dd1
conffile line: /etc/dbus-1/system.d/org.freedesktop.locale1.conf 5893ab03e7e96aa3759baceb4dd04190
current md5: 5893ab03e7e96aa3759baceb4dd04190
conffile line: /etc/dbus-1/system.d/org.freedesktop.login1.conf 4aac4fe1a99c9fca83c85b80e4e0c2ba
current md5: 4aac4fe1a99c9fca83c85b80e4e0c2ba
conffile line: /etc/dbus-1/system.d/org.freedesktop.network1.conf 162e9a90d8f824f79ef2c6390827ec7b
current md5: 162e9a90d8f824f79ef2c6390827ec7b
conffile line: /etc/dbus-1/system.d/org.freedesktop.resolve1.conf 6969148b4616c56a5c9065cec5ab0775
current md5: 6969148b4616c56a5c9065cec5ab0775
conffile line: /etc/dbus-1/system.d/org.freedesktop.systemd1.conf 846824928e39a465c06c3aae53510535
current md5: 846824928e39a465c06c3aae53510535
conffile line: /etc/dbus-1/system.d/org.freedesktop.timedate1.conf 682369fbf3de26b21e775732c89a2bbe
current md5: 682369fbf3de26b21e775732c89a2bbe
conffile line: /etc/dhcp/dhclient-exit-hooks.d/timesyncd a891f21f45b0648b7082d999bf424591
current md5: a891f21f45b0648b7082d999bf424591
conffile line: /etc/pam.d/systemd-user 3bdb96b18046bd209135cdfe73421db6
current md5: 3bdb96b18046bd209135cdfe73421db6
conffile line: /etc/systemd/bootchart.conf 7cb6c9cab8ec511882e0e05fceb87e45
current md5: 7cb6c9cab8ec511882e0e05fceb87e45
conffile line: /etc/systemd/journald.conf d928a3ce9f51fcff8ed925270f14a2aa
current md5: d928a3ce9f51fcff8ed925270f14a2aa
conffile line: /etc/systemd/logind.conf 5b41bb868487d1013382b738f6648328
current md5: 5b41bb868487d1013382b738f6648328
conffile line: /etc/systemd/resolved.conf cc77726b02979ddc8b034a338f7bdea9
current md5: cc77726b02979ddc8b034a338f7bdea9
conffile line: /etc/systemd/system.conf 1340491c660f9eb234c92fe1225ff427
current md5: 1340491c660f9eb234c92fe1225ff427
conffile line: /etc/systemd/timesyncd.conf 4e1cf2b5f85dff6c1f186135b9f66a85
current md5: 4e1cf2b5f85dff6c1f186135b9f66a85
conffile line: /etc/systemd/user.conf 2eaf5976751be8864d0555f30814d832
current md5: 2eaf5976751be8864d0555f30814d832
<apt_pkg.AcquireItem object:Status: 2 Complete: 1 Local: 1 IsTrusted: 1 FileSize: 993100 DestFile:'/var/cache/apt/archives/udev_229-4ubuntu21.17_amd64.deb' DescURI: 'http://archive.ubuntu.com/ubuntu/pool/main/s/systemd/udev_229-4ubuntu21.17_amd64.deb' ID:0 ErrorText: ''>
check_conffile_prompt(/var/cache/apt/archives/udev_229-4ubuntu21.17_amd64.deb)
found pkg: udev
conffile line: /etc/init.d/udev e4da2ae5c153148fad0b3f6e5e7ce61e
current md5: e4da2ae5c153148fad0b3f6e5e7ce61e
conffile line: /etc/init/udev.conf 41c0081f3a830e0902aaff76a53edf98
current md5: 41c0081f3a830e0902aaff76a53edf98
conffile line: /etc/init/udevmonitor.conf ec187fc822d47c41416e7c531c8c48dd
current md5: ec187fc822d47c41416e7c531c8c48dd
conffile line: /etc/init/udevtrigger.conf 651ff2421dde80be7ce7ccbf7fa8cf18
current md5: 651ff2421dde80be7ce7ccbf7fa8cf18
conffile line: /etc/modprobe.d/fbdev-blacklist.conf 0b9c466830040ec52986cc3ea117bef5
current md5: 0b9c466830040ec52986cc3ea117bef5
conffile line: /etc/udev/udev.conf a9c43ddab6e58eefa56db50ff44b2b46
current md5: a9c43ddab6e58eefa56db50ff44b2b46
<apt_pkg.AcquireItem object:Status: 2 Complete: 1 Local: 1 IsTrusted: 1 FileSize: 53928 DestFile:'/var/cache/apt/archives/libudev1_229-4ubuntu21.17_amd64.deb' DescURI: 'http://archive.ubuntu.com/ubuntu/pool/main/s/systemd/libudev1_229-4ubuntu21.17_amd64.deb' ID:0 ErrorText: ''>
check_conffile_prompt(/var/cache/apt/archives/libudev1_229-4ubuntu21.17_amd64.deb)
found pkg: libudev1
No conffiles in deb /var/cache/apt/archives/libudev1_229-4ubuntu21.17_amd64.deb (There is no member named 'conffiles')
blacklist: []
whitelist: []
Option --dry-run given, *not* performing real actions
Packages that will be upgraded: libpam-systemd libsystemd0 libudev1 systemd systemd-sysv udev
Writing dpkg log to /var/log/unattended-upgrades/unattended-upgrades-dpkg.log
applying set ['systemd-sysv']
/usr/bin/dpkg --status-fd 9 --unpack --auto-deconfigure /var/cache/apt/archives/systemd-sysv_229-4ubuntu21.17_amd64.deb 
/usr/bin/dpkg --status-fd 11 --configure systemd-sysv:amd64 
/usr/bin/dpkg --status-fd 13 --configure --pending 
left to upgrade {'udev', 'libpam-systemd', 'libudev1', 'libsystemd0', 'systemd'}
applying set ['udev', 'libudev1']
/usr/bin/dpkg --status-fd 9 --unpack --auto-deconfigure /var/cache/apt/archives/udev_229-4ubuntu21.17_amd64.deb /var/cache/apt/archives/libudev1_229-4ubuntu21.17_amd64.deb 
/usr/bin/dpkg --status-fd 11 --configure libudev1:amd64 udev:amd64 
/usr/bin/dpkg --status-fd 13 --configure --pending 
left to upgrade {'libpam-systemd', 'libsystemd0', 'systemd'}
applying set ['libsystemd0', 'libpam-systemd', 'systemd']
/usr/bin/dpkg --status-fd 9 --unpack --auto-deconfigure /var/cache/apt/archives/libpam-systemd_229-4ubuntu21.17_amd64.deb /var/cache/apt/archives/libsystemd0_229-4ubuntu21.17_amd64.deb 
/usr/bin/dpkg --status-fd 11 --configure libsystemd0:amd64 
/usr/bin/dpkg --status-fd 13 --unpack --auto-deconfigure /var/cache/apt/archives/systemd_229-4ubuntu21.17_amd64.deb 
/usr/bin/dpkg --status-fd 15 --configure systemd:amd64 libpam-systemd:amd64 
/usr/bin/dpkg --status-fd 17 --configure --pending 
left to upgrade set()
All upgrades installed
InstCount=0 DelCount=0 BrokenCount=0
root@x-uu-lp-1260041:~# dpkg -l unattended-upgrades | cat
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name                Version                    Architecture Description
+++-===================-==========================-============-===========================================
ii  unattended-upgrades 1.1ubuntu1.18.04.7~16.04.2 all          automatic installation of security upgrades
root@x-uu-lp-1260041:~#

root@x-uu-lp-1260041:~#  while sleep 0.1; do python3 -c 'import apt, apt_pkg, time; print(apt_pkg.pkgsystem_lock()); time.sleep(2)' ; done
Traceback (most recent call last):
  File "<string>", line 1, in <module>
SystemError: E:Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource temporarily unavailable), E:Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it?
Traceback (most recent call last):
  File "<string>", line 1, in <module>
SystemError: E:Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource temporarily unavailable), E:Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it?
Traceback (most recent call last):
  File "<string>", line 1, in <module>
SystemError: E:Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource temporarily unavailable), E:Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it?
Traceback (most recent call last):
  File "<string>", line 1, in <module>
SystemError: E:Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource temporarily unavailable), E:Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it?
Traceback (most recent call last):
  File "<string>", line 1, in <module>
SystemError: E:Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource temporarily unavailable), E:Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it?
Traceback (most recent call last):
  File "<string>", line 1, in <module>
SystemError: E:Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource temporarily unavailable), E:Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it?
Traceback (most recent call last):
  File "<string>", line 1, in <module>
SystemError: E:Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource temporarily unavailable), E:Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it?
Traceback (most recent call last):
  File "<string>", line 1, in <module>
SystemError: E:Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource temporarily unavailable), E:Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it?
Traceback (most recent call last):
  File "<string>", line 1, in <module>
SystemError: E:Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource temporarily unavailable), E:Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it?
Traceback (most recent call last):
  File "<string>", line 1, in <module>
SystemError: E:Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource temporarily unavailable), E:Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it?
Traceback (most recent call last):
  File "<string>", line 1, in <module>
SystemError: E:Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource temporarily unavailable), E:Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it?
Traceback (most recent call last):
  File "<string>", line 1, in <module>
SystemError: E:Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource temporarily unavailable), E:Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it?
Traceback (most recent call last):
  File "<string>", line 1, in <module>
SystemError: E:Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource temporarily unavailable), E:Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it?
Traceback (most recent call last):
  File "<string>", line 1, in <module>
SystemError: E:Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource temporarily unavailable), E:Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it?
Traceback (most recent call last):
  File "<string>", line 1, in <module>
SystemError: E:Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource temporarily unavailable), E:Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it?
Traceback (most recent call last):
  File "<string>", line 1, in <module>
SystemError: E:Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource temporarily unavailable), E:Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it?
Traceback (most recent call last):
  File "<string>", line 1, in <module>
SystemError: E:Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource temporarily unavailable), E:Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it?
Traceback (most recent call last):
  File "<string>", line 1, in <module>
SystemError: E:Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource temporarily unavailable), E:Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it?
Traceback (most recent call last):
  File "<string>", line 1, in <module>
SystemError: E:Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource temporarily unavailable), E:Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it?
Traceback (most recent call last):
  File "<string>", line 1, in <module>
SystemError: E:Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource temporarily unavailable), E:Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it?
Traceback (most recent call last):
  File "<string>", line 1, in <module>
SystemError: E:Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource temporarily unavailable), E:Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it?
Traceback (most recent call last):
  File "<string>", line 1, in <module>
SystemError: E:Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource temporarily unavailable), E:Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it?
Traceback (most recent call last):
  File "<string>", line 1, in <module>
SystemError: E:Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource temporarily unavailable), E:Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it?
Traceback (most recent call last):
  File "<string>", line 1, in <module>
SystemError: E:Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource temporarily unavailable), E:Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it?
Traceback (most recent call last):
  File "<string>", line 1, in <module>
SystemError: E:Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource temporarily unavailable), E:Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it?
Traceback (most recent call last):
  File "<string>", line 1, in <module>
SystemError: E:Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource temporarily unavailable), E:Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it?
Traceback (most recent call last):
  File "<string>", line 1, in <module>
SystemError: E:Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource temporarily unavailable), E:Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it?
Traceback (most recent call last):
  File "<string>", line 1, in <module>
SystemError: E:Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource temporarily unavailable), E:Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it?
Traceback (most recent call last):
  File "<string>", line 1, in <module>
SystemError: E:Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource temporarily unavailable), E:Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it?
Traceback (most recent call last):
  File "<string>", line 1, in <module>
SystemError: E:Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource temporarily unavailable), E:Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it?
Traceback (most recent call last):
  File "<string>", line 1, in <module>
SystemError: E:Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource temporarily unavailable), E:Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it?
Traceback (most recent call last):
  File "<string>", line 1, in <module>
SystemError: E:Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource temporarily unavailable), E:Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it?
True
True
...

I also installed apt and related packages from -proposed:

root@x-uu-lp-1260041:~# dpkg -l python3-apt | cat
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name           Version                    Architecture Description
+++-==============-==========================-============-=================================
ii  python3-apt    1.1.0~beta1ubuntu0.16.04.3 amd64        Python 3 interface to libapt-pkg

tags:

added: verification-done verification-done-xenial
removed: verification-needed verification-needed-xenial

Revision history for this message

Launchpad Janitor (janitor) wrote on 2019-04-25:

#12

Download full text (33.9 KiB)

This bug was fixed in the package unattended-upgrades - 1.1ubuntu1.18.04.7~16.04.2

---------------
unattended-upgrades (1.1ubuntu1.18.04.7~16.04.2) xenial; urgency=medium

  * Don't check blacklist too early and report updates from not allowed origins
    as kept back. (LP: #1781176)
  * test/test_blacklisted_wrong_origin.py: Fix and enable test
  * Filter out progress indicator from dpkg log (LP: #1599646)
  * Clear cache when autoremoval fails (LP: #1779157)
  * Find autoremovable kernel packages using the patterns in APT's way
    (LP: #1815494)

unattended-upgrades (1.1ubuntu1.18.04.7~16.04.1) xenial; urgency=medium

  * Start service after systemd-logind.service to be able to take inhibition
    lock (LP: #1806487)
  * Handle gracefully when logind is down (LP: #1806487)

unattended-upgrades (1.1ubuntu1.18.04.7~16.04.0) xenial; urgency=medium

  * Backport to Xenial (LP: #1702793)
  * Revert to build-depending on debhelper (>= 9~) and dh-systemd
  * Revert configuration example changes to avoid triggering a debconf question
  * debian/postinst: Update recovery to be triggered on Xenial's package versions

unattended-upgrades (1.1ubuntu1.18.04.7) bionic; urgency=medium

  * Trigger unattended-upgrade-shutdown actions with PrepareForShutdown()
    Performing upgrades in service's ExecStop did not work when the upgrades
    involved restarting services because systemd blocked other stop/start
    actions making maintainer scripts time out and be killed leaving a broken
    system behind.
    Running unattended-upgrades.service before shutdown.target as a oneshot
    service made it run after unmounting filesystems and scheduling services
    properly on shutdown is a complex problem and adding more services to the
    mix make it even more fragile.
    The solution of monitoring PrepareForShutdown() signal from DBus
    allows Unattended Upgrade to run _before_ the jobs related to shutdown are
    queued thus package upgrades can safely restart services without
    risking causing deadlocks or breaking part of the shutdown actions.
    Also ask running unattended-upgrades to stop when shutdown starts even in
    InstallOnShutdown mode and refactor most of unattended-upgrade-shutdown to
    UnattendedUpgradesShutdown class. (LP: #1778219)
  * Increase logind's InhibitDelayMaxSec to 30s. (LP: #1778219)
    This allows more time for unattended-upgrades to shut down gracefully
    or even install a few packages in InstallOnShutdown mode, but is still a
    big step back from the 30 minutes allowed for InstallOnShutdown previously.
    Users enabling InstallOnShutdown node are advised to increase
    InhibitDelayMaxSec even further possibly to 30 minutes.
    - Add NEWS entry about increasing InhibitDelayMaxSec and InstallOnShutdown
      changes
  * Ignore "W503 line break before binary operator"
    because it will become the best practice and breaks the build
  * Stop using ActionGroups, they interfere with apt.Cache.clear()
    causing all autoremovable packages to be handled as newly autoremovable
    ones and be removed by default. Dropping ActionGroup usage does not slow
    down the most frequent case of not having anything to upgrade a...

This bug was fixed in the package unattended-upgrades - 1.1ubuntu1.18.04.7~16.04.2

---------------
unattended-upgrades (1.1ubuntu1.18.04.7~16.04.2) xenial; urgency=medium

* Don't check blacklist too early and report updates from not allowed origins
    as kept back. (LP: #1781176)
  * test/test_blacklisted_wrong_origin.py: Fix and enable test
  * Filter out progress indicator from dpkg log (LP: #1599646)
  * Clear cache when autoremoval fails (LP: #1779157)
  * Find autoremovable kernel packages using the patterns in APT's way
    (LP: #1815494)

unattended-upgrades (1.1ubuntu1.18.04.7~16.04.1) xenial; urgency=medium

* Start service after systemd-logind.service to be able to take inhibition
    lock (LP: #1806487)
  * Handle gracefully when logind is down (LP: #1806487)

unattended-upgrades (1.1ubuntu1.18.04.7~16.04.0) xenial; urgency=medium

* Backport to Xenial (LP: #1702793)
  * Revert to build-depending on debhelper (>= 9~) and dh-systemd
  * Revert configuration example changes to avoid triggering a debconf question
  * debian/postinst: Update recovery to be triggered on Xenial's package versions

unattended-upgrades (1.1ubuntu1.18.04.7) bionic; urgency=medium

* Trigger unattended-upgrade-shutdown actions with PrepareForShutdown()
    Performing upgrades in service's ExecStop did not work when the upgrades
    involved restarting services because systemd blocked other stop/start
    actions making maintainer scripts time out and be killed leaving a broken
    system behind.
    Running unattended-upgrades.service before shutdown.target as a oneshot
    service made it run after unmounting filesystems and scheduling services
    properly on shutdown is a complex problem and adding more services to the
    mix make it even more fragile.
    The solution of monitoring PrepareForShutdown() signal from DBus
    allows Unattended Upgrade to run _before_ the jobs related to shutdown are
    queued thus package upgrades can safely restart services without
    risking causing deadlocks or breaking part of the shutdown actions.
    Also ask running unattended-upgrades to stop when shutdown starts even in
    InstallOnShutdown mode and refactor most of unattended-upgrade-shutdown to
    UnattendedUpgradesShutdown class. (LP: #1778219)
  * Increase logind's InhibitDelayMaxSec to 30s. (LP: #1778219)
    This allows more time for unattended-upgrades to shut down gracefully
    or even install a few packages in InstallOnShutdown mode, but is still a
    big step back from the 30 minutes allowed for InstallOnShutdown previously.
    Users enabling InstallOnShutdown node are advised to increase
    InhibitDelayMaxSec even further possibly to 30 minutes.
    - Add NEWS entry about increasing InhibitDelayMaxSec and InstallOnShutdown
      changes
  * Ignore "W503 line break before binary operator"
    because it will become the best practice and breaks the build
  * Stop using ActionGroups, they interfere with apt.Cache.clear()
    causing all autoremovable packages to be handled as newly autoremovable
    ones and be removed by default. Dropping ActionGroup usage does not slow
    down the most frequent case of not having anything to upgrade and when
    there are packages to upgrade the gain is small compared to the actual
    package installation.
    Also collect autoremovable packages before adjusting candidates because that
    also changed .is_auto_removable attribute of some of them. (LP: #1803749)
    (Closes: #910874)

unattended-upgrades (1.1ubuntu1.18.04.6) bionic; urgency=medium

* Unlock for dpkg operations with apt_pkg.pkgsystem_unlock_inner() when it is
    available. Also stop running when reacquiring the lock fails.
    Thanks to Julian Andres Klode for original partial patch (LP: #1789637)
  * Skip rebuilding python-apt in upgrade autopkgtests.
    Python-apt has a new build dependency making the rebuilding as is failing
    and the reference handling issue is worked around in unattended-upgrades
    already. (LP: #1781586)
  * Stop trying when no adjustment could be made and adjust package candidates
    only to lower versions (LP: #1785093)
  * Skip already adjusted packages from being checked for readjusting.
    This makes it clearer that the recursion ends and can also be a bit quicker.
    (LP: #1785093)

unattended-upgrades (1.1ubuntu1.18.04.5) bionic; urgency=medium

* Stop updating the system when reacquiring the dpkg system lock fails.
    (LP: #1260041)

unattended-upgrades (1.1ubuntu1.18.04.4) bionic; urgency=medium

* Redirect stderr output in upgrade-between-snapshots, too, otherwise it
    breaks the test sometimes (LP: #1781446)

unattended-upgrades (1.1ubuntu1.18.04.3) bionic; urgency=medium

* Redirect stderr output in upgrade-all-security, otherwise it breaks the
    test (LP: #1781446)

unattended-upgrades (1.1ubuntu1.18.04.2) bionic; urgency=medium

[ Balint Reczey ]
  * Clear cache when autoremoval is invalid for a package set marked for
    removal and clear cache after failed commits to return from a possibly
    invalid state (LP: #1779157)
  * Don't start or gracefully stop upgrade on battery (LP: #1773033)
  * Skip updates on metered connections (Closes: #855570) (LP: #1781183)
  * Add debian/tests/upgrade-all-security to install all current security updates.
    On development releases this tests latest stable, on stable releases it tests
    the release itself.
  * Speed up unattended-upgrade (Closes: #892028, #899366) (LP: #1396787)
    - Adjust candidates only for packages to be possibly installed
    - Filter out packages cheaper when they are not from allowed origins
    - Collect autoremovable packages, too, when looking for upgradable ones
    - Measure time of running with --dry-run in autopkgtests
  * Skip starting init.d script in debhelper-generated postinst part
    (LP: #1778800)

[ Ivan Kurnosov ]
  * Fixed is_pkgname_in_blacklist to be side-effect free. (LP: #1781176)
    Otherwise 'is_pkgname_in_blacklist' mutates the 'pkgs_kept_back' and
    'unattended-upgrades' treats the package as a blacklisted candidate

unattended-upgrades (1.1ubuntu1.18.04.1) bionic; urgency=medium

[ Michael Vogt ]
  * unattended-upgrades: fix Unlocked context manager. (LP: #1602536)
    The Unlocked context manager did correctly unlock but did not
    reacquire the lock which means that in minimal-upgrade step
    mode it is possible to run apt code without a lock. If something
    else (like landscape, apt, synaptic, packagekit) locks the cache
    in the meantime this will work and u-u will get dpkg errors
    because dpkg will not be able to perform its operations. It is
    less of an issue in non-minimal mode, but even then the auto-remove
    step may fail in this way.

[ Balint Reczey ]
  * Fix adjusting candidates (LP: #1775292)
  * Relock apt lock before reopening the cache (LP: #1602536)
  * Fix crashing while adjusting candidates and save candidates to adjust only
    in first sweep run, not emptying the set later
    (Closes: #901258) (LP: #1775307)

unattended-upgrades (1.1ubuntu1) bionic; urgency=medium

* Merge from Debian unstable (LP: #1764797)
    - Remaining changes:
      - unattended-upgrades: Do not automatically upgrade the development
        release of Ubuntu unless Unattended-Upgrade::DevRelease is true.
    - Dropped changes, included in Debian:
      - Rename d/NEWS.Debian to d/NEWS to have it shipped
      - Fix typo in NEWS file
      - d/rules: Exclude mypy cache from source package.

unattended-upgrades (1.1) unstable; urgency=medium

[ cgail914 ]
  * Update 50unattended-upgrades.Raspbian
    added a semi-column sign on line 86 to facilitate uncommenting the line
    for users and not end up with an error message when running
    unattended-upgrades. And make the whole file consistent.

[ Tobias Bannert ]
  * completed german translation

[ Simon McVittie ]
  * d/rules: Exclude mypy cache from source package.

[ Julian Andres Klode ]
  * Do not reuse old apt.Version objects after reopening cache (LP: #1737441)

[ Balint Reczey ]
  * Rename d/NEWS.Debian to d/NEWS to have it shipped
  * Fix typo in NEWS file
  * Add missing semicolon to commented-out Remove-Unused-Kernel-Packages option
  * Set UnattendedUpgradesCache.allowed_origins before calling
    apt.Cache.__init__()
  * Find package candidates to adjust sweeping through all packages only once.
    Later reuse the list candidates and filter out packages installed in the
    meantime. Thanks to Julian Andres Klode for the original patch
  * Use updated python-apt in upgrade-between-snapshots test
  * upgrade-between-snapshots: Mount /proc, too, in the chroot.
    Also clean up chroot properly on exit.
  * upgrade-between-snapshots: Use http_proxy environment variable in chroot,
    too
  * upgrade-between-snapshots: Remove packages installed as the side-effect of
    updating apt and python-apt
  * Ignore errors from compiling backported packages
  * Make is_autoremove_valid() nondestructive.
    Also fix autoremoval of packages when one package can't be removed and
    keeps back other package removals due to missing cache.clear()
  * Fix tracking removed packages
  * Suggest default-mta | mail-transport-agent to keep Lintian happy

[ Michael Vogt ]
  * unattanded-upgrades: refactor get_candidates_to_adjust() to
    adjust_candidates()

unattended-upgrades (1.0ubuntu2) bionic; urgency=medium

[ Balint Reczey ]
  * Rename d/NEWS.Debian to d/NEWS to have it shipped
  * Fix typo in NEWS file

[ Simon McVittie ]
  * d/rules: Exclude mypy cache from source package.

unattended-upgrades (1.0ubuntu1) bionic; urgency=medium

* Merge from Debian unstable
    - Remaining changes:
      - unattended-upgrades: Do not automatically upgrade the development
        release of Ubuntu unless Unattended-Upgrade::DevRelease is true.
    - Dropped changes, included in Debian:
      - Run upgrade-between-snapshots only on amd64.
        The test exercises only unattented-upgrade's Python code and uses
        dependencies from the frozen Debian snapshot archive thus running
        it on all architectures would provide little benefit.

unattended-upgrades (1.0) unstable; urgency=medium

[ Simon Arlott ]
  * Revert sending mails on WARNINGS when in MailOnlyOnError mode"
  * Consider conffile prompts to be errors (Closes: #852465)
    Flag packages that have to be upgraded manually because of a conffile
    prompt and consider this to be an error when sending email or exiting.

[ Simon McVittie ]
  * Add python, python3, setuptools, DistutilsExtra to Build-Depends.
    They are needed for `clean`, so Build-Depends-Indep is not enough.
  * Add .gitignore and debian/.gitignore
  * Remove bzr configuration.
    This is unnecessary now that u-u is in git.

[ Michael Vogt ]
  * unattended-upgrades: tweak mail-on-warnings PR
  * unattended-upgrade: extract is_autoremove_valid helper

[ Balint Reczey ]
  * Run upgrade-between-snapshots only on amd64.
    The test exercises only unattented-upgrade's Python code and uses
    dependencies from the frozen Debian snapshot archive thus running
    it on all architectures would provide little benefit.
  * Clean up processes started for getting md5 sums
  * Don't keep /var/lib/dpkg/status open multiple times
  * Adjust candidates in UnattendedUpgradesCache.open()
  * Perform autoremovals in minimal steps, too.
    Also add check to remove only the set of packages selected for autoremoval.
    Without that check unattended-upgrades when (by default) configured to
    remove newly unused packages could also remove auto removable packages
    which were unused before starting starting the upgrade step.
  * Remove unused automatically installed kernel packages
    (LP: #1357093, #1624644, #1675079, #1698159)
  * Stop including Python syntax in the report (Closes: #876796)
  * Do not auto remove packages related to the running kernel (LP: #1615381)
  * Check packages to be autoremoved against blacklists, whitelists.
    Also check if the packages are held.
  * Report package removals in the summary email (Closes: #876797)
  * Run upgrade-between-snapshots test with debugging enabled
  * Don't create new UnattendedUpgradesCache for checking for autoremovals
    .open() refreshes the state in each cache_commit(), this is enough
  * Update .pot and .po files
  * Update .travis.yml to actually build and test u-u from the repo
  * Run only a simple installation test on Travis, the system upgrade
    test was always failing

unattended-upgrades (0.99ubuntu2) bionic; urgency=medium

* Run upgrade-between-snapshots only on amd64.
    The test exercises only unattented-upgrade's Python code and uses
    dependencies from the frozen Debian snapshot archive thus running
    it on all architectures would provide little benefit.

unattended-upgrades (0.99ubuntu1) bionic; urgency=medium

* Merge from Debian unstable (LP: #1722426)
    - Remaining changes:
      - unattended-upgrades: Do not automatically upgrade the development
        release of Ubuntu unless Unattended-Upgrade::DevRelease is true.
    - Dropped changes, included in Debian:
      - Fix version of test package in test_remove_unused_dependencies
      - Do not touch reboot-required on linux-image-extra removal
      - unattended-upgrades: Do not reboot during a dry-run.

unattended-upgrades (0.99) unstable; urgency=medium

[ Peter Nowee ]
  * Fix Raspbian default config codename matching.
    Using `archive=${distro_codename}` does not match, at least not in
    Raspbian Stretch anymore. Changing it to `codename=${distro_codename}`.
    I tested that it now works and did not notice any regressions.
    Same change was made to the Debian-specific configuration 3 years ago,
    see commit 9a2afa5.
  * Enable RPi-specific upgrades on Raspbian.
    In addition to the Raspbian repository, Raspbian images distributed by
    the Raspberry Pi Foundation (RPF) depend on the RPF repository for
    kernel and firmware updates.
    This commit adds a pattern matching line for packages from the RPF
    repository to the Raspbian config file for unattended-upgrades.

[ Alexandre Detiste ]
  * Drop unused dependency on apt-utils (Closes: #876425)

[ Frans Spiesschaert ]
  * Dutch translation update

[ Chris Leick ]
  * German translation update

[ Ben Wong ]
  * Fix configuration file examples (Closes: #877395)

[ Balint Reczey ]
  * Test for running systemd on Debian, too, when applying workaround for it
  * Fix calling dh_installinit during build
  * Tidy up d/control using cme fix
  * Fix log file location in man page.
    Thanks to Jaakov for the bug report (Closes: #817974)
  * Build-depend on debhelper (>= 9.20160709) instead of dh-systemd
  * Link unattended-upgrades.8 to unattended-upgrade.8 man page
  * Add Auto-Submitted header to email report (LP: #1230246)
  * Exit with error when package installation failed or u-u is signalled to
    stop (Closes: #838368)
  * Process packages needing smaller upgrade sets earlier in generating
    minimal upgrade sets.
    Inspired by Michael Vogt's partition pre-calculation code
  * Exit with printing error when apt errors prevent initialization
    (LP: #1737442)
  * Mark invalid UTF-8 characters in dpkg's log, but don't crash
    (LP: #1737635)
  * Try upgrading packages replacing configuration dir with configuration file
    (LP: #1737637)
  * Make unattended-upgrade-shutdown exit with error when apt config is
    invalid (LP: #1737717)
  * Exit when an apt error prevents checking a package for conffile prompt
  * Install upgrades from ${distro_codename}, label=Debian by default.
    This enables updates from stable point releases but also lets testing
    and sid being updated with the package updates.
    Fixes #33. (Closes: #787945, #597061)
  * Fix debian/NEWS.Debian's format
  * Add NEWS item about unattended-uprades installing stable/all updates
  * Stop asking debconf question about Origins-Pattern.
    50unattended-upgrades now contains multiple origins by default and setting
    them from debconf can't be made really easy. Users should change the
    configuration file itself instead. (LP: #1577215)
  * Update PO files about debconf templates
  * Don't log exceptions which did not happen
  * Add autopkgtest for upgrading unstable between two snapshots from
    snapshot.d.o
  * Remove tabs from Debian's configuration file
  * Catch SystemError instead of apt_pkg.Error for backwards compatibility
  * Check in autopkgtest if unattended-upgrades mark additional packages as
    manually installed
  * Test upgrading a full system with desktop packages in autopkgtest.
    Also pick different shapshots with which does not contain
    broken packages.
  * Test sending email after upgrading a full system
  * Show "please don't turn off the computer" while installing updates on
    shutdown.
    This is more informational for users than the original "sleeping for 5s".
    Thanks to Mario Loderer for the suggestion (LP: #1741579)
  * Use eatmydata for system upgrade autopkgtest
  * Run upgrade-between-snapshots autopkgtest even on other distros
  * Apt install built u-u in snapshot upgrade test
  * Update .pot file
  * Fix version of test package in test_remove_unused_dependencies
    (Closes: #886803)
  * Refresh cache after committing changes to avoid reinstalling packages
    (Closes: #875383)
  * Relax calculating truly minimal sets to sets expected to be minimal.
    This speeds up calculation by making it from ~O(n^2) to ~O(n) at the
    expense of creating slightly bigger sets in rare cases.

[ Evilham ]
  * Add Devuan support.

[ Brian Murray ]
  * unattended-upgrades: Do not reboot during a dry-run (LP: #1269177)

[ Michael Vogt ]
  * enable pep484 test
  * mypy fixes
  * add two missing return values
  * tests: cleanup test_mail.py to use proper tmpdirs

[ Julian Andres Klode ]
  * Do not touch reboot-required on linux-image-extra removal (LP: #1458204)

[ Sjoerd Job Postmus ]
  * Adjust candidate version of packages to be newly installed (LP: #1446552)

unattended-upgrades (0.98ubuntu4) bionic; urgency=medium

* Cherry pick from git:
    - Fix version of test package in test_remove_unused_dependencies (Closes: #886803)

unattended-upgrades (0.98ubuntu3) bionic; urgency=medium

*  Do not touch reboot-required on linux-image-extra removal (LP: #1458204)

unattended-upgrades (0.98ubuntu2) bionic; urgency=medium

* unattended-upgrades: Do not reboot during a dry-run. (LP: #1269177)

unattended-upgrades (0.98ubuntu1) artful; urgency=medium

* Merge from Debian unstable (LP: #1722426)
    - Remaining changes:
      - unattended-upgrades: Do not automatically upgrade the development
        release of Ubuntu unless Unattended-Upgrade::DevRelease is true.
    - Dropped changes, included in Debian:
      - Use lsb_release instead of dpkg-vendor in postinst

unattended-upgrades (0.98) unstable; urgency=medium

* Rename test to test_non_minimal_steps_upgrade to reflect content
  * Catch SystemError while keeping apt lock unlocked (LP: #1632361)
  * Add --stop-only option to unattended-upgrade-shutdown and use it on
    hibernation. This prevents starting unattended-upgrades right before
    hibernating when Unattended-Upgrade::InstallOnShutdown is true.
    (Closes: #610333)
  * Stop already running unattended-upgrades before hibernation even with
    systemd (LP: #1455097)
  * Use lsb_release instead of dpkg-vendor in postinst (LP: #1719630)
  * Update README.md with the fact that unattended=upgrades is enabled
    by default (Closes: #865519)

unattended-upgrades (0.97ubuntu2) artful; urgency=medium

* Use lsb_release instead of dpkg-vendor in postinst (LP: #1719630)

unattended-upgrades (0.97ubuntu1) artful; urgency=medium

* Merge from Debian unstable (LP: #1718419)
    - Remaining changes:
      - unattended-upgrades: Do not automatically upgrade the development
        release of Ubuntu unless Unattended-Upgrade::DevRelease is true.
    - Dropped changes, included in Debian:
      - Recover from broken dh_installinit override in versions < 0.93.1ubuntu3

unattended-upgrades (0.97) unstable; urgency=medium

* Handle recovering from broken dh_installinit override on Ubuntu, too
  * Declare needs-reboot for autopkgtests
  * Clean up more test artifacts
  * Run u-u-s only when running on AC power
  * Catch SystemError from fetcher.run(), too
  * Default to MinimalSteps=True in most tests to excercise default setting
  * Check only changed packages in check_changes_for_sanity()
  * Store candidate versions to adjust in UnattendedUpgradesCache()'s constructor

unattended-upgrades (0.96ubuntu1) artful; urgency=low

* Merge from Debian unstable (LP: #1714019)
    - Remaining changes:
      - Recover from broken dh_installinit override in versions < 0.93.1ubuntu3
      - unattended-upgrades: Do not automatically upgrade the development
        release of Ubuntu unless Unattended-Upgrade::DevRelease is true.
    - Dropped changes, included in Debian:
      - Cherry-pick 2e5deed, f26edb4 from upstream to add support for a
        --download-only option, enabling us to download updates at a random
        time of day by default but apply them predictably in the 6am-7am
        window.
      - Fix PEP8 failures (replace except: with except Exception:)
      - unattended-upgrades: Provide some information and create a log entry
        when there is a failure to parse the allowed origins.
      - Add UbuntuESM to the list of sources automatically upgraded from by
        default.
      - Complete the solution for the unattended-upgrades.service unit not
        correctly working
      - d/rules : Remove the override_dh_installinit. The stop option is no
        longer available so the command falls back to default. This is the
        normal behavior so the override is not required
      - d/unattended-upgrades.init : Add Default-Start runlevels, otherwise
        the unattended-upgrades.service unit cannot be enabled on boot
      - d/postinst : Cleanup the stop symlinks created by the wrong
        override_dh_installinit. Without that, the systemd unit cannot be
        enabled correctly.
        Force disable the service before deb-systemd-helper runs so the old
        symlink is not left dangling (workaround for Debian Bug #797108).
        Force enable and start of the systemd unit to work around Debian Bug
        #797108 which fails to enable systemd units correctly when
        WantedBy= statement is changed which is the case here.
      - d/unattended-upgrades.service : Fix the service so it runs correctly on
        shutdown :
        - Remove DefaultDependencies=no : Breaks normal shutdown dependencies
        - Set After= to network.target and local-fs.target. Since our service
          is now ExecStop, it will run before network and local-fs become
          unavailable.
        - Add RequiresMountsFor=/var/log /var/run /var/lib /boot : Necessary if
          /var is a separate file system. Set WantedBy= to multi-user.target
      - Add DEP8 tests to verify the following :
        - Verify that the unattended-upgrades.service unit is enabled and
          started.
        - Verify that InstallOnShutdown works when configured.
      - The systemd unit needs to be an ExecStop since it is is activated on
        shutdown. Otherwise, it will get scheduled after completion of
        the local-fs.target. In the case where /var is a separate
        filesystem, unattended-upgrade-shutdown will hang until timeout
        since /var/run is expected but no longer there
      - When performing a sanity check for packages to install or upgrade
        return false when either there are no packages in the cache or the
        package to upgrade is not in the change set.
      - Do not mark packages for deletion / autoremoval if unattended-upgrades
        is being run in dry-run mode.
      - Store delay command line option as an int not a string since we do
        maths with it.

unattended-upgrades (0.96) unstable; urgency=medium

* Use test/aptroot instead of / as APT root directory in tests
    (Closes: #873079)

unattended-upgrades (0.95) unstable; urgency=medium

[ Michael Vogt ]
  * fix some type hints

[ Balint Reczey ]
  * Increase timeout to 30 minutes for u-u-s to finish before killing it.
    Soft timeout until u-u-s is considered to be finished properly
    is also increased to 25 minutes from 10 minutes.
  * Update the signal used to SIGTERM in the documentation
  * Default to performing upgrades in minimal steps
  * Use same progress logfile when performing upgrades in minimal steps.
    This allows u-u-s to always show the progress.
  * Joining maintaining the package as an uploader
  * Log when not all upgrades could be installed
  * Fix incorrect example for Update-Days.
  * Add Debian backports example to Origins-Pattern.
  * Don't restart unattended-upgrades when the package is upgraded
  * Silence lintinan warning  init.d-script-possible-missing-stop
  * Update .pot and .po file

unattended-upgrades (0.94) unstable; urgency=medium

[ Brian Murray ]
  * Add apt history log to apport reports
  * unattended-upgrades: Provide some information and create a log entry when
    there is a failure to parse the allowed origins. (LP: #1680599)
  * improve the changes sanity check to cache more insane cases
  * Do not mark packages for deletion / autoremoval if unattended-upgrades
    is being run in dry-run mode.

[ Louis Bouchard ]
  * Fix --delay type in unattended-upgrade-shutdown (Closes: #837161)

[ Balint Reczey ]
  * ACK NMU
  * Fix indentation in test-systemd.py
  * Keep apt's partial dir in tests.
    This fixes make -C test in a clean repository
  * Clean up all generated files in override_dh_auto_clean
  * Update debhelper compat level to 9
  * Move acquiring shutdown_lock earlier in u-u to cover dpkg --configure step
  * Start handling SIGUSR1 gracefully earlier in unattended-upgrade
    (LP: #1690980)
  * Handle SIGTERM instead of SIGUSR1 as a graceful shutdown signal
  * Place unattended-upgrade pid file early and remove it on exit.
  * Override maintainer-script-calls-systemctl lintian warnings
  * Don't start package downloads when shutdown has already started
  * Let unattended-upgrade run uninterrupted in shutdown mode until timeout
  * Fix indentation in test-systemd.py

[ Julian Andres Klode ]
  * Add a --download-only option (Closes: #863911) (LP: #1686470)
  * Fix PEP8 failures (replace except: with except Exception:)
    (Closes: #865897)

[ Steve Langasek ]
  * Add UbuntuESM to the list of sources automatically upgraded from by default
    (LP: #1687129)

[ Jonatan Nyberg ]
  * Update Swedish debconf strings (Closes: #855361)

[ Peter Lewis ]
  * Multiple typo fixes

[ Michael Vogt ]
  * add HACKING.md
  * add pep484 type hints
  * add spread test
  * Enable updates on Raspbian

[ John Horne ]
  * Blacklisted packages are now added to the pkgs_kept_back list.
  * Reduced instance of line too long.
  * Some typos corrected in the README file.
  * Fix for pep8 - closing bracket missing visual indentation
  * Added tests that blacklisted packages are mentioned in email messages.
  * Updated argument type comment for is_pkgname_in_blacklist function.

[ nachoparker ]
  * There is noRaspbian-Security label

unattended-upgrades (0.93.1+nmu2) unstable; urgency=medium

* Non-maintainer upload.
  * Fix PEP8 failures (replace except: with except Exception:)
    (Closes: #865897)

unattended-upgrades (0.93.1+nmu1) unstable; urgency=medium

* Non-maintainer upload.

[ Louis Bouchard ]
  * Fix the unattended-upgrades.service unit not correctly working:
    - d/rules : Remove the override_dh_installinit. The stop option is no longer
      available so the command falls back to default. This is the normal
      behavior so the override is not required
    - d/unattended-upgrades.init : Add Default-Start runlevels, otherwise the
      unattended-upgrades.service unit cannot be enabled on boot
    - d/postinst : Cleanup the stop symlinks created by the wrong
      override_dh_installinit. Without that, the systemd unit cannot be
      enabled correctly.
      Force disable the service before deb-systemd-helper runs so the old
      symlink is not left dangling (workaround for Debian Bug #797108).
      Force enable and start of the systemd unit to work around Debian Bug
      #797108 which fails to enable systemd units correctly when WantedBy=
      statement is changed which is the case here.
    - d/unattended-upgrades.service : Fix the service so it runs correctly on
      shutdown :
        Remove DefaultDependencies=no : Breaks normal shutdown dependencies
        Set After= to network.target and local-fs.target. Since our service is
        now ExecStop, it will run before network and local-fs become
        unavailable. Add RequiresMountsFor=/var/log /var/run /var/lib /boot :
        Necessary if /var is a separate file system. Set WantedBy= to
        multi-user.target
    - Add DEP8 tests to verify the following :
      Verify that the unattended-upgrades.service unit is enabled and started.
      Verify that InstallOnShutdown works when configured.
    (Closes: #809669)

unattended-upgrades (0.93.1ubuntu8) artful; urgency=medium

[ Steve Langasek ]
  * Cherry-pick 2e5deed, f26edb4 from upstream to add support for a
    --download-only option, enabling us to download updates at a random time
    of day by default but apply them predictably in the 6am-7am window.
    LP: #1686470.

unattended-upgrades (0.93.1ubuntu7) artful; urgency=medium

* Fix PEP8 failures (replace except: with except Exception:)

unattended-upgrades (0.93.1ubuntu6) artful; urgency=medium

* unattended-upgrades: Do not automatically upgrade the development release
    of Ubuntu unless Unattended-Upgrade::DevRelease is true. (LP: #1649709)

unattended-upgrades (0.93.1ubuntu5) artful; urgency=medium

* unattended-upgrades: Provide some information and create a log entry when
    there is a failure to parse the allowed origins. (LP: #1680599)

unattended-upgrades (0.93.1ubuntu4) artful; urgency=medium

* Add UbuntuESM to the list of sources automatically upgraded from by
    default.  LP: #1687129.

unattended-upgrades (0.93.1ubuntu3) artful; urgency=medium

* Complete the solution for the unattended-upgrades.service unit not
    correctly working (LP: #1654600):
    - d/rules : Remove the override_dh_installinit. The stop option is no longer
      available so the command falls back to default. This is the normal
      behavior so the override is not required
    - d/unattended-upgrades.init : Add Default-Start runlevels, otherwise the
      unattended-upgrades.service unit cannot be enabled on boot
    - d/postinst : Cleanup the stop symlinks created by the wrong
      override_dh_installinit. Without that, the systemd unit cannot be
      enabled correctly.
      Force disable the service before deb-systemd-helper runs so the old
      symlink is not left dangling (workaround for Debian Bug #797108).
      Force enable and start of the systemd unit to work around Debian Bug #797108
      which fails to enable systemd units correctly when WantedBy= statement
      is changed which is the case here.
    - d/unattended-upgrades.service : Fix the service so it runs correctly on
      shutdown :
        Remove DefaultDependencies=no : Breaks normal shutdown dependencies
        Set After= to network.target and local-fs.target. Since our service is
        now ExecStop, it will run before network and local-fs become unavailable.
        Add RequiresMountsFor=/var/log /var/run /var/lib /boot : Necessary if
        /var is a separate file system. Set WantedBy= to multi-user.target
    - Add DEP8 tests to verify the following :
      Verify that the unattended-upgrades.service unit is enabled and started.
      Verify that InstallOnShutdown works when configured.

unattended-upgrades (0.93.1ubuntu2) zesty; urgency=medium

* The systemd unit needs to be an ExecStop since it is is activated on
    shutdown. Otherwise, it will get scheduled after completion of
    the local-fs.target. In the case where /var is a separate
    filesystem, unattended-upgrade-shutdown will hang until timeout
    since /var/run is expected but no longer there (LP: #1654600)

unattended-upgrades (0.93.1ubuntu1) zesty; urgency=medium

[ Brian Murray ]
  * When performing a sanity check for packages to install or upgrade return
    false when either there are no packages in the cache or the package to
    upgrade is not in the change set. (LP: #1654070)
  * Do not mark packages for deletion / autoremoval if unattended-upgrades is
    being run in dry-run mode. (LP: #1544942)

[ Louis Bouchard ]
  * Store delay command line option as an int not a string since we do maths
    with it.

unattended-upgrades (0.93.1) unstable; urgency=medium

[ Brian Murray ]
  * Create logfile_dpkg if it doesn't exist
  * Make sure the statedir exists too
  * ensure network and local-fs are available in shutdown

[ Michael Vogt ]
  * fix incorrect "needrestart" package name, move to sugests
    (Closes: #844051, #846652)

[ Manuel "Venturi" Porras Peralta ]
  * [INTL:es] Spanish po translation (Closes: #817160)

[ Takuma Yamada ]
  * [INTL:ja] Japanese translation of po file update (Closes: #820755)

[ Jonatan Nyberg ]
  * [INTL:sv] Swedish strings for unattended-upgrades debconf (Closes: #822119)

[ Frans Spiesschaert ]
  * [INTL:nl] Dutch po file for the unattended-upgrades package
    (Closes: #823975)

unattended-upgrades (0.93) unstable; urgency=medium

[ Michael Vogt ]
  * Ensure to keep "automatic install" information (Closes: #828215)
  * add recommends to "need-restart" to ensure that all running serivces
    affected by library updates get restarted

[ Brian Murray ]
  * Update 50unattended-upgrades.Ubuntu

[ Germar Reitze ]
  * enable escaped colons in Unattended-Upgrade::Allowed-Origins
  * fix pep8 warning

unattended-upgrades (0.92) unstable; urgency=medium

[ Matt Bearup ]
  * Add support for logging to syslog

[ Raphael Geissert ]
  * Fix bug in minimal upgrade step calculation

unattended-upgrades (0.91) unstable; urgency=medium

* Updated japanese debconf templates.
    Thanks to Takuma Yamada (Closes: 815389)
  * Increase TimeoutStartSec in the shutdown script
  * Document how to set Dpkg::Options.
    Thanks to Matt Bearup
  * add Unattended-Upgrade::Update-Days config
  * [INTL:pt_BR] Brazilian Portuguese.
    Thanks to Adriano Rafael Gomes (Closes: #805460)

-- Balint Reczey <rbalint@ubuntu.com>  Thu, 21 Feb 2019 15:36:42 +0100

Changed in unattended-upgrades (Ubuntu Xenial):
status:	Fix Committed → Fix Released

	Status	Importance	Assigned to
unattended-upgrades (Ubuntu)	Fix Released	Undecided	Unassigned
Xenial	Fix Released	Undecided	Unassigned
Bionic	Fix Released	Undecided	Unassigned

Ubuntu
unattended-upgrades package

Unattended-Upgrades crashes with a dpkg error

Bug Description

Duplicates of this bug

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntuunattended-upgrades package

Unattended-Upgrades crashes with a dpkg error

Bug Description

Duplicates of this bug

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntu
unattended-upgrades package