David Timms wrote: > Mason wrote: > >> What can I do to make it happen? > > Help the maintainer, by testing the proposed fix yourself with an rpmbuild: > > 1. yum downloader --source name-of-package(or parent package) > 2. extract the rpm > 3. test your rpmbuild capability works with the existing packages as is > 4. open up the .spec > 5. bump the release part > 6. add a comment describing the action you are taking > 7. add a patch from elsewhere to the patch file definition > 8. add the apply patch command to the %prep section > 9. rpmbuild -ba the-package > 10. install the built package > 11. test the application > 12. when you are sure that the fix works and doesn't introduce other > issues, make a diff of the spec ot the original > 13. post the spec patch and the actual patch to the bug. indicate that > this has successfully built and been running, perhaps with some stats > eg: a couple of runs of before and after: > - time applicationname > > Much more on package development on the fedoraproject wiki, just ask if > you are having trouble... For the record, SUSE quickly fixed the problem, using the --disable-system-cairo solution. https://bugzilla.novell.com/show_bug.cgi?id=622375#c13 The SUSE package maintainer wrote in comment 9: > Thanks for checking this out. There is/was another issue which would turn up > when we use the internal cairo. > This is basically sorted out and I'll drive switching to internal cairo asap > (either 11.4 or even for security updates given this bugreport). Is anyone aware of any potential issue when using Mozilla's private libcairo on Fedora 13? -- Regards. -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
