Summary: | Stabilize www-servers/tornado-2.2.1 | ||
---|---|---|---|
Product: | Gentoo Security | Reporter: | Dirkjan Ochtman (RETIRED) <djc> |
Component: | Vulnerabilities | Assignee: | Python Gentoo Team <python> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | mike |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 416547 |
Description
Dirkjan Ochtman (RETIRED)
2012-05-14 10:50:42 UTC
amd64 stable Just wanted to mention that 2.2.1 [1] is (mostly) a security fix. Perhaps skipping to that is warranted? [1] http://www.tornadoweb.org/documentation/releases/v2.2.1.html Ebuilds generally have to spend 30 days in unstable before being eligible for stabilization. It's definitely too soon to stabilize 2.2.1. I thought fixes to known security bugs in stabilized ebuilds were an exception to that. It doesn't matter to me - just wanted to make it known. Ah, sorry, I can't read. In that case, this would probably be a good idea. amd64, sorry, for the extra work. (In reply to comment #2) > Just wanted to mention that 2.2.1 [1] is (mostly) a security fix. Perhaps > skipping to that is warranted? > > [1] http://www.tornadoweb.org/documentation/releases/v2.2.1.html Then I think security@ should take it. amd64 stable x86 stable |