ODBC Stack Modernization
Summary
Modernize the Fedora ODBC stack across 8 packages (unixODBC, libiodbc, and 6 driver packages: mariadb-connector-odbc, mysql-connector-odbc, postgresql-odbc, freetds, sqliteodbc, mdbtools). The central change is replacing the static, centrally-maintained /etc/odbcinst.ini driver registration file with an auto-generated configuration assembled from per-driver drop-in snippets, using RPM file triggers — the same pattern used by ldconfig, ca-certificates, and crypto-policies. Supporting changes include switching to bare library names resolved via a compiled-in search path, moving driver plugins to a dedicated directory, and general spec cleanups.
Owner
- Name: Michal Schorm
- Email: mschorm@redhat.com
Current status
- Targeted release: Fedora Linux 45
- Last updated: 2026-08-03
- Announced
- Discussion thread
- FESCo issue: #3655
- Tracker bug: #2510639
- Release notes tracker: #418
Proposed code changes
All changes are in the dropin-registration topic branches in the Change owner's forks:
- unixODBC — drop-in infrastructure, driver-manager-neutral
odbcinst-generatesubpackage (GPL-2.0-or-later), file triggers,%ghostconfig, migration scriptlets, per-driver path resolution with multilibDriver/Driver64support,odbcinst-generate(1)man page; preceded by c39f980 removing deadConflicts: iodbc - libiodbc — add
Requires: odbcinst-generatefor shared driver registration on iODBC-only hosts - mariadb-connector-odbc — ship
10-mariadb.inidrop-in snippet, co-own snippet directories - mysql-connector-odbc — ship
10-mysql.inidrop-in snippet, co-own snippet directories - postgresql-odbc — ship
10-postgresql.inidrop-in snippet, co-own snippet directories - freetds — ship
10-freetds.inidrop-in snippet, co-own snippet directories - sqliteodbc — ship
10-sqlite.inidrop-in snippet, remove legacyodbcinstscriptlets, co-own snippet directories - mdbtools — ship
10-mdbtools.inidrop-in snippet, co-own snippet directories
Detailed Description
Background
The ODBC driver manager (unixODBC) uses /etc/odbcinst.ini to map driver names to shared libraries. In Fedora, this file has historically been shipped as %config(noreplace) inside the unixODBC package, pre-populated with entries for all known Fedora ODBC drivers.
The driver entries in Fedora were in poor shape. FileUsage values were wrong for multiple drivers, library paths were hardcoded and multilib-unfriendly, and the FreeTDS entry contained a dead Port key that the driver never reads from odbcinst.ini. These problems persisted because driver entries lived in the wrong package — fixing a driver's registration required a change to unixODBC, not to the driver package itself.
This coupling created several structural problems:
- Wrong ownership: Driver packages had no control over their own registration. A driver maintainer who wanted to fix or update their entry had to coordinate a change in
unixODBC. - Stale entries: All known drivers were pre-populated in the config regardless of whether they were installed, leading to broken references.
- Invisible drivers: New driver packages (e.g.
mdbtools-odbc) were not registered at all until someone manually added them to theunixODBCspec.mdbtools-odbcwas invisible to ODBC applications after install. - Fragile upgrades: The
%config(noreplace)semantics mean RPM silently keeps the old file on upgrade, so corrections (like fixedFileUsagevalues) never reach existing installations.
Of all 6 driver packages in Fedora, only sqliteodbc attempted self-registration via %post/%preun scriptlets calling odbcinst -i/odbcinst -u. The other 5 relied entirely on unixODBC pre-populating their entries.
What is changing
The modernization consists of two groups of changes:
Already in Fedora Rawhide (foundation work):
- ODBC driver plugins moved from
%{_libdir}to a dedicated%{_libdir}/odbc/directory across all driver packages. unixODBCcompiled with--with-odbc-driver-path=%{_libdir}/odbc, enabling bare library names (e.g.Driver = libmaodbc.soinstead of full paths).FileUsagevalues corrected across all drivers (BZ#2453060).Suggests:added for all 6 ODBC driver packages.- Removal of a 17-year-old dead patch (
keep-typedefs.patch).
Proposed in this change (driver registration):
- Each driver package ships a static
.inisnippet file to/usr/lib/odbc/odbcinst.d/(vendor defaults). Snippets are placed in anodbcinst.d/subdirectory rather than directly in/usr/lib/odbc/to separate configuration snippets (.inifiles) from driver shared libraries (.sofiles), preventing spurious file trigger fires when driver libraries are installed. - All driver packages co-own
%dir %{_prefix}/lib/odbcand%dir %{_prefix}/lib/odbc/odbcinst.dper Fedora directory ownership guidelines — every package that installs files into a directory must own it so directories are properly created and cleaned up regardless of installation order. - The regeneration infrastructure is split into a driver-manager-neutral
odbcinst-generatesubpackage (BuildArch: noarch, GPL-2.0-or-later, with SPDX license headers). It contains only a bash script, man page, license,%ghostconfig,%direntries, and RPM file triggers — nothing compiled. BothunixODBCandlibiodbcRequires:it. unixODBCowns%transfiletriggerinand%transfiletriggerpostunscriptlets that run a regeneration script (odbcinst-generate) whenever snippets are installed or removed.- The regeneration script merges all snippets (vendor defaults overlaid by admin overrides), resolves bare library names to absolute architecture-correct paths via per-driver filesystem probing (with multilib
Driver/Driver64support), and atomically replaces/etc/odbcinst.ini. /etc/odbcinst.inichanges from%config(noreplace)to%ghost— RPM tracks ownership but the file is never shipped; it is always generated.- Administrators can override or disable vendor drivers via
/etc/odbc/odbcinst.d/(see below).
Drop-in directory layout
/usr/lib/odbc/odbcinst.d/ ← vendor snippets (shipped by driver RPMs)
10-mariadb.ini
10-mysql.ini
10-postgresql.ini
10-freetds.ini
10-sqlite.ini
10-mdbtools.ini
/etc/odbc/odbcinst.d/ ← admin overrides and additions
/etc/odbcinst.ini ← generated output (%ghost)
Override semantics (stripped-name matching):
Files are named NN-name.ini. The numeric prefix is stripped for override matching (10-mariadb.ini and 60-mariadb.ini both become mariadb.ini); files sharing a stripped name compete and only one survives:
- Directory wins: A file in
/etc/odbc/odbcinst.d/always takes precedence over a file with the same stripped name in/usr/lib/odbc/odbcinst.d/, regardless of numeric prefix. - Higher prefix wins: Within the same directory, the file with the higher numeric prefix wins.
- Output sections are sorted alphabetically by stripped name.
- To disable a vendor driver, symlink its snippet to
/dev/null:
ln -sf /dev/null /etc/odbc/odbcinst.d/10-freetds.ini
- To apply changes after editing drop-in files manually, run:
odbcinst-generate
This uses stripped-name matching rather than the exact filename matching used by sysctl.d, tmpfiles.d, and modprobe.d. Those systems let files with different names coexist and resolve conflicting keys individually by lexicographic sort order. That model works for key-value configs, but ODBC driver registration declares complete [DriverName] INI sections — merging keys from two [MariaDB] sections across files would be ambiguous. The entire section is the atomic unit, so the override must replace the whole snippet.
Numeric prefix ranges:
- 10–29: Distro vendor (Fedora-shipped driver packages)
- 30–49: Third-party / out-of-tree (COPR packages, vendor RPMs)
- 50–99: Administrator overrides and additions
Precedent
This is the standard Fedora pattern for generated configuration. At least 22 packages use the same %transfiletriggerin + regeneration model, including:
glibc-common—/etc/ld.so.conf.d/→ldconfig→/etc/ld.so.cacheca-certificates—/etc/pki/ca-trust/source/→update-ca-trust→ca-bundle.crtcrypto-policies—/usr/share/crypto-policies/→update-crypto-policiesfontconfig—/usr/share/fonts/→fc-cacheshared-mime-info—/usr/share/mime/→update-mime-databaseglib2—/usr/share/glib-2.0/schemas/→glib-compile-schemas
Migration strategy (for FESCo consideration)
This is the area where community input is most welcome.
When upgrading from a system where /etc/odbcinst.ini was %config(noreplace) to the new %ghost model, RPM does not automatically create an .rpmsave backup. Without intervention, any user modifications to odbcinst.ini would be silently lost.
The proposed migration strategy uses content-based detection to distinguish stock configs from user-customized ones:
- A
%pretransLua scriptlet inunixODBCdetects first-time upgrades (the drop-in directory does not yet exist) and parses/etc/odbcinst.inifor INI[Section]headers. Each section is checked against the set of drivers historically shipped by Fedora (PostgreSQL,MySQL,MySQL-5,FreeTDS,MariaDB,MDBTools,SQLITE,SQLITE3). - Stock configs (only known sections): the file is silently dropped. The drop-in snippets will regenerate equivalent entries. No
.rpmsave, no notice. This is the common case — most users never touched the file. - Customized configs (any unknown section): the file is renamed to
/etc/odbcinst.ini.rpmsave. A%postnotice explains the migration path. This notice is repeated on every upgrade as long as the.rpmsavefile remains. - On subsequent upgrades (drop-in directory already exists), the
%pretransis a no-op.
What users need to do:
- Users who never modified
odbcinst.ini: nothing. The upgrade is completely silent. - Users who added custom driver entries: copy their custom
[sections]fromodbcinst.ini.rpmsaveinto a new file under/etc/odbc/odbcinst.d/and runodbcinst-generate.
Alternatives considered:
- Unconditional .rpmsave (always rename the file): rejected because it nags the large majority of users who never edited the file.
- Checksum comparison against known defaults: rejected because 22 distinct stock file variants exist across Fedora versions, and
sqliteodbc%postscriptlets historically injected architecture-specific[SQLITE]sections viaodbcinst -i, creating further permutations. RPM's embedded Lua has no digest functions. - Always preserve (never create
.rpmsave): rejected because it leaves the old static file alongside the new generated one, causing confusion. - In-place migration (automatically convert user entries to drop-in files): rejected as too complex and opaque. Users should be aware of the new mechanism.
Rejected ideas: scriptlet-based registration (Debian/Ubuntu, openSUSE)
Other distributions use odbcinst -i/odbcinst -u commands in driver package scriptlets (postinst/postrm on Debian, %post/%preun on openSUSE). I considered and rejected this for Fedora due to various bugs present in this approach.
How it works in Debian/Ubuntu: Each driver package calls odbcinst -i -d -f /usr/share/<driver>/odbcinst.ini.template in its postinst and odbcinst -u -d in its postrm. This approach has generated real bugs over more than a decade:
- Ubuntu Bug #1173083:
tdsodbcused a debconf prompt to ask whether to register the driver. In automated installs (containers, CI, preseed), the question was never answered, leaving FreeTDS silently unregistered. Open for 12 years before being fixed. - Debian Bug #1001141:
odbc-mariadbcalledodbcinstin its maintainer scripts but did not declare a dependency on theodbcinstbinary, causing silent registration failures.
How it works in openSUSE: Similar, using RPM %post/%preun scriptlets. All errors are suppressed with > /dev/null 2>&1 || true, so failures are completely silent. Coverage is inconsistent: only 3 of 5 driver packages self-register; mariadb-connector-odbc ships a sample .ini but no scriptlets; mdbtools has its ODBC driver incorrectly placed in the -devel subpackage.
Why the scriptlet approach is fundamentally fragile:
- Race conditions:
odbcinstperforms a read-modify-write cycle on/etc/odbcinst.iniwithout file locking. If two driver packages run scriptlets concurrently, the file can be corrupted or one registration silently lost. - Reference counting:
odbcinstmaintains a reference count per driver entry. A failed or interrupted scriptlet can leave the count out of sync, resulting in stale entries that never get removed or premature removal of valid entries. - Cross-package file modification: Multiple independent packages all modify a file owned by
unixODBC, violating single file ownership. - Per-driver boilerplate: Every driver package must independently implement registration logic, template files, and correct dependency declarations. Each one is a potential source of bugs.
Why the drop-in approach is better: RPM file triggers (%transfiletriggerin) are transactional — they fire once after the entire transaction completes, not once per package. The regeneration script rebuilds /etc/odbcinst.ini from scratch using only the snippet files currently on disk. There is no read-modify-write race, no reference counting, no possibility of stale entries, and driver packages need zero scriptlet logic — they ship a static file and nothing else.
With this change, Fedora would be the first distribution with a systemic, race-free, declarative ODBC driver registration mechanism with first-class admin override semantics.
Feedback
iODBC compatibility and absolute path resolution
Concern: Fedora ships libiodbc, and both unixODBC and iODBC read /etc/odbcinst.ini. Bare library names (Driver = libmaodbc.so) rely on unixODBC's compiled-in --with-odbc-driver-path search. iODBC has no equivalent — it requires an absolute path or a section name, not a bare soname. A bare name in the shared config file would dlopen-fail under iODBC.
Resolution: odbcinst-generate resolves bare library names to absolute, architecture-correct paths at generation time using per-driver existence-checked probing. For each bare .so name, the generator checks both /usr/lib64/odbc/ and /usr/lib/odbc/. If the file is not found in either directory, the bare name is left unchanged so unixODBC can still locate it via its compiled-in search path.
Multilib support (Driver/Driver64): On a multilib host where both 64-bit and 32-bit packages of a driver are installed (e.g. mariadb-connector-odbc.x86_64 and mariadb-connector-odbc.i686), the generator emits both keys:
Driver = /usr/lib/odbc/libmaodbc.so Driver64 = /usr/lib64/odbc/libmaodbc.so
unixODBC selects the matching key based on the calling application's word size — a 64-bit application reads Driver64, a 32-bit application (e.g. Wine) reads Driver. The same logic applies to Setup/Setup64. When only one architecture is present, only Driver is emitted.
iODBC and Driver64: iODBC does not support the Driver64 key. Its driver loading code (_iodbcdm_driverload() in iodbc/connect.c) reads only the Driver key, and its dlopen wrapper (DLL_OPEN macro in iodbcinst/dlf.h) calls dlopen() directly with no multilib awareness, no libltdl, and no search-path fallback. iODBC ignores unknown keys harmlessly, so the extra Driver64 line causes no errors — it is simply never read. On multilib hosts, iODBC always reads Driver (the 32-bit path), which is correct for iODBC's typical use case (32-bit applications). On non-multilib hosts, Driver carries the only available path regardless of architecture. This is a fundamental design difference from unixODBC, which has compile-time #ifdef PLATFORM64 logic to select between Driver and Driver64.
This per-driver probing also handles two edge cases: (1) a 32-bit-only driver on a 64-bit host is correctly resolved to /usr/lib/odbc/ instead of /usr/lib64/odbc/, and (2) a third-party driver whose .so lives outside /usr/lib*/odbc/ is not rewritten to a non-existent path.
Snippets remain noarch-portable with bare names (Driver = libmaodbc.so), but the generated /etc/odbcinst.ini carries absolute paths. This ensures the generated file works with both unixODBC and iODBC without requiring iODBC to depend on unixODBC or ship its own trigger.
Concern: Can unixODBC and iODBC genuinely coexist? The unixODBC spec carried Conflicts: iodbc, and the snippet mechanism only worked when unixODBC was installed.
Resolution (shared subpackage): The regeneration infrastructure (odbcinst-generate, file triggers, drop-in directories, %ghost /etc/odbcinst.ini) has been split into a subpackage named simply odbcinst-generate (via %package -n odbcinst-generate in the unixODBC SRPM). The package is named after the tool it ships, not after either driver manager, because both are equal consumers — libiodbc: Requires: unixODBC-... would point a dependency arrow into the wrong namespace. This follows the pattern of neutral infrastructure packages like hicolor-icon-theme and crypto-policies. No separate SRPM or new-package review is needed since it remains a subpackage of the unixODBC SRPM. Both unixODBC and libiodbc now Requires: odbcinst-generate, so the snippet mechanism works regardless of which driver manager is installed — including iODBC-only hosts.
Resolution (Conflicts removal): The Conflicts: iodbc line was a dead no-op: it targeted the package name iodbc, but iODBC has been packaged as libiodbc for years with no Provides: iodbc. Even if the name matched, there are zero file-level conflicts today: different sonames (libodbc.so.2 vs libiodbc.so.2), different binaries, different header paths (/usr/include/ vs /usr/include/libiodbc/), different pkg-config names, and libiodbc ships no config files at all. Co-installation was verified in a Fedora Rawhide container. The line has been removed.
Migration notice scoped to actual modifications
Concern: The original %pretrans unconditionally renamed /etc/odbcinst.ini to .rpmsave, producing a migration notice for every upgrading user. Most users never touched the file.
Resolution: The %pretrans now parses the file for INI section headers and checks each against the set of drivers historically shipped by Fedora. Stock configs (only known sections) are silently dropped — the snippets regenerate equivalent entries. Only configs with unknown sections (user-added custom drivers) are preserved as .rpmsave with a notice.
A checksum-based approach was investigated but is not viable: 22 distinct stock file variants exist across Fedora versions, sqliteodbc %post scriptlets injected architecture-specific sections via odbcinst -i creating further permutations, and RPM's embedded Lua has no digest functions.
See Migration strategy for full details.
Numeric ranges and third-party drivers
Concern: Out-of-distro drivers (COPR packages, third-party connectors) need a reserved numeric band and a documented tie-break rule.
Resolution: The numeric prefix range is now split into three bands:
- 10–29: Distro vendor (Fedora-shipped driver packages)
- 30–49: Third-party / out-of-tree (COPR packages, vendor RPMs)
- 50–99: Administrator overrides and additions
Tie-break rules are explicitly documented: admin directory always wins over vendor directory for the same stripped name (regardless of prefix); within the same directory, higher prefix wins. Collision behavior (two packages shipping the same filename) is an RPM file conflict — third-party packagers should use unique names (e.g. 30-seerodbc.ini, 31-oracle-instantclient.ini).
The odbcinst-generate(1) man page now documents these ranges, tie-break rules, and includes a NOTES section comparing the design with sysctl.d, tmpfiles.d, and other Fedora drop-in systems, explaining why stripped-name matching is used instead of exact-filename matching.
Multilib Driver/Driver64 support
Concern: On a multilib host with both 64-bit and 32-bit driver packages installed (e.g. for Wine), the generator should resolve the 64-bit driver into Driver64= and the 32-bit driver into Driver= so both work depending on the client application's word size.
Resolution: odbcinst-generate now checks both /usr/lib64/odbc/ and /usr/lib/odbc/ for each bare library name. When a driver .so exists in both directories (i.e. both the .x86_64 and .i686 RPMs are installed), the generated output contains:
Driver = /usr/lib/odbc/libmaodbc.so Driver64 = /usr/lib64/odbc/libmaodbc.so
unixODBC selects the matching key based on the calling application's word size. The same logic applies to Setup/Setup64. When only one architecture is present, only Driver is emitted. iODBC does not recognize Driver64 but ignores unknown keys harmlessly — the Driver key still provides the correct path.
Subpackage naming: odbcinst-generate
Concern: The original subpackage name unixODBC-odbcinst-generate bakes in the wrong ownership. Both driver managers (unixODBC and iODBC) are equal consumers of the regeneration infrastructure, and libiodbc: Requires: unixODBC-... is a dependency arrow pointing into the wrong namespace.
Resolution: The subpackage is now named odbcinst-generate (via %package -n odbcinst-generate in the unixODBC SRPM), named after the tool it ships. This follows the pattern of neutral infrastructure packages like hicolor-icon-theme and crypto-policies — a small neutral package that owns shared infrastructure, with both driver managers depending on it. No separate SRPM or new-package review is needed. The package ships active behavior (binary, file triggers, man page), not just directories, so the -filesystem suffix does not apply.
Benefit to Fedora
- Decoupled driver registration: Each driver package owns its own registration. Adding a new ODBC driver to Fedora no longer requires changes to
unixODBC. - Correct out-of-the-box experience: Only installed drivers appear in the config. Installing a driver automatically makes it visible to applications; removing it automatically cleans up. This fixes the long-standing problem where
mdbtools-odbcwas installable but invisible to ODBC applications. - Admin override mechanism: System administrators can override vendor defaults or disable drivers without editing generated files, using the same drop-in pattern familiar from systemd, ldconfig, and crypto-policies.
- Cross-driver-manager compatibility: Snippets use bare library names for noarch portability; the generator resolves them to absolute, architecture-correct paths in the generated output (with multilib
Driver/Driver64support for hosts with both 64-bit and 32-bit driver packages). The resulting/etc/odbcinst.iniworks with both unixODBC and iODBC without hardcoded%{_libdir}paths. - Correct metadata:
FileUsagevalues are fixed across all drivers. Fedora becomes the first distribution to ship correct values for all its ODBC drivers. - Reduced spec complexity: Driver packages no longer need
%post/%preunscriptlets for registration. A single static.inifile per driver replaces all of it.
Scope
- Proposal owners:
- Implement drop-in infrastructure in
unixODBC(directories, regeneration script, file triggers,%ghostconfig, migration scriptlets) - Split regeneration infrastructure into a driver-manager-neutral
odbcinst-generatesubpackage (%package -nin theunixODBCSRPM), licensed GPL-2.0-or-later with SPDX headers and copyright notices - Ship
odbcinst-generate(1)man page with AUTHORS and COPYRIGHT sections - Add
Requires: odbcinst-generatetolibiodbcfor driver-manager-independent snippet support - Add drop-in snippet files to all 6 driver packages:
mariadb-connector-odbc,mysql-connector-odbc,postgresql-odbc,freetds,sqliteodbc,mdbtools - All 6 driver packages co-own
%dir %{_prefix}/lib/odbcand%dir %{_prefix}/lib/odbc/odbcinst.dper Fedora directory ownership guidelines - Remove legacy
%post/%preunodbcinstscriptlets fromsqliteodbc - Remove dead
Conflicts: iodbcfromunixODBC(no-op since iODBC was repackaged aslibiodbc; zero file-level conflicts today) - Test upgrade scenarios and iODBC co-installation in containers via COPR
- Implement drop-in infrastructure in
- Other developers:
- No action required from other package maintainers. The change is self-contained within the 7 packages listed above.
- Release engineering: N/A (not a System Wide Change)
- Policies and guidelines: N/A
- Trademark approval: N/A
- Alignment with the Fedora Strategy: Fedora leads in the Linux distribution development. This change adopts a modern, well-established Fedora pattern for an area of the stack that has lagged behind.
Upgrade/compatibility impact
On upgrade from a previous Fedora release:
- Unmodified configs (the common case): the old file is silently replaced by a generated
/etc/odbcinst.ini. No.rpmsave, no notice. The upgrade is completely transparent. - Customized configs (user-added driver sections):
/etc/odbcinst.iniis saved as/etc/odbcinst.ini.rpmsave, and a notice is printed with migration instructions. - A new
/etc/odbcinst.iniis generated from drop-in snippets with absolute, architecture-correct paths. - All standard drivers (MariaDB, MySQL, PostgreSQL, FreeTDS, SQLite, MDBTools) are registered automatically if their packages are installed.
Applications using ODBC continue to work without changes. The generated odbcinst.ini uses the same INI format as before; only the mechanism that produces it has changed.
How To Test
Test builds are available in COPR: mschorm/ODBC
Fresh install (no previous ODBC config):
- Install
unixODBCand one or more driver packages - Verify
/etc/odbcinst.iniis generated and contains entries for the installed drivers - Verify that uninstalling a driver package removes its entry from
odbcinst.ini
Upgrade from current Rawhide (unmodified config):
- Start with a system running the current
unixODBC(pre-drop-in) - Upgrade to the new version
- Verify
/etc/odbcinst.ini.rpmsaveis not created (stock config is silently dropped) - Verify the new
/etc/odbcinst.inicontains correct entries for installed drivers with absolute paths
Upgrade with custom driver entries:
- Start with a system where
/etc/odbcinst.inihas been manually edited (e.g. a custom[MyDriver]section added) - Upgrade to the new version
- Verify
/etc/odbcinst.ini.rpmsavepreserves the custom entries - Copy the custom section into
/etc/odbc/odbcinst.d/60-mydriver.ini - Run
odbcinst-generate - Verify the custom driver appears in the regenerated
/etc/odbcinst.ini
Admin override:
- Install
mariadb-connector-odbc(ships10-mariadb.ini) - Create
/etc/odbc/odbcinst.d/60-mariadb.iniwith modified settings - Run
odbcinst-generate - Verify the admin override takes precedence
Driver disable:
ln -sf /dev/null /etc/odbc/odbcinst.d/10-freetds.ini- Run
odbcinst-generate - Verify FreeTDS no longer appears in
/etc/odbcinst.ini
Multilib (Driver/Driver64):
- Install both
mariadb-connector-odbc.x86_64andmariadb-connector-odbc.i686 - Verify
/etc/odbcinst.inicontains bothDriver = /usr/lib/odbc/libmaodbc.soandDriver64 = /usr/lib64/odbc/libmaodbc.soin the[MariaDB]section - Remove the
.i686package; verify onlyDriver = /usr/lib64/odbc/libmaodbc.soremains (noDriver64)
User Experience
For most users, the change is invisible. Installing an ODBC driver package automatically registers it; removing it automatically unregisters it. No manual odbcinst commands are needed.
Power users and administrators gain a familiar drop-in override mechanism. Customizing ODBC driver registration now works the same way as customizing library paths (ld.so.conf.d) or CA certificates (ca-trust).
Users upgrading from a previous Fedora release with an unmodified odbcinst.ini will see no change — the upgrade is silent. Only users who added custom driver entries will see a migration notice and find their previous configuration saved as .rpmsave.
Dependencies
All 8 affected packages are maintained by the change owner:
unixODBC(includes newodbcinst-generatesubpackage)libiodbcmariadb-connector-odbcmysql-connector-odbcpostgresql-odbcfreetdssqliteodbcmdbtools
No other packages are affected. The generated /etc/odbcinst.ini is format-compatible with the previous static file.
Contingency Plan
- Contingency mechanism: Revert the
unixODBCspec to ship a static%config(noreplace)odbcinst.iniand remove drop-in snippet files from driver packages. This is a straightforward revert of the topic branch in each package. - Contingency deadline: N/A (not a System Wide Change)
- Blocks release? No
Documentation
- BZ#2453060 — Standardize unixODBC connector installation directory
- COPR test repository: mschorm/ODBC
- A new
odbcinst-generate(1)man page is shipped with theodbcinst-generatesubpackage, documenting the regeneration tool, drop-in directory layout, override semantics, multilib resolution, and comparison withsysctl.d/tmpfiles.d. Both the script and man page carry SPDX license headers (GPL-2.0-or-later) and copyright notices; the man page includes AUTHORS and COPYRIGHT sections. - The existing upstream
odbcinst.ini(5)man page will be updated or supplemented with a note about the drop-in mechanism
Release Notes
The ODBC driver stack has been modernized. ODBC driver registration now uses a drop-in snippet mechanism: each driver package ships a small .ini file that is automatically merged into /etc/odbcinst.ini when the package is installed or removed. Administrators can override vendor defaults or add custom drivers by placing files in /etc/odbc/odbcinst.d/.
Users with an unmodified /etc/odbcinst.ini will see no change. Users who had added custom driver entries will find their previous configuration saved as /etc/odbcinst.ini.rpmsave after upgrading. Custom driver sections should be migrated to individual files under /etc/odbc/odbcinst.d/.
