[Starlingx-discuss] Building openstack-helm under OpenSUSE OBS after option serve has been removed from helm fails (work around)
Dominig ar Foll (Intel Open Source)
dominig.arfoll at fridu.net
Tue Jul 23 17:36:21 UTC 2019
On 23/07/2019 16:10, Bailey, Henry Albert (Al) wrote:
> In Centos, openstack-helm is installing this version in mock:
> helm-2.13.1-0.tis.2.x86_64 1560862674 37163874 f8bf2d311350ac6b6b4c3059b16cf54d installed
It's coming. Just a question of time.
> However the spec file we use does not actually specify an upper version value for helm, so presumably if we were to update our rpm repo and pick up a higher version of helm we would likely hit the same issue.
> https://opendev.org/starlingx/upstream/src/branch/master/openstack/openstack-helm/centos/openstack-helm.spec#L43
I am afraid that a solution not using "serve" will be required.
> For now, I'd suggest setting a max version of helm for in your spec file to 2.13 for that BuildRequires
As a work around, I have built an a version 2.13 of helm for 15.0 and 15.1
If the multiOS team wants it, they have to update their meta file to
reflect the following repos referencing.
<repository name="openSUSE_Leap_15.1">
<path project="Cloud:OpenStack:Stein" repository="openSUSE_Leap_15.1"/>
<path project="home:dominig:helm-backport"
repository="openSUSE_Leap_15.1"/>
<path project="openSUSE:Leap:15.1:Update" repository="standard"/>
<path project="openSUSE:Leap:15.1" repository="standard"/>
<arch>x86_64</arch>
</repository>
<repository name="openSUSE_Leap_15.0">
<path project="Cloud:OpenStack:Stein" repository="openSUSE_Leap_15.0"/>
<path project="home:dominig:helm-backport"
repository="openSUSE_Leap_15.0"/>
<path project="openSUSE:Leap:15.0:Update" repository="standard"/>
<path project="openSUSE:Leap:15.0" repository="standard"/>
<arch>x86_64</arch>
</repository>
</project>
--
Dominig ar Foll
Senior Software Architect
Intel Open Source Technology Centre
More information about the Starlingx-discuss
mailing list