Affected packages

Packages affected by coreutils-common upgrade from 8.32-18.fc34 to 8.32-19.fc34 (in Fedora 34)
Package Current state Build Distance Build time
perl-Catalyst-Controller-HTML-FormFu build 2 5 months ago
perl-autovivification build 2 5 months ago
php-guzzlehttp-guzzle6 build 3 5 months ago
python-evic build 3 5 months ago
postgis build 3 5 months ago
openvswitch build 3 5 months ago
dbus build 3 5 months ago
rubygem-redis build 4 5 months ago
python-yarl build 4 5 months ago
ncmpcpp build 4 5 months ago
ocaml-ppx-fields-conv build 4 5 months ago
perl-MooseX-Log-Log4perl build 4 5 months ago
vim-command-t build 4 5 months ago
python-sqlalchemy build 4 5 months ago
perl-Dancer-Session-Cookie build 4 5 months ago
python-pyphi build 4 5 months ago
ocaml-ppx-custom-printf build 4 5 months ago
numpy build 4 5 months ago
ocaml-ppx-optcomp build 4 5 months ago
sympy build 4 5 months ago
mame build 4 5 months ago
gr-osmosdr build 4 5 months ago
geeqie build 4 5 months ago
folks build 4 5 months ago
golang-github-paulbellamy-ratecounter build None 5 months ago
golang-github-lightstep-tracer build None 5 months ago
golang-opencensus build None 5 months ago
rubygem-activestorage build None 5 months ago
rust-r2d2 build None 5 months ago
rust-crossbeam-utils build None 5 months ago
python-furl build None 5 months ago
rust-rand build None 5 months ago
python-iniparse build None 5 months ago
python-seaborn build None 5 months ago
python-animatplot build None 5 months ago
python-hypothesis build None 5 months ago
erlang-riak_kv build None 5 months ago
R-matrixStats build None 5 months ago
R-backports build None 5 months ago
R-fastmatch build None 5 months ago
R-lpSolve build None 5 months ago
R-tmvnsim build None 5 months ago
R-base64enc build None 5 months ago
python-dns build None 5 months ago
utox build None 5 months ago
rust-liquid-core build None 5 months ago

Disclaimer

This page shows packages in Fedora 34 which buildability was possibly affected by coreutils-common upgrade from 8.32-18.fc34 to 8.32-19.fc34.
Please keep in mind that there were many other dependency changes happening in parallel that could have caused any particular failure.