[Debian-med-packaging] Problem updating spades backport

[Sascha Steinbiss]

Oops, too early in the morning — missed the footnote link:

[1] https://anonscm.debian.org/cgit/debian-med/spades.git/commit/?h=ubuntu/3.7.1%2bdfsg-2_ubuntu14.04_ppa1&id=5d623b23b7c17ebea3c3b04bc9051a69489f56da

> On 30 Mar 2016, at 07:11, Sascha Steinbiss <satta at tetrinetsucht.de> wrote:
> 
> Hi Afif and Andreas,
> 
>> [Cc'ing Sascha and preserving original messages below in case he missed
>> this thread]
> 
> Indeed I did! Thanks for the explicit ping!
> 
>> على السبت 26 آذار 2016 ‫00:00، كتب Andreas Tille:
>>> Nit hat I have a clear preference but a third option would be to
>>> take over the readily rendered manpage inside the backport.
>> 
>> I'm not sure i understand what you mean, Andreas. Do you mean to
>> manually build the manpages and then include them in the debian/ directory?
> 
> This also works, of course. I prefer to automate such steps though so I only have to edit the human readable version of the manpage and don’t forget to update the actual manpage as well.
> 
>> I hadn't answered before because I was hoping for a comment from Sascha.
> 
> Sorry, as I said I just missed the thread. 
> Indeed asciidoctor only has manpage support since 1.5.3, which is a fairly new version. Nevertheless, it seemed to be a more future proof option for me than ronn (which has been without upstream support for ages and caused weird FTBFS on some platforms) and asciidoc (which is quite heavyweight with lots of XML processing).
> I indeed reverted the commit introducing asciidoctor for my spades backport to trusty [1] and that solved this problem. Reproducibility tests are not run on stable so I don’t think it’s that much of an issue there, also the other problems with ronn in I noticed in unstable did not seem to surface in jessie. I see this might be a bit more tedious to merge if the manpages change often in newer versions since the syntax used in the manpages is slightly different as well. 
> In this light I would rather try backporting asciidoctor 1.5.4 to jessie (it should only depend on Ruby) because I have switched manpage builds for most of my packages to asciidoctor now, and that would address this problem for good in the backports ;)
> 
> Cheers
> Sascha
> 
>>> On Fri, Mar 25, 2016 at 11:41:45PM -0700, Afif Elghraoui wrote:
>>>> Hi, Sascha,
>>>> Since the latest spades package just entered testing yesterday, I went
>>>> to rebuild it for jessie to update the backport.
>>>> 
>>>> Unfortunately, the build failed when generating the manpages:
>>>> 
>>>> make[1]: Leaving directory '/<<BUILDDIR>>/spades-3.7.1+dfsg'
>>>>  debian/rules override_dh_installman
>>>> make[1]: Entering directory '/<<BUILDDIR>>/spades-3.7.1+dfsg'
>>>> mkdir -p /<<BUILDDIR>>/spades-3.7.1+dfsg/debian/man
>>>> asciidoctor -a docdate='' -b manpage
>>>> /<<BUILDDIR>>/spades-3.7.1+dfsg/debian/man_src/*.adoc
>>>> Couldn't find a view in @views for document
>>>> Use --trace for backtrace
>>>> debian/rules:48: recipe for target 'override_dh_installman' failed
>>>> make[1]: *** [override_dh_installman] Error 1
>>>> 
>>>> 
>>>> It seems to me that the version of asciidoctor in jessie is too old for
>>>> this task (0.1.4-3 vs 1.5.4-1 in testing/unstable). I'm tempted to
>>>> revert your commit that replaced ronn with asciidoctor in the backports
>>>> branch, but since you did it for reproducibility reasons, I thought I
>>>> should get your opinion first. The alternative would be to backport the
>>>> newer asciidoctor to jessie or to use another tool that would work in
>>>> jessie. What do you think?
>>>> 
>>>> 
>>>> Thanks and regards
>>>> Afif
>>>> 
>