man-db 2.8.0

Milestone information

Project:
man-db
Series:
main
Version:
2.8.0
Released:
2018-02-04  
Registrant:
Colin Watson
Release registered:
2019-01-06
Active:
Yes. Drivers can target bugs and blueprints to this milestone.  

Download RDF metadata

Activities

Assigned to you:
No blueprints or bugs assigned to you.
Assignees:
No users assigned to blueprints and bugs.
Blueprints:
No blueprints are targeted to this milestone.
Bugs:
No bugs are targeted to this milestone.

Download files for this release

After you've downloaded a file, you can verify its authenticity using its MD5 sum or signature. (How do I verify a download?)

File Description Downloads
download icon man-db-2.8.0.tar.xz (md5, sig) man-db 2.8.0 1
last downloaded 19 weeks ago
Total downloads: 1

Release notes 

Fixes:
------

* Fix locale macro loading for Chinese to load the macro file
  corresponding to just the language part of the user's locale.

* Honour --enable-cache-owner in generated systemd tmpfiles snippet
  rather than hardcoding "man".

* If man adds prefixes to a page to handle such things as disabling
  hyphenation, then take account of those when looking for a
  preprocessor line at the start of the page.

* Fix a segfault in 'man -D --help'.

Improvements:
-------------

* Treat "\(en" as another synonym for "\-" in NAME sections.

* Confine most subprocesses that handle untrusted data using
  seccomp. This mainly deals with subprocesses that perform
  encoding conversions, (de)compressors, groff programs, and a few
  other odds and ends. groff programs use a slightly more
  permissive filter since they need to create temporary files, so
  additional path-based confinement (e.g. using AppArmor) is still
  useful.

  If this goes wrong, then MAN_DISABLE_SECCOMP=1 can be set in the
  environment to disable it, but please report any such problem as a
  bug.

* man now falls back to cat if the compile-time default pager is not
  executable.

Changelog 

This release does not have a changelog.

0 blueprints and 0 bugs targeted

There are no feature specifications or bug tasks targeted to this milestone. The project's maintainer, driver, or bug supervisor can target specifications and bug tasks to this milestone to track the things that are expected to be completed for the release.

This milestone contains Public information
Everyone can see this information.