Summary: | Emerging qtella-0.6.4 and qtella-0.7.0 fails without kde | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | M. Creidieki Crouch <creidieki+gentoobugs> |
Component: | Current packages | Assignee: | Gentoo net-p2p team <net-p2p> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | j, kde |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | config.log after qtella-0.7.0 fails |
Description
M. Creidieki Crouch
2004-06-26 16:19:05 UTC
After this failed merge, could you please post the contents of config.log: /var/tmp/portage/qtella-0.7.0/work/qtella-0.7.0/config.log we need to find out why it's trying to drag in functions provided by kdelibs, even if the user specifically does not want them. (Adding kde team to cc as they may have more insight on this- feel free to take this bug as you'll probably have more experience in it than I) btw., Jon: "use foo && inherit bar" isn't allowed, because conditional dependencies break portage cache. Doesn't produce "use foo&& need-* || need-*" the same problem?! Created attachment 34445 [details]
config.log after qtella-0.7.0 fails
I also noticed that qtella seems to be installing kde-base/kde-env-3 when it installs qtella; I don't know if that's normal. hmm, you do have --with-kde=no in there, which is what I wanted to make sure of. kde-env-3 is required by the 'inherit kde' at the top of this ebuild. Any ideas, kde team? I really don't like having to make packages DEPEND on kdelibs. From looking at the source this seems to be a bug in the application itself. KDE-related code in qtella is surrounded by #ifdef USEKDE, but at the point where you get the problem this is missing. Maybe adding a patch that puts #ifdef USEKDE around line 76 to 78 in main.cpp will solve this. It will remove the commandline-option "show-searches", though. I'll be happy to try with that patch. How do I get at the code of something in portage, though? Is there a doc that covers how to download the code, edit something, and then rebuild it? I've been trying to figure that out for a while; if you don't know of any, I'll probably submit a documentation bug. If you could tell me what to do, I'd be happy to try changing that. I do have some C++ experience; I moved the file from my distfiles/ directory, changed those lines, and gzip'd it back up. But I can't figure out how to tell portage to ignore the fact that the md5 is bad. not only did that have to be disabled, but yahoo! support also had to be disabled, as it relied on kdelib functions. Please sync your portage tree in a little while and try to remerge 0.7.0. Then, report back here and let me know if it worked. It compiled with those changes! Thanks for your help. patch sent upstream and is in portage; thanks for your report! *** Bug 56082 has been marked as a duplicate of this bug. *** |