From bugzilla at redhat.com Thu Jul 2 06:02:35 2009
From: bugzilla at redhat.com (bugzilla at redhat.com)
Date: Thu, 2 Jul 2009 02:02:35 -0400
Subject: [publican-list] [Bug 509307] New: remarks in s are not
consistently highlighted in pdfs
Message-ID: <bug-509307-264938@bugzilla.redhat.com>
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
Summary: remarks in <title>s are not consistently highlighted in pdfs
https://bugzilla.redhat.com/show_bug.cgi?id=509307
Summary: remarks in <title>s are not consistently highlighted
in pdfs
Product: Red Hat Enterprise Linux 5
Version: 5.2
Platform: All
OS/Version: Linux
Status: NEW
Severity: medium
Priority: low
Component: publican
AssignedTo: mhideo at redhat.com
ReportedBy: dmison at redhat.com
QAContact: ecs-dev-list at redhat.com
CC: publican-list at redhat.com
Classification: Red Hat
Target Release: ---
Description of problem:
adding remarks to <title> tags, specifically for <chapter> and <section> do not
always have the expected highlighting in all the places they occur
This worked in 0.44
I'd modified my /usr/share/publican/xsl/pdf.xsl file as per BZ 491782 prior to
upgrading to 0.45, so when I upgraded to 0.45 I probably still had the 0.44
pdf.xsl
I uninstalled publican & reinstalled it on the 29th of June to verify that the
current version still had BZ 491782, which is probably the first time I got the
0.45 pdf.xsl
Version-Release number of selected component (if applicable):
publican-doc-0.45-0.el5
publican-ovirt-0.7-0.el5
publican-jboss-0.19-0.el5
publican-0.45-0.el5
publican-WebSite-obsoletes-1.03-1.el5
publican-redhat-0.19-0.el5
publican-gimp-0.5-2.el5
publican-fedora-0.18-0.el5
How reproducible:
any pdf, does not occur in html or html-single output
Steps to Reproduce:
1. add a remark to a chapter title, eg.
<chapter><title><remark>UPDATED</remark>chapter X
2. add a remark to a section title, eg.
<remark>UPDATED</remark>section Y
3. add SHOW_REMARKS = 1 to the Makefile
4. make clean pdf-en-US
Actual results:
remarks in chapter titles as not highlighted in the page content (ie when the
title appears at the start of a chapter)
Expected results:
both chapter & section title remarks are highlighted
- in the table of contents
- as they occur in page content
- in page headers
Additional info:
Publican 0.44 on Fedora 11 (plus xslthl package) has a similar problem with the
additional problem that no highlighting appears at all in the table of contents
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
From bugzilla at redhat.com Thu Jul 2 06:12:57 2009
From: bugzilla at redhat.com (bugzilla at redhat.com)
Date: Thu, 2 Jul 2009 02:12:57 -0400
Subject: [publican-list] [Bug 509307] remarks in s are not
consistently highlighted in pdfs
In-Reply-To: <bug-509307-264938@bugzilla.redhat.com>
References: <bug-509307-264938@bugzilla.redhat.com>
Message-ID: <200907020612.n626Cvr3009319@bz-web2.app.phx.redhat.com>
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=509307
--- Comment #1 from Darrin Mison <dmison at redhat.com> 2009-07-02 02:12:56 EDT ---
Note the ability to have highlighted remarks in chapter/section titles that
appear in all three places is important to the SOA QE team's process for being
able to quickly QE the product docs.
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
From mhideo at redhat.com Sun Jul 5 23:01:03 2009
From: mhideo at redhat.com (Michael Hideo)
Date: Mon, 06 Jul 2009 09:01:03 +1000
Subject: [publican-list] Publican 1.0
Message-ID: <4A5130AF.9000408@redhat.com>
Folks,
This is a heads up email for the plan to begin testing Publican 1.0 on
Fedora.
These are the actions we are looking at right now to begin alpha testing
the software:
F12 Guides
==========
* Installation Guide
* Security Guide
* Deployment Guide
* Virtualization Guide
* Release Notes
We will need someone from l10n to check that the translations come out
cleanly. Additionally, we will need a dedicated person to do QE against
the new bugs and to regression test against the old bugs. Also we need
someone to work between l10n and QE to ensure that all the langs still
build correctly.
A few other activities that need to performed:
* Brands need to be repackaged (cc-by-sa for fedora/rh)
* Need to start a lock on the test repos
Rough timeline is sometime in the next 2 weeks. Note that the publican
software has been completely re-written from the ground up. Apparently
it will not use a "make" system but will use proper commands and
actions. This will provide more flexibility for the future and allow us
to be cross platform.
More timelines and infotainment to come shortly.
- Mike
From bugzilla at redhat.com Mon Jul 6 01:55:18 2009
From: bugzilla at redhat.com (bugzilla at redhat.com)
Date: Sun, 5 Jul 2009 21:55:18 -0400
Subject: [publican-list] [Bug 509768] New: fix for no rounded corners in
html output when viewed in Safari
Message-ID: <bug-509768-264938@bugzilla.redhat.com>
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
Summary: fix for no rounded corners in html output when viewed in Safari
https://bugzilla.redhat.com/show_bug.cgi?id=509768
Summary: fix for no rounded corners in html output when viewed
in Safari
Product: Red Hat Enterprise Linux 5
Version: 5.2
Platform: All
OS/Version: Linux
Status: NEW
Severity: medium
Priority: low
Component: publican
AssignedTo: mhideo at redhat.com
ReportedBy: dmison at redhat.com
QAContact: ecs-dev-list at redhat.com
CC: publican-list at redhat.com
Classification: Red Hat
Target Release: ---
Description of problem:
The html output of <programlisting> and <example> do not appear with rounded
corners in Safari (and other webkit browsers I guess), only in Firefox.
FIX: the addition of the evil webkit-border-radius css attribute in the same
manner as the evil moz-border-radius attribute in common.css
eg:
/* Dirty EVIL Mozilla hack for round corners */
and double-plus EVIL webkit hack */
pre {
-moz-border-radius:11px;
-webkit-border-radius:11px;
}
.example {
-moz-border-radius:15px;
-webkit-border-radius:15px;
}
Version-Release number of selected component (if applicable):
0.45
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
From bugzilla at redhat.com Mon Jul 6 02:53:10 2009
From: bugzilla at redhat.com (bugzilla at redhat.com)
Date: Sun, 5 Jul 2009 22:53:10 -0400
Subject: [publican-list] [Bug 509768] fix for no rounded corners in html
output when viewed in Safari
In-Reply-To: <bug-509768-264938@bugzilla.redhat.com>
References: <bug-509768-264938@bugzilla.redhat.com>
Message-ID: <200907060253.n662rArW002772@bz-web1.app.phx.redhat.com>
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=509768
Jeff Fearn <jfearn at redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jfearn at redhat.com
--- Comment #1 from Jeff Fearn <jfearn at redhat.com> 2009-07-05 22:53:10 EDT ---
Also should have:
border-radius: 15px;
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
From bugzilla at redhat.com Mon Jul 6 04:34:57 2009
From: bugzilla at redhat.com (bugzilla at redhat.com)
Date: Mon, 6 Jul 2009 00:34:57 -0400
Subject: [publican-list] [Bug 509768] fix for no rounded corners in html
output when viewed in Safari
In-Reply-To: <bug-509768-264938@bugzilla.redhat.com>
References: <bug-509768-264938@bugzilla.redhat.com>
Message-ID: <200907060434.n664YvS2021365@bz-web1.app.phx.redhat.com>
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=509768
--- Comment #2 from Darrin Mison <dmison at redhat.com> 2009-07-06 00:34:56 EDT ---
oh, I didn't realise there was a non-evil method ;-)
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
From bugzilla at redhat.com Mon Jul 6 08:30:43 2009
From: bugzilla at redhat.com (bugzilla at redhat.com)
Date: Mon, 6 Jul 2009 04:30:43 -0400
Subject: [publican-list] [Bug 509768] fix for no rounded corners in html
output when viewed in Safari
In-Reply-To: <bug-509768-264938@bugzilla.redhat.com>
References: <bug-509768-264938@bugzilla.redhat.com>
Message-ID: <200907060830.n668Uh4Z005602@bz-web1.app.phx.redhat.com>
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=509768
Issue Tracker <tao at redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tao at redhat.com
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
From jaredsmith at jaredsmith.net Wed Jul 8 22:31:30 2009
From: jaredsmith at jaredsmith.net (Jared Smith)
Date: Wed, 08 Jul 2009 18:31:30 -0400
Subject: [publican-list] Publican 1.0
In-Reply-To: <4A5130AF.9000408@redhat.com>
References: <4A5130AF.9000408@redhat.com>
Message-ID: <1247092290.26721.3.camel@hockey.jaredsmith.net>
On Mon, 2009-07-06 at 09:01 +1000, Michael Hideo wrote:
> This is a heads up email for the plan to begin testing Publican 1.0 on
> Fedora.
Publican 1.0?
> Rough timeline is sometime in the next 2 weeks.
I'd be happy to dedicate a few hours over the next two weeks to help
test.
> Note that the publican
> software has been completely re-written from the ground up. Apparently
> it will not use a "make" system but will use proper commands and
> actions. This will provide more flexibility for the future and allow us
> to be cross platform.
Wow... is the code freely available yet?
> More timelines and infotainment to come shortly.
Can't wait to hear more details.
-Jared
From rpjday at crashcourse.ca Thu Jul 9 14:07:37 2009
From: rpjday at crashcourse.ca (Robert P. J. Day)
Date: Thu, 9 Jul 2009 10:07:37 -0400 (EDT)
Subject: [publican-list] does publican have a drop-down menu entry in f11?
Message-ID: <alpine.LFD.2.00.0907091006060.8882@localhost>
perhaps not the best place to ask this but, after i install publican
on my f11 system, should i expect to see it somewhere under, perhaps,
"applications", maybe under "office"? or is it not set up to install
a menu entry?
rday
--
========================================================================
Robert P. J. Day Waterloo, Ontario, CANADA
Linux Consulting, Training and Annoying Kernel Pedantry.
Web page: http://crashcourse.ca
Linked In: http://www.linkedin.com/in/rpjday
Twitter: http://twitter.com/rpjday
========================================================================
From jfearn at redhat.com Thu Jul 9 22:56:45 2009
From: jfearn at redhat.com (Jeffrey Fearn)
Date: Fri, 10 Jul 2009 08:56:45 +1000
Subject: [publican-list] does publican have a drop-down menu entry in f11?
In-Reply-To: <alpine.LFD.2.00.0907091006060.8882@localhost>
References: <alpine.LFD.2.00.0907091006060.8882@localhost>
Message-ID: <4A5675AD.5090609@redhat.com>
Robert P. J. Day wrote:
> perhaps not the best place to ask this but, after i install publican
> on my f11 system, should i expect to see it somewhere under, perhaps,
> "applications", maybe under "office"? or is it not set up to install
> a menu entry?
Hi Robert, publican is a CLI tool. The only entry it makes is if you
install the docs package it makes an entry under System->Documentation.
Cheers, Jeff.
--
Jeff Fearn <jfearn at redhat.com>
Software Engineer
Engineering Operations
Red Hat, Inc
Freedom ... courage ... Commitment ... ACCOUNTABILITY
http://file.bne.redhat.com/~jfearn/
From jfearn at redhat.com Thu Jul 9 23:37:16 2009
From: jfearn at redhat.com (Jeffrey Fearn)
Date: Fri, 10 Jul 2009 09:37:16 +1000
Subject: [publican-list] Publican 1.0
In-Reply-To: <1247092290.26721.3.camel@hockey.jaredsmith.net>
References: <4A5130AF.9000408@redhat.com>
<1247092290.26721.3.camel@hockey.jaredsmith.net>
Message-ID: <4A567F2C.7020904@redhat.com>
Jared Smith wrote:
> On Mon, 2009-07-06 at 09:01 +1000, Michael Hideo wrote:
>> This is a heads up email for the plan to begin testing Publican 1.0 on
>> Fedora.
>
> Publican 1.0?
>
>> Rough timeline is sometime in the next 2 weeks.
>
> I'd be happy to dedicate a few hours over the next two weeks to help
> test.
>
>> Note that the publican
>> software has been completely re-written from the ground up. Apparently
>> it will not use a "make" system but will use proper commands and
>> actions. This will provide more flexibility for the future and allow us
>> to be cross platform.
>
> Wow... is the code freely available yet?
Hi Jared, the code is not freely available yet. It will be in the repo
for the beat though.
Cheers, Jeff.
--
Jeff Fearn <jfearn at redhat.com>
Software Engineer
Engineering Operations
Red Hat, Inc
Freedom ... courage ... Commitment ... ACCOUNTABILITY
http://file.bne.redhat.com/~jfearn/
From jaredsmith at jaredsmith.net Thu Jul 9 23:51:53 2009
From: jaredsmith at jaredsmith.net (Jared Smith)
Date: Thu, 09 Jul 2009 19:51:53 -0400
Subject: [publican-list] Publican 1.0
In-Reply-To: <4A567F2C.7020904@redhat.com>
References: <4A5130AF.9000408@redhat.com>
<1247092290.26721.3.camel@hockey.jaredsmith.net>
<4A567F2C.7020904@redhat.com>
Message-ID: <1247183513.18600.6.camel@hockey.jaredsmith.net>
On Fri, 2009-07-10 at 09:37 +1000, Jeffrey Fearn wrote:
> Hi Jared, the code is not freely available yet. It will be in the repo
> for the beat though.
Thanks for the update.
I'm not sure what you mean by "in the repo for the beat". Which repo?
What do you mean by "for the beat"?
I'll try to be patient... but I can't wait to start trying it out.
Despite my (sometimes vocal) complaints about Publican, it's still a
pretty cool piece of software, and it makes me happy to hear that
development is moving forward. Thanks to everyone involved for their
hard work on it!
-Jared
From jfearn at redhat.com Thu Jul 9 23:59:42 2009
From: jfearn at redhat.com (Jeffrey Fearn)
Date: Fri, 10 Jul 2009 09:59:42 +1000
Subject: [publican-list] Publican 1.0
In-Reply-To: <1247183513.18600.6.camel@hockey.jaredsmith.net>
References: <4A5130AF.9000408@redhat.com>
<1247092290.26721.3.camel@hockey.jaredsmith.net>
<4A567F2C.7020904@redhat.com>
<1247183513.18600.6.camel@hockey.jaredsmith.net>
Message-ID: <4A56846E.2070009@redhat.com>
Jared Smith wrote:
> On Fri, 2009-07-10 at 09:37 +1000, Jeffrey Fearn wrote:
>> Hi Jared, the code is not freely available yet. It will be in the repo
>> for the beat though.
>
> Thanks for the update.
>
> I'm not sure what you mean by "in the repo for the beat". Which repo?
> What do you mean by "for the beat"?
I like to think my typos add "character" ... at least that is what I try
to tell myself!
The source code will be in the publican SVN repo for the beta.
Packages will be also made available, we haven't discussed how yet. We
want to do it so you can install the beta side by side with the current
packages so people can continue to do their work and test the new stuff
at the same time.
Cheers, Jeff.
--
Jeff Fearn <jfearn at redhat.com>
Software Engineer
Engineering Operations
Red Hat, Inc
Freedom ... courage ... Commitment ... ACCOUNTABILITY
http://file.bne.redhat.com/~jfearn/
From lbrindle at redhat.com Fri Jul 10 00:46:59 2009
From: lbrindle at redhat.com (Lana Brindley)
Date: Fri, 10 Jul 2009 10:46:59 +1000
Subject: [publican-list] Publican 1.0
In-Reply-To: <4A56846E.2070009@redhat.com>
References: <4A5130AF.9000408@redhat.com> <1247092290.26721.3.camel@hockey.jaredsmith.net> <4A567F2C.7020904@redhat.com> <1247183513.18600.6.camel@hockey.jaredsmith.net>
<4A56846E.2070009@redhat.com>
Message-ID: <4A568F83.6020203@redhat.com>
Jeffrey Fearn wrote:
> Jared Smith wrote:
>> On Fri, 2009-07-10 at 09:37 +1000, Jeffrey Fearn wrote:
>>> Hi Jared, the code is not freely available yet. It will be in the
>>> repo for the beat though.
>>
>> Thanks for the update.
>>
>> I'm not sure what you mean by "in the repo for the beat". Which repo?
>> What do you mean by "for the beat"?
>
> I like to think my typos add "character" ... at least that is what I try
> to tell myself!
>
> The source code will be in the publican SVN repo for the beta.
I kind of liked the sound of "in the repo for the beat".
I imagined Jeff wearing flouro yellow happy pants and carrying a massive
boom box while he said it ;)
L
-------------- next part --------------
A non-text attachment was scrubbed...
Name: lbrindle.vcf
Type: text/x-vcard
Size: 976 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/publican-list/attachments/20090710/cc4bafba/attachment.vcf>
From rpjday at crashcourse.ca Fri Jul 10 04:52:26 2009
From: rpjday at crashcourse.ca (Robert P. J. Day)
Date: Fri, 10 Jul 2009 00:52:26 -0400 (EDT)
Subject: [publican-list] and the repository is where?
Message-ID: <alpine.LFD.2.00.0907100049260.15382@localhost>
i've only used publican via the yum-installable package -- so
where's the svn repository? and while perusing the publican wiki page
here:
http://fedoraproject.org/wiki/DocsProject/Publican
i noticed that it continues to refer to F9 alpha, which seems a bit
out of date, and the name of the yum directory most of the way down
the page is given as "/etc/yum/yum.repos.d/", which doesn't sound
right.
rday
--
========================================================================
Robert P. J. Day Waterloo, Ontario, CANADA
Linux Consulting, Training and Annoying Kernel Pedantry.
Web page: http://crashcourse.ca
Linked In: http://www.linkedin.com/in/rpjday
Twitter: http://twitter.com/rpjday
========================================================================
From jwulf at redhat.com Fri Jul 10 05:05:08 2009
From: jwulf at redhat.com (Joshua Wulf)
Date: Fri, 10 Jul 2009 15:05:08 +1000
Subject: [publican-list] and the repository is where?
In-Reply-To: <alpine.LFD.2.00.0907100049260.15382@localhost>
References: <alpine.LFD.2.00.0907100049260.15382@localhost>
Message-ID: <4A56CC04.3090602@redhat.com>
svn repo linked from here: https://fedorahosted.org/publican/
On 07/10/2009 02:52 PM, Robert P. J. Day wrote:
> i've only used publican via the yum-installable package -- so
> where's the svn repository? and while perusing the publican wiki page
> here:
>
> http://fedoraproject.org/wiki/DocsProject/Publican
>
> i noticed that it continues to refer to F9 alpha, which seems a bit
> out of date, and the name of the yum directory most of the way down
> the page is given as "/etc/yum/yum.repos.d/", which doesn't sound
> right.
>
> rday
> --
>
> ========================================================================
> Robert P. J. Day Waterloo, Ontario, CANADA
>
> Linux Consulting, Training and Annoying Kernel Pedantry.
>
> Web page: http://crashcourse.ca
> Linked In: http://www.linkedin.com/in/rpjday
> Twitter: http://twitter.com/rpjday
> ========================================================================
>
> _______________________________________________
> publican-list mailing list
> publican-list at redhat.com
> https://www.redhat.com/mailman/listinfo/publican-list
> Wiki: https://fedorahosted.org/publican
>
--
Joshua J Wulf
Manager
Engineering Content Services
Red Hat Asia Pacific
eml: jwulf at redhat.com
tel: +61 7 3514-8140
cel: +61 431 929 675
From jfearn at redhat.com Fri Jul 10 05:07:29 2009
From: jfearn at redhat.com (Jeffrey Fearn)
Date: Fri, 10 Jul 2009 15:07:29 +1000
Subject: [publican-list] and the repository is where?
In-Reply-To: <alpine.LFD.2.00.0907100049260.15382@localhost>
References: <alpine.LFD.2.00.0907100049260.15382@localhost>
Message-ID: <4A56CC91.7020106@redhat.com>
Robert P. J. Day wrote:
> i've only used publican via the yum-installable package -- so
> where's the svn repository? and while perusing the publican wiki page
> here:
>
> http://fedoraproject.org/wiki/DocsProject/Publican
>
> i noticed that it continues to refer to F9 alpha, which seems a bit
> out of date, and the name of the yum directory most of the way down
> the page is given as "/etc/yum/yum.repos.d/", which doesn't sound
> right.
>
> rday
> --
>
> ========================================================================
> Robert P. J. Day Waterloo, Ontario, CANADA
>
> Linux Consulting, Training and Annoying Kernel Pedantry.
>
> Web page: http://crashcourse.ca
> Linked In: http://www.linkedin.com/in/rpjday
> Twitter: http://twitter.com/rpjday
> ========================================================================
>
> _______________________________________________
> publican-list mailing list
> publican-list at redhat.com
> https://www.redhat.com/mailman/listinfo/publican-list
> Wiki: https://fedorahosted.org/publican
The publican wiki is ^^^^^^^^^^^^^^^^^^^^
It has the SVN info.
I'm not sure what that fedora docs page is doing there ... it's far to
well written for me to have simply forgotten I wrote it some time in the
distant past :D
Cheers, Jeff.
--
Jeff Fearn <jfearn at redhat.com>
Software Engineer
Engineering Operations
Red Hat, Inc
Freedom ... courage ... Commitment ... ACCOUNTABILITY
http://file.bne.redhat.com/~jfearn/
From rpjday at crashcourse.ca Fri Jul 10 05:19:04 2009
From: rpjday at crashcourse.ca (Robert P. J. Day)
Date: Fri, 10 Jul 2009 01:19:04 -0400 (EDT)
Subject: [publican-list] and the repository is where?
In-Reply-To: <4A56CC91.7020106@redhat.com>
References: <alpine.LFD.2.00.0907100049260.15382@localhost>
<4A56CC91.7020106@redhat.com>
Message-ID: <alpine.LFD.2.00.0907100116430.15677@localhost>
On Fri, 10 Jul 2009, Jeffrey Fearn wrote:
> Robert P. J. Day wrote:
... snip ...
> > http://fedoraproject.org/wiki/DocsProject/Publican
> > Wiki: https://fedorahosted.org/publican
>
> The publican wiki is ^^^^^^^^^^^^^^^^^^^^
>
> It has the SVN info.
ah, gotcha.
> I'm not sure what that fedora docs page is doing there ... it's far
> to well written for me to have simply forgotten I wrote it some time
> in the distant past :D
might want to toss that older page, then. when i googled for
publican and repository, that's the one i ran across, and that might
throw a few folks who end up there the same way.
rday
--
========================================================================
Robert P. J. Day Waterloo, Ontario, CANADA
Linux Consulting, Training and Annoying Kernel Pedantry.
Web page: http://crashcourse.ca
Linked In: http://www.linkedin.com/in/rpjday
Twitter: http://twitter.com/rpjday
========================================================================
From rpjday at crashcourse.ca Fri Jul 10 06:16:58 2009
From: rpjday at crashcourse.ca (Robert P. J. Day)
Date: Fri, 10 Jul 2009 02:16:58 -0400 (EDT)
Subject: [publican-list] newbie observations on building publican from SVN
Message-ID: <alpine.LFD.2.00.0907100212290.3759@localhost>
from the perspective of someone who built publican from the repo for
the very first time a few minutes ago:
* the README file suggests i can get make help with one of "make help"
or "make help_params". neither of those targets seem to be supported.
* the build on a fully-updated f11 x86_64 system generates numerous
"... Legal_Notice.po MISSING Using en-US file" warnings. doesn't stop
the build, though.
* doing a straight "make" clearly attempts to *install* the
constructed rpm. that's kind of unusual, isn't it? i'm more used to
having to do that explicitly, with "make install". only after i
looked at the Makefile did i see the more limited "make rpm" target.
rday
--
========================================================================
Robert P. J. Day Waterloo, Ontario, CANADA
Linux Consulting, Training and Annoying Kernel Pedantry.
Web page: http://crashcourse.ca
Linked In: http://www.linkedin.com/in/rpjday
Twitter: http://twitter.com/rpjday
========================================================================
From rpjday at crashcourse.ca Fri Jul 10 06:41:47 2009
From: rpjday at crashcourse.ca (Robert P. J. Day)
Date: Fri, 10 Jul 2009 02:41:47 -0400 (EDT)
Subject: [publican-list] publican-doc-0.45 users guide still reads "0.44"
Message-ID: <alpine.LFD.2.00.0907100239410.31860@localhost>
not a big deal but, from the svn build, the file
file:///usr/share/doc/publican-doc-0.45/en-US/index.html still reads
"Publican 0.44" on the front page.
rday
--
========================================================================
Robert P. J. Day Waterloo, Ontario, CANADA
Linux Consulting, Training and Annoying Kernel Pedantry.
Web page: http://crashcourse.ca
Linked In: http://www.linkedin.com/in/rpjday
Twitter: http://twitter.com/rpjday
========================================================================
From rpjday at crashcourse.ca Fri Jul 10 07:33:46 2009
From: rpjday at crashcourse.ca (Robert P. J. Day)
Date: Fri, 10 Jul 2009 03:33:46 -0400 (EDT)
Subject: [publican-list] random observations on svn checkout of users guide
Message-ID: <alpine.LFD.2.00.0907100306070.5776@localhost>
figured i might as well peruse the users guide from beginning to end
so here's some random observations.
* as i mentioned already, version 0.45 of the UG still has a title of
"0.44"
* section 1.2, "Source-code listings are also set in mono-spaced roman
but add syntax highlighting as follows:"
- in my browser, i see no example of "syntax highlighting". am i
supposed to see something representing an example of
highlighting there? it's just straight mono-spaced roman.
* perhaps off-topic but will publican work with the relax ng schema of
docbook 5.0? it's possible that's mentioned later in the UG and i
just haven't got to it yet.
* Chapter 2 refers to five different brand packages, yet yum sees only
the following at the moment:
$ yum search publican
publican.noarch : Common files and scripts for publishing with DocBook XML
publican-doc.noarch : Documentation for the Publican package
publican-fedora.noarch : Publican documentation template files for fedora
publican-genome.noarch : Common documentation files for genome
publican-ovirt.noarch : Common documentation files for oVirt
$
where are the packages for gimp, redhat and jboss? are they in the
works? and that UG table says nothing about publican-genome (whatever
that is).
* Section 3.1:
"Run the following command to install the publican package:
# yum install publican publican-doc
i would rephrase that as installing the package *and* its associated
documentation package since, AFAICT, they can be installed
independently, no?
and just below that:
# yum install publican-brand
Replace brand with redhat, fedora, jboss, ovirt, or gimp.
we've already noticed that some of those packages don't seem to
exist, at least for a stock f11 x86_64 install.
* section 3.2 lists the create_book options "--help" and "--man" while
the actual help output lists them as "-help" and "-man". both work
but perhaps those should be made consistent to avoid confusion.
also, that list of options in Section 3.2 doesn't mention "--lang".
* still in Section 3.2, the instructions to create a new book fail to
note that, after running that create_book command, you need to "cd
Test_Book" before running ls. i'm sure readers will notice that right
away but you might as well be explicit to be accurate.
* Figure 3.1 lists an alleged new file "Appendix.xml". i see no such
file after a book creation.
time for more coffee. back in a bit.
rday
--
========================================================================
Robert P. J. Day Waterloo, Ontario, CANADA
Linux Consulting, Training and Annoying Kernel Pedantry.
Web page: http://crashcourse.ca
Linked In: http://www.linkedin.com/in/rpjday
Twitter: http://twitter.com/rpjday
========================================================================
From rpjday at crashcourse.ca Fri Jul 10 10:39:51 2009
From: rpjday at crashcourse.ca (Robert P. J. Day)
Date: Fri, 10 Jul 2009 06:39:51 -0400 (EDT)
Subject: [publican-list] "make srpm-en-US" fails, "bad date in %changelog"
Message-ID: <alpine.LFD.2.00.0907100637180.14233@localhost>
not sure if this is a known issue but with a brand new generic book
via "create_book --name Test_Book":
$ make srpm-en-US
...
END: xml-en-US Fri Jul 10 06:34:05 EDT 2009
START: test-en-US Fri Jul 10 06:34:05 EDT 2009
warning: failed to load external entity "tmp/en-US/xml/Feedback.xml"
...
END: spec-en-US Fri Jul 10 06:34:06 EDT 2009
START: srpm-en-US Fri Jul 10 06:34:06 EDT 2009
error: bad date in %changelog: 1.0
make: *** [srpm-en-US] Error 1
$
i thought that might have been this:
https://bugzilla.redhat.com/show_bug.cgi?id=478950
but it doesn't look like it.
rday
p.s. i will be back to annoying you with UG issues shortly.
--
========================================================================
Robert P. J. Day Waterloo, Ontario, CANADA
Linux Consulting, Training and Annoying Kernel Pedantry.
Web page: http://crashcourse.ca
Linked In: http://www.linkedin.com/in/rpjday
Twitter: http://twitter.com/rpjday
========================================================================
From rpjday at crashcourse.ca Fri Jul 10 11:05:11 2009
From: rpjday at crashcourse.ca (Robert P. J. Day)
Date: Fri, 10 Jul 2009 07:05:11 -0400 (EDT)
Subject: [publican-list] ongoing observations on users guide (svn checkout)
Message-ID: <alpine.LFD.2.00.0907100351350.6280@localhost>
* section 3.3.1, under "BRAND": "Accepted values are RedHat, fedora,
JBoss, oVirt and GIMP." already mentioned earlier that some of those
brands don't *appear* to exist as packages, so i'll shut up about it
from now on.
* section 3.3.3: " If you distribute a book as an RPM package, the
data placed within this tag sets 'the first two digits of the version
number in the .rpm filename'.
So, an edition of '1.0' becomes a version of '1.0'."
that's not a terribly informative example -- stating that '1.0'
becomes '1.0'. perhaps a more complex edition number would show what
was happening more clearly.
* section 3.3.6: "This example loads the Book_Info.xml, Preface.xml,
Chapter.xml, and Appendix.xml XML files."
no, it doesn't load Appendix.xml, it loads Revision_History.xml.
as we observed before, there is no auto-generated Appendix.xml file.
* section 3.3.7: "If you define an entity ? <!ENTITY LIFT "Liberty
Installation and Formatting Tome"> ? you can enter &LIFT; in your XML
and it will appear as The Secret to Eternal Life every time the book
is built ..."
- i'm pretty sure that's not true.
i think that's all i have for now.
rday
--
========================================================================
Robert P. J. Day Waterloo, Ontario, CANADA
Linux Consulting, Training and Annoying Kernel Pedantry.
Web page: http://crashcourse.ca
Linked In: http://www.linkedin.com/in/rpjday
Twitter: http://twitter.com/rpjday
========================================================================
From rpjday at crashcourse.ca Fri Jul 10 13:15:27 2009
From: rpjday at crashcourse.ca (Robert P. J. Day)
Date: Fri, 10 Jul 2009 09:15:27 -0400 (EDT)
Subject: [publican-list] Error in /usr/share/publican/make/Makefile.common
Message-ID: <alpine.LFD.2.00.0907100912250.1301@localhost>
line 181:
@if [ ! -d $(COMMON_CONTENT)/$(BRAND) ]; then \
echo; \
echo "*ERROR: Brand $(BRAND) is not installed*" ; \
echo "Either install $(BRAND) or change to a valid Brand."; \
echo "Installed Brands:" \ <---- ERROR
echo "`ls $(COMMON_CONTENT)`"; \
exit 1; \
fi
that line should have a semi-colon as do the rest of them. without
it, if you try to build with an uninstalled brand, you'll get:
*ERROR: Brand fedora is not installed*
Either install fedora or change to a valid Brand.
Installed Brands: echo common
make: *** [pre] Error 1
note how the word "echo" is printed as if it's an installed brand.
that shouldn't happen, of course. adding the semi-colon fixes it.
rday
--
========================================================================
Robert P. J. Day Waterloo, Ontario, CANADA
Linux Consulting, Training and Annoying Kernel Pedantry.
Web page: http://crashcourse.ca
Linked In: http://www.linkedin.com/in/rpjday
Twitter: http://twitter.com/rpjday
========================================================================
From stickster at gmail.com Fri Jul 10 13:29:36 2009
From: stickster at gmail.com (Paul W. Frields)
Date: Fri, 10 Jul 2009 09:29:36 -0400
Subject: [publican-list] and the repository is where?
In-Reply-To: <alpine.LFD.2.00.0907100116430.15677@localhost>
References: <alpine.LFD.2.00.0907100049260.15382@localhost>
<4A56CC91.7020106@redhat.com>
<alpine.LFD.2.00.0907100116430.15677@localhost>
Message-ID: <20090710132936.GD28530@localhost.localdomain>
On Fri, Jul 10, 2009 at 01:19:04AM -0400, Robert P. J. Day wrote:
> On Fri, 10 Jul 2009, Jeffrey Fearn wrote:
>
> > Robert P. J. Day wrote:
> ... snip ...
> > > http://fedoraproject.org/wiki/DocsProject/Publican
>
> > > Wiki: https://fedorahosted.org/publican
> >
> > The publican wiki is ^^^^^^^^^^^^^^^^^^^^
> >
> > It has the SVN info.
>
> ah, gotcha.
>
> > I'm not sure what that fedora docs page is doing there ... it's far
> > to well written for me to have simply forgotten I wrote it some time
> > in the distant past :D
>
> might want to toss that older page, then. when i googled for
> publican and repository, that's the one i ran across, and that might
> throw a few folks who end up there the same way.
It's a wiki! ;-) If you have a FAS account, log in to the wiki and
simply correct the instructions. Well, OK, I took care of this for
you already.
--
Paul W. Frields http://paul.frields.org/
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
http://redhat.com/ - - - - http://pfrields.fedorapeople.org/
irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug
From rpjday at crashcourse.ca Fri Jul 10 13:34:08 2009
From: rpjday at crashcourse.ca (Robert P. J. Day)
Date: Fri, 10 Jul 2009 09:34:08 -0400 (EDT)
Subject: [publican-list] and the repository is where?
In-Reply-To: <20090710132936.GD28530@localhost.localdomain>
References: <alpine.LFD.2.00.0907100049260.15382@localhost>
<4A56CC91.7020106@redhat.com>
<alpine.LFD.2.00.0907100116430.15677@localhost>
<20090710132936.GD28530@localhost.localdomain>
Message-ID: <alpine.LFD.2.00.0907100932120.1524@localhost>
On Fri, 10 Jul 2009, Paul W. Frields wrote:
> On Fri, Jul 10, 2009 at 01:19:04AM -0400, Robert P. J. Day wrote:
> > On Fri, 10 Jul 2009, Jeffrey Fearn wrote:
> >
> > > Robert P. J. Day wrote:
> > ... snip ...
> > > > http://fedoraproject.org/wiki/DocsProject/Publican
> >
> > > > Wiki: https://fedorahosted.org/publican
> > >
> > > The publican wiki is ^^^^^^^^^^^^^^^^^^^^
> > >
> > > It has the SVN info.
> >
> > ah, gotcha.
> >
> > > I'm not sure what that fedora docs page is doing there ... it's far
> > > to well written for me to have simply forgotten I wrote it some time
> > > in the distant past :D
> >
> > might want to toss that older page, then. when i googled for
> > publican and repository, that's the one i ran across, and that might
> > throw a few folks who end up there the same way.
>
> It's a wiki! ;-) If you have a FAS account, log in to the wiki and
> simply correct the instructions. Well, OK, I took care of this for
> you already.
i think the point that was made was that that page shouldn't even be
there, if i was reading jeff correctly. i thought he was suggesting
that fedorahosted.org/publican was the canonical wiki these days.
rday
--
========================================================================
Robert P. J. Day Waterloo, Ontario, CANADA
Linux Consulting, Training and Annoying Kernel Pedantry.
Web page: http://crashcourse.ca
Linked In: http://www.linkedin.com/in/rpjday
Twitter: http://twitter.com/rpjday
========================================================================
From rpjday at crashcourse.ca Fri Jul 10 13:35:37 2009
From: rpjday at crashcourse.ca (Robert P. J. Day)
Date: Fri, 10 Jul 2009 09:35:37 -0400 (EDT)
Subject: [publican-list] and the repository is where?
In-Reply-To: <20090710132936.GD28530@localhost.localdomain>
References: <alpine.LFD.2.00.0907100049260.15382@localhost>
<4A56CC91.7020106@redhat.com>
<alpine.LFD.2.00.0907100116430.15677@localhost>
<20090710132936.GD28530@localhost.localdomain>
Message-ID: <alpine.LFD.2.00.0907100934450.1557@localhost>
On Fri, 10 Jul 2009, Paul W. Frields wrote:
> It's a wiki! ;-) If you have a FAS account, log in to the wiki and
> simply correct the instructions. Well, OK, I took care of this for
> you already.
or you could give me commit access to the repository and i could fix
a lot of the things i'm currently reporting. you know, things like
the numerous misspellings of "separate" as "seperate". niggly stuff
like that. :-)
rday
--
========================================================================
Robert P. J. Day Waterloo, Ontario, CANADA
Linux Consulting, Training and Annoying Kernel Pedantry.
Web page: http://crashcourse.ca
Linked In: http://www.linkedin.com/in/rpjday
Twitter: http://twitter.com/rpjday
========================================================================
From stickster at gmail.com Fri Jul 10 13:45:10 2009
From: stickster at gmail.com (Paul W. Frields)
Date: Fri, 10 Jul 2009 09:45:10 -0400
Subject: [publican-list] and the repository is where?
In-Reply-To: <alpine.LFD.2.00.0907100932120.1524@localhost>
References: <alpine.LFD.2.00.0907100049260.15382@localhost>
<4A56CC91.7020106@redhat.com>
<alpine.LFD.2.00.0907100116430.15677@localhost>
<20090710132936.GD28530@localhost.localdomain>
<alpine.LFD.2.00.0907100932120.1524@localhost>
Message-ID: <20090710134510.GH28530@localhost.localdomain>
On Fri, Jul 10, 2009 at 09:34:08AM -0400, Robert P. J. Day wrote:
> On Fri, 10 Jul 2009, Paul W. Frields wrote:
> > It's a wiki! ;-) If you have a FAS account, log in to the wiki and
> > simply correct the instructions. Well, OK, I took care of this for
> > you already.
>
> i think the point that was made was that that page shouldn't even be
> there, if i was reading jeff correctly. i thought he was suggesting
> that fedorahosted.org/publican was the canonical wiki these days.
I put an admonition on the top of the page to send people to the
official page.
--
Paul W. Frields http://paul.frields.org/
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
http://redhat.com/ - - - - http://pfrields.fedorapeople.org/
irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug
From stickster at gmail.com Fri Jul 10 13:47:22 2009
From: stickster at gmail.com (Paul W. Frields)
Date: Fri, 10 Jul 2009 09:47:22 -0400
Subject: [publican-list] and the repository is where?
In-Reply-To: <alpine.LFD.2.00.0907100934450.1557@localhost>
References: <alpine.LFD.2.00.0907100049260.15382@localhost>
<4A56CC91.7020106@redhat.com>
<alpine.LFD.2.00.0907100116430.15677@localhost>
<20090710132936.GD28530@localhost.localdomain>
<alpine.LFD.2.00.0907100934450.1557@localhost>
Message-ID: <20090710134722.GI28530@localhost.localdomain>
On Fri, Jul 10, 2009 at 09:35:37AM -0400, Robert P. J. Day wrote:
> On Fri, 10 Jul 2009, Paul W. Frields wrote:
>
> > It's a wiki! ;-) If you have a FAS account, log in to the wiki and
> > simply correct the instructions. Well, OK, I took care of this for
> > you already.
>
> or you could give me commit access to the repository and i could fix
> a lot of the things i'm currently reporting. you know, things like
> the numerous misspellings of "separate" as "seperate". niggly stuff
> like that. :-)
True -- you can always send those things in as diffs, to this list for
example. (I don't have the ability to give you commit access
personally.)
Unfortunately, that repo, as far as I can tell, no longer contains up
to date Publican. The new Publican 1.0 that was announced isn't found
in any public repo that I can see from the fh.o/publican site.
Where's the code?
--
Paul W. Frields http://paul.frields.org/
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
http://redhat.com/ - - - - http://pfrields.fedorapeople.org/
irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug
From rpjday at crashcourse.ca Fri Jul 10 13:54:01 2009
From: rpjday at crashcourse.ca (Robert P. J. Day)
Date: Fri, 10 Jul 2009 09:54:01 -0400 (EDT)
Subject: [publican-list] and the repository is where?
In-Reply-To: <20090710134722.GI28530@localhost.localdomain>
References: <alpine.LFD.2.00.0907100049260.15382@localhost>
<4A56CC91.7020106@redhat.com>
<alpine.LFD.2.00.0907100116430.15677@localhost>
<20090710132936.GD28530@localhost.localdomain>
<alpine.LFD.2.00.0907100934450.1557@localhost>
<20090710134722.GI28530@localhost.localdomain>
Message-ID: <alpine.LFD.2.00.0907100951550.14241@localhost>
On Fri, 10 Jul 2009, Paul W. Frields wrote:
> On Fri, Jul 10, 2009 at 09:35:37AM -0400, Robert P. J. Day wrote:
> > On Fri, 10 Jul 2009, Paul W. Frields wrote:
> >
> > > It's a wiki! ;-) If you have a FAS account, log in to the wiki and
> > > simply correct the instructions. Well, OK, I took care of this for
> > > you already.
> >
> > or you could give me commit access to the repository and i could
> > fix a lot of the things i'm currently reporting. you know, things
> > like the numerous misspellings of "separate" as "seperate".
> > niggly stuff like that. :-)
>
> True -- you can always send those things in as diffs, to this list
> for example. (I don't have the ability to give you commit access
> personally.)
sure, that's doable, but what about changes to the user guide?
given the number of translations, how does one submit a patch against
something in the user guide? just against en-US? or what?
> Unfortunately, that repo, as far as I can tell, no longer contains
> up to date Publican. The new Publican 1.0 that was announced isn't
> found in any public repo that I can see from the fh.o/publican site.
>
> Where's the code?
/usr/share/publican/make/Makefile.common. *that* i can submit a
patch for.
rday
--
========================================================================
Robert P. J. Day Waterloo, Ontario, CANADA
Linux Consulting, Training and Annoying Kernel Pedantry.
Web page: http://crashcourse.ca
Linked In: http://www.linkedin.com/in/rpjday
Twitter: http://twitter.com/rpjday
========================================================================
From rpjday at crashcourse.ca Fri Jul 10 14:00:22 2009
From: rpjday at crashcourse.ca (Robert P. J. Day)
Date: Fri, 10 Jul 2009 10:00:22 -0400 (EDT)
Subject: [publican-list] so what *is* publican-genome?
Message-ID: <alpine.LFD.2.00.0907100955110.14285@localhost>
it's not mentioned here:
https://fedorahosted.org/publican/
but it's a yum-installable package, although what it produces looks
kind of crappy with the default book -- the section headings
splattered over top of the "Genome" graphic with a couple sizable
"oVirt" images on the first page.
given that it's in the standard fedora yum repo, it really should
work a bit better than that.
rday
p.s. i am not *trying* to be relentlessly annoying -- i am merely
succeeding. mercifully, i am almost out of complaints. :-)
--
========================================================================
Robert P. J. Day Waterloo, Ontario, CANADA
Linux Consulting, Training and Annoying Kernel Pedantry.
Web page: http://crashcourse.ca
Linked In: http://www.linkedin.com/in/rpjday
Twitter: http://twitter.com/rpjday
========================================================================
From rpjday at crashcourse.ca Fri Jul 10 14:17:43 2009
From: rpjday at crashcourse.ca (Robert P. J. Day)
Date: Fri, 10 Jul 2009 10:17:43 -0400 (EDT)
Subject: [publican-list] [PATCH] Correct "seperate" misspellings in
make/Makefile.common
Message-ID: <alpine.LFD.2.00.0907101016010.18723@localhost>
Correct misspellings of "seperate" to "separate" strictly in
Makefile.common.
Signed-off-by: Robert P. J. Day <rpjday at crashcourse.ca>
---
is this the proper format for submitted patches? i'm working off
the format i use for kernel patches.
Index: trunk/publican/make/Makefile.common
===================================================================
--- trunk/publican/make/Makefile.common (revision 736)
+++ trunk/publican/make/Makefile.common (working copy)
@@ -62,7 +62,7 @@
COMMON_CONTENT = $(COMMON_CONFIG)/Common_Content
-# a comma seperated list of other languages
+# a comma separated list of other languages
ifdef OTHER_LANGS
OTHER_LANGS_C = $(shell echo $(OTHER_LANGS) | sed -e 's/ /,/g')
endif
@@ -496,14 +496,14 @@
@echo
@echo "DOC_URL: URL for top right link in html. Currently: $(DOC_URL)"
@echo
- @echo "DT_OBSOLETES: A comma seperated list of desk top packages the package should obsolete. Currently: $(DT_OBSOLETES)"
+ @echo "DT_OBSOLETES: A comma separated list of desk top packages the package should obsolete. Currently: $(DT_OBSOLETES)"
@echo
@echo "GENERATE_SECTION_TOC_LEVEL: Include a TOC at the given section level. Currently: $(GENERATE_SECTION_TOC_LEVEL)"
@echo
@echo "IGNORED_TRANSLATIONS: When building replace any languages in this list with the source langauge text"
@echo " This allows you to work on translations without shipping incomplete translations. Currently: $(IGNORED_TRANSLATIONS)"
@echo
- @echo "OTHER_LANGS: space seperated list of language locales. Currently: $(OTHER_LANGS)"
+ @echo "OTHER_LANGS: space separated list of language locales. Currently: $(OTHER_LANGS)"
@echo
@echo "PRODUCT: Product this book is associated with. Currently: $(PRODUCT)"
@echo " When this book is published it will be nested in a directory named after the product"
@@ -518,7 +518,7 @@
@echo
@echo "WEB_BREW_DIST: brew tag to use for web rpms. Currently: $(WEB_BREW_DIST)"
@echo
- @echo "WEB_OBSOLETES: A comma seperated list of web site packages the web package should obsolete. Currently: $(WEB_OBSOLETES)"
+ @echo "WEB_OBSOLETES: A comma separated list of web site packages the web package should obsolete. Currently: $(WEB_OBSOLETES)"
@echo
@echo "XML_DESKTOP: Use XML for the desktop package instead of the default html-single. Currently: $(XML_DESKTOP)"
@echo
@@ -541,11 +541,11 @@
@echo
@echo "EXTRA_DIRS: Helps handle nested directories."
@echo
- @echo "EXTRA_DIRS_C: Comma seperated list of EXTRA_DIRS."
+ @echo "EXTRA_DIRS_C: Comma separated list of EXTRA_DIRS."
@echo
@echo "FORMATS: Output formats currently supported. Currently: $(FORMATS)."
@echo
- @echo "OTHER_LANGS_C: Comma seperated list of non-source languages."
+ @echo "OTHER_LANGS_C: Comma separated list of non-source languages."
@echo
@echo "PWD: present working directory."
@echo
========================================================================
Robert P. J. Day Waterloo, Ontario, CANADA
Linux Consulting, Training and Annoying Kernel Pedantry.
Web page: http://crashcourse.ca
Twitter: http://twitter.com/rpjday
"Kernel Newbie Corner" column @ linux.com: http://cli.gs/WG6WYX
========================================================================
From eric at christensenplace.us Fri Jul 10 14:53:20 2009
From: eric at christensenplace.us (Eric Christensen)
Date: Fri, 10 Jul 2009 10:53:20 -0400
Subject: [publican-list] and the repository is where?
In-Reply-To: <alpine.LFD.2.00.0907100951550.14241@localhost>
References: <alpine.LFD.2.00.0907100049260.15382@localhost>
<4A56CC91.7020106@redhat.com>
<alpine.LFD.2.00.0907100116430.15677@localhost>
<20090710132936.GD28530@localhost.localdomain>
<alpine.LFD.2.00.0907100934450.1557@localhost>
<20090710134722.GI28530@localhost.localdomain>
<alpine.LFD.2.00.0907100951550.14241@localhost>
Message-ID: <1247237600.2520.8.camel@thunder.christensenplace.us>
On Fri, 2009-07-10 at 09:54 -0400, Robert P. J. Day wrote:
> sure, that's doable, but what about changes to the user guide?
> given the number of translations, how does one submit a patch against
> something in the user guide? just against en-US? or what?
> rday
Robert,
There should be a feedback page at the beginning of the User Guide (and
every guide) that shows users how to provide feedback. I'm pretty sure
you do that on BZ [1].
[1]
https://bugzilla.redhat.com/enter_bug.cgi?component=desktop-user-guide&product=Fedora%20Documentation
--
Thanks,
Eric Christensen
Fedora Docs Project Lead
Fedora Talk: 5102043 Phone: 919-424-0063 x 5102043
E-Mail: sparks at fedoraproject.org SIP: sparks at talk.fedoraproject.org
IRC: Sparks on freenode.net
GPG Fingerprint: CA02 4ACA EB6C 1A76 F0D6 1127 7D04 D240 BD0C 14C1
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part
URL: <http://listman.redhat.com/archives/publican-list/attachments/20090710/e7bfff11/attachment.sig>
From rpjday at crashcourse.ca Fri Jul 10 15:13:13 2009
From: rpjday at crashcourse.ca (Robert P. J. Day)
Date: Fri, 10 Jul 2009 11:13:13 -0400 (EDT)
Subject: [publican-list] and the repository is where?
In-Reply-To: <1247237600.2520.8.camel@thunder.christensenplace.us>
References: <alpine.LFD.2.00.0907100049260.15382@localhost>
<4A56CC91.7020106@redhat.com>
<alpine.LFD.2.00.0907100116430.15677@localhost>
<20090710132936.GD28530@localhost.localdomain>
<alpine.LFD.2.00.0907100934450.1557@localhost>
<20090710134722.GI28530@localhost.localdomain>
<alpine.LFD.2.00.0907100951550.14241@localhost>
<1247237600.2520.8.camel@thunder.christensenplace.us>
Message-ID: <alpine.LFD.2.00.0907101112350.19361@localhost>
On Fri, 10 Jul 2009, Eric Christensen wrote:
> On Fri, 2009-07-10 at 09:54 -0400, Robert P. J. Day wrote:
> > sure, that's doable, but what about changes to the user guide?
> > given the number of translations, how does one submit a patch against
> > something in the user guide? just against en-US? or what?
> > rday
>
>
> Robert,
> There should be a feedback page at the beginning of the User Guide (and
> every guide) that shows users how to provide feedback. I'm pretty sure
> you do that on BZ [1].
>
> [1]
> https://bugzilla.redhat.com/enter_bug.cgi?component=desktop-user-guide&product=Fedora%20Documentation
it would take me less time to generate and submit patches than it
would to fight with the nightmare that is bugzilla.
rday
--
========================================================================
Robert P. J. Day Waterloo, Ontario, CANADA
Linux Consulting, Training and Annoying Kernel Pedantry.
Web page: http://crashcourse.ca
Twitter: http://twitter.com/rpjday
"Kernel Newbie Corner" column @ linux.com: http://cli.gs/WG6WYX
========================================================================
From eric at christensenplace.us Fri Jul 10 15:28:23 2009
From: eric at christensenplace.us (Eric Christensen)
Date: Fri, 10 Jul 2009 11:28:23 -0400
Subject: [publican-list] and the repository is where?
In-Reply-To: <alpine.LFD.2.00.0907101112350.19361@localhost>
References: <alpine.LFD.2.00.0907100049260.15382@localhost>
<4A56CC91.7020106@redhat.com>
<alpine.LFD.2.00.0907100116430.15677@localhost>
<20090710132936.GD28530@localhost.localdomain>
<alpine.LFD.2.00.0907100934450.1557@localhost>
<20090710134722.GI28530@localhost.localdomain>
<alpine.LFD.2.00.0907100951550.14241@localhost>
<1247237600.2520.8.camel@thunder.christensenplace.us>
<alpine.LFD.2.00.0907101112350.19361@localhost>
Message-ID: <1247239703.2520.22.camel@thunder.christensenplace.us>
On Fri, 2009-07-10 at 11:13 -0400, Robert P. J. Day wrote:
> On Fri, 10 Jul 2009, Eric Christensen wrote:
>
> > On Fri, 2009-07-10 at 09:54 -0400, Robert P. J. Day wrote:
> > > sure, that's doable, but what about changes to the user guide?
> > > given the number of translations, how does one submit a patch against
> > > something in the user guide? just against en-US? or what?
> > > rday
> >
> >
> > Robert,
> > There should be a feedback page at the beginning of the User Guide (and
> > every guide) that shows users how to provide feedback. I'm pretty sure
> > you do that on BZ [1].
> >
> > [1]
> > https://bugzilla.redhat.com/enter_bug.cgi?component=desktop-user-guide&product=Fedora%20Documentation
>
> it would take me less time to generate and submit patches than it
> would to fight with the nightmare that is bugzilla.
>
> rday
> --
Bugzilla really isn't a nightmare (takes me about 10 seconds to submit a
patch). It provides us an easy way of tracking patches and making sure
that everything happens.
--Eric
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part
URL: <http://listman.redhat.com/archives/publican-list/attachments/20090710/addd3954/attachment.sig>
From rpjday at crashcourse.ca Fri Jul 10 15:35:16 2009
From: rpjday at crashcourse.ca (Robert P. J. Day)
Date: Fri, 10 Jul 2009 11:35:16 -0400 (EDT)
Subject: [publican-list] and the repository is where?
In-Reply-To: <1247239703.2520.22.camel@thunder.christensenplace.us>
References: <alpine.LFD.2.00.0907100049260.15382@localhost>
<4A56CC91.7020106@redhat.com>
<alpine.LFD.2.00.0907100116430.15677@localhost>
<20090710132936.GD28530@localhost.localdomain>
<alpine.LFD.2.00.0907100934450.1557@localhost>
<20090710134722.GI28530@localhost.localdomain>
<alpine.LFD.2.00.0907100951550.14241@localhost>
<1247237600.2520.8.camel@thunder.christensenplace.us>
<alpine.LFD.2.00.0907101112350.19361@localhost>
<1247239703.2520.22.camel@thunder.christensenplace.us>
Message-ID: <alpine.LFD.2.00.0907101131300.19560@localhost>
On Fri, 10 Jul 2009, Eric Christensen wrote:
> Bugzilla really isn't a nightmare (takes me about 10 seconds to
> submit a patch). It provides us an easy way of tracking patches and
> making sure that everything happens.
*sigh*. i have no problem using BZ if i've found what i think is a
significant issue, whereupon i *will* be as complete and detailed as
possible because i want someone else more knowledgeable to take care
of it.
in *this* case, however, it actually takes less time to just create
a patch of the appropriate form (of which i am still uncertain since
no one has confirmed exactly what form of patch is proper on this ML)
and just post it to the list so someone can apply it.
seriously, if i have to go thru BZ to submit these types of patches,
i'm not going to bother with any of it. i save BZ for reports that
*matter*. i have no intention of inflicting BZ on myself for
correcting trivial errors or typoes.
rday
--
========================================================================
Robert P. J. Day Waterloo, Ontario, CANADA
Linux Consulting, Training and Annoying Kernel Pedantry.
Web page: http://crashcourse.ca
Twitter: http://twitter.com/rpjday
"Kernel Newbie Corner" column @ linux.com: http://cli.gs/WG6WYX
========================================================================
From stickster at gmail.com Fri Jul 10 15:59:10 2009
From: stickster at gmail.com (Paul W. Frields)
Date: Fri, 10 Jul 2009 11:59:10 -0400
Subject: [publican-list] and the repository is where?
In-Reply-To: <alpine.LFD.2.00.0907101131300.19560@localhost>
References: <4A56CC91.7020106@redhat.com>
<alpine.LFD.2.00.0907100116430.15677@localhost>
<20090710132936.GD28530@localhost.localdomain>
<alpine.LFD.2.00.0907100934450.1557@localhost>
<20090710134722.GI28530@localhost.localdomain>
<alpine.LFD.2.00.0907100951550.14241@localhost>
<1247237600.2520.8.camel@thunder.christensenplace.us>
<alpine.LFD.2.00.0907101112350.19361@localhost>
<1247239703.2520.22.camel@thunder.christensenplace.us>
<alpine.LFD.2.00.0907101131300.19560@localhost>
Message-ID: <20090710155910.GM28530@localhost.localdomain>
On Fri, Jul 10, 2009 at 11:35:16AM -0400, Robert P. J. Day wrote:
> On Fri, 10 Jul 2009, Eric Christensen wrote:
>
> > Bugzilla really isn't a nightmare (takes me about 10 seconds to
> > submit a patch). It provides us an easy way of tracking patches and
> > making sure that everything happens.
>
> *sigh*. i have no problem using BZ if i've found what i think is a
> significant issue, whereupon i *will* be as complete and detailed as
> possible because i want someone else more knowledgeable to take care
> of it.
>
> in *this* case, however, it actually takes less time to just create
> a patch of the appropriate form (of which i am still uncertain since
> no one has confirmed exactly what form of patch is proper on this ML)
> and just post it to the list so someone can apply it.
>
> seriously, if i have to go thru BZ to submit these types of patches,
> i'm not going to bother with any of it. i save BZ for reports that
> *matter*. i have no intention of inflicting BZ on myself for
> correcting trivial errors or typoes.
If I can make a suggestion... I use the 'bugzilla' command-line
utility often to file bugs, because it's fast and easy compared to the
Web browser. So for example:
$ bugzilla login # Then enter BZ username and password, makes a
# cookie that's used from here on out...
$ bugzilla info -c 'Fedora Documentation' # Tell me the components
# in this product (only
# if you don't know which)
$ bugzilla new -p 'Fedora Documentation' -v 'rawhide' \
-c 'security-guide' -s 'Security Guide missing foobar' \
-l "Looking at Security Guide, en-US 0.2. It doesn't have
a reference to foobar. Patch forthcoming."
The bug number spits back out to you, and you can visit it to attach
your file, which itself is a very fast operation nowadays, especially
since some HW and DB upgrades.
--
Paul W. Frields http://paul.frields.org/
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
http://redhat.com/ - - - - http://pfrields.fedorapeople.org/
irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug
From stickster at gmail.com Fri Jul 10 16:02:05 2009
From: stickster at gmail.com (Paul W. Frields)
Date: Fri, 10 Jul 2009 12:02:05 -0400
Subject: [publican-list] and the repository is where?
In-Reply-To: <alpine.LFD.2.00.0907101131300.19560@localhost>
References: <4A56CC91.7020106@redhat.com>
<alpine.LFD.2.00.0907100116430.15677@localhost>
<20090710132936.GD28530@localhost.localdomain>
<alpine.LFD.2.00.0907100934450.1557@localhost>
<20090710134722.GI28530@localhost.localdomain>
<alpine.LFD.2.00.0907100951550.14241@localhost>
<1247237600.2520.8.camel@thunder.christensenplace.us>
<alpine.LFD.2.00.0907101112350.19361@localhost>
<1247239703.2520.22.camel@thunder.christensenplace.us>
<alpine.LFD.2.00.0907101131300.19560@localhost>
Message-ID: <20090710160205.GN28530@localhost.localdomain>
On Fri, Jul 10, 2009 at 11:35:16AM -0400, Robert P. J. Day wrote:
> in *this* case, however, it actually takes less time to just create
> a patch of the appropriate form (of which i am still uncertain since
> no one has confirmed exactly what form of patch is proper on this ML)
> and just post it to the list so someone can apply it.
And I can't speak for patch email for the Publican repo, since it's
SVN. I'd assume 'svn diff -u | mail -s "Description of fix"' would be
OK. Git makes this dead-simple, but it's up to the maintainers for a
project to tell you what they prefer, otherwise.
--
Paul W. Frields http://paul.frields.org/
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
http://redhat.com/ - - - - http://pfrields.fedorapeople.org/
irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug
From rpjday at crashcourse.ca Fri Jul 10 16:27:28 2009
From: rpjday at crashcourse.ca (Robert P. J. Day)
Date: Fri, 10 Jul 2009 12:27:28 -0400 (EDT)
Subject: [publican-list] and the repository is where?
In-Reply-To: <20090710155910.GM28530@localhost.localdomain>
References: <4A56CC91.7020106@redhat.com>
<alpine.LFD.2.00.0907100116430.15677@localhost>
<20090710132936.GD28530@localhost.localdomain>
<alpine.LFD.2.00.0907100934450.1557@localhost>
<20090710134722.GI28530@localhost.localdomain>
<alpine.LFD.2.00.0907100951550.14241@localhost>
<1247237600.2520.8.camel@thunder.christensenplace.us>
<alpine.LFD.2.00.0907101112350.19361@localhost>
<1247239703.2520.22.camel@thunder.christensenplace.us>
<alpine.LFD.2.00.0907101131300.19560@localhost>
<20090710155910.GM28530@localhost.localdomain>
Message-ID: <alpine.LFD.2.00.0907101226550.20155@localhost>
On Fri, 10 Jul 2009, Paul W. Frields wrote:
> If I can make a suggestion... I use the 'bugzilla' command-line
> utility often to file bugs, because it's fast and easy compared to the
> Web browser. So for example:
i give up. seriously. i just don't have time for this.
rday
--
========================================================================
Robert P. J. Day Waterloo, Ontario, CANADA
Linux Consulting, Training and Annoying Kernel Pedantry.
Web page: http://crashcourse.ca
Twitter: http://twitter.com/rpjday
"Kernel Newbie Corner" column @ linux.com: http://cli.gs/WG6WYX
========================================================================
From jaredsmith at jaredsmith.net Fri Jul 10 18:14:23 2009
From: jaredsmith at jaredsmith.net (Jared Smith)
Date: Fri, 10 Jul 2009 14:14:23 -0400
Subject: [publican-list] and the repository is where?
In-Reply-To: <alpine.LFD.2.00.0907101226550.20155@localhost>
References: <4A56CC91.7020106@redhat.com>
<alpine.LFD.2.00.0907100116430.15677@localhost>
<20090710132936.GD28530@localhost.localdomain>
<alpine.LFD.2.00.0907100934450.1557@localhost>
<20090710134722.GI28530@localhost.localdomain>
<alpine.LFD.2.00.0907100951550.14241@localhost>
<1247237600.2520.8.camel@thunder.christensenplace.us>
<alpine.LFD.2.00.0907101112350.19361@localhost>
<1247239703.2520.22.camel@thunder.christensenplace.us>
<alpine.LFD.2.00.0907101131300.19560@localhost>
<20090710155910.GM28530@localhost.localdomain>
<alpine.LFD.2.00.0907101226550.20155@localhost>
Message-ID: <1247249663.2852.59.camel@hockey.jaredsmith.net>
On Fri, 2009-07-10 at 12:27 -0400, Robert P. J. Day wrote:
> i give up. seriously. i just don't have time for this.
Hi Robert... I'm not sure we've ever met, and I don't remember seeing
any comments from you previously on the publican list, so it's good to
meet you (well, as much as you can really meet someone in a mailing
list).
If you don't have time to send in a bugzilla ticket, email me the
patches and I'd be happy to open bugzilla tickets for each and every
one.
Seriously. I'd be happy to spend a little of my own time to save some
of yours.
May I suggest in passing, though, that you lose the attitude. I don't
know you from Adam, and I'm sure you're a really nice guy in real life,
and I'm sure you're infinitely smarter than I can ever hope to be.. but
based on what I've seen over the past few hours in the mailing list, I
can honestly say you're not doing yourself any favors.
Who am I, you might ask? I'm nobody... I'm just another guy who happens
to use Publican, follows the mailing list, and contributes patches from
time to time. But I'm also another guy who happened to be quite
appalled at the tone of your recent posts.
The methodology of open source development means that sometimes
documentation isn't correct or up-to-date, and sometimes mere mortals
make mistakes (heaven forbid!). As I see it, you're one of the few that
thinks that in open communities, he who shouts the loudest wins. And
the sense of entitlement ("You must give me access to the repository to
fix grammar problems even though I can't manage to capitalize my
sentences" and "I'd be happy to help and make suggestions, but only if
you guys cater to my whims") makes developers *less* likely for the
Publican developers (again, I'm not one) to listen to you, not more.
Now, I'm not saying that Publican is perfect... I'm simply saying that
the way we communicate will have an effect on how Publican gets to where
we want it to be.
My two cents... (before taxes)
-Jared
From jfearn at redhat.com Mon Jul 13 00:29:50 2009
From: jfearn at redhat.com (Jeffrey Fearn)
Date: Mon, 13 Jul 2009 10:29:50 +1000
Subject: [publican-list] newbie observations on building publican from SVN
In-Reply-To: <alpine.LFD.2.00.0907100212290.3759@localhost>
References: <alpine.LFD.2.00.0907100212290.3759@localhost>
Message-ID: <4A5A7FFE.9060405@redhat.com>
Hi Robert, I'm putting the finishing touches on a hobby project I've
been working on of rewriting publican in perl. This will change lots of
things, including making half the UG obsolete and removing all Makefiles.
The Red Hat docs team are organizing a public beta test to give the
rewrite a flogging.
I'll do my best to respond to the issues you have raised, but a few of
them will basically be "I already killed that bit" :)
Robert P. J. Day wrote:
> from the perspective of someone who built publican from the repo for
> the very first time a few minutes ago:
>
> * the README file suggests i can get make help with one of "make help"
> or "make help_params". neither of those targets seem to be supported.
This relates to commands you can run in a book not the publican build.
This has all completely changed so this file will have to be completely
rewritten.
> * the build on a fully-updated f11 x86_64 system generates numerous
> "... Legal_Notice.po MISSING Using en-US file" warnings. doesn't stop
> the build, though.
This is kind of correct, the Legal Notice file should never be
translated. But there isn't a way to mark pages as "never translate" ...
that would be a cool function :D
> * doing a straight "make" clearly attempts to *install* the
> constructed rpm. that's kind of unusual, isn't it? i'm more used to
> having to do that explicitly, with "make install". only after i
> looked at the Makefile did i see the more limited "make rpm" target.
The make files are heinous! The rewrite uses Module::Build and works as
expected.
Cheers, Jeff.
--
Jeff Fearn <jfearn at redhat.com>
Software Engineer
Engineering Operations
Red Hat, Inc
Freedom ... courage ... Commitment ... ACCOUNTABILITY
http://file.bne.redhat.com/~jfearn/
From jfearn at redhat.com Mon Jul 13 00:31:02 2009
From: jfearn at redhat.com (Jeffrey Fearn)
Date: Mon, 13 Jul 2009 10:31:02 +1000
Subject: [publican-list] publican-doc-0.45 users guide still reads "0.44"
In-Reply-To: <alpine.LFD.2.00.0907100239410.31860@localhost>
References: <alpine.LFD.2.00.0907100239410.31860@localhost>
Message-ID: <4A5A8046.1010408@redhat.com>
Robert P. J. Day wrote:
> not a big deal but, from the svn build, the file
> file:///usr/share/doc/publican-doc-0.45/en-US/index.html still reads
> "Publican 0.44" on the front page.
I am harassing the Red hat docs team leader for a writer to rewrite the
UG for the beta test, I will increase harassment.
Cheers, Jeff.
--
Jeff Fearn <jfearn at redhat.com>
Software Engineer
Engineering Operations
Red Hat, Inc
Freedom ... courage ... Commitment ... ACCOUNTABILITY
http://file.bne.redhat.com/~jfearn/
From jfearn at redhat.com Mon Jul 13 00:41:05 2009
From: jfearn at redhat.com (Jeffrey Fearn)
Date: Mon, 13 Jul 2009 10:41:05 +1000
Subject: [publican-list] random observations on svn checkout of users guide
In-Reply-To: <alpine.LFD.2.00.0907100306070.5776@localhost>
References: <alpine.LFD.2.00.0907100306070.5776@localhost>
Message-ID: <4A5A82A1.7050508@redhat.com>
Robert P. J. Day wrote:
> figured i might as well peruse the users guide from beginning to end
> so here's some random observations.
>
> * as i mentioned already, version 0.45 of the UG still has a title of
> "0.44"
>
> * section 1.2, "Source-code listings are also set in mono-spaced roman
> but add syntax highlighting as follows:"
>
> - in my browser, i see no example of "syntax highlighting". am i
> supposed to see something representing an example of
> highlighting there? it's just straight mono-spaced roman.
Publican is not a Fedora project and some of the functionality is not
available in Fedora due to packaging issues. In this case if you don't
have xslthl installed, which is not packaged for Fedora, then you won't
see highlighting.
The beta version uses a perl library for this, which is also not in
Fedora, but it should be easier to get that in to Fedora.
> * perhaps off-topic but will publican work with the relax ng schema of
> docbook 5.0? it's possible that's mentioned later in the UG and i
> just haven't got to it yet.
It would require a small amount of tweaking to support NG, but it will
require a massive amount of QA on the changes it introduces.
> * Chapter 2 refers to five different brand packages, yet yum sees only
> the following at the moment:
>
> $ yum search publican
> publican.noarch : Common files and scripts for publishing with DocBook XML
> publican-doc.noarch : Documentation for the Publican package
> publican-fedora.noarch : Publican documentation template files for fedora
> publican-genome.noarch : Common documentation files for genome
> publican-ovirt.noarch : Common documentation files for oVirt
> $
>
> where are the packages for gimp, redhat and jboss? are they in the
> works? and that UG table says nothing about publican-genome (whatever
> that is).
The Red Hat and JBoss brands never made it past Fedora packaging, but
they are available to RHEL users. publican-genome is a community brand
and not maintained by the publican team. I'm really happy
publican-genome got created as it is a shining example of exactly why we
went with this approach to branding.
Chapter 3 needs a complete rewrite since the beta completely changes the
interaction of the user.
> * Section 3.1:
>
> "Run the following command to install the publican package:
>
> # yum install publican publican-doc
>
> i would rephrase that as installing the package *and* its associated
> documentation package since, AFAICT, they can be installed
> independently, no?
>
> and just below that:
>
> # yum install publican-brand
>
> Replace brand with redhat, fedora, jboss, ovirt, or gimp.
>
> we've already noticed that some of those packages don't seem to
> exist, at least for a stock f11 x86_64 install.
Yup, Publican is not a Fedora project and the instructions cover things
available on different platforms. We probably need to make that clearer.
> * section 3.2 lists the create_book options "--help" and "--man" while
> the actual help output lists them as "-help" and "-man". both work
> but perhaps those should be made consistent to avoid confusion.
>
> also, that list of options in Section 3.2 doesn't mention "--lang".
>
> * still in Section 3.2, the instructions to create a new book fail to
> note that, after running that create_book command, you need to "cd
> Test_Book" before running ls. i'm sure readers will notice that right
> away but you might as well be explicit to be accurate.
>
> * Figure 3.1 lists an alleged new file "Appendix.xml". i see no such
> file after a book creation.
Cheers, Jeff.
--
Jeff Fearn <jfearn at redhat.com>
Software Engineer
Engineering Operations
Red Hat, Inc
Freedom ... courage ... Commitment ... ACCOUNTABILITY
http://file.bne.redhat.com/~jfearn/
From jfearn at redhat.com Mon Jul 13 00:42:47 2009
From: jfearn at redhat.com (Jeffrey Fearn)
Date: Mon, 13 Jul 2009 10:42:47 +1000
Subject: [publican-list] "make srpm-en-US" fails, "bad date in %changelog"
In-Reply-To: <alpine.LFD.2.00.0907100637180.14233@localhost>
References: <alpine.LFD.2.00.0907100637180.14233@localhost>
Message-ID: <4A5A8307.50409@redhat.com>
Robert P. J. Day wrote:
> not sure if this is a known issue but with a brand new generic book
> via "create_book --name Test_Book":
>
> $ make srpm-en-US
> ...
> END: xml-en-US Fri Jul 10 06:34:05 EDT 2009
> START: test-en-US Fri Jul 10 06:34:05 EDT 2009
> warning: failed to load external entity "tmp/en-US/xml/Feedback.xml"
> ...
> END: spec-en-US Fri Jul 10 06:34:06 EDT 2009
> START: srpm-en-US Fri Jul 10 06:34:06 EDT 2009
> error: bad date in %changelog: 1.0
> make: *** [srpm-en-US] Error 1
> $
>
> i thought that might have been this:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=478950
>
> but it doesn't look like it.
The dates in the Revision History have to match the format expected by rpm.
The beta uses a perl date manipulation routine to refortmat this, so any
valid date should work.
Cheers, Jeff.
--
Jeff Fearn <jfearn at redhat.com>
Software Engineer
Engineering Operations
Red Hat, Inc
Freedom ... courage ... Commitment ... ACCOUNTABILITY
http://file.bne.redhat.com/~jfearn/
From jfearn at redhat.com Mon Jul 13 00:46:21 2009
From: jfearn at redhat.com (Jeffrey Fearn)
Date: Mon, 13 Jul 2009 10:46:21 +1000
Subject: [publican-list] and the repository is where?
In-Reply-To: <alpine.LFD.2.00.0907100934450.1557@localhost>
References: <alpine.LFD.2.00.0907100049260.15382@localhost> <4A56CC91.7020106@redhat.com> <alpine.LFD.2.00.0907100116430.15677@localhost> <20090710132936.GD28530@localhost.localdomain>
<alpine.LFD.2.00.0907100934450.1557@localhost>
Message-ID: <4A5A83DD.4070801@redhat.com>
Robert P. J. Day wrote:
> On Fri, 10 Jul 2009, Paul W. Frields wrote:
>
>> It's a wiki! ;-) If you have a FAS account, log in to the wiki and
>> simply correct the instructions. Well, OK, I took care of this for
>> you already.
>
> or you could give me commit access to the repository and i could fix
> a lot of the things i'm currently reporting. you know, things like
> the numerous misspellings of "separate" as "seperate". niggly stuff
> like that. :-)
We really need to have a policy on how people get access. Like submit X
patches or buy Jeff X six pack[s] of Cider, something formal anyways.
Discuss!
Cheers, Jeff.
--
Jeff Fearn <jfearn at redhat.com>
Software Engineer
Engineering Operations
Red Hat, Inc
Freedom ... courage ... Commitment ... ACCOUNTABILITY
http://file.bne.redhat.com/~jfearn/
From jfearn at redhat.com Mon Jul 13 00:49:36 2009
From: jfearn at redhat.com (Jeffrey Fearn)
Date: Mon, 13 Jul 2009 10:49:36 +1000
Subject: [publican-list] and the repository is where?
In-Reply-To: <20090710134722.GI28530@localhost.localdomain>
References: <alpine.LFD.2.00.0907100049260.15382@localhost> <4A56CC91.7020106@redhat.com> <alpine.LFD.2.00.0907100116430.15677@localhost> <20090710132936.GD28530@localhost.localdomain> <alpine.LFD.2.00.0907100934450.1557@localhost>
<20090710134722.GI28530@localhost.localdomain>
Message-ID: <4A5A84A0.8050100@redhat.com>
Paul W. Frields wrote:
> On Fri, Jul 10, 2009 at 09:35:37AM -0400, Robert P. J. Day wrote:
>> On Fri, 10 Jul 2009, Paul W. Frields wrote:
>>
>>> It's a wiki! ;-) If you have a FAS account, log in to the wiki and
>>> simply correct the instructions. Well, OK, I took care of this for
>>> you already.
>> or you could give me commit access to the repository and i could fix
>> a lot of the things i'm currently reporting. you know, things like
>> the numerous misspellings of "separate" as "seperate". niggly stuff
>> like that. :-)
>
> True -- you can always send those things in as diffs, to this list for
> example. (I don't have the ability to give you commit access
> personally.)
>
> Unfortunately, that repo, as far as I can tell, no longer contains up
> to date Publican. The new Publican 1.0 that was announced isn't found
> in any public repo that I can see from the fh.o/publican site.
>
> Where's the code?
>
It's on my laptop. It will be checked in to the SVN repo before the beta.
Cheers, Jeff.
--
Jeff Fearn <jfearn at redhat.com>
Software Engineer
Engineering Operations
Red Hat, Inc
Freedom ... courage ... Commitment ... ACCOUNTABILITY
http://file.bne.redhat.com/~jfearn/
From jfearn at redhat.com Mon Jul 13 00:58:34 2009
From: jfearn at redhat.com (Jeffrey Fearn)
Date: Mon, 13 Jul 2009 10:58:34 +1000
Subject: [publican-list] so what *is* publican-genome?
In-Reply-To: <alpine.LFD.2.00.0907100955110.14285@localhost>
References: <alpine.LFD.2.00.0907100955110.14285@localhost>
Message-ID: <4A5A86BA.1000201@redhat.com>
Robert P. J. Day wrote:
> it's not mentioned here:
publican-genome is a community owned brand! I love this!
See: https://fedorahosted.org/genome/
They probably need to change the URLs in their spec file to point to the
genome project.
It's pretty hard to make a brand with the 0.x publican, so I'm not going
to harass people about them. The beta makes this much easier, still
probably need some finessing though.
> https://fedorahosted.org/publican/
>
> but it's a yum-installable package, although what it produces looks
> kind of crappy with the default book -- the section headings
> splattered over top of the "Genome" graphic with a couple sizable
> "oVirt" images on the first page.
>
> given that it's in the standard fedora yum repo, it really should
> work a bit better than that.
>
> rday
>
> p.s. i am not *trying* to be relentlessly annoying -- i am merely
> succeeding. mercifully, i am almost out of complaints. :-)
<voice accent="crocodile_dundee">
That's not relentlessly annoying...
</voice>
BTW I'm Australian so that outback accent isn't so hard to achieve ;)
Cheers, Jeff.
--
Jeff Fearn <jfearn at redhat.com>
Software Engineer
Engineering Operations
Red Hat, Inc
Freedom ... courage ... Commitment ... ACCOUNTABILITY
http://file.bne.redhat.com/~jfearn/
From mhideo at redhat.com Mon Jul 13 22:07:09 2009
From: mhideo at redhat.com (Michael Hideo)
Date: Tue, 14 Jul 2009 08:07:09 +1000
Subject: [publican-list] publican-doc-0.45 users guide still reads "0.44"
In-Reply-To: <4A5A8046.1010408@redhat.com>
References: <alpine.LFD.2.00.0907100239410.31860@localhost>
<4A5A8046.1010408@redhat.com>
Message-ID: <4A5BB00D.8030001@redhat.com>
Jeffrey Fearn wrote:
> Robert P. J. Day wrote:
>> not a big deal but, from the svn build, the file
>> file:///usr/share/doc/publican-doc-0.45/en-US/index.html still reads
>> "Publican 0.44" on the front page.
>
> I am harassing the Red hat docs team leader for a writer to rewrite the
> UG for the beta test, I will increase harassment.
>
Hi Jeff,
I will circle back to this on thursday once i have regression tests
written. that is about as far ahead as i can plan right now.
- Mike
From rpjday at crashcourse.ca Tue Jul 14 13:31:32 2009
From: rpjday at crashcourse.ca (Robert P. J. Day)
Date: Tue, 14 Jul 2009 09:31:32 -0400 (EDT)
Subject: [publican-list] newbie observations on building publican from SVN
In-Reply-To: <4A5A7FFE.9060405@redhat.com>
References: <alpine.LFD.2.00.0907100212290.3759@localhost>
<4A5A7FFE.9060405@redhat.com>
Message-ID: <alpine.LFD.2.00.0907140929250.4355@localhost>
On Mon, 13 Jul 2009, Jeffrey Fearn wrote:
> Hi Robert, I'm putting the finishing touches on a hobby project I've
> been working on of rewriting publican in perl. This will change lots
> of things, including making half the UG obsolete and removing all
> Makefiles.
>
> The Red Hat docs team are organizing a public beta test to give the
> rewrite a flogging.
i'm guessing that that beta test will be announced here when it's
ready to go? i'd be happy to pound on it.
rday
--
========================================================================
Robert P. J. Day Waterloo, Ontario, CANADA
Linux Consulting, Training and Annoying Kernel Pedantry.
Web page: http://crashcourse.ca
Twitter: http://twitter.com/rpjday
"Kernel Newbie Corner" column @ linux.com: http://cli.gs/WG6WYX
========================================================================
From jfearn at redhat.com Tue Jul 14 22:00:41 2009
From: jfearn at redhat.com (Jeffrey Fearn)
Date: Wed, 15 Jul 2009 08:00:41 +1000
Subject: [publican-list] newbie observations on building publican from SVN
In-Reply-To: <alpine.LFD.2.00.0907140929250.4355@localhost>
References: <alpine.LFD.2.00.0907100212290.3759@localhost>
<4A5A7FFE.9060405@redhat.com>
<alpine.LFD.2.00.0907140929250.4355@localhost>
Message-ID: <4A5D0009.9010305@redhat.com>
Robert P. J. Day wrote:
> On Mon, 13 Jul 2009, Jeffrey Fearn wrote:
>
>> Hi Robert, I'm putting the finishing touches on a hobby project I've
>> been working on of rewriting publican in perl. This will change lots
>> of things, including making half the UG obsolete and removing all
>> Makefiles.
>>
>> The Red Hat docs team are organizing a public beta test to give the
>> rewrite a flogging.
>
> i'm guessing that that beta test will be announced here when it's
> ready to go? i'd be happy to pound on it.
There will be a big announcement on this list detailing everything once
it's worked out.
Cheers Jeff.
--
Jeff Fearn <jfearn at redhat.com>
Software Engineer
Engineering Operations
Red Hat, Inc
Freedom ... courage ... Commitment ... ACCOUNTABILITY
http://file.bne.redhat.com/~jfearn/
From bugzilla at redhat.com Wed Jul 15 00:32:35 2009
From: bugzilla at redhat.com (bugzilla at redhat.com)
Date: Tue, 14 Jul 2009 20:32:35 -0400
Subject: [publican-list] [Bug 511404] New: [Feature Request]
Message-ID: <bug-511404-264938@bugzilla.redhat.com>
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
Summary: [Feature Request]
https://bugzilla.redhat.com/show_bug.cgi?id=511404
Summary: [Feature Request]
Product: Red Hat Enterprise Linux 5
Version: 5.4
Platform: All
OS/Version: Linux
Status: NEW
Severity: medium
Priority: medium
Component: publican
AssignedTo: jfearn at redhat.com
ReportedBy: ccurran at redhat.com
QAContact: ecs-dev-list at redhat.com
CC: publican-list at redhat.com
Classification: Red Hat
Target Release: ---
Description of problem:
As you may or may not know, the stepalternatives tag presently has no special
formatting. Presently it formats the same way as itemized list items format.
What I would love to see is the words "optional" or "alternative step" or
whatever Brian suggests placed in front of the text in the step. Perhaps some
light bold markup or similar.
There is a business case for this. It makes my life easier for explaining how
to use different features. Presently using admonitions or repeating the
procedure is the easiest way to write around it and get a similar effect. The
problem with this is using admonitions is distracting and may be interpreted as
no-core functionality.
Additional info:
Cider.
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
From bugzilla at redhat.com Wed Jul 15 00:53:54 2009
From: bugzilla at redhat.com (bugzilla at redhat.com)
Date: Tue, 14 Jul 2009 20:53:54 -0400
Subject: [publican-list] [Bug 511404] [Feature Request]
In-Reply-To: <bug-511404-264938@bugzilla.redhat.com>
References: <bug-511404-264938@bugzilla.redhat.com>
Message-ID: <200907150053.n6F0rsp3026294@bz-web1.app.phx.redhat.com>
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=511404
David O'Brien <daobrien at redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |daobrien at redhat.com
--- Comment #1 from David O'Brien <daobrien at redhat.com> 2009-07-14 20:53:54 EDT ---
Putting a label on this tag will only limit its usefulness. If you add
"optional" to all <stepalternative> tags then they can only be used as
optional. If you call them alternatives, then they can only be that. It will
also require revisiting and validating all those instances where the tag has
already been used. Relying on formatting is ok; adding textual labels is highly
questionable. There is also a team of people involved in working on our style
guide, not a single person.
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
From bugzilla at redhat.com Wed Jul 15 01:50:22 2009
From: bugzilla at redhat.com (bugzilla at redhat.com)
Date: Tue, 14 Jul 2009 21:50:22 -0400
Subject: [publican-list] [Bug 511404] [Feature Request]
In-Reply-To: <bug-511404-264938@bugzilla.redhat.com>
References: <bug-511404-264938@bugzilla.redhat.com>
Message-ID: <200907150150.n6F1oM0G003825@bz-web1.app.phx.redhat.com>
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=511404
Jeff Fearn <jfearn at redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
AssignedTo|jfearn at redhat.com |mhideo at redhat.com
--- Comment #2 from Jeff Fearn <jfearn at redhat.com> 2009-07-14 21:50:21 EDT ---
FYI 1: stepalternative does have:
Attribute
Name: performance
Type Enumeration:
optional
required
Default: "required"
FYI 2: Neither optional or required are contained in the translation strings in
DocBook, meaning automated translation of the labels would require upstream
modification.
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
From bugzilla at redhat.com Wed Jul 15 01:54:20 2009
From: bugzilla at redhat.com (bugzilla at redhat.com)
Date: Tue, 14 Jul 2009 21:54:20 -0400
Subject: [publican-list] [Bug 511404] [Feature Request]
In-Reply-To: <bug-511404-264938@bugzilla.redhat.com>
References: <bug-511404-264938@bugzilla.redhat.com>
Message-ID: <200907150154.n6F1sK5t026024@bz-web2.app.phx.redhat.com>
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=511404
--- Comment #3 from Christopher Curran <ccurran at redhat.com> 2009-07-14 21:54:20 EDT ---
Oh, I am aware I am not the only one working. Are you aware the tag is
presently unsupported?
*WARNING: Unvalidated tag: stepalternatives*
This tag may not be displayed correctly, may generate invalid xhtml, or may
breach Section 508 Accessibility standards.
The default is also "required", not optional.
Presently it formats with a bullet point, which in this writers view is
completely wrong. Updating the output to alphabet characters would be a partial
fix.
There is no reason why something tagged stepalternative --an alternative step--
could not have "Alternative step:" or similar appended to the front.
The textual tags require localized support, but I'm sure we can get that
with a quick ping around our translators.
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
From bugzilla at redhat.com Thu Jul 16 03:40:27 2009
From: bugzilla at redhat.com (bugzilla at redhat.com)
Date: Wed, 15 Jul 2009 23:40:27 -0400
Subject: [publican-list] [Bug 486520] Preface headings and revision history
should use sentence caps
In-Reply-To: <bug-486520-264938@bugzilla.redhat.com>
References: <bug-486520-264938@bugzilla.redhat.com>
Message-ID: <200907160340.n6G3eRe8027923@bz-web2.app.phx.redhat.com>
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=486520
--- Comment #5 from Murray McAllister <mmcallis at redhat.com> 2009-07-15 23:40:25 EDT ---
0) Identified because I used sentence case for a whole book and Preface and
Revision History did not.
1) The effect is every book will have the same heading style and be consistent.
2) No time and effort required since even people like myself can remember
sentence case rules.
3) For gain see 1).
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
From bugzilla at redhat.com Thu Jul 16 04:17:43 2009
From: bugzilla at redhat.com (bugzilla at redhat.com)
Date: Thu, 16 Jul 2009 00:17:43 -0400
Subject: [publican-list] [Bug 486520] Preface headings and revision history
should use sentence caps
In-Reply-To: <bug-486520-264938@bugzilla.redhat.com>
References: <bug-486520-264938@bugzilla.redhat.com>
Message-ID: <200907160417.n6G4Hhd0004315@bz-web2.app.phx.redhat.com>
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=486520
David O'Brien <daobrien at redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC|publican-list at redhat.com |
--- Comment #6 from David O'Brien <daobrien at redhat.com> 2009-07-16 00:17:42 EDT ---
(In reply to comment #5)
> 0) Identified because I used sentence case for a whole book and Preface and
> Revision History did not.
This would indicate that the balance of the book was at odds with our standing
styles, given that the Preface (in particular) includes sections based on
templates that use initial caps.
>
> 1) The effect is every book will have the same heading style and be consistent.
You can achieve this effect by adhering to existing styles.
>
> 2) No time and effort required since even people like myself can remember
> sentence case rules.
The time and effort is required in determining and implementing a new style and
then ensuring that *it*, rather than a previous style, is adhered to.
>
> 3) For gain see 1).
It's true that our styles are not consistently applied across all books. That
doesn't mean we need to change. It's also true that there are many styles used
throughout the world. Again, doesn't mean we need to change. Review, sure. If
we identify problems, if there is general agreement, and the benefit is obvious
and outweighs the cost then sure, let's investigate a style change. There are
far too many other aspects of our documentation that need attention besides how
we present our headings.
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
From bugzilla at redhat.com Fri Jul 17 00:16:57 2009
From: bugzilla at redhat.com (bugzilla at redhat.com)
Date: Thu, 16 Jul 2009 20:16:57 -0400
Subject: [publican-list] [Bug 486520] Preface headings and revision history
should use sentence caps
In-Reply-To: <bug-486520-264938@bugzilla.redhat.com>
References: <bug-486520-264938@bugzilla.redhat.com>
Message-ID: <200907170016.n6H0GvDu022027@bz-web1.app.phx.redhat.com>
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=486520
Jeff Fearn <jfearn at redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |publican-list at redhat.com
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
From bugzilla at redhat.com Fri Jul 17 00:24:26 2009
From: bugzilla at redhat.com (bugzilla at redhat.com)
Date: Thu, 16 Jul 2009 20:24:26 -0400
Subject: [publican-list] [Bug 486520] Preface headings and revision history
should use sentence caps
In-Reply-To: <bug-486520-264938@bugzilla.redhat.com>
References: <bug-486520-264938@bugzilla.redhat.com>
Message-ID: <200907170024.n6H0OQeG023838@bz-web1.app.phx.redhat.com>
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=486520
Jeff Fearn <jfearn at redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jfearn at redhat.com
--- Comment #7 from Jeff Fearn <jfearn at redhat.com> 2009-07-16 20:24:25 EDT ---
Check this out:
http://search.cpan.org/~dconway/Text-Autoformat-1.666.0/lib/Text/Autoformat.pm#Case_transformations
Maybe we could automate styling the title of the output based on a parameter
... maybe.
e.g:
Param: title_format
Values: NULL, upper, lower, sentence, title, highlight
Default: NULL
Where NULL is "don't be playing with my stylez fool"
This way we could set defaults or overrides in the Brands as required, and we
wouldn't have to manually go and change 250 books :D
Big question is if this works for translations, and if so, which languages do
or don't require it.
Cheers, Jeff.
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
From bugzilla at redhat.com Fri Jul 17 00:34:00 2009
From: bugzilla at redhat.com (bugzilla at redhat.com)
Date: Thu, 16 Jul 2009 20:34:00 -0400
Subject: [publican-list] [Bug 492499] Add a section on how to reach Support
/ GSS
In-Reply-To: <bug-492499-264938@bugzilla.redhat.com>
References: <bug-492499-264938@bugzilla.redhat.com>
Message-ID: <200907170034.n6H0Y0cn025769@bz-web1.app.phx.redhat.com>
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=492499
Ruediger Landmann <rlandman at redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jfearn at redhat.com,
| |publican-list at redhat.com
Component|Installation_Guide |publican
AssignedTo|rlandman at redhat.com |mhideo at redhat.com
--- Comment #3 from Ruediger Landmann <rlandman at redhat.com> 2009-07-16 20:33:59 EDT ---
This is a great idea, but the issue is broader that just the Installation
Guide. Other documentation could benefit from this as well.
We could add a "To get more help" text to our Publican templates, to be
included as a standard element in the Preface of our books.
For example, the Red Hat brand version could point to GSS, the Fedora brand
version could point to http://fedoraforum.org/, and the JBoss brand version
could point both to GSS and to http://www.jboss.org/community/index.jspa
I'm happy to work up the required text.
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
From bugzilla at redhat.com Fri Jul 17 00:41:05 2009
From: bugzilla at redhat.com (bugzilla at redhat.com)
Date: Thu, 16 Jul 2009 20:41:05 -0400
Subject: [publican-list] [Bug 486520] Preface headings and revision history
should use sentence caps
In-Reply-To: <bug-486520-264938@bugzilla.redhat.com>
References: <bug-486520-264938@bugzilla.redhat.com>
Message-ID: <200907170041.n6H0f5l0027340@bz-web1.app.phx.redhat.com>
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=486520
--- Comment #8 from Murray McAllister <mmcallis at redhat.com> 2009-07-16 20:41:05 EDT ---
re comment #7 the use of values provides gateway to multiple different heading
styles.
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
From bugzilla at redhat.com Fri Jul 17 00:52:16 2009
From: bugzilla at redhat.com (bugzilla at redhat.com)
Date: Thu, 16 Jul 2009 20:52:16 -0400
Subject: [publican-list] [Bug 492499] Add a section on how to reach Support
/ GSS
In-Reply-To: <bug-492499-264938@bugzilla.redhat.com>
References: <bug-492499-264938@bugzilla.redhat.com>
Message-ID: <200907170052.n6H0qGKG029352@bz-web1.app.phx.redhat.com>
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=492499
--- Comment #4 from Jeff Fearn <jfearn at redhat.com> 2009-07-16 20:52:15 EDT ---
You could change Feedback.xml title to be "Contact and Feedback" or similar and
add this section to that file.
This way you don't have to go back and modify all the existing books and the
next time they are rebuilt they get this section.
Cheers, Jeff.
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
From jfearn at redhat.com Mon Jul 20 01:30:38 2009
From: jfearn at redhat.com (Jeffrey Fearn)
Date: Mon, 20 Jul 2009 11:30:38 +1000
Subject: [publican-list] SVN repo locked!
Message-ID: <4A63C8BE.105@redhat.com>
Please consider the SVN repo to be locked until further notice. I will
be restructuring it for the Beta, so the layout will be changing somewhat.
No it's not really locked, but play along with me anyway :)
Cheers, Jeff.
--
Jeff Fearn <jfearn at redhat.com>
Software Engineer
Engineering Operations
Red Hat, Inc
Freedom ... courage ... Commitment ... ACCOUNTABILITY
http://file.bne.redhat.com/~jfearn/