On 2023-10-04 14:52, Patrick Shanahan wrote:

* Pit Suetterlin via openSUSE Users [10-04-23 08:46]:

...

Hi List,

I just DUPed my Tumbleweed to 20231001, which obvioiusly force-switched me from mlocate to plocate. Unfortunately, not a clean switch, as after reboot locate fails with

/var/lib/plocate/plocate.db: No such file or directory

Investigating further shows

woodstock:~ # systemctl status plocate-updatedb.service ○ plocate-updatedb.service - Update the locate database Loaded: loaded (/usr/lib/systemd/system/plocate-updatedb.service; static) Active: inactive (dead) Docs: man:updatedb woodstock:~ # systemctl status plocate-updatedb.timer ○ plocate-updatedb.timer - Daily locate database update Loaded: loaded (/usr/lib/systemd/system/plocate-updatedb.timer; disabled; preset: disabled) Active: inactive (dead) Trigger: n/a Triggers: ● plocate-updatedb.service Docs: man:updatedb

Not too nice to replace a working setup with a disabled one :(

found same and was also disappointed.

but a simple "updatedb" creates the needed db and allows plocate/locate to function as before.

You still need to enable the timer. -- Cheers / Saludos, Carlos E. R. (from openSUSE 15.5 (Laicolasse))

On 10/4/23 13:55, Pit Suetterlin via openSUSE Users wrote:

Carlos E. R. wrote:

...

On 2023-10-04 14:52, Patrick Shanahan wrote:

...

found same and was also disappointed.

but a simple "updatedb" creates the needed db and allows plocate/locate to function as before.

You still need to enable the timer.

Indeed, *and* start it ;^>

systemctl enable plocate-updatedb.timer systemctl start plocate-updatedb.timer

Hmm, As I eye a test of tumbleweed, do we have a place where updates requiring "User Interaction" are listed when these type of updates come out? (other than factory?) Like a tumbleweed page where at the top, a list of these type package updates are listed in chronological order (only need to keep the last 60 days worth or so -- which should only be a handful or so)? That type of info is really helpful. -- David C. Rankin, J.D.,P.E.

On Fri, 6 Oct 2023 22:01, David C. Rankin wrote:

On 10/4/23 07:52, Patrick Shanahan wrote:

...

found same and was also disappointed. but a simple "updatedb" creates the needed db and allows plocate/locate to function as before.

I've read the entire thread and still have not seen a reason as to "Why?" this was done.

The issue to me is if I want mlocate installed instead of plocate, why isn't that fine? Why are we now sticking "obsoletes" in spec files to force the user to change packages?

This seems like something that would be better as a notice or recommendation when mlocate is updated (not the technical zypper "recommends"), but a simple text output (or yast summary) of "plocate is recommended instead of mlocate, change packages (n/Y)?" Much like zypper/yast does for repo changes for packages.

Obviously, "obsoletes" makes sense if mlocate has a security problem and is no longer maintained upstream, but I haven't seen that as the reason.

So "Why?" is plocate replacing mlocate, and can there be a notice and choice given to the user?

In short, & in part: 1a. mlocate code is stale and has been so for quite some time. (Thankfully no security issues have been found so far) 1b. plocate code is active in maintainance and development. 2. plocate user side (locate cmd) is a good deal faster than that of mlocate, even and esp. on older hardware. 3. comparing plocate and mlocate user side shows little difference, low learning curve on swap. (other alternatives differ more, or much more) - Yamaban.

Knurpht-openSUSE wrote:

Op woensdag 4 oktober 2023 23:48:27 CEST schreef Bjoern Voigt via openSUSE

...

But why Tumbleweed 2031001 forced you to switch to plocate? mlocate is still available and in my case "zypper dup" did not switch from mlocate to plocate.

Same here

Interesting. Not sure what triggered it. I definitely only did a normal dup. And zypper.log confirms that mlocate was uninstalled, and plocate installed. But yes, mlocate also here still is listed as available from the main repo Is there a way to find out 'post mortem' why zypper decided to switch? At least, if I try to install it again I get Problem: the installed plocate-1.1.19-1.1.x86_64 obsoletes 'mlocate < 6.1.1.19-1.1' provided by the to be installed mlocate-0.26-34.1.x86_64 So the question seems rather why it's not been removed on your systems ;^>

On 05.10.23 01:10, Patrick Shanahan wrote:

...

Problem: the installed plocate-1.1.19-1.1.x86_64 obsoletes 'mlocate < 6.1.1.19-1.1' provided by the to be installed mlocate-0.26-34.1.x86_64

So the question seems rather why it's not been removed on your systems ;^> "obsoletes" may be the answer ???

Something is wrong with "obsoletes 'mlocate < 6.1.1.19-1.1'". The latest release of mlocate is 0.26. See https://pagure.io/mlocate/releases Maybe it's really a good idea to obsolete mlocate. There are no new mlocate releases since many years. Björn

On Wed, 04 Oct 2023 23:53:47 +0200, Knurpht-openSUSE wrote:

Op woensdag 4 oktober 2023 23:48:27 CEST schreef Bjoern Voigt via openSUSE Users:

...

But why Tumbleweed 2031001 forced you to switch to plocate? mlocate is still available and in my case "zypper dup" did not switch from mlocate to plocate.

#zypper search --details "*locate"

...

S  | Name         | Type       | Version     | Arch   | Repository ---+--------------+------------+-------------+--------+-------------      | libfallocate | srcpackage | 0.1.1-17.19 | noarch | repo-src-oss i+ | mlocate      | package    | 0.26-34.1   | x86_64 | repo-oss      | mlocate      | srcpackage | 0.26-34.1   | noarch | repo-src-oss      | plocate      | package    | 1.1.19-1.1  | x86_64 | repo-oss      | plocate      | srcpackage | 1.1.19-1.1  | noarch | repo-src-oss

Same here S  | Name                      | Summary                                                     | Type ---+--------------------------- +------------------------------------------------------------+------- [...] i+ | mlocate                   | A utility for finding files by name                         | pakket i  | mlocate-lang              | Translations for package mlocate                            | pakket     | plocate                   | A much faster locate(1)                                     | pakket [...]

Could it be that mlocate is only replaced if it was automatically installed?  Like both of you, I explicitly installed mlocate, and it was not replaced by plocate.  (User-installed indicated by "i+"):   $ zypper se '*locate'   S  | Name    | Summary                             | Type   ---+---------+-------------------------------------+--------   i+ | mlocate | A utility for finding files by name | package      | plocate | A much faster locate(1)             | package Is there a way to change the 'automatically installed' flag? -- Robert Webb

On Fri, 6 Oct 2023 09:11:29 +0000 (UTC), Robert Webb via openSUSE Users wrote: [Regarding whether 'zypper dup' installs plocate]]

