public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Felix Moessbauer <felix.moessbauer@siemens.com>,
	isar-users@googlegroups.com
Subject: Re: [PATCH 1/1] do not forward SDE into sbuild environment
Date: Fri, 17 May 2024 17:28:27 +0200	[thread overview]
Message-ID: <a271aeae-6907-49ad-a8b8-f696fc2542c2@siemens.com> (raw)
In-Reply-To: <20240517150505.569940-1-felix.moessbauer@siemens.com>

On 17.05.24 17:05, Felix Moessbauer wrote:
> The SOURCE_DATE_EPOCH inside the sbuild environment is automatically set
> according to the debian changelog. By that, we do not need to explicitly
> forward a possibly different, but ignored value into the sbuild
> environment.
> 
> This patch also fixes a warning about converting the SDE to a template.
> 

To be clear: That warning was only visible with a not-yet-published
patch of mine.

Jan

> Signed-off-by: Felix Moessbauer <felix.moessbauer@siemens.com>
> ---
>  meta/classes/dpkg.bbclass | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/meta/classes/dpkg.bbclass b/meta/classes/dpkg.bbclass
> index 3fa9f604..0e25eb76 100644
> --- a/meta/classes/dpkg.bbclass
> +++ b/meta/classes/dpkg.bbclass
> @@ -50,6 +50,7 @@ dpkg_runbuild() {
>          # Filter some standard variables
>          echo ${line} | grep -q "^HOME=" && continue
>          echo ${line} | grep -q "^PWD=" && continue
> +        echo ${line} | grep -q "^SOURCE_DATE_EPOCH=" && continue
>  
>          var=$(echo "${line}" | cut -d '=' -f1)
>          value=$(echo "${line}" | cut -d '=' -f2-)

-- 
Siemens AG, Technology
Linux Expert Center


  reply	other threads:[~2024-05-17 15:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-17 15:05 Felix Moessbauer
2024-05-17 15:28 ` Jan Kiszka [this message]
2024-05-28  5:39 ` Uladzimir Bely

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=a271aeae-6907-49ad-a8b8-f696fc2542c2@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=felix.moessbauer@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