This is a tracking bug for Change: Relocate RPM database to /usr For more details, see: https://fedoraproject.org/wiki/Changes/RelocateRPMToUsr Currently, the RPM databases is located in /var. Let's move it to /usr. The move is already under way in rpm-ostree-based installations, and in (open)SUSE. If you encounter a bug related to this Change, please do not comment here. Instead create a new bug and set it to block this bug.
PR to rpm made: https://src.fedoraproject.org/rpms/rpm/pull-request/21
PR merged and released into Rawhide
This bug appears to have been reported against 'rawhide' during the Fedora Linux 36 development cycle. Changing version to 36.
*** Bug 1847619 has been marked as a duplicate of this bug. ***
We have reached the 'Change complete (100% complete)' deadline in the Fedora Linux 36 release schedule. At this time, all Changes should be fully complete. Indicate this by setting this tracking bug to ON_QA. If you need to defer this Change to a subsequent release, please needinfo me.
Proposed as a Blocker for 36-final by Fedora user chrismurphy using the blocker tracking app because: https://fedoraproject.org/wiki/Changes/RelocateRPMToUsr NOTE: the bug does not affect upgrades, just new clean installs. A condition of the change is there should be a symlink /var/lib/rpm -> /usr/lib/sysimage/rpm and the change does block release. We're past freeze so the contingency probably doesn't apply. Since the missing symlink isn't breaking any dnf or PackageKit functionality, or seemingly anything else out of the box, I think we're on solid ground saying "well it's a beta" and documenting this in common bugs. And making this a final blocker, so that's what I'm proposing.
Darn, wrong bug! Undo!
Bull in a china shop today...
F36 was released today. If this Change did not land in the release, please notify bcotton as soon as possible.
What's the rationale for the move to /usr ? The purpose of /var was/is to get host-dependent files out of /usr (originally, so /usr could be read-only and shared amongst diskless machines). Having separate filesystems for /var (volatile) and /usr (relatively stable) still seems like a good idea, if just for accountability.
(In reply to Bruce Jerrick from comment #10) > What's the rationale for the move to /usr ? ... Thinking about this some more, the rpmdb is closer-tied to the contents of /usr than to the logs, etc. of a specific machine. But I hope there's not a trend to move /var back to /usr .
(In reply to Bruce Jerrick from comment #11) > (In reply to Bruce Jerrick from comment #10) > > What's the rationale for the move to /usr ? ... > > Thinking about this some more, the rpmdb is closer-tied to the contents of > /usr than to the logs, etc. of a specific machine. > But I hope there's not a trend to move /var back to /usr . Nah, it's just the rpmdb and in the future the dnfdb. The rest is staying where it is.