rpmdb-migrate is a newly added (rpm >= 4.17.0-7) service which performs a rpm database rebuild at boot-time when /var/lib/rpm/.migratedb flag file exists (ie similar to rpmdb-rebuild service hooked on /usr/lib/sysimage/rpm/.rebuilddb). The immediate motivation is for performing database location migration for https://fedoraproject.org/wiki/Changes/RelocateRPMToUsr in a reasonably safe and controlled environment. * Does the service require post-rpm-installation configuration in order to be useful (for example, does it need manual edits to a configuration file)? No * Does the service listen on a network socket for connections originating on a separate physical or virtual machine? No * Is the service non-persistent (i.e. run once at startup and exit)? Yes * What is the exact name (or names) of the systemd unit files to be enabled? rpmdb-migrate.service * Is this request for all Fedora deliverables or only for some Editions (list them)? All
PR submitted: https://src.fedoraproject.org/rpms/fedora-release/pull-request/212
PR merged and released into Rawhide.
Hmm, should this service actually be enabled in the default presets? We already have a %triggerun scriptlet which enables it on upgraded systems: https://src.fedoraproject.org/rpms/rpm/blob/rawhide/f/rpm.spec#_435 I don't think it should be enabled on new systems, since those presumably have the database in the correct location. See https://bugzilla.redhat.com/show_bug.cgi?id=2262393.
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days