Bug 1301106
Summary: | Package Review: python-ImcSdk | ||
---|---|---|---|
Product: | [Community] RDO | Reporter: | Brian Demers <brdemers> |
Component: | Package Review | Assignee: | hguemar |
Status: | CLOSED NOTABUG | QA Contact: | hguemar |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | Liberty | CC: | apevec, hguemar, karlthered |
Target Milestone: | --- | Flags: | karlthered:
rdo-review+
|
Target Release: | Kilo | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | python-ImcSdk-0.7.2-3.el7 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-01-24 16:00:50 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 1301112 |
Description
Brian Demers
2016-01-22 15:35:56 UTC
rdoinfo pull request: https://github.com/redhat-openstack/rdoinfo/pull/143 Resolves this TODO in the python-ironic-cisco spec https://github.com/openstack-packages/python-ironic-cisco/blob/4ca3dae48b308173c7580f9434dbf3cc00e33208/python-ironic-cisco.spec#L31-L32 Repeating from rdoinfo PR: Python SDK for Cisco Ucs IMC doesn't seem to be directly openstack related, so we shouldn't need to maintain it in openstack-packages and chase its trunk. How frequent are releases, would it be enough to rely on what's published on pypi? Yes, updates should be infrequent. Whats on pypi is fine (that is what I used to submit the fedora package) Ideally, we would just what gets packaged for fedora (on the EPEL branch), but this is a big of a knowledge gap for me. Thoughts? I think we should just keep it in Fedora as it's a general-purpose lib. I'll rebuild it in CBS. Ok, imported in CBS, I dropped the unused BR to python3-devel. Since this is a new dependency, I tagged it straight to release. Please reopen if it doesn't answer your question Works for me, but one more question. How does/when the package get pushed to a repo that the delorean builds will pick up? If it's in CBS and Fedora, so it's already picked up by delorean http://cbs.centos.org/koji/buildinfo?buildID=8296 http://koji.fedoraproject.org/koji/buildinfo?buildID=711044 <= this builds needs to be in stable (I pushed it) Since there's no F22 build, I am rebuilding it into this copr builder but we'll be migrating delorean to F23 so less critical. https://copr.fedorainfracloud.org/coprs/apevec/RDO-Liberty/build/156150/ |