RPM

The OCS can build RPMs, it uses the most complicated and obfuscated way known to humanity.

The build process starts in sbt. It calls a series of scripts copying files from the build machine to a remote server called gsswgbuild. That server runs Linux, CentOS 7, and has the RPM tools to generate it.

To make it run, go to a project like OT and call ocsDist RPM64

sbt
> project app_ot
> ocsDist RPM64

the whole process is very slow, it can take several minutes but at the end you will have an rpn on the application target directory

app/ot/target/ot/2025B.1.1.2/RPM64/ot-2025B.1.1.2-0.x86_64.rpm

Copy this file to sbfyum01 like scp app/ot/target/ot/2025B.1.1.2/RPM64/ot-2025B.1.1.2-0.x86_64.rpm yum@sbfyum-lv1:/usr/yum/repo/rhel/9/testing/x86_64

Pitfalls

Given the complicated process, it can fail in many ways. Here is a list of some known ones.

• It doesn't work for test releases. It fails silently.