Bug 2032671 - Drop or split out GTK+ 2 support
Summary: Drop or split out GTK+ 2 support
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: graphviz
Version: rawhide
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Jaroslav Škarvada
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-12-14 23:26 UTC by Adam Williamson
Modified: 2021-12-15 21:55 UTC (History)
2 users (show)

Fixed In Version: graphviz-2.50.0-2.fc36
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-12-15 20:46:17 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Adam Williamson 2021-12-14 23:26:37 UTC 
graphviz still depends on GTK+ 2. From this upstream discussion:

https://gitlab.com/graphviz/graphviz/-/issues/1848#note_476091808

it seems the features that rely on GTK+ 2 are actually quite minor and potentially disposable. Since upstream is not moving at all fast on coming up with a resolution, perhaps it would make sense downstream to either remove those features entirely, or at least split them into one or more subpackages so the core graphviz no longer pulls in GTK+ 2 and dependencies?
Comment 1 Jaroslav Škarvada 2021-12-15 20:23:41 UTC 
Split to the graphviz-gtk2 subpackage. There are still deps like glib, gobject, gdk_pixbuf that I haven't dealt with, just with the gtk.
Comment 2 Fedora Update System 2021-12-15 20:42:05 UTC 
FEDORA-2021-104ca6af05 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2021-104ca6af05
Comment 3 Fedora Update System 2021-12-15 20:46:17 UTC 
FEDORA-2021-104ca6af05 has been pushed to the Fedora 36 stable repository.
If problem still persists, please make note of it in this bug report.
Comment 4 Adam Williamson 2021-12-15 21:55:11 UTC 
Thanks a lot! Dealing with the others would be great too, of course, if it's not too difficult (I don't know the details).
Note You need to log in before you can comment on or make changes to this bug.