Affected packages

Packages affected by iptables-libs upgrade from 1.8.8-3.fc37 to 1.8.8-4.fc37 (in Fedora 37)
Package Current state Build Distance Build time
criu build 3 2 months ago
golang-opentelemetry-otel-0.20 build None a month ago
golang-github-mholt-certmagic-0.8 build None a month ago
golang-github-prometheus-client build None a month ago
golang-github-zmap-zlint-2 build None a month ago
golang-go4 build None a month ago
golang-k8s-node-api build None a month ago
golang-k8s-csi-api build None a month ago
golang-github-zmap-zlint build None a month ago
golang-storj-common build None a month ago
golang-github-distribution-3 build None a month ago
golang-github-powerman-check build None a month ago
golang-github-influxdata-tdigest build None a month ago
golang-sigs-k8s-controller-runtime build None a month ago
golang-github-acme-lego build None a month ago
golang-sigs-k8s-kustomize build None a month ago
golang-istio-pkg build None a month ago
golang-github-docker-licensing build None a month ago
golang-github-docker-slim build None a month ago
golang-github-quay-clair-3 build None a month ago
hugo build None a month ago
golang-github-acme-lego-3 build None a month ago
golang-github-quay-claircore build None a month ago
golang-x-exp build None a month ago
golang-gocloud build None a month ago
golang-gonum-1-plot build None a month ago
golang-k8s-legacy-cloud-providers build None a month ago
golang-gvisor build None a month ago
golang-github-quay-clair-4 build None 2 months ago
golang-github-hashicorp-memberlist build None 2 months ago
golang-k8s-apimachinery build None 2 months ago
golang-sigs-k8s-application build None 2 months ago
golang-github-cockroachdb-pebble build None 2 months ago
golang-github-prometheus-alertmanager build None 2 months ago
gopass build None 2 months ago
virt-bootstrap build None 2 months ago
diffoscope build None 2 months ago

Disclaimer

This page shows packages in Fedora 37 which buildability was possibly affected by iptables-libs upgrade from 1.8.8-3.fc37 to 1.8.8-4.fc37.
Please keep in mind that there were many other dependency changes happening in parallel that could have caused any particular failure.