From eburuschkin at sicom.com Thu May 18 20:49:48 2017 From: eburuschkin at sicom.com (Eric Buruschkin) Date: Thu, 18 May 2017 16:49:48 -0400 Subject: [publican-list] Is it possible to build documentation without the requirement of Message-ID: We use publican to build pdf documentation, and have only used older versions of publican for a while now (2.8.x). I am now migrating the repository of xml to a new server home and am now using a much newer version - 4.3.2. We never used productnumber in any way previously, and am now seemingly forced to add one. While this is great for packaging and documenting different versions of software/products, this is preventing me from publishing new documents. I've tried different combinations of editing Book_Info.xml and publican.cfg to leave version/productnumber empty, but to no avail. Is there a way to bypass this requirement? A patch I can apply? -- *Confidentiality Notice: *This electronic mail message is intended exclusively for the individual or entity to which it is addressed. The information contained in this communication is the property of SICOM Systems, Inc. and contains confidential and privileged proprietary information intended only for the personal and confidential use of the individual or entity to which it is addressed. If you are not the addressee indicated in this message (or an agent responsible for delivery of the message to such person), you are hereby notified that you have received this communication in error and that any review, dissemination, copying or unauthorized use of this message is strictly prohibited. In such case, you should destroy this message and kindly notify the sender by reply e-mail. -------------- next part -------------- An HTML attachment was scrubbed... URL: From jfearn at redhat.com Thu May 18 22:06:51 2017 From: jfearn at redhat.com (Jeff Fearn) Date: Thu, 18 May 2017 22:06:51 +0000 Subject: [publican-list] Is it possible to build documentation without the requirement of In-Reply-To: References: Message-ID: <15e49f2d-6edd-dc7d-b3b3-c967d974f0f4@redhat.com> On 18/05/17 20:49, Eric Buruschkin wrote: > We use publican to build pdf documentation, and have only used older > versions of publican for a while now (2.8.x). I am now migrating the > repository of xml to a new server home and am now using a much newer > version - 4.3.2. > > We never used productnumber in any way previously, and am now seemingly > forced to add one. While this is great for packaging and documenting > different versions of software/products, this is preventing me from > publishing new documents. > > I've tried different combinations of editing Book_Info.xml and publican.cfg > to leave version/productnumber empty, but to no avail. > > Is there a way to bypass this requirement? A patch I can apply? Delete from book/article Info file, and add 'version: 11' to publican.cfg Cheers, Jeff.