[testing-devel] overrides: fast-track podman-2.0.6-1.fc32, ostree-2020.6-2.fc32

[dustymabe]

This fast-tracks the new podman and ostree releases.

commit 19fad0b2c9690c7443671c6286031c2c22ec2fe9
Author: Dusty Mabe <dusty@dustymabe.com>
Date:   Thu Sep 3 16:19:34 2020 -0400

    overrides: fast-track ostree-2020.6-2.fc32
    
    https://bodhi.fedoraproject.org/updates/FEDORA-2020-eb29bce63d
    
    This includes a fix for:
    https://github.com/coreos/fedora-coreos-tracker/issues/617

commit 77744d50f2e2811c136a385a3e419fe329f380ca
Author: Dusty Mabe <dusty@dustymabe.com>
Date:   Thu Sep 3 16:03:59 2020 -0400

    overrides: fast-track podman-2.0.6-1.fc32
    
    https://bodhi.fedoraproject.org/updates/FEDORA-2020-0c1986cdf7
    
    See also:
    https://github.com/coreos/fedora-coreos-tracker/issues/575

[dustymabe]

podman 2.0.6 is currently rolled out to next and seems to be going fine. Let's get it into testing-devel. If an issue crops up we can revert before next week's testing release.

[cgwalters]

Hmm this doesn't seem to be working locally for me, I'm still getting

  ostree-2020.4-2.fc32.x86_64 (fedora-coreos-pool)
  ostree-libs-2020.4-2.fc32.x86_64 (fedora-coreos-pool)

[cgwalters]

Do we have to wait for the pool to regenerate or something?

[cgwalters]

Nevermind, some sort of local rpm-md caching issue it seems; a cosa clean fixed it. But there also is seemingly a bug here in that even with --strict we're letting the depsolver find the old version. Might be something else to use coreos/rpm-ostree#2125 for the lockfiles too.