From Bugzilla Helper: User-Agent: Mozilla/5.0 Galeon/1.2.6 (X11; Linux i686; U;) Gecko/20020913 Description of problem: update -u currently will do the equivalent of chkconfig --add <package> for any package which gets updated. this isn't really what users want. entries in /etc/init.d/rcN.d should not be added by up2date if they are not already there (nor if they already are, duh). perhaps this is really a rpm -U issue? rpm -i should probably create those entries, but rpm -U probably should not. Version-Release number of selected component (if applicable): up2date-2.8.39-1.7.3 How reproducible: Always Steps to Reproduce: 1.install rh7.3 2.chconfig --del <package> 3.up2date <same package> reinserts the chkconfig softlinks in rcN.d/ Additional info:
Thats a general packaging issue. Installing the packages by hand would do the same thing. Reassigning to the distro component for Red Hat Linux.
that does beg the question, actually. running rpm by hand implies an expectation that things will be freshly installed. when we run up2date, we would rather expect that our configuration will not be corrupted. it may be correct that it is a rpm issue, but it's impact on up2date users is far more serious than it's impact at installation time. i run up2date daily overnight. this is the only way to keep ahead of the script kiddies. with this bug, i need to daily monitor if my rcN.d directories have been corrupted by up2date.