I do not like the semantic-desktop features, so that I've tried to switch off the use flag, but ... see the attached log Reproducible: Always Steps to Reproduce: 1. (install kde-crazy, unmask, add @kde to world_sets) 2. USE="-semantic-desktop" emerge -uDN world
Created attachment 174147 [details] build.log
as I am unable to assign this bug as a blocker to kde-crazy tracker bug please reporter or assigner to add this bug as a blocker of #249853 bug. thx in advance
btw, I've spoken with one of the Fedora KDE maintainers, and from what he says it is a upstream problem ... however, if a proper patch is not available, Gentoo should workaround this (e.g. disabling the possibility to switch off Nepomuk in kdelibs), so I am not closing this as "upstream"
Well we are updating snapshots weekly. Thus patching such thing has no perspecitve and it is better to force upstream to fix this. Snapshots are intended to help them catch all bugs. This is one of them. So please report this upstream and close as fixed when they fix it by themselves. I know we can workaround this by enabling nepomuk by default but as i said just for one release it is pointless.
the point was that it might not get fixed in 4.2 final, as there is not too much pressure, and in that case it should be caught at the distribution level, so this report might serve as tracker so I'll reopen if such case comes (and I catch it) btw, I thought that it is a good practice that the maintainers of the packages report such upstream bugs as they should be able to rule out the distribution buildsystem failure, unlike the ordinary lame users (as I am) who do not understand how the things work, and a reference to the upstream bug tracker is given before the distribution specific bugreport is closed ...
> btw, I thought that it is a good practice that the maintainers of the packages > report such upstream bugs as they should be able to rule out the distribution > buildsystem failure, unlike the ordinary lame users (as I am) who do not > understand how the things work, and a reference to the upstream bug tracker is > given before the distribution specific bugreport is closed ... > Yes yes we gladly use our users to do it for us :P And adding some detection ifdefs will be much better than forcing nepomuk by default. And this is bug not some missing feature so it should get fixed. :] And I already found out that it is really bug in there, so it is not buildsystem error :] And jfyi this bug is not closed, it is marked upstream. :]
https://bugs.kde.org/show_bug.cgi?id=176984
(In reply to comment #6) > And jfyi this bug is not closed, it is marked upstream. :] well, I have an option to "Reopen bug" just below the "Additional Comments" textarea ... how can I (re)open something that is not closed? (on the other hand, there is also option to "Mark bug as CLOSED", oh well ...)
(In reply to comment #8) > (In reply to comment #6) > > And jfyi this bug is not closed, it is marked upstream. :] > > well, I have an option to "Reopen bug" just below the "Additional Comments" > textarea ... how can I (re)open something that is not closed? > > (on the other hand, there is also option to "Mark bug as CLOSED", oh well ...) > Nah bugzilla is magic somethimes, important is how we interpret the thing :]
