Affected packages

Packages affected by libuuid upgrade from 2.36-2.fc33 to 2.36.1-1.fc33 (in Fedora 33)
Package Current state Build Distance Build time
deepin-system-monitor build 2 3 months ago
libvirt build 2 3 months ago
owncloud-client build 2 3 months ago
rubygem-aruba build 3 2 months ago
python-niapy build 3 2 months ago
python-pyfastnoisesimd build 3 2 months ago
dmlite build 3 3 months ago
ocrmypdf build 3 3 months ago
python-trimesh build 3 3 months ago
python-geopandas build 3 3 months ago
libftdi build 3 3 months ago
python-numpoly build 3 3 months ago
python-pyinsane2 build 3 3 months ago
python-pynetdicom build 3 3 months ago
syncthing build 3 3 months ago
cyrus-imapd build 3 3 months ago
galera build 3 3 months ago
python2.7 build 4 3 months ago
lazarus build 4 3 months ago
oci-seccomp-bpf-hook build 4 3 months ago
scalacheck build 4 3 months ago
python-chaospy build 4 3 months ago
R-R.devices build 4 3 months ago
gap-pkg-hap build 4 3 months ago
lv2-ir-plugins build 4 3 months ago
pam_abl build 4 4 months ago
golang-github-streadway-amqp build None 2 months ago
chaos-client build None 2 months ago
golang-github-projectdiscovery-mapcidr build None 2 months ago
crlfuzz build None 2 months ago
dnsprobe build None 2 months ago
rubygem-eventmachine build None 2 months ago
perl-IO-Async build None 2 months ago
rubygem-thin build None 2 months ago
perl-Inline-C build None 2 months ago
perl-Hardware-Vhdl-Tidy build None 2 months ago
gap-pkg-guava build None 3 months ago
erlang-riak_core build None 3 months ago
erlang-riak_kv build None 3 months ago
golang-github-lucas-clemente-quic build None 3 months ago
licensecheck build None 3 months ago
golang-github-docker-distribution build None 3 months ago
golang-github-prometheus build None 3 months ago
golang-k8s-kubernetes build None 3 months ago
rust-desed build None 4 months ago
rust-copydeps build None 4 months ago

Disclaimer

This page shows packages in Fedora 33 which buildability was possibly affected by libuuid upgrade from 2.36-2.fc33 to 2.36.1-1.fc33.
Please keep in mind that there were many other dependency changes happening in parallel that could have caused any particular failure.