Keep the -dev binary package in sync with Debian

[Lucas Kanashiro]

The Server team is planning to split src:docker.io, src:containerd and src:runc to improve their maintenance. The problem is that when we do major updates of src:docker.io or src:containerd or src:runc in all supported releases, very often we break reverse dependencies relying on the library (-dev package) provided by them. This is kind of expected, as stated in the SRU exception, but it consumes a lot of time of our team fixing those packages via SRUs.

The solution is to create src:docker.io-app, src:containerd-app and src:runc-app to provide only the application binary package, so we can keep updating it across all supported releases without changing the library. And make src:docker.io, src:containerd and src:runc track what we have in Debian, but making them not provide the application binary anymore (docker.io, containerd and runc binaries). With that, we will not break packages in the archive depending on their library packages while doing docker, containerd and runc application (docker.io, containerd and runc binaries) updates.

This bug is going to cover the update of src:docker.io, src:containerd and src:runc to grab what we have in Debian and add a simple delta to make them not provide the application binary.

[Sergio Durigan Junior (sergiodj)]

Lucas and I talked about this bug and I will review his debdiff (which he'll post soon).

[Lucas Kanashiro (lucaskanashiro)]

Diff (just the debian directory to reduce the size of the file) of the proposed src:docker.io targeting mantic.

[Sergio Durigan Junior (sergiodj)]

Hey Lucas,

Thanks for the debdiff. I applied it successfully against the pkg/ubuntu/devel branch of docker.io's git-ubuntu repository, which makes things easier for me to review.

I'll leave questions about the changes here as I review them.

- With this merge, you're effectively deleting the Ubuntu-specific d/changelog entries for old versions of docker.io. Is this something we may want to keep, especially considering that the package still carries delta?

- When I run "uscan --download-current-version", I'm now experiencing the same issue that I have with the Debian package:

$ uscan --download-current-version
uscan warn: In debian/watch no matching hrefs for version 20.10.24 in watch line
  https://github.com/moby/moby/tags archive/refs/tags/v(\d\S*)\.tar\.gz debian ./debian/get-orig-source.sh

I haven't investigated this problem in detail, but the d/watch we're currently carrying in Ubuntu has this comment on top, which seems to be related:

# github's ".../tags" paginates too soon, so we lose historical versions too early for tianon's tastes (hence uscan.tianon.xyz)

[Sergio Durigan Junior (sergiodj)]

- You're getting rid of the docker.io binary package, so you can also get rid of the following snippet on d/rules:

override_dh_gencontrol:
 echo 'libc:Built-Using=$(BUILT_LIBC)' >> debian/docker.io.substvars
 dh_gencontrol

- Since you'll be providing docker.io from the new docker.io-app package, maybe it makes more sense to move the docker-doc package there as well.

- Same comment for the contents under debian/tests/. I think they should be moved to the docker.io-app package.

[Lucas Kanashiro (lucaskanashiro)]

Thanks for the review Sergio! Let me answer each point below:

- d/changelog changes: I understand your point but in my perspective we haven't had a delta compared to Debian so far. I am saying that because src:docker.io has been a fork of the Debian package and diverged completely in the last years, the last Debian upload in the Ubuntu src:docker.io is version 1.11.2~ds1-1 from 8 years ago. Due to that, I believe it is a good idea to start fresh again, and now we are adding a delta on top of what we have in Debian, and keep tracking those change from now on. WDYT?

- uscan issue: You are right, I was also not able to get the upstream tarballs with uscan. Due to that, I am going to use our old d/watch (using tianon's service to avoid some of those issues) for now, but I'd like to investigate this a bit more to make sure we really need this delta in future uploads.

- override_dh_gencontrol in d/rules: Agreed. It is going to be removed.

- docker-doc binary package: Agreed. I moved this binary package to src:docker.io-app and I am going to remove it from src:docker.io.

- d/tests removal: Agreed. The tests are already in src:docker.io-app, I am going to remove them from src:docker.io.

[Sergio Durigan Junior (sergiodj)]

Thanks, Lucas.

- d/changelog changes: Works for me. As we discussed previously, I'm fine with your final decision since you're the one who will be taking care of the package.

Meanwhile, I was able to build the package locally and found some final nits:

- lintian is telling me about missing NOTICE files for the Apache license:

E: docker.io source: missing-notice-file-for-apache-license [cli/NOTICE]
E: docker.io source: missing-notice-file-for-apache-license [engine/NOTICE]
E: docker.io source: missing-notice-file-for-apache-license [engine/vendor/code.cloudfoundry.org/clock/NOTICE]
E: docker.io source: missing-notice-file-for-apache-license [swarmkit/vendor/code.cloudfoundry.org/clock/NOTICE]

I think this is a side effect of the docker-docs migration.

The only binary package generated by docker.io now is golang-github-docker-docker-dev. It installs successfully.

There are no dep8 tests in the package anymore, as they've been moved to docker.io-app.

The rest of the package LGTM, so I'm giving it a +1 already. Feel free to upload once you address the lintian errors above.

[Lucas Kanashiro (lucaskanashiro)]

Thanks, Sergio! Fixed the lintian error and uploaded the package (now that src:docker.io-app and its binaries already landed in the release pocket).

[Launchpad Janitor (janitor)]

This bug was fixed in the package docker.io - 20.10.24+dfsg1-1ubuntu2

---------------
docker.io (20.10.24+dfsg1-1ubuntu2) mantic; urgency=medium

  * d/p/test--skip-daemon-oci-linux-pbuilder-tests.patch: always skip engine
    test TestGetSourceMount which is failing in LP. The Debian maintainer
    already skipped this test when the package is built with pbuilder, now
    this condition has been removed and the test is always skipped.

docker.io (20.10.24+dfsg1-1ubuntu1) mantic; urgency=medium

  * Merge from Debian unstable (LP: #2022390, #1946376). Make src:docker.io
    follow Debian and src:docker.io-app is going to ship the application and
    documentation with vendorized dependencies so we can keep updating just the
    application across all supported releases.
  * Added changes:
    - d/control: remove binary paragraghs for docker.io and docker-doc.
    - d/docker-doc.docs: removed together with the docker-doc binary package.
    - d/docker.io.*: remove all packaging related files associated to the
      docker.io binary package.
    - d/p/engine-allow-exclude-unit-test.patch: add patch to allow excluding
      extra directories when running engine unit tests.
    - d/rules:
      + Do not run aufs related unit tests in the engine component.
      + Do not install apparmor profile for docker.io.
      + remove override_dh_gencontrol, since docker.io binary package was also
        removed.
    - d/tests: remove since all tests are related to the docker application
      provided by docker.io binary package.
    - d/golang-github-docker-docker-dev.docs: install NOTICE files to comply
      with Apache license.

 -- Lucas Kanashiro <email address hidden> Tue, 06 Jun 2023 21:29:06 -0300

[Lucas Kanashiro (lucaskanashiro)]

In order to make this work, we also need to introduce the src:docker.io-app in all supported releases.

[Launchpad Janitor (janitor)]

This bug was fixed in the package containerd - 1.6.20~ds1-1ubuntu2

---------------
containerd (1.6.20~ds1-1ubuntu2) mantic; urgency=medium

  * d/p/0009-Skip-test-trying-to-set-OOM-score.patch: fix FTBFS.

containerd (1.6.20~ds1-1ubuntu1) mantic; urgency=medium

  * Merge from Debian unstable (LP: #2022390). Make src:containerd
    follow Debian and src:containerd-app is going to ship the application with
    vendorized dependencies so we can keep updating just the application across
    all supported releases.
  * Added changes:
    - d/control: remove the binary paragraph for containerd.
    - d/containerd.*: remove all packaging related files associated to the
      containerd binary package.
    - d/tests/{cri-integration,integration}: remove since they depend on the
      containerd binary package which is not provided by this source package
      anymore.
    - d/rules: remove execute_after_dh_auto_build target, it is changing
      content in the containerd binary package. Also avoid installing binaries
      in the library package.
    - d/golang-github-containerd-containerd-dev.install: remove this file, it
      is causing a FTBFS, no need to have it in place, the library files are
      already installed correctly without it.
    - d/golang-github-containerd-containerd-dev.docs: install NOTICE file to
      be compliant with the Apache 2 license.

 -- Lucas Kanashiro <email address hidden> Wed, 21 Jun 2023 23:07:52 -0300

[Steve Langasek (vorlon)]

Hello Lucas, or anyone else affected,

Accepted containerd into lunar-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/containerd/1.6.12-0ubuntu3.2 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-lunar to verification-done-lunar. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-lunar. 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.

[Steve Langasek (vorlon)]

Hello Lucas, or anyone else affected,

Accepted containerd-app into lunar-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/containerd-app/1.7.2-0ubuntu1~23.04.1 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-lunar to verification-done-lunar. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-lunar. 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.

[Steve Langasek (vorlon)]

Hello Lucas, or anyone else affected,

Accepted containerd into kinetic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/containerd/1.6.12-0ubuntu1~22.10.3 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-kinetic to verification-done-kinetic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-kinetic. 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.

[Steve Langasek (vorlon)]

Hello Lucas, or anyone else affected,

Accepted containerd-app into kinetic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/containerd-app/1.7.2-0ubuntu1~22.10.1 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-kinetic to verification-done-kinetic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-kinetic. 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.

[Steve Langasek (vorlon)]

Hello Lucas, or anyone else affected,

Accepted containerd into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/containerd/1.6.12-0ubuntu1~22.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 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-jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-jammy. 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.

[Steve Langasek (vorlon)]

Hello Lucas, or anyone else affected,

Accepted containerd-app into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/containerd-app/1.7.2-0ubuntu1~22.04.1 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-jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-jammy. 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.

[Steve Langasek (vorlon)]

Hello Lucas, or anyone else affected,

Accepted containerd into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/containerd/1.6.12-0ubuntu1~20.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 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.

[Steve Langasek (vorlon)]

Hello Lucas, or anyone else affected,

Accepted containerd-app into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/containerd-app/1.7.2-0ubuntu1~20.04.1 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.

[Steve Langasek (vorlon)]

Hello Lucas, or anyone else affected,

Accepted docker.io into lunar-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/docker.io/20.10.21-0ubuntu3.1 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-lunar to verification-done-lunar. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-lunar. 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.

[Steve Langasek (vorlon)]

Hello Lucas, or anyone else affected,

Accepted docker.io-app into lunar-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/docker.io-app/20.10.25-0ubuntu1~23.04.1 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-lunar to verification-done-lunar. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-lunar. 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.

[Steve Langasek (vorlon)]

Hello Lucas, or anyone else affected,

Accepted docker.io into kinetic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/docker.io/20.10.21-0ubuntu1~22.10.3 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-kinetic to verification-done-kinetic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-kinetic. 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.

[Steve Langasek (vorlon)]

Hello Lucas, or anyone else affected,

Accepted docker.io-app into kinetic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/docker.io-app/20.10.25-0ubuntu1~22.10.1 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-kinetic to verification-done-kinetic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-kinetic. 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.

[Steve Langasek (vorlon)]

Hello Lucas, or anyone else affected,

Accepted docker.io into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/docker.io/20.10.21-0ubuntu1~22.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 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-jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-jammy. 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.

[Steve Langasek (vorlon)]

Hello Lucas, or anyone else affected,

Accepted docker.io-app into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/docker.io-app/20.10.25-0ubuntu1~22.04.1 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-jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-jammy. 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.

[Steve Langasek (vorlon)]

Hello Lucas, or anyone else affected,

Accepted docker.io into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/docker.io/20.10.21-0ubuntu1~20.04.3 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.

[Steve Langasek (vorlon)]

Hello Lucas, or anyone else affected,

Accepted docker.io-app into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/docker.io-app/20.10.25-0ubuntu1~20.04.1 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.

[Ubuntu SRU Bot (ubuntu-sru-bot)]

All autopkgtests for the newly accepted containerd (1.6.12-0ubuntu1~20.04.4) for focal have finished running.
The following regressions have been reported in tests triggered by the package:

containerd/1.6.12-0ubuntu1~20.04.4 (arm64, ppc64el, s390x)

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/focal/update_excuses.html#containerd

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

Thank you!

[Ubuntu SRU Bot (ubuntu-sru-bot)]

All autopkgtests for the newly accepted containerd (1.6.12-0ubuntu1~22.10.3) for kinetic have finished running.
The following regressions have been reported in tests triggered by the package:

containerd/1.6.12-0ubuntu1~22.10.3 (amd64, arm64, ppc64el, s390x)

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/kinetic/update_excuses.html#containerd

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

Thank you!

[Ubuntu SRU Bot (ubuntu-sru-bot)]

All autopkgtests for the newly accepted docker.io (20.10.21-0ubuntu1~20.04.3) for focal have finished running.
The following regressions have been reported in tests triggered by the package:

docker.io/20.10.21-0ubuntu1~20.04.3 (arm64, ppc64el, s390x)

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/focal/update_excuses.html#docker.io

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

Thank you!

[Ubuntu SRU Bot (ubuntu-sru-bot)]

All autopkgtests for the newly accepted containerd (1.6.12-0ubuntu3.2) for lunar have finished running.
The following regressions have been reported in tests triggered by the package:

containerd/1.6.12-0ubuntu3.2 (amd64, arm64, ppc64el, s390x)

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/lunar/update_excuses.html#containerd

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

Thank you!

[Ubuntu SRU Bot (ubuntu-sru-bot)]

All autopkgtests for the newly accepted containerd (1.6.12-0ubuntu1~22.04.4) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:

containerd/1.6.12-0ubuntu1~22.04.4 (amd64, arm64, ppc64el, s390x)

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/jammy/update_excuses.html#containerd

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

Thank you!

[Ubuntu SRU Bot (ubuntu-sru-bot)]

All autopkgtests for the newly accepted docker.io (20.10.21-0ubuntu1~22.10.3) for kinetic have finished running.
The following regressions have been reported in tests triggered by the package:

docker.io/20.10.21-0ubuntu1~22.10.3 (amd64, arm64, ppc64el, s390x)

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/kinetic/update_excuses.html#docker.io

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

Thank you!

[Lucas Kanashiro (lucaskanashiro)]

The DEP-8 tests need to be removed from src:containerd and src:docker.io since the binaries tested were moved to the -app package. I uploaded both to all series removing the tests (they are in the -app packages already).

[Ubuntu SRU Bot (ubuntu-sru-bot)]

All autopkgtests for the newly accepted docker.io (20.10.21-0ubuntu3.1) for lunar have finished running.
The following regressions have been reported in tests triggered by the package:

docker.io/20.10.21-0ubuntu3.1 (amd64, arm64, ppc64el, s390x)

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/lunar/update_excuses.html#docker.io

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

Thank you!

[Ubuntu SRU Bot (ubuntu-sru-bot)]

All autopkgtests for the newly accepted docker.io (20.10.21-0ubuntu1~22.04.4) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:

docker.io/20.10.21-0ubuntu1~22.04.4 (arm64, ppc64el, s390x)

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/jammy/update_excuses.html#docker.io

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

Thank you!

[Steve Langasek (vorlon)]

Hello Lucas, or anyone else affected,

Accepted containerd into lunar-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/containerd/1.6.12-0ubuntu3.3 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-lunar to verification-done-lunar. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-lunar. 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.

[Steve Langasek (vorlon)]

Hello Lucas, or anyone else affected,

Accepted containerd into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/containerd/1.6.12-0ubuntu1~22.04.5 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-jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-jammy. 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.

[Steve Langasek (vorlon)]

Hello Lucas, or anyone else affected,

Accepted containerd into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/containerd/1.6.12-0ubuntu1~20.04.5 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.

[Lucas Kanashiro (lucaskanashiro)]

Kinetic has reached EOL and no more updates are going to be accepted.

[Steve Langasek (vorlon)]

Hello Lucas, or anyone else affected,

Accepted docker.io into lunar-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/docker.io/20.10.21-0ubuntu3.2 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-lunar to verification-done-lunar. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-lunar. 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.

[Steve Langasek (vorlon)]

Hello Lucas, or anyone else affected,

Accepted docker.io into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/docker.io/20.10.21-0ubuntu1~22.04.5 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-jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-jammy. 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.

[Steve Langasek (vorlon)]

Hello Lucas, or anyone else affected,

Accepted docker.io into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/docker.io/20.10.21-0ubuntu1~20.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 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.

[Ubuntu SRU Bot (ubuntu-sru-bot)]

All autopkgtests for the newly accepted containerd (1.6.12-0ubuntu3.2) for lunar have finished running.
The following regressions have been reported in tests triggered by the package:

containerd/1.6.12-0ubuntu3.2 (amd64, arm64, ppc64el, s390x)

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/lunar/update_excuses.html#containerd

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

Thank you!

[Ubuntu SRU Bot (ubuntu-sru-bot)]

All autopkgtests for the newly accepted containerd (1.6.12-0ubuntu1~20.04.4) for focal have finished running.
The following regressions have been reported in tests triggered by the package:

containerd/1.6.12-0ubuntu1~20.04.4 (amd64, arm64, ppc64el, s390x)

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/focal/update_excuses.html#containerd

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

Thank you!

[Ubuntu SRU Bot (ubuntu-sru-bot)]

All autopkgtests for the newly accepted docker.io (20.10.21-0ubuntu3.1) for lunar have finished running.
The following regressions have been reported in tests triggered by the package:

docker.io/20.10.21-0ubuntu3.1 (amd64, arm64, ppc64el, s390x)

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/lunar/update_excuses.html#docker.io

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

Thank you!

[Ubuntu SRU Bot (ubuntu-sru-bot)]

All autopkgtests for the newly accepted containerd (1.6.12-0ubuntu1~22.04.4) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:

containerd/1.6.12-0ubuntu1~22.04.4 (amd64, arm64, ppc64el, s390x)

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/jammy/update_excuses.html#containerd

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

Thank you!

[Ubuntu SRU Bot (ubuntu-sru-bot)]

All autopkgtests for the newly accepted docker.io (20.10.21-0ubuntu1~20.04.3) for focal have finished running.
The following regressions have been reported in tests triggered by the package:

docker.io/20.10.21-0ubuntu1~20.04.3 (amd64, arm64, ppc64el, s390x)

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/focal/update_excuses.html#docker.io

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

Thank you!

[Ubuntu SRU Bot (ubuntu-sru-bot)]

All autopkgtests for the newly accepted docker.io (20.10.21-0ubuntu1~22.04.4) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:

docker.io/20.10.21-0ubuntu1~22.04.4 (amd64, arm64, ppc64el, s390x)

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/jammy/update_excuses.html#docker.io

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

Thank you!

[Lucas Kanashiro (lucaskanashiro)]

Since there is no more regressions (all addressed), I'll be performing the same verification we do for regular container stack backport which is running autopkgtest.

[Lucas Kanashiro (lucaskanashiro)]

# Verification

I downloaded the source and binaries from -proposed for each package and ran autopkgtest locally using them:

## Lunar

### docker.io-app

autopkgtest [18:07:09]: @@@@@@@@@@@@@@@@@@@@ summary
basic-smoke PASS
docker-in-lxd PASS

### containerd-app

autopkgtest [17:55:46]: @@@@@@@@@@@@@@@@@@@@ summary
basic-smoke PASS

## Jammy

### docker.io-app

autopkgtest [18:04:44]: @@@@@@@@@@@@@@@@@@@@ summary
basic-smoke PASS
docker-in-lxd PASS

### containerd-app

autopkgtest [17:51:19]: @@@@@@@@@@@@@@@@@@@@ summary
basic-smoke PASS

## Focal

### docker.io-app

autopkgtest [18:07:09]: @@@@@@@@@@@@@@@@@@@@ summary
basic-smoke PASS
docker-in-lxd PASS

### containerd-app

autopkgtest [17:55:46]: @@@@@@@@@@@@@@@@@@@@ summary
basic-smoke PASS

[Launchpad Janitor (janitor)]

This bug was fixed in the package containerd - 1.6.12-0ubuntu1~20.04.5

---------------
containerd (1.6.12-0ubuntu1~20.04.5) focal; urgency=medium

  * d/tests: remove since the containerd binary package is now provided by
    src:containerd-app.

containerd (1.6.12-0ubuntu1~20.04.4) focal; urgency=medium

  * Do not provided the containerd binary package anymore (LP: #2022390).
    The containerd binary package is now provided by src:containerd-app.
    - d/control: remove the containerd binary package paragraph.
    - d/containerd.*: remove all files related to the containerd binary
      package.
    - d/docs: remove application documentation.
    - d/rules: remove override_dh_installsystemd.

 -- Lucas Kanashiro <email address hidden> Mon, 17 Jul 2023 16:13:38 -0300

[Launchpad Janitor (janitor)]

This bug was fixed in the package containerd-app - 1.7.2-0ubuntu1~20.04.1

---------------
containerd-app (1.7.2-0ubuntu1~20.04.1) focal; urgency=medium

  * Backport version from Mantic to Focal (LP: #2023694, #2022390).
    - Build with Go 1.20
      + d/control: b-d on golang-1.20-go instead of golang-go.
      + d/rules: add Go 1.20 to $PATH.

 -- Lucas Kanashiro <email address hidden> Thu, 29 Jun 2023 17:39:58 -0300

[Launchpad Janitor (janitor)]

This bug was fixed in the package docker.io - 20.10.21-0ubuntu1~20.04.4

---------------
docker.io (20.10.21-0ubuntu1~20.04.4) focal; urgency=medium

  * d/tests: remove since docker.io binary package is now provided by
    src:docker.io-app, and the tests were moved to it.

docker.io (20.10.21-0ubuntu1~20.04.3) focal; urgency=medium

  * Do not provide the docker{.io,-doc} binary packages anymore (LP: #2022390).
    Those binary packages are now provided by src:docker.io-app.
    - d/control: remove docker{.io,-doc} binary package paragraphs.
    - d/docker{.io,-doc}*: remove all files related to the removed binaries.
    - d/rules: remove
      override_dh_{installinit,installsystemd,installudev,install}.

 -- Lucas Kanashiro <email address hidden> Mon, 17 Jul 2023 16:22:27 -0300

[Chris Halse Rogers (raof)]

The verification of the Stable Release Update for containerd 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.

[Launchpad Janitor (janitor)]

This bug was fixed in the package docker.io-app - 20.10.25-0ubuntu1~20.04.1

---------------
docker.io-app (20.10.25-0ubuntu1~20.04.1) focal; urgency=medium

  * Backport version from Mantic to Focal (LP: #2023694, #2022390)
    - Build with Go 1.18
      + d/control: b-d on golang-1.18-go intead of golang-go
      + d/rules: add Go 1.18 to $PATH

 -- Lucas Kanashiro <email address hidden> Thu, 29 Jun 2023 18:55:06 -0300

[Launchpad Janitor (janitor)]

This bug was fixed in the package containerd - 1.6.12-0ubuntu1~22.04.5

---------------
containerd (1.6.12-0ubuntu1~22.04.5) jammy; urgency=medium

  * d/tests: remove since the containerd binary package is now provided by
    src:containerd-app.

containerd (1.6.12-0ubuntu1~22.04.4) jammy; urgency=medium

  * Do not provided the containerd binary package anymore (LP: #2022390).
    The containerd binary package is now provided by src:containerd-app.
    - d/control: remove the containerd binary package paragraph.
    - d/containerd.*: remove all files related to the containerd binary
      package.
    - d/docs: remove application documentation.
    - d/rules: remove override_dh_installsystemd.

 -- Lucas Kanashiro <email address hidden> Mon, 17 Jul 2023 16:11:59 -0300

[Launchpad Janitor (janitor)]

This bug was fixed in the package containerd-app - 1.7.2-0ubuntu1~22.04.1

---------------
containerd-app (1.7.2-0ubuntu1~22.04.1) jammy; urgency=medium

  * Backport version from Mantic to Jammy (LP: #2023694, #2022390).
    - Build with Go 1.20
      + d/control: b-d on golang-1.20-go instead of golang-go.
      + d/rules: add Go 1.20 to $PATH.

 -- Lucas Kanashiro <email address hidden> Thu, 29 Jun 2023 17:39:58 -0300

[Launchpad Janitor (janitor)]

This bug was fixed in the package docker.io - 20.10.21-0ubuntu1~22.04.5

---------------
docker.io (20.10.21-0ubuntu1~22.04.5) jammy; urgency=medium

  * d/tests: remove since docker.io binary package is now provided by
    src:docker.io-app, and the tests were moved to it.

docker.io (20.10.21-0ubuntu1~22.04.4) jammy; urgency=medium

  * Do not provide the docker{.io,-doc} binary packages anymore (LP: #2022390).
    Those binary packages are now provided by src:docker.io-app.
    - d/control: remove docker{.io,-doc} binary package paragraphs.
    - d/docker{.io,-doc}*: remove all files related to the removed binaries.
    - d/rules: remove
      override_dh_{installinit,installsystemd,installudev,install}.

 -- Lucas Kanashiro <email address hidden> Mon, 17 Jul 2023 16:21:21 -0300

[Launchpad Janitor (janitor)]

This bug was fixed in the package docker.io-app - 20.10.25-0ubuntu1~22.04.1

---------------
docker.io-app (20.10.25-0ubuntu1~22.04.1) jammy; urgency=medium

  * Backport version from Mantic to Jammy (LP: #2023694, #2022390)

 -- Lucas Kanashiro <email address hidden> Thu, 29 Jun 2023 18:21:05 -0300

[Launchpad Janitor (janitor)]

This bug was fixed in the package containerd - 1.6.12-0ubuntu3.3

---------------
containerd (1.6.12-0ubuntu3.3) lunar; urgency=medium

  * d/tests: remove since the containerd binary package is now provided by
    src:containerd-app.

containerd (1.6.12-0ubuntu3.2) lunar; urgency=medium

  * Do not provided the containerd binary package anymore (LP: #2022390).
    The containerd binary package is now provided by src:containerd-app.
    - d/control: remove the containerd binary package paragraph.
    - d/containerd.*: remove all files related to the containerd binary
      package.
    - d/docs: remove application documentation.
    - d/rules: remove override_dh_installsystemd.

 -- Lucas Kanashiro <email address hidden> Mon, 17 Jul 2023 16:07:58 -0300

[Launchpad Janitor (janitor)]

This bug was fixed in the package containerd-app - 1.7.2-0ubuntu1~23.04.1

---------------
containerd-app (1.7.2-0ubuntu1~23.04.1) lunar; urgency=medium

  * Backport version from Mantic to Lunar (LP: #2023694, #2022390).

 -- Lucas Kanashiro <email address hidden> Thu, 29 Jun 2023 17:39:58 -0300

[Launchpad Janitor (janitor)]

This bug was fixed in the package docker.io - 20.10.21-0ubuntu3.2

---------------
docker.io (20.10.21-0ubuntu3.2) lunar; urgency=medium

  * d/tests: remove since docker.io binary package is now provided by
    src:docker.io-app, and the tests were moved to it.

docker.io (20.10.21-0ubuntu3.1) lunar; urgency=medium

  * Do not provide the docker{.io,-doc} binary packages anymore (LP: #2022390).
    Those binary packages are now provided by src:docker.io-app.
    - d/control: remove docker{.io,-doc} binary package paragraphs.
    - d/docker{.io,-doc}*: remove all files related to the removed binaries.
    - d/rules: remove
      override_dh_{installinit,installsystemd,installudev,install}.

 -- Lucas Kanashiro <email address hidden> Mon, 17 Jul 2023 16:16:55 -0300

[Launchpad Janitor (janitor)]

This bug was fixed in the package docker.io-app - 20.10.25-0ubuntu1~23.04.1

---------------
docker.io-app (20.10.25-0ubuntu1~23.04.1) lunar; urgency=medium

  * Backport version from Mantic to Lunar (LP: #2023694, #2022390)

 -- Lucas Kanashiro <email address hidden> Thu, 29 Jun 2023 18:21:05 -0300

[Lucas Kanashiro (lucaskanashiro)]

Debdiff containing the runc merge from Debian targeting noble. This depend on src:runc-app already in the NEW queue.

[Sergio Durigan Junior (sergiodj)]

Thanks, Lucas. Here's my review.

I found it a bit strange that we're dropping all d/changelog entries (related to the -0ubuntuX releases), but I guess that's OK...? I mean, I see now that you have done the same thing for containerd and docker.io, and since I reviewed those changes and gave my OK, maybe this is something that we already discussed and I'm just not remembering?

Either way, packaging-wise the changes mostly LGTM, but I have a question about the following d/changelog entry:

+ - d/tests/{checkpoint,integration}: remove since they depend on the
+ runc binary package which is not provided by this source package
+ anymore.

I couldn't find these changes in the debdiff. Maybe you forgot to include them?

[Lucas Kanashiro (lucaskanashiro)]

Thanks for the review Sergio.

As we did with containerd and docker.io, we are dropping the ubuntu related changelog entries. Previously, the package was not merged from debian, from now on it will be merged and the history will be kept.

And you are right, I forgot to delete the tests in the debdiff. I am attaching a new debdiff removing them.

[Sergio Durigan Junior (sergiodj)]

Thanks, Lucas. LGTM, +1.

[Launchpad Janitor (janitor)]

This bug was fixed in the package runc - 1.1.10+ds1-1ubuntu1

---------------
runc (1.1.10+ds1-1ubuntu1) noble; urgency=medium

  * Merge from Debian unstable (LP: #2022390). Make src:runc follow Debian and
    src:runc-app is going to ship the application with vendorized dependencies
    so we can keep updating just the application across all supported releases.
  * Added changes:
    - d/control: remove the binary paragraph for runc.
    - d/runc.*: remove all packaging related files associated to the
      runc binary package
    - d/tests/{checkpoint,integration}: remove since they depend on the
      runc binary package which is not provided by this source package
      anymore.
    - d/golang-github-opencontainers-runc-dev.install: remove this file, it
      is causing a FTBFS, no need to have it in place, the library files are
      already installed correctly without it.
    - d/rules: no need to generate manpages after build.
    - d/rules: remove runc binary from the binary package
    - d/golang-github-opencontainers-runc-dev.docs: install NOTICE file to
      be compliant with the Apache 2 license.

 -- Lucas Kanashiro <email address hidden> Thu, 11 Jan 2024 19:43:18 -0300

[Timo Aaltonen (tjaalton)]

Hello Lucas, or anyone else affected,

Accepted runc into mantic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/runc/1.1.7-0ubuntu2.3 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-mantic to verification-done-mantic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-mantic. 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.

[Timo Aaltonen (tjaalton)]

Hello Lucas, or anyone else affected,

Accepted runc into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/runc/1.1.7-0ubuntu1~22.04.3 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-jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-jammy. 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.

[Timo Aaltonen (tjaalton)]

Hello Lucas, or anyone else affected,

Accepted runc into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/runc/1.1.7-0ubuntu1~20.04.3 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.

[Ubuntu SRU Bot (ubuntu-sru-bot)]

All autopkgtests for the newly accepted runc (1.1.7-0ubuntu2.3) for mantic have finished running.
The following regressions have been reported in tests triggered by the package:

umoci/0.4.7+ds-3ubuntu0.1 (amd64)

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/mantic/update_excuses.html#runc

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

Thank you!

[Steve Langasek (vorlon)]

Hello Lucas, or anyone else affected,

Accepted runc-app into mantic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/runc-app/1.1.12-0ubuntu2~23.10.1 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-mantic to verification-done-mantic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-mantic. 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.

[Steve Langasek (vorlon)]

Hello Lucas, or anyone else affected,

Accepted runc-app into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/runc-app/1.1.12-0ubuntu2~22.04.1 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-jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-jammy. 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.

[Steve Langasek (vorlon)]

Hello Lucas, or anyone else affected,

Accepted runc-app into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/runc-app/1.1.12-0ubuntu2~20.04.1 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.

[Ubuntu SRU Bot (ubuntu-sru-bot)]

All autopkgtests for the newly accepted runc (1.1.7-0ubuntu1~20.04.3) for focal have finished running.
The following regressions have been reported in tests triggered by the package:

runc/1.1.7-0ubuntu1~20.04.3 (ppc64el)

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/focal/update_excuses.html#runc

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

Thank you!

[Ubuntu SRU Bot (ubuntu-sru-bot)]

All autopkgtests for the newly accepted runc (1.1.7-0ubuntu1~22.04.3) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:

runc/1.1.7-0ubuntu1~22.04.3 (ppc64el)

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/jammy/update_excuses.html#runc

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

Thank you!

[Lucas Kanashiro (lucaskanashiro)]

The src:runc regressions above helped me to identify an error in the package. I forgot to remove the basic-smoke test which tries to make use of the runc binary (now provided by src:runc-app). In order to fix this, I uploaded src:runc again to Focal (1.1.7-0ubuntu1~20.04.4), Jammy (1.1.7-0ubuntu1~22.04.4), and Mantic (1.1.7-0ubuntu2.4). Please, accept them from -unapproved.

[Andreas Hasenack (ahasenack)]

Hello Lucas, or anyone else affected,

Accepted runc into mantic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/runc/1.1.7-0ubuntu2.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 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-mantic to verification-done-mantic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-mantic. 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.

[Andreas Hasenack (ahasenack)]

Hello Lucas, or anyone else affected,

Accepted runc into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/runc/1.1.7-0ubuntu1~22.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 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-jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-jammy. 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.

[Andreas Hasenack (ahasenack)]

Hello Lucas, or anyone else affected,

Accepted runc into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/runc/1.1.7-0ubuntu1~20.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 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.

[Ubuntu SRU Bot (ubuntu-sru-bot)]

All autopkgtests for the newly accepted runc (1.1.7-0ubuntu2.3) for mantic have finished running.
The following regressions have been reported in tests triggered by the package:

golang-github-containers-psgo/unknown (armhf)
golang-github-containers-storage/unknown (armhf)
runc/1.1.7-0ubuntu2.3 (arm64, ppc64el, s390x)

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/mantic/update_excuses.html#runc

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

Thank you!

[Ubuntu SRU Bot (ubuntu-sru-bot)]

All autopkgtests for the newly accepted runc (1.1.7-0ubuntu1~22.04.3) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:

runc/1.1.7-0ubuntu1~22.04.3 (arm64, ppc64el, s390x)

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/jammy/update_excuses.html#runc

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

Thank you!

[Ubuntu SRU Bot (ubuntu-sru-bot)]

All autopkgtests for the newly accepted runc (1.1.7-0ubuntu2.4) for mantic have finished running.
The following regressions have been reported in tests triggered by the package:

containerd/unknown (armhf)
golang-github-containers-common/unknown (armhf)
golang-github-containers-psgo/1.7.1+ds1-1 (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/mantic/update_excuses.html#runc

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

Thank you!

[Ubuntu SRU Bot (ubuntu-sru-bot)]

All autopkgtests for the newly accepted runc (1.1.7-0ubuntu1~20.04.4) for focal have finished running.
The following regressions have been reported in tests triggered by the package:

golang-github-containers-psgo/unknown (armhf)
golang-github-containers-storage/unknown (s390x)

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/focal/update_excuses.html#runc

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

Thank you!

[Lucas Kanashiro (lucaskanashiro)]

Now, there is no regressions against runc/1.1.7-0ubuntu2.4 in Mantic and runc/1.1.7-0ubuntu1~20.04.4 in Focal.

[Lucas Kanashiro (lucaskanashiro)]

# Verification - Mantic

## runc-app

autopkgtest [17:32:53]: @@@@@@@@@@@@@@@@@@@@ summary
basic-smoke PASS
command1 PASS

## runc

autopkgtest [17:26:14]: @@@@@@@@@@@@@@@@@@@@ summary
command1 PASS

All the tests above were executed against the versions available in mantic-proposed.

# Verification - Jammy

## runc-app

autopkgtest [18:08:05]: @@@@@@@@@@@@@@@@@@@@ summary
basic-smoke PASS
command1 PASS

## runc

autopkgtest [18:05:50]: @@@@@@@@@@@@@@@@@@@@ summary
command1 PASS

All the tests above were executed against the versions available in jammy-proposed.

# Verification - Focal

## runc-app

autopkgtest [18:36:58]: @@@@@@@@@@@@@@@@@@@@ summary
basic-smoke PASS
command1 PASS

## runc

autopkgtest [18:33:29]: @@@@@@@@@@@@@@@@@@@@ summary
command1 PASS

All the tests above were executed against the versions available in focal-proposed.

[Launchpad Janitor (janitor)]

This bug was fixed in the package runc - 1.1.7-0ubuntu2.4

---------------
runc (1.1.7-0ubuntu2.4) mantic; urgency=medium

  * d/t/control: remove basic-smoke test since it depends on runc binary now
    provided by src:runc-app.

runc (1.1.7-0ubuntu2.3) mantic; urgency=medium

  * Do not provided the runc binary package anymore (LP: #2022390).
    The runc binary package is now provided by src:runc-app.
    - d/control: remove the runc binary package paragraph.
    - d/runc.*: remove all files related to the runc binary package.
    - d/p/test--skip-fs-related-cgroups-tests.patch: skip a new cgroups test
      trying to write to /sys/fs/cgroup/memory.
    - d/golang-github-opencontainers-runc-dev.install: fix path of library
      files.

 -- Lucas Kanashiro <email address hidden> Mon, 06 May 2024 17:12:15 -0300

[Launchpad Janitor (janitor)]

This bug was fixed in the package runc-app - 1.1.12-0ubuntu2~23.10.1

---------------
runc-app (1.1.12-0ubuntu2~23.10.1) mantic; urgency=medium

  * Backport version from Noble to Mantic (LP: #2040460, #2022390).

 -- Lucas Kanashiro <email address hidden> Tue, 12 Mar 2024 17:08:06 -0300

[Launchpad Janitor (janitor)]

This bug was fixed in the package runc - 1.1.7-0ubuntu1~22.04.4

---------------
runc (1.1.7-0ubuntu1~22.04.4) jammy; urgency=medium

  * d/t/control: remove basic-smoke test since it depends on runc binary now
    provided by src:runc-app.

runc (1.1.7-0ubuntu1~22.04.3) jammy; urgency=medium

  * Do not provide the runc binary package anymore (LP: #2022390).
    The runc binary package is now provided by src:runc-app.
    - d/control: remove the containerd binary package paragraph.
    - d/containerd.*: remove all files related to the containerd binary
      package.
    - d/p/test--skip-fs-related-cgroups-tests.patch:
    - d/golang-github-opencontainers-runc-dev.install:

 -- Lucas Kanashiro <email address hidden> Mon, 06 May 2024 16:50:52 -0300

[Launchpad Janitor (janitor)]

This bug was fixed in the package runc-app - 1.1.12-0ubuntu2~22.04.1

---------------
runc-app (1.1.12-0ubuntu2~22.04.1) jammy; urgency=medium

  * Backport version from Noble to Jammy (LP: #2040460, #2022390).
    - d/rules: override dh_dwz to do nothing to avoid build error.

 -- Lucas Kanashiro <email address hidden> Tue, 12 Mar 2024 17:08:06 -0300

[Launchpad Janitor (janitor)]

This bug was fixed in the package runc - 1.1.7-0ubuntu1~20.04.4

---------------
runc (1.1.7-0ubuntu1~20.04.4) focal; urgency=medium

  * d/t/control: remove basic-smoke test since it depends on runc binary now
    provided by src:runc-app.

runc (1.1.7-0ubuntu1~20.04.3) focal; urgency=medium

  * Do not provide the runc binary package anymore (LP: #2022390).
    The runc binary package is now provided by src:runc-app.
    - d/control: remove the containerd binary package paragraph.
    - d/containerd.*: remove all files related to the containerd binary
      package.
    - d/p/test--skip-fs-related-cgroups-tests.patch: skip a new cgroups test
      trying to write to /sys/fs/cgroup/memory.
    - d/golang-github-opencontainers-runc-dev.install: fix path of library
      files.

 -- Lucas Kanashiro <email address hidden> Mon, 06 May 2024 16:53:24 -0300

[Launchpad Janitor (janitor)]

This bug was fixed in the package runc-app - 1.1.12-0ubuntu2~20.04.1

---------------
runc-app (1.1.12-0ubuntu2~20.04.1) focal; urgency=medium

  * Backport version from Noble to Focal (LP: #2040460, #2022390).
    - d/rules: override dh_dwz to do nothing to avoid build error.

 -- Lucas Kanashiro <email address hidden> Tue, 12 Mar 2024 17:08:06 -0300