Indeed, containerd appears to have an SRU special exception granted by tech board:
https://wiki.ubuntu.com/StableReleaseUpdates#Docker.io_group """ Docker.io group The source packages docker.io, containerd, and runc may be uploaded according to the procedure documented in DockerUpdates. Per Technical Board discussion regarding delegation of these decisions to the SRU team, this stable release exception has been approved by BrianMurray for the SRU team as of 2016-09-20. """ The approved update policy that applies for this case is: https://wiki.ubuntu.com/DockerUpdates >From this, Andreas is correct that 1.3.1 needs to be landed in devel first (perhaps it needs the block-proposed tag removed?) and complete migration, before 1.3.1 is uploaded for SRU to bionic. ** Changed in: containerd (Ubuntu) Status: New => Triaged ** Changed in: containerd (Ubuntu Bionic) Status: New => Triaged ** Changed in: containerd (Ubuntu Disco) Status: New => Triaged ** Changed in: containerd (Ubuntu Eoan) Status: New => Triaged ** Changed in: containerd (Ubuntu) Importance: Undecided => High ** Changed in: containerd (Ubuntu Bionic) Importance: Undecided => High ** Changed in: containerd (Ubuntu Disco) Importance: Undecided => High ** Changed in: containerd (Ubuntu Eoan) Importance: Undecided => High ** Tags added: server-next ** Summary changed: - Update to containerd 1.3.1 + [SRU] Update to containerd 1.3.1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1854841 Title: [SRU] Update to containerd 1.3.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/containerd/+bug/1854841/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
