Affected packages

Packages affected by glibc-headers upgrade from 2.31.9000-9.fc33 to 2.31.9000-10.fc33 (in Fedora rawhide)
Package Current state Build Distance Build time
librepo build 2 2 months ago
samba build 2 2 months ago
wine build 2 2 months ago
libxcrypt build 2 2 months ago
coreutils build 2 2 months ago
dnssec-tools build 3 2 months ago
astrometry build 3 2 months ago
gnutls build 3 2 months ago
dino build 3 2 months ago
grub2 build 3 2 months ago
freeipa build 3 2 months ago
fuse-emulator-utils build 3 2 months ago
zulucrypt build 3 2 months ago
openscap build 3 2 months ago
clufter build 3 2 months ago
brightnessctl build 3 2 months ago
snapper build 3 2 months ago
rubygem-hitimes build 3 2 months ago
borgbackup build 3 2 months ago
kdewebdev build 3 2 months ago
sympy build 3 2 months ago
mpich build 3 2 months ago
sphinx build 3 2 months ago
rust-dbus0.2 build 4 2 months ago
python-theano build 4 2 months ago
dl_poly build 4 2 months ago
poco build 4 2 months ago
udisks2-qt5 build 4 2 months ago
prooftree build 4 2 months ago
neon build 4 2 months ago
ardour5 build 4 2 months ago
opam build 4 2 months ago
collectd build 4 2 months ago
scalasca build 4 2 months ago
kdebase3 build 4 2 months ago
postgis build 4 2 months ago
opencv build 4 2 months ago
sqlite2 build 4 2 months ago
koffice-kivio build 4 2 months ago
golang-gopkg-robfig-cron-3 build None 2 months ago
rust-zincati build None 2 months ago
golang-github-influxdata-cache build None 2 months ago
python-ffc build None 2 months ago
golang-github-hashicorp-memberlist build None 2 months ago
golang-github-mesos build None 2 months ago
golang-x-net build None 2 months ago
eiskaltdcpp build None 2 months ago
golang-github-googlecloudplatform-k8s-cloud-provider build None 2 months ago
golang-k8s-utils build None 2 months ago
golang-k8s-client build None 2 months ago

Disclaimer

This page shows packages in Fedora rawhide which buildability was possibly affected by glibc-headers upgrade from 2.31.9000-9.fc33 to 2.31.9000-10.fc33.
Please keep in mind that there were many other dependency changes happening in parallel that could have caused any particular failure.