public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Uladzimir Bely <ubely@ilbers.de>
To: Anton Mikanovich <amikan@ilbers.de>, isar-users@googlegroups.com
Subject: Re: [PATCH] sbuild: Declare using random build path
Date: Tue, 25 Mar 2025 19:57:33 +0300	[thread overview]
Message-ID: <8b3eb8badfa7fe8083bd8931abb0ded9ebc6ec97.camel@ilbers.de> (raw)
In-Reply-To: <20250318155058.263431-1-amikan@ilbers.de>

On Tue, 2025-03-18 at 17:50 +0200, Anton Mikanovich wrote:
> After 0.87.1 version of sbuild BUILD_PATH value is no more random by
> default. It is better for reproducibility but breaks concurrent
> builds
> because this path got removed during cleanup stage.
> To keep sbuild choose a random build location (just like it is in
> older
> package versions) set the empty string to build-path option.
> 
> More details can be found in sbuild commit:
> 14cc3a41f7eed7d9bd62e3c443d077b0f345cb24
> 
> This fixes Isar building on Trixie hosts.
> 
> Signed-off-by: Anton Mikanovich <amikan@ilbers.de>
> ---
>  meta/classes/dpkg.bbclass | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/meta/classes/dpkg.bbclass b/meta/classes/dpkg.bbclass
> index 64404103..0e5a495d 100644
> --- a/meta/classes/dpkg.bbclass
> +++ b/meta/classes/dpkg.bbclass
> @@ -124,7 +124,7 @@ dpkg_runbuild() {
>          --finished-build-commands="rm -f ${deb_dir}/sbuild-build-
> depends-main-dummy_*.deb" \
>          --finished-build-commands="find ${deb_dir} -maxdepth 1 -type
> f -name '*.deb' -print -exec cp ${CP_FLAGS} -t ${ext_deb_dir}/ {} +"
> \
>          --finished-build-commands="cp /var/log/dpkg.log
> ${ext_root}/dpkg_partial.log" \
> -        --build-dir=${WORKDIR} --dist="${DEBDISTRONAME}" ${DSC_FILE}
> +        --build-path="" --build-dir=${WORKDIR} --
> dist="${DEBDISTRONAME}" ${DSC_FILE}
>  
>      sbuild_dpkg_log_export "${WORKDIR}/rootfs/dpkg_partial.log"
>      deb_dl_dir_export "${WORKDIR}/rootfs" "${distro}"
> -- 
> 2.34.1

Applied to next.

-- 
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/8b3eb8badfa7fe8083bd8931abb0ded9ebc6ec97.camel%40ilbers.de.

      parent reply	other threads:[~2025-03-25 16:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-18 15:50 Anton Mikanovich
2025-03-18 21:20 ` 'Jan Kiszka' via isar-users
2025-03-19  6:59   ` 'MOESSBAUER, Felix' via isar-users
2025-03-19  7:32   ` Anton Mikanovich
2025-03-25 16:57 ` 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=8b3eb8badfa7fe8083bd8931abb0ded9ebc6ec97.camel@ilbers.de \
    --to=ubely@ilbers.de \
    --cc=amikan@ilbers.de \
    --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