Bug List: (This bug is not in your last search results)   Show last search results      Search page      Enter new bug
Bug#: 30702
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Robert Coie (RETIRED) <rac@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Paul Moore <pcmoore@umich.edu>
Add CC:
CC:
Remove selected CCs
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 30702 depends on: Show dependency tree
Bug 30702 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug


Description:   Opened: 2003-10-08 15:42 0000
I get the following error (-v flag used with emerge) on certain packages (this
particular one was autoconf-2.57a-r1):

***
>>> Regenerating /etc/ld.so.cache...
>>> Regenerating /etc/ld.so.cache...
>>> Auto-cleaning packages ...

>>> No outdated packages were found on your system.


 * Regenerating GNU info directory index...
install-info: warning: no info dir entry in
`//usr/share/info/emodules.info.orig.gz'
 * Processed 75 info files; 1 errors.
***

Here is my emerge info output:

***
Portage 2.0.48-r5 (default-alpha-1.4, gcc-3.2.3, glibc-2.3.1-r4,2.3.2-r1)
=================================================================
System uname: 2.4.21-alpha-r1 alpha EV67
GENTOO_MIRRORS="http://gentoo.oregonstate.edu
http://www.ibiblio.org/pub/Linux/distributions/gentoo"
CONFIG_PROTECT="/etc /var/qmail/control /usr/share/config
/usr/kde/2/share/config /usr/kde/3/share/config /usr/X11R6/lib/X11/xkb"
CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d"
PORTDIR="/usr/portage"
DISTDIR="/usr/portage/distfiles"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR_OVERLAY="/usr/local/my_gentoo"
USE="alpha encode foomaticdb gif jpeg kde libg++ libwww mikmod ncurses oss
pdflib png qt quicktime sdl spell truetype xml2 xmms xv gnome-libs gdbm berkdb
slang readline tcltk ruby gpm tcpd pam ssl perl python esd imlib oggvorbis
motif mozilla ev6 ipv6 X xinerama gtk gtk2 opengl java zlib gnome cups ldap
crypt mozsvg mozspellcheck -alsa -nls"
COMPILER="gcc3"
CHOST="alphaev67-unknown-linux-gnu"
CFLAGS="-mcpu=ev67 -O3 -pipe "
CXXFLAGS="-mcpu=ev67 -O3 -pipe "
ACCEPT_KEYWORDS="alpha ~alpha"
MAKEOPTS="-j1"
AUTOCLEAN="yes"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
FEATURES="ccache"
***

Thanks for your help.

------- Comment #1 From SpanKY 2003-10-08 19:35:59 0000 -------
please run `qpkg -f /usr/share/info/emodules.info.orig.gz` and tell us what
package owns it

------- Comment #2 From Paul Moore 2003-10-09 06:56:39 0000 -------
Thanks for the quick response, here is the info you asked for:

***
[pmoore@sockpuppet ~ ]qpkg -f /usr/share/info/emodules.info.orig.gz
app-editors/xemacs *
[pmoore@sockpuppet ~ ]
***

Let me know if you need any more information.

------- Comment #3 From Seemant Kulleen (RETIRED) 2003-10-15 18:24:07 0000 -------
portage devs, any hints on this?

------- Comment #4 From Doug Weimer 2003-10-15 23:30:39 0000 -------
This fails because /usr/share/info/emodules.info.orig.gz needs to be removed
by the ebuild before installation. The .orig file is created by patch due
to a fuzzy match with 'emodules.info-21.4.8-gentoo.patch'. The line 'rm -f
${D}/usr/share/info/emodules.info~*' in the xemacs ebulids appears to be
an attempt to fix this, but the backup file created is named emodules.info.orig
so ~* doesn't work.

To fix this either update the patch to properly match each xemacs version
or add 'rm -f ${D}/usr/share/info/emodules.info.orig'.

The fuzzy match occurs because the patch is based on version 21.4.8 and the
"makeinfo version" line in emodules.info is different in newer versions of
xemacs.

------- Comment #5 From Paul Moore 2003-10-16 10:12:56 0000 -------
... so does this mean that to fix my problem i can just delete the offending
file?

------- Comment #6 From Doug Weimer 2003-10-16 20:55:05 0000 -------
As far as I understand the way info works, yes, you can delete it. Because
the file contained an error it wouldn't have been added into the main info
directory, so you shouldn't have to update the dir file.

------- Comment #7 From Paul Moore 2003-11-12 09:19:59 0000 -------
I just deleted the file and all is well, thanks for your help ... marking this
FIXED.

------- Comment #8 From Donnie Berkholz 2003-12-18 09:07:16 0000 -------
*** Bug 36045 has been marked as a duplicate of this bug. ***

Bug List: (This bug is not in your last search results)   Show last search results      Search page      Enter new bug