Description of problem: when installing the openni package (or anything depending on it) via rpm-ostree on Fedora Silverblue, installation fails with error Running post scripts... done error: Running %post for openni: Executing bwrap(/bin/sh): Child process exited abnormally; run `journalctl -t 'rpm-ostree(openni.post)'` for more information Version-Release number of selected component (if applicable): openni-1.5.7.10-13.fc29.x86_64 How reproducible: always Steps to Reproduce: 1. install Fedora Silverblue 29 2. run rpm-ostree install openni Actual results: Installation fails Expected results: Installation should complete successfully Additional info: journalctl -t 'rpm-ostree(openni.post)' output: Apr 23 11:16:23 localhost.localdomain rpm-ostree(openni.post)[1945]: Failed: Failed to write to the file! Apr 23 11:16:23 localhost.localdomain rpm-ostree(openni.post)[1945]: Failed: Failed to write to the file! Apr 23 11:16:23 localhost.localdomain rpm-ostree(openni.post)[1945]: Failed: Failed to write to the file!
I'm having the same issue on Silverblue 30. Looking at the code, the post-install runs a helper program called "niReg" that tries to update some values in /var/lib/ni/modules.xml, but opening that file for writing fails on Silverblue. I don't really know enough about rpm-ostree to know why that fails, though.
I'm assuming that layered packages in rpm-ostree aren't allowed to touch /var. I think the solution would be to patch this line in the OpenNI source code, where the /var/lib/ni path is defined. https://github.com/OpenNI/OpenNI/blob/1e9524ffd759841789dadb4ca19fb5d4ac5820e7/Source/OpenNI/XnOpenNI.cpp#L7075
This message is a reminder that Fedora 29 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '29'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 29 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.