| Summary: | Stable =net-p2p/valknut-0.4.9 | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Samuli Suominen (RETIRED) <ssuominen> |
| Component: | Current packages | Assignee: | Gentoo net-p2p team <net-p2p> |
| Status: | RESOLVED FIXED | ||
| Severity: | enhancement | CC: | esigra |
| Priority: | High | Keywords: | STABLEREQ |
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Bug Depends on: | |||
| Bug Blocks: | 234660, 283429 | ||
|
Description
Samuli Suominen (RETIRED)
2009-12-16 16:28:53 UTC
Stable for HPPA. I marked =net-p2p/dclib-0.3.23 but valknut-0.3.23 is a Qt3 application and as per bug #283429, all Qt3 applications are about to be removed. I propose to go for valknet Qt4 version instead ( valknut-0.4.9 ) As discussed on IRC with Samuli, We ( as Qt team ) would like to remove all Qt3 applications as soon as possible, so having another stable qt3 application doesn't make sense. Closing this bug as LATER , in order to stabilize version 0.4.9 in ~30days Cheers I filed bug #283429 to collect packages which would need attention before Qt3 would be deprecated (i.e. masked). That bug report still doesn't have a date set, and in the mean time, dclib-0.3.23 fixes quite a few bugs compared to the previous stable, which means that we should still stabilise that, and along with it anything Qt3-based as long as it isn't clear when Qt3 is going to be masked. C.f. [1], which explains why dclib-0.3.23 is important, particularly the =Hub address sent on making peer connections= section. I know you'd like to get rid of Qt3 yesterday, but that's not realistic. [1] http://wxdcgui.sourceforge.net/news-0.3.23.html (In reply to comment #4) > [1] http://wxdcgui.sourceforge.net/news-0.3.23.html Actually, you'll need to read all the changelogs from 0.3.14 onward - because of the blocking bug #234660, bigendian arches got stuck on 0.3.13 and for those (3 out of 6, minus the now stable HPPA) it's probably best to stabilise 0.3.23 to have at least something newer than 0.3.13. Well OK. As I said I am against this stabilization but I guess we can stabilize it and remove it later So, stable for amd64 In the light of recent events, we might as well get 0.4.9 stable... specially for tracking purposes, so linking to bug 283429. x86 stable amd64 stable too ppc64 done ppc stable Stable for HPPA. alpha/ia64 keywords dropped, closing |