You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Ben Collins-Sussman <su...@collab.net> on 2005/07/05 20:08:09 UTC
Re: bug: time zone problem with use-commit-times option
Michael, will you please file this as a bug? It definitely sounds
like a problem to me. (When you file the bug, point out that I asked
you to file it.) Sorry for the delayed response.
On Apr 29, 2005, at 7:20 AM, Michael.Brackx@alcatel.be wrote:
> Hi,
>
> It seems the use-commit-times option does not take the time zone
> into account. This gives problems as the checked out files can
> appear to be modified in the future.
>
> scenario:
> - server is in time zone -8
> - clients are in time zone +1
> - commit a file on a client
> - check out the file on a client with the use-commit-times option
> enabled: the file's last modified time is 9 hours into the future.
>
> server: subversion 1.1.4 (r13838), apache 2.0.54, windows 2000
> client: subversion 1.1.4 (r13838), windows 2000
>
> Michael
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: bug: time zone problem with use-commit-times option
Posted by kf...@collab.net.
Ben Collins-Sussman <su...@collab.net> writes:
> Michael, will you please file this as a bug? It definitely sounds
> like a problem to me. (When you file the bug, point out that I asked
> you to file it.) Sorry for the delayed response.
Not just point out that you asked, but point to this thread itself! :-)
-K
> On Apr 29, 2005, at 7:20 AM, Michael.Brackx@alcatel.be wrote:
>
> > Hi,
> >
> > It seems the use-commit-times option does not take the time zone
> > into account. This gives problems as the checked out files can
> > appear to be modified in the future.
> >
> > scenario:
> > - server is in time zone -8
> > - clients are in time zone +1
> > - commit a file on a client
> > - check out the file on a client with the use-commit-times option
> > enabled: the file's last modified time is 9 hours into the future.
> >
> > server: subversion 1.1.4 (r13838), apache 2.0.54, windows 2000
> > client: subversion 1.1.4 (r13838), windows 2000
> >
> > Michael
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> > For additional commands, e-mail: users-help@subversion.tigris.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: bug: time zone problem with use-commit-times option
Posted by Gary Thomas <ga...@mlbassoc.com>.
On Tue, 2005-07-05 at 15:08 -0500, Ben Collins-Sussman wrote:
> Michael, will you please file this as a bug? It definitely sounds
> like a problem to me. (When you file the bug, point out that I asked
> you to file it.) Sorry for the delayed response.
>
>
> On Apr 29, 2005, at 7:20 AM, Michael.Brackx@alcatel.be wrote:
>
> > Hi,
> >
> > It seems the use-commit-times option does not take the time zone
> > into account. This gives problems as the checked out files can
> > appear to be modified in the future.
> >
> > scenario:
> > - server is in time zone -8
> > - clients are in time zone +1
> > - commit a file on a client
> > - check out the file on a client with the use-commit-times option
> > enabled: the file's last modified time is 9 hours into the future.
> >
> > server: subversion 1.1.4 (r13838), apache 2.0.54, windows 2000
> > client: subversion 1.1.4 (r13838), windows 2000
BTW, I just tested this and did not observe anything incorrect.
My server is GMT-0600. I tested it with two clients GMT-0600
and GMT+0100. When I look at the time stamps on the files, they
are identical:
[gary@neptune gary]$ date
Tue Jul 5 21:46:05 BST 2005
[gary@neptune gary]$ TZ=GMT ls -ltr wx_tools
total 48
-rw-rw-r-- 1 gary gary 909 Feb 11 18:19 releaseTool.py
-rw-rw-r-- 1 gary gary 7738 Feb 14 15:44 releaseToolFrame.py
-rw-rw-r-- 1 gary gary 5781 Feb 14 15:44 makeRPMDialog.py
-rw-rw-r-- 1 gary gary 800 Feb 16 16:13 config.py
-rw-rw-r-- 1 gary gary 5972 Feb 25 23:40 runCmdDialog.py
-rw-rw-r-- 1 gary gary 10219 May 31 17:30 makeCustomerReleaseDialog.py
-rw-rw-r-- 1 gary gary 930 Jun 17 16:16 boards.cfg
[gthomas@hermes support_tools]$ date
Tue Jul 5 14:46:17 MDT 2005
[gthomas@hermes support_tools]$ TZ=GMT ls -ltr wx_tools
total 48
-rw-r--r-- 1 gthomas wheel 909 Feb 11 18:19 releaseTool.py
-rw-r--r-- 1 gthomas wheel 7738 Feb 14 15:44 releaseToolFrame.py
-rw-r--r-- 1 gthomas wheel 5781 Feb 14 15:44 makeRPMDialog.py
-rw-r--r-- 1 gthomas wheel 800 Feb 16 16:13 config.py
-rw-r--r-- 1 gthomas wheel 5972 Feb 25 23:40 runCmdDialog.py
-rw-r--r-- 1 gthomas wheel 10219 May 31 17:30 makeCustomerReleaseDialog.py
-rw-r--r-- 1 gthomas wheel 930 Jun 17 16:16 boards.cfg
Of course, when you look at the times in local time, they are
quite different:
[gary@neptune gary]$ ls -ltr wx_tools
total 48
-rw-rw-r-- 1 gary gary 909 Feb 11 18:19 releaseTool.py
-rw-rw-r-- 1 gary gary 7738 Feb 14 15:44 releaseToolFrame.py
-rw-rw-r-- 1 gary gary 5781 Feb 14 15:44 makeRPMDialog.py
-rw-rw-r-- 1 gary gary 800 Feb 16 16:13 config.py
-rw-rw-r-- 1 gary gary 5972 Feb 25 23:40 runCmdDialog.py
-rw-rw-r-- 1 gary gary 10219 May 31 18:30 makeCustomerReleaseDialog.py
-rw-rw-r-- 1 gary gary 930 Jun 17 17:16 boards.cfg
[gthomas@hermes support_tools]$ ls -ltr wx_tools/
total 48
-rw-r--r-- 1 gthomas wheel 909 Feb 11 11:19 releaseTool.py
-rw-r--r-- 1 gthomas wheel 7738 Feb 14 08:44 releaseToolFrame.py
-rw-r--r-- 1 gthomas wheel 5781 Feb 14 08:44 makeRPMDialog.py
-rw-r--r-- 1 gthomas wheel 800 Feb 16 09:13 config.py
-rw-r--r-- 1 gthomas wheel 5972 Feb 25 16:40 runCmdDialog.py
-rw-r--r-- 1 gthomas wheel 10219 May 31 11:30 makeCustomerReleaseDialog.py
-rw-r--r-- 1 gthomas wheel 930 Jun 17 10:16 boards.cfg
Are you sure that what you're seeing is not just the local time
differences? (e.g. 'ls' normally prints using local time)
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: bug: time zone problem with use-commit-times option
Posted by Mi...@alcatel.be.
Hi,
I don't think it is a bug anymore. I believe it is a feature :)
Altough in the mean time I upgraded to /version 1.2.0 (r14790)/, I am
able to reproduce the "problem".
Probably my problem was that the time of the server was actually in the
future. The commit time of a file is the time of the server and not of
the client (I assume this is a feature). So the commit was actually in
the future. And the time of file when checking it out is also in the future.
Michael
Ben Collins-Sussman wrote:
> Michael, will you please file this as a bug? It definitely sounds
> like a problem to me. (When you file the bug, point out that I asked
> you to file it.) Sorry for the delayed response.
>
>
> On Apr 29, 2005, at 7:20 AM, Michael.Brackx@alcatel.be wrote:
>
>> Hi,
>>
>> It seems the use-commit-times option does not take the time zone
>> into account. This gives problems as the checked out files can
>> appear to be modified in the future.
>>
>> scenario:
>> - server is in time zone -8
>> - clients are in time zone +1
>> - commit a file on a client
>> - check out the file on a client with the use-commit-times option
>> enabled: the file's last modified time is 9 hours into the future.
>>
>> server: subversion 1.1.4 (r13838), apache 2.0.54, windows 2000
>> client: subversion 1.1.4 (r13838), windows 2000
>>
>> Michael
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
>> For additional commands, e-mail: users-help@subversion.tigris.org
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: bug: time zone problem with use-commit-times option
Posted by Norbert Unterberg <nu...@gmail.com>.
2005/7/5, Ben Collins-Sussman <su...@collab.net>:
> > It seems the use-commit-times option does not take the time zone
> > into account. This gives problems as the checked out files can
> > appear to be modified in the future.
Is this still a problem with version 1.2? The use-commit-times option
was broken 1.1.4, but there have been corrections in 1.2.0.
Norbert
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org