-- On 2008-08-19 +0100 at 21:40:04 Jon Peatfield wrote --

> On Tue, 19 Aug 2008, FRANCHISSEUR Robert wrote:
> 
> ><snip>
> > openssh-3.9p1-8.SL.4.22      from sl-base
> 
> This is from the sl-contrib repo, I don't understand why it is showing up 
> as sl-base...
> 
> ><snip>
> 
> What does running:
> 
>   yum -d 1 list openssh
> 
> show?  For me on sl4x it shows:
> 
> Installed Packages
> openssh.x86_64                           3.9p1-8.RHEL4.24       installed
> 

       I got :

         yum -d 1 list openssh
       Installed Packages
       openssh.x86_64                           3.9p1-8.SL.4.22        installed       
       Available Packages
       openssh.x86_64                           3.9p1-8.RHEL4.24       sl-errata       
       


> but if I enable sl-contrib I also get the sl one, e.g.
> 
> $ yum --enablerepo=sl-contrib -d 1 list openssh
> Installed Packages
> openssh.x86_64                           3.9p1-8.RHEL4.24       installed
> Available Packages
> openssh.x86_64                           3.9p1-8.SL.4.22        sl-contrib
> 

       I am sure sl-contrib is not enabled ( I check many times) 
       but strange enough, enabling sl-contrib I only got:

         yum --enablerepo=sl-contrib -d 1 list openssh
       Installed Packages
       openssh.x86_64                           3.9p1-8.SL.4.22        installed       
       
       So investigating furter I finaly found that when adding our local
       repo in sl.repo I did a bad copy paste :-(( 

[sl-base]
name=SL 4 base
baseurl=ftp://distrib-coffee.ipsl.jussieu.fr/pub/linux/scientific-linux/45/$basearch/SL/RPMS/
        http://distrib-coffee.ipsl.jussieu.fr/pub/linux/scientific-linux/45/$basearch/contrib/RPMS/
                                                                                      ======= 
        ...
        which I didn't notice for almost one month I was checking everything ...

> Of course as far as rpm/yum are concerned 'SL' counts as newer than 'RHEL' 
> so if you have sl-contrib enabled it will be preferred and so count as a 
> newer update - even it it isn't really newer.
> 
> For reasons very like this in the scripts we run to do yum updates we have 
> stuff like:
> 
> ...
>   $yumopts .= ' --disablerepo=\'*\' --enablerepo='.$stdrepos;
> ...
>   system ("yum $yumverb -y $yumopts update");
> ...
> 
> so we don't get surprised if a repo got turned on - usually just to test 
> something, we rarely *intentionally* permanently enable any other than the 
> ones we consider 'standard'.
> 

       That's indeed a very good idea !

       Thank's a lot for your answer.

-- 
                 Best regards,
                               Robert FRANCHISSEUR

 ____ Apollo_gist :-)_______________________________________________
| Robert FRANCHISSEUR                                               |
| Laboratoire de Météorologie Dynamique -                  C.N.R.S. |
| Equipe "R.A.M.S.E.S." -       UPMC       -   Tour 45-55 3ème 315C |
| Boite 99 - 4, place Jussieu        F-75252 PARIS CEDEX 05  FRANCE |
| Phone  : +33 (0)1 44 27 73 87          fax : +33 (0)1 44 27 62 72 |
| e-mail : robert at lmd . jussieu . fr   http://www.lmd.jussieu.fr |
 -------------------------------------------------------------------