On Sat, Oct 29, 2022 at 10:49 AM Orion Poplawski <orion@xxxxxxxx> wrote: > > On 10/28/22 22:53, Todd Zullinger wrote: > > Hi, > > > > Richard W.M. Jones wrote: > >> https://bugzilla.redhat.com/show_bug.cgi?id=2042147#c2 > >> https://fedoraproject.org/wiki/Changes/RelocateRPMToUsr > >> https://bugzilla.redhat.com/2042099 > >> > >> The RPM database is supposed to move from /var/lib/rpm to > >> /usr/lib/sysimage/rpm. This was supposed to happen automatically when > >> you upgraded the rpm package from an earlier version to 4.17.0-10.fc36 > >> (Feb-Mar 2022). > >> > >> On several machines it is reported that the migration was only half- > >> completed. The symptoms are that the RPM database is still in > >> /var/lib/rpm (/usr contains symlinks to it). See typical output from > >> failed & successful migrations at the end of the email. > >> > >> So _if_ you have rpm >= 4.17.0-10.fc36 installed: > >> > >> - Do you see the symptom of a failed migration? Or does it appear > >> to be successful? (Or neither case??) > >> > >> - Did you: > >> * Install F37 or Rawhide from scratch? > >> * Upgrade using ordinary dnf update or similar? > >> * Upgrade using dnf system-upgrade? > >> * Some other install/upgrade method? > > > > I upgraded two systems from f35 to f36 in the past week via > > dnf system-upgrade. Neither of them completed the rpm > > migration. > > > > I _think_ the issue is due to the version-release in the > > %triggerun which should enable the rpmdb-migrate service. > > That is: > > > > %triggerun -- rpm < 4.17.0-7 > > # Handle rpmdb migrate service on erasure of old to avoid ordering issues > > if [ -x /usr/bin/systemctl ]; then > > systemctl --no-reload preset rpmdb-migrate ||: > > fi > > > > That was accurate when it was added in 0b9f813 (Migrate > > rpmdb to /usr/lib/sysimage/rpm (#2042099), 2022-01-26). > > > > However, when rpm was updated in f35 in e9927df (Rebase to > > rpm 4.17.1 (http://rpm.org/wiki/Releases/4.17.1), > > 2022-07-01), which never had the migration code, it > > prevented any up-to-date f35 system from triggering the > > migration. > > > > Anyone upgrading from f35 after rpm-4.17.1 was pushed to > > f35 won't have the rpmdb-migrate service enabled and the > > database will remain in /var/lib/rpm (with .migratedb) and > > symlinks in /usr/lib/sysimage/rpm. > > > > It seems that it's not so much a failed migration as a > > migration which is never attempted. :/ > > Likely in certain situations. > > What I don't understand is why all the trickery around enabling the > service - why not just enable it unconditionally? It already has a > condition: > I was being careful because I wasn't initially sure what approach I'd use. It changed a couple of times. It can probably change now to be unconditional activation during install/upgrade of rpm, though. -- 真実はいつも一つ！/ Always, there's only one truth! _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
