Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 612336 - kde-apps/pykde4-4.14.3-r3 do not remove kio module
Summary: kde-apps/pykde4-4.14.3-r3 do not remove kio module
Status: RESOLVED WONTFIX
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal
Assignee: Gentoo KDE team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-03-11 19:40 UTC by Alex Turbov
Modified: 2017-03-18 09:01 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments
Do not exclude KIO from PyKDE4, just disable KAutoMount/KAutoUnmount classes which cause a build error of PyKDE4.kio (pykde4-4.14.3-avoid-kio-kautomount-private-dtor.patch,1.31 KB, patch)
2017-03-11 19:42 UTC, Alex Turbov
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Alex Turbov 2017-03-11 19:40:07 UTC
Recent changes to pykde4 (the pykde4-4.14.3-nokio.patch) break the Pate plugin in kate:4 -- it needs PyKDE4.kio!

Digging a little into the problem I've found that KAutoMount and KAutoUnmount classes in the current `kde-frameworks/kdelibs-4.14.29-r1` have private destructor and `sip` gives an compile error when `pykde4` builds... (I think that was a reson for applying pykde4-4.14.3-nokio.patch on -r3 of ebuild).

I've found another workaround: do not exclude KIO module from pykde4, just disable guilty classes... (going to attach a patch).



Reproducible: Always
Comment 1 Alex Turbov 2017-03-11 19:42:14 UTC
Created attachment 466720 [details, diff]
Do not exclude KIO from PyKDE4, just disable KAutoMount/KAutoUnmount classes which cause a build error of PyKDE4.kio

Replace `pykde4-4.14.3-nokio.patch` in `pykde4-4.14.3-r3.ebuild` with this patch!!!
Comment 2 Andreas Sturmlechner gentoo-dev 2017-03-18 09:01:12 UTC
If you find an in-tree package that would be affected by the kio module removal, then I would do another revbump. But as things are, perpetually broken pykde4 will be kicked from tree on the first possible occasion, and I'm not going to spend more time on it.

So if you decide to keep pykde4 longer-term, you should create a local copy with your patch, as you did with kate:4 already.