Bug 31381 - a conflict with another package
Summary: a conflict with another package
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: gd
Version: 7.1
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Phil Knirsch
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-03-10 23:28 UTC by Michal Jaegermann
Modified: 2015-03-05 01:09 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2001-03-16 00:07:23 UTC
Embargoed:


Attachments (Terms of Use)

Description Michal Jaegermann 2001-03-10 23:28:16 UTC
Programs supplied by 'gd-progs' provide version 0.60 of these programs,
while 'libwmf' from Powertools, required for conversion of files from
M$-Word ('wv' suite), has version 0.51 of these scripts and much more
of other stuff.  These packages should be coordinated and probably
'libwmf' made dependent on 'gd-progs'.

Comment 1 Phil Knirsch 2001-03-15 18:17:08 UTC
Hm... I've just tried these programs and they all work fine, even with the 'new'
libgd (which we actually have been at 1.8.x for quite a while now).

I've converted some .doc files and some .wmf files successfully, so i don't
really see your point here.

If you could provide some more details on WHAT exactly is failing and
reproducible examples that'd be great.

Read ya, Phil

Comment 2 Michal Jaegermann 2001-03-16 00:07:19 UTC
What about a recent entry in Changelog for 'libwmf' in the latest rawhide
which says "fix conflicts with gd-progs (Bug #29369)"?

Besides this report did not say that thing fail but only that two different
packages supply the same thing (libwmf an older version).

Comment 3 Phil Knirsch 2002-01-24 13:32:25 UTC
As powertools has been discontinued and we don't ship libwmf anymore since 7.2
i'll close this bug as a 'WONTFIX' as the corresponding conflicting package is
no more and the wmf specific apps coming with gd are the ones required for it's
operation (graphics conversion).

Read ya, Phil


Note You need to log in before you can comment on or make changes to this bug.