On 07/03/2012 10:15 AM, Marcelo Moreira de Mello wrote:
On 07/03/2012 07:01 AM, Jan Pazdziora wrote:
On Mon, Jul 02, 2012 at 05:12:58PM -0300, Marcelo Moreira de Mello wrote:
Hello team,
Here follow a patch which fixed the issue reported on BZ#798571.
Marcelo,
are we sure that it's just the description change that is needed? Do
the timezones otherwise work as expected on both Perl and Java stacks,
or is some logic change needed as well?
Hello Jan,
I thought the same when I was changing the code. Then, I checked the
git changelog and saw some commits which only changed the description
(0518d03935bdefa5cf0a1e5b76b7f44105eaf6f2 per example).
Looking the commit b77210efc1f39fbb095f47b8c67580045b4b6165, it seems
that the trick to the Perl and Java stacks seems to use the timezone
description (such as America/Sao_Paulo).
After changing the code, the webUI displayed the Russian time using
GMT+4 as expected.
Best Regards,
mmello
Hi guys,
I can't speak for anything else, but 0518d039 was a special case. In
that bug the time zones were operating properly and adding the correct
number of hours to GMT to get the time, but the text in the string
resource file was incorrect. You shouldn't use that as a model unless
the same is true of the time zones you are looking at.
-Stephen
_______________________________________________
Spacewalk-devel mailing list
Spacewalk-devel@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-devel
