Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 51237 - emerge emacs has errors
Summary: emerge emacs has errors
Status: RESOLVED NEEDINFO
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: x86 Linux
: High normal (vote)
Assignee: Emacs project
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-05-16 17:33 UTC by Stony
Modified: 2004-08-23 03:59 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Stony 2004-05-16 17:33:38 UTC
When I emerge emacs, it says there are errors.  I looked, but I couldn't even locate the errors it was talking about.

Reproducible: Always
Steps to Reproduce:
1.emerge -u emacs
2.
3.

Actual Results:  
emacs is installed, but it says there was an error:
>>> No outdated packages were found on your system.
 
 
 * Regenerating GNU info directory index...
 * Processed 510 info files: 1 errors; run with emerge --verbose to view errors

Expected Results:  
It should have said
Emerge Successfull!!

Email me back and I will attach a log file of the emerge.  I don't think I want
to drop it in this html box.
Comment 1 Matthew Kennedy (RETIRED) gentoo-dev 2004-05-16 23:32:56 UTC
Hi. Please attach your emerge log.  Also, please attach the output of "emerge --verbose emacs"
Comment 2 alex f 2004-06-23 01:31:16 UTC
I bet this is the libcdio info file error. It's already fixed, someonejust needs to make the latest libcdio ebuild stable.
Comment 3 Troels Henriksen 2004-08-22 04:04:07 UTC
Doesn't this have something to do with the Info-system? I get this all the time, I think it happens when an Info-file can't be updated or something like that.

It doesn't really matter.
Comment 4 Mamoru KOMACHI (RETIRED) gentoo-dev 2004-08-23 03:59:02 UTC
Yes, we need to know what package says the error. If the original reporter gives us more information, we'll reassign this bug to appropriate package maintainer.