These are outdated packages that needed to recompile against the latest libffi
To accomplish these I used these command
# tazpkg recharge
# cat /var/lib/tazpkg/packages.info | grep "libffi" | awk '{ print $1 }' | grep -v "libffi"
Then compare the date modified of the package in the repo against the date modified of libffi package in the repo
Here are the outdated packages found that depend on libffi that needed to recompile:
cairo-gl
glibmm
gobject-introspection
gtk-sharp
gtkdialog
gvolwheel
harbuzz
iron-linux
libgiomm
liboobs
linux64-open-vm-tools-kernel
llvm
lximage-qt
lxqt-admin
lxqt-policykit
micropython
mirage
obconf-qt
obmenu
open-vm-tools
open-vm-tools-kernel
oxygen-gtk
pangox-compat
pcmanfm-qt
pnmixer
pyroom
python
qjackctl
sbxkb
sylpheed (not sylpheed-full)
system-tools-backends
urxvt-full
viewnior
wayland
yad-gtk2
yad-gtk2-html
yad-gtk3
Almost 37 packages needed to rebuild due to changes in libffi version. It is very alarming that slitaz maintainers are failed to track what packages are needed to recompile if a new version of a package in the database was cooked.
They baldy need to automate the rebuilding of packages which depends on it if a new version of package in the database was introduced (For example if new version of libffi was cooked, all packages in the repo depends on libffi will be recompiled and uploaded to repo). So that the packages in the repo which will be downloaded by the end-users will not broke their system. Also the automated build process of slitaz rolling live-cd will not produce a broken one.
Adding a feature to rebuild the packages after compiling a new package on cookutils and the cooker is highly recommended