Tested 1.10ubuntu5.2 on Disco:
root@uu-sru-dd:~# apt list --upgradable
Listing... Done
apport/disco-updates,disco-security 2.20.10-0ubuntu27.2 all [upgradable from:
2.20.10-0ubuntu27.1]
snapd/disco-updates 2.40+19.04 amd64 [upgradable from: 2.38+19.04]
root@uu-sru-dd:~# perl -MMIME::QuotedPrint -pe
'$_=MIME::QuotedPrint::decode($_);' /var/mail/mail
>From r...@uu-sru-dd.lxd Fri Nov 01 17:48:11 2019
Return-path: <r...@uu-sru-dd.lxd>
Envelope-to: r...@uu-sru-dd.lxd
Delivery-date: Fri, 01 Nov 2019 17:48:11 +0000
Received: from root by uu-sru-dd.lxd with local (Exim 4.92)
(envelope-from <r...@uu-sru-dd.lxd>)
id 1iQb1v-0001Pj-9M
for r...@uu-sru-dd.lxd; Fri, 01 Nov 2019 17:48:11 +0000
Subject: [package on hold] unattended-upgrades result for uu-sru-dd.lxd: SUCCESS
To: r...@uu-sru-dd.lxd
Auto-Submitted: auto-generated
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: root <r...@uu-sru-dd.lxd>
Message-Id: <e1iqb1v-0001pj...@uu-sru-dd.lxd>
Date: Fri, 01 Nov 2019 17:48:11 +0000
Unattended upgrade result: All upgrades installed
Packages with upgradable origin but kept back:
Ubuntu disco-updates:
snapd apport
Unattended-upgrades log:
Initial blacklist :
Initial whitelist:
Starting unattended upgrades script
Allowed origins are: o=Ubuntu,a=disco, o=Ubuntu,a=disco-security,
o=UbuntuESM,a=disco, o=Ubuntu,a=disco-updates
Packages that will be upgraded:
root@uu-sru-dd:~# 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.10ubuntu5.2 all automatic installation of
security upgrades
** Description changed:
[Impact]
* Packages kept back are listed in the email report, but it is not clear
from which origins they are installable. This information may help
administrators to decide if the packages need to be manually upgraded.
[Test Case]
* test_mail.py test is updated to check if the kept back packages are
reported per origin and this is checked at build time.
* For manual testing:
- 1. Configure u-u to allow upgrades from the -updates pocket and send email
with the upgrade report.
- 2. Set up the system to have a few packages upgradable from both the
-security and -updates pockets.
- 3. Mark a subset of packages which are upgradable as held, marking packages
from each of the pockets.
- 4. Run u-u and observe the kept packages listed in the email. Each package
is listed only in the allowed origin providing the highest version. (LP:
#1848697 covers listing them in all origins from which the packages could be
upgraded to.)
+ 1. Configure u-u to allow upgrades from the -updates pocket and send email
with the upgrade report.
+ 2. Set up the system to have a few packages upgradable from both the
-security and -updates pockets.
+ 3. Mark a subset of packages which are upgradable as held, marking packages
from each of the pockets.
+ 4. Run u-u and observe the kept packages listed in the email. Each package
is listed only in the allowed origin providing the highest version. (LP:
#1848697 covers listing them in all origins from which the packages could be
upgraded to.)
[Regression Potential]
* Unattended upgrades may crash while trying to perform updates or while
trying to send the summary email. Build-time tests and autopkgtests
include testing both functions.
--
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/1821376
Title:
Report packages kept back by origins
Status in unattended-upgrades package in Ubuntu:
Fix Released
Status in unattended-upgrades source package in Xenial:
Fix Committed
Status in unattended-upgrades source package in Bionic:
Fix Committed
Status in unattended-upgrades source package in Disco:
Fix Committed
Bug description:
[Impact]
* Packages kept back are listed in the email report, but it is not
clear from which origins they are installable. This information may
help administrators to decide if the packages need to be manually
upgraded.
[Test Case]
* test_mail.py test is updated to check if the kept back packages are
reported per origin and this is checked at build time.
* For manual testing:
1. Configure u-u to allow upgrades from the -updates pocket and send email
with the upgrade report.
2. Set up the system to have a few packages upgradable from both the
-security and -updates pockets.
3. Mark a subset of packages which are upgradable as held, marking packages
from each of the pockets.
4. Run u-u and observe the kept packages listed in the email. Each package
is listed only in the allowed origin providing the highest version. (LP:
#1848697 covers listing them in all origins from which the packages could be
upgraded to.)
[Regression Potential]
* Unattended upgrades may crash while trying to perform updates or
while trying to send the summary email. Build-time tests and
autopkgtests include testing both functions.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1821376/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
