public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Uladzimir Bely <ubely@ilbers.de>
To: Felix Moessbauer <felix.moessbauer@siemens.com>,
	isar-users@googlegroups.com
Cc: amikan@ilbers.de, jan.kiszka@siemens.com, quirin.gylstorff@siemens.com
Subject: Re: [PATCH 0/1] fix copy out of apt cache after sbuild
Date: Mon, 29 Jan 2024 13:50:17 +0300	[thread overview]
Message-ID: <b4cc1ae2026cd148b05227b136a001aa5e6d0b79.camel@ilbers.de> (raw)
In-Reply-To: <20240122132647.779902-1-felix.moessbauer@siemens.com>

On Mon, 2024-01-22 at 14:26 +0100, 'Felix Moessbauer' via isar-users
wrote:
> This series fixes the build issues reported in "potential race
> condition in sbuild post commands" by not copying symlinks. This has
> been tested on various large layers and seems to do the job. However,
> it still remains unclear why packages are missing in the apt cache
> under some rebuild scenarios.
> 
> While investigating this, I also noticed that we AGAIN have a
> quadratic
> space blow-up in the isar-apt directory that is copied into the build
> folder of each package. This makes me wonder if the whole APT
> handling
> is properly understood. IMHO this needs another haul-over, which is
> also
> indicated by the number of apt related issues which were reported in
> the
> last months.
> 
> Best regards,
> Felix
> 
> Felix Moessbauer (1):
>   fix copy out of apt cache after sbuild
> 
>  meta/classes/dpkg.bbclass | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> -- 
> 2.39.2
> 

Applied to next, thanks.

      parent reply	other threads:[~2024-01-29 10:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-22 13:26 Felix Moessbauer
2024-01-22 13:26 ` [PATCH 1/1] " Felix Moessbauer
2024-01-22 13:47 ` [PATCH 0/1] " Schmidt, Adriaan
2024-01-22 15:04   ` MOESSBAUER, Felix
2024-01-29 10:50 ` 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=b4cc1ae2026cd148b05227b136a001aa5e6d0b79.camel@ilbers.de \
    --to=ubely@ilbers.de \
    --cc=amikan@ilbers.de \
    --cc=felix.moessbauer@siemens.com \
    --cc=isar-users@googlegroups.com \
    --cc=jan.kiszka@siemens.com \
    --cc=quirin.gylstorff@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