Bug 199079 - databases/mysql-workbench52: Incompatible with glib 2.42 - Empty Result Grids
Summary: databases/mysql-workbench52: Incompatible with glib 2.42 - Empty Result Grids
Status: Closed Overcome By Events
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: amd64 Any
: --- Affects Some People
Assignee: freebsd-ports-bugs (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-04-01 02:00 UTC by Chris Wells
Modified: 2016-03-05 12:35 UTC (History)
2 users (show)

See Also:


Attachments
Patch that resolves the issue. (1.63 KB, patch)
2015-04-01 02:00 UTC, Chris Wells
no flags Details | Diff
Screen shot of empty data grid and output. (69.55 KB, image/png)
2015-04-01 02:01 UTC, Chris Wells
no flags Details
Screen shot of missing column data in table editor. (59.71 KB, image/png)
2015-04-01 02:03 UTC, Chris Wells
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Chris Wells 2015-04-01 02:00:21 UTC
Created attachment 155071 [details]
Patch that resolves the issue.

With glib 2.42 installed, the current mysql-workbench-gpl52 package displays blank output and result sets.  The issue was reported to the MySQL project and fixed in version 6.2.4:

http://bugs.mysql.com/bug.php?id=74147

There is a diff patch attached to their ticket that resolves the issue in our current mysql-workbench-gpl52 port:

http://bugs.mysql.com/file.php?id=21874&bug_id=74147

I'm attaching the same diff to this ticket for convenience.

I would expect this issue to exist on all hardware, but I selected amd64 because that's all I've personally verified it on.
Comment 1 Chris Wells 2015-04-01 02:01:47 UTC
Created attachment 155072 [details]
Screen shot of empty data grid and output.
Comment 2 Chris Wells 2015-04-01 02:03:01 UTC
Created attachment 155073 [details]
Screen shot of missing column data in table editor.
Comment 3 Raphael Kubo da Costa freebsd_committer freebsd_triage 2016-02-28 22:57:06 UTC
Hi,

The patch looks valid, but the port has been marked broken since June of last year (and has probably been broken for even longer) because it fails to build with libc++.

Unless there is also a fix for that, I'm afraid the port will be removed within the next few days.
Comment 4 w.schwarzenfeld 2016-03-02 16:06:10 UTC
Freshports: This port expired on: 2016-02-29.
Comment 5 Raphael Kubo da Costa freebsd_committer freebsd_triage 2016-03-05 12:35:54 UTC
It doesn't look like anyone's going to make this port work again, so I'll close this bug report and remove the port from the tree.