Affected packages

Packages affected by systemd upgrade from 250.7-1.fc36 to 250.8-1.fc36 (in Fedora 36)
Package Current state Build Distance Build time
trytond build 1 2 months ago
libnitrokey build 1 2 months ago
fedmsg build 1 2 months ago
casync build 1 2 months ago
cjdns build 1 2 months ago
graphlcd-base build 1 2 months ago
prelude-lml build 1 2 months ago
zfs-fuse build 1 2 months ago
accountsservice build 1 2 months ago
amanda build 1 2 months ago
prelude-manager build 1 2 months ago
android-tools build 1 2 months ago
transmission build 1 2 months ago
libftdi build 1 2 months ago
lua-ldap build 2 2 months ago
module-build build 2 2 months ago
python-django-auth-ldap build 2 2 months ago
python3.6 build 2 2 months ago
0ad build 2 2 months ago
rubygem-selenium-webdriver build 3 2 months ago
kid3 build 3 2 months ago
elementary-music build 3 2 months ago
qt5-qtwebengine build 3 2 months ago
python-psycopg2 build 3 2 months ago
tinygo build 3 2 months ago
qt-creator build 3 2 months ago
fedpkg build 3 2 months ago
mate-user-admin build 3 2 months ago
dolphin-emu build 3 2 months ago
apr-util build 4 2 months ago
gnustep-base build 4 2 months ago
cone build 4 2 months ago
mingw-wine-gecko build 4 2 months ago
entangle build 4 2 months ago
libgda build 4 2 months ago
denemo build 4 2 months ago
shotwell build 4 2 months ago
owncloud-client build 4 2 months ago
gnome-2048 build 4 2 months ago
wingpanel build 4 2 months ago
koffice-kivio build 4 2 months ago
heaptrack build 4 2 months ago
guitarix build 4 2 months ago
ocrmypdf build None a month ago
nvml build None 2 months ago
kguitar build None 2 months ago
arbor build None 2 months ago
libqtxdg build None 2 months ago
deepin-kwin build None 2 months ago
libfm-qt build None 2 months ago
kmplayer build None 2 months ago
vagrant-libvirt build None 2 months ago
lammps build None 2 months ago
gazebo build None 2 months ago

Disclaimer

This page shows packages in Fedora 36 which buildability was possibly affected by systemd upgrade from 250.7-1.fc36 to 250.8-1.fc36.
Please keep in mind that there were many other dependency changes happening in parallel that could have caused any particular failure.