From: Uladzimir Bely <ubely@ilbers.de>
To: Christoph Steiger <christoph.steiger@siemens.com>,
isar-users@googlegroups.com
Subject: Re: [PATCH] debianize: make default changelog timestamp configurable
Date: Thu, 13 Mar 2025 07:38:58 +0300 [thread overview]
Message-ID: <d73dcf7d565890dd7e94ab0f5685bb8be2a29e52.camel@ilbers.de> (raw)
In-Reply-To: <20250304100351.121924-1-christoph.steiger@siemens.com>
On Tue, 2025-03-04 at 11:03 +0100, 'Christoph Steiger' via isar-users
wrote:
> Add the `DEBIAN_CHANGELOG_TIMESTAMP` variable to make the default
> changelog timestamp configurable. This might be required if the
> default
> timestamp leads to problems in the build process.
>
> This is the case for e.g. python packages that use distutils<3.8 or
> with
> the hatchling build system, since the internally used zip does not
> support timestamps before 1. January 1980.
>
> Signed-off-by: Christoph Steiger <christoph.steiger@siemens.com>
> ---
> meta/classes/debianize.bbclass | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/meta/classes/debianize.bbclass
> b/meta/classes/debianize.bbclass
> index cf808eec..5e9d76f3 100644
> --- a/meta/classes/debianize.bbclass
> +++ b/meta/classes/debianize.bbclass
> @@ -14,12 +14,13 @@ DEBIAN_CONFLICTS ??= ""
> DEBIAN_BREAKS ??= ""
> DEBIAN_MULTI_ARCH ??= "no"
> DEBIAN_COMPAT ??= "10"
> +DEBIAN_CHANGELOG_TIMESTAMP ??= "3600"
> DESCRIPTION ??= "must not be empty"
> MAINTAINER ??= "Unknown maintainer <unknown@example.com>"
>
> deb_add_changelog() {
> changelog_v="${CHANGELOG_V}"
> - timestamp=3600
> + timestamp="${DEBIAN_CHANGELOG_TIMESTAMP}"
> if [ -f ${S}/debian/changelog ]; then
> if [ ! -f ${WORKDIR}/changelog.orig ]; then
> cp ${S}/debian/changelog
> ${WORKDIR}/changelog.orig
> --
> 2.39.5
>
Applied to next, thanks.
--
Best regards,
Uladzimir.
--
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/d73dcf7d565890dd7e94ab0f5685bb8be2a29e52.camel%40ilbers.de.
prev parent reply other threads:[~2025-03-13 4:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-04 10:03 'Christoph Steiger' via isar-users
2025-03-13 4:38 ` Uladzimir Bely [this message]
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=d73dcf7d565890dd7e94ab0f5685bb8be2a29e52.camel@ilbers.de \
--to=ubely@ilbers.de \
--cc=christoph.steiger@siemens.com \
--cc=isar-users@googlegroups.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