search for: asciidoc

...omm UPS" battery_min = 11 battery_max = 13.6 This is how the things need to be specified, right? In any event, I pulled the whole tree but its build fails as follows: make[2]: Entering directory `/home/bruda/nut-master/docs/man' Using existing upsclient.3 manual page, since 'asciidoc' was not found. Using existing upscli_add_host_cert.3 manual page, since 'asciidoc' was not found. Using existing upscli_cleanup.3 manual page, since 'asciidoc' was not found. Using existing upscli_connect.3 manual page, since 'asciidoc' was not found. Using existing ups...

...battery_max = 13.6 > > This is how the things need to be specified, right? Yes. > In any event, I pulled the whole tree but its build fails as follows: > > make[2]: Entering directory `/home/bruda/nut-master/docs/man' > Using existing upsclient.3 manual page, since 'asciidoc' was not found. > Using existing upscli_add_host_cert.3 manual page, since 'asciidoc' was not found. > Using existing upscli_cleanup.3 manual page, since 'asciidoc' was not found. > Using existing upscli_connect.3 manual page, since 'asciidoc' was not found. &gt...

I would like to learn AsciiDoc. Is there any good examples how to use AsciiDoc with R? I know that there is packages called ascii to do this, but it would be nice to see some examples how AsciiDoc works with R. Is there an AsciiDoc distribution for Max OS X? -Johannes

...on it's nut-2.6.5 which doesn't have Riello's models. Do we need to wait next upcoming nut release to get start with Riello? I tried to install from source but stuck: # git clone https://github.com/networkupstools/nut.git # pkg_add python-3.2.3p0 autoconf-2.69p0 automake-1.13.1 libtool asciidoc # ln -s /usr/local/bin/python2.7 /usr/local/bin/python # pwd /root/nut # export AUTOMAKE_VERSION=1.13 # export AUTOCONF_VERSION=2.69 # export CONFIGURE_STYLE=autoconf # ./autogen.sh Calling autoreconf... aclocal-1.13: warning: autoconf input should be named 'configure.ac', not ' configu...

On May 24, 2014, at 5:49 PM, Stefan Bruda wrote: >> Don't worry about the battery physical properties for now - the >> problem there is that we don't have enough information from the UPS >> to do a proper calculation. With the V_interval[] settings, you can >> tweak the new state-of-charge calculation to match what you see via >> upsc when the battery is

...>> for all the intervening bug reports -- it's amazing what a pending >> release can do to focus minds. >> >> >> indeed >> >> If you do find another regression or bug please verify it against >> the trunk (see http://code.google.com/p/asciidoc/source/checkout) >> and include a minimal test case that illustrates the problem. >> >> >> just a question, because NUT' configure script is checking this: >> a2x version is still 8.6.1 while asciidoc is already 8.6.3. >> do you plan to also bump a2x versi...

Hi Stuart, sorry for the lag in answering, I know that you're awaiting feedback for the final release... 2010/10/19 Stuart Rackham > Hi Arnaud > > I successfully compiled all the docs in svn:// > svn.debian.org/nut/branches/AsciiDoc using the current AsciiDoc trunk, and > yes, the chunked manual only has a single toc. But there was the added > problem of the article sections not being chunked by default, the > chunk.section.depth parameter was set to 0 by default (for chapter level > chunking in books), this has be...

On Jul 13, 2010, at 6:59 PM, Arnaud Quette wrote: > Author: aquette > Date: Tue Jul 13 22:59:52 2010 > New Revision: 2472 > URL: http://trac.networkupstools.org/projects/nut/changeset/2472 [...] > Modified: branches/AsciiDoc/docs/Makefile.am > = > = > = > = > = > = > = > = > ====================================================================== > --- branches/AsciiDoc/docs/Makefile.am Sun Jul 11 16:25:16 2010 > (r2471) > +++ branches/AsciiDoc/docs/Makefile.am Tue Jul 13 22:59:52 20...

On Nov 4, 2010, at 6:21 PM, Arjen de Korte wrote: > Author: adkorte-guest > Date: Thu Nov 4 22:21:51 2010 > New Revision: 2669 > URL: http://trac.networkupstools.org/projects/nut/changeset/2669 > > Log: > Add checking minimum required version for AsciiDoc tools I noticed that somewhere around this commit, the documentation stopped being built by default in BuildBot. Before I go digging too far, should I just add "--with-doc=auto" to the configure parameters, or should that eventually be included in the "--with-all=auto" s...

Hello, At 09:24 -0400 on 2014-5-23 Charles Lepple wrote: > > See attached. Still doesn't have the writable V_interval values, > but I probably won't have time to test that until later. Thank you for the patch. > Don't worry about the battery physical properties for now - the > problem there is that we don't have enough information from the UPS > to do a

On Oct 21, 2014, at 11:37 PM, Gene Heskett <gheskett at wdtv.com> wrote: > Hummm, that got me past that barricade, but then it needed asciidoc, which > pulled in everything else it was fussing about. The everything else was > close to all of tex and latex, something north of 220 megs worth. Drive > space I have, but thats a heck of big hunk of dependency. You mean that LaTeX isn't on everyone's short list of must-hav...

...slightly outside the scope of the NUT project :-) On Thu, Sep 3, 2009 at 8:31 AM, Arnaud Quette<aquette at alioth.debian.org> wrote: > Author: aquette > Date: Thu Sep 3 12:31:10 2009 > New Revision: 1953 > > Log: > IE6 layout fix (test) > > Modified: > branches/AsciiDoc/docs/website/scripts/nut_jquery.js > > Modified: branches/AsciiDoc/docs/website/scripts/nut_jquery.js > ============================================================================== > --- branches/AsciiDoc/docs/website/scripts/nut_jquery.js Thu Sep 3 11:58:30 2009 (r1952...

I need to install asciidoc on my build machine. There is a version for CentOS-5 available at dags rpm site. I have a repository configured for dag like so: [dag] name=Dag Wieers RPM Repository for Red Hat Enterprise Linux #Also see URL http://dag.wieers.com/home-made/apt/ baseurl=http://apt.sw.be/redhat/el$releasever/en/$...

Since I've heard about AsciiDoc (thanks ESR), I'm in the process of revamping the full Network UPS Tools documentation and website. Without going into the usual "it curred my desease, got my wife back home, and made me won a billion", it really saved my life ^_ ^ I was searching for such tool for years! thanks a l...

On Mon, Sep 14, 2009 at 4:49 PM, Arnaud Quette <aquette at alioth.debian.org> wrote: > Author: aquette > Date: Mon Sep 14 20:49:59 2009 > New Revision: 1986 > > Log: > draft index of manual pages > > Added: > branches/AsciiDoc/docs/man/index.txt Cool! One potential issue: /sw/bin/asciidoc --backend=xhtml11 \ --attribute localdate=`TZ=UTC date +%Y-%m-%d` \ --attribute localtime=`TZ=UTC date +%H:%M:%S` \ -o index.html index.txt WARNING: index.txt: line 6: missing [User_man] section WARNING: index.txt: line 96: mis...

...://packages.ubuntu.com/source/lucid/nut lists the build > dependencies, and it looks like both libgd2-xpm-dev and > libgd2-noxpm-dev are still available. (NUT does not explicitly need > the XPM support, so either one should work.) Hummm, that got me past that barricade, but then it needed asciidoc, which pulled in everything else it was fussing about. The everything else was close to all of tex and latex, something north of 220 megs worth. Drive space I have, but thats a heck of big hunk of dependency. However, the configure is still bailing out: checking for library containing gdImage...

...Riello's models. > Do we need to wait next upcoming nut release to get start with Riello? We're not too far away from a release: https://github.com/networkupstools/nut/issues/37 > I tried to install from source but stuck: [...] > Using existing nut.conf.5 manual page, since 'asciidoc' was not found. We don't check the generated man pages into the Git repository, so the easiest way to get around this is probably to just install asciidoc. At some point I will fix the Buildbot step which generates snapshot tarballs with the generated man pages included. -- Charles Lep...

Hello, I'm starting to think that converting the Syslinux documentation to asciidoc would be the best, and probably easiest, way to get some kind of consistency between the web docs and what is shipped. I don't think it would be all that hard to do (see http://www.methods.co.nz/asciidoc/). Anyone interested in trying to tackle this? -hpa

...:40:51 2010 > New Revision: 2671 > URL: http://trac.networkupstools.org/projects/nut/changeset/2671 > > Log: > Exclude -I. and extra developer warning flags with Net-SNMP support enabled > (using them is the responsibility of the NUT developers) > > Modified: > branches/AsciiDoc/m4/nut_check_libnetsnmp.m4 > Arjen, was this really intended to target the AsciiDoc branch? note that I've not checked if it's simply a sync with trunk, but in this case you would probably have mentioned it... cheers, Arnaud -------------- next part -------------- An HTML attachment w...

Citeren Arnaud Quette <aquette op alioth.debian.org>: > Author: aquette > Date: Fri Dec 17 23:32:20 2010 > New Revision: 2748 > URL: http://trac.networkupstools.org/projects/nut/changeset/2748 > > Log: > --with-doc=auto now behave depending on AsciiDoc presence Instead of building whatever can be build (depending on the versions found), you now have changed the behavior to an 'all-or-nothing' approach. I'm not sure that I like this. Best regards, Arjen -- Please keep list traffic on the list (off-list replies will be rejected)