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
All the referenced bugs are verified now. Please note that some of them
did not need SRU template, those are listed in this bug.
** Tags removed: verification-needed verification-needed-xenial
** Tags added: verification-done verification-done-xenial
--
You received this bug notification because
Hello Matt, 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 testi
** Changed in: unattended-upgrades (Ubuntu)
Importance: Wishlist => Low
** Changed in: unattended-upgrades (Ubuntu Xenial)
Importance: Wishlist => Low
** Tags removed: verification-needed verification-needed-xenial
** Tags added: upgrade-software-version verification-done
** Changed in: un
lukasz,
After a kernel update yesterday I can confirmed that the old kernel was removed
and the was no reboot today.
apt-cache policy unattended-upgrades
unattended-upgrades:
Installed: 1.1ubuntu1.18.04.7~16.04.1
Candidate: 1.1ubuntu1.18.04.7~16.04.1
Also installed from xenial-proposed:
apt-
** Changed in: unattended-upgrades (Ubuntu Xenial)
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1702793
Title:
Full back
Hello Matt, 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.0 in a few hours, and then
in the -proposed repository.
Please help us by testi
** Description changed:
[Impact]
* I would like to propose a one-off full backport of unattended-upgrades
1.2ubuntu1 to Bionic, Artful, Xenial and possibly Trusty releases because
selectively backporting fixes for crashes and for issues that made u-u
unreliable would be more risky thank
Its worth mentioning that for bugs with links to Error Tracker crash
buckets that those buckets will probably not receive crash reports from
the new version of the package even if it is "the same crash" because
bucketing is done using python line numbers which are likely to change
given the scope o
** Description changed:
[Impact]
* I would like to propose a one-off full backport of unattended-upgrades
1.2ubuntu1 to Bionic, Artful, Xenial and possibly Trusty releases because
selectively backporting fixes for crashes and for issues that made u-u
unreliable would be more risky thank
** Description changed:
[Impact]
* I would like to propose a one-off full backport of unattended-upgrades
1.2ubuntu1 to Bionic, Artful, Xenial and possibly Trusty releases because
selectively backporting fixes for crashes and for issues that made u-u
unreliable would be more risky thank
** Description changed:
[Impact]
* I would like to propose a one-off full backport of unattended-upgrades
1.2ubuntu1 to Bionic, Artful, Xenial and possibly Trusty releases because
selectively backporting fixes for crashes and for issues that made u-u
unreliable would be more risky thank
** Description changed:
[Impact]
* I would like to propose a one-off full backport of unattended-upgrades
1.2ubuntu1 to Bionic, Artful, Xenial and possibly Trusty releases because
selectively backporting fixes for crashes and for issues that made u-u
unreliable would be more risky thank
** Description changed:
[Impact]
* I would like to propose a one-off full backport of unattended-upgrades
1.2ubuntu1 to Bionic, Artful, Xenial and possibly Trusty releases because
selectively backporting fixes for crashes and for issues that made u-u
unreliable would be more risky thank
** Description changed:
[Impact]
* I would like to propose a one-off full backport of unattended-upgrades
1.2ubuntu1 to Bionic, Artful, Xenial and possibly Trusty releases because
selectively backporting fixes for crashes and for issues that made u-u
unreliable would be more risky thank
** Description changed:
[Impact]
* I would like to propose a one-off full backport of unattended-upgrades
1.2ubuntu1 to Bionic, Artful, Xenial and possibly Trusty releases because
selectively backporting fixes for crashes and for issues that made u-u
unreliable would be more risky thank
** Description changed:
[Impact]
* I would like to propose a one-off full backport of unattended-upgrades
1.2ubuntu1 to Bionic, Artful, Xenial and possibly Trusty releases because
selectively backporting fixes for crashes and for issues that made u-u
unreliable would be more risky thank
** Description changed:
[Impact]
* I would like to propose a one-off full backport of unattended-upgrades
1.2ubuntu1 to Bionic, Artful, Xenial and possibly Trusty releases because
selectively backporting fixes for crashes and for issues that made u-u
unreliable would be more risky thank
** Description changed:
[Impact]
* I would like to propose a one-off full backport of unattended-upgrades
1.2ubuntu1 to Bionic, Artful, Xenial and possibly Trusty releases because
selectively backporting fixes for crashes and for issues that made u-u
unreliable would be more risky thank
** Description changed:
[Impact]
* I would like to propose a one-off full backport of unattended-upgrades
1.2ubuntu1 to Bionic, Artful, Xenial and possibly Trusty releases because
selectively backporting fixes for crashes and for issues that made u-u
unreliable would be more risky thank
I'm collecting the fixes in Bionic's u-u for Xenial and it is close to
be ready for the full backport, but fixing LP: #178116 (or fixing all
cases where python-apt losses the lock) is a prerequisite for the
backport if we want to avoid an increased crash rate on Xenial.
** Changed in: unattended-
Any update/progress on the full backport of 'uu' ?
** Tags added: ua
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1702793
Title:
Full backport SRU for unatt
** Tags added: sts
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1702793
Title:
Full backport SRU for unattended-upgrades
Status in unattended-upgrades packa
** Description changed:
[Impact]
* I would like to propose a one-off full backport of unattended-upgrades
1.2ubuntu1 to Bionic, Artful, Xenial and possibly Trusty releases because
selectively backporting fixes for crashes and for issues that made u-u
unreliable would be more risky thank
There is one bug in particular I'm interested in LP: #1615381 , where a
running kernel may be removed by 'uu'
# /var/log/unattended-upgrades/unattended-upgrades-dpkg.log
...
Removing linux-image-4.13.0-39-generic (4.13.0-39.44~16.04.1) ...^M
WARN: Proceeding with removing running kernel image.^M
25 matches
Mail list logo
