I emerged microcode_ctl 1.08 and found this (this is the new init file before etc-update merging): nest falcone # cat /etc/init.d/._cfg0000_microcode_ctl # Copyright 1999-2004 Gentoo Foundation # Distributed under the terms of the GNU General Public License v2 # $Header: /var/cvsroot/gentoo-x86/sys-apps/microcode-ctl/files/microcode_ctl.conf.d,v 1.1 2004/09/01 01:16:46 vapier Exp $ MICROCODE_DEV="/dev/cpu/microcode" No wonder it complains at startup when running the init script: Sep 1 15:08:24 nest rc-scripts: Could not get dependency info for "microcode_ctl"! Sep 1 15:08:24 nest rc-scripts: Please run: Sep 1 15:08:24 nest rc-scripts: # /sbin/depscan.sh Sep 1 15:08:24 nest rc-scripts: to try and fix this. Sep 1 15:08:25 nest rc-scripts: Could not get dependency info for "microcode_ctl"! Sep 1 15:08:25 nest rc-scripts: Please run: Sep 1 15:08:25 nest rc-scripts: # /sbin/depscan.sh Sep 1 15:08:25 nest rc-scripts: to try and fix this. Sep 1 15:08:26 nest rc-scripts: Could not get dependency info for "microcode_ctl"! Sep 1 15:08:26 nest rc-scripts: Please run: Sep 1 15:08:26 nest rc-scripts: # /sbin/depscan.sh Sep 1 15:08:26 nest rc-scripts: to try and fix this. Sep 1 15:08:26 nest eth0: Setting full-duplex based on MII#1 link partner capability of 45e1. Sep 1 15:08:26 nest rc-scripts: Could not get dependency info for "microcode_ctl"! Sep 1 15:08:26 nest rc-scripts: Please run: Sep 1 15:08:26 nest rc-scripts: # /sbin/depscan.sh Sep 1 15:08:26 nest rc-scripts: to try and fix this. Sep 1 15:08:27 nest rc-scripts: Could not get dependency info for "microcode_ctl"! Sep 1 15:08:27 nest rc-scripts: Please run: Sep 1 15:08:27 nest rc-scripts: # /sbin/depscan.sh Sep 1 15:08:27 nest rc-scripts: to try and fix this. Sep 1 15:08:27 nest rc-scripts: ERROR: "microcode_ctl" does not have a start function. The important part: Sep 1 15:08:27 nest rc-scripts: ERROR: "microcode_ctl" does not have a start function. The interesting thing is, that the ebuild differs from 1.07-r1 but only the microcode.dat file was changed. If you update from previous version then you can leave the old initscript, thus skipping this bug. Or for new install: Install 1.07-r1 and download the appropriate microcode from the softwares website. Or update then to 1.08 and do what updaters should do. Reproducible: Always Steps to Reproduce: 1.emerge microcode-ctl or emerge -U microcode-ctl 2.etc-update (if update. if you don't let the new initscript to be merged the 3.rc-update add microcode_ctl default (if new install) 4.reboot Actual Results: Recieved a bunch of error messages at startup. Expected Results: Load the microcode. Portage 2.0.50-r10 (default-x86-2004.0, gcc-3.3.4, glibc-2.3.4.20040808-r0, 2.6.7-ck5) ================================================================= System uname: 2.6.7-ck5 i686 Pentium III (Coppermine) Gentoo Base System version 1.5.3 Autoconf: sys-devel/autoconf-2.59-r4 Automake: sys-devel/automake-1.8.5-r1 ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CFLAGS="-march=pentium3 -O3 -pipe -fomit-frame-pointer -fforce-addr -falign-functions=4 -fprefetch-loop-arrays" CHOST="i686-pc-linux-gnu" COMPILER="" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3.2/share/config /usr/kde/3.3/share/config:/usr/kde/3.3/env:/usr/kde/3.3/shutdown /usr/kde/3/share/config /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-march=pentium3 -O3 -pipe -fomit-frame-pointer -fforce-addr -falign-functions=4 -fprefetch-loop-arrays" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs ccache sandbox" GENTOO_MIRRORS="ftp://mirrors.sec.informatik.tu-darmstadt.de/gentoo/ http://gentoo.math.bme.hu ftp://gentoo.inode.at/source/ http://gentoo.inode.at/" MAKEOPTS="-j3" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="" SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage" USE="X aalib acl acpi adns alsa apm arts atlas audiofile avi bidi bindist bonobo caps cdr crypt cscope cups curl dedicated divx4linux dvb dvd emacs emacs-w3 encode ethereal evo fam fbcon fdftk fftw firebird flac flash foomaticdb freetds gb gd gdbm gif ginac gphoto2 gpm gstreamer gtk gtk2 gtkhtml icc icc-pgo ifc imagemagick imap imlib ipv6 jack java jikes jpeg lcms ldap leim lesstif libg++ libgda libwww mad maildir mcal memlimit mikmod mmx monitors motif mozilla mpeg mpi mule nas ncurses nhc98 nls nocardbus nocd nptl odbc offensive oggvorbis opengl pam pdflib perl plotutils png ppds prelude python quicktime readline ruby sasl sdl slang slp snmp speex spell sqlite sse ssl svg svga tcltk tcpd theora threads tiff truetype unicode usb video_cards_rage128 videos wmf x86 xface xml xml2 xmms xosd xv xvid zlib"
The other thing I don't get why is it in dependency with the 2.6.8.1 headers, less would be enough as well... Since no change in code.
whoops, should have had a 'newins' not a 'newexe' fixed init in portage as for the DEPEND, the ebuild DEPENDs on virtual/os-headers, not a specific version
Yes I have seen the ebuild from the inside. The interesting thing is: It wanted to emerge linux26-headers 2.6.8.1 so I did it with nodeps. If I knew what was missing I would have written it down. I'm not yet familiar with ebuilds that much.
