Description of problem: In case the package perl-Schedule-Cron-Events will be recognized as redundant on Satellite 5.3.0 (BZ #492283) and will be removed from the compose, there will be another non-required package: perl-Set-Crontab to consider. Otherwise this BZ has no relevance. Version-Release number of selected component (if applicable): Satellite-5.3.0-RHEL5-re20090323.0 on i386 perl-Schedule-Cron-Events-1.8-15.el5 perl-Set-Crontab-1.02-3.el5.noarch.rpm How reproducible: Deterministic. (After BZ #492283 is solved) Steps to Reproduce: 1. Install Satellite 5.3.0 and remove perl-Schedule-Cron-Events package according to BZ #492283. 2. Run rpm -q perl-Set-Crontab, check that the package perl-Set-Crontab is installed. 3. Run rpm -e perl-Set-Crontab. 4. Run rpm -q perl-Set-Crontab again, check that it's now been removed. Actual results: Package perl-Set-Crontab is installed but it is not required by anything in the Satellite, so it can safely be removed. Expected results: Either the package should be Required by some other package, or it should not be on the compose.
request to remove this package from iso was sent to rel eng, ticket 38458
mass move to onqa
# rpm -q perl-Schedule-Cron-Events package perl-Schedule-Cron-Events is not installed # rpm -q perl-Set-Crontab perl-Set-Crontab-1.02-3.el5 perl-Set-Crontab is still present, and perl-Schedule-Cron-Events was removed, so this unnecessary package redundancy still exists. Moving to FAILS_QA, tested on 530-re20090403.2.
resubmitted ticket #39136 to remove these rpms from the sat 530 composes
# rpm -q perl-Set-Crontab package perl-Set-Crontab is not installed Moving to VERIFIED, tested on 530-re20090409.1.
# rpm -q perl-Set-Crontab package perl-Set-Crontab is not installed RELEASE_PENDING from 7/24 build.
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHEA-2009-1434.html