>-----Original Message-----
>From: Philipp Marek [mailto:[EMAIL PROTECTED]
>Sent: Tuesday, June 26, 2007 1:48 PM
>To: [email protected]
>Cc: Worley, Chris B
>Subject: Re: Invalid or incomplete multibyte or wide character
>
>Hello Chris!
>
>
>On Dienstag, 26. Juni 2007 Worley, Chris B wrote:
>> I had the "multibyte" error a few times in my commit.  The
work-around
>> is to "fsvs ignore" those files (or delete them).
>Yes, but that's really only a work-around. That should Just Work(TM).
>Please see my other mail.

Yes, I'll fix the locale settings.  Thanks for the fix.

>
>> It is strange that
>> even when "ignored" the file names show up during "commit".
>They shouldn't. Are you sure that you ignored them correctly?

I'm never sure I'm doing anything correctly ;)

I used both:

# fsvs ignore "./roots/*/var/log/*"
# fsvs ignore ./roots/2/var/log/*

...and my dump looks like:

# fsvs ignore dump
...
./roots/2/var/log/messages
...
./roots/*/var/log/*

...and my commit looks like:

# fsvs commit -m "test"
...
.mC.     13786  ./roots/2/var/log/messages
...

Note that I never did an "fsvs init"... the README " How is it used?"
section didn't contain one... I didn't see the "init" command until I
read the "USAGE".

Thanks,

Chris
P.S. thanks for the explanation of the diff issue.  I just won't worry
about the error output.
P.P.S. Lines wrapped by Outlook.  Oulook su***.
>
>> I also had an error in "fsvs diff" of binary files:
>>
>> [EMAIL PROTECTED] challanger.x86_64]# fsvs diff
>> ./roots/2/var/lib/rpm/Packages
>> diff -u ./roots/2/var/lib/rpm/Packages.r2
>> ./roots/2/var/lib/rpm/Packages.local
>> Binary files ./roots/2/var/lib/rpm/Packages     Rev. 2          (Fri
Jun
>> 8 09:54:56 2007) and ./roots/2/var/lib/rpm/Packages         Local
>> version   (Wed Jun 13 16:10:50 2007) differ
>I hope that the lines are just wrapped because of the mail, and not in
the
>console output?
>
>> An error occurred: No such file or directory (2)
>>   in df__do_diff: Child 16391 gave an exit status 2
>Well, diff has documented that "... exit status of 0 means no
differences were
>found, 1 means some differences were found, and 2 means trouble."
>
>I didn't know that binary files mean trouble; I'd diffed some of them
>with "-a" very successfully.
>
>Hmmm ... What to do?
>I don't like to ignore the error code 2, as that could mean *real*
trouble,
>too.
>The other way would be to check the files ourself for binaryness, which
is not
>the Right Thing ... as more or less the same check is duplicated in
diff, and
>we'd possibly had to read the whole files.
>
>I wrote a mail to the GNU diff mailing list
>(http://lists.gnu.org/archive/html/bug-gnu-utils/2007-06/threads.html),
let's
>take a look what they say.
>
>Perhaps the easiest way (for now!) is to write a small shell script
that
>simply contains something like
>       #!/bin/sh
>       diff "$@"
>       exit 0
>and give its path via FSVS_DIFF to fsvs. That allows to ignore such
errors.
>
>
>I'll keep track of this issue; would you like to be notified if there's
any
>news or do you check yourself?
>
>
>Regards,
>
>Phil
>
>
>--
>Versioning your /etc, /home or even your whole installation?
>             Try fsvs (fsvs.tigris.org)!

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to