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: [bugfix] Use 'mkdir -p' for ODBC plugin directory creation
Date: Wed, 29 Jul 2026 11:11:51 GMT	[thread overview]
Message-ID: <178532351150.1.4944519370124667616.rpms-unixODBC-78ea12b1564d@fedoraproject.org> (raw)

            A new commit has been pushed.

            Repo   : rpms/unixODBC
            Branch : rawhide
            Commit : 78ea12b1564defb8a9b051ccf8a1cd56aab784f1
            Author : Michal Schorm <mschorm@redhat.com>
            Date   : 2026-07-29T12:39:21+02:00
            Stats  : +1/-1 in 1 file(s)
            URL    : https://src.fedoraproject.org/rpms/unixODBC/c/78ea12b1564defb8a9b051ccf8a1cd56aab784f1?branch=rawhide

            Log:
            [bugfix] Use 'mkdir -p' for ODBC plugin directory creation

On i686, '%{_libdir}' resolves to '/usr/lib' — the same path as
'%{_prefix}/lib'. When other mkdir calls in %install already create
'/usr/lib/odbc/' (e.g. for drop-in snippet directories), the bare
'mkdir' here fails with "File exists" because it lacks '-p'.

Switching to 'mkdir -p' makes the directory creation idempotent
regardless of the order of mkdir calls and whether '%{_libdir}'
coincides with '%{_prefix}/lib'.

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

---
diff --git a/unixODBC.spec b/unixODBC.spec
index c021f97..c9e9a55 100644
--- a/unixODBC.spec
+++ b/unixODBC.spec
@@ -83,7 +83,7 @@ install -m644 %{SOURCE1} $RPM_BUILD_ROOT%{_sysconfdir}
 %endif
 
 # Directory for ODBC connector/driver plugins
-mkdir $RPM_BUILD_ROOT%{_libdir}/odbc
+mkdir -p $RPM_BUILD_ROOT%{_libdir}/odbc
 
 # copy text driver documentation into main doc directory
 # currently disabled because upstream no longer includes text driver

                 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=178532351150.1.4944519370124667616.rpms-unixODBC-78ea12b1564d@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