Bug 381829 - kdevplatform rpm dependency missing
Summary: kdevplatform rpm dependency missing
Status: RESOLVED NOT A BUG
Alias: None
Product: kdevelop
Classification: Applications
Component: general (show other bugs)
Version: 5.1.1
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: kdevelop-bugs-null
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-06-30 14:16 UTC by Elmer Joandi
Modified: 2017-07-03 19:25 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
crash dump (11.11 KB, text/plain)
2017-07-03 18:58 UTC, Elmer Joandi
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Elmer Joandi 2017-06-30 14:16:29 UTC
Fedora 23-25 - kdevelop needs proper rpm versioning dependency to kdevplatform, as nothing works (parser, make, crashes, etc) without upgrading those two packages simultaneously.
Comment 1 Milian Wolff 2017-07-01 13:19:06 UTC
please report this to your packagers, we don't supply RPMs of kdevelop
Comment 2 Elmer Joandi 2017-07-02 07:21:44 UTC
humm, and from where packagers should know version dependency between kdevelop and kdevplatorm. Is it between major or minor versions. Still it did cost me several hours to understand which package at which version is causing the problem. And unless something at package source provides the versioning dependency data, packagers will never get it right.

I.e. if dependent package really requires a same version of dependable, then it should refuse compile otherwise.
Comment 3 Sven Brauch 2017-07-02 10:09:05 UTC
It does refuse to compile if the versions don't match.
Comment 4 Elmer Joandi 2017-07-03 09:17:24 UTC
well it would be nice then to have that version check and warning at startup, that such a situation causes major unpredicted instability.
Comment 5 Sven Brauch 2017-07-03 16:42:53 UTC
I don't even get how you manage to get it to start up / load anything with those two not at the same version. We have SOVERSION info on the shared libs and we have versioned plugins. Have a trace / description of what actually happens?

Either way, this is first and foremost a packaging problem and it must be fixed on the packaging side.
Comment 6 Elmer Joandi 2017-07-03 16:47:46 UTC
yum --releasever=25 upgrade kdevelop
yum --releasever=23 downgrade kdevelop
yum --releasever=24 upgrade kdevelop

so it happens, usually Fedora packages keep their versioning dependencies good on those tricks.
Comment 7 Sven Brauch 2017-07-03 17:51:16 UTC
Yes but then what? What versions of what files are on the system and what happenw when you start kdevelop?
Comment 8 Elmer Joandi 2017-07-03 18:42:25 UTC
I think that one point even the library was 4.x and kdevelop 5.x.
But also different 5.x

result was that background parser got stuck and on compile it crashed and Qt project was not opened (custom dev make manager)
(additionally, it crashes without 3D acceleration, which is a bit nuisance for me). So I deleted sessions and messed with other config files...

Searching net for clues, I came up suggestion to have library version same as kdevelop and that solved the problem - seems that other people have had the same long trouble.
Comment 9 Sven Brauch 2017-07-03 18:55:45 UTC
What I would like to see would be an actual file listing and an actual error message / trace of what happens.
Comment 10 Elmer Joandi 2017-07-03 18:58:46 UTC
Created attachment 106434 [details]
crash dump
Comment 11 Sven Brauch 2017-07-03 19:25:28 UTC
That is definitely KDevelop 4 crashing. For 5, all the plugins are installed into a versioned subdirectory ...