current bug reproduce with following version: anaconda-11.5.0.12 +++ This bug was initially created as a clone of Bug #227625 +++ Description of problem: during installation in Punjabi (Indian Language), default selected Time zone was US/NewYork, but it should be Calcuta Version-Release number of selected component (if applicable): anaconda-11.2.0.19-1.x86_64.rpm How reproducible: Everytime during install in Punjabi Steps to Reproduce: 1. Select Installation in Punjabi 2. Move forward till Time zone reach 3. Actual results: it is US/NewYork Expected results: should Asia/Calcuta (India) Additional info: using following build rawhide-20070206 --- Additional comment from abartlet on 2007-02-07 17:28:55 EDT --- While for some languages it might be quite clear the connection between the Language and a good guess at the location, is this something we can actually do in the general case, without causing nightmares? What would happen if we selected timezones based on a language shared between two countries that object to the other? We will quickly have nobody happy. Personally I think the default should be UTC until the map is clicked. --- Additional comment from aalam on 2007-02-07 23:14:42 EDT --- it is based on locale, as pa_IN is represent Punjabi_India, where *_IN is limiting the area as India, and so timezone is clearly 1 and only 1 Calcutta. --- Additional comment from abartlet on 2007-02-08 06:44:35 EDT --- Sure, but should en_AU be Sydney, Adelaide or Perth? Should en_US be east or west coast? I still argue you can't win... --- Additional comment from aalam on 2007-02-08 07:50:15 EDT --- I think bug was only for pa_IN, not going to consider en_AU as it is very far from my city --- Additional comment from clumens on 2007-02-21 14:59:44 EDT --- This will be fixed in the next release of anaconda. It affects at least all languages that anaconda cannot display during the initial stage.
Can you please attach additional information verifying that this is a problem with F11 or rawhide? These cloned bugs can be hard to tell whether it's actually a problem or not without extra information attached. Thanks.
it was in rawhide (before 14July), but tested with latest rawhide Bug is not there. it is showing correct timezone Closing bug...