Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: Review Request: yum-cron - get yum updates via a cron job https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=244894 ------- Additional Comments From grdetil@xxxxxxxxxxxxxxxxx 2007-06-20 13:46 EST ------- The old preun script was doing the right thing in only doing a "chkconfig --del" on a full uninstall, not on an update. The problem stemmed from the fact the init script name changed, which is an exceptional condition, an not something the writer of the old preun script could have foreseen. I think in other similar cases, when the init script name changes, the package name changes too, and the new one is set up to obsolete the old one, so the old one gets fully uninstalled. In this case, as it's a simple update of the same package, I think the only thing you can do is check in the pre script to see if it's an upgrade ($1 -gt 1) and then remove (or rename) the lockfile and chkconfig --del yum. Renaming, rather than removing, the lockfile will ensure the service keeps running after the name change. The "condrestart" in the post script didn't work on the upgrade from 0.1-1 to 0.2-2, again because of the name change of the lockfile. -- Configure bugmail: https://bugzilla.redhat.com/bugzilla/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. _______________________________________________ Fedora-package-review mailing list Fedora-package-review@xxxxxxxxxx http://www.redhat.com/mailman/listinfo/fedora-package-review