SL6 porting instructions

ETICS project configurations

• emi_B_1_dev :
  • development project configuration: contains sub-systems/components configurations currently 'in work' and which are likely to subsequently be locked and used for a release candidate build
  • NightlyBuilds are enabled with the following shedule: 04:00 (AM)
    • etics-repository.cern.ch/repository/reports/name/emi_B_1_dev_sl6_64/-/reports/reportModules.html
  • NB for 06.11.2011 - 72% successful
  • NB for 13.11.2011 - 75% successful

• emi_R_1_rc :
  • contains tagged configurations for the components scheduled to be released/updated
  • NightlyBuilds are enabled with the following shedule: 12:00 & 22:00:
    • etics-repository.cern.ch/repository/reports/name/emi_R_1_rc_sl6_64/-/reports/reportModules.html

ETICS build instructions

Local build

Always check which is the latest of the client that must be used by looking at EticsCurrentClients.

Configure a local ETICS worker node following these instructions. In order to build succesfully on SL6 you need to use a still unreleased version of the etics-client. It can be installed locally using the following commands:

python etics-client-setup.py --release 1.5.5-3 --volatile etics_3_5_0 --skip-plugins

The --skip-plugins option makes the local build faster, but you won't get any QA metrics out of your build.

Since the sl6_x86_64_gcc446EPEL platform is not automatically recognized by the ETICS client, you will have to set the platform parameter in your user-level etics-client configuration in ~/.etics.conf or the system-level file in $ETICS_HOME/etc/etics.conf to

platform=sl6_x86_64_gcc446EPEL

After the usual workspace setup, you can checkout your configuration:

etics-checkout --config <subsys-config> --project emi --project-config emi_R_1_rc [--enablesudo] --verbose --continueonerror <emi.subsystem>

Use --enablesudo if you want the etics-client to install missing dependencies on your system. Note that if you want the etics-client to be able to install packages on your system, you should be in the sudoers file on the machine without a password set, i.e. something like:

andrea    ALL=(ALL) NOPASSWD: ALL

Otherwise, just install the missing dependencies as listed by the etics-client after a checkout.

You can run a "normal" build with this command:

etics-build --config <subsys-config> --verbose --target postpublish --continueonerror --createsource <emi.subsystem>

In order to run the mock repackaging step use the following command:

etics-build --config <subsys-config> --verbose --target postpublish --continueonerror --repackage=emi-1-sl6-x86_64 <emi.subsystem>

Note that using the --repackage option automatically enables the --createsource option, so there is no need to use it explicitly

Also in this case you need to be in the sudoers file to be able to install mock (if missing), configure a local APT repository and run mock builds.

Remote build

• Checkout command:
  

Figure 1 -WA Checkout Fields

• Build command: to enable Mock repackage, you have to add, after pressing More Options tab, in the Custom Build Options the value "--repackage=emi-1-sl6-x86_64"
  

Figure 2 -WA Build Fields

• Platform & etics-client version selection: as mentioned before, the etics-client version for SL6, the 1.5.5-3, is not yet the default one. In order to use it you have to specify it in the Appen Requirements field, after pressing the More options tab, the value "client_release=1.5.5-3@etics_3_5_0"

Figure 3 -WA Platform and etics-client version selection Fields

Common problems and suggested solutions