Bug 412307 – dev-python/pytz-2012c stabilization request

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Ian Delaney (RETIRED) 2012-04-17 08:25:18 UTC]

archtester pytz # USE_PYTHON="2.6 2.7 3.1" ebuild pytz-2012c.ebuild clean test 

 * Testing of dev-python/pytz-2012c with CPython 2.6...
........................................................................................................................
Ran 203 tests in 0.414s               OK

 * Testing of dev-python/pytz-2012c with CPython 2.7...
.........................................................................................................................

Ran 203 tests in 0.417s              OK

 * Testing of dev-python/pytz-2012c with CPython 3.1...
........................................................................................................................

Ran 203 tests in 0.476s              OK

archtester pytz # USE_PYTHON="2.6 2.7 3.1" ebuild pytz-2012c.ebuild merge
>>> Original instance of package unmerged safely.
 * Compilation and optimization of Python modules for CPython 2.6        [ ok ]
 * Compilation and optimization of Python modules for CPython 2.7        [ ok ]
 * Compilation and optimization of Python modules for CPython 3.1        [ ok ]
>>> dev-python/pytz-2012c merged.

good to go

[Comment 1 Patrick Lauer 2012-04-18 05:14:25 UTC]

+  18 Apr 2012; Patrick Lauer <[e-mail]> +pytz-2012c.ebuild,
+  -pytz-2011g.ebuild, -pytz-2011h.ebuild, -pytz-2011k.ebuild,
+  -pytz-2011n.ebuild:
+  Bump for #412307

[Comment 2 Patrick Lauer 2012-04-18 05:18:41 UTC]

Arch teams, please get us some new timezone definitions for python stable. Very boring package, so it should not be a problem :)

Target keywords: "alpha amd64 arm hppa ia64 ppc ppc64 s390 sh sparc x86"

[Comment 3 SpanKY 2012-04-18 18:33:29 UTC]

why are you asking for stabilization on a package you added less than *12* hours ago ?  how could this possibly be critical ?

[Comment 4 Agostino Sarubbo 2012-04-24 08:34:21 UTC]

(In reply to comment #3)
> why are you asking for stabilization on a package you added less than *12*
> hours ago ?  how could this possibly be critical ?

No response.

From irc, from python herd, seems there is not a valid reason to do this now.

Please reopen it in the future, only when you have filed a bug to base-system for new timezone-data.

[Comment 5 SpanKY 2012-04-27 15:58:12 UTC]

toolchain maintains timezone-data ;).  also, i've marked 2012c stable there.

[Comment 6 Mike Gilbert 2012-04-28 05:24:15 UTC]

Reopening so this does not get lost.

[Comment 7 Kacper Kowalik (Xarthisius) (RETIRED) 2012-05-28 18:50:47 UTC]

(In reply to comment #6)
> Reopening so this does not get lost.
Looks like it got lost nevertheless :)

Corresponding sys-libs/timezone-data is stable on all arches, so please proceed. TIA!

[Comment 8 Jeff (JD) Horelick (RETIRED) 2012-05-29 05:37:14 UTC]

x86 stable

[Comment 9 Agostino Sarubbo 2012-05-29 12:11:26 UTC]

amd64 stable

[Comment 10 Brent Baude (RETIRED) 2012-05-29 19:48:22 UTC]

ppc done

[Comment 11 Markus Meier 2012-06-03 18:15:19 UTC]

arm stable

[Comment 12 Brent Baude (RETIRED) 2012-06-05 21:15:49 UTC]

ppc64 done

[Comment 13 Jeroen Roovers (RETIRED) 2012-06-06 15:20:45 UTC]

Stable for HPPA.

[Comment 14 Raúl Porcel (RETIRED) 2012-07-01 18:29:24 UTC]

alpha/ia64/s390/sh/sparc stable