Don't skip adding a database entry due to SO_MAN

An existing `SO_MAN` entry shouldn't stop us considering a page for
insertion into the database, because until we run `ult_src` we don't yet
know whether that page will be `ULT_MAN` (which should replace the
existing entry) or `SO_MAN` (which shouldn't).

* src/check_mandirs.c (test_manfile): Don't return early due to an
existing matching `SO_MAN` entry, but only due to an `ULT_MAN` entry.
* NEWS.md: Document this.

1 files changed, 2 insertions, 0 deletions

diff --git a/NEWS.md b/NEWS.md
index 4440c5a1..af7c534f 100644
--- a/NEWS.md
+++ b/NEWS.md
@@ -13,6 +13,8 @@ Fixes:
    the correct type.
  * Store links in the database using the section and extension of the link
    rather than of the ultimate source file.
+ * Only skip adding a page to the database due to an existing entry if the
+   entry represents an ultimate source.
 
 Improvements: