When I install iodbc the libmyodbc package is removed, and I don't understand why. Does anyone have an explanation?
closed as not a real question by izx, ajmitch, hbdgaf, John S Gruber, jokerdino♦ Aug 22 '12 at 8:08
It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center. If this question can be reworded to fit the rules in the help center, please edit the question.
Its not entirely clear why they conflict. The relationship is declared in libmyodbc, as such:
But confusingly, its also recommending libiodbc2!
The changelog only mentions this way back in 2002 in an update from Debian:
This seems like a bug, and its probably worth asking the maintainer for an explanation via a bug report filed with
It appears myodbc is specifically an ODBC wrapper for mysql, while iodbc is a generalized ODBC wrapper for all kinds of DBs, so a conflict seems logical.
Evidently somehow one database connector is used to configure another...which evidently if they conflict, it isn't.
See the other answer to this question for more information, and on how to file a bug.