similar to: Getting asciidoc

Displaying 20 results from an estimated 5000 matches similar to: "Getting asciidoc"

2008 Dec 29
4
yum cannot find bittorent rpm at dag
I am trying to get the x86_64 isos of CentOS-5.2. I wish to use bittorrent. The last time that I did this I required the bittorent package from Dag's repository. I have configured /etc/yum.repos.d/DagWieers.repo thus: [dag] name=Dag Wieers RPM Repository for Red Hat Enterprise Linux #Also see URL http://dag.wieers.com/home-made/apt/
2008 Oct 01
1
Help wanted: asciidoc documentation
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
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 > = > = > = > = > = > = > = > = > ====================================================================== > ---
2005 Nov 06
2
other repositories question
Hello. I would like to know how other repositories than the official ones for CentOS 4 affect an update of a package if a package is present in both repositories. Will yum install the package that it finds having the highest version number ? and if so, is there a mean to tell yum that we would like to keep the preference to one repository instead of the highest version number on a possibly
2009 Sep 03
2
[nut-commits] svn commit r1953 - branches/AsciiDoc/docs/website/scripts
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
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
2010 Nov 12
3
AsciiDoc 8.6.3 release redux
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
2009 Sep 15
1
[nut-commits] svn commit r1986 - branches/AsciiDoc/docs/man
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` \
2010 Nov 05
1
[nut-commits] svn commit r2671 - branches/AsciiDoc/m4
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: >
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.
2007 Feb 15
2
What is/provides php-pear(PEAR)
I am running up against a less than helpful error message when trying to install php-pear-DB (why people cannot content themselves with all lowercase packages names escapes me, but that is a rant for another time and place). After enableing centos-plus and adding includepkgs=php-pear-DB I get this: # yum install php-pear-DB Setting up Install Process Setting up repositories Reading repository
2012 Dec 07
4
[PATCH][git-pull] AsciiDoc-based documentation
The following changes since commit ddb10ce99c327888ade4d2ba3e4c50ad12aaa059: Matt Fleming (1): Delete 16-bit COMBOOT support are available in the git repository at: git://github.com/geneC/syslinux.git doc-elflink-for-mfleming Gene Cumm (3): txt/: Add new AsciiDoc formatted documentation Makefile: add txt/ NEWS: add txt/ Makefile | 2 +- NEWS
2011 Jan 28
1
ssl-nss-port branch does not compile on Ubuntu (asciidoc)
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
2008 Dec 12
1
Centos 5.2 yum check-update fails - repo change?
A couple of days ago I run yum update to take care of installing new updates for evolution.i386, evolution-data-server.i386 and nscd.i386 . The update went through with no fuss. Yesterday when I ran check-update I got the exact same updates list. So I did not run yum update, thinking this was a sync error or a repo issue. Today (just a few minutes ago) I ran the update check again and got the
2009 Oct 01
1
Help with AsciiDoc man pages
I'm looking for a little bit of help with the man page conversion. So far, about a third of the man pages are converted, and I think it would make sense to have a second or third set of eyes compare the output to be sure that we are not losing any information in the conversion process. In the tarballs generated from the AsciiDoc branch on http://buildbot.ghz.cc/public/nut/ you will find the
2009 Dec 01
1
[nut-commits] svn commit r2147 - branches/AsciiDoc/docs/man
Can someone double-check the UTF-8 in the rhino Authors section? Showed up fine locally on my machine, but my web browser insists that it is Latin-1. - Charles On Nov 30, 2009, at 10:30 PM, Charles Lepple <clepple-guest at alioth.debian.org > wrote: > Author: clepple-guest > Date: Tue Dec 1 03:30:32 2009 > New Revision: 2147 > > Log: > AsciiDoc: convert powerpanel
2007 Feb 17
1
Advice, Please.
Hello, I have a home setup where I am using Centos 4.4 as a sort of mail server. This is what I have done. I have it configured to pop mail locally. I have fetchmail configured to dl from my provider my families mail through a cron job and .fetchmailrc in their home directories. They then pop the server to retrieve their mail. They send their mail directly through the provider. I have
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 Jun 03
2
Tripp Lite SMART3000RM2U (protocol 3003) running time and charge?
Hello, At 15:42 -0400 on 2014-6-1 Charles Lepple wrote: > > 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