#10365 untag ca-certificates-2021.2.50-4.fc36 from f36-build
Closed: Fixed by mtasaka. Opened by mtasaka.

Recently built ca-certificates-2021.2.50-4.fc36 broke f36 buildroot:
https://koji.fedoraproject.org/koji/taskinfo?taskID=78188038

Error: 
 Problem 1: package python3-dnf-4.10.0-1.fc36.noarch requires python3-rpm >= 4.14.0, but none of the providers can be installed
  - package python3-rpm-4.17.0-1.fc36.1.i686 requires libcrypto.so.3, but none of the providers can be installed
  - package dnf-4.10.0-1.fc36.noarch requires python3-dnf = 4.10.0-1.fc36, but none of the providers can be installed
  - package openssl-libs-1:3.0.0-1.fc36.i686 requires ca-certificates >= 2008-5, but none of the providers can be installed
  - conflicting requests
  - nothing provides p11-kit >= 0.24 needed by ca-certificates-2021.2.50-4.fc36.noarch
  - nothing provides p11-kit-trust >= 0.24 needed by ca-certificates-2021.2.50-4.fc36.noarch
 Problem 2: package python3-hawkey-0.65.0-1.fc36.i686 requires libpython3.10.so.1.0, but none of the providers can be installed
  - package python3-dnf-plugins-core-4.0.24-1.fc36.noarch requires python3-hawkey >= 0.46.1, but none of the providers can be installed
  - package python3-libs-3.10.0-2.fc36.i686 requires python-pip-wheel, but none of the providers can be installed
  - package dnf-plugins-core-4.0.24-1.fc36.noarch requires python3-dnf-plugins-core = 4.0.24-1.fc36, but none of the providers can be installed
  - package python-pip-wheel-21.3.1-1.fc36.noarch requires ca-certificates, but none of the providers can be installed
  - conflicting requests
  - nothing provides p11-kit >= 0.24 needed by ca-certificates-2021.2.50-4.fc36.noarch
  - nothing provides p11-kit-trust >= 0.24 needed by ca-certificates-2021.2.50-4.fc36.noarch

Please untag this build, thank you.
Relevant change: https://src.fedoraproject.org/rpms/ca-certificates/c/40ecfc5f64c5216dff3206c02086effbe9bc2944?branch=rawhide


Just hit this as well.

CC: @rrelyea

Would someone take care of this?

@mtasaka untagged

Looks good, thank you!

Metadata Update from @mtasaka:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

Metadata