similar to: [nut-commits] svn commit r1986 - branches/AsciiDoc/docs/man

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

After a fresh ?nut' (version 2.7.2.5) clone on Yosemite, Configuration summary: ====================== build serial drivers: yes build USB drivers: yes build SNMP drivers: yes build neon based XML driver: yes enable Avahi support: no build Powerman PDU client driver: no build IPMI driver: no build Mac OS X meta-driver: yes build i2c based drivers: no enable SSL support: yes (OpenSSL)

Sorry I ran ?make' command in nut-website/nut... (I still can?t understand why creating man page is so long, it is much more faster on ubuntu.) When running ?make? in nut-website, same issue then described previously, even with Arno patch > sort: stray character in field spec: invalid field specification `4.1,4.5rV > > >>>>>> and it ends with: > >

> The Buildbot has detected a new failure of openSUSE on Network UPS > Tools. > Full details are available at: > http://buildbot.networkupstools.org/public/nut/builders/openSUSE/builds/1012 Arjen, I think this is a bug in older versions of asciidoc/a2x where it ignores --destination-dir and tries to write the intermediate XML file to the read-only source directory. Looks like

On Nov 23, 2014, at 3:19 PM, Jean Perriault (GM TAF) <jpweb.taf at gmail.com> wrote: > After a fresh ?nut' (version 2.7.2.5) clone on Yosemite, The version number is simply a placeholder, indicating that the Git tree has changes beyond v2.7.2, and is not yet released as v2.7.3. After we start making changes, you may want to use "git describe --tags" or the Git commit ID.

Hi Dan Charles and Jean are having an issue with the nut-website buildrules. would you have a bit of time to check to help them? thx and cheers, Arno 2014-11-24 14:59 GMT+01:00 Charles Lepple <clepple at gmail.com>: > On Nov 23, 2014, at 3:19 PM, Jean Perriault (GM TAF) <jpweb.taf at gmail.com> > wrote: > > After a fresh ?nut' (version 2.7.2.5) clone on Yosemite,

Full_Name: Ed Borasky Version: 1.8.1 OS: Windows XP Professional Submission from: (NULL) (208.252.96.195) R 1.8.1 seems to be running into a memory allocation problem in the "aggregate" function. I have a rather large dataset (14 columns by 223,000 rows -- almost 40 megabytes) and a script that performs some processing on it. The system is a 768 MB Pentium 4. Here's the console

On Nov 20, 2014, at 7:11 AM, Jean Perriault (GM TAF) <jpweb.taf at gmail.com> wrote: > Hello, > Here is a summary of discussions around NUT builds on Mac OS X 10.10. > > Starting from https://github.com/networkupstools/nut-website/issues/7 > > @JeanPerriault > I've found msort on macports (https://trac.macports.org/browser/trunk/dports/textproc/msort/Portfile,

Hello, Here is a summary of discussions around NUT builds on Mac OS X 10.10. Starting from https://github.com/networkupstools/nut-website/issues/7 <https://github.com/networkupstools/nut-website/issues/7> @JeanPerriault I've found msort on macports (https://trac.macports.org/browser/trunk/dports/textproc/msort/Portfile, http://billposer.org/Software/Downloads/ msort.pdf), but I'm

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 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 > = > = > = > = > = > = > = > = > ====================================================================== > ---

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.

FYI (mostly Charles and Arjen), a2x version has just been bumped to 8.6.3 in their trunk. So we will be able revert r2686 cheers, Arno 2010/11/12 Stuart Rackham > > > On 12/11/10 10:45, Arnaud Quette wrote: > >> Hi Stuart, >> >> 2010/11/10 Stuart Rackham >> >> The planned 28-Oct release date has slipped by, in the mean time I >> think all

Arnaud, Thanks for removing the warning. I suspect that many users still using IE6 are doing so because of their IT department (rather than personal preference). IMHO, browser evangelism is 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

2010/11/4 Arjen de Korte > Author: adkorte-guest > Date: Thu Nov 4 22: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: >

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

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 lot Stuart and others. Kudos for the work! NUT revamp is not yet

Hi, I've been thinking of moving to using asciidoc for vignettes. As part of doing so, it would be nice to have an R package with all the pieces preconfigured in order to let others build the vignettes without a lot of configuration work. Conceptually, the following combination would work: * rJava package * rJython package * ascii package for Sweave processing of original asciidoc source

It looks like there was an issue with the AsciiDoc merge from the trunk: http://buildbot.networkupstools.org/private/nut/builders/Ubuntu-lucid-x86/builds/119/steps/compile/logs/stdio As mentioned in the email about windows_port, I would recommend testing the branch after a merge from the trunk. You can either run "make distcheck", or contact me (off-list) to set up a password so

On Aug 14, 2009, at 8:31 AM, Charles Lepple wrote: > Author: clepple-guest > Date: Fri Aug 14 12:31:25 2009 > New Revision: 1931 > > Log: > Warn when making 'html' without asciidoc tool Heh. Now I get a warning when running automake (with or without asciidoc). I'll fix that later.