<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body style="font-family: sans-serif; font-size: 15px;"
bgcolor="#FFFFFF" text="#000000">
<font face="sans-serif" size="3">
<div id="QCMcontainer"
style="font-family:sans-serif;font-size:15px;">Thanks for the
responses.<br>
<br>
Firstly, the option to use
<meta http-equiv="content-type" content="text/html;
charset=utf-8">
<pre class="message" style="font-family: monospace; padding-top: 8px; margin-top: 0px; border-top-width: 0px; color: rgb(0, 0, 0); font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: 19.2px; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; widows: 1; word-spacing: 0px; -webkit-text-stroke-width: 0px;">OPENSSL_ia32cap="~0x200000000000000" clamtk
instead of
<meta http-equiv="content-type" content="text/html; charset=utf-8">OPENSSL_ia32cap=0 clamtk
does work. I don't know if that helps anyone.
If the cpuinfo is still useful please let me know which specific bit is wanted
I will look at what I reported on clamtk and state that it's not a clamtk or debian fault.
And I'll look at reporting on ubuntu/xubuntu if I think it will be useful.
</pre>Regards
Tim
<div class="moz-cite-prefix">On 02/03/16 11:09, Sebastian Andrzej Siewior wrote:
</div><blockquote style="font-size: medium;" cite="mid:20160302110901.GA28291@breakpoint.cc" type="cite"><pre wrap="">On 2016-03-02 10:01:25 [+0000], Tim Passingham wrote:
</pre><blockquote type="cite"><pre wrap="">This was some time ago, and my memory is not good. Is there some problem
with the solution that works?
</pre></blockquote><pre wrap="">This is not a solution, it is a workaround. You can also close the
upstream (clamtk) bug report because it is not a clamtk bug.
</pre><blockquote type="cite"><pre wrap="">I find the debian bug reporting by email very strange - Ivery much prefer
the forum-based method. I can't see the whole bug report chain, so I have
no context, and I've no idea if we have exchanged information before or not.
</pre></blockquote><pre wrap="">The full chain is at
<a class="moz-txt-link-freetext" href="http://bugs.debian.org/793557">http://bugs.debian.org/793557</a>
</pre><blockquote type="cite"><pre wrap="">I also don't know if I should have done a Reply All or not. Sorry.
</pre></blockquote><pre wrap="">No, it is fine. Regarding xubuntu: If the latest (up-to-date) version of
openssl on your system still triggers the bug then open a bug *there* and
point them to this bug report. Kurt's message [0] is very informative on
what needs to be done.
[0] <a class="moz-txt-link-freetext" href="https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793557#132">https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793557#132</a>
</pre><blockquote type="cite"><pre wrap="">Tim
</pre></blockquote><pre wrap="">Sebastian
</pre>
</blockquote>
<pre class="moz-signature" cols="72">--
email: <a class="moz-txt-link-abbreviated" href="mailto:tim@tim-passingham.co.uk">tim@tim-passingham.co.uk</a></pre></div></font></body></html>