Something curious just happened.
kde-frameworks-5 r26 to the stable channel (previously only was in candidate). It adds a new slot
which is used by the application snap
bovo r5 in the candidate channel.
Now, since bovo r5 wants to connect to the new content slot from kde-frameworks-5 r26 my expectation after releasing was that
snap install --candidate bovo would force a refresh of the kde-frameworks-5 snap so it would be able to provide the slot, except snapd didn’t do that.
That leaves me with a broken bovo now. The system still has the old kde-frameworks-5 installed, which doesn’t provide the required slot for the ABI set bovo was built against.
As one would expect explicitly calling
snap refresh will pull in the new kde-frameworks-5 and connect bovo.
Surely snapd should make sure it has the newest version of a content snap upon installing a consumer of the content snap, not only that the content snap is installed.