On Tue, 9 Jan 2018, Dominique Leuenberger / DimStar wrote:
On Tue, 2018-01-09 at 08:41 +0000, Rainer Klier wrote:
Am Dienstag, den 09.01.2018, 09:28 +0100 schrieb Dominique Leuenberger / DimStar:
On Tue, 2018-01-09 at 08:15 +0000, Rainer Klier wrote:
no, both are from TW repo. it would be interesting, what happens to evolution for a user, who cleanly and correctly always did a "zypper dup".... does it also crash?
Highly doubtful, since there is an openQA test of a duped machine - and I am sure many more would have jumped on the wagon here and shouted 'me too'
hmm, yes, that seems obvious.
Anyway, to hopefully get this to an end: what you very likely forgot to update at the same time as libwebkitgtk-4_0-37 was webkit2gtk-4_0- injected-bundles (note: this is an assumption/guess only)
thanks, but this didn't solve it.
i updated the injected-bundles package also, but it didn't solve it.
i now also added the GNOME:Factory repo (juhuuu, another repo to my list.. ;-) to get evolution AND all *webkit* packages from there, and was able to install everything from there. but this also didn't solve this issue.
Urgh - so in order to fix an already polluted system you pollute it more... as the maintainer of GNOME:Factory, I can only say: there should be really no reason at all to add G:F to any machine that is not doing actual devel work on the GNOME packages. Upgrades from G:F moved to TW at a high enough pace - once things are tested on the developers machines. But of course, you are 'free' to do as you wish.
The real issue is of course false binary compatibility promises made
via not changing the SONAME or using symbol versioning...
Of course it's quite hard to do right, especially with C++, but still
I'd expect "core" libraries to do better here...
Richard.
--
Richard Biener