man-db 2.8.4

Milestone information

Project:
man-db
Series:
main
Version:
2.8.4
Released:
2018-07-27  
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.4.tar.xz (md5, sig) man-db 2.8.4 1
last downloaded 36 weeks ago
Total downloads: 1

Release notes 

Fixes:
------

* Rely on decompressors reading from their standard input rather
  than redundantly passing them the input file on their command
  line. This works better with downstream AppArmor confinement of
  decompressors.

* Fix invalid syntax in tmpfiles.d/man-db.conf when configured with
  --disable-cache-owner.

* Make seccomp sandbox allow sched_getaffinity, sometimes used by
  xz.

* Check for mandb_nfmt and mandb_tfmt in the manual page hierarchy
  as documented, not in the current directory. This was broken by
  the working-directory-handling changes in 2.8.3. Note that this
  change means that "man -l" will never use an external formatter
  (which was never documented behaviour and was surely a bad idea).

* Make seccomp sandbox allow some shared memory operations across
  the board rather than just when ESET File Security is in use; the
  Astrill VPN seems to require something similar, and there are
  doubtless other such preload hacks.

* Some versions of ESET File Security call msgget and msgsnd; if
  this program is in use, then allow those.

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.