Summary: | dolphin crashes upon right-click if dolphin-plugins not same version | ||
---|---|---|---|
Product: | [Applications] dolphin | Reporter: | kde |
Component: | general | Assignee: | Dolphin Bug Assignee <dolphin-bugs-null> |
Status: | RESOLVED DOWNSTREAM | ||
Severity: | crash | CC: | kfm-devel, panfaust |
Priority: | NOR | ||
Version: | 20.08.2 | ||
Target Milestone: | --- | ||
Platform: | unspecified | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
kde
2020-10-31 19:25:41 UTC
Hi, I'm going to mark this issue as resolved/downstream because this is just an issue with the debian packaging, and that can be fixed for real only in the debian packaging. Why? Let's say KDE releases a newer version KDE Applications, which would provide both newer dolphin and dolphin-plugins. Now, supose the debian "experts" update the new dolphin but not the new dolphin-plugins in sid, or that they package it improperly in a way that the newer version of dolphin migrates from sid to testing, while testing still has the older dolphin-plugins (which is exactly what they did). Can this packaging situation be fixed in the dolphin-plugins CMakeLists.txt for example? Well, the way I see it, no, because there isn't any way to prevent a distribution from providing a new version of dolphin along with an old version of dolphin plugins. Even if we set a minimum version for DolphinVcs here: https://invent.kde.org/sdk/dolphin-plugins/-/blob/master/CMakeLists.txt like I said above, that's not going to stop a distribution from providing a modern dolphin along with an old dolphin-plugins, which is what caused your problem. P.S. With all due respect: I have been doing *.deb kde packaging over the last 10 years, and maybe the debian "experts" should automate their packaging (like we did in other distributions such as Kubuntu or KDE Neon) and take better care of sid -> testing migrations so they don't end up having this random outdated mix of packages. |