Hi Jean-Michel, hi Mario,
I've checked, and I know what was the problem. We are going to improve
the scripts to prevent this problems in the future.
Could you please open a GGUS ticket to track the problem? I'll fix the
repositories and I'll close the GGUS when it's finished.
Mario, this problem affect also to many other services, introducing a
new version of yaim-core and glite-version. Do you think we should
send a broadcast when I correct the repository?
Thanks,
Pablo
On Mon, Oct 18, 2010 at 9:59 AM, Pablo Guerrero <[log in to unmask]> wrote:
> Hi Jean-michel,
>
> It's true, this was introduced by mistake with the last APEL patch,
> I'm going to check what happened and try to fix it.
>
> Thanks,
>
> Pablo
>
> On Mon, Oct 18, 2010 at 9:49 AM, Jean-Michel Barbet
> <[log in to unmask]> wrote:
>> Hello,
>>
>> Doing yum list updates on a gLite 3.2 CREAM-CE, I was surprised to see
>> updated packages while the meta-package is up to date. I believe this
>> is not normal :
>>
>> yum list updates
>> [...]
>> glite-apel-core.noarch 2.0.13-8 glite-CREAM_updates
>> glite-version.noarch 3.2.3-1 glite-CREAM_updates
>> glite-yaim-core.noarch 4.0.13-2 glite-CREAM_updates
>>
>> The metapackage is : glite-CREAM-3.2.7-2.sl5
>>
>> And the list of RPMs that corresponds to the metapackage
>> http://glite.web.cern.ch/glite/packages/R3.2/sl5_x86_64/deployment/glite-CREAM/3.2.7-2.sl5/glite-CREAM-3.2.7-2.sl5.html
>> tells that the versions of the above RPMs should still be :
>> glite-apel-core 2.0.12-8
>> glite-yaim-core 4.0.12-1
>> glite-version 3.2.2-1
>>
>> Anything wrong ? Or maybe I jumped in the middle of a new release
>> process.
>>
>> Thank you.
>>
>> 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: [log in to unmask]
>> ------------------------------------------------------------------------
>>
>
|