Bug 541542
| Summary: | ocaml-cairo: cairo_ps_surface_set_dpi_REPLACED_BY_cairo_surface_set_fallback_resolution | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Richard W.M. Jones <rjones> |
| Component: | ocaml-cairo | Assignee: | Richard W.M. Jones <rjones> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | low | ||
| Version: | 13 | CC: | fedora-ocaml-list, oandrieu, orion, rjones |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | 1:1.2.0-0.2.gita5c5ee9f.fc13 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | 541427 | Environment: | |
| Last Closed: | 2011-06-02 21:23:16 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: | 541427, 545116 | ||
| Bug Blocks: | |||
|
Description
Richard W.M. Jones
2009-11-26 09:40:36 UTC
Orion, can you attach the test_cairo.ml program to this bug? It's in the comment above - it's one line. Yup, I'm being stupid. This works OK for me: $ echo 'module C = Cairo' > test_cairo.ml $ ocamlfind c -package cairo -linkpkg test_cairo.ml -o test_cairo $ ./test_cairo [no errors] ocaml-3.11.1-5.fc13.x86_64 ocaml-findlib-1.2.5-1.fc13.x86_64 ocaml-cairo-1.2.0.cvs20080301-11.fc12.x86_64 cairo-1.8.8-3.fc12.x86_64 cairo-devel-1.8.8-3.fc12.x86_64 Looks like you have a newer ocaml-cairo. I have: ocaml-cairo-1.0.0-2.fc13.x86_64 (In reply to comment #4) > Looks like you have a newer ocaml-cairo. I have: > > ocaml-cairo-1.0.0-2.fc13.x86_64 Upstream version numbers went backwards, which is why we had to use an epoch. Your ocaml-cairo is actually newer. I upgraded to 1:ocaml-cairo-1.0.0-2.fc13, and now I do see the error. I've raised the issue with upstream. I got a reply from upstream, and basically we messed up the packaging here. The upstream version numbers didn't go back, 1.2.0 is the latest version, and 1.0.0 is an old version. I'll have to sort this out ... I'm building a new package which should fix this: http://koji.fedoraproject.org/koji/taskinfo?taskID=1859347 * Mon Dec 7 2009 Richard W.M. Jones <rjones> - 1:1.2.0-0.1.gita5c5ee9f - So we are wrong, version numbers did NOT roll backwards. - Revert to current git head (a5c5ee9f) which is a pre-release of 1.2.0 (RHBZ#541542). - Replace %%define with %%global. - Patch0 is now upstream. - Checked package with rpmlint - no problems. Grrr unluckily we just hit this issue: https://www.redhat.com/archives/fedora-devel-list/2009-December/msg00230.html This bug appears to have been reported against 'rawhide' during the Fedora 13 development cycle. Changing version to '13'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping This message is a reminder that Fedora 13 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '13'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 13's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 13 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping |