https://git.openrobots.org/https://git.openrobots.org/favicon.ico?14752240372018-10-26T09:49:44ZOpenrobotsrobotpkg - Pull request #184: Update omniORB & omniORBpy to 4.2.2https://git.openrobots.org/issues/184?journal_id=3692018-10-26T09:49:44ZAnthony Malletanthony.mallet@laas.fr
<ul></ul><p>The default PREFER.omniORB on ubuntu 18.04 should not be 'robotpkg',<br />as this would create a big mess for people normally installing it via<br />system packages - and it would as a side effect create binary packages<br />pulling a custom version of omniORB.</p> robotpkg - Pull request #184: Update omniORB & omniORBpy to 4.2.2https://git.openrobots.org/issues/184?journal_id=3702018-10-26T09:52:02ZAnthony Malletanthony.mallet@laas.fr
<ul></ul><p>Also, middleware/omniORB and middleware/omniORBpy should be in sync.<br />It looks like you only updated middleware/omniORBpy.</p> robotpkg - Pull request #184: Update omniORB & omniORBpy to 4.2.2https://git.openrobots.org/issues/184?journal_id=3732018-10-26T10:12:55ZGuilhem Saurel
<ul></ul><p>I updated both:<br />- omniORB <a class="external" href="https://github.com/nim65s/robotpkg/commit/279f087fa29d681f5f8b0ec5cdc674f7c40eddb5">https://github.com/nim65s/robotpkg/commit/279f087fa29d681f5f8b0ec5cdc674f7c40eddb5</a><br />- omniORBpy <a class="external" href="https://github.com/nim65s/robotpkg/commit/1ed1a91be34ce1879415120a9685a6e8943989b8">https://github.com/nim65s/robotpkg/commit/1ed1a91be34ce1879415120a9685a6e8943989b8</a></p>
<p>About the PREFER, I don't really mind, as long as we can build packages with the python 3 version :)</p> robotpkg - Pull request #184: Update omniORB & omniORBpy to 4.2.2https://git.openrobots.org/issues/184?journal_id=3742018-10-26T10:17:17ZAnthony Malletanthony.mallet@laas.fr
<ul></ul><p>On Friday 26 Oct 2018, at 12:12, Guilhem Saurel wrote:</p>
<blockquote>
<p><a class="external" href="https://github.com/nim65s/robotpkg/commit/279f087fa29d681f5f8b0ec5cdc674f7c40eddb5">https://github.com/nim65s/robotpkg/commit/279f087fa29d681f5f8b0ec5cdc674f7c40eddb5</a></p>
</blockquote>
<p>Sorry, I missed that one ...</p> robotpkg - Pull request #184: Update omniORB & omniORBpy to 4.2.2https://git.openrobots.org/issues/184?journal_id=3792018-10-26T14:11:43ZJoseph Mirabel
<ul></ul><p>I do not know if it is possible to have simultaneously omniORB with python 2 and 3. The issue comes with omniidl (part of omniORBpy) which installs files in /usr/lib/omniidl/ regardless of the version of Python.</p>
<p>It will work only if theses files are compatible with Python 2 and 3. I believe the libraries won't be and the Python files will.</p> robotpkg - Pull request #184: Update omniORB & omniORBpy to 4.2.2https://git.openrobots.org/issues/184?journal_id=3802018-10-26T14:35:05ZGuilhem Saurel
<ul></ul><p>Then, we could either patch a few things to put omniidl in a path dependent of the python version, or rename it omniidl-py2 / omniidl-py3, or rename the packages to be robotpkg-py27-omniorb / robotpkg-py35-omniorb and set them incompatible to each other.</p> robotpkg - Pull request #184: Update omniORB & omniORBpy to 4.2.2https://git.openrobots.org/issues/184?journal_id=3812018-10-26T16:59:41ZAnthony Malletanthony.mallet@laas.fr
<ul></ul><p>On Friday 26 Oct 2018, at 16:11, Joseph Mirabel wrote:</p>
<blockquote>
<p>I do not know if it is possible to have simultaneously omniORB with<br />python 2 and 3. The issue comes with omniidl (part of omniORBpy) which<br />installs files in /usr/lib/omniidl/ regardless of the version of<br />Python.</p>
</blockquote>
<p>This is the debian packaging that installs files to /usr/lib/omniidl<br />for omniORBpy. robotpkg (or rather omniORBpy by default) installs them<br />in an appropriate location (PYTHON_SITELIB).</p>
<p>omniidl is however not part of omniORBpy, it's from omniORB. The fact<br />that omniidl is implemented in python is unrelated (although bringing<br />in a lot of confusion) to the omniORBpy target python version. For<br />instance, on ubuntu-18.04, omniidl uses python3 as it's interpreter,<br />but python-omniorb is for python2 (don't ask why).</p>
<p>It happens sometimes that a package is implemented in python (which<br />is an internal concern) and also produces or deal with python<br />code (I'm looking at sphinx or morse). Then the two python versions<br />are in principle unrelated, but in practice it's a mess to separate<br />the two. In particular, robotpkg cannot depend on more than one python<br />version for a package.</p> robotpkg - Pull request #184: Update omniORB & omniORBpy to 4.2.2https://git.openrobots.org/issues/184?journal_id=4042018-11-22T16:41:21ZGuilhem Saurel
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Closed</i></li></ul><p>I checked that we can now get gepetto-viewer-corba (on the devel branch, with minor updates) working with python3, so it's OK for me, thanks !</p>