public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Michal Schorm <mschorm@redhat.com>
To: git-commits@fedoraproject.org
Subject: [rpms/unixODBC] rawhide: [cleanup] Remove dead 'Conflicts: iodbc' from spec
Date: Wed, 29 Jul 2026 11:11:51 GMT	[thread overview]
Message-ID: <178532351104.1.6311259298169556536.rpms-unixODBC-c39f98009a55@fedoraproject.org> (raw)

            A new commit has been pushed.

            Repo   : rpms/unixODBC
            Branch : rawhide
            Commit : c39f98009a5560fd40b8b535d66b1695081ec867
            Author : Michal Schorm <mschorm@redhat.com>
            Date   : 2026-07-20T01:51:27+02:00
            Stats  : +0/-2 in 1 file(s)
            URL    : https://src.fedoraproject.org/rpms/unixODBC/c/c39f98009a5560fd40b8b535d66b1695081ec867?branch=rawhide

            Log:
            [cleanup] Remove dead 'Conflicts: iodbc' from spec

This line was present from the very first spec import (commit fc5859a,
'unixODBC-1.8.12-2.src.rpm', Preston Brown, Jun 2000 — Red Hat Linux
"Winston" era).  No comment was ever attached explaining the reason.

The conflict existed because in 2000 both packages shipped:
- Config files via '%config %{_sysconfdir}/*' (catching '/etc/odbcinst.ini'
  and '/etc/odbc.ini')
- Standard ODBC headers ('sql.h', 'sqlext.h', 'sqltypes.h') directly
  in '/usr/include/'
- An ODBC driver manager library under the same soname

Since then, 'libiodbc' has been restructured to avoid all collisions:
- Different sonames: 'libiodbc.so.2' vs 'libodbc.so.2'
- Different binaries: 'iodbctest'/'iodbctestw' vs 'isql'/'odbcinst'
- Namespaced headers: '/usr/include/libiodbc/' vs '/usr/include/'
- Different pkg-config: 'libiodbc.pc' vs 'odbc.pc'
- No config files shipped by 'libiodbc' at all

On top of that, the Conflicts targets the package name 'iodbc', but
iODBC has been packaged as 'libiodbc' for years with no
'Provides: iodbc'.  The line is a no-op — it conflicts with a package
name that does not exist in Fedora.

'libiodbc' has never declared a reciprocal Conflicts on 'unixODBC'.

Co-Authored-By: Claude AI <noreply@anthropic.com>

---
diff --git a/unixODBC.spec b/unixODBC.spec
index 3e3f328..c021f97 100644
--- a/unixODBC.spec
+++ b/unixODBC.spec
@@ -21,8 +21,6 @@ BuildRequires: make automake autoconf libtool libtool-ltdl-devel bison flex
 BuildRequires: readline-devel
 %{!?rhel:BuildRequires: multilib-rpm-config}
 
-Conflicts: iodbc
-
 # ODBC driver packages
 Suggests: freetds
 Suggests: mariadb-connector-odbc

                 reply	other threads:[~2026-07-29 11:11 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=178532351104.1.6311259298169556536.rpms-unixODBC-c39f98009a55@fedoraproject.org \
    --to=mschorm@redhat.com \
    --cc=git-commits@fedoraproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox