rpm-ostree is a new model for rpm packages on using ostree[0]. In order to implement atomic upgrades without special filesystem support, it runs %post scripts using rofiles-fuse[1] This means that %post scripts, whenever replacing an existing file, must do create-new-then-rename, rather than open(O_TRUNC). This is a core distinction between `/usr/bin/install` and `/usr/bin/cp`. Additionally, if your %post script is generated cached state derived purely from /usr content (e.g. ldconfig, gtk-update-icon-cache), please consider moving it to /usr, so that the cache state is stored with the data. The initial rpm-ostree implementation of %post is here: https://github.com/projectatomic/rpm-ostree/pull/338 [0] https://ostree.readthedocs.io/en/latest/manual/adapting-existing/ [1] https://github.com/ostreedev/ostree/blob/master/man/rofiles-fuse.xml
Also, rpm-ostree doesn't currently implement Lua, and we'd like to avoid doing so for as long as possible. For more information, see: http://lists.rpm.org/pipermail/rpm-ecosystem/2016-August/000391.html
This bug appears to have been reported against 'rawhide' during the Fedora 27 development cycle. Changing version to '27'.
https://src.fedoraproject.org/rpms/nfs-utils/pull-request/1
https://src.fedoraproject.org/rpms/mock/pull-request/2
ad #4 (the code in that PR will go away, but anyway) I do not get why /var/cache should be read only. That does not make sense to me.
(In reply to Miroslav Suchý from comment #5) > ad #4 (the code in that PR will go away, but anyway) I do not get why > /var/cache should be read only. That does not make sense to me. There's a bit more information at https://ostree.readthedocs.io/en/latest/manual/adapting-existing/ But to elaborate on that, in order to support reliable "offline" updates as well as rollbacks, we have a strict rule that the update system does *not* touch user data. /var is user data. We *do* support "rpm-ostree livefs" today which will run `systemd-tmpfiles` which will process /var - in the case of mock, rpm-ostree synthesizes a tmpfiles.d snippet. This is significantly more controlled than allowing arbitrary %post to write directly to /var. See also https://github.com/projectatomic/rpm-ostree/pull/888 and http://lists.rpm.org/pipermail/rpm-ecosystem/2017-July/000481.html
This bug appears to have been reported against 'rawhide' during the Fedora 28 development cycle. Changing version to '28'.
https://src.fedoraproject.org/rpms/plymouth/pull-request/1#
Another case here is that the `update-alternatives` system stores links in `/var`, which is wrong. They should be moved under `/usr`.
Want to add the following two too? bug #1702226 bug #1702233
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. 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 '28'. 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 28 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.
This is a tracker.. moving to rawhide.
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle. Changing version to '31'.
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle. Changing version to 31.
Switching back to rawhide since this is a running tracker.