Hello,

On Mon, Oct 23, 2006 at 06:05:37PM +0200, A Mennucc wrote:
> Package: unison-gtk
> Version: 2.13.16-5
> Severity: minor
> 
> hi
> 
> I have recently started  using Debian/etch/amd64 on my work PC ;
> there are some files (coming from old damaged FAT floppies ) that
> have now different (and weird) modification times.
> 
> When I  use unison from my notebook (that runs on
> Debian/etch/i386) to the above PC, unison wants to sync the mtime
> (since I use "times=yes"), but unison fails
> 
> Here is an example error:
> 
> disks/vecchi_floppy/roba/orario4.bas
> Failed to set modification time of file 
> /home/andrea/disks/vecchi_floppy/roba/orario4.bas to 1901-12-13 at 21:45:52: 
> the time was set to 1901-12-13 at 21:45:52 instead
> 
> (it does not sound very intelligent , BTW)
> 
> Here is the stat of the file in the i386
> 
> $ stat disks/vecchi_floppy/roba/orario4.bas
>   File: `disks/vecchi_floppy/roba/orario4.bas'
>   Size: 29793           Blocks: 64         IO Block: 4096   regular file
> Device: fe00h/65024d    Inode: 126183      Links: 1
> Access: (0744/-rwxr--r--)  Uid: (  226/  andrea)   Gid: ( 1000/  andrea)
> Access: 1901-12-13 21:45:52.000000000 +0100
> Modify: 1901-12-13 21:45:52.000000000 +0100
> Change: 2006-10-23 17:42:28.000000000 +0200
> 
> 
> here is the stat of the file in the amd64
> 
> $ stat disks/vecchi_floppy/roba/orario4.bas
>   File: `disks/vecchi_floppy/roba/orario4.bas'
>   Size: 29793           Blocks: 64         IO Block: 4096   regular file
> Device: 306h/774d       Inode: 149420      Links: 1
> Access: (0744/-rwxr--r--)  Uid: (  226/  andrea)   Gid: ( 1000/  andrea)
> Access: 2006-10-23 17:41:33.000000000 +0200
> Modify: 2038-01-19 04:14:08.000000000 +0100
> Change: 2006-10-23 14:24:48.000000000 +0200
> 
> 
> It may be that unison is confused by having 64 bit dates on one side,
> 32 bit on the other.
> 
> 
> a.

OK, it is off course, an upstream bugs. I will forward it to upstream.


Kind regard
Sylvain Le Gall


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to