Bug 1690725
| Summary: | Add nmstate to comps file for release | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | rhel-prp-maitai <rhel-prp-maitai> |
| Component: | releng | Assignee: | Pavel Niahodkin <pniahodk> |
| Status: | CLOSED ERRATA | QA Contact: | Release Test Team <release-test-team-automation> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 8.1 | CC: | fge, jwboyer, pkotvan, pniahodk |
| Target Milestone: | rc | Flags: | pm-rhel:
mirror+
|
| Target Release: | 8.1 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-11-05 22:08:47 UTC | Type: | --- |
| 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: | 1674456 | ||
|
Comment 2
Pavel Niahodkin
2019-03-20 13:24:46 UTC
(In reply to Pavel Niahodkin from comment #2) > Do you have any preferences regarding the group where your package will be > put? Could you elaborate on the `group` you are referring to? Any example? Gris Ge, I'm sorry for not being verbose about that. You can check rhel-8.1.0 compos file here: https://code.engineering.redhat.com/gerrit/gitweb?p=comps.git;a=blob;f=comps-rhel-8.1.0.xml.in;h=0437b84404bc1135c2b75d54a64a4f77c394160b;hb=HEAD If you don't have an access, here's the full list of available comps groups: http://pastebin.test.redhat.com/744351 Hi Pavel Niahodkin, Thanks for the links. The `nmstate` would be `network-tools`. and `python3-libnmstate` would be `codeready-builder`. Verified on RHEL-8.1.0-Snapshot-1.0 -> RHEL-8.1.0-20190806.2 with nmstate-0.0.8-3.el8 and python3-libnmstate-0.0.8-3.el8. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2019:3543 |