Summary: | openssh 4.0_p1 stops functioning after emerged sys-libs/com_err-1.37 package | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Robert Velisav MICIOVICI <robert.miciovici> |
Component: | Current packages | Assignee: | SpanKY <vapier> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | jay.phelps, michael.knappe, seemant, wschlich |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Robert Velisav MICIOVICI
2005-06-24 16:02:53 UTC
Portage is not able to resolve reverse dependencies (yet). Does `revdep-rebuild` fix this? libcom_err.so.3 is provided by kerberos i believe, not e2fsprogs seemant: i vaguely remember another bug being filed about this ? This is definitely bad. revdep-rebuild found only twi packages to rebuild, NOT including openssh and samba. I guess I'll discover more alaong the way :( thats probably because openssh doesnt link against com_err ... it links against kerberos which links against com_err Not asking the obvious how a big 'error' like this could get into "x86" and wasn't cought by "~x86" i'm wondering how I can fix this problem I have 2 'stable' systems that I can't login to anymore and I won't be around for a nother 2 months to fix it myself. They don't have keyboards nor telnetd running. I guess the only way to 'fix' this is to get someone to hookup a keyboard, blindly log in, and run revdep-rebuild. If I can get that to happen, would ssh automatically work again or do I need a reboot then still too? Please let there be a nother way to 'fix' this remotly with the current sshd ... I do have apache and glftpd for example running that are still accessable. So I just emerge -avuD world on a nother box and noticed that there was indeed a note. However I, as probably many, don't watch their output continually. So I would recommend not for only this update, but also for other updates that require for example a revdep-rebuild, to Re-warn once the emerge cycle is complete. Maybe even finish with a question like 'you must run revdep-rebuild because of broken packages'. This is more then just an inconvinience. This can lead into major problems! This was reported a few days ago, and i updated today and have the same problem! Shouldn't someone mask a critical bug like this in portage so that we don't lock out people who only have ssh access (very common for servers!) It's not a 'bug'. There IS a message popping by inbetween that you have to run revdep-rebuild (which might not even be installed). So what if you decide to update your box before going home, and you loose your link overnight. You don't wanna be driving across the country to fix your remote servers. I don't know what the best 'fix' for this should be. But portage should atleast 'stop' right then and there so that you atleast can see the message. Ideally after an update that breaks openssh (which it can't figure out on it's on (yet) so should be done in the ebuild) openssh should be remerged so we know for sure that sshd will always remain working. (Maybe ldd-ing sshd from the ebuild or something like before and after and see that if it wasn't broken before, then this ebuild broke it.) I always read output from emerges (PORTLOG_DIR ist set), but the problem is that revdep-rebuild does not detect most of the broken packages. On x86 it did not find samba nor openssh. On alpha it found both. I have no explanation for this, though. Same error on amd64. Running stable amd64 and ssh is broken. revdep-build does not detect any problem. Running latest stable gentoolkit-0.2.0. I found no problems with openssh 3.9_p1-r2 on amd64 with com_err-1.37 on x86 I need to recompile openssh, but on amd64 everything is working fine... gentoolkit-0.2.0 I have run into the same problem, sshd does not work anymore due to missing libcom_err.so.3. But actually also updating to PEAR-DB-1.7.6 fails for the same reason: >>> Install PEAR-DB-1.7.6 into /var/tmp/portage/PEAR-DB-1.7.6/image/ category dev-php /usr/bin/php: error while loading shared libraries: libcom_err.so.3: cannot open shared object file: No such file or directory !!! ERROR: dev-php/PEAR-DB-1.7.6 failed. !!! Function php-pear_src_install, Line 49, Exitcode 127 !!! (no error message) revdep-rebuild does not help. On the affected system I can find the following libcom_err files: affected_system portage # find / -name "libcom_err*" /lib/libcom_err.so /lib/libcom_err.so.2 /lib/libcom_err.so.2.1 /usr/lib/libcom_err.a /usr/lib/libcom_err.so As I am operating a bunch of gentoo servers it looks like I have bad luck each time I install or update one. This is my emerge info: affected_system lib # emerge info Portage 2.0.51.19 (default-linux/x86/2005.0, gcc-3.3.5-20050130, glibc-2.3.4.20041102-r1, 2.6.11-gentoo-r11 i686) ================================================================= System uname: 2.6.11-gentoo-r11 i686 Intel(R) Xeon(TM) CPU 2.40GHz Gentoo Base System version 1.6.12 Python: dev-lang/python-2.3.5 [2.3.5 (#1, Jun 14 2005, 18:51:34)] dev-lang/python: 2.3.5 sys-apps/sandbox: [Not Present] sys-devel/autoconf: 2.13, 2.59-r6 sys-devel/automake: 1.5, 1.8.5-r3, 1.7.9-r1, 1.6.3, 1.4_p6, 1.9.5 sys-devel/binutils: 2.15.92.0.2-r10 sys-devel/libtool: 1.5.16 virtual/os-headers: 2.6.8.1-r4 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-march=pentium4 -O2 -pipe -fomit-frame-pointer" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.3/env /usr/kde/3.3/share/config /usr/kde/3.3/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/share/config /usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/ /var/bind /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-march=pentium4 -O2 -pipe -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig ccache distlocks sandbox sfperms strict" GENTOO_MIRRORS="http://distfiles.gentoo.org http://distro.ibiblio.org/pub/Linux/distributions/gentoo" MAKEOPTS="-j3" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.de.gentoo.org/gentoo-portage" USE="X Xaw3d aac acl acpi apache2 apm arts avi bash-completion bcmath berkdb bitmap-fonts bzlib calendar cdparanoia cdr cpdflib crypt cups curl dba dbm dbx dga divx4linux dvd dvdr dvdread emboss encode fastcgi ffmpeg flash foomaticdb fortran ftp gd gdbm gif gmp gnome gstreamer gtk gtk2 gtkhtml icq imagemagick imap imlib innodb iodbc jabber java jpeg kde kerberos lcms ldap libwww mad maildir mbox mcal mhash mime mng motif mozilla mp3 mpeg mysql mysqli ncurses nls nocardbus nptl oci8 ogg oggvorbis openal opengl oss pam pcre pdflib perl phpplotutils png posix ppds python qt quicktime readline samba sapdb sasl sdl session simplexml slang slp snmp soap spl sse ssl svg svga sysvipc szip tcltk tcpd theora tidy tiff tokenizer truetype truetype-fonts type1-fonts unicode usb vhosts vorbis wmf x86 xml xml2 xmlrpc xmms xpm xprint xsl xv xvid zlib userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CBUILD, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS Can you please help us fix this soon or give me a hint, how to solve this temporarily as this has a rather big impact on system operation? regards, Michael I have to correct myself, revdep-rebuild did help, it was my own fault. regards, Michael *** This bug has been marked as a duplicate of 97457 *** Considering that most of us ran "emerge --update world" and had this little bomb dropped on us I think this project needs be masked for its destructive tendencies. |