[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

[atomic-devel] Looking for stability when composing trees

We are evaluating Atomic Host, but our development has been knocked on its ear several times by upstream changes to Atomic Host and friends. We need a way to compose trees and be assured that we are getting a specific, already tested collection of base packages.

Based on how we accomplished this in our existing build environment using 'yum', we have done experiments with specifying versions for packages in our treefiles hoping to force 'rpm-ostree compose tree' to pull specific versions, but got this error:

Downloading metadata: 100%
error: No package 'emacs-24.3-18.el7.x86_64' found

Is there a way to do this?

If this is the wrong place for questions like this, please point me in the right direction.

Thanks in advance,

Mark Dyer

For what it is worth we are using CentOS on x86_64. 
the compose command line looks like this:

rpm-ostree compose --repo=/srv/repo tree --proxy= --add-metadata-string=version=3.20160701.141806-hw centos-atomic-host-abc.json

The specified tree file includes the vanilla centos-atomic-host.json file, defines 'osname' and 'ref' and has 

packages": ["emacs-24.3-18.el7.x86_64"]

If more information would be useful, please let me know what you need.

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]