public inbox for elfutils@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: elfutils-devel@sourceware.org
Cc: Mark Wielaard <mark@klomp.org>
Subject: [PATCH] config: Add a versioned requires on libs for elfutils-debuginfod-client
Date: Thu,  7 Apr 2022 15:29:22 +0200	[thread overview]
Message-ID: <20220407132922.20798-1-mark@klomp.org> (raw)

elfutils-debuginfod-client contains the debuginfod-client binary
which is uses libelf and libdw. Add an explicit versioned requires
on elfutils-libs so they will always be in sync like done with all
other inter sub package dependencies.

Signed-off-by: Mark Wielaard <mark@klomp.org>
---
 config/ChangeLog        | 5 +++++
 config/elfutils.spec.in | 2 ++
 2 files changed, 7 insertions(+)

diff --git a/config/ChangeLog b/config/ChangeLog
index acbaaa88..be27373f 100644
--- a/config/ChangeLog
+++ b/config/ChangeLog
@@ -1,3 +1,8 @@
+2022-04-07  Mark Wielaard  <mark@klomp.org>
+
+	* elfutils.spec.in (debuginfod-client): Add an explicit requires
+	on elfutils-libs.
+
 2021-11-10  Mark Wielaard  <mark@klomp.org>
 
 	* elfutils.spec.in: Update for 0.186.
diff --git a/config/elfutils.spec.in b/config/elfutils.spec.in
index aac0dffc..f4b26f03 100644
--- a/config/elfutils.spec.in
+++ b/config/elfutils.spec.in
@@ -141,6 +141,8 @@ profiling) of processes.
 %package debuginfod-client
 Summary: Library and command line client for build-id HTTP ELF/DWARF server
 License: GPLv3+ and (GPLv2+ or LGPLv3+)
+# For debuginfod-find binary
+Requires: elfutils-libs = %{version}-%{release}
 
 %package debuginfod-client-devel
 Summary: Libraries and headers to build debuginfod client applications
-- 
2.18.4


             reply	other threads:[~2022-04-07 13:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-07 13:29 Mark Wielaard [this message]
2022-04-12 13:24 ` Mark Wielaard

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=20220407132922.20798-1-mark@klomp.org \
    --to=mark@klomp.org \
    --cc=elfutils-devel@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).