]> git.ipfire.org Git - thirdparty/openembedded/openembedded-core-contrib.git/commit
dnf: fix Exception handling for class ProcessLock
authorChangqing Li <changqing.li@windriver.com>
Mon, 25 Mar 2024 04:47:11 +0000 (12:47 +0800)
committerRichard Purdie <richard.purdie@linuxfoundation.org>
Sat, 30 Mar 2024 22:23:54 +0000 (22:23 +0000)
commitd86c0e3468504c6ed19e38750abbb8970b5b7691
tree87313fb6eae7b78314ceacc88ccbc40a3a353a42
parenta04a084b6e513d15cb57ee103c6d6215ce1c75b9
dnf: fix Exception handling for class ProcessLock

Yocto based systems will sometimes have log_lock.pid left in target
filesystems.  Users typing 'ls /' will notice it, and will never be
removed.

It happened when log rotate happened, refer [1], since the problem
descripted in patch 0001-lock.py-fix-Exception-handling.patch, file
log_lock.pid will not be removed after dnf exit. For target system,
refer [4], dnf have a solution to remove it. But for OE, refer commit
[2][3], for fix another issue, OE changed log_lock.pid to root dir for
native dnf, so solution in [4] not works for log_lock.pid under "/", so
it will always exist under "/" of target system.

Use patch 0001-lock.py-fix-Exception-handling.patch to fix the problem.

[1] https://github.com/rpm-software-management/dnf/blob/a6d82221ae32045f0f788708a52d2f2bf5c5740b/dnf/logging.py#L127C31-L127C42
[2] https://git.openembedded.org/openembedded-core/commit/?id=742a1b71249f4da1c8d8e13e270b0eb6128a3f66
[3] https://git.openembedded.org/openembedded-core/commit/?id=7610f81586bd475f28fd3d89a7350771720c3264
[4] https://github.com/rpm-software-management/dnf/blob/master/etc/tmpfiles.d/dnf.conf

Signed-off-by: Changqing Li <changqing.li@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
meta/recipes-devtools/dnf/dnf/0001-lock.py-fix-Exception-handling.patch [new file with mode: 0644]
meta/recipes-devtools/dnf/dnf_4.19.0.bb