dev-libs/libical-3.0.13 has this text in release notes: Note that the libical-glib library is considered unstable; therefore not binary compatible with previous releases I guess upgrading libical from 3.0.12 to 3.0.14 should trigger a rebuild of dependent apps.
evolution-data-server-3.42.4.ebuild has: RDEPEND=" >=app-crypt/gcr-3.4 >=app-crypt/libsecret-0.5[crypt] >=dev-db/sqlite-3.7.17:= >=dev-libs/glib-2.70:2 >=dev-libs/libical-3.0.8:=[glib,introspection?] .... but a rebuild of evolution-data-server was not triggered by new libical. Odd ...
(In reply to Joakim Tjernlund from comment #1) > > but a rebuild of evolution-data-server was not triggered by new libical. > Odd ... Because the subslot needs to be cranked, right?
Was there any problem?
(In reply to Andreas Sturmlechner from comment #3) > Was there any problem? Didn't get that far. I saw the notice before running Evo so I rebuilt first.
This was part of every release notes so far since it was added. I don't see any relevant change in the last few releases so I am reluctant to bump subslot without any issues reported.