https://bugzilla.novell.com/show_bug.cgi?id=224491 jengelh@gmx.de changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|jengelh@gmx.de | ------- Comment #2 from jengelh@gmx.de 2006-11-29 07:35 MST ------- Today/zypper: Exactly. kdm case: see another bug report another time -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

https://bugzilla.novell.com/show_bug.cgi?id=224491 andreas.hanke@gmx-topmail.de changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |andreas.hanke@gmx-topmail.de ------- Comment #5 from andreas.hanke@gmx-topmail.de 2006-11-29 09:15 MST ------- (In reply to comment #0)

# smart upgrade ... Installing packages (1): zypper-0.6.13-5@i586 Requires: hal-0.5.8_git20061106-20@i586 (installed) Required By: kdebase3-SuSE-10.2-84@i586 (installed)

Your system must have been broken before because zypper does not require hal. libzypp does. You must have deleted hal some time ago with --nodeps. There is no way that smart can prompt you for installing hal as a dependency of zypper because hal is not a direct, but an indirect dependency of zypper. zypper is harmless, it contains just 1 binary and 1 shell script and is 500 KB in size. If you dislike the hal dependency, kdebase3-SuSE -> zypper is not the right place to cut dependencies. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

https://bugzilla.novell.com/show_bug.cgi?id=224491 ------- Comment #7 from andreas.hanke@gmx-topmail.de 2006-11-29 14:46 MST ------- The dependency of zypper on hal is inherited from libzypp. As you can see in # ldd -u -r /usr/bin/zypper | grep hal /usr/lib/libhal-storage.so.1 /usr/lib/libhal.so.1 zypper does not use it. This dependency is there only because of pkg-config and libtool. In order to accelerate the progress, it would be really useful to know which particular package you don't want to be pulled in by dependencies. This can help avoiding misunderstandings caused by pasted smartpm. I simply can't believe that you make a bug report about the kdebase3-SuSE -> zypper dependency unless you clearly say so and not leave it up to the reader what the pasted smartom output means. Right now a view onto the dependency chain could look like this: kdebase3-SuSE bash readline ncurses coreutils info libacl libattr pam desktop-data-SuSE dosbootdisk fillup ghostscript-fonts-std aaa_base perl hal-resmgr insserv libacl dbus-1 hal resmgr sed kdebase3 *** kio_slp openslp kdelibs3 *** Mesa libdrm expat xorg-x11-libX11 *** xorg-x11-libXau *** xorg-x11-libXdmcp *** xorg-x11-libXext *** xorg-x11-libs *** glibc filesystem dbus-1 aaa_base insserv pwdutils libxml2 dbus-1-qt3 *** libgcc41 hal aaa_base pwdutils PolicyKit dbus-1-glib expat glib2 libusb libvolume_id pm-utils pm-tools hwinfo insserv sed libpng qt3 *** rpm perl libstdc++41 zlib release-notes susehelp perl htdig info2html recode susehelp_{cz,de,en,es,fr,hu,it} wget yast2-theme-openSUSE zypper And now I really like to know why exactly krpmview should be split from kdebase3-SuSE just because of zypper. zypper is a command-line interface for libzypp, the native (and other than smartpm, supported) package manager of SUSE distributions. It is a package that contains 3 ELF binaries, 1 shell script, 1 man page, 1 gettext catalog, 1 config file and 2 documentation files and is less than half an MB in size. This dependency has not been added overnight; it has been present before and was unnoticed. The only reason why you can see it is that zypper is separate from libzypp. In 10.0 times, when the predecessor of libzypp was called yast2-packagemanager, the binaries that kdebase3-SuSE needs were inside yast2-packagemanager. kdebase3-SuSE, on the other hand, depends on more or less half of the distribution. What about cutting the dependencies at another place, where it actually makes a difference: kdebase3-kdm -> kdebase3-SuSE? Making kdebase3-kdm usable without kdebase3-SuSE would solve this problem much more effectively, and without breaking krpmview. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

https://bugzilla.novell.com/show_bug.cgi?id=224491 ------- Comment #9 from jengelh@gmx.de 2006-11-29 15:11 MST ------- Sorry, missed your last paragraph:

Making kdebase3-kdm usable without kdebase3-SuSE would solve this problem much more effectively, and without breaking krpmview.

Yeah, the 'perfect solution'. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

https://bugzilla.novell.com/show_bug.cgi?id=224491 ------- Comment #11 from jengelh@gmx.de 2006-11-30 16:09 MST ------- I'd like to have a themed kdm though. Without deps at best. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

https://bugzilla.novell.com/show_bug.cgi?id=224491 jengelh@gmx.de changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |VERIFIED -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.