Re: [rdiff-backup-users] 64-bit Python

[Ben Escoto]

>>>>> Bob Fischer <address@hidden>
>>>>> wrote the following on Fri, 30 Jan 2004 10:56:57 -0500
> I run rdiff-backup on a 32-bit Linux machine (SuSE 9.0 P-II), trying to
> back up a 64-bit machine (SuSE 9.0 Kernel 2.6.1 AMD64).  This morning I
> got the error included at the end.
> 
> As best as I can tell, what's happening is a mismatch between the 32-bit
> integer types on one side and 64-bit integer type on the other side.  Is
> this true?
> 
> Has anyone else seen this?  It seems that rdiff-backup is best run with
> 32-bit pythons on both sides...
...
>     self.conn.os.utime(self.path, (long(time.time()), modtime))
> OverflowError: long int too large to convert to int

Sorry, I'm at a bit of a loss how the line:

self.conn.os.utime(self.path, (long(time.time()), modtime))

can cause that error, since nothing is getting converted to an int.
Maybe there is a bug in python on one connection you are running?  Try
making a temp file 'foobar', and then running python and typing in:

~ $ python
Python 2.2.3 (#1, Oct 15 2003, 23:33:35) 
[GCC 3.3.1 20030930 (Red Hat Linux 3.3.1-6)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import os, time
>>> os.utime('foobar', (long(time.time()), long(time.time())))
>>>

and make sure that works with no errors.  (Try this on both sides.)


-- 
Ben Escoto