Please remove myodbc from the archive
Bug #1564856 reported by
Robie Basak
This bug affects 3 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| myodbc (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
Prior to 5.7, MySQL did not restrict symbols available in libmysqlclient (<= 18). Upstream cleaned up in libmysqlclient20 as shipped with MySQL 5.7. It looks like myodbc 5.1.10-3 uses some of these symbols, so FTBFS against libmysqlclient-dev provided by MySQL 5.7 (that corresponds to libmysqlclient20).
I'm told by upstream that:
5.3.2 can be built against MySQL 5.7 with Fedora's patch, since they are doing it.
5.3.6 should work too, with a smaller patch.
Revision history for this message
| Lars Tangvald (lars-tangvald) wrote | #1 |
| tags: | added: mysql-5.7-transition |
Revision history for this message
| Robie Basak (racb) wrote | #2 |
| summary: |
- myodbc uses internal libmysqlclient functions no longer exported by 5.7 + Please remove myodbc from the archive |
Revision history for this message
| Adam Conrad (adconrad) wrote | #3 |
| Changed in myodbc (Ubuntu): | |
| status: | New → Fix Released |
Revision history for this message
| Nathan Neulinger (nneul-0) wrote | #4 |
To post a comment you must log in.
Getting myodbc working with 5.7 would be a fairly significant task:
* It would require updating to 5.3 which is non-trivial since upstream has switched from autoconf to cmake, so packaging would need changes.
* It would still need patching due to a known issue with the current 5.3 packages.
One suggestion is:
Remove myodbc:
The package has not been maintained in a while, and there are no hard dependencies on it. It is the default alternative for libreoffice-
Once upstream has finished the work on MySQL 5.7 we can try to update myodbc in proposed to get it back into the release, but there is a significant chance there won't be enough time.