From: Jan Kiszka <jan.kiszka@siemens.com>
To: "Hombourger,
Cedric (DI CTO FDS CES LX)" <cedric.hombourger@siemens.com>,
"isar-users@googlegroups.com" <isar-users@googlegroups.com>
Subject: Re: [PATCH] repository: make repo_del_srcpackage delete only source packages
Date: Fri, 23 Feb 2024 13:23:27 +0100 [thread overview]
Message-ID: <5f4783e3-8f92-4f28-b408-cb9165f95db4@siemens.com> (raw)
In-Reply-To: <2cd276fc18b728145f6489038ba53545c9f323a7.camel@siemens.com>
On 23.02.24 12:52, Hombourger, Cedric (DI CTO FDS CES LX) wrote:
> 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.
>
Ok, this information is valuable to assess the criticality of the issue,
thus should go also into the commit message.
Jan
--
Siemens AG, Technology
Linux Expert Center
next prev parent reply other threads:[~2024-02-23 12:23 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
2024-02-23 12:23 ` Jan Kiszka [this message]
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=5f4783e3-8f92-4f28-b408-cb9165f95db4@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