93872 – xcdroast "Expecting at least version 2.01a11" (need updated cdrecord-prodvd)

Bug 93872 - xcdroast "Expecting at least version 2.01a11" (need updated cdrecord-prodvd)

Summary: xcdroast "Expecting at least version 2.01a11" (need updated cdrecord-prodvd)

Status:	RESOLVED DUPLICATE of bug 82733

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	Current packages (show other bugs)
Hardware:	x86 Linux

Importance:	High minor (vote)
Assignee:	Gentoo Optical Media project

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2005-05-24 18:55 UTC by Kevin Airy
Modified:	2005-05-30 16:02 UTC (History)
CC List:	0 users

See Also:
Package list:
Runtime testing required:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Kevin Airy 2005-05-24 18:55:56 UTC

I did emerge -uD cdrecord-prodvd cdrtools xcdroast, and then tried to run 
xcdroast and it says "Warning invalid cdrecord-ProDVD version 2.01.01a01 found
Expecting at least version 2.01a11
Start xcdroast with the -n option to override (not recommended!)
A later version of cdrecord-ProDVD is available, but not a newer ebuild.

Reproducible: Always
Steps to Reproduce:
1.emerge -uD cdrecord-prodvd cdrtools xcdroast
2.xcdroast
3.

Actual Results:  
Warning invalid cdrecord-ProDVD version 2.01.01a01 found
Expecting at least version 2.01a11
Start xcdroast with the -n option to override (not recommended!)


Expected Results:  
Should run fine as soon as a new ebuild with 2.01a11 or higher is released.

cdrecord-prodvd-2.01b31-i686-pc-linux-gnu is available for download from
http://ftp.berlios.de/pub/cdrecord/ProDVD/

Comment 1 Lars Weiler (RETIRED) gentoo-dev

2005-05-30 16:02:59 UTC

cdrecord-prodvd is at the latest available version.  Please have a look at
ftp://ftp.berlios.de/pub/cdrecord/ProDVD/

Your error is xcdroast related.  There is just the workaround with -n, as the
author states himself.  Your problem has been reported in bug #82733 already.

*** This bug has been marked as a duplicate of 82733 ***