Jeff if you know how to use CVS (or if you want you can use our
fantastic cgi)
you can create a diff between tag and your chnage log is made.
So i do it for you :
export CVSROOT=:pserver:[log in to unmask]:/cvs/lcgdeploy
cvs co lcg2
cd lcg2/rpm_list/
cvs diff -r LCG-2_3_0 -r LCG-2_3_1 > Changelog
and you can clean it after with a cat Changelog | sort -u and/or play
with it.
For details read rhe release note.
See you Lp
On 7 mars 05, at 11:42, Jeff Templon wrote:
> Hi,
>
> Is there an LCG-wide ChangeLog file? This would be very handy for
> discovering what has changed between releases, for example changed RPM
> dependencies.
>
> apt-get and yum are excellent tools, but they are no substitute for
> being explicit about what has changed in a release. even if alternate
> RPM installations are not directly supported, there should be a clear
> and accurate record of what's been changed from release to release
> (without each site having to make their own CVS diff and study the
> results).
>
> J "574 would have been 852 if I had been here" T
>
> On Mar 7, 2005, at 11:00, Louis Poncet wrote:
>
>> It why we prefer to use (and proide the support) for apt-get and yum.
>> You don't need to touch anything it will work by itself.
>> If you need a local mirror you can use our script repgen.pl in the
>> folder server of yaim.
>>
>> http://grid-deployment.web.cern.ch/grid-deployment/documentation/Apt-
>> Yum-Repositories
>>
>> It will be put in the wiki wiki pretty soon the be a part of the
>> documentation.
>>
>> Lp
>>
>> On 7 mars 05, at 10:06, David Groep wrote:
>>
>>> Hi all,
>>>
>>> When upgrading to LCG2.3.1 we found an unexpected new dependency for
>>> the
>>> RB machine. This will break the system for everyone that will try to
>>> 'just upgrade' the RPMs in place and leave the configuration
>>> unchanged
>>> as
>>> was advertized in the release notes for LCG2.3.1 :-(
>>>
>>> On the RB, the edg-replica-manager client tools need to be installed
>>> for match making, but the new version of the edg-replica-manager rpm
>>> has
>>> an new dependency now on "lcg_util", which in turn triggers
>>> dependencies
>>> on CASTOR-client, LFC-client, GFAL-client and CGSI_gSOAP_2.3.
>>>
>>> So, for those of you who tried to use html2updates to have the RPMs
>>> updated
>>> from (a mirror of) the LCG2.3.1 repository, you will need to add
>>> these
>>> dependencies explicitly in the configuration of the RB machine:
>>>
>>>
>>> "/software/packages"=pkg_repl("CGSI_gSOAP_2.3","1.1.3
>>> -2_sl3","i386");
>>> "/software/packages"=pkg_repl("GFAL-client","1.4.0-1_sl3","i386");
>>> "/software/packages"=pkg_repl("LFC-client","1.0.1-1_sl3","i386");
>>>
>>> "/software/packages"=pkg_repl("CASTOR-client","1.7.1.5
>>> -1.longname","i386");
>>> "/software/packages"=pkg_repl("lcg_util","1.1.0-1_sl3","i386");
>>>
>>> and then have these updated using the result of
>>>
>>> $QUATTORDIR/bin/html2updates.pl \
>>> --name=lcg231 \
>>> --url=http://grid-deployment.web.cern.ch/grid-deployment/download/
>>> RpmDir_i386-sl3/i386-sl3-LCG-2_3_1
>>>
>>> The rest seems to work OK (on the worker nodes there was already a
>>> dependency on lcg_utils and the rest.
>>>
>>> This problem will hold for everyone who explicitly needs to install
>>> RPMs and
>>> wants to know what is installed on which machine, so it may be of
>>> interest
>>> to other on the ROLLOUT list as well....
>>>
>>> Cheers,
>>> DavidG.
>>>
>>> PS: also the semantics have changed in the 'minor upgrade', as Simone
>>> already pointed out.
>>>
>>> --
>>> David Groep
>>>
>>> ** National Institute for Nuclear and High Energy Physics, PDP/Grid
>>> group **
>>> ** Room: H1.56 Phone: +31 20 5922179, PObox 41882, NL-1009DB
>>> Amsterdam
>>> NL **
>>>
>> --
>> Louis Poncet
>> Where: Bat28-R-003 CERN
>> CH-1211 Geneve 23
>> Mail : [log in to unmask]
>> Phone: +41(0)227.674.231
>> LAL / IN2P3 / CNRS / CERN
>> Problem >> RTFM then google it !
>>
--
Louis Poncet
Where: Bat28-R-003 CERN
CH-1211 Geneve 23
Mail : [log in to unmask]
Phone: +41(0)227.674.231
LAL / IN2P3 / CNRS / CERN
Problem >> RTFM then google it !
|