Re: Updating yum-conf reactivates the nightly updates

2009-09-03 Thread Jon Peatfield

On Thu, 3 Sep 2009, Jean-Michel Barbet wrote:


Hello,

On Aug 19th I updated the OS packages on a SL4.5 server. Recently I
discovered that updating yum-conf had reactivated the nightly yum
updates that I had disabled. Evidence is in the postconfig script :

rpm -q --scripts yum-conf-45-2.SL
postinstall scriptlet (using /bin/sh):
/sbin/chkconfig --add yum
/sbin/chkconfig yum on
/sbin/service yum restart >> /dev/null
[...]

=>  I consider this as potentially dangerous and I am raising the
   alarm signal...

I do not know if this is the same for other versions of SL.


At least with sl53 it doesn't seem to be...

 $ rpm -q --scripts --triggers yum-conf
 
 $ rpm -q yum-conf
 yum-conf-53-3.SL.noarch

however we must have been worried by this at some point since as part of 
our standard nightly cron jobs we have code that does:


 /sbin/chkconfig --level 2345 yum off

and we also replace the /etc/cron.daily/yum.cron file just to be sure :-)

--
/\
| "Computers are different from telephones.  Computers do not ring." |
|   -- A. Tanenbaum, "Computer Networks", p. 32  |
-|
| Jon Peatfield, _Computer_ Officer, DAMTP,  University of Cambridge |
| Mail:  jp...@damtp.cam.ac.uk Web:  http://www.damtp.cam.ac.uk/ |
\/


Re: Updating yum-conf reactivates the nightly updates

2009-09-03 Thread Troy Dawson

Alec T. Habig wrote:

Troy Dawson writes:

It is the same for *every* version of SL.


A suggestion - take a look at the .spec file from yum-cron.  There's
some logic in there you could steal which ensures that the current state
is preserved on upgrade.

Not saying the default for a fresh install should be "off" (as it is in
yum-cron since that was in the Fedora packaging guidelines), just that
upgrades should respect any changes made by the user.  If someone made
the decision to disable this, that decision should be respected. 


Alec

PS - use the current Fedora yum-cron as a baseline for anything, the
EPEL version is frozen at an ancient state to avoid CentOS conflicts.



Just so ya'll know, I didn't mean to be so terse, I'm just currently at 
a place with very poor internet connection, and that was about all I 
could reply with.


I'll take a look at the specs that you are talking about when I get a 
better internet connection.


We will be looking indepth at how we do automatic updates in SL6.  But 
our phillosophy has always been that out of the box, it should do 
automatic updates.  Then if an adminstator is good enough that they know 
what they are doing, there should be a way for them to disable or alter 
the automatic updates.


But you are correct, these last yum-conf updates should not have changed 
whatever you had set in chkconfig.  If we ever have to do this mass 
yum-conf update again, we will have that fixed. When I get to a decent 
internet connection area, I'll investigate and fix up the spec files so 
this will hopefully not happen again.


Thanks
Troy

--
__
Troy Dawson  daw...@fnal.gov  (630)840-6468
Fermilab  ComputingDivision/LCSI/CSI DSS Group
__


Re: Updating yum-conf reactivates the nightly updates

2009-09-03 Thread Alec T. Habig
Troy Dawson writes:
> 
> It is the same for *every* version of SL.

A suggestion - take a look at the .spec file from yum-cron.  There's
some logic in there you could steal which ensures that the current state
is preserved on upgrade.

Not saying the default for a fresh install should be "off" (as it is in
yum-cron since that was in the Fedora packaging guidelines), just that
upgrades should respect any changes made by the user.  If someone made
the decision to disable this, that decision should be respected. 

Alec

PS - use the current Fedora yum-cron as a baseline for anything, the
EPEL version is frozen at an ancient state to avoid CentOS conflicts.

-- 
Alec Habig, University of Minnesota Duluth Physics Dept.
ha...@neutrino.d.umn.edu
   http://neutrino.d.umn.edu/~habig/


Re: Updating yum-conf reactivates the nightly updates

2009-09-03 Thread Troy Dawson

Jean-Michel Barbet wrote:

Hello,

On Aug 19th I updated the OS packages on a SL4.5 server. Recently I
discovered that updating yum-conf had reactivated the nightly yum
updates that I had disabled. Evidence is in the postconfig script :

rpm -q --scripts yum-conf-45-2.SL
postinstall scriptlet (using /bin/sh):
/sbin/chkconfig --add yum
/sbin/chkconfig yum on
/sbin/service yum restart >> /dev/null
[...]

=> I consider this as potentially dangerous and I am raising the
alarm signal...

I do not know if this is the same for other versions of SL.

JM



It is the same for *every* version of SL.

Troy

--
__
Troy Dawson  daw...@fnal.gov  (630)840-6468
Fermilab  ComputingDivision/LCSI/CSI DSS Group
__


Updating yum-conf reactivates the nightly updates

2009-09-03 Thread Jean-Michel Barbet

Hello,

On Aug 19th I updated the OS packages on a SL4.5 server. Recently I
discovered that updating yum-conf had reactivated the nightly yum
updates that I had disabled. Evidence is in the postconfig script :

rpm -q --scripts yum-conf-45-2.SL
postinstall scriptlet (using /bin/sh):
/sbin/chkconfig --add yum
/sbin/chkconfig yum on
/sbin/service yum restart >> /dev/null
[...]

=> I consider this as potentially dangerous and I am raising the
   alarm signal...

I do not know if this is the same for other versions of SL.

JM

--

Jean-michel BARBET| Tel: +33 (0)2 51 85 84 86
Laboratoire SUBATECH Nantes France| Fax: +33 (0)2 51 85 84 79
CNRS-IN2P3/Ecole des Mines/Universite | E-Mail: bar...@subatech.in2p3.fr