Red Hat Bugzilla – Bug 564406
kopete-cryptography FTBFS against kdepim-4.4.0
Last modified: 2010-02-15 09:17:37 EST
In short, kopete-cryptography-1.3.0-kde4.4.0 uses libkeo headers that are no longer exported by kdepim.
krop in #kontact suggested : "drop the kopete-cryptography packaging"
Unfortunately, I see no alternative at the moment.
Leave it as is for now (i.e. leave the previous build in), I'll look into this tomorrow.
The offending kdepim commit to revert:
(and we'll need to reenable our kdepim-devel package too).
*** Bug 564980 has been marked as a duplicate of this bug. ***
Actually, this is the 4.4 branch commit I'm reverting:
Fixed in kdepim-4.4.0-4.fc1. kopete-cryptography-1.3.0-16.fc13 built successfully.
thanks for taking care.
Do we have reply from upstream?
Sadly, no really helpful one. :-( There were 2 suggestions:
(a) drop kopete-cryptography packaging entirely. Huh? They won't even support software in extragear anymore?!
(b) copy the libkleo headers into kopete-cryptography. This is just wrong for several reasons:
1. It's not in kopete-cryptography upstream. We'd have to patch it (also hack the CMakeLists.txt, not just add the headers).
2. Bundling the header probably also means bundling the library or we'll be doing the "build against private header, link against public copy" hack which is quite dangerous if they get out of sync.
3. Bundled libraries (or even just parts of libraries, e.g. header files) suck and violate our packaging guidelines.
So both (a) and (b) look like "no go" to me.
IMHO it's unacceptable that kdepim stops exporting an API which is used by an extragear application.