From: Alan Jonckheere [jonckheere@fnal.gov]
Sent: Monday, November 11, 2002 4:50 PM
To: Harry Melanson
Cc: Terry Wyatt
Subject: Re: frozen builds?

I *wish* the tmp/ directory was empty for a frozen release, but it's
not, not even close.

  ls -ld $SRT_PUBLIC_CONTEXT/rcpdb/*
For a non-frozen build there will be two directories. These are renamed
*.save and replace with sym links pointing to ../rcpfiledb during the
freeze. Also, to check, 
  ls -l $SRT_PUBLIC_CONTEXT/rcpfiledb
must point to a directory of the same name as the release, *not* the
preceding one.

Another way, that you can use from offsite:
  setup upd
  upd list -aK+ D0RunII -q dist | sort
will list all the frozen releases. If it's there, it's frozen.
  upd list -aK+ D0RunII-bin <version>
will then show you the binary parts. The one you are interested in must
be there. There are normally 4 independent freezes that happen. So you
need to check that the one you need is done + the -q dist part.

NOTE: the rcpdb is frozen very early in the release, the creation and
declaration of the tar files at the very end. For use locally, it's the
rcpdb freeze that matters. For remote use it's the tarfile creation.

Alan



Harry Melanson wrote:
> 
> I'm not sure.  Alan showed me how to know when the RCP system is frozen, but
> more goes on before the release is fully frozen.
> 
> Al - can you write a paragraph that I can include?
> 
> H
> 
> > -----Original Message-----
> > From: Terry Wyatt [mailto:twyatt@fnal.gov]
> > Sent: Monday, November 11, 2002 3:13 PM
> > To: Harry Melanson
> > Subject: frozen builds?
> >
> >
> > Hi Harry,
> >   What is the easiest way to determine whether or not a particular release
> > is frozen?  (Is is that the ./tmp directory is empty?)  Whatever, it would
> > be good to add that information to the "Freezing a release" section of:
> > http://www-d0.fnal.gov/computing/algorithms/howto/howtousereleases.html
> >    Cheers, Terry.
> >
> >