Affected packages

Packages affected by boost-numpy3 upgrade from 1.83.0-0.fc40 to 1.83.0-2.fc40 (in Fedora 40)
Package Current state Build Distance Build time
galera build 2 2 months ago
botan build 2 2 months ago
CuraEngine build 2 2 months ago
asio build 2 2 months ago
apt-cacher-ng build 2 2 months ago
metslib build 2 2 months ago
wdt build 2 2 months ago
libfreehand build 2 2 months ago
hpx build 2 2 months ago
glob2 build 2 2 months ago
libftdi build 2 2 months ago
espresso build 2 2 months ago
vdrift build 2 2 months ago
flowcanvas build 2 2 months ago
pdns-recursor build 2 2 months ago
smoldyn build 2 2 months ago
blender build 2 2 months ago
python-mapnik build 2 2 months ago
python-pynn build 2 2 months ago
radiotray-ng build 2 2 months ago
xmlcopyeditor build 2 2 months ago
nest build 2 2 months ago
filezilla build 2 2 months ago
libzypp build 2 2 months ago
uwsgi build 2 2 months ago
openclonk build 2 2 months ago
deepin-file-manager build 2 2 months ago
abiword build 2 2 months ago
syncevolution build 2 2 months ago
paraview build 2 2 months ago
opentoonz build 2 2 months ago
vtk build 2 2 months ago
trademgen build 2 2 months ago
gecode build 2 2 months ago
simspark build 2 2 months ago
torque build 2 2 months ago
openms build 2 2 months ago
Singular build 2 2 months ago
asymptote build 2 2 months ago
digikam build 2 2 months ago
Macaulay2 build 2 2 months ago
player build 2 2 months ago
mcrouter build 3 2 months ago
mp build 3 2 months ago
wdune build 3 2 months ago
vakzination build 3 2 months ago
proxygen build 3 2 months ago
InsightToolkit build 3 2 months ago
kf5-akonadi-mime build 3 2 months ago
kf5-kmailtransport build 3 2 months ago
opencascade build 3 2 months ago
darktable build 3 2 months ago
gdal build 3 2 months ago
netgen-mesher build 4 2 months ago
gimp build 4 2 months ago
petpvc build None 2 months ago
alizams build None 2 months ago

Disclaimer

This page shows packages in Fedora 40 which buildability was possibly affected by boost-numpy3 upgrade from 1.83.0-0.fc40 to 1.83.0-2.fc40.
Please keep in mind that there were many other dependency changes happening in parallel that could have caused any particular failure.