public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Anton Mikanovich <amikan@ilbers.de>
To: Jan Kiszka <jan.kiszka@siemens.com>, isar-users@googlegroups.com
Subject: Re: [PATCH] sbuild: Declare using random build path
Date: Wed, 19 Mar 2025 09:32:52 +0200	[thread overview]
Message-ID: <f05fe9e2-3149-4398-91e6-6101c2b62605@ilbers.de> (raw)
In-Reply-To: <6866b9a3-9953-4f41-b1dc-9074edf91012@siemens.com>

18/03/2025 23:20, Jan Kiszka wrote:
> On 18.03.25 16:50, 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.
> Can you elaborate?
>
In this case new default BUILD_PATH=/build/reproducible-path got shared 
between
multiple sbuild instances for all the packages. When the first package 
finish
the built it removes /build/reproducible-path, which results in other sbuild
processes fails with errors like:

| E: Failed to change to directory �/build/reproducible-path�: No such 
file or directory

So we just won't use static BUILD_PATH on trixie for now.
>> To keep sbuild choose a random build location (just like it is in older
>> package versions) set the empty string to build-path option.
> Err, no. We clearly need reproducibility as well.

As Felix already mentioned, this change do not brake anything, but just 
do not
apply additional reproducibility improvement on trixie hosts.
Actually there will be no any changes in paths on bookworm and lower, but
trixie will behave in the same way as bookworm currently does.

-- 
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/f05fe9e2-3149-4398-91e6-6101c2b62605%40ilbers.de.

  parent reply	other threads:[~2025-03-19  7:33 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 [this message]
2025-03-25 16:57 ` 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=f05fe9e2-3149-4398-91e6-6101c2b62605@ilbers.de \
    --to=amikan@ilbers.de \
    --cc=isar-users@googlegroups.com \
    --cc=jan.kiszka@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