[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#511153: marked as done (tzsetup-udeb: time zone list in tzsetup out of date wrt glibc/tzdata time)

Your message dated Sun, 2 Mar 2014 13:58:59 +0100
with message-id <20140302125859.GG22946@mraw.org>
and subject line Re: Bug#511153: tzsetup-udeb: time zone list in tzsetup out of date wrt glibc/tzdata time
has caused the Debian Bug report #511153,
regarding tzsetup-udeb: time zone list in tzsetup out of date wrt glibc/tzdata time
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
511153: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=511153
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: tzsetup-udeb
Severity: wishlist
In rev 2332 of pkg-glibc (http://svn.debian.org/viewsvn/pkg-glibc?rev=2332&view=rev), a number of new time zones, such as Indiana/Knox and Kentucky/Louisville were added.
It looks like these new time zones aren't being surfaced in tzsetup-udeb yet.
Please update tzsetup-udeb so it's aligned with the latest pkg-glibc time zone data. 


-- System Information:
Debian Release: lenny/sid
APT prefers hardy-updates
APT policy: (500, 'hardy-updates'), (500, 'hardy-security'), (500, 'hardy'), (500, 'dapper-updates'), (500, 'dapper-security'), (500, 'dapper') 

Architecture: amd64 (x86_64)

Kernel: Linux 2.6.24-19-server (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
~

--- End Message ---
--- Begin Message --- 
Christian PERRIER <bubulle@debian.org> (2014-03-02):
> Quoting Cyril Brulebois (kibi@debian.org):
> 
> > > Actually, there might me other cases like this one as I haven't seen
> > > anyone actively trying to cope with changes in tzdata to align tzsetup
> > > with them (such as the recent nightmare in Argentinian timezones).
> > 
> > what should we do about this bug report?
> 
> IIRC, there have been a few moments in various releases, where the
> list of possible timezones for multi-TZ countries have been
> updated. So, in short, it can be closed, IMHO.

Alright, doing so, thanks.

Mraw,
KiBi.

Attachment: signature.asc
Description: Digital signature


--- End Message ---
Reply to: