Affected packages

Packages affected by python3-pyparsing upgrade from 2.4.0-1.fc31 to 2.4.0-5.fc32 (in Fedora rawhide)
Package Current state Build Distance Build time
python-Pympler build 2 3 months ago
perl build 2 3 months ago
python35 build 2 3 months ago
postgresql build 2 3 months ago
python-libpysal build 2 3 months ago
python-astropy-healpix build 2 4 months ago
pcp build 2 4 months ago
python-mplcursors build 2 4 months ago
python-xarray build 2 4 months ago
python-junit_xml build 3 3 months ago
python-marshmallow-enum build 3 3 months ago
python-joblib build 3 3 months ago
python-epub build 3 3 months ago
python-structlog build 3 3 months ago
python-pyqtgraph build 3 3 months ago
xonsh build 3 3 months ago
pybind11 build 3 3 months ago
GraphicsMagick build 3 3 months ago
ImageMagick build 3 3 months ago
mod_perl build 3 3 months ago
python-vulture build 3 3 months ago
python-pygments build 3 3 months ago
python-behave build 3 3 months ago
pyOpenSSL build 3 3 months ago
znc build 3 3 months ago
vim build 3 3 months ago
clang build 3 3 months ago
python-envisage build 3 3 months ago
rrdtool build 3 3 months ago
opensips build 3 3 months ago
claws-mail build 3 3 months ago
graphviz build 3 3 months ago
python-pillow build 3 3 months ago
gdal build 3 3 months ago
subversion build 3 3 months ago
python-wxpython4 build 3 3 months ago
kvirc build 3 3 months ago
coq build 3 3 months ago
swig build 3 3 months ago
paraview build 3 3 months ago
python-arpeggio build 3 4 months ago
python-pycountry build 3 4 months ago
python-pycdlib build 3 4 months ago
pylint build 3 4 months ago
python-priority build 3 4 months ago
python-lz4 build 3 4 months ago
perl-Time-Warp build 3 4 months ago
borgbackup build 3 4 months ago
lsp-plugins build 3 4 months ago
pythran build 3 4 months ago
mod_perl build 3 4 months ago
coq build 3 4 months ago
asterisk build 4 a month ago

Disclaimer

This page shows packages in Fedora rawhide which buildability was possibly affected by python3-pyparsing upgrade from 2.4.0-1.fc31 to 2.4.0-5.fc32.
Please keep in mind that there were many other dependency changes happening in parallel that could have caused any particular failure.