Re: [Kicad-developers] asciidoc

It was also happy here https://gitlab.com/kicad/packaging/kicad-fedora-builder/-/jobs/1316881996 tor. 3. jun. 2021 22.38 skrev Steven A. Falco : > 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 :-) > >

Re: [Kicad-developers] 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

Re: [Kicad-developers] asciidoc

Hopefully it should be running ok in https://gitlab.com/kicad/packaging/kicad-fedora-builder/-/jobs/1316881996 On Thu, 3 Jun 2021 at 22:32, Nick Østergaard wrote: > Ah,ok, I misread the pipeline logs.. > > Error: Login invalid/expired. Please visit > https://copr.fedorainfracloud.org/api to get

Re: [Kicad-developers] asciidoc

Ah,ok, I misread the pipeline logs.. Error: Login invalid/expired. Please visit 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 wrote: > The build you are looking at happened before I put in the fix. In

Re: [Kicad-developers] asciidoc

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

Re: [Kicad-developers] asciidoc

@Steven A. Falco 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/ On Sun, 30 May 2021 at 22:51, Jon Evans wrote: > If

Re: [Kicad-developers] asciidoc

Hi, this topic more relevant for kicad-doc I think. Am 30.05.21 um 20:34 schrieb Jon Evans: > You want this one: https://github.com/Mogztter/asciidoctor-web-pdf > > On Ubuntu I install it with "sudo npm i -g @asciidoctor/core asciidoctor-pdf" For Debian (and also for Ubuntu) this isn't

Re: [Kicad-developers] asciidoc

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 Maybe this is also helpful for setting up a Fedora VM or Docker container On Sun, May 30, 2021 at 3:00 PM

Re: [Kicad-developers] asciidoc

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 On Ubuntu I install it with "sudo npm i -g @asciidoctor/core asciidoctor-pdf" On Sun, May 30, 2021

Re: [Kicad-developers] asciidoc

You want this one: 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 wrote: > > I'm able to build the html pages, which is all we need for the nightlies, but > I am not

Re: [Kicad-developers] asciidoc

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

Re: [Kicad-developers] asciidoc

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

Re: [Kicad-developers] asciidoc

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

[Kicad-developers] asciidoc

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

Re: [Kicad-developers] Asciidoc question.

Thanks Mark! I'll file this away for future reference. On 11/12/2017 10:07 AM, Mark Roszko wrote: > FYI, here's how you add icons > > https://github.com/KiCad/kicad-website/commit/893c902228c5d0a0d6fdbcdf783878cbbd439f6e > > Never did figure out how to make hugo set global asciidoc parameters

Re: [Kicad-developers] Asciidoc question.

FYI, here's how you add icons https://github.com/KiCad/kicad-website/commit/893c902228c5d0a0d6fdbcdf783878cbbd439f6e Never did figure out how to make hugo set global asciidoc parameters On Fri, Nov 10, 2017 at 2:28 PM, Wayne Stambaugh wrote: > I was hoping the icon would

Re: [Kicad-developers] Asciidoc question.

On Sat, Nov 11, 2017 at 01:46:07PM +0100, Marco Ciampa wrote: > On Fri, Nov 10, 2017 at 08:20:32AM -0500, Wayne Stambaugh wrote: > > Maybe one of our resident asciidoc experts can help me out. I used a > > WARNING admonition in the kicad website symbol library table blog > > post[1]. I was

Re: [Kicad-developers] Asciidoc question.

On Fri, Nov 10, 2017 at 08:20:32AM -0500, Wayne Stambaugh wrote: > Maybe one of our resident asciidoc experts can help me out. I used a > WARNING admonition in the kicad website symbol library table blog > post[1]. I was expecting to see the warning icon per the asciidoc > documentation[2] but I

Re: [Kicad-developers] Asciidoc question.

I was hoping the icon would draw user's attention to the warning to the obvious backup your files statement but maybe I was being a bit optimistic. I'm fine with it the way it is. I just wanted to be sure I didn't do anything wrong. On 11/10/2017 08:48 AM, Nick Østergaard wrote: > The source

Re: [Kicad-developers] Asciidoc question.

The source and generated code looks correct. It just seems like we don't have any definition for the admonitionblock div classes for the icons in the CSS. I guess this is a matter of taste, on whether one likes icons or text. I guess icons was not implemented because we didn't use many of these

[Kicad-developers] Asciidoc question.

Maybe one of our resident asciidoc experts can help me out. I used a WARNING admonition in the kicad website symbol library table blog post[1]. I was expecting to see the warning icon per the asciidoc documentation[2] but I only see a "WARNING" string where I expected the icon. Am I doing