Saul: The strategy we have been using for StarlingX is to not allow a change in stx-upstream for a openstack-helm or openstack-helm-infra change unless a corresponding commit is proposed to those upstream projects. Then each time someone in StarlingX upversions our builds to a newer version of openstack-helm and openstack-helm-infra, they remove the stx-upstream patches for all commits that were merged into that version of openstack-helm. Frank -----Original Message----- From: Saul Wold [mailto:sgw@linux.intel.com] Sent: Monday, September 23, 2019 3:05 PM To: starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] MultiOS: why do we build or own Helm and Helm-infra rather than to use th eone provided by the distro? On 9/23/19 9:13 AM, Victor Rodriguez wrote:
On Mon, Sep 23, 2019 at 9:56 AM Penney, Don <Don.Penney@windriver.com> wrote:
Don't we also have a large number of patches to these?
Good point Don : https://opendev.org/starlingx/openstack-armada-app/src/branch/master/o penstack-helm/centos/openstack-helm.spec
Dominig we do have many patches for helm package
Are these backports or have any chance of actually being upstreamed to openstack-helm? Sau!
-----Original Message----- From: Victor Rodriguez [mailto:vm.rod25@gmail.com] Sent: Monday, September 23, 2019 10:44 AM To: Little, Scott Cc: starlingx Subject: Re: [Starlingx-discuss] MultiOS: why do we build or own Helm and Helm-infra rather than to use th eone provided by the distro?
On Mon, Sep 23, 2019 at 8:51 AM Scott Little <scott.little@windriver.com> wrote:
I believe there was a minimum version required to support another package, and CentOS build of that version was not available... at least not at that time.
If is supported now, do you think we could work on using the existing one provided by the distro ?
Scott
On 2019-09-17 11:12 a.m., Victor Rodriguez wrote:
You mean why do we build the RPM : http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/lat est_build/outputs/RPMS/std/helm-2.13.1-0.tis.2.x86_64.rpm ??
On Tue, Sep 17, 2019 at 4:35 AM Dominig ar Foll (Intel Open Source) <dominig.arfoll@fridu.net> wrote:
Hello,
I wonder why StarlingX needs to build locally a version of Helm and Helm Infra. Would it be possible to use the OpenSUSE release ? Release 2.13 and 3.0 are already available. Would any do ?
-- Dominig ar Foll Senior Software Architect Intel Open Source Technology Centre
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discu ss
Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discus s
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss