<html>
<head>
<base href="http://fiji.sc/bugzilla/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW --- - Update for ImageJ-win-64.exe fails."
href="http://fiji.sc/bugzilla/show_bug.cgi?id=585#c3">Comment # 3</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW --- - Update for ImageJ-win-64.exe fails."
href="http://fiji.sc/bugzilla/show_bug.cgi?id=585">bug 585</a>
from <span class="vcard"><a class="email" href="mailto:johannes.schindelin@gmx.de" title="Johannes Schindelin <johannes.schindelin@gmx.de>"> <span class="fn">Johannes Schindelin</span></a>
</span></b>
<pre>Hi Carol,
it is good that you specified exactly the steps you performed because that was
not clear from the original bug report. Based on the original account, I had
chased around for 30 minutes before I gave up and admitted to myself that I
failed at reproducing your issue.
Unfortunately, even after the additional report, I am unable to reproduce. This
time, I just followed the following steps:
- downloaded a .zip from
<a href="http://jenkins.imagej.net/job/Stable-Fiji/lastSuccessfulBuild/artifact/fiji-win64.zip">http://jenkins.imagej.net/job/Stable-Fiji/lastSuccessfulBuild/artifact/fiji-win64.zip</a>
- unpacked it onto the Desktop
- ran ImageJ-win64.exe from there
- it wanted to update ij-core, which I let it do.
- restarted as suggested
- called up the updater again
- it said "up-to-date!"
As I spent already some time on this issue today, I might have to shift
additional endeavors to fix your problem to another day, based on your
feedback.
For the record: it would be good if you sent your response by logging in to
<a class="bz_bug_link
bz_status_NEW "
title="NEW --- - Update for ImageJ-win-64.exe fails."
href="show_bug.cgi?id=585">http://fiji.sc/bugzilla/show_bug.cgi?id=585</a>. Our BugZilla is not set up to
understand response mails.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>