public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "cedric.hombourger@siemens.com" <cedric.hombourger@siemens.com>
To: "isar-users@googlegroups.com" <isar-users@googlegroups.com>,
	"Kiszka, Jan" <jan.kiszka@siemens.com>
Subject: Re: [PATCH] repository: make repo_del_srcpackage delete only source packages
Date: Fri, 23 Feb 2024 11:52:00 +0000	[thread overview]
Message-ID: <2cd276fc18b728145f6489038ba53545c9f323a7.camel@siemens.com> (raw)
In-Reply-To: <dacca66e-ca9d-4209-8458-c527ff8444ce@siemens.com>

On Fri, 2024-02-23 at 12:34 +0100, Jan Kiszka wrote:
> 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.

There's no race. The issue will be seen if you bitbake -fc
deploy_source on a previously built recipe. 

> 
> 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}"
> >  }
> >  
> 

-- 
Cedric Hombourger
Siemens AG
www.siemens.com

  reply	other threads:[~2024-02-23 11:52 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
2024-02-23 11:52   ` cedric.hombourger [this message]
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=2cd276fc18b728145f6489038ba53545c9f323a7.camel@siemens.com \
    --to=cedric.hombourger@siemens.com \
    --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