| Summary: | =dev-lang/python-{2.5.4-r5,2.6.8-r1,2.7.3-r3,3.1.5-r1,3.2.3-r2} stable request | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Nikoli <nikoli> |
| Component: | [OLD] Keywording and Stabilization | Assignee: | Python Gentoo Team <python> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | idl0r |
| Priority: | Normal | Keywords: | STABLEREQ |
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Bug Depends on: | |||
| Bug Blocks: | 463532 | ||
|
Description
Nikoli
2013-02-19 16:35:57 UTC
wontfix for now because most of them are vulnerable. I don't think it's that clear-cut, and I don't think the arch team should be the ones to make these kinds of decisions. Upstream doesn't even have patches ready, so it'll be realistically be quite a while before we have something we can put in the tree. Does it really make sense to hold off these stabilization over that? (I'm fine if we say we should hold off, I just think we should have the discussion.) I would like to see these versions go stable. And no, I don't think that a security bug is a reason to hold of stabilization when no fix is available or tested. Adding archs. amd64 stable x86 stable ppc stable ppc64 stable Stable for HPPA. arm stable alpha stable Seems there is one regression: bug #462862 ia64 stable sparc stable sh stable s390 stable M68K is not anymore a stable arch, removing it from the cc list |