Bug 2081099
Summary: | unixODBC-2.3.11 is available | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Upstream Release Monitoring <upstream-release-monitoring> |
Component: | unixODBC | Assignee: | Michal Schorm <mschorm> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | rawhide | CC: | acaringi, hhorak, jstanek, mschorm, odubaj, praiskup, stevenfalco, tgl |
Target Milestone: | --- | Keywords: | EasyFix, FutureFeature, Triaged |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | unixODBC-2.3.11-1.fc36 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2023-04-20 05:23:51 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: |
Description
Upstream Release Monitoring
2022-05-02 18:16:58 UTC
Latest upstream release: 2.3.11 Current version/release in rawhide: 2.3.9-5.fc36 URL: http://www.unixodbc.org/ Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/ More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream. Based on the information from Anitya: https://release-monitoring.org/project/7344/ Is there any status on this update? I see that there is a pull request, but I haven't seen any further activity. KiCad will likely start using unixODBC soon, and the KiCad developers suggested that it would be good if Fedora could update unixODBC to the 2.3.11 release, since it fixes some bugs. Hi Steven, I've got back to the PR, enhanced it, tested a bit more and merged. I've made the builds for - Rawhide: https://bodhi.fedoraproject.org/updates/FEDORA-2022-d36eb9c2bc - F37: https://bodhi.fedoraproject.org/updates/FEDORA-2022-2853d75802 Do you need this update to be merged & built to F36 and F35 too ? Thanks for such a rapid response - it is appreciated! KiCad will use unixODBC both in the official Rawhide repo and in a nightly Copr that is built for F35 through F38. My best estimate is that it would be helpful to have your update in F36, but I think F35 will become obsolete before KiCad will start using unixODBC. So if it is not too much trouble, I'd like to see your update in F36, because that release will still exist for quite a while. It will also help my testing, because my desktop is on F36. FEDORA-2022-d61504a7c1 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-d61504a7c1 FEDORA-2022-d61504a7c1 has been pushed to the Fedora 36 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-d61504a7c1` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-d61504a7c1 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. Looks good, Michal. Thanks for the update! (In reply to Steven A. Falco from comment #8) > Looks good, Michal. Thanks for the update! Thanks for the patience. I've disabled automatic move of the update to the stable repository, to make sure it doesn't break anything to others. I hope more people will come by and leave karma. FEDORA-2022-d61504a7c1 has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report. |