Your message dated Mon, 11 Apr 2011 17:57:28 -0400
with message-id <[email protected]>
and subject line Problems with ~/.gvs
has caused the Debian Bug report #590252,
regarding Problems with ./~gvs
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
590252: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=590252
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: flexbackup
Version: 1.2.1-6
Severity: important
The backup-images are deleted when a gnome user mount ~/.gvs is active.
flexbackup return 1, but gives no output on stderr.
This is a known problem discussed in the flexbackup mailinglist :
http://sourceforge.net/mailarchive/message.php?msg_name=1237420040.3064.46.camel%40localhost
--- End Message ---
--- Begin Message ---
severity normal
thanks
1. The url of the discussion is incomplete. It should be:
http://sourceforge.net/mailarchive/forum.php?thread_name=1237983739.3229.4.camel%40localhost&forum_name=flexbackup-help
2. This report is by a third party over a year after the original
discussion took place. Mr. Henze, could you reproduce this bug?
3. In the specific instance mentioned in the referenced discussion, the
'find' command is erroring out for this particular user.
4. Flexback is a perl script that ties together a number of basic
utilities. Problems with the execution of those utilities should not
be simply attributed to flexback, but analyzed for what they are.
>From the flexbackup FAQ 4.9:
"If flexbackup detects a non-zero exit status for any command in the
pipeline, it will stop. Something probably happened further up in the
log that caused the archive or buffering program to exit with an error
status. Look over the log again, or run with "-d verbose=false" to turn
off the printing of filenames to make it more obvious."
The non-zero exit from find caused flexbackup to exit.
The thing to do is to run find with its arguments stand-alone and review
the output.
I'm not sure why Mr. Canner was unable to get find working using prunes
and excludes. It may be due to root being unable to stat .gvfs, but I
don't have the inclination to pursue that.
If you want to get to the root of things (pun intended) look here:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/225361
Closing this, as it is not a flexbackup issue.
--
KBK
--- End Message ---
