Re: [rdiff-backup-users] changed file format?

[Ben Escoto]

>>>>> Stephen Isard <address@hidden>
>>>>> wrote the following on Tue, 01 Jun 2004 13:36:59 +0100

> I think you are right that it is something to do with daylight
> savings time.  When I sent my original message I was on GMT (same as
> UTC, no?).

Yes, I think GMT was too British so they made everyone refer to it
with a French acronym.

> So +01:00 would have been incorrect. The UK switched to summer time
> on 28 March, so +01:00 should now be right.  I have just redone the
> same test and got no error messages at all.  All the files from both
> 0.12.3 and 0.12.6 have +01:00 suffixes.

Since you've moved into dst, it may be too late to test this, but I
wonder if you could test this in your version of Python:

laptop:~ $ python
Python 2.3.3 (#1, May  7 2004, 10:31:40) 
[GCC 3.3.3 20040412 (Red Hat Linux 3.3.3-7)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import time
>>> time.daylight
1
>>> time.localtime()
(2004, 6, 6, 12, 12, 32, 6, 158, 1)
>>> time.altzone
25200
>>> time.timezone
28800

Where I am, we are in daylight savings, so we use the alternate
timezone, putting us 25200 seconds (7 hours) before UTC.  If you ever
see rdiff-backup giving the wrong date, perhaps you could check these
settings on your version of python.

> Yes. The two error_log files from the original test are
> error_log.2004-03-06T13:26:34+01:00.data.gz
> error_log.2004-03-06T13:28:37+01:00.data.gz
> 
> However, the current_mirror file (created by 0.12.6) is
> current_mirror.2004-03-06T13:28:37Z.data
> and all of the other data and stats files for 13:28:37 have Z as well.

I'm baffled by this error since, looking at the code, rdiff-backup
uses the same time string in both the current_mirror and error_log
files.  I can't see how they would every come out differently.  Is
this something you can still reproduce?


-- 
Ben Escoto

pgpJWt9UQG5nU.pgp
Description: PGP signature