See bug https://bugzilla.redhat.com/show_bug.cgi?id=2052433: mlocate conflicts with plocate, and on upgrades dnf refuses to upgrade without workarounds. The problem occurs because comps groups pull in plocate, so when the group is upgraded, dnf wants to pull in plocate. Comps groups pull in plocate, because this is what we want on new installations.
I'd like to add Obsoletes:mlocate to replace mlocate by plocate also on upgrades. The plan was to do this for F38, but the issue with group upgrades wasn't noticed. Also, this will make updated systems more like those newly installed, reducing support burden. I prefer this to coming up with some more complicated solution to fix the upgrade path.
Metadata Update from @bcotton: - Issue set to the milestone: Fedora Linux 36 - Issue tagged with: self contained change
+1
Can we bump the release of plocate in f36 to some arbitrary high value and only obsolete plocate < that version-release? That way, users are switched on upgrades, but they can still install dnf swap plocate with mlocate after if they really want to.
<
EDIT: I've also commented on the bugzilla.
Yes, we can certainly do that. The guidelines say to never use unversioned Obsoletes, so we'd have to put something above the current version of mlocate there anyway. So the part in your proposal that is new is to build mlocate with a yet-higher version. We can certainly do that. I'm not sure if it'll work as expected, but if it doesn't, we can bump the version in Obsoletes in plocate yet again and no harm done.
mlocate
plocate
The reason is that currently, mlocate has the more or less same release across Fedora versions. If we even need to bump it on F35/F34 (e.g. for a bugfix), we would need to change the Obsoletes tag in plocate. This way (with an artificially high Release), we would only ever need to change the Obsoletes tag if we bump mlocate in F35/F34 to a newer Version, which is unlikely to happen.
Anyway +1
I assume the plan would be to retire mlocate now then if you are completely obsoleting it? I suppose thats fine... +1
With Miro's proposal above, we should be able to keep mlocate available. I didn't confirm that it works as expected yet though.
+1 from me
OK, it's been a week. Fast-track fail.
APPROVED (+5, 0, 0)
Metadata Update from @zbyszek: - Issue tagged with: pending announcement
Announced.
Metadata Update from @zbyszek: - Issue untagged with: pending announcement - Issue close_status updated to: Accepted - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.