Bug 2148680
| Summary: | [Rebase] Rebase libva to 2.16.0 or higher for RHEL 9.3 | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 9 | Reporter: | Neal Gompa <ngompa13> |
| Component: | libva | Assignee: | Jiri Kucera <jkucera> |
| Status: | CLOSED MIGRATED | QA Contact: | Tomas Pelka <tpelka> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | CentOS Stream | CC: | brandon.johnson, bstinson, carl, cschalle, davide, jwboyer, michel, ndegraef, ovasik, tdawson, tpelka |
| Target Milestone: | rc | Keywords: | MigratedToJIRA, Triaged |
| Target Release: | --- | Flags: | pm-rhel:
mirror+
|
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Rebase: Bug Fixes and Enhancements | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2023-09-21 22:43:35 UTC | Type: | Component Upgrade |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Neal Gompa
2022-11-27 02:51:04 UTC
Merge request proposed: https://gitlab.com/redhat/centos-stream/rpms/libva/-/merge_requests/4 Hey Niels, can you help unstick this please? Also, I just bumped this MR to 2.17.0 since it apparently came out a while ago and is in Fedora too... Removing needinfo on me. The associated team said they will try to take a look at getting this in for 9.3, the ball is in their court now :-) Friendly ping? I've bumped the MR to libva 2.19.0 since that's been around for a while in Fedora now... My MR is still stuck unreviewed, so I'm guessing it's going to slip again? Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug. This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there. Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information. To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like: "Bugzilla Bug" = 1234567 In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information. |