On Tue, 2019-02-26 at 13:43 +0100, Ralf Mardorf wrote:

On Tue, 2019-02-26 at 14:33 +0200, Edvinas Valatka via arch-general wrote:

...

On Tue, Feb 26, 2019 at 8:57 AM David C. Rankin wrote:

...

This was odd,

$ apropos memcmp memcmp: nothing appropriate.

In fact, no man pages were available (checked 2 arch installs). I ended up having to rebuild the database with 'mandb' and now all is well.

My question is -- what did this? It must have occurred in the last couple of days.

After https://git.archlinux.org/svntogit/packages.git/commit/trunk?h=packages/man-db&id=a296a036a34944f714488f43bf576cca58bda604 , you have to manualy enable man-db.timer

Seemingly not ;), see

[rocketmouse@archlinux ~]$ systemctl status man-db.service ● man-db.service - Daily man-db regeneration Loaded: loaded (/usr/lib/systemd/system/man-db.service; static; vendor preset: disabled) Active: inactive (dead) Docs: man:mandb(8) [rocketmouse@archlinux ~]$ sudo systemctl enable man-db.service [sudo] password for rocketmouse: The unit files have no installation config (WantedBy=, RequiredBy=, Also=, Alias= settings in the [Install] section, and DefaultInstance= for template units). This means they are not meant to be enabled using systemctl.

Possible reasons for having this kind of units are: • A unit may be statically enabled by being symlinked from another unit's .wants/ or .requires/ directory. • A unit's purpose may be to act as a helper for some other unit which has a requirement dependency on it. • A unit may be started when needed via activation (socket, path, timer, D-Bus, udev, scripted systemctl call, ...). • In case of template units, the unit is meant to be enabled with some instance name specified.

My apologies. it's "timer" not "service" :D. [rocketmouse@archlinux ~]$ systemctl status man-db.timer ● man-db.timer - Daily man-db regeneration Loaded: loaded (/usr/lib/systemd/system/man-db.timer; disabled; vendor preset: disabled) Active: inactive (dead) Trigger: n/a Docs: man:mandb(8) [rocketmouse@archlinux ~]$ sudo systemctl enable man-db.timer Created symlink /etc/systemd/system/timers.target.wants/man-db.timer → /usr/lib/systemd/system/man-db.timer. [rocketmouse@archlinux ~]$ systemctl status man-db.timer ● man-db.timer - Daily man-db regeneration Loaded: loaded (/usr/lib/systemd/system/man-db.timer; enabled; vendor preset: disabled) Active: inactive (dead) Trigger: n/a Docs: man:mandb(8)

On 2/26/19 1:13 PM, David C. Rankin wrote:

On 02/26/2019 06:33 AM, Edvinas Valatka via arch-general wrote:

...

After https://git.archlinux.org/svntogit/packages.git/commit/trunk?h=packages/man-db&id=a296a036a34944f714488f43bf576cca58bda604 , you have to manualy enable man-db.timer

+# probably not required +# install -d -m755 ${pkgdir}/usr/lib/systemd/system/multi-user.target.wants +# ln -s ../man-db.timer ${pkgdir}//usr/lib/systemd/system/multi-user.target.wants/man-db.timer

That would then seem to be an update that requires user-intervention and have some note listed on https://www.archlinux.org/.

The most recent note under "Latest News" is getting quite stale.

I scan the pacman Upgrade output and don't recall seeing a note there either.

I don't see the logic in not enabling the timer by default. If the man pages are installed, they need to be usable without further user intervention. It would make more sense to have the people that DON'T want to use the man pages disable the timer rather than force everybody who wants working man pages to enable it. Otherwise RTFM means little if they are broken.

It is not a news item and it is not a "you have to manually enable basic system functionality", it is a bug report. Although I have been using Graysky's mandb-ondemand timer for long enough that I guess I did not notice this myself. Actually ISTR an IRC conversation with another packager, who discovered the same thing and who said he would get in touch with the the mandb maintainer about this. -- Eli Schwartz Bug Wrangler and Trusted User