is volunteering to help with this migration. That's really much
appreciated.
As far as I can tell, I've managed to execute this transition in "experimental"
the containerd migration.
It is possible that I missed packages, so I'd appreciate some double-checking
of my work.
That sounds very goal oriented if we agreed on the goal being
"get podman 5 into testing asap". This is clearly one of my goals.
The approach that you describe above comes with risk:
- Does uploading packages that start this transition cause unpleasant surprises?
- Does this break packages that we miss to testbuild?
- Does this slow down other, unrelated ongoing transitions?
- Does this require major upstream version updates to other packages (and if so, are the maintainers of affected packages available to quickly react and help with restoring those packages)?
- Do we need to temporarily remove other packages to ease this migration?
I personally believe the benefits of achieving the goal outweighs the risk. I
do hope the Debian release team agrees and is comfortable with me starting the
migration by uploading packages that are currently in experimental to unstable,
and are able to advise and help with hints to britney to minimize the disruption.
My pitch would be to start with sourceful uploads of (and in that order):
- golang-google-genproto
- golang-google-grpc
- golang-github-grpc-ecosystem-grpc-gateway.v2
- golang-github-google-cel-go
- golang-opentelemetry-otel
- golang-github-googleapis-gnostic
- etcd
- golang-gogottrpc
- golang-github-containerd-btrfs
- golang-github-containerd-go-cni
- golang-github-containerd-go-runc
- golang-github-coreos-bbolt
- golang-github-google-certificate-transparency
- golang-github-lightstep-lightstep-tracer-common
- golang-github-kurin-blazer
- golang-google-cloud
- golang-github-containerd-cgroups
- golang-github-containerd-typeurl
- containerd
- golang-github-cloudflare-cfssl
- rootlesskit
-
docker.io- golang-github-fsouza-go-dockerclient
- golang-github-openshift-imagebuilder
- golang-github-containers-storage
- golang-github-containers-image
- golang-github-containers-common
- golang-github-containers-buildah
- libpod
Yes, that is a long list. I think we can do it, but I'm also
interested in minimizing surprises, smooth transitions, and would like to mititgate
the risks mentioned above with coordination and thinking this through.
Thanks so much for your assistance!