Could it be that mlocate is only replaced if it was automatically installed?  [...]

The answer is no.  It does not depend on the auto-installed status of mlocate.  Even 'zypper install plocate' requires the user-directed de-installation of mlocate, in cases like mine, whether or not mlocate was auto-installed. First, mlocate was user-installed:   # zypper se '*locate'   S  | Name    | Summary                             | Type   ---+---------+-------------------------------------+--------   i+ | mlocate | A utility for finding files by name | package      | plocate | A much faster locate(1)             | package   #   # zypper in -D --details plocate   Loading repository data...   Reading installed packages...   Resolving package dependencies...   Problem: the installed mlocate-lang-0.26-34.1.noarch requires 'mlocate = 0.26',   but this requirement cannot be provided    Solution 1: deinstallation of mlocate-lang-0.26-34.1.noarch    Solution 2: do not install plocate-1.1.19-1.1.x86_64    Solution 3: break mlocate-lang-0.26-34.1.noarch by ignoring some of its dependencies   Choose from above solutions by number or cancel [1/2/3/c/d/?] (c): 1   Resolving dependencies...   Resolving package dependencies...   The following NEW package is going to be installed:     plocate  1.1.19-1.1  x86_64  Main Repository (OSS)  openSUSE   The following 2 packages are going to be REMOVED:     mlocate       0.26-34.1  x86_64  openSUSE     mlocate-lang  0.26-34.1  noarch  openSUSE   1 new package to install, 2 to remove.   Overall download size: 162.9 KiB. Already cached: 0 B. After the operation,   additional 140.9 KiB will be used.   Continue? [y/n/v/...? shows all options] (y): n   # Then: On Fri, 6 Oct 2023 12:38:53 +0300, Andrei Borzenkov wrote:

On 06.10.2023 12:11, Robert Webb via openSUSE Users wrote:

...

Is there a way to change the 'automatically installed' flag?

Remove package from /var/lib/zypp/AutoInstalled

So, I *added* "mlocate" to the file to change its status the other way. Second, with mlocate now as auto-installed:   # zypper se '*locate'   S | Name    | Summary                             | Type   --+---------+-------------------------------------+--------   i | mlocate | A utility for finding files by name | package     | plocate | A much faster locate(1)             | package The result of 'zypper in -D --details plocate' does not change. -- Robert Webb