cfv-users — user questions and discussion

[cfv-users] Future of cfv

[<cfv...@da...>]

Hello,

cfv is my favorite checksumming tool since nearly a decade. Matthew and all
contributors, I want to thank you for writing this great tool and all effort you
put into it!

I recently installed a Debian buster system and I wanted to do a simple

  apt install cfv

However, that did not work, because cfv was removed from Debian buster.

I am writing all this because I think development of cfv has stalled and I want
to change that.

I like the tool and care for it, that's why I have started a repository at
Github [1] for continuing development of cfv.

Anybody is welcome to join me!

Stay tuned for an upcoming 2.0 release of cfv :)

Best regards,
David Gnedt

[1] https://github.com/cfv-project/cfv

[cfv-users] --strippaths=all on create

[Robert G. <ro...@re...>]

Having a weird issue when creating sfv files.

cfv -C --strippaths=all -t sfv -f $SFV $OUTFILE.rar

The above command does not strip the paths out. I still see the
original full path in the sfv file. When i use strippaths while
verifying, it works just peachy. Is this intended?

Verify
cfv --strippaths=all -f file.sfv

I would prefer to create the sfv files without paths.. just basename
so its easier to verify.

Thoughts?

-- 
Rob Gil
REM5

[cfv-users] vague errors.

[<gnu...@gm...>]

Hi. Firstly thanks for your useful app.

There is probably a better place for this but anyway.

while doing "cfv -C -r " on my mp3 collection, which already has some 
.cfv 's in it.
i got "3219 files, 0 OK, 263 chksum file errors.  0.425 seconds, 0.0K/s"

After much testing i figured out that the chksum file errors where from 
my existing .cfv's.

I dont like the look of those errors.

Could you please make a option to update the existing chksums. Thanks.

Re: [cfv-users] WinXP filename globbing (was: (no subject))

[Matthew M. <do...@us...>]

Hey there, sorry for the late reply, missed the email since this list
doesn't usually get much traffic.

On Sun, Nov 28, 2004 at 12:38:26AM +0100, Sknerus McKwacz wrote:
> I have too copies of the same folder (WinXP)
> 
> C:\a
> 
> +---b
> |   |   test01.jpg
> |   |   test02.jpg
> |   |   test03.jpg
> |   |
> |   \---CSV
> |           test.csv
> |
> \---b [d]
>     |   test01.jpg
>     |   test02.jpg
>     |   test03.jpg
>     |
>     \---CSV
>             test.csv
> 
> Now the command:
>   cfv -p "c:\a\b" -u -t csv -f "c:\a\b\CSV\test.csv" "c:\a\b\*.jpg"
> 
> gives 
>   c:\a\b\CSV\test.csv: 8 files, 8 OK.  0.047 seconds, 81981.9K/s
> 
> But
>   cfv -p "c:\a\b [d]" -u -t csv -f "c:\a\b [d]\CSV\test.csv" "c:\a\b
> [d]\*.jpg"
> 
> gives:
>   cfv: no matches for c:\a\b [d]\*.jpg
> 
> While this one works ok:
>    cfv -p "c:\a\b [d]" -u -t csv -f "c:\a\b [d]\CSV\test.csv"
> 
> Any ideas?

On windows the shell doesn't do the globbing itself, so any applications
have to do it themselves.  In this case, the directory "b [d]" is
causing a problem because [d] is interpreted as a character set
containing the letter d.  You can work around it by encasing the [
inside a pair of [], like so: "c:\a\b [[]d]\*.jpg"
This is a bit ugly, but there is really no way around it, the standard
of escaping special characters with a \ doesn't work too well on windows
since that is the path separator...

In this case however, you should be able to say 
cfv -p "c:\a\b [d]" -u -t csv -f CSV\test.csv *.jpg
since -p changes to the given directory, the specified paths are then
relative to that directory and you can get by without having to put the
[d] in there at all.

-- 
Matthew Mueller
do...@us...

[cfv-users] (no subject)

[Sknerus M. <mc...@ho...>]

I have too copies of the same folder (WinXP)

C:\a

+---b

|   |   test01.jpg

|   |   test02.jpg

|   |   test03.jpg

|   |

|   \---CSV

|           test.csv

|

\---b [d]

    |   test01.jpg

    |   test02.jpg

    |   test03.jpg

    |

    \---CSV

            test.csv

 

Now the command:

  cfv -p "c:\a\b" -u -t csv -f "c:\a\b\CSV\test.csv" "c:\a\b\*.jpg"

 

gives 

  c:\a\b\CSV\test.csv: 8 files, 8 OK.  0.047 seconds, 81981.9K/s

 

But

  cfv -p "c:\a\b [d]" -u -t csv -f "c:\a\b [d]\CSV\test.csv" "c:\a\b
[d]\*.jpg"

 

gives:

  cfv: no matches for c:\a\b [d]\*.jpg

 

While this one works ok:

   cfv -p "c:\a\b [d]" -u -t csv -f "c:\a\b [d]\CSV\test.csv"

 

 

Any ideas?

 

Regards,

Sknerus

Re: [cfv-users] Leading \ required in Path

[Matthew M. <do...@us...>]

On Mon, Nov 15, 2004 at 01:39:46PM -0800, Di'dact wrote:
> I do 
>  
> cfv -C -rr -t csv4 -f B.csv B
>  
> and get items like this
>  
> halima05.jpg,138040,6a89c6e3,"B\Baker, Joseph\The Tale of Halima 1&2",
>  
> According to all the csvs I've used in the past the B shouldn't be there, there should be a leading \ following the quote.  I'm using this on winnt and win98 and need it to not have the leading B there and have a leading slash.  Any ideas?
>  
> Carl

There are two ways to get rid of the leading B:

1)
cd B
cfv -C -rr -t csv4 -f ../B.csv

2)
cfv -C -rr -t csv4 -p B -f ../B.csv

(hmm, perhaps the --strippaths option should apply to creation as
well...)

There isn't a way currently to get it to add the leading slash though.  
Unfortunatly with csv files there isn't really any standard to follow,
so it's hard to say if having the leading slash is "right" or not.  What
is the reason you need it?  For compatibility with other software?


-- 
Matthew Mueller
do...@us...

[cfv-users] Leading \ required in Path

[Di'dact <did...@ya...>]

I do 
 
cfv -C -rr -t csv4 -f B.csv B
 
and get items like this
 
halima05.jpg,138040,6a89c6e3,"B\Baker, Joseph\The Tale of Halima 1&2",
 
According to all the csvs I've used in the past the B shouldn't be there, there should be a leading \ following the quote.  I'm using this on winnt and win98 and need it to not have the leading B there and have a leading slash.  Any ideas?
 
Carl

		
---------------------------------
Do you Yahoo!?
 Discover all that’s new in My Yahoo!