You can only deploy Opkg packages to a local repository that has been created with the Opkg Package Type.
You can download packages from a local or a remote Opkg repository.
To create a new local repository that supports Opkg, in the Administration module, go to Repositories | Repositories | Local and set the Package Type to Opkg.
Artifactory supports the common Opkg index scheme which indexes each feed location according to all ipk packages in it.
To deploy a Opkg package to Artifactory, go to the Artifactory Repository Browser and click the icon.
Select your Opkg repository as the Target Repository, and upload the file you want to deploy.
After you deploy the artifact, you need to wait about one minute for Artifactory to recalculate the repository index and display your upload in the Repository Browser.
You can download ipk packages from Local Opkg Repositories as described above, or from Remote Repositories specified as supporting Opkg packages.
To specify that a Remote Repository supports Opkg packages, set its Package Type to Opkg when it is created.
You can either point the remote to a specific feed (location of a Packages file), i.e.
Or you can specify some base level and point your client to the relevant feeds in it i.e. url is
http://downloads.openwrt.org/chaos_calmer/15.05/ and your
opkg.conf file has the entry
Note that the index files for remote Opkg repositories are stored and renewed according to the Retrieval Cache Period setting.
As there is no "release" of the Opkg client, to support gpg signature verification and basic HTTP authentication that are provided by Artifactory it has to be compiled with the following options:
For example, to compile Opkg on Ubuntu to support these you can use:
# Download opkg release (latest when this was written was 0.3.1): wget http://downloads.yoctoproject.org/releases/opkg/opkg-0.3.1.tar.gz tar -zxvf opkg-0.3.1.tar.gz # Install compilation dependencies: apt-get update && apt-get install -y gcc libtool autoconf pkg-config libarchive13 libarchive-dev libcurl3 libcurl4-gnutls-dev libssl-dev libgpgme11-dev # Compile Opkg(compile with curl to support basic auth, and with gpg support for signature verification): # Note: if there's no configure script in the release you downloaded you need to call ./autogen.sh first ./configure --with-static-libopkg --disable-shared --enable-gpg --enable-curl --prefix=/usr && make && sudo make install
Each Opkg feed corresponds to a path in Artifactory where you have chosen to upload ipk packages to. This is where the Packages index is written.
For example, you can add each such feed to your
opkg.conf (default location is /
etc/opkg/opkg.conffile) with entries like:
src artifactory-armv7a http://prod.mycompany:8080/artifactory/opkg-local/path/to/my/ipks/armv7a src artifactory-i386 http://prod.mycompany:8080/artifactory/opkg-local/path/to/my/ipks/i386
Artifactory uses your GPG public and private keys to sign and verify Opkg package indexes (note that Artifactory signs repository metadata, not packages).
To learn how to generate a GPG key pair and upload it to Artifactory, see Managing Signing Keys.
Once you have GPG key pair, to have Opkg verify signatures created with the private key you uploaded to Artifactory, you need to import the corresponding public key into Opkg's keychain (requires gnupg).
opkg-key add key.pub
mkdir -p /usr/etc/opkg/gpg opkg-key add key.pub cp -R /etc/opkg/gpg/* /usr/etc/opkg/gpg
After the key is imported you need to add the
check_signature option in your
opkg.conf file by adding the following entry:
option check_signature true
If resolving fails with the following errors:
If you need to access a secured Artifactory server that requires a username and password, you can specify these in your
opkg.conf file by adding the 'http_auth' option:
option http_auth user:password
You can use your encrypted password as described in Using Your Secure Password.
The Artifactory REST API provides extensive support for signing keys and recalculating the repository index as follows: