https://bugs.kde.org/show_bug.cgi?id=519481
--- Comment #24 from ALIEN426 <[email protected]> --- Update: Most likely the bug is in the writeConfig/parseConfig/setEntry logic. The first time the config is parsed, the deletion marker enty overwrites the global entry. As a result, the second time the config is parsed the deletion marker entry is treated as a nonexistent key and is silently dropped. The key dropping behavior was introduced in this commit, but the bug was not actually "caused by" it as I stated earlier. The change fixes a legitimate issue with nonexistent keys: https://invent.kde.org/frameworks/kconfig/-/commit/7a34db5ab0666addabd038269366407645b04647 -- You are receiving this mail because: You are watching all bug changes.
