SBackup fails if target path contains #

Bug #330680 reported by Matej Vitasek
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
sbackup (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: sbackup

When the target directory contains # (number sign), sbackupd fails with message
"E: Target directory is not writable - please test in simple-config-gnome!"
even though the access rights are set correctly (with no # backup works just fine).

The problem is, according to my quick research, calling the Python function gnomevfs.make_directory ( http://www.pygtk.org/pygnomevfs/gnomevfs-functions.html#function-gnomevfs--make_directory ). This function accepts the target *URI* as the first parameter, but sbackupd.py passes the original name to it, the one containing #. According to this http://en.wikipedia.org/wiki/URI everything after # in an URI is considered the "fragment".

The solution would probably be to URI-encode the target path first.

Using
Ubuntu 8.10
sbackup version 0.10.5ubuntu2

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

A fix for this issue was pushed into repository series 0.11.

Changed in sbackup (Ubuntu):
status: New → Fix Committed
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.

Other bug subscribers

Remote bug watches

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