Bug 114993
Summary: | printf-style problem | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | d.binderman |
Component: | libungif | Assignee: | Jonathan Blandford <jrb> |
Status: | CLOSED DUPLICATE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 1 | CC: | ddumas |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-02-21 19:01:05 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
d.binderman
2004-02-05 09:56:47 UTC
Even though this is a newer package, the same warning is being generated from the same line in the gifinfo.c file, so i'm going to mark this as a duplicate of the bug from the older package. Though, since you have already dug in and found what's causing the error. You might be able to go a step further and easily provide a patch that fixes this problem by figuring out which variable is suppose to be that missing extra parameter corresponding to image number. I'd tell you to check upstream to see if its fixed at http://prtr-13.ucsc.edu/~badger/software/libungif/ but i can't seem to get through to that site. Instead please try the latest version of this package in the fedora core development tree and create a patch against that if the problem is still present. *** This bug has been marked as a duplicate of 78707 *** >You might be able to go a step further and easily provide a >patch that fixes this problem I would very much like to be able to do this, but I can't. I've found bugs in over 200 Redhat Fedora core packages. I simply don't have the time or resource to fix every bug. I've gone part of the way in finding the obvious bug. Maybe Redhat would be interested in fixing the bugs I've found, maybe even the ones which have been around since Redhat 8.0 and still aren't fixed. >but i can't seem to get through to that site. Nor can I. Changed to 'CLOSED' state since 'RESOLVED' has been deprecated. |