Summary: | dev-util/kdevelop-3.3.2 stable request | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | David Carlos Manuelda <StormByte> |
Component: | New packages | Assignee: | Gentoo KDE team <kde> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | ansla80, gerdlc, ladanyi, nail2001, rossi.f |
Priority: | High | ||
Version: | 2006.0 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 133537 |
Description
David Carlos Manuelda
2006-05-31 18:58:34 UTC
Please arches mark kdevelop 3.3.2 stable as that's was supposed to go stable together with KDE 3.5, too. It's also needed because as you can see kdevelop 3.2 does not build with Qt 3.3.5 and later (3.3.6-r1 stable). well I'm having a segfault with r++, I won't be able to give a debug of it til tomorrow. Everything else within the kdevelop suite works though. Please advise, and I'll try and have the debug if needed tomorrow night for you. r++ segfaults on SPARC too, however I'm not sure what it actually does or how it should be invoked so that might be part of it. So anyone care to mention what it is that r++ does? I'd like to, if I had a clue about it >_> okay okay now i'll take a look to that. I think it is their C++ parser for code completion etc. I found a few links discussing it, but nothing describing it directly. I have been using kdevelop 3.3 for quite some time on amd64 without any issues, as have colleagues. I am not sure that r++ is supposed to be called directly, and I am unable to find any major bugs with kdevelop that make it worse than the current stable. I am open to opinions, but I am of the opinion that it is ready to go stable. I also agree that no program should just segfault but it does not seem to be causing breakage here. Arch teams, your current stable is *broken*. I don't give a damn about r++ segfaulting, no feature seems crippled by that and the command is not supposed to be ran by users, so _please_ mark this stable to fix your stable tree if you think well of your users. Stable on amd64. x86 is stable now. /me pokes flameeyes to be nice :-P. I care about the users when I have time to think about them *wink*. *whistle* >X_X< SPARC stable What about the first post. Same problem here. have you seen #133537? stable on ppc. We are the last arch. All done. |