From: Changqing Li <changqing.li@windriver.com>
To: Alexander Kanavin <alex.kanavin@gmail.com>,
Changqing Li <changqing.li@eng.windriver.com>
Cc: Alexandre Belloni <alexandre.belloni@bootlin.com>,
Richard Purdie <richard.purdie@linuxfoundation.org>,
Ross Burton <ross.burton@arm.com>,
"openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [master][PATCH 2/2] rootfs-postcommands.bbclass: add post func remove_unused_dnf_log_lock
Date: Wed, 6 Dec 2023 10:39:22 +0800 [thread overview]
Message-ID: <f997b989-a4f5-4691-a94b-625afdcf0936@windriver.com> (raw)
In-Reply-To: <CANNYZj-L-fycO7KaV_zM9QXnkOwKpC_7-UEsioqbSuroA=CQ4Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1290 bytes --]
On 12/5/23 17:55, Alexander Kanavin wrote:
> CAUTION: This email comes from a non Wind River email account!
> Do not click links or open attachments unless you recognize the sender and know the content is safe.
>
> On Tue, 5 Dec 2023 at 06:46, Changqing Li
> <changqing.li@eng.windriver.com> wrote:
>
>> So I add this patch
>> https://git.openembedded.org/openembedded-core/commit/?id=406a72a9a47c2735b7e18cefc682b1df00d5a9aa
>> to remove the lock file in rootfs.
>>
>> Since for dnf-native, it will not have reboot process, so it is better
>> to remove it at post process of rootfs, to make an clean rootfs.
> The review comments that led to the revert are still valid, and this
> message does not address them. The concern was that the removal via
> rootfs postprocess is too late. If dnf leaves lock files around, they
> should be removed just after the dnf execution.
Hi, Alex
Thanks. Agree that the lock file should be removed after dnf execution.
This is a bug of dnf. I had raise a bug upstream in Jul:
https://github.com/rpm-software-management/dnf/issues/1963.
This patch more like an workaround before dnf fix this issue, and this
log_lock.pid in rootfs
has no function impact, just a dirty file in rootfs.
Regards
Sandy
> Alex
[-- Attachment #2: Type: text/html, Size: 2610 bytes --]
next prev parent reply other threads:[~2023-12-06 2:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-30 9:14 [master][PATCH 1/2] dnf: only write the log lock to root for native dnf changqing.li
2023-06-30 9:14 ` [master][PATCH 2/2] rootfs-postcommands.bbclass: add post func remove_unused_dnf_log_lock changqing.li
2023-06-30 15:07 ` [OE-core] " Alexander Kanavin
2023-07-04 11:11 ` Ross Burton
2023-07-11 8:34 ` Changqing Li
2023-07-17 20:22 ` Alexander Kanavin
2023-12-05 5:46 ` Changqing Li
2023-12-05 9:55 ` Alexander Kanavin
2023-12-06 2:39 ` Changqing Li [this message]
2023-12-06 9:41 ` Alexander Kanavin
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=f997b989-a4f5-4691-a94b-625afdcf0936@windriver.com \
--to=changqing.li@windriver.com \
--cc=alex.kanavin@gmail.com \
--cc=alexandre.belloni@bootlin.com \
--cc=changqing.li@eng.windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.org \
--cc=ross.burton@arm.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