| Summary: | rebuild of postgresql-ip4r package against new postgresql version | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Pavel Raiskup <praiskup> |
| Component: | postgresql-ip4r | Assignee: | Devrim Gündüz <devrim> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 20 | CC: | devrim, jmlich, praiskup |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | postgresql-ip4r-1.05-9.fc20 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-09-28 00:22:27 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Bug Depends On: | |||
| Bug Blocks: | 1007840 | ||
|
Description
Pavel Raiskup
2013-09-13 13:03:31 UTC
I'll use this bug to rebase ip4r 2.0 extension also. (In reply to Pavel Raiskup from comment #1) > I'll use this bug to rebase ip4r 2.0 extension also. OK, no .. we probably want wait some time before rebase. Created bug #1009468. postgresql-ip4r-1.05-9.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/postgresql-ip4r-1.05-9.fc20 Package postgresql-ip4r-1.05-9.fc20: * should fix your issue, * was pushed to the Fedora 20 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing postgresql-ip4r-1.05-9.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-17076/postgresql-ip4r-1.05-9.fc20 then log in and leave karma (feedback). postgresql-ip4r-1.05-9.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report. |