Update EoL dates for 16.04 LTS and 21.04 so they are not on weekends

This, being a cherry-pick, results in differences remaining in ubuntu.csv between Impish and the stable releases. Don't we want to just copy the latest back instead?

While I agree with the idea that we should copy the latest back I don't think its worth spending the extra effort on this time for two reasons.

1) The changes are for dates which have already passed the most recent of which is 2020-01-18.
2) The packages need to be built in a PPA w/ -security and not -updates which is not as trivial as just re-uploading the package to the queue.

Additionally, adding new releases (e.g. Impish) has always been a cherry-pick. How about we update the new release process document to indicate that ubuntu.csv should be copied from the development release so that things end up being consistent?

Hello Brian, or anyone else affected,

Accepted distro-info-data into hirsute-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/distro-info-data/0.46ubuntu3 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, what testing has been performed on the package and change the tag from verification-needed-hirsute to verification-done-hirsute. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-hirsute. 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.

Hello Brian, or anyone else affected,

Accepted distro-info-data into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/distro-info-data/0.43ubuntu1.6 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, what testing has been performed on the package and change the tag from verification-needed-focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-focal. 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.

Hello Brian, or anyone else affected,

Accepted distro-info-data into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/distro-info-data/0.37ubuntu0.11 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, what testing has been performed on the package 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 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.

Hello Brian, or anyone else affected,

Accepted distro-info-data into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/distro-info-data/0.28ubuntu0.18 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, what testing has been performed on the package 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.

> How about we update the new release process document to indicate that ubuntu.csv should be copied from the development release so that things end up being consistent?

+1

> The packages need to be built in a PPA w/ -security and not -updates which is not as trivial as just re-uploading the package to the queue.

I thought distro-info-data was an exception as it's trivially verifiable that it's only shipping non-pocket-dependent CSVs? Either way, maybe we can document the requirement here, too.

All autopkgtests for the newly accepted distro-info-data (0.46ubuntu3) for hirsute have finished running.
The following regressions have been reported in tests triggered by the package:

distro-info-data/0.46ubuntu3 (arm64, ppc64el, amd64, s390x, armhf)

Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-migration/hirsute/update_excuses.html#distro-info-data

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

Hello Brian, or anyone else affected,

Accepted distro-info-data into hirsute-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/distro-info-data/0.46ubuntu4 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, what testing has been performed on the package and change the tag from verification-needed-hirsute to verification-done-hirsute. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-hirsute. 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.

The verification passed for hirsute.

(hirsute-amd64)root@impulse:/home/bdmurray/source-trees/snapcore/models# grep "xenial\|hirsute" /usr/share/distro-info/ubuntu.csv
16.04 LTS,Xenial Xerus,xenial,2015-10-22,2016-04-21,2021-04-21,2021-04-21,2024-04-23
21.04,Hirsute Hippo,hirsute,2020-10-22,2021-04-22,2022-01-20
(hirsute-amd64)root@impulse:/home/bdmurray/source-trees/snapcore/models# distro-info --devel
impish
(hirsute-amd64)root@impulse:/home/bdmurray/source-trees/snapcore/models# distro-info --supported
bionic
focal
hirsute
impish
(hirsute-amd64)root@impulse:/home/bdmurray/source-trees/snapcore/models# distro-info --stable
hirsute
(hirsute-amd64)root@impulse:/home/bdmurray/source-trees/snapcore/models# distro-info --stable --fullname
Ubuntu 21.04 "Hirsute Hippo"
(hirsute-amd64)root@impulse:/home/bdmurray/source-trees/snapcore/models# distro-info --devel --release
21.10
(hirsute-amd64)root@impulse:/home/bdmurray/source-trees/snapcore/models# distro-info --stable --date=2021-10-22
impish
(hirsute-amd64)root@impulse:/home/bdmurray/source-trees/snapcore/models# apt-cache policy distro-info-data
distro-info-data:
  Installed: 0.46ubuntu4
  Candidate: 0.46ubuntu4
  Version table:
 *** 0.46ubuntu4 500
        500 http://192.168.10.7/ubuntu hirsute-proposed/main amd64 Packages
        100 /var/lib/dpkg/status

The verification also passed on focal:

