How to release a high priority security fix

The following set of instructions shows how to release a high priority security fix that bypasses certification and the standard release process directly to production.

Upload the updated RPMS to the repository

1. Log on to lxb6124 using the glbuild account.

2. Put the RPM(s) to the following places depending on their type

• RPMS build via ETICS (ETICS repository)
  
  Nothing to be uploaded. Make sure that the RPMS have been registered and are available in the repository. For further details consult the ETICS manual.

• RPMS build via gLite (gLite repository)
  
  Depending on the type copy/download them to the following destination
  
  

  noarch	/mnt/glite_repository/packages/R3.0/repository/bin/rhel30/noarch/RPMS
  i386	/mnt/glite_repository/packages/R3.0/repository/bin/rhel30/i386/RPMS

• External RPMS (external dependency repository)
  
  Externals RPMS should go to the following location:
  
  

  /mnt/glite_repository/packages/externals/bin/rhel30/i386/RPMS

Update the release definition

1. Log on to lxb6124 using the glbuild account.

2. Update the production update file.

• Go to the production directory
  
  

  cd /mnt/glite_repository/packages/R3.0/production/

• Update the file 3.0.0-production.rhel30.updates.list
  
  by adding one entry (in one line) at the top - with the following syntax
  
  

  glite glite-XYZ-1.2.3-4.noarch.rpm	for RPMS in the glite repository (both i386 and noarch)
  etics glite-XYZ-1.2.3-4.noarch.rpm	for RPMS in the ETICS repository (both i386 and noarch)
  external my-external-1.2.3-4.noarch.rpm	for RPMS in the external repository (both i386 and noarch)

• Commit the changes to CVS (recommended but not necessary)

Recreate the production APT repository

1. Log on to lxb2042 using the glbuild account.

2. Go to the production APT repository

3. Run the repository creation script

The script will tell you if everything went fine - otherwise have a look at the log file aptCreation.log for details why it failed (most probable reason is a typo in the release definition file (see above)).

Remove the security backup repository (for space reasons)

1. Log on to lxplus using the glbuild account.

2. Remove the old backup repository

Upload the new APT repository

1. Log on to lxb2042 using the glbuild account.

2. Go to the production APT repository

3. Copy the directory rhel30 to the production afs mirror space:

Attention: please make sure that you use the options -rp!!!

Put the repository live

1. Log on to lxplus using the glbuild account.

2. Move the repository to the backup location

3. Move the new repository in place

4. The new repository will become live every hour at XX:30.

-- JoachimFlammer - 21 Dec 2006