Installed man-db 2.3.18-3 (i386 source)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.7
Date: Sat, 19 May 2001 19:29:39 +0100
Source: man-db
Binary: man-db
Architecture: source i386
Version: 2.3.18-3
Distribution: unstable
Urgency: low
Maintainer: Colin Watson <cjwatson@debian.org>
Changed-By: Colin Watson <cjwatson@debian.org>
Description:
man-db - Display the on-line manual.
Closes: 17735 42128 42479 42791 47000
Changes:
man-db (2.3.18-3) unstable; urgency=low
.
* So, I flame Peter T. Breuer on Usenet for his bug report being several
bugs rolled up into one and being full of flamage itself. Then I think,
well, since I'm ranting about it, I may as well see if I can fix it. Of
course, it now turns out that fixing that was key to a load of other
bugs. So I apologize to Peter and promise, again, to write the code
before spouting off in future. :)
* If opening a database or a cat page fails due to a lack of permissions
(e.g. a read-only partition), recover gracefully and only complain about
it in debug mode (addresses part of bug #47000).
* Improved documentation of MANDB_MAP directives in /etc/manpath.config
(addresses the other part of that bug, so closes: #47000).
.
* Once man and mandb don't complain about certain classes of permission
problems, it becomes easy to install them non-setuid. Since in this mode
man can't write cat pages or update the database on the fly, non-setuid
is the default but a debconf question asks whether to install them
setuid. I hope this meets the concerns about man-db's security policy
(closes: #42128).
* As well as the above, the recent security updates should have made sure
that man and mandb drop privileges at the right times, and so can read
privately-owned directories (closes: #42479, #42791).
* In non-setuid mode there's no need to use the root-squashing wrapper.
I'm not going to close related bugs yet, as they're still present for
those who install setuid; I still intend to split the setuid stuff out
into a separate process and remove the wrapper entirely.
* The postinst and cron.weekly now explicitly su to man to run mandb,
since the wrapper might not be present.
* If searching for a page in the database returns no output, check the
filesystem anyway, as the database might not be up to date.
.
* Tidied up parsing of multiple whatis keys in .SH NAME sections, so that
each separate name gets assigned its own whatis entry correctly.
Separating items in the NAME section with newlines remains unsupported,
as at the moment man pages can get away with spreading their whatis
description over multiple lines and I'd rather not break them
gratuitously. However, multiple items will be recognized (and have been
for a long time, albeit brokenly up to now) if they are separated by a
.br (break) request. *roff doesn't normally do much with newlines in the
middle of paragraphs in its input, so this is consistent. See bug #97916
for more details (closes: #17735).
.
* Updated tools/config.sub to know about the sh/sheb architectures.
Files:
7942e5064d61141a7085f1abe091cb1d 731 doc important man-db_2.3.18-3.dsc
58e05ef203d67beabb11589cceedf336 30698 doc important man-db_2.3.18-3.diff.gz
8a00db535e6a8ae0bd610830e3db676d 333320 doc important man-db_2.3.18-3_i386.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.5 (GNU/Linux)
Comment: Colin Watson <cjwatson@debian.org> -- Debian GNU/Linux developer
iD8DBQE7Bsj9MVrRHkkXpRQRAnnzAJ9pP7kkLJwpC8daqizIzVxSpWgcoACfZvrG
+AqjJJFVjuwyuKXHhe1x150=
=HFRW
-----END PGP SIGNATURE-----
Installed:
man-db_2.3.18-3.diff.gz
to pool/main/m/man-db/man-db_2.3.18-3.diff.gz
man-db_2.3.18-3.dsc
to pool/main/m/man-db/man-db_2.3.18-3.dsc
man-db_2.3.18-3_i386.deb
to pool/main/m/man-db/man-db_2.3.18-3_i386.deb
Reply to: