Control: severity -1 important Hi Martin,
On Wed, Jul 29, 2020 at 8:42 AM Martin Pitt <mp...@debian.org> wrote: > Package: podman > Version: 2.0.3+dfsg1-1 > Severity: serious > Tags: upsteam fixed-upstream > > Version 2.0.3 breaks the REST API really hard, which breaks cockpit-podman > and > any other API user. This is tracked here: > > https://github.com/containers/podman/issues/7078 > > This has been fixed upstream and will be in 2.0.4. I'd like to block this > version from testing to avoid the regression. > > If you disagree and would rather get this in ASAP (given how young the > package > is still), I'm fine with that as well, and disable the cockpit-podman test > on > debian-testing for a while. > > Thank you for your bugreport. I looked into backporting the change and checked in with my contact upstream. It turns out that this is not the only issue with the REST interface, and neither of them are easy to backport to 2.0.3. A new release will come out soon that should be suitable for cockpit-podman. Cockpit looks like a really cool project. I do need to find some time to play with it, in particular with the upcoming cockpit-podman component. Thanks for packaging it! Are you working full time on "cockpit"? Given that the REST interface is not available in testing (the respective systemd units were only introduced in 2.0.3+dfsg1-1), and podman provides a lot of value even without them, I'd rather have the current package migrate to testing at this point. Having said this, I do really appreciate your bug report and will see to a remedy as soon as it becomes available in the form of a new upstream release. For the time being, I'd recommend disabling the cockpit-podman test for the time being and re-enable it when this bug gets closed properly. Thanks for your understanding. -- regards, Reinhard
