kdb rm /..: removes spec key

[markus2330]

Steps to Reproduce the Problem

Assume that spec.ini is in pwd and contains:

[]
mountpoint = mymountpoint.ini

[mykey]
type = long

sudo kdb mount `pwd`/spec.ini spec/tests/hello ni
sudo kdb spec-mount /tests/hello

kdb set /tests/hello/mykey 123
kdb rm /tests/hello/mykey

Expected Result

That I removed what I've set just before.

Actual Result

The spec key is removed, spec.ini then contains:

;Ni1
; Generated by Nickel Plugin using Elektra (see libelektra.org).

 = 

[]
 mountpoint = mymountpoint.ini

Interestingly, the validation then still fails and kdb meta-get /tests/hello/mykey type still returns long. But this might be a different mmap-related bug (#2760).

System Information

• Elektra Version: master

[kodebach]

kdb getmeta /tests/hello/mykey type still returns long

That may be because of #2700. It may also be related to #2456.

[markus2330]

Thank you for making the connections.

[stale]

I mark this issue stale as it did not have any activity for one year. I'll close it in two weeks if no further activity occurs. If you want it to be alive again, ping the issue by writing a message here or create a new issue with the remainder of this issue.
Thank you for your contributions 💖

[markus2330]

As this bug might lead to accidental removal of wrong data, we should fix it. I updated the initial description to use meta-get.

Also the to-be-believed-mmap-related bug still can be reproduced with Elektra 0.9.2.

[stale]

I mark this issue stale as it did not have any activity for one year. I'll close it in two weeks if no further activity occurs. If you want it to be alive again, ping the issue by writing a message here or create a new issue with the remainder of this issue.
Thank you for your contributions 💖

[stale]

I closed this issue now because it has been inactive for more than one year. If I closed it by mistake, please do not hesitate to reopen it or create a new issue with the remainder of this issue.
Thank you for your contributions 💖

[kodebach]

@markus2330 Does this bug still exist? Should we reopen the issue?

[markus2330]

#3742 should fix it.