ubuntu-support-status lists end-of-support packages (after EOL) as supported

[Matthias Andree]

Test Case
---------
1) Run ubuntu-support-status --show-unsupported and observe the count of unsupported packages and the count of packages supported until some future date.
2) Travel to the future and overshoot by a month.
3) Run ubuntu-support-status --unsupported and observe the unsupported count has not changed.

With the version of the package from -proposed the count in step 3 should be incremented by the quantity of packages supported until that future date e.g. if you have 8 unsupported and 8 packages supported until (1/2017) with the proposed version you should have 16 unsupported in (2/2017).

Regression Potential
--------------------
A return was missing say that packages were unsupported, so very very little.

Original Report
---------------
Please see the screen dump below. It contains a section "Supported until February 2015 (9m):", but it is April 2016, so the packages should NOT appear in the --show-supported list, and it should NOT be introduced with "Supported..." because the packages listed below that banner line are UNsupported.

------

$ LC_ALL=en_US.UTF-8 LANGUAGE=en LANG=en_US.UTF-8 ubuntu-support-status --show-supported
Support status summary of 'rho':

You have 29 packages (0.9%) supported until January 2017 (9m)
You have 245 packages (7.4%) supported until February 2015 (9m)
You have 201 packages (6.1%) supported until May 2017 (3y)
You have 2290 packages (68.9%) supported until May 2019 (5y)

You have 18 packages (0.5%) that can not/no-longer be downloaded
You have 539 packages (16.2%) that are unsupported
Supported until January 2017 (9m):
libclang-common-3.6-dev libclang1-3.6 libglamor-ltst0 libllvm3.6
linux-headers-3.13.0-65 linux-headers-3.13.0-65-generic
[...]

Supported until February 2015 (9m):
apparmor-docs apparmor-utils asciidoc autopoint bash-doc bsh
checkbox-qt chromium-browser chromium-browser-l10n
chromium-codecs-ffmpeg-extra comerr-dev dblatex debconf-doc
dh-autoreconf docbook-dsssl docbook-utils doxygen doxygen-latex
enblend enfuse expect faad foomatic-db-engine fortune-mod
[...]

ProblemType: BugDistroRelease: Ubuntu 14.04
Package: update-manager-core 1:0.196.14
ProcVersionSignature: Ubuntu 3.13.0-83.127-generic 3.13.11-ckt35
Uname: Linux 3.13.0-83-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.19
Aptdaemon:

Architecture: i386
Date: Sun Apr 24 10:29:43 2016
EcryptfsInUse: Yes
GsettingsChanges:
 b'com.ubuntu.update-manager' b'show-details' b'true'
 b'com.ubuntu.update-manager' b'first-run' b'false'
 b'com.ubuntu.update-manager' b'check-new-release-ignore' b"'natty'"
 b'com.ubuntu.update-manager' b'launch-time' b'1323564009'
PackageArchitecture: allSourcePackage: update-manager
UpgradeStatus: Upgraded to trusty on 2014-12-25 (486 days ago)

[Marc Deslauriers (mdeslaur)]

The ubuntu-support-status tool is deprecated and uses the outdated "Supported" field in the packages file to obtain information. The tool and field were used in Ubuntu 10.04 and earlier when we had a 3 year/5 year split between desktop and server packages.

We should prepare updates that remove this tool completely.

[Brian Murray (brian-murray)]

This was fixed in Yakkety shortly after the bug was reported.

https://bazaar.launchpad.net/~ubuntu-core-dev/update-manager/main/revision/2725

[Andy Whitcroft (apw)]

Hello Matthias, or anyone else affected,

Accepted update-manager into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/update-manager/1:16.04.4 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 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 to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

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

[Brian Murray (brian-murray)]

Hello Matthias, or anyone else affected,

Accepted update-manager into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/update-manager/1:0.196.22 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 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 to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

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

[Brian Murray (brian-murray)]

Hello Matthias, or anyone else affected,

Accepted update-manager into precise-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/update-manager/1:0.156.14.20 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 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 to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

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

[Brian Murray (brian-murray)]

I installed the version of update-manager, python3-update-manager, and update-manager-core from xenial proposed. I then travelled to November 28, 2021 and ran 'ubuntu-support-status --show-unsupported' and discovered all my packages were not supported.

Marking as v-done-xenial.

[Brian Murray (brian-murray)]

I installed the version of update-manager, python3-update-manager, and update-manager-core from trusty proposed. I then traveled to October 13, 2017 and ran 'ubuntu-support-status --show-unsupported' and discovered that 7 additional packages were unsupported.

Marking as v-done-trusty.

[Brian Murray (brian-murray)]

Before installing the version of update-manager in precise-proposed I ran "ubuntu-support-status --show-unsupported" and discovered that some packages went out of support earlier in the year. I then installed the -proposed versions of the package and then saw that the packages were no longer supported.

[Martin Pitt (pitti)]

The verification of the Stable Release Update for update-manager has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

[Launchpad Janitor (janitor)]

This bug was fixed in the package update-manager - 1:0.196.22

---------------
update-manager (1:0.196.22) trusty-proposed; urgency=medium

  * Correctly calculate the end of support, and return correctly when support
    has ended. Patch from Andrew Gaul, with thanks. (LP: #1574193)

 -- Brian Murray <email address hidden> Fri, 30 Sep 2016 09:45:52 -0700

[Launchpad Janitor (janitor)]

This bug was fixed in the package update-manager - 1:0.156.14.20

---------------
update-manager (1:0.156.14.20) precise-proposed; urgency=medium

  * Correctly calculate the end of support, and return correctly when support
    has ended. Patch from Andrew Gaul, with thanks. (LP: #1574193)

 -- Brian Murray <email address hidden> Fri, 30 Sep 2016 09:55:44 -0700

[Launchpad Janitor (janitor)]

This bug was fixed in the package update-manager - 1:16.04.4

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

  * Correctly calculate the end of support, and return correctly when support
    has ended. Patch from Andrew Gaul, with thanks. (LP: #1574193)

 -- Brian Murray <email address hidden> Fri, 30 Sep 2016 09:16:37 -0700