Am Freitag, 21. Dezember 2007 schrieb M9.: > Hi, > > I am looking for yast to be repaired, but it is nearly impossible to > update now, every solution causes another problem atm. > Does anyone know a solution for the Yast2 problem? > After the update yesterday, it does not show when called upon. > even the dos-version does not respond. > > [EMAIL PROTECTED]:~> rpm -qa | grep yast2 > yast2-storage-lib-2.16.6-7 > yast2-pam-2.16.0-24 > yast2-control-center-2.16.0-7 > yast2-backup-2.16.1-3 > yast2-ldap-client-2.16.5-3 > yast2-metapackage-handler-0.7.3-13 > yast2-qt-2.16.9-2 > yast2-pkg-bindings-2.16.7-2 > yast2-firewall-2.15.8-35 > yast2-x11-2.15.11-56 > yast2-printer-2.16.6-7 > yast2-registration-2.16.0-15 > yast2-nis-client-2.16.0-23 > yast2-samba-server-2.16.0-27 > autoyast2-2.16.3-3 > yast2-trans-nl-2.15.12-2 > yast2-slp-2.15.0-59 > yast2-control-center-qt-2.16.0-7 > yast2-bootloader-2.16.3-3 > autoyast2-installation-2.16.3-3 > yast2-hardware-detection-2.16.0-7 > yast2-2.16.18-3 > yast2-irda-2.15.1-122 > yast2-scanner-2.15.5-70 > yast2-ldap-2.15.1-108 > yast2-sound-2.16.1-17 > yast2-kerberos-client-2.16.1-3 > yast2-security-2.15.1-52 > yast2-repair-2.16.2-14 > yast2-tune-2.15.7-51 > yast2-users-2.16.5-3 > yast2-sudo-2.15.3-118 > yast2-update-2.16.1-15 > yast2-trans-stats-2.15.0-46 > yast2-country-data-2.16.4-3 > yast2-core-2.16.16-2 > yast2-nfs-client-2.15.0-52 > yast2-mouse-2.16.0-13 > yast2-ncurses-2.16.7-3 > yast2-xml-2.16.0-10 > yast2-apparmor-2.1-54 > yast2-support-2.15.3-42 > yast2-storage-2.16.6-7 > yast2-ntp-client-2.16.2-9 > yast2-tv-2.16.0-27 > yast2-fingerprint-reader-2.16.2-3 > yast2-installation-2.16.8-2 > yast2-restore-2.16.0-15 > yast2-add-on-2.16.0-22 > yast2-inetd-2.15.1-72 > yast2-perl-bindings-2.16.0-29 > yast2-transfer-2.16.0-4 > yast2-bluetooth-2.15.4-46 > yast2-sysconfig-2.15.3-85 > yast2-packager-2.16.12-3 > yast2-online-update-2.16.6-3 > yast2-network-2.16.17-3 > yast2-samba-client-2.16.1-13 > yast2-mail-2.15.23-34 > yast2-control-center-gnome-2.13.2-127 > yast2-schema-2.15.0-156 > yast2-theme-openSUSE-2.16.1-2 > yast2-runlevel-2.16.0-15 > yast2-country-2.16.4-3 > yast2-iscsi-client-2.16.2-9 > yast2-online-update-frontend-2.16.6-3 > yast2-profile-manager-2.16.0-14 > [EMAIL PROTECTED]:~> > > Anyone sees something out of order here? I've basically the same versions and the ncurses interface worked for me.
The current dependency problem seems to be that there is a update to openldap-2.4 but there are still many packages , which have dependencies on libldap-2.3/liblber-2.3 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
