<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hi Rakesh,<br>
<br>
Good thing you asked!<br>
<br>
OK, so the bug tracker had the commit "number":
967348651061f039b3dbc7a71d70687d928977dd<br>
So I went to the repository for ParaView on Github:
<a class="moz-txt-link-freetext" href="https://github.com/Kitware/ParaView/">https://github.com/Kitware/ParaView/</a><br>
Clicked on one of the "commits" tab and replace "master" with the
commit number: <a class="moz-txt-link-freetext" href="https://github.com/Kitware/ParaView/commits/master">https://github.com/Kitware/ParaView/commits/master</a>
->
<a class="moz-txt-link-freetext" href="https://github.com/Kitware/ParaView/commits/967348651061f039b3dbc7a71d70687d928977dd">https://github.com/Kitware/ParaView/commits/967348651061f039b3dbc7a71d70687d928977dd</a><br>
So, since the problem was with IceT, I went to where it is in
ParaView:
<a class="moz-txt-link-freetext" href="https://github.com/Kitware/ParaView/tree/967348651061f039b3dbc7a71d70687d928977dd/Utilities">https://github.com/Kitware/ParaView/tree/967348651061f039b3dbc7a71d70687d928977dd/Utilities</a><br>
OK, the respective folder only says "IceT - 916f22d", namely the
commit number from where it comes. Went to the root folder of
ParaView and looked at ".gitmodules":
<a class="moz-txt-link-freetext" href="https://github.com/Kitware/ParaView/blob/967348651061f039b3dbc7a71d70687d928977dd/.gitmodules">https://github.com/Kitware/ParaView/blob/967348651061f039b3dbc7a71d70687d928977dd/.gitmodules</a><br>
<br>
OK, IceT repo is here: git://paraview.org/IceT.git - so I jumped
online to here: paraview.org/IceT.git -- automatic redirect by the
website --> <a class="moz-txt-link-freetext" href="http://paraview.org/gitweb?p=IceT.git">http://paraview.org/gitweb?p=IceT.git</a><br>
Clicked on one of the links that say "commit" and replace the number
by "916f22d": paraview.org/gitweb?p=IceT.git;a=commit;h=916f22d<br>
Mmm, it's a merge. OK, then clicked on the "shortlog" link and this
<i>jumped out</i> of the list:
<a class="moz-txt-link-freetext" href="http://paraview.org/gitweb?p=IceT.git;a=commit;h=36fad20880740ecacedf9cf80f92a3255c19055b">http://paraview.org/gitweb?p=IceT.git;a=commit;h=36fad20880740ecacedf9cf80f92a3255c19055b</a><br>
Clicked on the "diff" link and there we have it!<br>
<br>
Wait, I found another commit different from the one I indicated
before. Apparently I didn't backtrack it properly.... Oh, both are
from the same day! So both are needed! See the shortlog:
<a class="moz-txt-link-freetext" href="http://paraview.org/gitweb?p=IceT.git;a=shortlog;h=e2231f1454c90d7d4fd16540d9468ffbdaaec3f7">http://paraview.org/gitweb?p=IceT.git;a=shortlog;h=e2231f1454c90d7d4fd16540d9468ffbdaaec3f7</a><br>
<br>
Best regards,<br>
Bruno<br>
<br>
On 07-01-2012 21:31, Rakesh Hammond wrote:
<blockquote
cite="mid:CAFYzz269avESfrTovTXuM_z_-kOu0PFtrVwRQQaa86ip0Y91Ow@mail.gmail.com"
type="cite">Bruno,<br>
<br>
Thanks - I think this is what I am after, I will have a play with
this diff.<br>
<br>
For future reference, can you please tell me how did you find it?
<br>
<br>
I think it would be nice to have a link from the mantis ticket to
source code change !<br>
<br>
Regards,<br>
Rakesh<br>
<div class="gmail_quote">On 7 January 2012 19:59, Bruno Santos <span
dir="ltr"><<a moz-do-not-send="true"
href="mailto:bruno.santos@bluecape.com.pt">bruno.santos@bluecape.com.pt</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0pt 0pt 0pt
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
Hi Rakesh,<br>
<br>
If I backtracked it correctly, this should be the fix you are
looking for:<br>
<a moz-do-not-send="true"
href="http://paraview.org/gitweb?p=IceT.git;a=commitdiff;h=e2231f1454c90d7d4fd16540d9468ffbdaaec3f7"
target="_blank">http://paraview.org/gitweb?p=IceT.git;a=commitdiff;h=e2231f1454c90d7d4fd16540d9468ffbdaaec3f7</a><br>
<br>
Best regards,<br>
Bruno<br>
<br>
Date: Sat, 7 Jan 2012 12:07:24 +0000<br>
From: Rakesh Hammond <<a moz-do-not-send="true"
href="mailto:rakesh.hammond@googlemail.com">rakesh.hammond@googlemail.com</a>><br>
Subject: [Paraview] Icet test build fails with Paraview-3.12.0<br>
<div>
<div class="h5"><br>
Hi,<br>
<br>
I am trying to build the ParaView-3.12.0 (stable release
on 08th of<br>
November 2011) with an mpich library on Linux with
gcc-4.5.2.<br>
<br>
The IceT tests unfortunately fails. Having looked around
the bug tracker,<br>
I found this ticket<br>
<br>
<a moz-do-not-send="true"
href="http://www.vtk.org/Bug/view.php?id=12716"
target="_blank">http://www.vtk.org/Bug/view.php?id=12716</a><br>
<br>
The problem I am having is same as what is described here,
unfortunately<br>
the fix was merged into the current development directory
on the 11th of<br>
November 2011.<br>
<br>
Is it possible to find out exactly what the fix was ? (for
example doing a<br>
commitdif?). I am not familiar with git that much, but
looking around I was<br>
unable to get the code difference. If any one knows how
to get the<br>
changes, please send me the url link.<br>
<br>
Is there are any plans to release a patch for 3.12.0 any
time soon? At<br>
work, we are not allowed to build from nightly builds, so
I am a little bit<br>
stuck on how to progress further. My options are either
to wait for a<br>
patch or make the necessary modifications for the stable
3.12.0 and build.<br>
<br>
Thanks,<br>
Rakesh<br>
<br>
</div>
</div>
_______________________________________________<br>
Powered by <a moz-do-not-send="true"
href="http://www.kitware.com" target="_blank">www.kitware.com</a><br>
<br>
Visit other Kitware open-source projects at <a
moz-do-not-send="true"
href="http://www.kitware.com/opensource/opensource.html"
target="_blank">http://www.kitware.com/opensource/opensource.html</a><br>
<br>
Please keep messages on-topic and check the ParaView Wiki at:
<a moz-do-not-send="true"
href="http://paraview.org/Wiki/ParaView" target="_blank">http://paraview.org/Wiki/ParaView</a><br>
<br>
Follow this link to subscribe/unsubscribe:<br>
<a moz-do-not-send="true"
href="http://www.paraview.org/mailman/listinfo/paraview"
target="_blank">http://www.paraview.org/mailman/listinfo/paraview</a><br>
</blockquote>
</div>
<br>
<p class="" avgcert""="" color="#000000" align="left">Não foram
detectados vírus nesta mensagem.<br>
Verificado por AVG - <a moz-do-not-send="true"
href="http://www.avg.com">www.avg.com</a><br>
Versão: 2012.0.1901 / Base de dados de Vírus: 2109/4731 - Data
de Lançamento: 01/08/12</p>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="72">--
<a class="moz-txt-link-freetext" href="http://www.bluecape.com.pt">http://www.bluecape.com.pt</a>
blueCAPE Lda - CAE solutions
Rua Fonte dos Corvos, n.29
Casais da Serra
2665-305 Milharado
PORTUGAL
(+351) 219 755 345 Tel.
(+351) 219 755 345 Fax
(+351) 963 440 984 Mob.
</pre>
</body>
</html>