Tree [23c99a] 2.7.0 / debian /
 History



File Date Author Commit
 README.Debian 2006-12-10 tmancill tmancill [392fb8] sync ./debian/ to 2.7.0-3
 changelog 2006-12-10 tmancill tmancill [392fb8] sync ./debian/ to 2.7.0-3
 control 2006-12-10 tmancill tmancill [392fb8] sync ./debian/ to 2.7.0-3
 copyright 2006-12-10 tmancill tmancill [a32a07] initial import of 2.7.0 source tree
 dirs 2006-12-10 tmancill tmancill [a32a07] initial import of 2.7.0 source tree
 docs 2006-12-10 tmancill tmancill [a32a07] initial import of 2.7.0 source tree
 links 2006-12-10 tmancill tmancill [a32a07] initial import of 2.7.0 source tree
 menu 2006-12-10 tmancill tmancill [a32a07] initial import of 2.7.0 source tree
 ripperX.sgml 2006-12-10 tmancill tmancill [392fb8] sync ./debian/ to 2.7.0-3
 ripperx.xpm 2006-12-10 tmancill tmancill [a32a07] initial import of 2.7.0 source tree
 rules 2006-12-10 tmancill tmancill [392fb8] sync ./debian/ to 2.7.0-3

Read Me

ripperX for Debian
------------------

ripperX got a much-needed shot in the arm from Dave Cinege, who 
picked up the Debian source and fixed a great number of bugs.  Check 
the debian/changelog for details, but in brief:

* generated filenames should be safe now
* no more empty tmp directories left around
* the progress bar works with cdparanoia 9.8
* using openpty() now, which should be devfs safe

There is an outstanding bug that occurs when the CDDB artist name 
contains the string ' / '.

############################
# FINDING YOUR CDROM DRIVE
############################

All access to the CD-ROM in ripperx is done via cdparanoia.  By
default, cdparanoia will look at /dev/cdrom (which you could symlink to
/dev/scd0, for example), or you can specify the correct device directly
via ripperX.  To do this:

* click on Config
* click on the Wav tab in the Config dialog
* type "-d /dev/scd0" into the Extra Options field

If you continue to have problems accessing your CD-ROM device, you can
try using "cdparanoia -v -Q" to access the device to look for meaningful
error messages.  Oftentimes the problem is related to permissions - either
the userid running ripperx is not a member of the "cdrom" group, or the
device permissions on your CD-ROM device themselves are not correct.

 -- tony mancill <tmancill@debian.org>  Sun, 09 Jul 2006 21:12:35 -0700

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks