From: "'Florian Bezdeka' via isar-users" <isar-users@googlegroups.com>
To: srinuvasan.a@siemens.com, isar-users@googlegroups.com
Subject: Re: [PATCH] debianize: set appropriate Standards-Version for each debian suite
Date: Tue, 28 Oct 2025 12:56:22 +0100 [thread overview]
Message-ID: <6a94c7b3e8f2906fc8c85da2c356b80b8a63eb96.camel@siemens.com> (raw)
In-Reply-To: <20251027115328.97284-1-srinuvasan.a@siemens.com>
On Mon, 2025-10-27 at 17:23 +0530, srinuvasan.a via isar-users wrote:
> From: srinuvasan <srinuvasan.a@siemens.com>
>
> The Standards-Version field in debian/control declares the Debian Policy
> version that the package complies with. Currently, the custom source packages
> use a hard-coded Standards-Version: 3.9.6, which is obsolete and does not align
> with the policies of newer Debian releases
>
> Update the packaging to set the correct Standards-Version dynamically based on
> the target Debian suite, ensuring compliance with the appropriate Debian Policy
> version for each release.
>
> Signed-off-by: srinuvasan <srinuvasan.a@siemens.com>
> ---
> meta/classes/debianize.bbclass | 9 ++++++++-
> 1 file changed, 8 insertions(+), 1 deletion(-)
>
> diff --git a/meta/classes/debianize.bbclass b/meta/classes/debianize.bbclass
> index 1f54e8f9..0d7b804b 100644
> --- a/meta/classes/debianize.bbclass
> +++ b/meta/classes/debianize.bbclass
> @@ -83,11 +83,18 @@ deb_create_control[vardeps] += "DEBIANIZE_BUILD_DEPENDS \
> DEBIAN_RULES_REQUIRES_ROOT"
> deb_create_control() {
> # Add Source section
> + case "${BASE_DISTRO_CODENAME}" in
> + buster) STANDARDS_VERSION="4.3.0" ;;
> + bullseye) STANDARDS_VERSION="4.5.1" ;;
> + bookworm) STANDARDS_VERSION="4.6.2" ;;
> + trixie|sid|*) STANDARDS_VERSION="4.7.2" ;;
> + esac
> +
Hm... But that means that downstream users might end up with a
different standard version for their package after updating isar the
next time.
I'm expecting build failures here and there. Quite sure that not all
packages / recipes out there will fulfill the newer standards.
Maybe add a short note to the API changelog? An available quick fix
would be to overwrite STANDARDS_VERSION in the affected recipes.
> cat << EOF > ${S}/debian/control
> Source: ${BPN}
> Section: ${@ deb_list_beautify(d, 'DEBIAN_SECTION')}
> Priority: optional
> -Standards-Version: 3.9.6
> +Standards-Version: ${STANDARDS_VERSION}
> Maintainer: ${MAINTAINER}
> Build-Depends: ${@ deb_list_beautify(d, 'DEBIANIZE_BUILD_DEPENDS')}
> EOF
> --
>
--
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 visit https://groups.google.com/d/msgid/isar-users/6a94c7b3e8f2906fc8c85da2c356b80b8a63eb96.camel%40siemens.com.
next prev parent reply other threads:[~2025-10-28 11:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-27 11:53 srinuvasan.a via isar-users
2025-10-28 11:56 ` 'Florian Bezdeka' via isar-users [this message]
2025-10-29 12:02 ` [PATCH v2] " srinuvasan.a via isar-users
2025-10-29 15:25 ` '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=6a94c7b3e8f2906fc8c85da2c356b80b8a63eb96.camel@siemens.com \
--to=isar-users@googlegroups.com \
--cc=florian.bezdeka@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