Bug#639537: backintime: messes with file access time when performing backups

[Julian Gilbey]

Package: backintime-gnome
Version: 1.0.8-1
Severity: normal

Hi!

When backintime performs a backup, it does not preserve the file
access time. This means that mailbox-checking programs, such as mutt,
lose the information as to when the mailbox was last actually read.

I would recommend that backintime does something like

orig_times = os.stat(file)
[perform whichever actions required on file]
os.utime(file, (orig_times.st_atime, orig_times.st_mtime))

whenever it needs to read a file for backup purposes.

Julian

-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'oldstable'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.0.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_GB.UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages backintime-gnome depends on:
ii backintime-common 1.0.8-1 simple backup/snapshot system
ii menu 2.1.45 generates programs menu for all me
ii python 2.6.7-3 interactive high-level object-orie
ii python-glade2 2.24.0-2 GTK+ bindings: Glade support
ii python-gnome2 2.28.1-3 Python bindings for the GNOME desk
ii python-gtk2 2.24.0-2 Python bindings for the GTK+ widge
ii python-notify 0.1.1-3 Python bindings for libnotify

Versions of packages backintime-gnome recommends:
ii meld 1.4.0-2 graphical tool to diff and merge f
ii nautilus-actions 3.1.2-1 nautilus extension to configure pr

backintime-gnome suggests no packages.

-- no debconf information

--
To UNSUBSCRIBE, email to debian-bugs-...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org

[c.b...@posteo.jp]

Thanks for the report.
Can you reproduce that problem with current "stable" Debian version?

[c.b...@posteo.jp]

Dear Julian,

I'm a member of the new upstream maintainer team.

The bug is quit old. Please try to reproduce that problem with the
current upstream version.
If you can reproduce it please open an Issue at upstream and link it
here.

It seems rsync specific but we would take care of it if it is
reproducable.

I suggest to close that Debian bug report because it seems not distro
specific.

Kind
Christian Buhtz