← Back to team overview

kicad-developers team mailing list archive

Re: asciidoc

 

Yes - I had to refresh my token too.  By the way, below is a link to the copr test build I made (in my private copr) - it passed :-)

https://copr.fedorainfracloud.org/coprs/stevenfalco/kicad/build/2215757/

	Steve

On 6/3/21 4:32 PM, Nick Østergaard wrote:
Ah,ok, I misread the pipeline logs..

Error: Login invalid/expired. Please visit https://copr.fedorainfracloud.org/api <https://copr.fedorainfracloud.org/api> to get or renew your API token.

I gotta update that.

On Thu, 3 Jun 2021 at 22:29, Steven A. Falco <stevenfalco@xxxxxxxxx <mailto:stevenfalco@xxxxxxxxx>> wrote:

    The build you are looking at happened before I put in the fix.  In other words, I saw that same build failure (on May 30), and put in the fix a few hours later.

    The next doc build should use rubygem-asciidoctor in place of asciidoc, and it should pass.

    Can you kick off a manual build of the docs to test that?

             Steve

    On 6/3/21 3:26 PM, Nick Østergaard wrote:
     > @Steven A. Falco <mailto:stevenfalco@xxxxxxxxx <mailto:stevenfalco@xxxxxxxxx>>
     >
     > Did you have a look at building the docs for fedora with the other package?
     >
     > It appears to still BuildRequires: asciidoc when I look in the spec file in https://copr.fedorainfracloud.org/coprs/g/kicad/kicad/build/2215751/ <https://copr.fedorainfracloud.org/coprs/g/kicad/kicad/build/2215751/> <https://copr.fedorainfracloud.org/coprs/g/kicad/kicad/build/2215751/ <https://copr.fedorainfracloud.org/coprs/g/kicad/kicad/build/2215751/>>
     >
     > On Sun, 30 May 2021 at 22:51, Jon Evans <jon@xxxxxxxxxxxxx <mailto:jon@xxxxxxxxxxxxx> <mailto:jon@xxxxxxxxxxxxx <mailto:jon@xxxxxxxxxxxxx>>> wrote:
     >
     >     If you use Docker, there is also a container for the docs build based on Debian:
     >
     > https://gitlab.com/kicad/services/kicad-doc/-/blob/master/utils/docker/Dockerfile.kicad-doc-builder-base <https://gitlab.com/kicad/services/kicad-doc/-/blob/master/utils/docker/Dockerfile.kicad-doc-builder-base> <https://gitlab.com/kicad/services/kicad-doc/-/blob/master/utils/docker/Dockerfile.kicad-doc-builder-base <https://gitlab.com/kicad/services/kicad-doc/-/blob/master/utils/docker/Dockerfile.kicad-doc-builder-base>>
     >
     >     Maybe this is also helpful for setting up a Fedora VM or Docker container
     >
     >     On Sun, May 30, 2021 at 3:00 PM Steven A. Falco <stevenfalco@xxxxxxxxx <mailto:stevenfalco@xxxxxxxxx> <mailto:stevenfalco@xxxxxxxxx <mailto:stevenfalco@xxxxxxxxx>>> wrote:
     >      >
     >      > I'll have to spin up a VM to play with that.  I'll get back to you... :-)
     >      >
     >      >         Steve
     >      >
     >      > On 5/30/21 2:34 PM, Jon Evans wrote:
     >      > > You want this one: https://github.com/Mogztter/asciidoctor-web-pdf <https://github.com/Mogztter/asciidoctor-web-pdf> <https://github.com/Mogztter/asciidoctor-web-pdf <https://github.com/Mogztter/asciidoctor-web-pdf>>
     >      > >
     >      > > On Ubuntu I install it with "sudo npm i -g @asciidoctor/core asciidoctor-pdf"
     >      > >
     >      > > On Sun, May 30, 2021 at 2:33 PM Steven A. Falco <stevenfalco@xxxxxxxxx <mailto:stevenfalco@xxxxxxxxx> <mailto:stevenfalco@xxxxxxxxx <mailto:stevenfalco@xxxxxxxxx>>> wrote:
     >      > >>
     >      > >> I'm able to build the html pages, which is all we need for the nightlies, but I am not able to build the pdf files.  I get an error:
     >      > >>
     >      > >>           Could NOT find ASCIIDOCTORPDF (missing: ASCIIDOCTORPDF_COMMAND)
     >      > >>
     >      > >> It looks like CMakeModules/FindASCIIDOCTORPDF.cmake wants a program called "asciidoctor-web-pdf".
     >      > >>
     >      > >> Fedora has a package "rubygem-asciidoctor-pdf" which provides a program called "asciidoctor-pdf".
     >      > >>
     >      > >> I don't know if "asciidoctor-pdf" is equivalent to "asciidoctor-web-pdf".  If it is, then perhaps the cmake file should accept either one.
     >      > >>
     >      > >>          Steve
     >      > >>
     >      > >> On 5/30/21 1:58 PM, Steven A. Falco wrote:
     >      > >>> Thanks Jon.
     >      > >>>
     >      > >>> I'm running a test build now.  If it passes, I'll propose a patch for the README.  I'll also push the change to the nightly Fedora builds.
     >      > >>>
     >      > >>>       Steve
     >      > >>>
     >      > >>> On 5/30/21 1:51 PM, Jon Evans wrote:
     >      > >>>> Hi Steve,
     >      > >>>>
     >      > >>>> As the readme notes, I have not yet updated the docs for Fedora or
     >      > >>>> Manjaro/Arch as I don't use those distros and am not sure of the right
     >      > >>>> incantations.
     >      > >>>>
     >      > >>>> If you can advise what should go into the README I'm happy to update it.
     >      > >>>>
     >      > >>>> Also, please let me know if you run into any snags building the docs
     >      > >>>> with the new toolchain.
     >      > >>>>
     >      > >>>> Best,
     >      > >>>> Jon
     >      > >>>>
     >      > >>>> On Sun, May 30, 2021 at 1:49 PM Steven A. Falco <stevenfalco@xxxxxxxxx <mailto:stevenfalco@xxxxxxxxx> <mailto:stevenfalco@xxxxxxxxx <mailto:stevenfalco@xxxxxxxxx>>> wrote:
     >      > >>>>>
     >      > >>>>> The Fedora nightly build for doc failed because it wanted asciidoctor, but all it had was asciidoc.
     >      > >>>>>
     >      > >>>>> I believe I just need to change the "buildrequires" from:
     >      > >>>>>
     >      > >>>>> BuildRequires:  asciidoc
     >      > >>>>>
     >      > >>>>> to:
     >      > >>>>>
     >      > >>>>> BuildRequires:  rubygem-asciidoctor
     >      > >>>>>
     >      > >>>>> in the kicad-nightly-doc.spec file.
     >      > >>>>>
     >      > >>>>> However, I also noticed that the page https://gitlab.com/kicad/services/kicad-doc <https://gitlab.com/kicad/services/kicad-doc> <https://gitlab.com/kicad/services/kicad-doc <https://gitlab.com/kicad/services/kicad-doc>> still calls for asciidoc, so that README.adoc should probably be updated too.
     >      > >>>>>
     >      > >>>>>           Steve
     >      > >>>>>
     >      > >>>>>
     >      > >>>>>
     >      > >>>>> _______________________________________________
     >      > >>>>> Mailing list: https://launchpad.net/~kicad-developers <https://launchpad.net/~kicad-developers> <https://launchpad.net/~kicad-developers <https://launchpad.net/~kicad-developers>>
     >      > >>>>> Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx <mailto:kicad-developers@xxxxxxxxxxxxxxxxxxx> <mailto:kicad-developers@xxxxxxxxxxxxxxxxxxx <mailto:kicad-developers@xxxxxxxxxxxxxxxxxxx>>
     >      > >>>>> Unsubscribe : https://launchpad.net/~kicad-developers <https://launchpad.net/~kicad-developers> <https://launchpad.net/~kicad-developers <https://launchpad.net/~kicad-developers>>
     >      > >>>>> More help   : https://help.launchpad.net/ListHelp <https://help.launchpad.net/ListHelp> <https://help.launchpad.net/ListHelp <https://help.launchpad.net/ListHelp>>
     >      > >>>
     >      > >>
     >      >
     >
     >     _______________________________________________
     >     Mailing list: https://launchpad.net/~kicad-developers <https://launchpad.net/~kicad-developers> <https://launchpad.net/~kicad-developers <https://launchpad.net/~kicad-developers>>
     >     Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx <mailto:kicad-developers@xxxxxxxxxxxxxxxxxxx> <mailto:kicad-developers@xxxxxxxxxxxxxxxxxxx <mailto:kicad-developers@xxxxxxxxxxxxxxxxxxx>>
     >     Unsubscribe : https://launchpad.net/~kicad-developers <https://launchpad.net/~kicad-developers> <https://launchpad.net/~kicad-developers <https://launchpad.net/~kicad-developers>>
     >     More help   : https://help.launchpad.net/ListHelp <https://help.launchpad.net/ListHelp> <https://help.launchpad.net/ListHelp <https://help.launchpad.net/ListHelp>>
     >




Follow ups

References