From: Jan Kiszka <jan.kiszka@siemens.com>
To: Cedric Hombourger <cedric.hombourger@siemens.com>,
isar-users@googlegroups.com
Subject: Re: [PATCH] repository: make repo_del_srcpackage delete only source packages
Date: Fri, 23 Feb 2024 12:34:37 +0100 [thread overview]
Message-ID: <dacca66e-ca9d-4209-8458-c527ff8444ce@siemens.com> (raw)
In-Reply-To: <20240223094207.1482845-1-cedric.hombourger@siemens.com>
On 23.02.24 10:42, 'Cedric Hombourger' via isar-users wrote:
> The reprepro removesrc command not only deletes the requested source
> package but also any binary packages that were built from it. If
> do_deploy_source is recalled after do_deploy_deb, we would see
> previously deployed binary packages vanish from isar-apt.
>
While I agree that a task should do what it is supposed to do, not more:
How is such a race possible? dpkg_build depends on deploy_source, and
deploy_deb depends on dpkg_build.
Jan
> Signed-off-by: Cedric Hombourger <cedric.hombourger@siemens.com>
> ---
> meta/classes/repository.bbclass | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/meta/classes/repository.bbclass b/meta/classes/repository.bbclass
> index a61e5dcd..28e712fd 100644
> --- a/meta/classes/repository.bbclass
> +++ b/meta/classes/repository.bbclass
> @@ -70,8 +70,8 @@ repo_del_srcpackage() {
> if [ -n "${GNUPGHOME}" ]; then
> export GNUPGHOME="${GNUPGHOME}"
> fi
> - reprepro -b "${dir}" --dbdir "${dbdir}" \
> - removesrc "${codename}" \
> + reprepro -b "${dir}" --dbdir "${dbdir}" -A source \
> + remove "${codename}" \
> "${packagename}"
> }
>
--
Siemens AG, Technology
Linux Expert Center
next prev parent reply other threads:[~2024-02-23 11:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-23 9:42 Cedric Hombourger
2024-02-23 11:34 ` Jan Kiszka [this message]
2024-02-23 11:52 ` cedric.hombourger
2024-02-23 12:23 ` Jan Kiszka
2024-02-26 7:07 ` [PATCH v2] " Cedric Hombourger
2024-03-11 12:07 ` 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=dacca66e-ca9d-4209-8458-c527ff8444ce@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=cedric.hombourger@siemens.com \
--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