# an FTBFS on a non-release architecture is "important" severity 956041 important thanks
On Wed, 8 Apr 2020, Faidon Liambotis wrote: > Indeed, creating a separate package for two manpages is indeed a not a > great investment of time and resources -- not to mention a policy > violation¹ :) Yeah… just a “should”, but still. > I'd prefer to not have to carry a Debian-specific patch that changes the > build system for upstream's documentation. Implementing a simple > Markdown parser for the few elements the docs have right now (sections > and URLs mostly) in shell seems within reach, but it would be > error-prone with regards to any future modifications of those documents. > Breakages would likely slip through and I wouldn't even notice until a > bug report came in. True. > That said, if the patch is upstreamable, I'd encourage you to submit it > directly to upstream². Assuming it gets merged in some way or form, I > wouldn't mind backporting it before upstream tagged a release. This sounds sensible, if upstream is amenable to merging it, at least as an alternative. Do you have working relationship with upstream and could test the waters, so to speak, whether they would merge it, or, alternatively, accept a one-shot manual conversation of the manpages? Thanks, //mirabilos -- tarent solutions GmbH Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/ Tel: +49 228 54881-393 • Fax: +49 228 54881-235 HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941 Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg
