Rebuild Todo List cargo-c SOVER rebuild
The latest version of cargo-c has changed how the SOVER is derived from a library's Cargo.toml.
In case of `0.6.1` it used to generate `.so.0` but does now generate `.so.0.6`. Before this, a dynamic linker could not tell `0.6.0` and `0.7.0` apart.
When updating cargo-c, this means a rebuild of a cargo-c dependee is going to be a sover bump, and the packages depending on it need to be rebuilt as well.
Since this is counter-intuitive for rebuilds with no pkgver= changes/identical source code, we could consider uploading cargo-c to extra-staging and then rebuild all relevant cargo-c dependees and their dependees.
Packages that are unaffected (that don't contain a `.so.0` file, because they are >= 1.0.0) are not included in this todo.
Filter Todo List Packages
|Arch||Repository||Name||Current Version||Staging Version||Maintainers||Status||Last Touched By|