A routine system upgrade using only hardened ebuilds (no ~arch masks) with:
pulls in a version of hotplug (20040923) that will render the system unusable on the next reboot.
Rumor has it in bug #70793 that an ewarn has been added to the ebuild. However the continued interest in bug #11359 shows that an ewarn by itself is not useful because nobody will ever see it in the middle of a multi-package emerge.
Since this new hotplug package has the potential to render most systems unusable, the ebuild should refuse to run if any of the pre-requisites are not already in place. There is also some doubt expressed in bug #70793 as to whether the pre-requisites are even appropriate.
I would suggest that this ebuild be immediately masked off until a proper solution can be found.
Steps to Reproduce:
After reboot the system was unusable because it could no longer find many of the
required hardware devices. It took about an hour to determine what the problem
might be (due to the loss of any network access) and then about 10 minutes to
rebuild the old package to verify. Luckily the older working ebuild (and
tarball) had not been purged from the system.
Not install a hardened ebuild that was guaranteed to break the system.
sabre root # emerge info
Portage 2.0.51-r3 (default-linux/x86/2004.0, gcc-3.3.4, glibc-188.8.131.5240808-r1,
System uname: 2.4.26-gentoo-r9 i686 AMD Athlon(tm) XP 1700+
Gentoo Base System version 1.4.16
distcc 2.16 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [enabled]
ccache version 2.3 [enabled]
CFLAGS="-O3 -march=athlon-xp -funroll-loops -pipe"
CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config
/usr/kde/3.1/share/config /usr/kde/3.2/share/config /usr/kde/3.3/env
/usr/kde/3.3/share/config /usr/kde/3.3/shutdown /usr/kde/3/share/config
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-O3 -march=athlon-xp -funroll-loops -pipe"
FEATURES="autoaddcvs ccache distcc distlocks maketest sandbox severe sfperms
USE="3dnow X alsa apache2 apm arts avi berkdb bitmap-fonts bonobo cdr cjk crypt
cups curl dga directfb divx4linux doc dvb dvd dvdread emacs encode esd ethereal
f77 fam fastcgi fbcon flac foomaticdb fortran gb gd gdbm gif gnome gphoto2 gpm
gtk gtk2 gtkhtml guile imagemagick imap imlib innodb java jpeg junit kde libg++
libwww live mad maildir mikmod mmx motif mozilla mpeg mysql nas ncurses network
nls odbc ofx oggvorbis opengl oss pam pda pdflib perl png python qt quicktime
quotes readline samba sasl sdl slang slp spell sse ssl svga tcltk tcpd tetex
theora tiff truetype unicode usb wmf x86 xml xml2 xmms xv xvid zeo zlib"
sabre root #
How on earth could Bug 70793 be resolved as FIXED? Does someone really think that "fix" is a proper word? You are leaving an ebuild marked stable with some sort of message displayed after emerging it, while it requires a dependency on another ebuild to be able to use system after reboot? :-(
*** This bug has been marked as a duplicate of 70793 ***
Until such time as bug #70793 is reopened and resolved in an acceptable manner, I will continue to reopen this bug so that people doing a bug search on "hotplug" instead of "ALL hotplug" will have a hint on how to recover their broken systems.
People are working on notifying users better right now.
Your patience is appreciated.
This bug is closed.