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

Re: source for os 3.2

Added the corresponding source repos to the repos I used to get OpenShift, yet the package declared in the RPM info isn't available.
Any ideas?
[root alan-lnx ~]# rpm -q --info atomic-openshift-node-
Name        : atomic-openshift-node
Version     :
Release     : 1.git.0.a4463d9.el7
Architecture: x86_64
Install Date: Tue 24 May 2016 08:51:40 PM EDT
Group       : Unspecified
Size        : 1609
License     : ASL 2.0
Signature   : RSA/SHA256, Wed 11 May 2016 05:36:07 PM EDT, Key ID 199e2f91fd431d51
Source RPM  : atomic-openshift-
Build Date  : Wed 11 May 2016 12:30:25 PM EDT
Build Host  : x86-034.build.eng.bos.redhat.com
Relocations : (not relocatable)
Packager    : Red Hat, Inc. <http://bugzilla.redhat.com/bugzilla>
Vendor      : Red Hat, Inc.
URL         : https://github.com/openshift/origin
Summary     : Origin Node
Description :
Origin Node
[root alan-lnx ~]# yum install atomic-openshift-
Loaded plugins: langpacks, product-id, search-disabled-repos, subscription-manager
No package atomic-openshift- available.
Error: Nothing to do

On Mon, Jun 13, 2016 at 4:30 PM, Jason DeTiberus <jdetiber redhat com> wrote:
On Mon, Jun 13, 2016 at 7:08 PM, Seth Jennings <sjenning redhat com> wrote:
> It corresponds to the this commit:
> https://github.com/openshift/origin/commit/a4463d9

Not exactly, the atomic-openshift packages are generated from an
internal repository that continually merges from the origin repo.

> If you do an 'oc version' you (might?) see the short git commit id in
> the version string.
> Also the full name of that package is
> atomic-openshift-, which also
> contains the short git commit id.
> On Mon, Jun 13, 2016 at 5:55 PM, Alan Jones <ajones diamanti com> wrote:
>> I'm running with the OpenShift RPMs that have the number for
>> master and node.
>> Is there a tag in the OpenShift origin on git hub that corresponds to this?

There is not. The tags for the enterprise builds are maintained in an
internal repo.

>> Is it possible to get the exact source that was used?

Yes, through the shipped source rpm packages.

Jason DeTiberus

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