Project

General

Profile

Actions

Bug #6685

closed

foreman-selinux left installed after "yum remove foreman forman-proxy"

Added by Jorick Astrego over 9 years ago. Updated about 8 years ago.

Status:
Rejected
Priority:
Low
Assignee:
-
Category:
RPMs
Target version:
-
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

I remove foreman and foreman-proxy through yum and the foreman-selinux package remains installed. This gave me dependency problems later on.

rpm -qa|grep foreman
foreman-selinux-1.6.0-0.develop.201406261522git5532684.el6.noarch


Related issues 1 (0 open1 closed)

Related to Packaging - Feature #6901: foreman-cleanup commandRejectedActions
Actions #1

Updated by Dominic Cleal over 9 years ago

  • Project changed from Foreman to Packaging
  • Category changed from 21 to RPMs
  • Status changed from New to Need more information
  • Difficulty deleted (trivial)

I don't follow what problem this could give you? foreman-selinux isn't a sub-package or anything, just yum remove it too.

Actions #2

Updated by Jorick Astrego over 9 years ago

Yes it is a trivial issue. I ran into problems when testing different versions, the foreman-selinux package broke the rpm dependencies.

When I remove foreman I expect all rpm dependencies to be removed, so normally I would do "yum remove foreman foreman-proxy" and not "yum remove foreman foreman-proxy foreman-selinux"

As I said not a big issue but is there a reason for the current behaviour?

Actions #3

Updated by Dominic Cleal over 9 years ago

Removing any package from yum will never remove its dependencies, and foreman-selinux is a complementary package rather than a dep (or vice versa). I'm not sure that even making it a dependency of foreman would cause it to be removed - you'd probably just want to do "yum remove foreman\*" instead.

Actions #4

Updated by Jorick Astrego over 9 years ago

I've submitted Feature #6901 to explain better.

Actions #5

Updated by Dominic Cleal over 9 years ago

Actions #6

Updated by Tomer Brisker about 8 years ago

  • Status changed from Need more information to Rejected

Closing this as this is expected rpm behavior as explained by Dominic.
Leaving related RFE open for adding a tool to automate this.

Actions

Also available in: Atom PDF