fongecore / rubyripper

Automatically exported from code.google.com/p/rubyripper
0 stars 0 forks source link

Claims that intended final file folder is already created and cannot proceed #41

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Open rubyripper
2. Set finished file location to desired location
3. Click "Rip Now"

What is the expected output? What do you see instead?
I expect that the CD will actually rip. Instead, the correct directory is
created, but Rubyripper claims it already existed, and so it could not rip.

What version of the product are you using? On what operating system?
Rubyripper 0.3 Ubuntu "Dapper Drake"

Please provide any additional information below.

Original issue reported on code.google.com by sam.j.sc...@gmail.com on 24 Dec 2006 at 3:20

GoogleCodeExporter commented 8 years ago
This one is also reported on the Rubyforge bugtracker (which is deprecated). I 
can't reproduce this so far. The only way I get this message is.

* I have ripped the same CD before and forgot to remove the directory
* I made a mistake in my settings, I get a warning, change the setting and then 
the 
directory is already created.

Only the second reason I can do something about, by creating the directories as 
very last check.

Please post your config ~/.rubyripper_config file anyway

Original comment by rubyripp...@gmail.com on 24 Dec 2006 at 9:14

GoogleCodeExporter commented 8 years ago
I found a bug in my code that applies when you
* select multiple codecs
AND
* don't use %f (the output dir will be the same for all codecs)

This is now fixed in svn revision 43.
I will close the bug presuming that only under this conditions the problex 
exists. 
Please verify (and open another bug if other conditions will lead to the same 
thing).

Original comment by rubyripp...@gmail.com on 24 Dec 2006 at 9:29

GoogleCodeExporter commented 8 years ago

Original comment by rubyripp...@gmail.com on 24 Dec 2006 at 9:29

GoogleCodeExporter commented 8 years ago
Problem is solved. Thank you.

Original comment by sam.j.sc...@gmail.com on 24 Dec 2006 at 3:07