From: Jan Kiszka <jan.kiszka@siemens.com>
To: Uladzimir Bely <ubely@ilbers.de>, isar-users@googlegroups.com
Subject: Re: [PATCH] dpkg-source: lock isar-apt while do_fetch_common_source
Date: Mon, 1 Jul 2024 07:49:41 +0200 [thread overview]
Message-ID: <f59ea2dd-dbd3-461f-b2df-1722eecf8177@siemens.com> (raw)
In-Reply-To: <20240701052847.883-1-ubely@ilbers.de>
On 01.07.24 07:28, Uladzimir Bely wrote:
> Task do_fetch_common_source requires isar-apt repo unchanged while
> running "apt-get ... source ..." inside. Otherwise, it may fail on repo
> "Sources" or "Packages" file:
>
> ```
> Err:4 file:/isar-apt isar/main Sources
> Hash Sum mismatch
> ```
> This is quite often reproduced in CI since commit 2ca3a7e.
>
> Signed-off-by: Uladzimir Bely <ubely@ilbers.de>
> ---
> meta/classes/dpkg-source.bbclass | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/meta/classes/dpkg-source.bbclass b/meta/classes/dpkg-source.bbclass
> index d6ab5aad..a70a392d 100644
> --- a/meta/classes/dpkg-source.bbclass
> +++ b/meta/classes/dpkg-source.bbclass
> @@ -41,6 +41,7 @@ do_dpkg_build[depends] += "${BPN}:do_deploy_source"
> SCHROOT_MOUNTS = "${WORKDIR}:/work ${REPO_ISAR_DIR}/${DISTRO}:/isar-apt"
>
> do_fetch_common_source[depends] += "${SCHROOT_DEP} ${BPN}:do_deploy_source"
> +do_fetch_common_source[lockfiles] = "${REPO_ISAR_DIR}/isar.lock"
> do_fetch_common_source[network] = "${TASK_USE_SUDO}"
> do_fetch_common_source() {
> schroot_create_configs
Too bad that reprepro does not support atomic updates - agreed, needed.
Jan
--
Siemens AG, Technology
Linux Expert Center
next prev parent reply other threads:[~2024-07-01 5:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-01 5:28 Uladzimir Bely
2024-07-01 5:49 ` Jan Kiszka [this message]
2024-07-04 4:00 ` 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=f59ea2dd-dbd3-461f-b2df-1722eecf8177@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=ubely@ilbers.de \
/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