From: Anton Mikanovich <amikan@ilbers.de>
To: isar-users@googlegroups.com
Subject: Re: [PATCH v2] deb-dl-dir: Fix isar-apt packages checking on export
Date: Fri, 12 Jun 2026 13:56:06 +0300 [thread overview]
Message-ID: <d1745f39-d069-465c-8224-d5ed16a2aba6@ilbers.de> (raw)
In-Reply-To: <20260610075714.4022552-1-amikan@ilbers.de>
On 10/06/2026 10:57, Anton Mikanovich wrote:
> To use variable inside of lock section it should be exported.
> Otherwize it will be empty and isar-apt packages checking logic will
> not work.
>
> Fixes: 86f1c6e0 ("deb-dl-dir: Avoid multiple find run on export")
>
> Signed-off-by: Anton Mikanovich <amikan@ilbers.de>
> ---
> meta/classes-recipe/deb-dl-dir.bbclass | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/meta/classes-recipe/deb-dl-dir.bbclass b/meta/classes-recipe/deb-dl-dir.bbclass
> index 620ddc96..cec7bd76 100644
> --- a/meta/classes-recipe/deb-dl-dir.bbclass
> +++ b/meta/classes-recipe/deb-dl-dir.bbclass
> @@ -149,8 +149,8 @@ deb_dl_dir_export() {
> export owner=$(id -u):$(id -g)
> mkdir -p "${pc}"
>
> - isar_debs="$(${SCRIPTSDIR}/lockrun.py -r -f '${REPO_ISAR_DIR}/isar.lock' -c \
> - "find '${REPO_ISAR_DIR}/${DISTRO}' -name '*.deb' -print")"
> + export isar_debs=$(${SCRIPTSDIR}/lockrun.py -r -f '${REPO_ISAR_DIR}/isar.lock' -c \
> + "find '${REPO_ISAR_DIR}/${DISTRO}' -name '*.deb' -print")
>
> flock "${pc}".lock sudo -Es << 'EOSUDO'
> set -e
Applied with "Otherwize"->"Otherwise" typo fix.
--
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/d1745f39-d069-465c-8224-d5ed16a2aba6%40ilbers.de.
prev parent reply other threads:[~2026-06-12 10:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-10 7:57 Anton Mikanovich
2026-06-12 10:56 ` Anton Mikanovich [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=d1745f39-d069-465c-8224-d5ed16a2aba6@ilbers.de \
--to=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