From: "'Jan Kiszka' via isar-users" <isar-users@googlegroups.com>
To: srinuvasan.a@siemens.com, isar-users@googlegroups.com
Subject: Re: [PATCH] meta/recipes-kernel/linux/files: use debhelper-compat to generate compat file
Date: Fri, 9 Aug 2024 18:43:38 +0200 [thread overview]
Message-ID: <e2f0d76f-a156-43f7-9c33-66495639a38f@siemens.com> (raw)
In-Reply-To: <20240809065158.224059-1-srinuvasan.a@siemens.com>
On 09.08.24 08:51, srinuvasan.a@siemens.com wrote:
> From: Srinuvasan A <srinuvasan.a@siemens.com>
>
> Now debhelper supports the versions debhelper-compat (= 9) till
What is "now" in this context? Which Debian releases are your referring
to? Keep in mind that we are still compiling down to buster with these
files. Doubt that this would still work...
> debhelper-compat (= 13), hence set appropriate debian helper compatible version
> in the debian/control file and remove the debian/compat file.
>
> Signed-off-by: Srinuvasan A <srinuvasan.a@siemens.com>
> ---
> meta/recipes-kernel/linux/files/debian/compat | 1 -
> meta/recipes-kernel/linux/files/debian/control.tmpl | 2 +-
> 2 files changed, 1 insertion(+), 2 deletions(-)
> delete mode 100644 meta/recipes-kernel/linux/files/debian/compat
>
> diff --git a/meta/recipes-kernel/linux/files/debian/compat b/meta/recipes-kernel/linux/files/debian/compat
> deleted file mode 100644
> index f599e28b..00000000
> --- a/meta/recipes-kernel/linux/files/debian/compat
> +++ /dev/null
> @@ -1 +0,0 @@
> -10
> diff --git a/meta/recipes-kernel/linux/files/debian/control.tmpl b/meta/recipes-kernel/linux/files/debian/control.tmpl
> index 04ad0f4f..ae257b7c 100644
> --- a/meta/recipes-kernel/linux/files/debian/control.tmpl
> +++ b/meta/recipes-kernel/linux/files/debian/control.tmpl
> @@ -2,7 +2,7 @@ Source: linux-${KERNEL_NAME_PROVIDED}
> Section: kernel
> Priority: optional
> Maintainer: ${MAINTAINER}
> -Build-Depends: bc, kmod, cpio, ${KBUILD_DEPENDS}
> +Build-Depends: debhelper-compat (= 12), bc, kmod, cpio, ${KBUILD_DEPENDS}
> Homepage: http://www.kernel.org/
>
> Package: linux-image-${KERNEL_NAME_PROVIDED}
Jan
--
Siemens AG, Technology
Linux Expert Center
--
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/isar-users/e2f0d76f-a156-43f7-9c33-66495639a38f%40siemens.com.
next prev parent reply other threads:[~2024-08-09 16:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-09 6:51 srinuvasan.a via isar-users
2024-08-09 16:43 ` 'Jan Kiszka' via isar-users [this message]
2024-08-11 14:20 ` Srinuvasan Arjunan
2024-08-27 15:45 ` Uladzimir Bely
2024-08-28 5:04 ` 'Arjunan, Srinu' via isar-users
2024-09-09 5:51 ` [PATCH v2] " srinuvasan.a via isar-users
2024-09-09 5:53 ` 'Arjunan, Srinu' via isar-users
2024-09-11 11:28 ` Uladzimir Bely
2024-12-16 11:20 ` [PATCH v3] meta/recipes-kernel: " srinuvasan.a via isar-users
2024-12-16 11:15 ` Srinuvasan Arjunan
2024-12-20 7:48 ` Uladzimir Bely
2025-01-31 12:14 ` 'Jan Kiszka' via isar-users
2025-01-31 12:31 ` 'MOESSBAUER, Felix' via isar-users
2025-01-31 12:39 ` 'Jan Kiszka' via isar-users
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=e2f0d76f-a156-43f7-9c33-66495639a38f@siemens.com \
--to=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.com \
--cc=srinuvasan.a@siemens.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox