Date: Sat, 28 Jan 2017 16:32:44 -0500 From: Derek Schrock <dereks@lifeofadishwasher.com> To: Matthew Seaman <matthew@FreeBSD.org> Cc: freebsd-questions@freebsd.org Subject: Re: freebsd-update fetch Message-ID: <20170128213244.GA45064@ircbsd.lifeofadishwasher.com> In-Reply-To: <4a020ce7-16c0-5c0e-17e9-51632fb6edd2@FreeBSD.org> References: <1485035504.85963.6.camel@yandex.com> <4a020ce7-16c0-5c0e-17e9-51632fb6edd2@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Jan 21, 2017 at 05:27:32PM EST, Matthew Seaman wrote: > On 21/01/2017 21:51, Stari Karp wrote: > > My system is FreeBSD 11.0_RELEASE-p7 (amd64). > > I have today (the third time in 3 weeks) when I run freebsd-update > > fetch: > > The following files will be updated as part of updating to FreeBSD > > 11.0-RELEASE-p7: > > > > /usr/share/man/mandoc.db > > /usr/share/openssl/man/mandoc.db > > > > Is this security update or something is wrong on my system? Usually is > > some email about update. > > No -- this is a bug in freebsd-update(8). The mandoc.db files are > supplied as part of the base system install, but it seems freebsd-update > is not managing to update them correctly. This is pretty harmless > though -- the mandoc.db files are used by apropos(1) to show a summary > of the man pages in those sections. All it means is that the database > of manpages may be slightly out of date. > > I think you may be able to simply move aside the existing mandoc.db > files, and then run 'freebsd-update fetch install' to replace them with > pristine copies of the latest versions. I haven't tried that though. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213762
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20170128213244.GA45064>