Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#48047 - [docker] Docker man pages incorrectly formatted

Attached to Project: Community Packages
Opened by Tom Tobin (tomxtobin) - Friday, 05 February 2016, 15:13 GMT
Last edited by Sébastien Luttringer (seblu) - Sunday, 07 February 2016, 10:20 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Sébastien Luttringer (seblu)
Architecture All
Severity Very Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

# Description

Docker man pages are being formatted incorrectly because Arch's `go-md2man` package is out of date.


# Additional info

- Tested against Docker `1:1.10.0-1`
- `go-md2man` upstream is `1.0.5`; only `1.0.2` is available in Arch.
- `go-md2man` appears to be orphaned.


# Steps to reproduce

- Check, e.g., `/usr/share/man/man5/config-json.5.gz`
- Note the stray "item" words, and the incorrect formatting of the config.json sample.
- Compare to Docker's upstream `man/config-json.5.md`
- See the changes to `go-md2man` since `1.0.2` which appear to fix these issues.
This task depends upon

Closed by  Sébastien Luttringer (seblu)
Sunday, 07 February 2016, 10:20 GMT
Reason for closing:  Fixed
Additional comments about closing:  1:1.10.0-4
Comment by Tom Tobin (tomxtobin) - Friday, 05 February 2016, 15:16 GMT
I should've marked this as "Very Low" severity, since it's documentation.

(And Flyspray doesn't use Markdown, eh? Oops.)
Comment by Tom Tobin (tomxtobin) - Saturday, 06 February 2016, 15:33 GMT
The incorrect man page formatting still appears in docker 1:1.10.0-3. The updated version of go-md2man (1.05) is now available in Arch, though, and it correctly formats the upstream man pages when used.
Comment by Doug Newgard (Scimmia) - Saturday, 06 February 2016, 15:33 GMT
Looking at the .BUILDINFO file in the -3 package, it was indeed built with go-md2man 1.02.
Comment by Sébastien Luttringer (seblu) - Saturday, 06 February 2016, 17:09 GMT
I built manually -2 against go-md2man 1.5 and then I pushed go-md2man to our repo.
When I built the -3 the repo sync was not done yet. Damn.

-4 should be ok.

Comment by Tom Tobin (tomxtobin) - Saturday, 06 February 2016, 18:11 GMT
Just updated to -4 and it looks good here. Thanks!

Loading...