Bug#915560: [Pkg-nagios-devel] Bug#915560: icinga2-doc: Please provide HTML documentation in icinga2-doc

2018-12-05 Thread Sebastiaan Couwenberg
On 12/5/18 2:04 PM, Lee Garrett wrote: > Also, https://icinga.com/docs/ is of limited use for Debian, as it always > points to the latest icinga2 version, which does not match the feature set and > version shipped in Debian. You filed this issue for the backports version, which should keep up

Bug#915560: [Pkg-nagios-devel] Bug#915560: icinga2-doc: Please provide HTML documentation in icinga2-doc

2018-12-05 Thread Lee Garrett
On 05/12/2018 13:05, Sebastiaan Couwenberg wrote: > On 12/5/18 11:50 AM, Lee Garrett wrote: >> I know of upstream's documentation page. It would be great to have the >> documentation offline, though, as there are many reasons why you'd want to >> read the documentation but don't have internet

Bug#915560: [Pkg-nagios-devel] Bug#915560: icinga2-doc: Please provide HTML documentation in icinga2-doc

2018-12-05 Thread Sebastiaan Couwenberg
On 12/5/18 11:50 AM, Lee Garrett wrote: > I know of upstream's documentation page. It would be great to have the > documentation offline, though, as there are many reasons why you'd want to > read the documentation but don't have internet access. Right now icinga2-doc > is not useful as it is.

Bug#915560: [Pkg-nagios-devel] Bug#915560: icinga2-doc: Please provide HTML documentation in icinga2-doc

2018-12-05 Thread Lee Garrett
Hi Sebastian, I know of upstream's documentation page. It would be great to have the documentation offline, though, as there are many reasons why you'd want to read the documentation but don't have internet access. Right now icinga2-doc is not useful as it is. It should be fairly

Bug#915560: icinga2-doc: Please provide HTML documentation in icinga2-doc

2018-12-04 Thread Lee Garrett
Package: icinga2-doc Version: 2.10.1-3~bpo9+1 Severity: normal Hi, currently icinga2-doc ships all documentation as *.md.gz. This is impractical. It would be great if icinga2-doc shipped HTML files generated from the markdown to point your local browser to. Alternatively you could provide