Setting up distro-info-data (0.43ubuntu1.6) ...
Setting up distro-info (0.23ubuntu1) ...
(focal-amd64)root@impulse:/tmp# grep "xenial\|hirsute" /usr/share/distro-info/ubuntu.csv
16.04 LTS,Xenial Xerus,xenial,2015-10-22,2016-04-21,2021-04-21,2021-04-21,2024-04-23
21.04,Hirsute Hippo,hirsute,2020-10-22,2021-04-22,2022-01-20
(focal-amd64)root@impulse:/tmp# distro-info --devel
impish
(focal-amd64)root@impulse:/tmp# distro-info --supported
bionic
focal
hirsute
impish
(focal-amd64)root@impulse:/tmp# distro-info --stable
hirsute
(focal-amd64)root@impulse:/tmp# distro-info --stable --fullname
Ubuntu 21.04 "Hirsute Hippo"
(focal-amd64)root@impulse:/tmp# distro-info --devel --release
21.10
(focal-amd64)root@impulse:/tmp# distro-info --stable --date=2021-10-22
impish

The verification also passed on bionic:

Setting up distro-info-data (0.37ubuntu0.11) ...
Setting up distro-info (0.18ubuntu0.18.04.1) ...
(bionic-amd64)root@impulse:/tmp# grep "xenial\|hirsute" /usr/share/distro-info/ubuntu.csv
16.04 LTS,Xenial Xerus,xenial,2015-10-22,2016-04-21,2021-04-21,2021-04-21,2024-04-23
21.04,Hirsute Hippo,hirsute,2020-10-22,2021-04-22,2022-01-20
(bionic-amd64)root@impulse:/tmp# distro-info --devel
impish
(bionic-amd64)root@impulse:/tmp# distro-info --supported
bionic
focal
hirsute
impish
(bionic-amd64)root@impulse:/tmp# distro-info --stable
hirsute
(bionic-amd64)root@impulse:/tmp# distro-info --stable --fullname
Ubuntu 21.04 "Hirsute Hippo"
(bionic-amd64)root@impulse:/tmp# distro-info --devel --release
21.10
(bionic-amd64)root@impulse:/tmp# distro-info --stable --date=2021-10-22
impish

And the verification also passed on xenial:

Setting up distro-info-data (0.28ubuntu0.18) ...
Setting up distro-info (0.14ubuntu0.2) ...
(xenial-amd64)root@impulse:/tmp# grep "xenial\|hirsute" /usr/share/distro-info/ubuntu.csv
16.04 LTS,Xenial Xerus,xenial,2015-10-22,2016-04-21,2021-04-21,2021-04-21,2024-04-23
21.04,Hirsute Hippo,hirsute,2020-10-22,2021-04-22,2022-01-20
(xenial-amd64)root@impulse:/tmp# distro-info --devel
impish
(xenial-amd64)root@impulse:/tmp# distro-info --supported
bionic
focal
hirsute
impish
(xenial-amd64)root@impulse:/tmp# distro-info --stable
hirsute
(xenial-amd64)root@impulse:/tmp# distro-info --stable --fullname
Ubuntu 21.04 "Hirsute Hippo"
(xenial-amd64)root@impulse:/tmp# distro-info --devel --release
21.10
(xenial-amd64)root@impulse:/tmp# distro-info --stable --date=2021-10-22
impish

Yeah, distro-info-data is a pure-data package so it can just be copied to -security as-is. Let me do that.

This bug was fixed in the package distro-info-data - 0.46ubuntu4

---------------
distro-info-data (0.46ubuntu4) hirsute; urgency=medium

  * Update debian.csv to the one from distro-info-data version 0.51 which
    updates bullseye's release date, bookworm's creation date, and buster's
    EoL date based on the updated planned bullseye release date. This fixes an
    autopkgtest failure.

distro-info-data (0.46ubuntu3) hirsute; urgency=medium

  * Move Ubuntu EoLs off weekend days. (LP: #1939457)

 -- Brian Murray <email address hidden> Fri, 13 Aug 2021 10:52:00 -0700

The verification of the Stable Release Update for distro-info-data has completed successfully and the package is now being 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.

This bug was fixed in the package distro-info-data - 0.43ubuntu1.6

---------------
distro-info-data (0.43ubuntu1.6) focal; urgency=medium

  * Move Ubuntu EoLs off weekend days. (LP: #1939457)

 -- Brian Murray <email address hidden> Tue, 10 Aug 2021 15:12:42 -0700

This bug was fixed in the package distro-info-data - 0.37ubuntu0.11

---------------
distro-info-data (0.37ubuntu0.11) bionic; urgency=medium

  * Move Ubuntu EoLs off weekend days. (LP: #1939457)

 -- Brian Murray <email address hidden> Tue, 10 Aug 2021 15:18:17 -0700

This bug was fixed in the package distro-info-data - 0.28ubuntu0.18

---------------
distro-info-data (0.28ubuntu0.18) xenial; urgency=medium

  * Move Ubuntu EoLs off weekend days. (LP: #1939457)

 -- Brian Murray <email address hidden> Tue, 10 Aug 2021 15:20:10 -0700