Package: gphotofs
Version: 0.4.0-3
Severity: minor

Hi, 

I started to use gphotofs recently and had just noticed that files
under gphotofs are 1 hour more than the actual shoot time:

 $ jhead IMG_105{2,3,4}.JPG | grep -Ei 'IMG_|date'
 File name    : IMG_1052.JPG
 File date    : 2009:10:01 12:50:39
 Date/Time    : 2009:10:01 11:50:39
 File name    : IMG_1053.JPG
 File date    : 2009:10:01 12:55:04
 Date/Time    : 2009:10:01 11:55:04
 File name    : IMG_1054.JPG
 File date    : 2009:10:01 13:24:12
 Date/Time    : 2009:10:01 12:24:12

The "Date/Time" fields reflect the actual time, so the file
date/time is wrong. I always keep the correct file date/time on my
HD, so the wrong date/time on gphotofs defeats the rsync
incremental upload. 

Such wrong-time behavior only exhibit in gphotofs. If I mount the SD
directly via a all-in-one reader, the file date/time is right.

Thanks

Tong

-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (300, 'testing'), (50, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.28-grml64 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/bash

Versions of packages gphotofs depends on:
ii  fuse-utils                   2.7.4-1.1   Filesystem in USErspace (utilities
ii  libc6                        2.9-4       GNU C Library: Shared libraries
ii  libexif12                    0.6.16-2.1  library to parse EXIF files
ii  libfuse2                     2.7.4-1.1   Filesystem in USErspace library
ii  libglib2.0-0                 2.20.0-2    The GLib library of C routines
ii  libgphoto2-2                 2.4.4-1     gphoto2 digital camera library
ii  libgphoto2-port0             2.4.4-1     gphoto2 digital camera port librar
ii  libusb-0.1-4                 2:0.1.12-13 userspace USB programming library

gphotofs recommends no packages.

gphotofs suggests no packages.

-- no debconf information



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

Reply via email to