Timezone 5.0.7 windows

Marking Bug #531980 a duplicate - we reported this the same time.

Will there be a fix for 5.0.7 or will it only be fixed in 5.0.8?
Lionel

Workaround: remove the users' time zones (you'll have to enter it again when this is fixed)
    update res_users set context_tz =null;
Lionel

This other, seems to work but must be more testing is to :
    install 5.0.6 version,
    copy library.zip
    install 5.0.7 version
    extract from library.zip v 5.0.6 pytz directory
    delete from library.zip v5.0.7 pytz directory
    insert into library.zip pytz v 5.0.6 directory

Just a remark. I try to unzip both library, copy between directory,k and rezip it, and that doesn't work (i don't understand why)
But with explorer, without unzipping library, just enter in it and drag adn drop library, no warning when running 5.0.7 client.

Have a nice day and good tests

Damage that for a software which wants to be international and professionnal no language and timezone patch is online in download section.
Well done for test and develop 5.2 branch, but stable version is incomplete.

Stephane, reassigning to you, seems that this really is a packaging issue for Client 5.0.7. Basically using the library.zip in client-5.0.7 you can't do 'import pytz' anymore, and you can also see that the zoneinfo directory is missing, now if you replace the whole pytz module with the pytz module from 5.0.6 or the one in the pytz-2010b-py2.5.egg from the web-5.0.7 it works.

Could you double-check the windows packaging procedures and make sure that they are deterministic? How come we have different pytz modules in web and client, or between 5.0.6 and 5.0.7?

And by the way, why does one of them use a site-packages python deployment structure while the other has a library.zip version without sources?

BTW everyone, you don't need to use SQL if your user has a timezone set and you want to remove it temporarily: it is possible to unset the timezone using the User Preferences in the Web client (not in GTK).

 I will add a backlog item to make this consistent.

Hi all,

I uploaded a beta of the client 5.0.8, can you check and tell me if the issue is still valid.

http://openerp.com/download/unstable/win32/openerp-client-setup-5.0.8beta1.exe

Thanks

I uploaded this branch for a code review:

Branch: https://code.launchpad.net/~stephane-openerp/openobject-client/fix_timezone_pytz
Windows Installer: http://openerp.com/download/unstable/win32/openerp-client-setup-5.0.8.dev1055.exe

I will ask to the code reviewer to check the bugfix

I had a feedback and the last client has a bug with the timezone :/

Don't use it,

Stephane

I pushed a new version of my Windows Installer for this bugfix

Branch: https://code.launchpad.net/~stephane-openerp/openobject-client/fix_timezone_pytz
Windows Installer: http://openerp.com/download/unstable/win32/openerp-client-setup-5.0.8.dev1056.exe

Please report,

Thanks

Stéphane,
I still meet this problem using openerp-client-setup-5.0.8.dev1056.exe, sorry.
Lionel

I know, I just fixed the packaging process.

I'm uploading a new version of the client and I checked the zoneinfo directory from pytz-2010, I think it's fixed.

Can you test this version ?

http://openerp.com/download/unstable/win32/openerp-client-setup-5.0.8.pytz1.exe

Thanks

Stéphane,
This version fixed this issue on my setup. Thanks.
You marked the bug with "fix released" - do you advise we use this version in production, or should we wait for 5.0.8?
Lionel

This version is not the official, it's a test to be sure that we have removed the bug with the pytz package.

The official 5.0.8 is still planned for the next week (April 1st).

And the bug was in the packaging process (on my Windows box).

Stéphane,

I just tested it and it's ok for me.

Many thanks.