git-doc: example source snippet is empty in technical/api-hashmap.html
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
git (Debian) |
Fix Released
|
Unknown
|
|||
git (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Anders Kaseorg reports[1]:
I noticed this warning while building git-doc:
ASCIIDOC technical/
/bin/sh: 1: source-highlight: not found
asciidoc: WARNING: api-hashmap.txt: line 218: filter non-zero exit code: source-highlight -f xhtml -s c: returned 127
asciidoc: WARNING: api-hashmap.txt: line 218: no output from filter: source-highlight -f xhtml -s c
(Actually, I noticed it because it’s fatal on very old Ubuntu releases,
but never mind that.) The effect is that the example source snippet under
‘Usage example’ in /usr/share/
up as empty. That snippet was added in v2.0.0-
This can be resolved by adding source-highlight as a build dependency.
[1] http://
This was fixed in Debian, but Ubuntu trusty reverted the fix:
git (1:2.0.
* debian/control: Drop source-highlight build dependency.
Unfortunately that changelog entry doesn't say why the fix was reverted.
Changed in git (Debian): | |
status: | Unknown → Fix Released |
Owww, I’m guessing it’s because Ubuntu doesn’t want a package in main (git) build-depending on a package in universe (source-highlight).
Options include /wiki.ubuntu. com/UbuntuMainI nclusionRequire ments); technical/ api-hashmap. txt;
• filing a main inclusion report for source-highlight (https:/
• patching the [source] tags out of Documentation/
• getting upstream to take that patch, which it probably should, given this failure mode;
• or just living with Ubuntu-forked packaging, and watching the Ubuntu version fall farther and farther behind (please please please not again).
Thinking out loud, this is not the first time I wish Debian had Build-Recommends.