Bug 188148 - graphviz is broken
Summary: graphviz is broken
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: graphviz
Version: 5
Hardware: i686
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jima
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 197236 (view as bug list)
Depends On:
Blocks: FE6Target
TreeView+ depends on / blocked
 
Reported: 2006-04-06 13:46 UTC by Sonal Santan
Modified: 2007-11-30 22:11 UTC (History)
4 users (show)

Fixed In Version: 2.8-4.fc5
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-09-15 02:01:43 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Sonal Santan 2006-04-06 13:46:16 UTC
Description of problem:
dotty provided by graphviz-2.8-3.fc5 does not work since lefty is missing from
the package. I get the following output when running dotty--

prompt>which dotty
/usr/bin/dotty
prompt>dotty /usr/share/graphviz/graphs/directed/alf.dot
which: no lefty in
(.:/sbin:/usr/sbin:/usr/local/sbin:/usr/kerberos/bin:/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin:/usr/local/jre1.5.0_05/bin)
dotty: cannot locate the lefty program
       make sure that your path includes
       the directory containing dotty and lefty


Version-Release number of selected component (if applicable):
graphviz-2.8-3.fc5


How reproducible:
Always reproduceable.

Steps to Reproduce:
1.prompt> dotty /usr/share/graphviz/graphs/directed/alf.dot
2.
3.
  
Actual results:
dotty errors out.

Expected results:
dotty should display the graph.

Additional info:

Comment 1 Alex Lancaster 2006-09-14 15:22:57 UTC
This package has been broken for 5 months, please fix this ASAP!  Is this
package orphaned? There is also a duplicate at bug #197236.

Comment 2 Jima 2006-09-14 15:53:21 UTC
*** Bug 197236 has been marked as a duplicate of this bug. ***

Comment 3 Topher 2006-09-14 22:13:18 UTC
Is the fix really not as simple as it appears?

Comment 4 Jima 2006-09-15 02:01:43 UTC
It was pretty simple, actually.  Alex came into #fedora-extras this morning
looking for help on this issue, and I rolled an update, resolving this and
#184171.  I inadvertantly created another bug (if only one) in the process, but
it's not a blocker, and if this package goes orphan next week, I'll likely take
over and do another round of cleanups.


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