If I build a new image by running "emerge baselayout" into an empty directory (having unmasked baselayout 2 and openrc), then I get the following packages drawn in: [binary N ] virtual/init-0 to /var/embedded/builds/base1/ [binary N ] sys-apps/baselayout-2.0.1 to /var/embedded/builds/base1/ USE="-build" [binary N ] sys-apps/openrc-0.4.3-r3 to /var/embedded/builds/base1/ USE="ncurses -debug -pam -unicode" Total: 3 packages (3 new), Size of downloads: 0 kB But then openrc winges about: >>> Installing (3 of 3) sys-apps/openrc-0.4.3-r3 to /var/embedded/builds/base1/ * checking 248 files for package collisions * Auto-adding 'termencoding' service to your boot runlevel ln: creating symbolic link `/var/embedded/builds/base1//etc/runlevels/boot/termencoding': No such file or directory * Auto-adding 'bootmisc' service to your boot runlevel ln: creating symbolic link `/var/embedded/builds/base1//etc/runlevels/boot/bootmisc': No such file or directory ..etc.. Which package is supposed to create /etc/runlevels/{boot,default,nonetwork, etc} ? (Running equery from the client root image says that these dirs are unowned by any package?) Vapier suggested filling this as a bug Reproducible: Always Steps to Reproduce:
fixed in cvs http://sources.gentoo.org/sys-apps/openrc/openrc-0.4.3-r3.ebuild?r1=1.3&r2=1.4 http://sources.gentoo.org/sys-apps/openrc/openrc-9999.ebuild?r1=1.50&r2=1.51
