similar to: AsciiDoc 8.6.3 release redux

Displaying 20 results from an estimated 1000 matches similar to: "AsciiDoc 8.6.3 release redux"

2010 Nov 05
1
[nut-commits] svn commit r2669 - in branches/AsciiDoc: . m4
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.
2014 Oct 22
1
config file locations
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
2010 Oct 22
0
NUT and AsciiDoc (was: Next AsciiDoc release)
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
2014 Oct 22
0
config file locations
On Tuesday 21 October 2014 22:06:48 Charles Lepple did opine And Gene did reply: > Hi Gene, > > On Oct 21, 2014, at 9:12 PM, Gene Heskett <gheskett at wdtv.com> wrote: > >> configure: error: libgd not found, required for CGI build > >> > >> And gdlib does not appear to be available from the repo's. > > Sorry, I must have missed that message.
2014 Oct 22
4
config file locations
Hi Gene, On Oct 21, 2014, at 9:12 PM, Gene Heskett <gheskett at wdtv.com> wrote: >> configure: error: libgd not found, required for CGI build >> >> And gdlib does not appear to be available from the repo's. > Sorry, I must have missed that message. This is still with Ubuntu 10.04, right? http://packages.ubuntu.com/source/lucid/nut lists the build dependencies,
2014 Nov 23
6
building NUT on Mac OS X Yosemite (website/documentation)
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)
2010 Dec 18
3
[nut-commits] svn commit r2748 - trunk
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
2014 Nov 23
0
building NUT on Mac OS X Yosemite (website/documentation)
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: > >
2014 Nov 24
0
building NUT on Mac OS X Yosemite (website/documentation)
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.
2014 Nov 20
0
building NUT on Mac OS X Yosemite (website/documentation)
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,
2014 Dec 01
2
building NUT on Mac OS X Yosemite (website/documentation)
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,
2010 Nov 07
0
[nut-commits] buildbot failure in Network UPS Tools on openSUSE [asciidoc]
> 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
2017 Jun 24
6
Device not supported?
On 06/24/2017 04:52 AM, Charles Lepple wrote: > On Jun 23, 2017, at 5:50 PM, Ambrogio Coletti <ambrojohn at gmail.com> wrote: >> "This TrippLite device (09ae:1330) is not (or perhaps not yet) supported by usbhid-ups. [...]" >> but my device (SU2200RTXLCD2U) is supported, as clearly state here. > No, the HCL also mentions "protocol 4001". For Tripp-Lite,
2014 Nov 20
2
building NUT on Mac OS X Yosemite
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
2009 Aug 16
1
A new project using AsciiDoc: Network UPS Tools
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
2013 Jul 29
3
nut package with Riello UPS support
Thanks for you reply. I have installed asciidoc with "pkg_add asciidoc" And it returns something: # asciidoc fgh asciidoc: FAILED: input file /root/nut/fgh missing # which asciidoc /usr/local/bin/asciidoc Maybe there is any way to skip building man pages. This is not the such main thing as a new devices support. I also could built the driver that I need # make riello_ser but I don't
2013 Jul 30
0
Fwd: nut package with Riello UPS support
Here is what I did: # cd /root/nut/ # nut here it's checkouted repository # ./configure --with-user=_ups --with-group=_ups # cd drivers/ # make riello_ser # chgrp bin riello_ser # cp riello_ser /usr/local/bin # here I copied builder driver to folder where nut-package will store their files/drivers # pkg_add nut-2.6.5p1 # ls -la /dev/tty00 crw-rw---- 1 _ups _ups 8, 0 Jul 30
2009 Sep 30
3
AsciiDoc and R
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
2010 Jul 14
1
[nut-commits] svn commit r2472 - in branches/AsciiDoc: . docs docs/website
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 > = > = > = > = > = > = > = > = > ====================================================================== > ---
2009 Mar 27
5
Getting asciidoc
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/$basearch/dag gpgkey=http://dag.wieers.com/rpm/packages/RPM-GPG-KEY.dag.txt