|Summary:||inn news daemon installed in desktop installation|
|Product:||[Retired] Red Hat Public Beta||Reporter:||Michael Wardle <michael.wardle>|
|Component:||comps||Assignee:||Tim Powers <timp>|
|Status:||CLOSED WORKSFORME||QA Contact:||Brock Organ <borgan>|
|Fixed In Version:||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|Last Closed:||2003-01-13 22:24:18 UTC||Type:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Cloudforms Team:||---||Target Upstream Version:|
Description Michael Wardle 2003-01-13 15:32:14 UTC
Description of problem: I just performed a "Desktop" class install of Red Hat Linux 8.0.92 and added a couple extra packages under the desktop and development categories as well as checked the windows connectivity category to get samba installed. I was surprised to see that the news daemon, innd, had also been installed. How reproducible: Haven't tried. Steps to Reproduce: 1. Perform a Desktop class installation of Red Hat Linux 2. Add some packages from the KDE, Windows Server, Development, and Graphical Internet groups Actual results: innd is installed. Expected results: innd is not installed as I had not specified the "news server" group or anything else obviously related to a news server. Additional info: rpm -q --whatdepends inn returns an error (it seems the --whatdepends flag is gone). I am unable to start the graphical package manager to confirm which groups I selected.
Comment 1 Michael Wardle 2003-01-13 16:21:14 UTC
rpm --query --whatrequires inn lists no packages, so it will probably not have been installed as a dependency. Perhaps it's somehow related to the graphical internet category.
Comment 2 Michael Fulbright 2003-01-13 21:42:41 UTC
This is a comps of packaging issue.
Comment 3 Tim Powers 2003-01-13 22:24:18 UTC
It's not a comps issue, the only package which requires inn is inn-devel (you can see this by running "rpm -q --redhatrequires inn") I have performed a default desktop GNOME/KDE install and inn is not installed. Perhaps you inadvertantly selected inn. If you are able to reproduce this please reopen the bug. Tim