Opened 13 years ago

Closed 12 years ago

#152 closed Feature Wish (fixed)

Missing yum repository for RPM snapshot builds

Reported by: Samuli Seppänen Owned by: Samuli Seppänen
Priority: major Milestone: beta 2.3
Component: Packaging Version: OpenVPN git master branch (Community Ed)
Severity: Not set (select this one, unless your'e a OpenVPN developer) Keywords:


Fedora, Redhat, CentOS and many other RPM-based distributions use the Yum package manager to distrubute software. Once RPM snapshots are available, yum repositories should be setup to allow testing the packages more easily.

Change History (4)

comment:1 Changed 13 years ago by David Sommerseth

A reference:

Quick steps - purely guessed:

  • Copy RPMs into a directory on a web server, preferably separated with a separate directory per CPU architecture (x86, i686)
  • install createrepo
  • cd repo root directory and do: createrepo .

Repository config for clients will then be something like:

# file /etc/yum.repos.d/openvpn-testing.repo
name=OpenVPN testing package repository

We could also sign the RPMs. Then we should package our public signing key as an RPM which will place the public key in /etc/pki/rpm-gpg. Then the repo file can be modified with gpgcheck=1. It's also possible then to ship the openvpn-testing.repo in the same RPM. Users would then just need to install this RPM and they're set to start with yum install of openvpn stuff.

It *might* be we also need to create different repos for different distros, especially if we want to support RHEL5 based stuff. Currently Fedora and RHEL6 bases are pretty close, but Fedora moves quickly forward.

comment:2 Changed 13 years ago by David Sommerseth

Quick how-to on signing RPMs:

comment:3 Changed 12 years ago by Samuli Seppänen

Owner: changed from Samuli Seppänen to Samuli Seppänen
Status: newaccepted

Any number of RPM repositories can now be created in automated fashion.

comment:4 Changed 12 years ago by Samuli Seppänen

Resolution: fixed
Status: acceptedclosed

Yum repos now available.

Note: See TracTickets for help on using tickets.