<div dir="ltr"><div>Anne,<br><br>I think useage of xml:id tag will not work across repositories, hence the issues I was facing. To be very clear, training-manuals builds were failing straight away. It was a bit hectic to get it back on track.<br>
<br></div>We need to use xi:include for including common folder's content and xpointer for the xml:id. So you see the problems faced. This patch will give you some idea of what exactly happened.<br><a href="https://review.openstack.org/#/c/108263/3/doc/training-guides/associate-guide/bk001-ch007-associate-network-node.xml">https://review.openstack.org/#/c/108263/3/doc/training-guides/associate-guide/bk001-ch007-associate-network-node.xml</a><br>
Ignore the xi:fallback part, I could not fix the changes myselves because someone else had taken up the bug. But it was eventually fixed.<br><a href="http://git.openstack.org/cgit/openstack/training-guides/commit/?id=67f88dd957e78f850bfb4e04281f56ff2a432188">http://git.openstack.org/cgit/openstack/training-guides/commit/?id=67f88dd957e78f850bfb4e04281f56ff2a432188</a><br>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Jul 21, 2014 at 6:50 PM, Anne Gentle <span dir="ltr"><<a href="mailto:anne@openstack.org" target="_blank">anne@openstack.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi Pranav,<div>I don't know if the file names are changing, do you have evidence of a file name change so I can troubleshoot further? </div>
<div><br></div><div>My working theory is that the conditionals are causing the error you pasted. The file is "not found" because it has a particular condition. As an example, any image starting with <span style="color:rgb(85,85,85);font-family:'Bitstream Vera Sans Mono',monospace;font-size:13px">dbconfig- </span></div>
<div>is not accessible to the build unless the condition os="debian" is met.</div><div><br></div><div>We typically use xml:id so that file name changes do not matter, but it does require everyone to refer to items only by xml:id. In the case of images, the reference to the image would need an xml:id on it, that the training guide would then reference. </div>
<div><br></div><div>This difficulty happens often when sharing content, I've seen it many times. We can work through it with the toolchain we have, I believe.</div><div>Anne</div></div><div class="gmail_extra"><br><br>
<div class="gmail_quote"><div><div class="h5">On Sun, Jul 20, 2014 at 9:42 PM, Pranav Salunke <span dir="ltr"><<a href="mailto:dguitarbite@gmail.com" target="_blank">dguitarbite@gmail.com</a>></span> wrote:<br></div>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5">
<div dir="ltr"><div><div>Hello,<br><br></div><div>I have seen a few changes in the common folder present under openstack-manuals repository break training manuals. Particularly the changes which include file name change. We need to address this so that the training manuals and other repositories which use common folder can adopt to the changes. These changes should be merged only when the dependences under other documentation related projects are addressed.<br>
<br><br>The other issue with common folder arises with relative paths which gives following errors.<br><a href="http://paste.openstack.org/show/86763/" target="_blank">http://paste.openstack.org/show/86763/</a><br></div>
<div>We need to address these errors properly to encourage re-use of existing material. Can we discuss these issues during the IRC meeting or during the design session at Juno Summit?<br>
</div>Regards,<br></div>Pranav<br></div>
<br></div></div>_______________________________________________<br>
Openstack-docs mailing list<br>
<a href="mailto:Openstack-docs@lists.openstack.org" target="_blank">Openstack-docs@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs</a><br>
<br></blockquote></div><br></div>
</blockquote></div><br></div>