diff options
Diffstat (limited to 'doc/book-enea-linux-release-info/doc/known_bugs_and_limitations.xml')
-rw-r--r-- | doc/book-enea-linux-release-info/doc/known_bugs_and_limitations.xml | 453 |
1 files changed, 453 insertions, 0 deletions
diff --git a/doc/book-enea-linux-release-info/doc/known_bugs_and_limitations.xml b/doc/book-enea-linux-release-info/doc/known_bugs_and_limitations.xml new file mode 100644 index 0000000..5058404 --- /dev/null +++ b/doc/book-enea-linux-release-info/doc/known_bugs_and_limitations.xml | |||
@@ -0,0 +1,453 @@ | |||
1 | <?xml version="1.0" encoding="ISO-8859-1"?> | ||
2 | <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN" | ||
3 | "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"> | ||
4 | <chapter id="bugs-limitations"> | ||
5 | <title>Known Problems in This Release</title> | ||
6 | |||
7 | <para>The open source projects are continuously working on correcting | ||
8 | reported problems. Corrections to bugs detected by Enea have been | ||
9 | upstreamed, and the corrections been included in Enea Linux regardless of | ||
10 | when they will be included by the open source project. Remaining issues are | ||
11 | listed below, and workarounds to some of the problems are described in | ||
12 | chapter <emphasis>Troubleshooting</emphasis> in the <olink | ||
13 | targetdoc="book_enea_linux_users_guide" | ||
14 | targetptr="book_enea_linux_users_guide"><trademark | ||
15 | class="registered">Enea</trademark> Linux User's Guide</olink>.</para> | ||
16 | |||
17 | <section id="bugs-limitations-yocto"> | ||
18 | <title>Yocto</title> | ||
19 | |||
20 | <para>Open source projects often use bug databases for much more than | ||
21 | tracking bugs. The Yocto Project's Bugzilla database also functions as a | ||
22 | feature tracking program, both for the current release and for future | ||
23 | releases, and a way to track non-software issues, like documentation | ||
24 | changes.</para> | ||
25 | |||
26 | <para>The following page shows a sampling of the database: <ulink | ||
27 | url="https://www.yoctoproject.org/tools-resources/bugs">https://www.yoctoproject.org/tools-resources/bugs</ulink>.</para> | ||
28 | |||
29 | <para>For the full database, visit <ulink | ||
30 | url="https://bugzilla.yoctoproject.org">https://bugzilla.yoctoproject.org</ulink>.</para> | ||
31 | </section> | ||
32 | |||
33 | <section id="bugs-limitations-sdk"> | ||
34 | <title>Toolchain / SDK</title> | ||
35 | |||
36 | <itemizedlist spacing="compact"> | ||
37 | <listitem> | ||
38 | <para>Building the kernel might fail if GNU Make of version 3.82 has | ||
39 | been installed on the host. The mandatory recovery action is to revert | ||
40 | to version 3.81.</para> | ||
41 | </listitem> | ||
42 | |||
43 | <listitem> | ||
44 | <para>Installing a second toolchain in the same directory as a | ||
45 | previous one will break the $PATH variable of the first | ||
46 | one.<remark>LXCR-3624</remark></para> | ||
47 | </listitem> | ||
48 | </itemizedlist> | ||
49 | </section> | ||
50 | |||
51 | <section id="bugs-package-manager"> | ||
52 | <title>Smart Package Manager</title> | ||
53 | |||
54 | <para>Installation of some packages might currently fail when installing | ||
55 | using the Smart Package Manager. An example is the qemu package. Errors | ||
56 | can e.g. be reported by smart about conflicts with files from other | ||
57 | packages.</para> | ||
58 | |||
59 | <para>The recommended solution to this problem is to install the failing | ||
60 | package using rpm, already available in enea-image-base. In order to | ||
61 | install it using rpm, first install rpm using the command <command>smart | ||
62 | install rpm</command>, then download the package to the target, and | ||
63 | finally on the target use <command>rpm -i | ||
64 | <packagename>.rpm</command>. If not installed, several dependencies | ||
65 | can be reported as "Failed dependencies" with lines "x is needed by y". In | ||
66 | that case, install the required packages "x" found by dependencies by | ||
67 | using the smart package manager. Add a channel to an accessible directory | ||
68 | containing all missing rpm packages. Add packages detected to be missing, | ||
69 | until all dependencies are resolved.<remark>FIXME It would be nice to add | ||
70 | also a PowerPC example with qemu failing, the example below is for | ||
71 | ARM.</remark></para> | ||
72 | |||
73 | <section> | ||
74 | <title>Example with Failing QEMU Package</title> | ||
75 | |||
76 | <para>As an example, the qemu installation can show the following | ||
77 | error.</para> | ||
78 | |||
79 | <note> | ||
80 | <para>The example below is for ARM, including the RPM names. For | ||
81 | PowerPC similar errors can occur and other packages are needed.</para> | ||
82 | </note> | ||
83 | |||
84 | <para><emphasis role="bold">error: file /var/run from install of | ||
85 | qemu-2.1.0+git0+541bbb07eb-r0.0.aarch64 conflicts with file from package | ||
86 | base-files-3.0.14-r89.0.hierofalcon</emphasis></para> | ||
87 | |||
88 | <para>A solution to this problem is to install the above qemu package | ||
89 | using rpm, already available in enea-image-base. In order to install it | ||
90 | using rpm, first install rpm using the command <command>smart install | ||
91 | rpm</command>, then download the above package from | ||
92 | <build_dir>/tmp/deploy/rpm/aarch64. On target, use <command>rpm -i | ||
93 | qemu-2.1.0+git0+541bbb07eb-r0.0.aarch64.rpm</command>. If not installed, | ||
94 | several dependencies can be seen, e.g.:</para> | ||
95 | |||
96 | <programlisting>error: Failed dependencies: | ||
97 | libpixman-1-0 >= 0.32.6 is needed by qemu-2.1.0+git0+541bbb07eb-r0.0.aarch64 | ||
98 | libpixman-1.so.0()(64bit) is needed by qemu-2.1.0+git0+541bbb07eb-r0.0.aarch64 | ||
99 | libglib-2.0.so.0()(64bit) is needed by qemu-2.1.0+git0+541bbb07eb-r0.0.aarch64 | ||
100 | libcap2 >= 2.22 is needed by qemu-2.1.0+git0+541bbb07eb-r0.0.aarch64 | ||
101 | libglib-2.0-0 >= 2.40.0 is needed by qemu-2.1.0+git0+541bbb07eb-r0.0.aarch64 | ||
102 | bluez4 >= 4.101 is needed by qemu-2.1.0+git0+541bbb07eb-r0.0.aarch64 | ||
103 | libbluetooth.so.3()(64bit) is needed by qemu-2.1.0+git0+541bbb07eb-r0.0.aarch64 | ||
104 | libcap.so.2()(64bit) is needed by qemu-2.1.0+git0+541bbb07eb-r0.0.aarch64</programlisting> | ||
105 | |||
106 | <para>Install the required packages found by dependencies by using the | ||
107 | smart package manager, as specified in the User's Guide, by adding a | ||
108 | channel to an accessible directory containing all of the above rpm | ||
109 | packages. Suggestion for installing required packages, as in the | ||
110 | following example for qemu and ARM:</para> | ||
111 | |||
112 | <programlisting>smart install bash | ||
113 | smart install libcap | ||
114 | smart install bluez4 | ||
115 | smart install libpixman-1-0 | ||
116 | rpm -i qemu-2.1.0+git0+541bbb07eb-r0.0.aarch64.rpm</programlisting> | ||
117 | |||
118 | <para>Add packages detected to be missing until all dependencies are | ||
119 | resolved.</para> | ||
120 | </section> | ||
121 | </section> | ||
122 | |||
123 | <section id="bugs-limitations-eclipse"> | ||
124 | <title>Eclipse Tools</title> | ||
125 | |||
126 | <para>The Eclipse tools provided together with Enea Linux are part of the | ||
127 | Yocto Application Development Toolkit (ADT) and are maintained by | ||
128 | different open source projects. The list below outlines current problems | ||
129 | with the plug-ins as such, as well as kernel limitations when using a tool | ||
130 | towards the mentioned target:</para> | ||
131 | |||
132 | <itemizedlist spacing="compact"> | ||
133 | <listitem> | ||
134 | <para><emphasis role="bold">HOB</emphasis> is currently not supported | ||
135 | on Red Hat.<remark>LXCR-2994, LXCR-3222</remark></para> | ||
136 | </listitem> | ||
137 | |||
138 | <listitem> | ||
139 | <para><emphasis role="bold">SystemTap</emphasis> is currently not | ||
140 | supported on Red Hat.<remark>LXCR-3274</remark></para> | ||
141 | </listitem> | ||
142 | |||
143 | <listitem> | ||
144 | <para>When running <emphasis role="bold">SystemTap</emphasis> for the | ||
145 | first time on a target, you may need to manually ssh into the target | ||
146 | beforehand, in order to add the RSA key of the host to the file | ||
147 | known_hosts. Failing to do so will result in Eclipse freezing with the | ||
148 | progress window displayed, and a terminal message <literal>The | ||
149 | authenticity of host <target_ip> can't be | ||
150 | established</literal>.</para> | ||
151 | </listitem> | ||
152 | |||
153 | <listitem> | ||
154 | <para><emphasis role="bold">SystemTap</emphasis> scripts sometimes | ||
155 | result crosstap error messages about inaccessible variables. This is | ||
156 | not an issue with the tool itself, but stems from the compiler | ||
157 | optimizing away some of the variables. See workaround in the User's | ||
158 | Guide.<remark>LXCR-2204</remark></para> | ||
159 | </listitem> | ||
160 | |||
161 | <listitem> | ||
162 | <para>Currently <emphasis role="bold">BitBake Commander</emphasis> | ||
163 | projects can only be created for a local connection. Due to an | ||
164 | upstream bug, selecting a remote connection causes the Eclipse GUI to | ||
165 | freeze such that it must be killed.<remark>LXCR-2801</remark></para> | ||
166 | </listitem> | ||
167 | |||
168 | <listitem> | ||
169 | <para>A limitation currently makes <emphasis | ||
170 | role="bold">Eclipse</emphasis> non-responding when running a streaming | ||
171 | script, i.e. a script that runs continuously.</para> | ||
172 | </listitem> | ||
173 | |||
174 | <listitem> | ||
175 | <para>The <emphasis role="bold">LatencyTop</emphasis> plug-in for the | ||
176 | P2041 target reports some errors due to the permissions configuration | ||
177 | on the target, but it works correctly if the | ||
178 | <literal>latencytop</literal> command is issued from the Eclipse | ||
179 | console.<remark>LXCR-6303</remark></para> | ||
180 | </listitem> | ||
181 | |||
182 | <listitem> | ||
183 | <para>Currently <emphasis role="bold">LatencyTOP</emphasis> is not | ||
184 | available for ARM kernels built with SMP support due to an ARM | ||
185 | specific limitation in the Linux kernel.</para> | ||
186 | </listitem> | ||
187 | |||
188 | <listitem> | ||
189 | <para><emphasis role="bold">PowerTOP</emphasis> sometimes freezes | ||
190 | Eclipse after displaying a progress bar with message | ||
191 | <literal>Gathering powertop data file | ||
192 | remotely</literal>.<remark>LXCR-3143</remark></para> | ||
193 | </listitem> | ||
194 | |||
195 | <listitem> | ||
196 | <para>When running <emphasis role="bold">powertop</emphasis> from the | ||
197 | Eclipse terminal towards p2020rdb targets it is necessary to specify | ||
198 | the full path in order to find the | ||
199 | command.<remark>LXCR-2265</remark></para> | ||
200 | </listitem> | ||
201 | |||
202 | <listitem> | ||
203 | <para>When running <emphasis role="bold">powertop</emphasis> from the | ||
204 | Eclipse terminal towards zynq ZC702 targets it is necessary to specify | ||
205 | the full path in order to find the | ||
206 | command.<remark>LXCR-2265</remark></para> | ||
207 | </listitem> | ||
208 | |||
209 | <listitem> | ||
210 | <para>The <emphasis role="bold">PowerTOP</emphasis> console in Eclipse | ||
211 | might display messages like <literal>Cannot load | ||
212 | /var/cache/powertop/<filename></literal>. As a workaround, run | ||
213 | <emphasis role="bold">powertop --calibrate</emphasis> for a while to | ||
214 | generate the missing files. See <ulink | ||
215 | url="https://bugzilla.redhat.com/show_bug.cgi?id=698020">Bugzilla | ||
216 | #698020</ulink>.<remark>LXCR-3575</remark></para> | ||
217 | </listitem> | ||
218 | |||
219 | <listitem> | ||
220 | <para><emphasis role="bold">ssh-only</emphasis> is currently the only | ||
221 | supported connection type when running Eclipse tools towards a | ||
222 | target.<remark>LXCR-2799</remark></para> | ||
223 | </listitem> | ||
224 | |||
225 | <listitem> | ||
226 | <para>Hyphen character '-' in the name of the <emphasis | ||
227 | role="bold">Yocto ADT AutoTools project</emphasis> can cause | ||
228 | configuration errors.<remark>LXCR-2290</remark></para> | ||
229 | </listitem> | ||
230 | |||
231 | <listitem> | ||
232 | <para>The <emphasis role="bold">LTTng</emphasis> tool does not work on | ||
233 | <emphasis role="bold">ARM</emphasis> targets, neither from within | ||
234 | Eclipse nor when run directly on target, due to a problem with | ||
235 | lttng-modules and gcc-4.8.x. See <ulink | ||
236 | url="https://bugzilla.yoctoproject.org/show_bug.cgi?id=6015">Bugzilla | ||
237 | #6015</ulink>.<remark>LXCR-2653, LXCR-3053</remark></para> | ||
238 | </listitem> | ||
239 | |||
240 | <listitem> | ||
241 | <para>When running <emphasis role="bold">LTTng</emphasis> from | ||
242 | Eclipse, it sometimes happens that a new session created in the | ||
243 | Control View does not immediately appear under Sessions for that | ||
244 | target. However, the session is created and will appear after | ||
245 | right-clicking "Sessions" and selecting "Refresh".</para> | ||
246 | </listitem> | ||
247 | |||
248 | <listitem> | ||
249 | <para>The<emphasis role="bold"> yocto-bsp</emphasis> properties page | ||
250 | has some problems in the graphical user interface. Occasionally it is | ||
251 | not possible to resize and scroll which makes it impossible to see the | ||
252 | lower part of the properties window.<remark>LXCR-3128</remark></para> | ||
253 | </listitem> | ||
254 | |||
255 | <listitem> | ||
256 | <para>When connecting an Eclipse project configured for <emphasis | ||
257 | role="bold">KGDB</emphasis> (GDB Hardware Debugging) to a 64-bit | ||
258 | PowerPC target, GDB fails to connect unless the architecture is | ||
259 | specified in <filename>.gdbinit</filename>. See <ulink | ||
260 | url="https://bugs.eclipse.org/bugs/show_bug.cgi?id=457697">Bugzilla | ||
261 | #457697</ulink>.<remark>LXCR-3984</remark></para> | ||
262 | </listitem> | ||
263 | </itemizedlist> | ||
264 | </section> | ||
265 | |||
266 | <section id="bugs-limitations-target-side-tools"> | ||
267 | <title>Target-Side Tools</title> | ||
268 | |||
269 | <para>The target-side tools can be run stand-alone on target or from | ||
270 | Eclipse on host. The issues below are only observed when running the tools | ||
271 | directly on target:</para> | ||
272 | |||
273 | <itemizedlist spacing="compact"> | ||
274 | <listitem> | ||
275 | <para>The <emphasis role="bold">perf report</emphasis> command hangs | ||
276 | or crashes due to segmentation fault on ARM | ||
277 | targets.<remark>LXCR-2708</remark></para> | ||
278 | </listitem> | ||
279 | |||
280 | <listitem> | ||
281 | <para>The <emphasis role="bold">perf report</emphasis> does not show | ||
282 | any output for the PandaBoard target.<remark>LXCR-2710</remark></para> | ||
283 | </listitem> | ||
284 | |||
285 | <listitem> | ||
286 | <para><emphasis role="bold">perf top</emphasis> displays for a few | ||
287 | seconds the error message <literal>Failed to open | ||
288 | /tmp/perf-388.map</literal>. Any attempt to exit the subsequent window | ||
289 | causes the system to hang.<remark>LXCR-3113</remark></para> | ||
290 | </listitem> | ||
291 | |||
292 | <listitem> | ||
293 | <para>When running the <command>perf top</command> command on the i.MX | ||
294 | 6Quad SABRE Lite target, the console text may become red after running | ||
295 | for some time (~ 1 minute).<remark>LXCR-3631</remark></para> | ||
296 | </listitem> | ||
297 | |||
298 | <listitem> | ||
299 | <para>The <emphasis role="bold">LTTng</emphasis> tool does not work on | ||
300 | <emphasis role="bold">ARM</emphasis> targets, neither from within | ||
301 | Eclipse nor when run directly on target, due to a problem with | ||
302 | lttng-modules and gcc-4.8.x. See <ulink | ||
303 | url="https://bugzilla.yoctoproject.org/show_bug.cgi?id=6015">Bugzilla | ||
304 | #6015</ulink>.<remark>LXCR-2653, LXCR-3053</remark></para> | ||
305 | </listitem> | ||
306 | |||
307 | <listitem> | ||
308 | <para>The <emphasis role="bold">powertop --calibrate</emphasis> | ||
309 | command does not work on the Keystone k2hk-evm | ||
310 | target.<remark>LXCR-2660</remark></para> | ||
311 | </listitem> | ||
312 | |||
313 | <listitem> | ||
314 | <para>The <emphasis role="bold">powertop</emphasis> command run with | ||
315 | <emphasis role="bold">--calibrate</emphasis> or -<emphasis | ||
316 | role="bold">-time</emphasis> arguments may show some warnings on | ||
317 | PowerPC targets.</para> | ||
318 | </listitem> | ||
319 | |||
320 | <listitem> | ||
321 | <para>When running <emphasis role="bold">powertop</emphasis> on | ||
322 | <emphasis role="bold">ARM</emphasis> targets, the following | ||
323 | warning/error is repeated: <literal>clk_set_rate: failed to set | ||
324 | i2c0_aper rate</literal> . Then powertop stops and the statistics are | ||
325 | no longer updated. What probably happens here is that the cpufreq | ||
326 | governor tries to scale the CPU frequency, but since the I2C clock is | ||
327 | derived from the CPU frequency, the I2C driver implements some policy | ||
328 | to stay within legal frequency limits and rejects the frequency | ||
329 | changes, ending up with the warning message. A <ulink | ||
330 | url="https://github.com/Xilinx/linux-xlnx/commit/0fdd34575efae5c8eced09b6b0a1b723bff4d225">fix</ulink> | ||
331 | has been merged in the linux-xlnx kernel but is not yet propagated | ||
332 | into meta-xilinx.<remark>LXCR-3205, LXCR-3106, | ||
333 | LXCR-2660</remark></para> | ||
334 | </listitem> | ||
335 | |||
336 | <listitem> | ||
337 | <para>If you get an error message like <literal>Cannot load from file | ||
338 | /var/cache/powertop/saved_results.powertop</literal> when running | ||
339 | <emphasis role="bold">powertop</emphasis>, there is most likely not | ||
340 | enough measurement data collected yet. All you have to do is to keep | ||
341 | powertop running for a certain time.<remark>LXCR-2176, LXCR-2660, | ||
342 | LXCR-3106</remark></para> | ||
343 | </listitem> | ||
344 | |||
345 | <listitem> | ||
346 | <para>The message <literal>Model-specific registers (MSR) not found | ||
347 | (try enabling CONFIG_X86_MSR)</literal> appears when you run <emphasis | ||
348 | role="bold">powertop</emphasis> on <emphasis | ||
349 | role="bold">non-x86</emphasis> targets. powertop is mainly an x86n | ||
350 | tool, so it expects X*^_MSR config to be enabled in the kernel. For | ||
351 | non-x86 targets this config is not available in the kernel, hence, | ||
352 | powertop warns about it, but the message can be ignored on those | ||
353 | targets.<remark> LXCR-2176, LXCR-2660, LXCR-3106</remark></para> | ||
354 | </listitem> | ||
355 | |||
356 | <listitem> | ||
357 | <para><emphasis role="bold">powertop</emphasis> issues a message | ||
358 | <literal>sh: /usr/bin/xset: No such file or directory</literal> when | ||
359 | it tries to use xset to configure X display preferences but cannot | ||
360 | find the binary since the image by default contains no X system. The | ||
361 | message can simply be ignored.<remark>LXCR-2176</remark></para> | ||
362 | </listitem> | ||
363 | </itemizedlist> | ||
364 | </section> | ||
365 | |||
366 | <section id="bugs-limitations-virtualization"> | ||
367 | <title>Virtualization</title> | ||
368 | |||
369 | <itemizedlist spacing="compact"> | ||
370 | <listitem> | ||
371 | <para><emphasis role="bold">virtualization</emphasis>: CONFIG_BRIDGE | ||
372 | is not included in the default p2020rdb | ||
373 | kernel.<remark>LXVTCR-273</remark></para> | ||
374 | </listitem> | ||
375 | |||
376 | <listitem> | ||
377 | <para><emphasis role="bold">lxc</emphasis>:</para> | ||
378 | |||
379 | <itemizedlist spacing="compact"> | ||
380 | <listitem> | ||
381 | <para>User namespace is not available on PowerPC targets as it is | ||
382 | an experimental feature in the 3.8 kernel.</para> | ||
383 | </listitem> | ||
384 | |||
385 | <listitem> | ||
386 | <para>If multiple Linux containers are started from the same | ||
387 | process and share resources, destroying the containers might | ||
388 | result in a race condition with error message "Error in | ||
389 | `./lxc-test-concurrent': double free or corruption (fasttop)" | ||
390 | followed by an application | ||
391 | crash."<remark>LXVTCR-365</remark></para> | ||
392 | </listitem> | ||
393 | </itemizedlist> | ||
394 | </listitem> | ||
395 | |||
396 | <listitem> | ||
397 | <para><emphasis role="bold">libvirt</emphasis>: Default network does | ||
398 | not start.<remark>LXVTCR-240</remark></para> | ||
399 | </listitem> | ||
400 | </itemizedlist> | ||
401 | </section> | ||
402 | |||
403 | <section id="bugs-limitations-doc"> | ||
404 | <title>Documentation</title> | ||
405 | |||
406 | <itemizedlist spacing="compact"> | ||
407 | <listitem> | ||
408 | <para><emphasis role="bold">PDF navigation</emphasis>: When using | ||
409 | links to open other PDFs, or jump to another place in the same PDF, | ||
410 | jumping back sometimes fails. This has been observed when opening a | ||
411 | PDF in Adobe Reader, inside a browser with PDF add-on, as well as when | ||
412 | the browser is configured to open PDF files in an external PDF reader. | ||
413 | As a workaround, open the HTML version of the | ||
414 | document.<remark>LXCR-3283</remark></para> | ||
415 | </listitem> | ||
416 | |||
417 | <listitem> | ||
418 | <para><emphasis role="bold">Internet Explorer (IE) cannot display some | ||
419 | web pages</emphasis>: It is recommended to use Firefox or another | ||
420 | non-IE browser for opening external links. If you prefer reading the | ||
421 | documentation in PDF format in Adobe Reader (not in an Adobe plug-in | ||
422 | in a browser), remember to configure a non-IE browser as default | ||
423 | browser to be able to follow all links from within Adobe Reader. | ||
424 | Example of a link that does not work in IE: <ulink | ||
425 | url="https://rt.wiki.kernel.org/">https://rt.wiki.kernel.org/</ulink>. | ||
426 | <remark>LXCR-3281</remark></para> | ||
427 | </listitem> | ||
428 | </itemizedlist> | ||
429 | </section> | ||
430 | |||
431 | <section id="bugs-limitations-other"> | ||
432 | <title>Miscellaneous</title> | ||
433 | |||
434 | <itemizedlist spacing="compact"> | ||
435 | <listitem> | ||
436 | <para>Running <emphasis role="bold">QEMU from an exported | ||
437 | rootfs</emphasis> requires sudo privileges on the host.</para> | ||
438 | </listitem> | ||
439 | |||
440 | <listitem> | ||
441 | <para><emphasis role="bold">menuconfig</emphasis> requires <emphasis | ||
442 | role="bold">Ncurses</emphasis>. If the terminal that pops up | ||
443 | immediately closes instead of showing the menuconfig interface, check | ||
444 | that the Ncurses development library is installed.</para> | ||
445 | </listitem> | ||
446 | </itemizedlist> | ||
447 | </section> | ||
448 | |||
449 | <!-- The file with a section below is autocreated by make init --> | ||
450 | |||
451 | <xi:include href="jiraissues_generated.xml" | ||
452 | xmlns:xi="http://www.w3.org/2001/XInclude" /> | ||
453 | </chapter> \ No newline at end of file | ||