Exclude regex for Trash does not include location used in Gnome >=2.22

Bug #249292 reported by Ludovic Lebègue
16
Affects Status Importance Assigned to Milestone
sbackup
Status tracked in Trunk
0.10
Won't Fix
Undecided
Unassigned
0.11
Invalid
Undecided
Unassigned
Trunk
Invalid
Undecided
Unassigned
sbackup (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: sbackup

The default Regexp location to exclude backup of Trash should be changed to "/home/[^/]+?/Trash/" has it is the default now with GNOME 2.22

Tags: bitesize
Revision history for this message
Ludovic Lebègue (llebegue) wrote :

Proposed patch

Common subdirectories: sbackup-0.10.4/debian and sbackup-0.10.4-new/debian
Common subdirectories: sbackup-0.10.4/po and sbackup-0.10.4-new/po
diff sbackup-0.10.4/sbackup.conf.example sbackup-0.10.4-new/sbackup.conf.example
56c56
< regex=\.mp3,\.avi,\.mpeg,\.mpg,\.mkv,\.ogg,\.ogm,\.tmp,/home/[^/]+?/\.thumbnails/,/home/[^/]+?/\.Trash,/home/[^/]+?/\..+/[cC]ache
---
> regex=\.mp3,\.avi,\.mpeg,\.mpg,\.mkv,\.ogg,\.ogm,\.tmp,/home/[^/]+?/\.thumbnails/,/home/[^/]+?/Trash,/home/[^/]+?/\..+/[cC]ache

Revision history for this message
Ludovic Lebègue (llebegue) wrote :

Actually the Regexp looks better if it is

/home/[^/]+?/\.local/share/Trash/

instead of

/home/[^/]+?/Trash

For 0.10.5 that would make a patch like this

diff -Nru sbackup-0.10.5/sbackup.conf.example sbackup-0.10.5-new/sbackup.conf.example
--- sbackup-0.10.5/sbackup.conf.example 2008-06-15 17:39:25.000000000 +0200
+++ sbackup-0.10.5-new/sbackup.conf.example 2008-07-17 19:48:37.000000000 +0200
@@ -53,7 +53,7 @@
 # of the file, it will NOT be backuped. Keep this list as specific
 # and as short as possible.

-regex=\.mp3,\.avi,\.mpeg,\.mpg,\.mkv,\.ogg,\.ogm,\.tmp,/home/[^/]+?/\.thumbnails/,/home/[^/]+?/\.Trash,/home/[^/]+?/\..+/[cC]ache,/home/[^/]+?/\.gvfs/
+regex=\.mp3,\.avi,\.mpeg,\.mpg,\.mkv,\.ogg,\.ogm,\.tmp,/home/[^/]+?/\.thumbnails/,/home/[^/]+?/\.local/share/Trash/,/home/[^/]+?/\..+/[cC]ache,/home/[^/]+?/\.gvfs/

 # Do not backup files bigger then this (in bytes)

Changed in sbackup:
status: New → In Progress
status: In Progress → New
Martin Schaaf (mascha)
Changed in sbackup:
status: New → Fix Committed
Revision history for this message
Przemek K. (azrael) wrote :

Is this bug fixed in Karmic or Lucid or not?

tags: added: bitesize
Revision history for this message
Juan Simón (simonbcn) wrote :

Incredible but no!! It isn't fixed yet. My sbackup has: "/home/[^/]+?/\.Trash"
A bug so simple to correct, 2 years old and it's still unsolved!!! o_O

Revision history for this message
Oumar Aziz OUATTARA (wattazoum) wrote :

I believe that SBackup has been updated on lucid. I suggest that you try NSsbackup. Look for it on Launchpad.

Revision history for this message
Jean-Peer Lorenz (peer.loz) wrote :

Changing status for sbackup 0.11 to 'Invalid' because it uses following regular expressions for exclusion by default:

\.mp3$
\.avi$
\.mpeg$
\.mkv$
\.ogg$
\.iso$
/home/[^/]+?/\.gvfs/
/home/[^/]+?/\.thumbnails/
/home/[^/]+?/\..+/[tT]rash/
/home/[^/]+?/\..+/[cC]ache/
~$

Revision history for this message
Jean-Peer Lorenz (peer.loz) wrote :

Changing status for sbackup 0.10 to 'Confirmed' because it uses following regular expressions:

/home/[^/]+?/\.thumbnails/
/home/[^/]+?/\.Trash
/home/[^/]+?/\..+/[cC]ache
/home/[^/]+?/\.gvfs/

summary: - Simple backup Regex for Trash to be changed for using gvfs
+ Exclude regex for Trash does not include location used in Gnome >=2.22
Revision history for this message
Jean-Peer Lorenz (peer.loz) wrote :

Status in Ubuntu distributions:

10.04 Lucid: is affected; packaged is sbackup 0.10.5ubuntu2.1
10.10 Maverick: not affected; packaged is 0.11.3 from the 0.11 series
11.04 Natty: not affected; 0.11 series

Revision history for this message
JC Hulce (soaringsky) wrote :

This bug has been marked as Fix Committed for over a year. If the fix has made it into Ubuntu, please mark this bug as Fix Released. If the fix has been released upstream, but not Ubuntu, create a new bug asking for the new version and tag it with upgrade-software-version. If this bug has not been fixed anywhere, change the status back to Confirmed.

Revision history for this message
Jean-Peer Lorenz (peer.loz) wrote :

The issue was fixed in sbackup series 0.11.x
Please upgrade. Thank you.

Changed in sbackup (Ubuntu):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.