From: "Fabian Grünbichler" <f.gruenbichler@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH kernel 3/6] d/control: provide linux-libc-dev with version
Date: Tue, 15 Jun 2021 13:27:26 +0200 [thread overview]
Message-ID: <20210615112729.1099797-4-f.gruenbichler@proxmox.com> (raw)
In-Reply-To: <20210615112729.1099797-1-f.gruenbichler@proxmox.com>
needed for it to be a proper replacement for linux-libc-dev when
resolving dependencies, such as for liburing-dev
Signed-off-by: Fabian Grünbichler <f.gruenbichler@proxmox.com>
---
debian/control.in | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/debian/control.in b/debian/control.in
index a9c8dd8..6cdc9df 100644
--- a/debian/control.in
+++ b/debian/control.in
@@ -83,7 +83,7 @@ Package: pve-kernel-libc-dev
Section: devel
Priority: optional
Architecture: any
-Provides: linux-libc-dev,
+Provides: linux-libc-dev (=${binary:Version}),
Conflicts: linux-libc-dev,
Replaces: linux-libc-dev,
Depends: ${misc:Depends}
--
2.30.2
next prev parent reply other threads:[~2021-06-15 11:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-15 11:27 [pve-devel] [PATCH bullseye kernel 0/6] debug package and packaging/build cleanups Fabian Grünbichler
2021-06-15 11:27 ` [pve-devel] [PATCH kernel 1/6] build: keep unstripped kernel and module files Fabian Grünbichler
2021-06-15 11:27 ` [pve-devel] [PATCH kernel 2/6] d/rules: build perf with python3 Fabian Grünbichler
2021-06-15 11:27 ` Fabian Grünbichler [this message]
2021-06-15 11:27 ` [pve-devel] [PATCH kernel 4/6] d/control: remove references to 2.6 kernel Fabian Grünbichler
2021-06-15 11:27 ` [pve-devel] [PATCH kernel 5/6] d/control: wrap-and-sort Fabian Grünbichler
2021-06-15 11:27 ` [pve-devel] [RFC kernel 6/6] d/rules: close race between 'cp' and module handling Fabian Grünbichler
2021-06-15 12:34 ` [pve-devel] applied: [PATCH bullseye kernel 0/6] debug package and packaging/build cleanups Thomas Lamprecht
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=20210615112729.1099797-4-f.gruenbichler@proxmox.com \
--to=f.gruenbichler@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal