EGEE SA1 Building and Contributing Packages

The primary platform for releasing software is RPM format. Current target platforms are SL4 and SL5 both 32 bit and 64bit.

Packages should pass through the SA1 koji system. https://koji.afroditi.hellasgrid.gr/koji/. This is the only way of getting packages into the SA1 repositories. The previous http://skoji.cern.ch/koji is now dead.

EGEE SA1 Repositories.

There are three repositories per platform, e.g for SL5.

http://www.sysadmin.hep.ac.uk/rpms/egee-SA1/centos5
The release repository contains RPMS that should be used in production. It contains software that documentation is relevant to.
http://www.sysadmin.hep.ac.uk/rpms/egee-SA1/centos5-testing
The testing repository is where the next release to production is prepared. Developers can at times move their packages from devel to testing. However at other times entry to testing may be frozen during final release preparation.
http://www.sysadmin.hep.ac.uk/rpms/egee-SA1/centos5-devel
The devel repository can always be added to dynamically by contributes. At any time there is a very good chance it will not work and should be considered a repository for software development.

More details are available: EGEESA1PackageRepository.

Submitting Packages Through Koji.

There are really few choices here, these are in decreasing preference.

  1. Submit builds from SCM to Koji: First install and setup a koji client. You can then submit builds as
koji build centos5-egee 'svn+http://www.sysadmin.hep.ac.uk/svn/grid-monitoring/trunk/msg/fuse-rpm/#1740'
     
which will then appear in the devel repositories if successful.
  1. Submit a SRPM to Koji: First install and setup a koij client. You can then submit such a SRPM to koji.
koji build centos5-egee yourpackage-1.45-23.el5.src.rpm
      
  1. Provide a SRPM: In this case please just provide the URL to a src.rpm. Someone will then submit the package through koji to make it to the repository.
  2. Provide a .tar.gz file: This will need to be provided with some instructions to allow someone else to right a .spec file for producing RPMS.

After this packages will be available in the -devel repositories.

Moving a Package to Testing from Devel within Koji

Developers can move their build from devel to testing

koji tag-pkg centos4-egee-testing yourpackage-1.45-23.el4
koji tag-pkg centos5-egee-testing yourpackage-1.45-23.el5

after a delay your packages will be available in the testing repository. Please note that at times close to release the testing repository may well be locked and this action will fail with a warning that the repository is locked.

Moving a Package from Testing to Release within Koji

The release admins will do this, you are always locked from doing so. Currently only James and Steve have rights to do this since they have the egee-prod permission.

For a list of packages:

koji tag-pkg centos4-egee yourpackage-1.45-23.el4  otherpackage-2.32.el4
koji tag-pkg centos5-egee yourpackage-1.45-23.el5  otherpackage-2.32.el5

There should also be away to do everything via clone-tag method but I need to check the details.

-- SteveTraylen - 20 May 2009

Edit | Attach | Watch | Print version | History: r10 < r9 < r8 < r7 < r6 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r10 - 2010-03-31 - unknown
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    EGEE All webs login

This site is powered by the TWiki collaboration platform Powered by Perl This site is powered by the TWiki collaboration platformCopyright & by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Ask a support question or Send feedback