Subject: | |
From: | |
Reply To: | |
Date: | Tue, 28 Jul 2009 15:33:09 +0800 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
Isn't this somewhat misconceived?
Last time I was responsible for maintaining software for a large
employer, the rule was we'd install maintenance when and if we need it.
Since then, I gather Big Corp's preference has to been to do as above,
but apply all maintenance regularly (but not necessarily often), and
then trot the whole shebang through QA?
Is there something I misunderstand?
I was completely unaware of this package, until I began to wonder who'd
been interfering with my system at hours when I'm in bed.
I really really do not want changes I haven't agreed to to systems I
care for.
We've all heard the story, "But I haven't changed a thing."
We all take it with a grain of salt.
It seems that removing this isn't so straightforward either:
08:54 [summer@bobtail ~]$ sudo yum remove yum-autoupdate
Password:
Loaded plugins: downloadonly, kernel-module, priorities, versionlock
Setting up Remove Process
Resolving Dependencies
--> Running transaction check
---> Package yum-autoupdate.noarch 5:1-1.SL set to be erased
--> Processing Dependency: yum-autoupdate for package: yum
--> Processing Dependency: yum-autoupdate for package: yum
--> Running transaction check
---> Package yum.noarch 0:3.2.19-25.sl set to be erased
--> Processing Dependency: yum >= 2.4 for package: mock
--> Processing Dependency: yum >= 3.2.19-16 for package: yum-utils
--> Processing Dependency: yum >= 3.0 for package: yum-downloadonly
--> Processing Dependency: yum >= 3.0 for package: yum-priorities
--> Processing Dependency: yum >= 3.0 for package: yum-versionlock
--> Processing Dependency: yum >= 3.2.5-2 for package: pirut
--> Running transaction check
---> Package yum-downloadonly.noarch 0:1.1.16-14.el5 set to be erased
---> Package mock.noarch 0:0.9.14-1.el5 set to be erased
---> Package yum-utils.noarch 0:1.1.16-14.el5 set to be erased
---> Package pirut.noarch 0:1.3.28-13.sl set to be erased
---> Package yum-priorities.noarch 0:1.1.16-14.el5 set to be erased
---> Package yum-versionlock.noarch 0:1.1.16-14.el5 set to be erased
--> Finished Dependency Resolution
Beginning Kernel Module Plugin
Finished Kernel Module Plugin
Dependencies Resolved
===============================================================================
Package Arch Version Repository
Size
===============================================================================
Removing:
yum-autoupdate noarch 5:1-1.SL installed
22 k
Removing for dependencies:
mock noarch 0.9.14-1.el5 installed
382 k
pirut noarch 1.3.28-13.sl installed
1.4 M
yum noarch 3.2.19-25.sl installed
3.1 M
yum-downloadonly noarch 1.1.16-14.el5 installed
4.6 k
yum-priorities noarch 1.1.16-14.el5 installed
13 k
yum-utils noarch 1.1.16-14.el5 installed
189 k
yum-versionlock noarch 1.1.16-14.el5 installed
9.7 k
Transaction Summary
===============================================================================
Install 0 Package(s)
Update 0 Package(s)
Remove 8 Package(s)
Is this ok [y/N]: n
Exiting on user Command
Complete!
--
Cheers
John
-- spambait
[log in to unmask] [log in to unmask]
-- Advice
http://webfoot.com/advice/email.top.php
http://www.catb.org/~esr/faqs/smart-questions.html
http://support.microsoft.com/kb/555375
You cannot reply off-list:-)
|
|
|