<div dir="ltr">Hi,<div><br></div><div>I've checked the new version and it seems that the patch is already there ;)</div><div>No problem with web client ;)<br clear="all"><div dir="ltr"><span style="font-family:arial, sans-serif;font-size:13px;border-collapse:collapse;color:rgb(80, 0, 80)"><div>
<br></div><div>Cheers,</div><div>Leon Kolchinsky</div></span></div><br>
<br><br><div class="gmail_quote">On Fri, Oct 21, 2011 at 23:27, Josh Moore <span dir="ltr"><<a href="mailto:josh@glencoesoftware.com">josh@glencoesoftware.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
On Oct 17, 2011, at 2:57 AM, Leon Kolchinsky wrote:<br>
<br>
> Hello Josh,<br>
<br>
Hi Leon,<br>
<div><div></div><div class="h5"><br>
> Here is the output from 2 Omero servers -<br>
><br>
> Server1:<br>
> [omero@vera143 pil]$ make<br>
> python t1.py<br>
> Found PIL.Image: <module 'PIL.Image' from<br>
> '/usr/lib64/python2.6/site-packages/PIL/Image.pyc'><br>
> python t2.py<br>
> Found Image:<module 'Image' from<br>
> '/usr/lib64/python2.6/site-packages/PIL/Image.pyc'><br>
> python t3.py<br>
> Found PIL.Image: <module 'PIL.Image' from<br>
> '/usr/lib64/python2.6/site-packages/PIL/Image.pyc'><br>
> Reimported Image: <module 'Image' from<br>
> '/usr/lib64/python2.6/site-packages/PIL/Image.pyc'><br>
><br>
> Server2:<br>
> [omero@vera145 pil]$ make<br>
> python t1.py<br>
> Found PIL.Image: <module 'PIL.Image' from<br>
> '/usr/lib64/python2.6/site-packages/PIL/Image.pyc'><br>
> python t2.py<br>
> Found Image:<module 'Image' from<br>
> '/usr/lib64/python2.6/site-packages/PIL/Image.pyc'><br>
> python t3.py<br>
> Found PIL.Image: <module 'PIL.Image' from<br>
> '/usr/lib64/python2.6/site-packages/PIL/Image.pyc'><br>
> Reimported Image: <module 'Image' from<br>
> '/usr/lib64/python2.6/site-packages/PIL/Image.pyc'><br>
><br>
> Seems OK, right?<br>
> I guess I'll check it again with the new version of Omero (when it's<br>
> released).<br>
<br>
</div></div>It does look correct, i.e. no other mismatched libraries, etc. Let us know how the web client functions without the patch.<br>
<br>
Cheers,<br>
<font color="#888888">~Josh.<br>
</font><div><div></div><div class="h5"><br>
<br>
> Thanks,<br>
> Leon Kolchinsky<br>
><br>
><br>
><br>
> On Wed, Oct 12, 2011 at 20:04, Josh Moore <<a href="mailto:josh@glencoesoftware.com">josh@glencoesoftware.com</a>> wrote:<br>
><br>
>><br>
>> On Oct 12, 2011, at 1:50 AM, Leon Kolchinsky wrote:<br>
>><br>
>>> Hi,<br>
>>><br>
>>><br>
>>> On Tue, Oct 11, 2011 at 20:00, Josh Moore <<a href="mailto:josh@glencoesoftware.com">josh@glencoesoftware.com</a>><br>
>> wrote:<br>
>>><br>
>>>><br>
>>>> On Oct 11, 2011, at 6:43 AM, Leon Kolchinsky wrote:<br>
>>>><br>
>>>>> Hello,<br>
>>>>><br>
>>>>> 1. How do I run auto "cleanse" job via cron (so it won't ask me for<br>
>>>> username<br>
>>>>> and password)?<br>
>>>>><br>
>>>>> "$ /srv/omeroserver/bin/omero -s localhost admin cleanse<br>
>> /srv/omerodata"<br>
>>>> -<br>
>>>>> asks for username/pass<br>
>>>>> "$ /srv/omeroserver/bin/omero -s root@localhost admin cleanse<br>
>>>>> /srv/omerodata" - asks for pass<br>
>>>><br>
>>>> There's currently no way to login passwordlessly, but I've added<br>
>>>> <a href="https://trac.openmicroscopy.org.uk/ome/ticket/6957" target="_blank">https://trac.openmicroscopy.org.uk/ome/ticket/6957</a> in order to examine<br>
>>>> adding support for that. Until then, you'll need to follow the recipes<br>
>> on<br>
>>>> the backup-and-restore page:<br>
>>>><br>
>>>><br>
>>>><br>
>> <a href="https://www.openmicroscopy.org/site/support/omero4/server/backup-and-restore" target="_blank">https://www.openmicroscopy.org/site/support/omero4/server/backup-and-restore</a><br>
>>><br>
>>><br>
>>> Thanks, I'll try that.<br>
>>><br>
>>>><br>
>>>><br>
>>>>> 2. Is it possible to include this patch into Omero releases (from Chris<br>
>>>>> Allan):<br>
>>>>><br>
>>>><br>
>> <a href="http://users.openmicroscopy.org.uk/~cxallan/pil_image_import_inline.patch" target="_blank">http://users.openmicroscopy.org.uk/~cxallan/pil_image_import_inline.patch</a><br>
>>>>><br>
>>>>> It solves some client issues for us (python 2.6).<br>
>>>>><br>
>>>>> This is how I patch OMERO web client:<br>
>>>>> [root@vera144 log]# cd /srv/OMERO.server-Beta-4.3.2/lib/python/<br>
>>>>> [root@vera144 python]# wget<br>
>>>>><br>
>>>><br>
>> <a href="http://users.openmicroscopy.org.uk/~cxallan/pil_image_import_inline.patch" target="_blank">http://users.openmicroscopy.org.uk/~cxallan/pil_image_import_inline.patch</a><br>
>>>>> [root@vera144 python]# cp omeroweb/webclient/webclient_gateway.py<br>
>>>>> omeroweb/webclient/webclient_gateway.py.orig<br>
>>>>> [root@vera144 python]# patch -p0 < pil_image_import_inline.patch<br>
>>>>> patching file omeroweb/webclient/webclient_gateway.py<br>
>>>>> [root@vera144 python]# chown omero.omero<br>
>>>>> omeroweb/webclient/webclient_gateway.pyl<br>
>>>><br>
>>>> Unfortunately, it's still unclear why this patch is only necessary for<br>
>> your<br>
>>>> installation, and therefore, it's likely that adding this would break<br>
>> other<br>
>>>> installations. The import block at the top of that file:<br>
>>>><br>
>>>> try:<br>
>>>> from PIL import Image, ImageDraw # see ticket:2597<br>
>>>> except ImportError:<br>
>>>> try:<br>
>>>> import Image, ImageDraw # see ticket:2597<br>
>>>> except:<br>
>>>> logger.error("You need to install the Python Imaging Library. Get<br>
>> it<br>
>>>> at <a href="http://www.pythonware.com/products/pil/" target="_blank">http://www.pythonware.com/products/pil/</a>")<br>
>>>> logger.error(traceback.format_exc())<br>
>>>><br>
>>>> should definitely have already imported "Image". If there are any<br>
>> generic<br>
>>>> fixes you can make to that block so that your installation works without<br>
>>>> Chris' patch, that would be something we could add to the main codebase.<br>
>>>><br>
>>> Hmm, I'm not a python user myself so it's kinda Chinese for me.<br>
>>> Sorry, I don't have any python skills (except of installing one and it's<br>
>>> modules.....)<br>
>>> Anyway AFAIK, additional "Import" shouldn't break anything in theory.<br>
>><br>
>> The issue with the import is that without the try/except block on any<br>
>> system that requires the "PIL" prefix, it will fail. I'm attaching a zip<br>
>> with a make file, could you unpack it and run it on your system:<br>
>><br>
>> /tmp $ unzip pil.zip<br>
>> Archive: pil.zip<br>
>> creating: pil/<br>
>> inflating: pil/Makefile<br>
>> inflating: pil/t1.py<br>
>> inflating: pil/t2.py<br>
>> inflating: pil/t3.py<br>
>> /tmp $ cd pil<br>
>> /tmp/pil $ make<br>
>> python t1.py<br>
>> Found PIL.Image: <module 'PIL.Image' from<br>
>> '/usr/local/lib/python2.6/site-packages/PIL/Image.pyc'><br>
>> python t2.py<br>
>> Found Image:<module 'Image' from<br>
>> '/usr/local/lib/python2.6/site-packages/PIL/Image.pyc'><br>
>> python t3.py<br>
>> Found PIL.Image: <module 'PIL.Image' from<br>
>> '/usr/local/lib/python2.6/site-packages/PIL/Image.pyc'><br>
>> Reimported Image: <module 'Image' from<br>
>> '/usr/local/lib/python2.6/site-packages/PIL/Image.pyc'><br>
>><br>
>><br>
>> Cheers,<br>
>> ~Josh.<br>
>><br>
>>>> Cheers,<br>
>>>> ~Josh.<br>
>>>><br>
>>>><br>
>>>>> Thank you,<br>
>>>>> Leon Kolchinsky<br>
>>>><br>
>>><br>
>>> Thanks,<br>
>>> Leon<br>
>><br>
>><br>
<br>
</div></div></blockquote></div><br></div></div>