Bug 101829 - gimp-print does not build
Summary: gimp-print does not build
Keywords:
Status: CLOSED DUPLICATE of bug 101858
Alias: None
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: gimp-print
Version: 3.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Tim Waugh
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-08-07 13:44 UTC by Michael Redinger
Modified: 2007-11-30 22:06 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-02-21 18:58:00 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Michael Redinger 2003-08-07 13:44:29 UTC 
The Taroon gimp-print-4.2.4-5.src.rpm package does not build correctly
on Taroon (everything install) because there are failed dependencies:

error: Failed build dependencies:
        ghostscript-devel is needed by gimp-print-4.2.4-5
        gimp-devel is needed by gimp-print-4.2.4-5

ghostscript-devel is not included in Taroon (but ghostscript is)
gimp and gimp-devel are not included in Taroon

See also bug #101828
Comment 1 Tim Waugh 2003-08-07 13:48:17 UTC 

*** This bug has been marked as a duplicate of 101828 ***
Comment 2 Michael Redinger 2003-08-07 13:52:59 UTC 
Hm, this is not really a duplicate of bug #101828 - note the missing "gimp-devel" 
in this report (as opposed to "gimp-print-devel" 101828).
Reopening it. Feel free to close it again. ;-)
Comment 3 Tim Waugh 2003-08-07 13:55:23 UTC 
Oops, sorry.
Comment 4 Michael Redinger 2003-08-07 13:57:53 UTC 
Forgot one thing:
I suppose I will find some similar bugs (missing build prereqs).
Should I file them against "distribution" or should I use the appropriate
package (and leave it to the maintainer to reassign the bug if needed)?
Comment 5 Bill Nottingham 2003-08-07 20:04:42 UTC 
File them against the package, so we can weed out incorrect/missing
buildprereqs, or incorrectly omitted -devel packages. Once those are verified as
being correct, we can then close the bug appropriately.

*** This bug has been marked as a duplicate of 101858 ***
Comment 6 Red Hat Bugzilla 2006-02-21 18:58:00 UTC 
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.
Note You need to log in before you can comment on or make changes to this bug.