Bug 424948

Summary:	audacious-3.2.4 dodoc: README does not exist
Product:	Gentoo Linux	Reporter:	mjbjr
Component:	Current packages	Assignee:	Gentoo Linux bug wranglers <bug-wranglers>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	kripton
Priority:	Normal
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---
Attachments:	emerge --info emerge -pqv '=media-sound/audacious-3.2.4' build log build env

Description mjbjr 2012-07-05 16:55:19 UTC

Created attachment 317316 [details]
emerge --info

Successfully installed zh_CN.mo.
Successfully installed zh_TW.mo.
Leaving directory po.
install: cannot stat `README': No such file or directory
!!! dodoc: README does not exist
 * ERROR: media-sound/audacious-3.2.4 failed (install phase):
 *   dodoc failed
 * 
 * If you need support, post the output of `emerge --info '=media-sound/audacious-3.2.4'`,
 * the complete build log and the output of `emerge -pqv '=media-sound/audacious-3.2.4'`.
 * The complete build log is located at '/var/tmp/portage/media-sound/audacious-3.2.4/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/media-sound/audacious-3.2.4/temp/environment'.
 * Working directory: '/var/tmp/portage/media-sound/audacious-3.2.4/work/audacious-3.2.4'
 * S: '/var/tmp/portage/media-sound/audacious-3.2.4/work/audacious-3.2.4'
 * QA Notice: file does not exist:
 * 
 * 	dodoc: README does not exist

>>> Failed to emerge media-sound/audacious-3.2.4

Comment 1 mjbjr 2012-07-05 16:56:27 UTC

Created attachment 317318 [details]
emerge -pqv '=media-sound/audacious-3.2.4'

Comment 2 mjbjr 2012-07-05 17:01:11 UTC

Created attachment 317320 [details]
build log

Comment 3 mjbjr 2012-07-05 17:02:15 UTC

Created attachment 317322 [details]
build env

Comment 4 jannis 2012-07-05 17:09:19 UTC

same here on ~amd64

Comment 5 Rafał Mużyło 2012-07-05 17:42:02 UTC

Search first !!!

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

Comment 6 mjbjr 2012-07-05 18:12:37 UTC

(In reply to comment #5)
> Search first !!!
> 
> *** This bug has been marked as a duplicate of bug 424912 ***

I did search, using the text in the bug title.

Why is 424912 crossed out?

Is it or is it not a duplicate of bug 42912?

Comment 7 Rafał Mużyło 2012-07-05 19:01:55 UTC

(In reply to comment #6)
> (In reply to comment #5)
> I did search, using the text in the bug title.
> 
> Why is 424912 crossed out?
> 

:roll: Cause it's been fixed by now.