Affected packages

Packages affected by gdbm-libs upgrade from 1:1.18.1-5.fc33 to 1:1.19-1.fc33 (in Fedora 33)
Package Current state Build Distance Build time
rubygem-aruba build 2 3 months ago
rubygem-eventmachine build 2 3 months ago
rubygem-thin build 2 3 months ago
ruby build 2 4 months ago
python-pyfastnoisesimd 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
community-mysql build 3 3 months ago
python-networkx build 3 4 months ago
fail2ban build 3 4 months ago
scalacheck build 4 3 months ago
python-chaospy build 4 3 months ago
gap-pkg-hap build 4 3 months ago
lv2-ir-plugins build 4 3 months ago
deepin-system-monitor build 4 3 months ago
galera build 4 3 months ago
sayonara build 4 3 months ago
perl-Inline-C build None 3 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
R-R.devices build None 3 months ago
octave-image build None 3 months ago

Disclaimer

This page shows packages in Fedora 33 which buildability was possibly affected by gdbm-libs upgrade from 1:1.18.1-5.fc33 to 1:1.19-1.fc33.
Please keep in mind that there were many other dependency changes happening in parallel that could have caused any particular failure.