Summary: | =app-portage/eix-0.28.5 : please stabilize | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Ian Stakenvicius (RETIRED) <axs> |
Component: | Current packages | Assignee: | Ian Stakenvicius (RETIRED) <axs> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | martin |
Priority: | Normal | Keywords: | STABLEREQ |
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Ian Stakenvicius (RETIRED)
![]() Stable for HPPA. app-portage/eix-0.28.5[clang] depends on sys-devel/clang, so, if we want to stabilize app-portage/eix-0.28.5 we need to stabilize sys-devel/clang first. (In reply to Ian Stakenvicius from comment #0) > [...] the only active bug [...] There are 4 opened bugs for eix-0.28.5: - bug 475564 - bug 474590 - bug 471132 - bug 471085 (In reply to Vicente Olivert Riera from comment #2) Regarding clang, I'm fine with use.stable.mask'ing that flag (In reply to Vicente Olivert Riera from comment #3) > (In reply to Ian Stakenvicius from comment #0) > > [...] the only active bug [...] > > There are 4 opened bugs for eix-0.28.5: > - bug 475564 > - bug 474590 > - bug 471132 > - bug 471085 474590 is the feature request for ~arch portage that I mentioned 471132 is not a valid bug but is being left open so that users can see it I apologize for missing 471085 (which I thought was resolved) and 475564. The former has been taken care of in 0.29.0 and i have no idea about the latter. How would ATs like to proceed? Mark RESO/INVA and try again when 0.29.0 is old enough? or... (In reply to Ian Stakenvicius from comment #4) > How would ATs like to proceed? Mark RESO/INVA and try again when > 0.29.0 is old enough? or... If all of those bugs will be fixed on 0.29.0 I would close this bug and wait until 0.29.0 be in the tree. Then I would wait 30 days to let people try that version and finally file a stable request on bugzilla. makes sense. |