Control: block 895462 by -1 I'm not sure that -1 is actually wishlist...
On Tue, May 08, 2018 at 03:14:47PM -0700, Jonathan Nieder wrote: > tags 898226 + upstream > # asciidoc is not gone yet :) > severity 898226 wishlist > quit > > Hi, > > Nicholas D Steeves wrote: > > > https://lists.debian.org/debian-backports/2018/05/msg00063.html > > > > src:git/1:2.17.0-1 Build-Depends on asciidoc (>= 8.6.10); however, > > in asciidoc/NEWS.Debian the following is advised: > > > > asciidoc (8.6.10-1) unstable; urgency=low > > > > The version 8.6.10 has been marked as FINAL RELEASE by the upstream > > maintainers. > > They advise their users to move to asciidoctor. > > See: https://github.com/asciidoc/asciidoc/releases > > Thanks for writing. If possible, I prefer to move to sphinx instead. > I'll start a conversation upstream. Yeah, I also prefer sphinx--much more powerful. On the upside, asciidoctor is really easy to switch to! I've heard a sed -i 's/asciidoc/asciidoctor/' debian/control is often all that is required. It also looks like upstream already supports Asciidoctor, given changelog entries such as these: debian/changelog.upstream 1427: Documentation: enable compat-mode for Asciidoctor 1432: Documentation: convert SubmittingPatches to AsciiDoc 3405: subtree: honour USE_ASCIIDOCTOR when set > [...] > > Consequently, to unblock an update of the existing stretch-backport of > > src:git it is preferable that src:git in sid transition to asciidoctor > > at this time, rather than creating a NEW stretch-backport of > > asciidoc/8.6.10-1. > > Backports should not require this --- git has built fine with older > versions of asciidoc before. I'm happy to work with anyone interested > in helping with the backport at [email protected]. Yes, it did :-) however, in this -backports thread Mert Dirik said that the asciidoc version bump allowed git to build reproducibly. ( https://lists.debian.org/debian-backports/2018/05/msg00063.html ) Given that 1) no-change bpos should be done whenever possible, and the sid branch should be modified to allow this, and 2) reproducibility is good, and both unstable and backports should be reproducible, it follows that 3) backport newer asciidoc to stretch or 4) transition to asciidoctor or 5) transition to sphinx is needed to continue to fulfill #1 and #2. Stretch has asciidoctor, but I haven't yet tested if it's new enough. CCing [email protected], but please reply to this bug, because I am not yet subscribed. Shall I go ahead and do the work to transition to Asciidoctor, or would you like to wait for upstream's response wrt sphinx? Cheers, Nicholas
signature.asc
Description: PGP signature
