Summary: | Please stabilize dev-python/psycopg-2.4.2 and dev-python/egenix-mx-base-3.2.1-r1 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Ian Delaney (RETIRED) <idella4> |
Component: | [OLD] Keywording and Stabilization | Assignee: | Python Gentoo Team <python> |
Status: | RESOLVED FIXED | ||
Severity: | enhancement | Keywords: | STABLEREQ |
Priority: | Normal | ||
Version: | 10.0 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | 394917 | ||
Bug Blocks: | |||
Attachments: | build.log |
Description
Ian Delaney (RETIRED)
2011-12-01 17:59:01 UTC
Please try to watch your spelling a little bit more. Duly noted. arch teams please stabilize =dev-python/psycopg-2.4.2 =dev-python/egenix-mx-base Are you a psycopg and egenix-mx-base maintainer or did you talk to a maintainer before CC'ing the arches? If not, please don't CC the arches. Since python is maintainer, what python herd says here? Anyway, BSD team is not relevant to stable request CC back amd64 if maintainer says ok to stabilize. Please go ahead, sorry for the delay. Created attachment 296021 [details] build.log (In reply to comment #7) > Please go ahead, sorry for the delay. No problem, just to be sure that maintainer agree, so in my build log there are a lot of warnings but there is not failure, it looks ok for you? They look like doc-only warnings, so the stabilization should be okay. amd64 stable x86 stable alpha/arm/ia64/s390/sh/sparc stable ppc done ppc64 stable, last arch done |