there's change in Belarus' timezone that needs to be stabilized - only 1,5 weeks left: # Belarus # From Yauhen Kharuzhy (2011-09-16): # By latest Belarus government act Europe/Minsk timezone was changed to # GMT+3 without DST (was GMT+2 with DST). Reproducible: Always
Actually, now we need 2011m as soon as possible and it is critical. Time in Ukraine/Kyiv does not show up properly as of today. The system thinks that Ukraine is not switching back to Winter time and sticking to DST all-year-round. Could be an issue for users in Ukraine.
Belarus timezone is now incorrect starting from today. Please stabilize newer package ASAP.
Marked 2011l stable. If you need a version bump file a bug for one.
http://sources.gentoo.org/viewcvs.py/gentoo-x86/sys-libs/timezone-data/timezone-data-2011l.ebuild?r1=1.2&r2=1.3
When did we stop doing arch testing/stabilising, particularly for packages that actually compile stuff for different platforms?
Since the only changes from prev versions are in the data, the stabilization is extremely time-sensitive, and we have an exception? Did I break something or did you just feel like complaining?
I'll gladly make an exception for timezone-data, as the source code, last I checked, only changes once an year or so, but the description data is, as Ryan puts it, "extremely time-sensitive". My real question is why is this package under toolchain rather than base-system (and I'm _not_ complaining about Ryan's choice).
timezone-data was forked from the C library, and glibc is the largest (only?) consumer on the system, so toolchain makes sense