Activity log for bug #2038453

Date Who What changed Old value New value Message
2023-10-04 15:38:20 Julian Andres Klode bug added bug
2023-10-04 15:38:31 Julian Andres Klode nominated for series Ubuntu Jammy
2023-10-04 15:38:31 Julian Andres Klode bug task added apt (Ubuntu Jammy)
2023-10-04 15:38:31 Julian Andres Klode nominated for series Ubuntu Mantic
2023-10-04 15:38:31 Julian Andres Klode bug task added apt (Ubuntu Mantic)
2023-10-04 15:38:31 Julian Andres Klode nominated for series Ubuntu Lunar
2023-10-04 15:38:31 Julian Andres Klode bug task added apt (Ubuntu Lunar)
2023-10-04 15:38:31 Julian Andres Klode nominated for series Ubuntu Focal
2023-10-04 15:38:31 Julian Andres Klode bug task added apt (Ubuntu Focal)
2023-10-04 15:38:35 Julian Andres Klode apt (Ubuntu Mantic): status New Fix Released
2023-10-04 15:38:52 Julian Andres Klode apt (Ubuntu Lunar): status New Won't Fix
2023-10-04 15:44:29 Julian Andres Klode description [Impact] The snapshot service provides users access to older states of the archive with ease of use, and enables a consistent user experience across all supported releases, as otherwise users would have to rewrite their sources.list to make use of snapshots and set up pinning. [Test plan] The complete regression test suite in autopkgtests includes an automatic test case for this and the known limitations that have been fixed. Aside from that, it is also worthwhile to do an end-to-end test: Configure snapshot=yes for Ubuntu sources in your sources.list and 1. run apt update - it should not use snapshot 2. run apt update --snapshot 20231001T000000Z, it should download the snapshot 3. run apt install --snapshot 20231001T000000Z hello, it should install hello from the snapshot [Where problems could occur] The integration has been purposefully limited in how it works to reduce the impact it has on the APT code; hence it was possible to cherry-pick this into 22.04, 20.04, and even 18.04 with only a minor editorial change. This significantly limits the risk. This feature is only enabled for sources with snapshot=yes (.list) or Snapshot: yes (.sources) or other truthy values apt recognizes. Most users will not have such entries as they did not have an APT supporting it. This combined should ensure that users do not experience any regressions. However the feature may be lacking in some ways that we may want to address in follow up SRUs; it has not been used in the wild a lot. [Impact] The snapshot service provides users access to older states of the archive with ease of use, and enables a consistent user experience across all supported releases, as otherwise users would have to rewrite their sources.list to make use of snapshots and set up pinning; hence partners requested the feature be SRUed to older releases as well. [Test plan] The complete regression test suite in autopkgtests includes an automatic test case for this and the known limitations that have been fixed. Aside from that, it is also worthwhile to do an end-to-end test: Configure snapshot=yes for Ubuntu sources in your sources.list and 1. run apt update - it should not use snapshot 2. run apt update --snapshot 20231001T000000Z, it should download the snapshot 3. run apt install --snapshot 20231001T000000Z hello, it should install hello from the snapshot [Where problems could occur] The integration has been purposefully limited in how it works to reduce the impact it has on the APT code; hence it was possible to cherry-pick this into 22.04, 20.04, and even 18.04 with only a minor editorial change. This significantly limits the risk. This feature is only enabled for sources with snapshot=yes (.list) or Snapshot: yes (.sources) or other truthy values apt recognizes. Most users will not have such entries as they did not have an APT supporting it. This combined should ensure that users do not experience any regressions. However the feature may be lacking in some ways that we may want to address in follow up SRUs; it has not been used in the wild a lot.
2023-10-04 15:52:34 Julian Andres Klode description [Impact] The snapshot service provides users access to older states of the archive with ease of use, and enables a consistent user experience across all supported releases, as otherwise users would have to rewrite their sources.list to make use of snapshots and set up pinning; hence partners requested the feature be SRUed to older releases as well. [Test plan] The complete regression test suite in autopkgtests includes an automatic test case for this and the known limitations that have been fixed. Aside from that, it is also worthwhile to do an end-to-end test: Configure snapshot=yes for Ubuntu sources in your sources.list and 1. run apt update - it should not use snapshot 2. run apt update --snapshot 20231001T000000Z, it should download the snapshot 3. run apt install --snapshot 20231001T000000Z hello, it should install hello from the snapshot [Where problems could occur] The integration has been purposefully limited in how it works to reduce the impact it has on the APT code; hence it was possible to cherry-pick this into 22.04, 20.04, and even 18.04 with only a minor editorial change. This significantly limits the risk. This feature is only enabled for sources with snapshot=yes (.list) or Snapshot: yes (.sources) or other truthy values apt recognizes. Most users will not have such entries as they did not have an APT supporting it. This combined should ensure that users do not experience any regressions. However the feature may be lacking in some ways that we may want to address in follow up SRUs; it has not been used in the wild a lot. [Impact] The snapshot service provides users access to older states of the archive with ease of use, and enables a consistent user experience across all supported releases, as otherwise users would have to rewrite their sources.list to make use of snapshots and set up pinning; hence partners requested the feature be SRUed to older releases as well. [Test plan] The complete regression test suite in autopkgtests includes an automatic test case for this and the known limitations that have been fixed. Aside from that, it is also worthwhile to do an end-to-end test: Configure snapshot=yes for Ubuntu sources in your sources.list and 1. run apt update - it should not use snapshot 2. run apt update --snapshot 20231001T000000Z, it should download the snapshot 3. run apt install --snapshot 20231001T000000Z hello, it should install hello from the snapshot [Where problems could occur] The integration has been purposefully limited in how it works to reduce the impact it has on the APT code; hence it was possible to cherry-pick this into 22.04, 20.04, and even 18.04, with only a minor editorial change. This significantly limits the risk. This feature is only enabled for sources with snapshot=yes (.list) or Snapshot: yes (.sources) or other truthy values apt recognizes. Most users will not have such entries as they did not have an APT supporting it. This combined should ensure that users do not experience any regressions. However the feature may be lacking in some ways that we may want to address in follow up SRUs; it has not been used in the wild a lot.
2023-10-04 18:15:39 Mauricio Faria de Oliveira nominated for series Ubuntu Bionic
2023-10-04 18:15:39 Mauricio Faria de Oliveira bug task added apt (Ubuntu Bionic)
2023-10-04 18:15:45 Mauricio Faria de Oliveira apt (Ubuntu Bionic): status New Won't Fix
2023-10-04 18:16:32 Mauricio Faria de Oliveira bug task added ubuntu-pro
2023-10-04 18:16:40 Mauricio Faria de Oliveira nominated for series ubuntu-pro/18.04
2023-10-04 18:16:40 Mauricio Faria de Oliveira bug task added ubuntu-pro/18.04
2023-10-04 18:18:53 Mauricio Faria de Oliveira bug added subscriber Mauricio Faria de Oliveira
2023-10-04 18:19:05 Mauricio Faria de Oliveira bug added subscriber Support Engineering Sponsors
2023-10-04 18:40:43 Launchpad Janitor apt (Ubuntu Focal): status New Confirmed
2023-10-04 18:40:43 Launchpad Janitor apt (Ubuntu Jammy): status New Confirmed
2023-10-04 18:41:16 Mauricio Faria de Oliveira ubuntu-pro/18.04: status New Triaged
2023-10-06 10:28:29 Julian Andres Klode description [Impact] The snapshot service provides users access to older states of the archive with ease of use, and enables a consistent user experience across all supported releases, as otherwise users would have to rewrite their sources.list to make use of snapshots and set up pinning; hence partners requested the feature be SRUed to older releases as well. [Test plan] The complete regression test suite in autopkgtests includes an automatic test case for this and the known limitations that have been fixed. Aside from that, it is also worthwhile to do an end-to-end test: Configure snapshot=yes for Ubuntu sources in your sources.list and 1. run apt update - it should not use snapshot 2. run apt update --snapshot 20231001T000000Z, it should download the snapshot 3. run apt install --snapshot 20231001T000000Z hello, it should install hello from the snapshot [Where problems could occur] The integration has been purposefully limited in how it works to reduce the impact it has on the APT code; hence it was possible to cherry-pick this into 22.04, 20.04, and even 18.04, with only a minor editorial change. This significantly limits the risk. This feature is only enabled for sources with snapshot=yes (.list) or Snapshot: yes (.sources) or other truthy values apt recognizes. Most users will not have such entries as they did not have an APT supporting it. This combined should ensure that users do not experience any regressions. However the feature may be lacking in some ways that we may want to address in follow up SRUs; it has not been used in the wild a lot. [Impact] The snapshot service provides users access to older states of the archive with ease of use, and enables a consistent user experience across all supported releases, as otherwise users would have to rewrite their sources.list to make use of snapshots and set up pinning; hence partners requested the feature be SRUed to older releases as well. [Test plan] The complete regression test suite in autopkgtests includes an automatic test case for this and the known limitations that have been fixed. Aside from that, it is also worthwhile to do an end-to-end test: Configure snapshot=yes for Ubuntu sources in your sources.list and 1. run apt update - it should not use snapshot 2. run apt update --snapshot 20231001T000000Z, it should download the snapshot 3. run apt policy --snapshot 20231001T000000Z hello, it should show hello in the snapshot 4. run apt install --snapshot 20231001T000000Z hello, it should install hello from the snapshot 5. Run apt update 6. Observe snapshots are gone from /var/lib/apt/lists again [Where problems could occur] The integration has been purposefully limited in how it works to reduce the impact it has on the APT code; hence it was possible to cherry-pick this into 22.04, 20.04, and even 18.04, with only a minor editorial change. This significantly limits the risk. This feature is only enabled for sources with snapshot=yes (.list) or Snapshot: yes (.sources) or other truthy values apt recognizes. Most users will not have such entries as they did not have an APT supporting it. This combined should ensure that users do not experience any regressions. However the feature may be lacking in some ways that we may want to address in follow up SRUs; it has not been used in the wild a lot.
2023-10-06 10:28:51 Julian Andres Klode description [Impact] The snapshot service provides users access to older states of the archive with ease of use, and enables a consistent user experience across all supported releases, as otherwise users would have to rewrite their sources.list to make use of snapshots and set up pinning; hence partners requested the feature be SRUed to older releases as well. [Test plan] The complete regression test suite in autopkgtests includes an automatic test case for this and the known limitations that have been fixed. Aside from that, it is also worthwhile to do an end-to-end test: Configure snapshot=yes for Ubuntu sources in your sources.list and 1. run apt update - it should not use snapshot 2. run apt update --snapshot 20231001T000000Z, it should download the snapshot 3. run apt policy --snapshot 20231001T000000Z hello, it should show hello in the snapshot 4. run apt install --snapshot 20231001T000000Z hello, it should install hello from the snapshot 5. Run apt update 6. Observe snapshots are gone from /var/lib/apt/lists again [Where problems could occur] The integration has been purposefully limited in how it works to reduce the impact it has on the APT code; hence it was possible to cherry-pick this into 22.04, 20.04, and even 18.04, with only a minor editorial change. This significantly limits the risk. This feature is only enabled for sources with snapshot=yes (.list) or Snapshot: yes (.sources) or other truthy values apt recognizes. Most users will not have such entries as they did not have an APT supporting it. This combined should ensure that users do not experience any regressions. However the feature may be lacking in some ways that we may want to address in follow up SRUs; it has not been used in the wild a lot. [Impact] The snapshot service provides users access to older states of the archive with ease of use, and enables a consistent user experience across all supported releases, as otherwise users would have to rewrite their sources.list to make use of snapshots and set up pinning; hence partners requested the feature be SRUed to older releases as well. [Test plan] The complete regression test suite in autopkgtests includes an automatic test case for this and the known limitations that have been fixed. Aside from that, it is also worthwhile to do an end-to-end test: Configure snapshot=yes for Ubuntu sources in your sources.list and 1. run apt update - it should not use snapshot 2. run apt update --snapshot 20231001T000000Z, it should download the snapshot 3. run apt policy --snapshot 20231001T000000Z hello, it should show hello in the snapshot 4. run apt install --snapshot 20231001T000000Z hello, it should install hello from the snapshot 5. Run apt update; observe snapshot not being downloaded 6. Observe snapshots are gone from /var/lib/apt/lists again [Where problems could occur] The integration has been purposefully limited in how it works to reduce the impact it has on the APT code; hence it was possible to cherry-pick this into 22.04, 20.04, and even 18.04, with only a minor editorial change. This significantly limits the risk. This feature is only enabled for sources with snapshot=yes (.list) or Snapshot: yes (.sources) or other truthy values apt recognizes. Most users will not have such entries as they did not have an APT supporting it. This combined should ensure that users do not experience any regressions. However the feature may be lacking in some ways that we may want to address in follow up SRUs; it has not been used in the wild a lot.
2023-10-06 10:35:06 Julian Andres Klode apt (Ubuntu Jammy): status Confirmed In Progress
2023-10-06 10:35:09 Julian Andres Klode apt (Ubuntu Focal): status Confirmed In Progress
2023-10-14 06:23:01 Steve Langasek apt (Ubuntu Jammy): status In Progress Fix Committed
2023-10-14 06:23:03 Steve Langasek bug added subscriber Ubuntu Stable Release Updates Team
2023-10-14 06:23:07 Steve Langasek bug added subscriber SRU Verification
2023-10-14 06:23:10 Steve Langasek tags verification-needed verification-needed-jammy
2023-10-14 06:24:26 Steve Langasek apt (Ubuntu Focal): status In Progress Fix Committed
2023-10-14 06:24:32 Steve Langasek tags verification-needed verification-needed-jammy verification-needed verification-needed-focal verification-needed-jammy
2023-10-30 13:59:49 Julian Andres Klode tags verification-needed verification-needed-focal verification-needed-jammy verification-done-focal verification-done-jammy verification-needed
2023-10-30 13:59:53 Julian Andres Klode tags verification-done-focal verification-done-jammy verification-needed verification-done verification-done-focal verification-done-jammy
2023-11-15 07:04:50 Launchpad Janitor apt (Ubuntu Focal): status Fix Committed Fix Released
2023-11-15 07:04:54 Chris Halse Rogers removed subscriber Ubuntu Stable Release Updates Team
2023-11-15 07:05:08 Launchpad Janitor apt (Ubuntu Jammy): status Fix Committed Fix Released
2024-04-18 15:05:31 Heitor Alves de Siqueira ubuntu-pro/18.04: status Triaged In Progress
2024-06-03 13:30:25 Heitor Alves de Siqueira ubuntu-pro/18.04: status In Progress Fix Committed
2024-06-24 13:42:18 Heitor Alves de Siqueira ubuntu-pro/18.04: status Fix Committed Fix Released