Bug 1920833
| Summary: | Version 2.6.5 is available | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Raphael Groner <projects.rg> |
| Component: | VirtualGL | Assignee: | Gary Gatling <gsgatlin> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | rawhide | CC: | gsgatlin, projects.rg, spotrh |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| URL: | https://src.fedoraproject.org/rpms/VirtualGL/pull-request/2 | ||
| Whiteboard: | |||
| Fixed In Version: | VirtualGL-2.6.5-1.fc33 VirtualGL-2.6.5-1.fc32 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2021-02-06 01:16:51 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: | |||
|
Description
Raphael Groner
2021-01-27 06:09:32 UTC
Hi. So I made a rpm based on the pull request's spec file just to test and tested it tonight and everything seems to work ok. I can't merge the pull request because of conflicts plus I also did not get the VirtualGL-2.6.5.tar.gz source tarball so I'm thinking I can do a commit and just update it and in the changelog leave the last entry as Tom Callaway rather then myself * Wed Jan 20 2021 Tom Callaway <spot> - 2.6.5-1 - update to 2.6.5 But change the date and it would be after the last entry from the last mass rebuild? Would that be an ok way to handle it? Or if I should use my own email and name thats fine also. Just wanted to know best way to proceed. Thanks. You have my permission to use your name and email on the change log if it's simpler. > Or if I should use my own email and name thats fine also. Just wanted to know best way to proceed. Thanks. > You have my permission to use your name and email on the change log if it's simpler. Lovely. That's how community should work. :o) I wondered too where to find the new sources because the CI build failed. FEDORA-2021-a813abeddd has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2021-a813abeddd FEDORA-2021-70b196b863 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2021-70b196b863 FEDORA-2021-a813abeddd has been pushed to the Fedora 33 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-a813abeddd` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-a813abeddd See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2021-70b196b863 has been pushed to the Fedora 32 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-70b196b863` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-70b196b863 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2021-a813abeddd has been pushed to the Fedora 33 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2021-70b196b863 has been pushed to the Fedora 32 stable repository. If problem still persists, please make note of it in this bug report. |